• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root RUU Issues

rodgman15

Well-Known Member
Ok so i'm trying to run the RUU so that I can apply the OTA from March, but i'm hitting a few snags (right away) and i'm not afraid to admit that I really don't know what i'm doing. First off I can't seem to lock the bootloader "fastboot oem lock", but at the same time my bootloader doesn't say "unlocked" along the top, here's what it displays:

Shooter XC Eng S-OFF RL
HBOOT-1.04.2000 (PG8610000)
Radio-1.09.00.0706
eMMC-boot
Apr 16 2011, 19:34:31

When issuing the "fastboot oem lock" command it comes back saying:
INFO[ERR] Command Error!!! OKAY

I don't know how I got so lost, or where along the lines I got lost. If anyone can give me a hint and maybe point me in the right direction it'd be much appreciated.
 
Shooter XC Eng S-OFF RL
HBOOT-1.04.2000 (PG8610000)
Radio-1.09.00.0706
eMMC-boot
Apr 16 2011, 19:34:31
Since you are S-OFF you don't need to lock the bootloader to flash the RUU. It's probably locked already which is what's causing the error but you can't see that status with the ENG hboot installed.

ramjet73
 
Ok so i'm trying to run the RUU so that I can apply the OTA from March, but i'm hitting a few snags (right away) and i'm not afraid to admit that I really don't know what i'm doing. First off I can't seem to lock the bootloader "fastboot oem lock", but at the same time my bootloader doesn't say "unlocked" along the top, here's what it displays:

Shooter XC Eng S-OFF RL
HBOOT-1.04.2000 (PG8610000)
Radio-1.09.00.0706
eMMC-boot
Apr 16 2011, 19:34:31

When issuing the "fastboot oem lock" command it comes back saying:
INFO[ERR] Command Error!!! OKAY

I don't know how I got so lost, or where along the lines I got lost. If anyone can give me a hint and maybe point me in the right direction it'd be much appreciated.

First off- What exactly are you trying to do? If you just want to get to stock software (ie. no S-ON), just run the RUU normally without trying to unlock. You'll still be S-OFF and stock.
 
First off- What exactly are you trying to do? If you just want to get to stock software (ie. no S-ON), just run the RUU normally without trying to unlock. You'll still be S-OFF and stock.
Actually, he is trying to lock but as you and I both pointed out :) that's unnecessary to flash the RUU since he is S-OFF, and I'm pretty sure his bootloader is locked already.

ramjet73
 
Actually, he is trying to lock but as you and I both pointed out :) that's unnecessary to flash the RUU since he is S-OFF, and I'm pretty sure his bootloader is locked already.

ramjet73

Ya that's pretty much what I was trying to do. Ultimately i'm trying to get the latest firmware, the simplest way possible. Which from my understanding is run the RUU, download the OTA, then i'm not sure if I need to reflash recovery or what's left from that point but I think i'm comfortable enough with that stuff. With all the guides and great help around here it's next to impossible to get too far off the right path!
 
Ya that's pretty much what I was trying to do. Ultimately i'm trying to get the latest firmware, the simplest way possible. Which from my understanding is run the RUU, download the OTA, then i'm not sure if I need to reflash recovery or what's left from that point but I think i'm comfortable enough with that stuff. With all the guides and great help around here it's next to impossible to get too far off the right path!

Sorry ramjet, I got ninja'd. xD But yeah basic process- run RUU (no locking/S-ON needed), update, then reflash recovery/downgrade HBOOT (it flashes back to stock recovery and HBOOT 1.58)
 
Sorry ramjet, I got ninja'd. xD But yeah basic process- run RUU (no locking/S-ON needed), update, then reflash recovery/downgrade HBOOT (it flashes back to stock recovery and HBOOT 1.58)
Just make sure you run both OTAs (November and March) before flashing a custom recovery. You might as well do a nandroid of the updated stock ROM for future reference right after flashing the custom recovery too since you are going to all that trouble to get there. ;)

ramjet73
 
if you want to confirm that its Re-locked before flashing a Ruu just flash the 1.57 hboot then do the "fastboot oem lock" .......... after clearing caches you should be able to run the ruu
 
Just make sure you run both RUU's (November and March) before flashing a custom recovery. You might as well do a nandroid of the updated stock ROM for future reference right after flashing the custom recovery too since you are going to all that trouble to get there. ;)

ramjet73

I'll assume you meant OTA instead of RUU in your first sentence above.
 
if you want to confirm that its Re-locked before flashing a Ruu just flash the 1.57 hboot then do the "fastboot oem lock" .......... after clearing caches you should be able to run the ruu
That will work to check the bootloader status and there is also a query zip file in this post that can be "flashed" in recovery to report the status as well.

He doesn't need to lock the bootloader to flash the RUU since he is S-OFF and after he does the stock hboot will be installed so he could check it then.

ramjet73
 
So you're saying there's no need for the RUU?

If all you want is the new radio, that can be flashed to a phone that is S-Off by itself. Ramjet posted the zip somewhere. If you want all the improvements to the stock ROM and want to run a rooted stock ROM, then do the RUU. I wrote a short post on that called "Regaining Your Sanity", but there does not seem to be much interest in it, LOL.
 
If all you want is the new radio, that can be flashed to a phone that is S-Off by itself. Ramjet posted the zip somewhere. If you want all the improvements to the stock ROM and want to run a rooted stock ROM, then do the RUU. I wrote a short post on that called "Regaining Your Sanity", but there does not seem to be much interest in it, LOL.

Ok now i'm thoroughly confused. I understand I could just flash the newest radio, but is it possible to get the March OTA, then switch hboots and run different roms? Or does switching roms negate the effects of the most recent OTA? My main goal is to get everything "up to date" so to speak with my phone, most recent everything (except the 1.58 hboot).
 
Well I swapped hboots, ran the RUU, in the process of taking the OTAs. Should be able to figure everything else out from here, but I just want to say thank you to everyone that chimed in and gave me a hand, or anyone who read the post and may have had an idea.
 
Back
Top Bottom