Database Info

[Q] Grabbed Update today and stuck

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

New 3.2 update bootlooping?

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..

[Q] Possible to root 4.1.1?

My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?

Reciprocate said:
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2046439

Reciprocate said:
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Click to expand...
Click to collapse
hey guy my question is did u unlock ur bootloader before rebooting also remember if u can manually boot into cwm u can redo the rom its either the up volume or down plus multi function button and power button at same time to go right to cwm

wingtytn said:
hey guy my question is did u unlock ur bootloader before rebooting also remember if u can manually boot into cwm u can redo the rom its either the up volume or down plus multi function button and power button at same time to go right to cwm
Click to expand...
Click to collapse
I think i actually locked it after i finished the install. And then restarted, do softbricks occur when you re-lock your bootloader?
Also another question..is there any way to check the /system /data partitions from inside the phone (terminal app maybe?) are correctly set to r/w over r/o (i don't like unplanned installs )

Soft bricks always occur on a locked bootloader. There are file managers that can do that like solid explorer.

jmxc23 said:
Soft bricks always occur on a locked boot loader. There are file managers that can do that like solid explorer.
Click to expand...
Click to collapse
Ah dully noted in the future the boot loader will be left unlocked! and thanks for the app recommendation i downloaded it and checked all my permissions I'm slightly less terrified to restart my phone now
thanks for all you help

[Q] Deleted OS from phone?!

So, I'm really sorry if there is an easy answer to this....but I swear I have looked....
I was running CM10.0 on a rooted gs3. I tried to update to 10.1 and the phone lost its mind. I booted it into TWRP and tried to do a factory reset, but that didn't help. Originally the phone would start. But gmail, the play store and most apps all crashed. So I kept messing around in recovery trying to undo the update.
Getting frustrated and confused I apparently wiped my system. I can't start the phone at all. I tried to flash another custom ROM which failed.
What is the easiest way to fix this? Would it be to use ODIN and flash a ROM? The only reason I didn't try this yet is I'm confused about the no OS. I start work as a pediatric intern tomorrow and need to have a working phone. I would normally spend more time trying to figure this out on my own but I'm kind of a nervous wreck at the moment, and need to try and get some sleep before the big day tomorrow.
I really don't care if the phone gets unrooted and back to stock, I just want a working phone...

Neya86 said:
So, I'm really sorry if there is an easy answer to this....but I swear I have looked....
I was running CM10.0 on a rooted gs3. I tried to update to 10.1 and the phone lost its mind. I booted it into TWRP and tried to do a factory reset, but that didn't help. Originally the phone would start. But gmail, the play store and most apps all crashed. So I kept messing around in recovery trying to undo the update.
Getting frustrated and confused I apparently wiped my system. I can't start the phone at all. I tried to flash another custom ROM which failed.
What is the easiest way to fix this? Would it be to use ODIN and flash a ROM? The only reason I didn't try this yet is I'm confused about the no OS. I start work as a pediatric intern tomorrow and need to have a working phone. I would normally spend more time trying to figure this out on my own but I'm kind of a nervous wreck at the moment, and need to try and get some sleep before the big day tomorrow.
I really don't care if the phone gets unrooted and back to stock, I just want a working phone...
Click to expand...
Click to collapse
Well likely you somehow corrupted one of the system partitions.
ODIN back to stock and it should fix everything

Neya86 said:
So, I'm really sorry if there is an easy answer to this....but I swear I have looked....
I was running CM10.0 on a rooted gs3. I tried to update to 10.1 and the phone lost its mind. I booted it into TWRP and tried to do a factory reset, but that didn't help. Originally the phone would start. But gmail, the play store and most apps all crashed. So I kept messing around in recovery trying to undo the update.
Getting frustrated and confused I apparently wiped my system. I can't start the phone at all. I tried to flash another custom ROM which failed.
What is the easiest way to fix this? Would it be to use ODIN and flash a ROM? The only reason I didn't try this yet is I'm confused about the no OS. I start work as a pediatric intern tomorrow and need to have a working phone. I would normally spend more time trying to figure this out on my own but I'm kind of a nervous wreck at the moment, and need to try and get some sleep before the big day tomorrow.
I really don't care if the phone gets unrooted and back to stock, I just want a working phone...
Click to expand...
Click to collapse
You will need to go to a Stock Image via Odin.

DarkMenace said:
You will need to go to a Stock Image via Odin.
Click to expand...
Click to collapse
Thanks guys, I finally got it working!
I thought that was what I needed to do, but I was so confused when it said I erased the OS...
Now to try and get some sleep before the first day on the job!

[Q] random shutdown and bootloop

Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.

arsenaljordan said:
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
Click to expand...
Click to collapse
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.

GUGUITOMTG4 said:
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
Click to expand...
Click to collapse
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.

arsenaljordan said:
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
Click to expand...
Click to collapse
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one

GUGUITOMTG4 said:
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
Click to expand...
Click to collapse
I have already flashed the stock recovery and ROM back to the device