I upgraded to KK 4.4.2 but i didnt like it so i tired to downgrade back to 4.1.2 but i think i just bricked my phone. turns on goes straight to AP Fastboot. i can bypass by holding up + down + power and run via normal powerup, but my phone has no touch sensitivity now? help me please.
My phone is bricked ! Please help !
#1
Posted 05 June 2014 - 04:44 AM
#2
Posted 05 June 2014 - 04:50 AM
How To: XT907 Upgrade to KitKat OTA
Sent from my S-Offed One M8
- sadtechnerd1 likes this
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
#3
Posted 05 June 2014 - 05:31 AM
battery is now "low" after 6hrs battling these forums. IS there any possible way to charge it while its in Fastboot ? beside a DIY rig i seen on youtube?
#4
Posted 05 June 2014 - 05:37 AM
yeh i think i am done for, my batter is now low, the bootloader is locked why must i do a silly thing and try to downgrade. I deserved this, all of it.
#5
Posted 05 June 2014 - 05:41 AM
If you can get the device to power off, use a wall charger, not a usb on a computer, and it should charge. If not, you say you can get it to boot without touch, have you tried charging in that mode?
Otherwise, you could make the factory cable, or order the TeamBlackHat factory adapter.
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
#6
Posted 05 June 2014 - 06:01 AM
i have a wall charger it turns on and immediately goes straight into AP Fastboot, i can by pass the boot and run it via other options (Normal powerup,factory,tools, ect) but it doesn't show that my phone is being charged. I tried the method for upgrading to KK but it fails at 1/15.
RSD Error: Failed flashing process. 1/15 flash sbl1 "sbl1.mbn"
AP Fastboot Flash Mode (s)
10.9B(*) (sha-le9f557, 2013-09-26 13:20:55)
eMMC Info: Size 8GB
Device is LOCKED, Status code: 0
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Sticky bit factory_fastboot
usb connected
#7
Posted 05 June 2014 - 06:41 AM
Yeah, if the battery is low, don't continue flashing it. It can cause all sorts of problems up to and including a hard brick.
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
#8
Posted 05 June 2014 - 06:50 AM
woah it charged !!!! its now indicate that the battery is ok ! so what would i have to do now since upgrading to KK doesn't work for me?
#9
Posted 05 June 2014 - 06:55 AM
he gave you a link in earlier post
#10
Posted 05 June 2014 - 07:10 AM
It failed before because of the low battery state. Flash it again if the battery is truly charged. The sticky bit error may persist after flashing. If so, follow this:
Non potest esse nisi unus
#11
Posted 05 June 2014 - 08:21 AM
It failed before because of the low battery state. Flash it again if the battery is truly charged. The sticky bit error may persist after flashing. If so, follow this:
THANK YOU SO MUCH !!! that work well with the OP from livinginkaos . what would i do without you guys. =D
#12
Posted 05 June 2014 - 08:47 AM
can I use the same way to fix a razer xt 926, with the same problem.
#13
Posted 05 June 2014 - 08:51 AM
Was that a rhetorical question?
Non potest esse nisi unus
#14
Posted 05 June 2014 - 08:58 AM
And I wasn't being a smart ass by asking that. You obviously can't use the same FXZ to fix it, you need the one for the xt926. The sticky bit command works regardless. The thread I linked to was for an Atrix HD. I guess I don't understand what you're asking.
Non potest esse nisi unus
#15
Posted 05 June 2014 - 09:01 AM
No I update my Razr Hd ota to kk 4.2.2 and I did not like it; when I try to downgrade may phone to 4.2.1 the phone got stock on AP fastboot.
#16
Posted 05 June 2014 - 09:06 AM
Ok, well, you learned a valuable lesson I guess. "Don't do that". Now go here and fix it.
There is no downgrading on locked phones. As you both learned the hard way, it bricks things. I wish people would read before doing...it'd save everyone a lot of time.
Non potest esse nisi unus
#17
Posted 05 June 2014 - 09:12 AM
Sam, Sorry about the misunderstanding but I was reading the directions you gave to fix the bricked phone, and I noticed I got the same problem. may be you can help me with the Razer HD.
#18
Posted 05 June 2014 - 09:16 AM
Sam, Sorry about the misunderstanding but I was reading the directions you gave to fix the bricked phone, and I noticed I got the same problem. may be you can help me with the Razer HD.
I would recommend following the thread Sam gave you and further posting in that thread so as not to confuse people. Flashing the wrong FXZ to the wrong phone causes Perma-Brick
#19
Posted 05 June 2014 - 09:20 AM
Yes, I provided you a link to the RAZR HD xt926 KK thread. NO ONE on an xt907 should be using that. And likewise, no one on an xt926 should ever flash an xt907 FXZ. As mentioned, it will perma-brick the phone with no chance of fixing it. Heed the warning carefully. What I gave you for a link is what you should follow. The other person was on an xt907 and rightly followed the link Kaos posted. I don't want there to be any confusion here.
Non potest esse nisi unus
#20
Posted 05 June 2014 - 09:42 AM
Sam, Thank you So much. I learned the lesson.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users