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

Root Somebody please help me!

Yea, unless you need to flash the RUU for some other reason you should be able to go for S-OFF using Harmonia with the wire trick.

Good luck!

ramjet73

Going for s-off using harmonia is what got me in this mess, either that or the fact that I have windows 7 64-bit. I might still flash the ruu and try the wire trick from there. At least now I have a little more know-how. Seriously, thanks a lot to all of you guys for helping me out. You really saved my ass on this one.
 
recovery should be easily enuff accessed if he re- unlocks. However the hboot in the ota will need to be the same as the one in the ruu you're trying to flash.

If the ota hboot is newer,the ruu will pass the main version check,but still fail the hboot check.

The newer phones are unfortunately too smart to be tricked into downgrading hboot. :(

Just fyi, both the original release and the update contain hboot 1.57. I think the update just updated the radio and possibly something else.
 
Going for s-off using harmonia is what got me in this mess, either that or the fact that I have windows 7 64-bit. I might still flash the ruu and try the wire trick from there. At least now I have a little more know-how. Seriously, thanks a lot to all of you guys for helping me out. You really saved my ass on this one.

I would still run the RUU if you wan to try s-off again. I know it works for people on Harmony, but you had issues, so I would carefully follow all of the instructions to the letter.
 
I would still run the RUU if you wan to try s-off again. I know it works for people on Harmony, but you had issues, so I would carefully follow all of the instructions to the letter.

OK so I thought I was in the clear, but Im not. I flashed the file in recovery to make my image 1.000.000.0, so that I could run the ruu. Now Im getting:

ERROR [155]: Unknown error

It gives me the option to start te recovery process, so I did that, it told me the recovery was successful, I run the ruu again, and get the same error code 155. Im so freakin close. What do I need to flash to get this thing going, now that I can access recdovery, it should be a piece of cake, right? The ruu recognizes my image as 1.000.000.0, so that part worked, im lost again!
 
The misctool utility used by that zip file (attached to this post) was developed by drellisdee, one of the developers for the Amon-RA recovery for the OG Evo, originally for the HTC Rezound which is a newer phone than the Evo 3D/V. I've used it to reset the mainver on my 3D, but I'm S-OFF and have no way to test it on an Evo V that is S-ON, but according to the developer it should reset the mainver as long as the phone is rooted and that should allow flashing an older RUU/hboot with S-ON. The Rezound got the wire trick very late so the users were forced to deal with S-ON for quite a while.

In this case, if the phone is unlocked again it should be possible to flash a custom recovery via fastboot and then run the zip file to reset mainver. I can't guarantee that will work but it's the only method I've heard about to try flashing an RUU with a lower mainver on an S-ON phone.

ramjet73

I am quite aware where it came from,my daily driver Phone is a rezound ;)

Yes it will effectively change the main version ,but it will not allow you to downgrade hboot,so ruus containing older hboots are off limits. Its main use is to set the main version so that hboot flashing of PxxxIMG files on s on phones is less fustrating :)
 
Has anybody had any experience using controlbear with win 7 x64. Thats what I have. It says on unlimited.io website that you can't s-off with a pc running 64 bit. Is there a way around it if thats the case?
 
Has anybody had any experience using controlbear with win 7 x64. Thats what I have. It says on unlimited.io website that you can't s-off with a pc running 64 bit. Is there a way around it if thats the case?


They say the 64 bit drivers are unreliable. While some have used their tools on 64 bit and had great success,they dont reccomemd them for a reason. IMO you would be better off to borrow a 32 bit machine.
 
I am quite aware where it came from,my daily driver Phone is a rezound ;)

Yes it will effectively change the main version ,but it will not allow you to downgrade hboot,so ruus containing older hboots are off limits. Its main use is to set the main version so that hboot flashing of PxxxIMG files on s on phones is less fustrating :)
Well, as brian706 pointed out, the hboot was not changed with the Evo V OTA so the good news is that down leveling the mainver will let Evo V users that are S-ON and have flashed the OTA install the only RUU.exe currently available. :)

ramjet73
 
Has anybody had any experience using controlbear with win 7 x64. Thats what I have. It says on unlimited.io website that you can't s-off with a pc running 64 bit. Is there a way around it if thats the case?
I did the wire trick on two Evo 3D's using my 64 bit Windows 7 Ultimate PC before they put that restriction on their website. The drivers I used aren't specifically 64 bit (at the time I was using the ones installed by HTC Sync) and if you start controlbear.exe on a 64 bit Windows system you will see that it has a "*32" next to it in the process list of Windows task manager, meaning it is running in 32 bit mode. Nonetheless, unlimited.io has taken the position that it's not supported so you can't go to them for help if it doesn't work.

ramjet73
 
I did the wire trick on two Evo 3D's using my 64 bit Windows 7 Ultimate PC before they put that restriction on their website. The drivers I used aren't specifically 64 bit (at the time I was using the ones installed by HTC Sync) and if you start controlbear.exe on a 64 bit Windows system you will see that it has a "*32" next to it in the process list of Windows task manager, meaning it is running in 32 bit mode. Nonetheless, unlimited.io has taken the position that it's not supported so you can't go to them for help if it doesn't work.

ramjet73

I think I'm going to be hard headed and try it again, because I dont know anybody with a 32 bit. Everybody seems to have 64 bit. And besides, I know how to fix it now, thanks to you guys!
 
Sounds like his best solution would be burn a 32bit Mint or Ubuntu disk and run it from there.

Unetbootin and a flash drive would be optimal.

Then go into bios with, the flash drive in the usb port, and set it as the first boot drive.

Click try after it loads.
 
So, I decided to stay away from the s-off for now. Just downloaded 4EXT recovery, and am using MidnightRom. So far, I like it, much faster and smoother than stock, and my signal bars seem to be more stable as well. Maybe I don't even need to s-off, thanks to 4ext!
 
So, I decided to stay away from the s-off for now. Just downloaded 4EXT recovery, and am using MidnightRom. So far, I like it, much faster and smoother than stock, and my signal bars seem to be more stable as well. Maybe I don't even need to s-off, thanks to 4ext!

CM10 says, very clearly, you need to s-off :D
 
Back
Top Bottom