Database Develop

[Q] Sprint OTA 4.4 on rooted (locked) 4.2.2 - Now reboots every 30 secs

So I had a rooted Sprint 4.2.2 (not unlocked, just rooted) and I got the OTA alert.
I accidentally installed it and it failed and now when it restarts, it gets to android for about 30 secs and then does the "powering off" bit and restarts... over and over.
In that 30 secs I can get to the settings and see that the version is still 4.2.2 so it didn't take. But it almost seems like it in stuck in that mode where it thinks it is doing the upgrade.
I tried killing memory resident stuff to prevent the restart to no avail.
I cannot get into any kind of stock recovery, it just reboots to normal mode
My only option is to go into Bootloader which does work.
But when I try to use RSD Lite and flash back to that last stock image, it shows
Failed flashing process 2/17 flash partition "gpt.bin"
I read that this may be due to the phone not allowing me to downgrade to a version lower than I currently have? Also read it could be the battery needs to be charged more.
Thoughts?

Can you get to the factory reset in that thirty seconds?
Sent from my XT1056 using xda app-developers app

If you can get to boot loader, will it go into recovery? If so, try restoring a backup. Likely you will have to do THIS, and I recommend doing this, the ota, then reroot.
Edit: if it boots to ROM for 30sec, try wiping cache and dalvik, then fix permissions, then reboot.

Ok so after reading around and doing some of my own playing around, I figured out how to fix it with some ideas from this thread
First off, the moto x rooting process actually REMOVES the recovery.img file from your phone, so what seems to be happening is that the upgrade downloads and starts to install... it attempts to load the recovery to flash the image, but since it doesn't exist, it just restarts the phone. When the phone restarts, the upgrade process still thinks it needs to run the upgrade, so it powers down.. this is where it gets stuck in the loop.
The solution is actually simple. Get into Bootloader mode (Power + Vol Down) which was slightly tricky since the phone always rebooted and never actually powered down. So I had to catch it at the end of the power off cycle, before it restarted. Once I was in bootloader mode I could use the following command:
Code:
fastboot erase cache
That seems to remove the downloaded update files as the phone stopped rebooting over and over.
But now I get Mobile IP Registration Error 67 (MIP) which basically means my registration data got wiped.. not sure I understand why that would happen.. but it basically means I need my MSL and have to enter the code to reset registration which will force a wipe of all data. At least I have the opportunity to back everything up over wifi now that I've stopped the looping.
The second part of this fix I haven't tried, but based on an educated guess, to actually GET the update correctly, I would need to flash the stock recovery image back using:
Code:
fastboot flash recovery recovery.img
where the recovery.img file comes from the zip file for the moto x stock image from the sbf repo:
http://sbf.droid-developers.org/phone.php?device=0
That of course needs to be done before I call Sprint to get my MSL and perform the reset.
All in all, a minor setback overall... better than a paperweight Perhaps instead of doing the erase cache step and just flashing recovery may have saved my MIP data
---- EDIT-----
Ah, gokart2, I see you had a similar process. Cheers

Turns out the Mobile 67 error was because my friend changed her service back to her old phone.... I should add that this wasn't my phone by my friend's phone.

Weir flash / memory problem on my m8

I just got and m8 from Cl, it was cheap and I was told the phone had a software issues so I took the plunge.
The phone seems normal, its pack o apps and you can play with it, then I decided to do a factory restore, but it failed (after the reboot it goes to a error screen showing a phone with and exclamation mark)
I tried the same from hboot, same result..
Tried to unlock bootloader, it appears to work but after boot the phone I still the same (loked and with all the user info intact )
Tried to erase the user accounts, it works, I can do a new setup of the Google account, but after restart the phone goes back to the initial state (user accounts are back)
I am not sure what's going on, but it looks like if the memory was protected and after every reboot it goes back to the original state.
Any suggestions of what to do? I am starting to see of there is any way to get warranty thru htc,
Thanks in advance.
The phone is in 4.4.2, can't take updated (it reboots itself on the process)

The phone with the exclamation point indicates the stock Android system recovery is installed. You could try and install TWRP recovery, at which time you could install a custom ROM. My only other thought is to run the RUU for the latest system update. If that doesn't straighten out your issues, something else is going on. Hit the link below and follow the instructions for the manual system update. This is the non-HK RUU. If you need the RUU for the HK version I can post it, also.
http://www.htc.com/us/support/htc-one-m8-sprint/news/

Thanks, I tried to install twrp but it fails, the bootloader is still locked and won't unlock, is there a way to install twrp without unlocking bootloader?
Will give it a try with the RUU, when tried to update thru fastboot it fails, it starts to do all the file checks and it just send you to the "press the power button message" , but no update was perform.

You might give this a try to get your bootloader unlocked and TWRP installed. There is no way around it. You have to unlock the bootloader first before you install TWRP.
http://forum.xda-developers.com/showthread.php?t=2727900

Thanks a lot for the help, nothing has work so far, the phone keeps having random reboots and every time it comes back its like it load an old backup, havent been able to do a firmwware upgrade (from android over wifi, fastboot, or windowsPC).
Is there an utility to test hardware? (possibly memory)
thanks

At the end I contacted HTC support and after some test I was told my phone was still under warranty and I got and RMA (great service)....
Thanks a lot for the help...

Tried to install OTAvwith TWRP, phone boots normally but then reboots to recovery

I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.

I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!

Issue returning N6 to stock - I've done it all

Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?

Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.

Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.

usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?

Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.

Need help rooting-

I am having a hell of a time rooting this phone. (Motorola Nexus 6 XT1100)
I am trying to follow this guide: https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
If anyone can offer some suggestions, they would be greatly appreciated.
I managed to get as far as unlocking the bootloader in fastboot mode.
The next step, obtaining root, is where all my problems started.
I downloaded CF Root and extracted the files, as instructed, allowed the root tool to run, (I'm using Linux, if it matters).
When the process was finished, and my phone attempted to reboot, it got stuck on the Google screen with the little lock (showing unlocked).
I allowed the phone to stay in this mode for around 30 minutes thinking it just needed time.
It never did anything. I attempted to let it try and start up again (a couple times actually) and it never goes past the Google lock screen.
I powered down the phone and restarted in fastboot mode, and attempted to run the CF Root tool again, with the same result.
I am currently stuck with only having access to fastboot.
I tried to flash a recovery and boot into that, but it won't allow that either. Perhaps this isn't even possible (YET), as it's not in the instructions to flash a recovery until after the rooting process, but I thought I would try it anyway.
I have tried flashing TWRP and Lineage recovery. No success with either, although the terminal is saying
sending 'recovery' OKAY
writing 'recovery' OKAY
But when trying to reboot recovery I get hit with
unknown reboot target recovery
Anyone know what's going on and how I can get this resolved? I just want to install a recovery and flash a custom ROM.

In that guide you can follow my journey to root starting in post# 929. I had & have had a LOT of help from my fellow XDAers. They're great & thank you all.

Thanks!
I'll check it out.

Boy, oh, boy.
I don't know what is going on.
I finally managed to get out of the bootloader screen.
I don't know what/how it worked. I downloaded Nexus Root Toolkit to a windows computer and tried the Flash Stock + Unroot option.
It keep saying waiting on device or device not detected or something ( I cant remember exactly, it was hours/many error screens ago!)
Next, I tried the option for Root + Add a Custom Recovery and directed it to where my TWRP file.
Again it acted like it was doing something. Even found my connected ADB device. Went through a couple processes, said it would need to restart a couple/few times. Everything was trucking along just fine until suddenly, it got hung up 'Waiting on device"
Not sure what happened, but all of a sudden, it could no longer find my device.
For chits and giggles, I decided to try and reboot recovery from the bootloader screen. I had attempted this many times and all it did was start back up in bootloader, BUT, this time, it actually started up in some recovery program I have never seen before. It wasn't stock and it certainly wasn't TWRP!
At this point, I hooked my device back into my computer running Linux and attempted to push TWRP, and reboot in recovery.
It worked!
Now that I had a recovery I was comfortable using, I proceeded to push my ROM.
Wanted to try Lineage with MicroG, but I am not advanced enough to go that route. I could not get a fake app store to work.
Guess I'll have to stick with what I know. I love the idea of MicroG, but it apparently doesn't work with Pure Nexus.
Anyway, just wanted to post some closure for this thread. I know the Motorola Nexus 6 is an old phone, but I like it. This is my second one. My first one, screen finally cracked and it was cheaper to just purchase a new one from Amazon than to replace the screen.