I am trying to put my phone back to stock, I have unrooted and relocked my bootlaoder. Now when I try to do a Sprint OTA my phone reboots, goes into boot loader and doesn't update anything. Everytime I try to run RUU I get an error. Any suggestions would help, thanks.
Sent from my EVO using xda premium
To accept the ota you need a stock recovery and stock rom.
om4 said:
To accept the ota you need a stock recovery and stock rom.
Click to expand...
Click to collapse
I am on a stock rom, how do I get stock recovery?
Sent from my EVO using xda premium
Unlock and flash the stock recovery, if you removed any bloatware you will need to flash a bare stock rom. Check the development section
Related
I'm on hboot 1.50 and I want to update to the latest software. After locking my bootloader, should I run the RUU.exe of the previous updates then do an OTA of the latest 2.17 or should I just run the RUU of the latest? Does either way work? I never did this before so I want to make sure I do it right.
Sent from my PG86100 using XDA App
All depends on if you are rooted or not, which you didn't mention.
If you are not rooted, you don't need to do all that, just go to settings-system updates and let it update that way.
If you are rooted, again no need to do all that, just flash a stock rooted rom, or custom rom of your choice.
I am rooted, hence I mentioned relocking the bootloader. My goal is to unroot. Should I run the latest RUU or the previous version then do the OTAyfor the latest 2.17 I believe it is.
Sent from my PG86100 using XDA App
JayDaKissEP said:
I am rooted, hence I mentioned relocking the bootloader. My goal is to unroot. Should I run the latest RUU or the previous version then do the OTAyfor the latest 2.17 I believe it is.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
You don't need to relock to recieve the update, I have hboot 1.5 unlocked too and all I needed to do was to have a fully stock (no bloatware removed) ROM and stock recovery, doeant matter if your currently rooted or not.
After the update you will loose root so you just need to flash a custom recovery again via fastboot and just flash root again.
This is all i did and worked like a charm. Updates don't check on the state of the bootloader, it just checks on the integrity of it for corruption or other showdown software running on it.
Sent from my PG86100 using Tapatalk
What do you mean all you needed was a stock rom and recovery? I thought installing the RUU.exe automatically puts the stock recovery back? I'm on warmtwopointthree with cwm recovery. What are you stating I need to do exactly?
Sent from my PG86100 using XDA App
JayDaKissEP said:
What do you mean all you needed was a stock rom and recovery? I thought installing the RUU.exe automatically puts the stock recovery back? I'm on warmtwopointthree with cwm recovery. What are you stating I need to do exactly?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
if you are still unlocked flash stock recovery and rom then take the OTA.
Or if you are relocked then run RUU.
Thanks
Sent from my PG86100 using XDA App
I am currently on an S-ON unlocked and rooted rezound with the stock gb update that happened in January. I have cwm recovery and am looking to get stock so I can recieve the ota but I don't want to lose my contacts, apps, etc. Thanks for helping in advance!
EDIT: Also will be getting s-off after the ota.
Sent from my ADR6425LVW using xda app-developers app
sk8bert12 said:
I am currently on an S-ON unlocked and rooted rezound with the stock gb update that happened in January. I have cwm recovery and am looking to get stock so I can recieve the ota but I don't want to lose my contacts, apps, etc. Thanks for helping in advance!
EDIT: Also will be getting s-off after the ota.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You can run the GB RUU and that will install the stock recovery. Or you can pull the recovery.IMG from the RUU and fastboot flash it.
zac41189 said:
You can run the GB RUU and that will install the stock recovery. Or you can pull the recovery.IMG from the RUU and fastboot flash it.
Click to expand...
Click to collapse
For anyone not wanting to download the whole RUU, here's just the stock signed recovery image. Let me know if it works for you, I have yet to flash it because I'm at work.
http://www.sendspace.com/file/081hbg
I ran the RUU for 1.22 and I am back to complete stock but the stock recovery did not install. I tried to flash a stock recovery images from one of the root files I downloaded and it said successful but still no recovery. I'm trying to update to the latest update to 2.13 but will fail. How can I get this to update?
Are you S-On or S-Off? If s-off you could try to ruu to 1.13 and see if that takes care of it.
If s-on have you tried installing another recovery like twrp and then try installing the stock recovery? If thay works ypu can ruu again on 1.22 and see if that makes the stock recovery stick.
Sent from my T-Mobile Samsung Galaxy S III using xda premium
brandonmaze said:
Are you S-On or S-Off? If s-off you could try to ruu to 1.13 and see if that takes care of it.
If s-on have you tried installing another recovery like twrp and then try installing the stock recovery? If thay works ypu can ruu again on 1.22 and see if that makes the stock recovery stick.
Sent from my T-Mobile Samsung Galaxy S III using xda premium
Click to expand...
Click to collapse
wut? that doesn't seem like it makes sense.
Before running ruu you are supposed to re lock the bootloader, after you re lock the bootloader you should have stock everything, in order to flash anything through fastboot you need to unlock the bootloader so that you have access to those partitions again
om4 said:
Before running ruu you are supposed to re lock the bootloader, after you re lock the bootloader you should have stock everything, in order to flash anything through fastboot you need to unlock the bootloader so that you have access to those partitions again
Click to expand...
Click to collapse
So what I took from this was to unlock the bootloader again, and try to flash the recovery again. So I tried that and still no recovery.
zjaksn said:
So what I took from this was to unlock the bootloader again, and try to flash the recovery again. So I tried that and still no recovery.
Click to expand...
Click to collapse
No...relock, then RUU^^^^^
Sent from my EVO using xda premium
Folks, I need some help here. I am using my DNA with tmobile now and have never activated with Verizon. How do I get the ota update? I am rooted with a custom Rom. Many thanks!
Sent from my HTC6435LVW using xda app-developers app
you can do a manual install of the ota by downloading it and installing via recovery but dont quote me on that. this is my first htc device so i dnt know too much about it myself
coshaw said:
Folks, I need some help here. I am using my DNA with tmobile now and have never activated with Verizon. How do I get the ota update? I am rooted with a custom Rom. Many thanks!
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Go to Original Development. You should find the RUU thread i believe from micromod777. Dunno your previous devices, but RUU is akin to SBF for motorola and ODIN for samsung. It is how you get released/leaked factory images onto your phone using your computer and fastboot. You can also flash the stock rom in recovery but if you are not s-off you will not be able to get the valuable(IMHO) parts which are the bootloader/radio etc . I would say your best bet to get the good stuff Is to go to original development, download the RUU to your computer, re lock your phone using fastboot oem lock in fastboot mode and a terminal on your cpu. Once you update you will have lost root. So re-unlock using superCID, re root after reinstalling your custom recovery. Now you will be updated, unlocked, and rooted. BACKUP your device.. IT WILL BE WIPED
Can some please list the details of installing the OTA-Global-Stock-4.05.605.14 710RD-Rooted.zip on a S-ON phone? Or any other way to avoid the OTA update from automatically trying to install and eventually aborting? I'm VERY new to the rooting terminology so please be specific. Thanks!
So nobody can help me with this?
Do I have to uproot and relock the bootloader to get the OTA, or is there another way to flash the update?
to get OTA you have to be relocked. did you check this thread yet?
http://forum.xda-developers.com/showthread.php?t=2250494
I've read through several of the posts. They seem more relevant to S-OFF, I'm still S-ON. I've re-locked the bootloader but the OTA still stops at the bootloader screen when the phone reboots. Do I have to "flash" the OTA manually from there using a computer (i.e. fastboot flash recovery ..\OTA.zip)?
You also need to be on stock Rom with stock recovery for the ota to work
Sent from my ADR6425LVW using xda app-developers app
That's what I figured, so just go back to stock. I think I can remember to do this (I had to to it a couple of months ago when I got a warranty replacement), but if you have any advice on this it would be great. Thanks!
Are you on the global leak now? If not just run the latest ruu for ics 605.12 which you can find at shipped-roms under vigor.
Sent from my ADR6425LVW using xda app-developers app
Have 3.14.605.13.710RD installed.
You could run the 605.12 ruu as it has the same hboot or extract the stock recovery from that and install it, as long as your on a non modified stock Rom you should be able to get the update.
Sent from my ADR6425LVW using xda app-developers app
Thanks! That worked... BUT... now it looks like I have a bigger problem. I was able to get the updates and re-root but when I was restoring my backup I could not boot up. Because I have the update HBOOT I can't go back and do the stock RUU, I am able to boot up into TWRP recovery but now I am TOTALLY lost. When I shut down from recovery it says I don't have an OS installed, idea ideas?
I got it! Kept reading various posts and re-installed AmonRA instead of TWRP and was able to install the OTA-Global-Stock-4.05.605.14 710RD-Rooted ROM, already had flashed the boot.img. Wow! How does anyone figure out how to do this stuff in the first place?!