So my Droid Turbo JUST had an upgrade pushed through and now it's locked up and frozen.
Anyone else having issues. And what do I do to resolve it.
Happen to see the number on that update? Were you unlocked and rooted?
I would try to reboot to recovery and wile the cache as a first attempt.
Related
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Well, unfortunately with the screen cracked, you can't return to Motorola. I had a goof with my Atrix when I first got it because I accidentally did a SBF flash to the wrong version and it bricked the phone and fried the motherboard and Motorola replaced it because I said the Gingerbread update messed it up. Ha.
Anyways, since returning to Moto is not an option for you, I would just go ahead and try to install a custom ROM, maybe try Neutrino ROM 2.2 or 2.5?
Do you have ROMRacer Recovery or CWM Recovery installed? Will it let you get into it? If so, put a custom ROM on your SD card, do a wipe data and cache and install it.
I'm no expert, but I have noticed no one else replied and just trying to help.
Hope all works out for you!
Boot loop issue - at&t Android 2.3.6
Thanks andreww88 for your reply. I read in one of the forums that once the phone is updated with 2.3.6 don't try to go back to older versions especially lower than 2.3.4. That would make the phone to be hard bricked. That is why I didn't try any other ROM other than NottachTrix 4G because it is built on 2.3.6. I could be wrong. That is why I need some guidance to try any other custom ROM.
i had the same issue. What i did was get the Atrix Fastool and whipe the phone. Then i extracted the sbf for 141 and then flashed 59 60 and 61 smg files from fastboot. After that everything worked properly. To then unlock my bootloader i used the flashing script and i was set. This is recoverable not easy but you can recover.
Thanks Moneyman1978 for your reply. Can you be more detail what you did to resolve this issue. Can you send me the links or point me to Fastool and 141 .SBF file also SMG files. Thanks again.
gpr789gpr said:
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Click to expand...
Click to collapse
Well, I had a similar issue. I did the 4.5.141 (OS 2.3.6) OTA update and then it would just bootloop. I'm on stock, rooted, locked BL. I then ran the OTA update again via recovery and that didn't help. I then did a full factory reset, then update via recovery and still didn't fix anything (good thing I had TiBu backup). After calling AT&T they finally admitted that Moto recalled the 4.5.141 build update since there was WIDESPREAD boot-loop issues with many Atrix users. Great.
They're sending me a new phone. Luckily, mine is in good condition.
Any one please have any suggestions for me. Do you think it is a hardware issue or can it be fixed by fixing the software??? Any help is appreciated.
If any of you has any ideas about how to fix this issue I would appreciate if you can share it here.
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
sucinimad said:
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Click to expand...
Click to collapse
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
deusfaux said:
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
Click to expand...
Click to collapse
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
deusfaux said:
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
Click to expand...
Click to collapse
In the end, I went through almost the exact experience (including red LED). Running on stock 4.3 image now. Thanks.
my phone is reboot today.
there might be problem with rooted stock kernel?
there are someone has same problem?
Acuity said:
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
Click to expand...
Click to collapse
i got the same issue, look here: http://forum.xda-developers.com/showthread.php?t=2380546
Hello,
New to xda-developer forum, but was hoping I could get some help.
I have a Droid Razr M, that has had the boot loader unlocked, but not rooted anymore, after getting an update prior to kitkat. If I remember correctly I was able to get previous updates with no issues with the boot loader unlocked. Today I heard that kitkat was out for my device, so I went into settings to check for a system update and I was offered to update to 4.4.2 (Kitkat). So I went ahead and did it.
However, the problems lies now that It is stick in a boot loop, with the "WARNING BOOTLOADER UNLOCKED" message that I always got after unlocking it. I noticed after the update the boot was taking a really like time, but then I noticed it would **** off and god right back to that same message. Knew something wasn't right, Itll shut down and reboot the that screen multiple times. I first tried clearing the cache partition. Nothing. Tried resetting/wiping, that also didnt fix it.
Some help would be greatly appreciated here.
If you need more information I can try my best.
Thank you!
So I just flashed back to stock 4.0.4 ROM with RDS Lite. Trying the OTA Kitkat update again, and now its just stuck at a black screen. I had it plugged into the charger as it was updating so its not dead. I cannot get it to reboot.
I've been trying to get the latest update (apparently it will fix the bluetooth issue), it downloads fine, goes into recovery, tries to do a system update and it errors out and reboots (and reports as failed).
I've tried 4 times over the past couple of days.
Anyone else experiencing a similar issue?
Any tips to get it working?
The update name is: update_SM-G900V_NE9_to_NI2
arian08 said:
I've been trying to get the latest update (apparently it will fix the bluetooth issue), it downloads fine, goes into recovery, tries to do a system update and it errors out and reboots (and reports as failed).
I've tried 4 times over the past couple of days.
Anyone else experiencing a similar issue?
Any tips to get it working?
The update name is: update_SM-G900V_NE9_to_NI2
Click to expand...
Click to collapse
I'm having the same issue. If anyone figures this out, please let me know.
Also Failing
I'm in the same boat. I've tried five times over a week. Keeps reporting a failure after the reboot.
I did have it rooted, but lost it from the last update. Haven't tried to root it again, so I don't think that would cause any issues.
I'm on Verizon. Hopefully somebody can figure it out.
Bump.
It's still happening. Anyone?
Still fails after factory reset
So Verizon claims to try taking the battery out and retrying to install the update. Tried it. Update fails.
After a couple weeks of this, I caved and did a factory reset. Update still fails. It seems to fail about 30% into the progress bar during recovery mode.
Possibly going to the Samsung guys at Best Buy will solve this...
My sister's sgh-i337 recently received an ota update. This update brought it up to Android version 4.4.4. The phone is not rooted and is completely stock. Since the update the phone will intermittently freeze up for about 30-40 seconds. It happens a lot when she swipes to answer a call but also happens randomly as well. Is this a known issue? Are there any solutions? I have booted to recovery and cleared the caches but that didn't help.
ElAguila said:
My sister's sgh-i337 recently received an ota update. This update brought it up to Android version 4.4.4. The phone is not rooted and is completely stock. Since the update the phone will intermittently freeze up for about 30-40 seconds. It happens a lot when she swipes to answer a call but also happens randomly as well. Is this a known issue? Are there any solutions? I have booted to recovery and cleared the caches but that didn't help.
Click to expand...
Click to collapse
You could try one of the back up programs to My Backup to back up app data & photos then try a factory reset. Also you could check for the 5.01 Ota update that was released last month I think and see if that fixes it. Just be forwarned that some people have reported issues with the 5.01 update but said a factory reset fixes them.