Root S-OFF, root, & Fix Everything All-in-One!

[remanifest]

I followed the tutorial and got juopunutbear, got S-OFF, but my radio wasn't what you said I should have...but I was able to install the Harmonia ROM you linked, and rebooted into it, went through all the first boot procedures, everything works fine.

About phone shows:
Hardware version: 0002
Software version: Harmonia 3.17

Software information
Android version: 4.0.3
HTC Sense version: 3.6
Software version: Harmonia 3.17

More
Kernel version 3.0.16-g4211684
Baseband version (I assume is the Radio): 1.06.00.0426
Build number: 1.13.652.2_R2 CL372137 release-keys

What does the Radio do? Should I be concerned with not having the same radio version as you said I should?

Hmmm, you're the second person in a row that hit this same radio version. It's nothing to be too concerned about, but we can (and should) fix it easily.

Go back to your HBOOT (bootloader) and issue the following commands again, same as before:
[high]fastboot erase cache[/high]
[HIGH]fastboot oem rebootRUU[/HIGH]
[high]fastboot flash zip shooter_ota_1.14.652.5_1.50.5050jb.zip[/high]
[high]fastboot reboot-bootloader[/high]

Wait for each command to finish before you move on to the next.

 

[remanifest]

Guide updated to accommodate the above problem. Strange that 2 people have had the same problem in a row... I'll investigate why that's happening and try to fix it if I can find the source of the problem

 

[gothicnerd1033]

Guide updated to accommodate the above problem. Strange that 2 people have had the same problem in a row... I'll investigate why that's happening and try to fix it if I can find the source of the problem

Dont forget, It didnt take for me either, But it didnt change to what they have.. It stayed to what I had previously.

Did you two happen to check what your radios were before doing all this? Did it change to the 1.06 radio or were you using that before s-offing?

 

[remanifest]

Dont forget, It didnt take for me either, But it didnt change to what they have.. It stayed to what I had previously.

Did you two happen to check what your radios were before doing all this? Did it change to the 1.06 radio or were you using that before s-offing?

Well, one of the reasons I made this guide was because all of the information out there was in a bunch of different threads, and it took me a long time to figure out what was "ideal" and what wasn't, so my radios & firmware were all over the place for a while.

But anyway, when I flashed that file I was coming from 1.09.00.0706, and it installed properly for me right away. I'm not sure what's causing this, but for now there's a workaround in place.

Just want this guide to help people out, so I'm really trying to get to the bottom of this :smokingsomb:

Any ideas you have are more than welcome.

 

[gothicnerd1033]

Is the radio update getting flashed first before the Hboot, and somehow the 1.50 Hboot is then downgrading back to a different radio?

I dont think it could be happening.. But its a thought. Maybe try to get it so it flashes the Hboot first then the radio(if it is the other way around of course)?

I dont know D=

 

[remanifest]

I'm testing something out right now, going to try to isolate this problem in about 5 minutes

EDIT: Ok, so the bootloader is flashing before the radio. If we're able to switch that order I'm thinking it'll take on the first try.

 

[gothicnerd1033]

I'm testing something out right now, going to try to isolate this problem in about 5 minutes

EDIT: Ok, so the bootloader is flashing before the radio. If we're able to switch that order I'm thinking it'll take on the first try.

Its worth the try. It might work that way.

 

[remanifest]

So after some experimenting and doing some things I thought may brick my phone, I discovered that:

1) The files are flashed in alphabetical order

2) Changing the file names to flash one before the other will not work. For example, I can't just name the hboot "zhboot.nb0" to make it flash last. If I do that, it won't flash at all. The fastboot RUU program is looking for something named "hboot*.nb0", and doesn't know anything about zhboot, or any other variation.

3) Same applies for the radio.

4) The only thing I could think that *may* work would be to swap the HBOOT and radio names, but I strongly believe that this would cause a brick. If this thing is so heavily dependent upon naming conventions, there must be a reason. If I flash my radio where my HBOOT should be, because the phone thought I knew what I was doing (I'm S-OFF, so...), I'll be in a world of hurt... same for flashing the HBOOT where the radio should be. If it goes wrong, there's no fix for that...

5) In essence, I'm scared to try anything further, and I don't think flashing it a second time if it doesn't take on the first flash is so bad.

 

[gothicnerd1033]

Yeah I DEFINITELY wouldnt try switching the names. People will have to live with doing the 2 steps over if it doesnt take the first time. Oh well.

 

[remanifest]

One option would be to split the HBOOT into its own zip file, but then you're still doing 2 flashes.

 

[gothicnerd1033]

One option would be to split the HBOOT into its own zip file, but then you're still doing 2 flashes.

It might make people get a little more nervous with an extra step or two(Even though its the same procedure). I would just leave it how it is for now, Unless we find a fix for it. Seeing a "Repeat these steps if necessary" is a little more comforting instead of seeing a huge list of many steps. LOL

But thats just me.
Others may feel differently.

 

[ramjet73]

One option would be to split the HBOOT into its own zip file, but then you're still doing 2 flashes.

Well, the original "fix everything" thread has four separate PG86IMG.zip files to flash and plenty of Evo V users have done that.

If the OTA's are downloaded and installed right after getting S-OFF while the stock ROM and recovery are still in place the only file that really needs to be flashed is a custom recovery since downgrading the hboot and flashing a superuser zip aren't necessary if the user plans to flash a custom Sense ROM.

I know there's a concern that some users may not be able to take the OTA's so maybe there could be a file with just the updated firmware for them to flash.

ramjet73

 

[Poweredge99]

Maybe I got lucky, I followed the guide last Saturday and have the correct radio version . Although I did just double check to make sure, would if been embarrassing if I didn't notice that. Fwiw, I was on Windows 7 (64).

 

[remanifest]

Maybe I got lucky, I followed the guide last Saturday and have the correct radio version . Although I did just double check to make sure, would if been embarrassing if I didn't notice that. Fwiw, I was on Windows 7 (64).

Yeah, it seems to be hit or miss on the radio going through with the HBOOT, and I'm not really sure why. For now, I'll leave it as is & hopefully that will stop some confusion.

It seems like everybody who has done a 2nd flash has been successful -- at least, nobody's reported otherwise.

 

[Deleted User]

So will I have a problem with rooting if I have a 64 bit windows 7 system?

 

[ron scubadiver]

If the OTA's are downloaded and installed right after getting S-OFF while the stock ROM and recovery are still in place the only file that really needs to be flashed is a custom recovery since downgrading the hboot and flashing a superuser zip aren't necessary if the user plans to flash a custom Sense ROM.


ramjet73

I think this makes the more sense than having everyone flash hboot 1.50.5050 and the OTA firmware. Not everyone is going straight to JB. The procedure also should have the option of rooting the stock ROM instead of going custom.

 

[Deleted User]

Can i still root my phone even though i have version2.95.652.5 710RD which was the new system update? and can I still root my phone with windows 7 64 bit?

 

[OverByter]

Yes, the only thing that the update possibly changed as far as rooting is that I don't think that we have a clear answer on getting s-offed with the new hboot, unlocking, rooting and installing a custom recovery won't be a problem except for being 64 bit, numerous people haven't had any issues and a few others have.
OB

 

[Brian706]

We did have one user confirm s-off after the new OTA using the Evo V windows version of the Controlbear software.

 

[Deleted User]

Ok wish me luck and I've had my phone for a month or two ,but have not rooted it or anything. SO its stock right?

 

[Brian706]

Ok wish me luck and I've had my phone for a month or two ,but have not rooted it or anything. SO its stock right?

Yes it's stock. You can do the bootloader unlock and apply root but before you do s-off, let's make sure you have the right version that was confirmed.

 

[ramjet73]

Yes it's stock. You can do the bootloader unlock and apply root but before you do s-off, let's make sure you have the right version that was confirmed.

Or maybe he should try the Sprint ICS version first. I don't think anyone has tried that yet and he would end up with hboot 1.58.5858 which would be more appropriate for the 2.95 build.

ramjet73

 

[Deleted User]

So what do i do? I want to install the mobster HD Rom

 

[ramjet73]

So what do i do? I want to install the mobster HD Rom

I think that ROM will work with the stock hboot so rooting should be enough. I would try that first using one of the guides here and wait to get S-OFF until you want to do something that requires it.

ramjet73

 

[Deleted User]

The mobster hd says it requires s-off what is a good rom that you recommend?