I unlocked the bootloader to my phone then tried to install the new 4.5.91 update. I think this is the problem. I should have updated first then unlocked.
What is happening to my phone now is that while the package is installing, it stops about 1/5 of the way and shows an exclamation point in a triangle. Does this mean I bricked it?
I took out the battery and turned on my phone again but I can't use it because it automatically goes back to trying to install the 4.5.91 update. Then goes back to the exclamation point screen.
Anyone know what is happening and what I can do to fix this? Thanks!
I tried factory data reset and it fixed the problem of the phone automatically installing the update every time I turn on the phone. I can now use my phone again but what should I do about updating it to 4.5.91 gingerbread? Again, the bootloader is already unlocked. I'm also using a gingerblur rom..don't know it that might help too. Thanks!!!
phbslmgui said:
I unlocked the bootloader to my phone then tried to install the new 4.5.91 update. I think this is the problem. I should have updated first then unlocked.
What is happening to my phone now is that while the package is installing, it stops about 1/5 of the way and shows an exclamation point in a triangle. Does this mean I bricked it?
I took out the battery and turned on my phone again but I can't use it because it automatically goes back to trying to install the 4.5.91 update. Then goes back to the exclamation point screen.
Anyone know what is happening and what I can do to fix this? Thanks!
I tried factory data reset and it fixed the problem of the phone automatically installing the update every time I turn on the phone. I can now use my phone again but what should I do about updating it to 4.5.91 gingerbread? Again, the bootloader is already unlocked. I'm also using a gingerblur rom..don't know it that might help too. Thanks!!!
Click to expand...
Click to collapse
I believe that, since your bootloader is already unlocked, you could try this. Assuming, of course, you are using an AT&T Atrix. And when you're using a custom ROM on any device, it is never a good idea to install an OTA
Let me know if you need anything else.
Related
I'm still new to this and I was hoping that someone could give me some help. The phone is a rooted tbolt running stock.
I grabbed the ota update this morning. The phone reboots and starts installing the update but I get the exclamation mark with the droid guy about 40% of the way through. I power cycled the phone after the error and everything came up normally. It took a few minutes, but then the phone rebooted to try and install the update again (and fails at 40%). Seems to be a pretty annoying loop.
Has anyone else experienced this and is there any way for me to tell the phone to stop trying to update?
skeezbo said:
I'm still new to this and I was hoping that someone could give me some help. The phone is a rooted tbolt running stock.
I grabbed the ota update this morning. The phone reboots and starts installing the update but I get the exclamation mark with the droid guy about 40% of the way through. I power cycled the phone after the error and everything came up normally. It took a few minutes, but then the phone rebooted to try and install the update again (and fails at 40%). Seems to be a pretty annoying loop.
Has anyone else experienced this and is there any way for me to tell the phone to stop trying to update?
Click to expand...
Click to collapse
It's because your rooted. Th OTA can't install with the clockworkmod recovery installed. Grab the rooted OTA (google it I don't have a link) and flash that and flash the kernel via bootloader.
Sent from my rooted stock OTA MR2 Thunderbolt
After reading about the update I'm not entirely sure that I want it. Is there any way to stop the phone from trying to install the update now?
install a rom thats the main reason we root the phone in the first place
Do you have a nandroid backup? Revert to that if you do. Otherwise, the only way to get rid of that is probably going to be to flash to full RUU over again (you'll be back to 100% stock and lose data and root)
Boot into clockwork recovery and wipe cache ONLY. Might work I'm not sure, but it definitely won't hurt.
Sent from my HTC Thunderbolt
JBO1018 said:
Boot into clockwork recovery and wipe cache ONLY. Might work I'm not sure, but it definitely won't hurt.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yessir, causes the update to fail before the reboot. Thanks so much!
No prob and by the way for future reference don't flash official updates over rooted phones. It's known to cause issues. Just wait for someone to post a rooted version of the update.
Sent from my HTC Thunderbolt
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
wingnutta said:
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
Click to expand...
Click to collapse
Are you rooted? That would be why. It's not advisable to accept an OTA update when your system has been altered. Unlocked is ok, just not rooted/modded.
If you are rooted and have a nandroid backup from before the update, try to restore from there. If not, boot into fastboot and restore to your model's original stock image (from motodev) then let the OTA updates bring you up to 3.1 and then 3.2. Re-install CWM Recovery, and re-root after that with solarnz' Universal Xoom Root and go from there.
If you're not rooted and your system is just continually rebooting, you should still try the fastboot/restore stock images procedure. There may be something easier, but I'll let someone else advise you on that.
Good luck!
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
wingnutta said:
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
Click to expand...
Click to collapse
I can't think of any way to resolve this that doesn't involve a wipe of some kind. Have you checked any other Moto/Xoom forums to see if anyone else had the same problem?
My condolences on the irritating situation and the potential loss of your stuff. Actually, a good reason to root is that you can back everything up!
Well i took the plunge and wiped by unlocking. Cured the bootlooping (obviously), and so then thought - why not root aswell
All done and running Tiamat 2.2 and very happy!
Appreciate the help peeps..
Hi folks, this is my first thread in this section of the forum, because i was using my old device LG p500 and now i moved to this wonderful smartphone. So, i'd like to solve this problem which is happening now. Basically, the phone unexpectedly stops, and reboot. It happens a couple of times, i guess 3 times in a week. It wasn't happening in ICS, just now that i upload from OTA to Jelly Bean. Note that this was happened while my phone was Unrooted and with Locked Bootloader, the same occured with root and unlocked bootloader. So, any clue? Maybe i should just change the rom, or clean everything as fast as i can.
Thank you.
ermito said:
Hi folks, this is my first thread in this section of the forum, because i was using my old device LG p500 and now i moved to this wonderful smartphone. So, i'd like to solve this problem which is happening now. Basically, the phone unexpectedly stops, and reboot. It happens a couple of times, i guess 3 times in a week. It wasn't happening in ICS, just now that i upload from OTA to Jelly Bean. Note that this was happened while my phone was Unrooted and with Locked Bootloader, the same occured with root and unlocked bootloader. So, any clue? Maybe i should just change the rom, or clean everything as fast as i can.
Thank you.
Click to expand...
Click to collapse
If you took the OTA then you are sol and will not be able to unlock your bootloader to flash a custom recovery or a rom the traditional way. There is safestrap but thats less than optimal for flashing. As far as the reboots go, it is probably an app that is causing the issues. I would do a factory reset and be selective about the apps I re-installed.
mentose457 said:
If you took the OTA then you are sol and will not be able to unlock your bootloader to flash a custom recovery or a rom the traditional way. There is safestrap but thats less than optimal for flashing. As far as the reboots go, it is probably an app that is causing the issues. I would do a factory reset and be selective about the apps I re-installed.
Click to expand...
Click to collapse
What are you saying? I'm already unlocked bootloader and flashed a custom recovery and it's been working normally.
ermito said:
What are you saying? I'm already unlocked bootloader and flashed a custom recovery and it's been working normally.
Click to expand...
Click to collapse
Sorry I must have glazed over the part about you having your bootloader unlocked.
Hi, i changed to the SlimRom since then and the reboots still happen, i'm very frustrated. It freezes, then reboot into the bootloader screen and stays there for ever until i press the power button for a while and the phone vibrate 3 times and after that it boot normally.
Here's a step-by-step of what happened:
Two days ago (I think) the KitKat update for XT925 was released. When the download was done, as I was playing CoC on my phone, my handset asked for permission to instal it. Right after I allowed it, I left for lunch or w/e, and when I came back my phone was on this boot image, with the motorola "M" logo sitting there, laughing at me. Went the rest of the day without my phone because I thought it was still finishing the installing. When I finally got home at night, still the same screen.
I DID root it, but no such things as CyanogenMod or anything else were flashed to it, so I got no backups. Bootloader is still locked. Already tried wiping cache and a factory reset from the recovery mode. After googling it for some good time now, this is my last hope. What am I supposed to do? I encrypted it if that helps in anything. Complete newbie here.
phmrr said:
Here's a step-by-step of what happened:
Two days ago (I think) the KitKat update for XT925 was released. When the download was done, as I was playing CoC on my phone, my handset asked for permission to instal it. Right after I allowed it, I left for lunch or w/e, and when I came back my phone was on this boot image, with the motorola "M" logo sitting there, laughing at me. Went the rest of the day without my phone because I thought it was still finishing the installing. When I finally got home at night, still the same screen.
I DID root it, but no such things as CyanogenMod or anything else were flashed to it, so I got no backups. Bootloader is still locked. Already tried wiping cache and a factory reset from the recovery mode. After googling it for some good time now, this is my last hope. What am I supposed to do? I encrypted it if that helps in anything. Complete newbie here.
Click to expand...
Click to collapse
being locked, i believe the only way to "try" and fix it would be to re-flash the kk sbf for your region with rsd. however, if the update is just rolling out, i doubt that is available yet.
im pretty sure you are stuck until you find this stock file, or it is released.
What was your battery at when you started the update?
Sent from my HTC6525LVW using Tapatalk
I have had nothing but issues with this phone upgrading. Every time it bricks, the first time I got it working by reformatting DATA partition. The other times basically gave up and 2-3 days later I come back and it magically starts working again. The day that 5.0.1 came out I downloaded the FUU, well everything looked good the it gets stuck at the Android is upgrading starting apps. Since then I have redownloaded all 5.0.1 files I could find on XDA, and the same results. I tried different roms, using TWRP to wipe and rewipe and format and do it again and again. I have tried to downgrade to 4.4.2 and 4.4.4 but i get the process system isn't responding when it boots up. I am unsure what to do now, anything will help.
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
berndblb said:
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
Click to expand...
Click to collapse
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
dab1414 said:
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
Click to expand...
Click to collapse
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
andybones said:
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
Click to expand...
Click to collapse
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
dab1414 said:
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
Click to expand...
Click to collapse
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
andybones said:
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
Click to expand...
Click to collapse
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
dab1414 said:
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
Click to expand...
Click to collapse
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
andybones said:
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
Click to expand...
Click to collapse
Yes I am S-OFF since the day I got the phone. And I have been using RKND roms, but I downloaded and tried all the 5.0.1 roms to see if anything would help. At this point I just want my phone working again, but preferably with the ability to change roms when i want to which is about once a month or two.
So I had tried everything I knew how to do again with no luck. Then I just let my phone sit for the last week. Then I decided to turn it on last night and it works fine. Is there any reason why I had to let the phone stay powered down for days for it to start working? This is the second time I had to do that when upgrading the firmware.
Thanks for bringing this up and I'm glad to hear it worked out for you even tho it took some time. My bro just ran the vzw update while on viper 4.1.0 and now he says his screen is unresponsive. He said it ran through all the normal start up procedures but the welcome screen is shaded (like it's in the background) and he says it won't respond to any touches whatsoever. I won't get a chance to see it until I return to work on Wednesday but if it does the same as yours maybe it'll fix itself by then. :fingers-crossed:
Edit: I just realized that you ran the FUU. He went and said yes to the stupid OTA! Hopefully I'll be able to do something with it when I get back but I'm thinking that running the OTA while rooted and S-Off'd might've screwed it up.
Update: I'm a moron! :silly: It didn't do anything to his phone. I just had to reinstall the recovery and viper 4.3.0 and it's working fine again. I think actually it might've been a good thing he did cause now the phone had the right firmware on it for LP so it all worked out. Sorry for cluttering up your thread.