Also, should the phone still be in bootloader when I run the RUU.exe, or should it be just connected while in the normal mode?
Upvote
0
If you're talking about the hboot, it is not. It is 1.04.
Also, should the phone still be in bootloader when I run the RUU.exe, or should it be just connected while in the normal mode?
I think that's where your error might be coming from. You should be on a stock bootloader. If returning completely to stock, you should just use the RUU. It will return everything to stock.
I've ran it from both successfully before. One time I had a problem running it while booted up and it worked from the bootloader so, I guess it depends. Seems like most times it's recommended to run from the bootloader though.
That's the difference between radio S-OFF and hboot S-OFF which are explained further in this post. Once you are radio S-OFF it is not necessary to unlock the bootloader to enable the restricted fastboot commands since you can use a custom hboot instead.When I tried to flash a recovery it would not take. Then I unlocked the bootloader again and the recovery flashed. In the bootloader it says "Unlocked" and S-Off and it appears to behave like an S-Off phone. The hot reboot problem is gone.
Is this result normal for doing an RUU on a phone that is S-Off and re-rooting it? This probably does not come up much because phones are unrooted to be sold or returned.
Yes, you can flash a custom hboot without relocking but that's probably not necessary at this point since you already unlocked.Ramjet, thank you for the information. My question now is absent the need to set the phone to stock at this time and having no plans to use a rom that that requires other than hboot 1.57, do I need to flash one of the custom bootloaders and relock the phone? Can I flash a custom bootloader and not relock?
Yes.Instead of unlocking the bootloader as I did, could I have simply flashed a custom bootloader using a PG86IMG.ZIP in the root of my sdcard and then used fastboot to flash a recovery?
You don't need to lock the bootloader to flash an RUU after you are S-OFF. I haven't unlocked/locked/relocked since gaining S-OFF. The only thing that might be needed at this point is to flash the zip that locks your bootloader if you ever need to return to 100% stock.I kind of think the answers are that I don't have to look the bootloader unless I need to do another ruu. If I need another bootloader with a lower version, I can flash it and not lock the bootloader. As for the second paragraph, I suspect I could have done that and eliminated the need to generate another unlock code, as I had deleted the original. I suspect locking of the bootloader is a side effect of the s-off procedure which is why a flashing a custom bootloader is part of the package/s-off procedure.
RUU reverts everything to factory stock
Thanks! This may be seen as a stupid question, but where can I check whether my bootloader is locked, unlocked or relocked? I went to the bootloader, but I don't see any of these listed anywhere.
It usually says it on the bootloader screen. I am guessing you are on a custom hboot which hides that information.
My guess would be that you are locked. If you did s-off and had it flash a custom hboot, then you would still be LOCKED as the wire trick returns you to LOCKED. Unless you physically unlocked the bootloader again, it should still be locked.
Also, the RUU would return you to a stock hboot which then would display locked or unlocked at the top.
Thanks! I mainly just need to make sure I'm on the stock bootloader (I don't even know how to get a different bootloader...the hboot isn't the bootloader is it?) so that I don't brick my phone in trying to flash RUU. I flashed back my hboot to 1.57 so hopefully that will show whether its locked or not.
Can I flash the ruu with goo manager?
omg no matter WHAT I try, I am always getting error 140. I checked the ruu log in my C drive and I get this bit:
INFOchecking main version...
FAILED (remote: 43 main version check fail)
I tried the zip image for flashing but that won't work either. I don't know what I could have done to it to make it not work anymore D:
Oh, if this helps, I got an error sign at some point when I tried to relock the bootloader in the command prompt but it did say relocked nonetheless...
I never thought I would ever have to run the RUU, so I've basically glossed over anything related to RUU. But now, I think I want to learn RUU-ness. The one thing that caught my attention was that there is an extra step that needs to be taken before one can RUU, and I can't remember what the hell it is. I've seen Brian link people over to XDA for more info. It's also probably in a guide somewhere.
Given the recent OTA, there's been a lot of chatter about RUU lately, and to me, all the threads are starting to run together.
My phone is effectively at JoeBlow status with 1.50 JBEAR and S-OFF plus Unlocked. Is the Jefofld guide a good place to start, or is it a dated guide? Is there something mroe current I should be looking at?
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.