I have a stock droid charge- installed OTA update, and now it bootloops at the samsung logo screen. Any advice? Already did factory reset and cleared cache. Might have to go complain to Verizon?
Codyktt said:
I have a stock droid charge- installed OTA update, and now it bootloops at the samsung logo screen. Any advice? Already did factory reset and cleared cache. Might have to go complain to Verizon?
Click to expand...
Click to collapse
if your phone was rooted, then it will not be able to install the OTA update. if stock and unrooted, then it should - and I would certainly contact VZW (unless you decide to root and upgrade to dwith's most efficient custom ROM, tweaked). he'll be adding FP5 in his next release.
Saved it, thanks to imnuts
For anybody else with this issue...
http://forum.xda-developers.com/showthread.php?t=1111486
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..
just use the one click root tool by kennethpenn, work perfectly thanks. use titanium back to do a backup of all the app and system then took out all the att bloatware. i have few questions at this point.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
3.
what other things i can do after i root the phone at this point?
thank you for your help
no one can help me with those questions??? anyone???
i am sure a lot of people have the same question.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
I'm not 100% sure on this, but as long as you're running an actual AT&T ROM (not an Asian or Rogers ROM), you'll be notified of the OTA's. Now, if you're not using the stock Recovery image (that is, if you've installed CWM Recovery), you won't be able to apply the update. OTA updates get applied via the stock Recovery image.
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
If you do a factory reset from CWM or within the phone's UI, you're fine. Root will remain in place, and you won't brick it. It just clears the user data from the phone, and should leave "sdcard" intact. However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
3.
what other things i can do after i root the phone at this point?
You ca use apps like AutoKiller to change your memory management, for one. That's about all I'm doing with root right now. If we ever get custom kernels, you'll be able to overclock your CPU. If you search the Play Store for "root," you'd doubtlessly find some other root apps that you may be interested in.
Hope this helps!
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
craig0r said:
However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
Click to expand...
Click to collapse
I can confirm that it's OK. My phone was rooted and stuck in a boot loop. I did a factory reset. It was reset and still rooted after the fact. So you can do it.
thank you all
redpoint73 said:
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
Click to expand...
Click to collapse
Just to clarify, pre-rooted versions of the official ROMs (which often get posted on XDA, as I mentioned) may need unlocked bootloader to install, so this will possibly not be an option for a while. Although there may be alternate safe ways to update (but not OTA). For instance, a leaked 1.83 firmware version is already available as an RUU in the Development subforum. Apparently, its okay to install via RUU, then re-root.
In general, the safe thing to do is to read up on here when updates are released, and see if there is a safe way to update on a rooted phone.
Hello,
I have an ATT Skyrocket on ICS (I727 UCLIC3). It's all stock and not rooted.
When I connected to Kies, I get a notification stating Android 4.1.2 I727 UCMC1 is available
1. I wanted to check if this update any known issues? and if i should take any precautions?
2. If I don't like this JB, is there an option to revert back to stock ICS? or is it point of no return?
If yes to question #2, How do I do a full back up before update? Should install CWM or TWRP for that?
And then I have to factory reset before JB update so the custom recovery won't interfere with JB upgrade?
Thx
Best advice is for you to read all of the stickies in the Skyrocket sub forums. Also, read the threads that have already been started about the update. The answers to all of the questions you asked and much more are there. It will also help you to learn ways to prevent hard or soft bricks, and what to do if you encounter issues. Good luck.
If you install CWM, you need to be rooted. If your rooted, you can't update to JB. Also, there is a thread with issues of JB. http://forum.xda-developers.com/showthread.php?t=2230909
I am pretty sure there is a way to do a backup on stock. Forgot though. Search though. The answer could be there.
Thx.
One more question: Should I reset factory reset my skyrocket? (before I let Kies update it to JB)?
I may have uninstalled or disabled some at&t bloatware... hence wondering it's better to factory reset before JB update...
gcretro said:
Thx.
One more question: Should I reset factory reset my skyrocket? (before I let Kies update it to JB)?
I may have uninstalled or disabled some at&t bloatware... hence wondering it's better to factory reset before JB update...
Click to expand...
Click to collapse
Not necessary to revert to factory settings before you update using kies, sure all the settings of your currant rom will be lost once you're on JB, but data on your internal sdcard should be left intact like pictures and music..Better to back it up some where before you proceed..
I didn't do anything at all before updating (I use the standard AT&T firmware) and all I really lost was my home screen layouts; all my apps were still there, settings intact, still logged on as applicable. I did have a moment of panic when the phone first started up when it brought up the AT&T app that sets up a new phone from scratch. I thought that meant that it had done a full factory reset, but after getting out of that everything was there except for the re-initialized home screens.
I did the JB update via kies. So far all good. yes, I had to resetup my app shortcuts.
I read that this update should provide skyrocket users with the "Smart Stay" feature... but i don't see it anywhere under settings.
Btw, should i factory reset my phone now AFTER JB update? in case something is still not activated or something
gcretro said:
I did the JB update via kies. So far all good. yes, I had to resetup my app shortcuts.
I read that this update should provide skyrocket users with the "Smart Stay" feature... but i don't see it anywhere under settings.
Btw, should i factory reset my phone now AFTER JB update? in case something is still not activated or something
Click to expand...
Click to collapse
If everything seems to be working, don't factory reset. With factory reset you will lose your apps and settings.
Sent from my SGH-I727 using xda app-developers app
Hey Ya'll,
Updated my phone this morning with the official T-Mobile Nougat update and man is my phone lagging! Anyone else having this problem?
-Travis
I didn't. What I did have was bootlooping that started about 48 hours after installation. Stock, not rooted and very minimal apps. I ran a factory reset and it has been much better.
My phone is bootlooping, too, after the update. My phone is also stock, not rooted. I'm afraid to do a factory reset, as I don't want to loose all of the photos of my new baby. I wish I hadn't delayed turning on my cloud back up.
anbowlynn said:
My phone is bootlooping, too, after the update. My phone is also stock, not rooted. I'm afraid to do a factory reset, as I don't want to loose all of the photos of my new baby. I wish I hadn't delayed turning on my cloud back up.
Click to expand...
Click to collapse
( it was the same problem with my S5 from 5.0.1 to MM will never do same error save all yr data and do clean flash )
1- do just cache clean
2- you can flash the old MM tmb but dont flash csc flash HOME_csc
but wait for more suggestion but for me is that the only solution
hapakun said:
Hey Ya'll,
Updated my phone this morning with the official T-Mobile Nougat update and man is my phone lagging! Anyone else having this problem?
-Travis
Click to expand...
Click to collapse
same. s7 slow and laggy as hell crappy battery life. they did this with the s5 too. slowed it down with updates until youre forced for a new phone.
This last update definitely negatively impacted my battery life. Stock, no root, and I wiped cache. I'm not in the mood to do a factory reset. Weasles.