Database Users

4.1.2 OTA Stuck in bootloop

Hey guys,
I've just tried updating my Nexus 7 to 4.1.2 OTA, after the download was installed it tried to reboot and it's just hanging on the Nexus logo boot screen. I've tried to boot in to recovery mode but I just get the little android with the red exclamation mark triangle.
My device is not rooted and was previously running completely stock firmware 4.1.1, never tweaked at all.
Any ideas would be very helpful - apologies if this is a glaringly obvious fix, I haven't searched much as I'm posting from my phone.
Many Thanks

I am having the same problem but mine is rooted. So I was probably thinking I was having the problem cos it's rooted.
Sent from my Nexus 7 using xda app-developers app

venturion said:
Hey guys,
I've just tried updating my Nexus 7 to 4.1.2 OTA, after the download was installed it tried to reboot and it's just hanging on the Nexus logo boot screen. I've tried to boot in to recovery mode but I just get the little android with the red exclamation mark triangle.
My device is not rooted and was previously running completely stock firmware 4.1.1, never tweaked at all.
Any ideas would be very helpful - apologies if this is a glaringly obvious fix, I haven't searched much as I'm posting from my phone.
Many Thanks
Click to expand...
Click to collapse
Do you have the 4.2.1 bootloader? or it might not work.

Don't think so, it's completely standard. Been updated from 4.1.0 to 4.1.1 when I bought it, since then only change to the firmware I've made is today downloading 4.1.2.

Did you do a manual update or was it system self prompted update?

I was notified that an update was available by my device. I pressed install now, it downloaded and the device rebooted and started installing it. Then it triedvto boot back up and failed.

if this happened and you did NOT root or unlock the bootloader, then you are eligible for a replacement. go to the store you have bought it from and ask for a replacement unit. if you did unlock the bootloader, then you have to boot into bootloader and use this tool and select 9 after installation. it should return your device to stock, providing you can still boot into bootloader. good luck!

Billchen0014 said:
if you did unlock the bootloader, then you have to boot into bootloader and use this tool and select 9 after installation. it should return your device to stock, providing you can still boot into bootloader. good luck!
Click to expand...
Click to collapse
I'm in this boat, unlocked bootloader, and had this porblem. What tool are we speaking of?

Billchen0014 said:
if this happened and you did NOT root or unlock the bootloader, then you are eligible for a replacement. go to the store you have bought it from and ask for a replacement unit. if you did unlock the bootloader, then you have to boot into bootloader and use this tool and select 9 after installation. it should return your device to stock, providing you can still boot into bootloader. good luck!
Click to expand...
Click to collapse
I was hoping that wouldn't be the case to be honest and that I'd be able to fix it myself, ah well. Thanks a lot for your help

Just so everyone knows, I took my tablet back and got a new one, which when updated broke again. I got a third tablet and contacted Google directly, they told me they can't really help but try updating again, which I did and bricked my 3rd device in a row. When I called Google again they said I need to speak to Asus (regarding this issue with Android software) in terms of getting another replacement. Which means I'll be left without a device until they replace it!

Wow, the same problem as I had.
My brand new, stock nexus 7 (4.1.1) informed me there was an update so I allowed it to install it.
It was connected to the PC during the whole process.
It installed the update, but got stuck on the boot screen (the X logo). It took too long so I suspected something went wrong...
In a few minutes I was forced to learn how to do a forced restart, enter the recovery menu, etc.
But sadly nothing helped, as it ALWAYS ended up showing that X logo and would not go further. So I decided for a drastic measure and wiped the device (reset to factory settings). Unsurprisingly, it then booted fine and the new update was there.
Of course I lost all my game saves and other data... Really pissed off, but decided to swallow it for the time being.
If this happens at the next update, I'll definitely say goodbye to the Nexus. Would be a shame though, as it's a lovely device, very handy.
Just for the record, I live in the EU and the device was bought in a brick and mortar shop, and it had 4.1.1 installed.

bangawasawa said:
Wow, the same problem as I had.
My brand new, stock nexus 7 (4.1.1) informed me there was an update so I allowed it to install it.
It was connected to the PC during the whole process.
It installed the update, but got stuck on the boot screen (the X logo). It took too long so I suspected something went wrong...
In a few minutes I was forced to learn how to do a forced restart, enter the recovery menu, etc.
But sadly nothing helped, as it ALWAYS ended up showing that X logo and would not go further. So I decided for a drastic measure and wiped the device (reset to factory settings). Unsurprisingly, it then booted fine and the new update was there.
Of course I lost all my game saves and other data... Really pissed off, but decided to swallow it for the time being.
If this happens at the next update, I'll definitely say goodbye to the Nexus. Would be a shame though, as it's a lovely device, very handy.
Just for the record, I live in the EU and the device was bought in a brick and mortar shop, and it had 4.1.1 installed.
Click to expand...
Click to collapse
Hi. Slightly off topic, but maybe worth mentioning : I have exactly the same problem with the 4.1.2 OTA update of the Nexus S.

What did you do, reset to factory settings?
Sent from my Nexus 7 using xda app-developers app

bangawasawa said:
What did you do, reset to factory settings?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, but I had some difficulties doing it, couldn't even tell you exactly how I managed to.
I'm really disappointed by this OTA update, it shouldn't be more complicated than flashing an alternative ROM.

[Q] Nexus 7 Update Problem

Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.

GAKB said:
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
Click to expand...
Click to collapse
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?

Solution
ceefercat said:
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Click to expand...
Click to collapse
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!

GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.

It's worth a try!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
That's fair enough, I tried a factory reset first myself to no avail. If you do get your nexus replaced, please let me know if the update works!

ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
I'm considering taking it back because it is not updating as it is supposed to, as it is designed to. A message comes up on the screen that a system update is available. I go through the procedure to download and install said update. The update doesn't install, though the system now says that it is up-to-date.
Bootloader? I don't even know what that is. I don't know that the problem is caused by the bootloader and neither do you. It may be a joke to you but to me its just a pain in the neck.

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
Bootloader issues are a pain in the neck. My bootloader is locked and i cannot erase, flash, format ANYTHING on my Nexus 7... :S

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
obviously the guy doesn't have working knowledge of ADB, rooting/unlocking or any other development terms we use to describe what we are doing to our devices.
The only jokable premise here is some nerd in his mother's basement thumbing his nose at random people because the world he lives in is so narrow it couldn't possibly comprehend the existence of someone honestly asking for advice and then doing the only logical thing he can think of to do as a consumer unfamiliar with a product at a developmental standpoint.
Not everyone wants to root. And not everyone who owns a Nexus has background experience in tinkering with electronics. I've been rooting since my Dinc and I actually want to keep mine as stock as possible. I find more problems come to me when I start messing with the device instead of just leaving it alone.
---------- Post added at 12:58 AM ---------- Previous post was at 12:46 AM ----------
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I appreciate the fix. trying it out now to see if I can get stock 4.2 to update properly
Edit: Worked like a charm thanks bro for the advice

[How-To] Install OTA Update on after Root/Custom Recovery

*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.

jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.

trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.

Thank you for the info! Does sound like an awful lot of work though

jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.

I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.

shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.

jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english

Does sound like an awful lot of work though

greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.

How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium

I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.

trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...

With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.

sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.

Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!

I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.

jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app

deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.

I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?

OTA update fail?

I am running a newly stock, factory restored s4 running 4.2.2. 3 times now I download and attempt to install , but it keeps stopping, rebooting and saying the update failed. What gives?
Any alternate method to update?.

HeDsh0t said:
I am running a newly stock, factory restored s4 running 4.2.2. 3 times now I download and attempt to install , but it keeps stopping, rebooting and saying the update failed. What gives?
Any alternate method to update?.
Click to expand...
Click to collapse
I get the same thing with the wife's S4. I downloaded the update 3 times now in the last month. Each time it shows installed but when verifying the OS and number its the same. So, got on chat with an ATT tech. Seems there is another "hold" on the update, they contacted Samsung tech and the deal is this according to Samsung.
The update comes from Google as an Android update,its up to the carriers to approve the update. Att says it comes from Samsung and its there responsibility to do the update. So where does this go? The usual pass the buck so and so says this. ATT says its Samsung, Samsung says its Google, Google says its ATT. As for the update. Its there but it don't install because ATT stops it with another hold on it.

leesumm said:
I get the same thing with the wife's S4. I downloaded the update 3 times now in the last month. Each time it shows installed but when verifying the OS and number its the same. So, got on chat with an ATT tech. Seems there is another "hold" on the update, they contacted Samsung tech and the deal is this according to Samsung.
The update comes from Google as an Android update,its up to the carriers to approve the update. Att says it comes from Samsung and its there responsibility to do the update. So where does this go? The usual pass the buck so and so says this. ATT says its Samsung, Samsung says its Google, Google says its ATT. As for the update. Its there but it don't install because ATT stops it with another hold on it.
Click to expand...
Click to collapse
Really? Hmm, didn't know they stopped it again. Would I be able to side load it using abd? I heard that works. (I know very little about it, but read the thread here)

HeDsh0t said:
Really? Hmm, didn't know they stopped it again. Would I be able to side load it using abd? I heard that works. (I know very little about it, but read the thread here)
Click to expand...
Click to collapse
You can't load something that isn't there. I have yet to find an OTA update to load but keep looking. Att says it will put it out when it gets ready. Only other option you have is to root and go custom. Mine is rooted with TWRP recovery, but as of yet I don't have a custom rom. It's my wife's phone and she isn't into the techy things as I am so I have let it go and when it happens it happens on the GS4. The HTC one I have is all dolled up with unlocked bootloader, S-Off , TWRP, and converted to a GPE model then running a custom rom.

leesumm said:
You can't load something that isn't there. I have yet to find an OTA update to load but keep looking. Att says it will put it out when it gets ready. Only other option you have is to root and go custom. Mine is rooted with TWRP recovery, but as of yet I don't have a custom rom. It's my wife's phone and she isn't into the techy things as I am so I have let it go and when it happens it happens on the GS4. The HTC one I have is all dolled up with unlocked bootloader, S-Off , TWRP, and converted to a GPE model then running a custom rom.
Click to expand...
Click to collapse
Grab the file from post 694 in this thread http://forum.xda-developers.com/showthread.php?t=2498897&page=70, change it to .zip and then sideload using the instructions from this thread http://forum.xda-developers.com/showthread.php?t=2529759

dwanhala said:
Grab the file from post 694 in this thread http://forum.xda-developers.com/showthread.php?t=2498897&page=70, change it to .zip and then sideload using the instructions from this thread http://forum.xda-developers.com/showthread.php?t=2529759
Click to expand...
Click to collapse
I didn't know there was a download of the OTA anywhere. I have been googleing and looking on the XDA for it for a while and come up empty handed in all searches. Now my question , rather than go thru the ADB stuff would it be possible to just copy the file to a folder such as roms , downloads etc. on the internal SD then use TWRP (if installed) to flash the zip ?

leesumm said:
I didn't know there was a download of the OTA anywhere. I have been googleing and looking on the XDA for it for a while and come up empty handed in all searches. Now my question , rather than go thru the ADB stuff would it be possible to just copy the file to a folder such as roms , downloads etc. on the internal SD then use TWRP (if installed) to flash the zip ?
Click to expand...
Click to collapse
Some people have flashed it from stock recovery from their external sd card, but this does do a full wipe I believe, where the ADB sideload doesn't wipe. Haven't heard of anyone flashing it thru TWRP, you may want to find a version without the bootloaders so that you don't lose the rom flashing ability. I'd imagine that your on MDL?

dwanhala said:
Some people have flashed it from stock recovery from their external sd card, but this does do a full wipe I believe, where the ADB sideload doesn't wipe. Haven't heard of anyone flashing it thru TWRP, you may want to find a version without the bootloaders so that you don't lose the rom flashing ability. I'd imagine that your on MDL?
Click to expand...
Click to collapse
Yeh, I finished reading the posts then found out it wipes the card , sorry my bad . But still can't get it to sideload successfully keeps saying failed.

leesumm said:
Yeh, I finished reading the posts then found out it wipes the card , sorry my bad . But still can't get it to sideload successfully keeps saying failed.
Click to expand...
Click to collapse
You'll either have to Odin back to stock and do the update, or research the error codes and see what you can do from there.

dwanhala said:
You'll either have to Odin back to stock and do the update, or research the error codes and see what you can do from there.
Click to expand...
Click to collapse
Samsung and rooting is not one of my favorite phones. This is my wife's phone but I rooted it a long time ago , just never did any thing with it so I know very little about it. The sideload failed with no error codes, it wont install from anywhere. From what I am reading any way, I just maybe should leave it alone till ATT gets it together if they do and comes down with a good download. Even the tech on chat yesterday said they pulled the download because of issues but failed to know it was still up for a download.

[Q] I need to reset my GS4, but there's a problem.

Hey guys,
So once upon a time, actually about a month ago, I had this great idea to root and flash CM on my AT&T GS4 on 4.3. Well I used Kingo Root and it went fine. But then came the flashing part. I went through all of the steps to get CM, until I saw to the "Downloading" Odin Mode screen and quickly realized the tutorial I used, did not take into the account I had a locked bootloader.. (Thanks AT&T..) Well I finally got out of that and quickly unrooted because I was scared of causing more damage.
Then came along the 4.4 KitKat OTA update which I desperately want. 4.3 is a disaster on my GS4. Anyways, after it downloaded and started to install, it restarted to the Odin Screen!! And so I got out of that.. again.. And now I'm back on 4.3 with no current issues. Except that I figured a factory reset would help me. Once again, it took me to the Odin screen and apparently I'm not going to be factory resseting either..
I really want to go to the exact way I got it. So I can start fresh and get the 4.4 update. I had seen where you could go into the recovery screen and select to wipe all data, but I'm not sure and do NOT want to lose my phone because it works right now.
So any thoughts?

Kwwolves2012 said:
Hey guys,
So once upon a time, actually about a month ago, I had this great idea to root and flash CM on my AT&T GS4 on 4.3. Well I used Kingo Root and it went fine. But then came the flashing part. I went through all of the steps to get CM, until I saw to the "Downloading" Odin Mode screen and quickly realized the tutorial I used, did not take into the account I had a locked bootloader.. (Thanks AT&T..) Well I finally got out of that and quickly unrooted because I was scared of causing more damage.
Then came along the 4.4 KitKat OTA update which I desperately want. 4.3 is a disaster on my GS4. Anyways, after it downloaded and started to install, it restarted to the Odin Screen!! And so I got out of that.. again.. And now I'm back on 4.3 with no current issues. Except that I figured a factory reset would help me. Once again, it took me to the Odin screen and apparently I'm not going to be factory resseting either..
I really want to go to the exact way I got it. So I can start fresh and get the 4.4 update. I had seen where you could go into the recovery screen and select to wipe all data, but I'm not sure and do NOT want to lose my phone because it works right now.
So any thoughts?
Click to expand...
Click to collapse
The best way to prepare your previously rooted phone for the OTA official update is to Odin back to stock your current firmware.
http://forum.xda-developers.com/showthread.php?t=2621279
Good luck.

John The Rhino said:
The best way to prepare your previously rooted phone for the OTA official update is to Odin back to stock your current firmware.
http://forum.xda-developers.com/showthread.php?t=2621279
Good luck.
Click to expand...
Click to collapse
Thanks for the reply, from what I have read, I think this going to help me.

Kwwolves2012 said:
Thanks for the reply, from what I have read, I think this going to help me.
Click to expand...
Click to collapse
I hope it does. Either way post your results. Also if you need more help it's here on XDA. Good luck.

So far so good
John The Rhino said:
I hope it does. Either way post your results. Also if you need more help it's here on XDA. Good luck.
Click to expand...
Click to collapse
This has seemingly completely reset my phone to factory settings which is what I wanted. I have not tried the OTA update yet, but I will try to post the results of that after I see how it goes.

Kwwolves2012 said:
This has seemingly completely reset my phone to factory settings which is what I wanted. I have not tried the OTA update yet, but I will try to post the results of that after I see how it goes.
Click to expand...
Click to collapse
Yup. Odin back to stock is the best way to go. Even if you decide not to take the official Kit Kat OTA update, you now have a fresh factory firmware installed. You can root, install Safestrap recovery & back up your stock rom (which I highly recommend) and flash custom roms, of which there is now some 30 + for our beloved MK2 S4. Either path you chose, you are going to be fine.