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

Root [CDMA] ATTN: Unlockable EVO3d

Just to save some effort, here is the RUU Scotty wants you to run.

MD5:
Code: 
630eaae52a612a7415362aa59ebc2e19

It's always worth trying everything... You just never know ;)


scotty85 said:
this just all of a sudden popped into my head,from reading the above a while ago:

i assume you ran the 2.17 ruu in attempt to downgrade(wich is wat didnt work).

have you run the ruu for 2.89.651.2 710,your current firmware? if your device is "refurbished"(but not so much),its a long shot chance that a previous user of that device may have modified something trying to downgrade,or do something similar.

in this scenario,running the 2.89 ruu should restore any modified partitions,and let the unlock work. i think we are on track with some sort of hardware issue/mismatch,but a last ditch effort to avoid yelling at sprint or htc may be to run the current ruu. a factory reset in hboot immediately afterward prolly isnt neccessary,but prolly wouldnt hurt :)
Click to expand...
 
SUCCESS!!! Simply awesome... whats funny, i thought of doing this after the 2.17 ruu failed, but i didnt see the significance of it all... I had root within 15 minutes of reading this post, lol... then i was having trouble with wifi tether, got that working... So here I am!! Thanks alot for all the support guys! I will for sure be recommending everyone I know to this forum. This was the VERY first forum i've ever joined for android advice and help, I extremely glad I did.
 
UnlockableEVO said:
SUCCESS!!! Simply awesome... whats funny, i thought of doing this after the 2.17 ruu failed, but i didnt see the significance of it all... I had root within 15 minutes of reading this post, lol... then i was having trouble with wifi tether, got that working... So here I am!! Thanks alot for all the support guys! I will for sure be recommending everyone I know to this forum. This was the VERY first forum i've ever joined for android advice and help, I extremely glad I did.
Click to expand...

Great News!! :beer: :D So glad to hear this! Thanks for the kind words, enjoy your rooted 3vo!
 
UnlockableEVO said:
SUCCESS!!! Simply awesome... whats funny, i thought of doing this after the 2.17 ruu failed, but i didnt see the significance of it all... I had root within 15 minutes of reading this post, lol... then i was having trouble with wifi tether, got that working... So here I am!! Thanks alot for all the support guys! I will for sure be recommending everyone I know to this forum. This was the VERY first forum i've ever joined for android advice and help, I extremely glad I did.
Click to expand...

awsome! i really didnt think it would work,im glad to have been wrong in this situation :D

i guess from this we can assume that sprint does just about as good a job as vzw at actually "refurbishing" their refurbs,lol. dont know what a previous user may have done,but sounds like something that changed things at least a lil bit!

note to self: when users have trouble with htcdev and everything looks correct,run ruu as one of the first fixes :smokingsomb:
 
here is a question for you experts....

the old s-off rev method was a permanent s-off approach.
j-bear from what i hear will go away when you run a RUU or get an OTA update.

is the above true. if so is it possible to use j-bear then downgrade hboot to trick the other tool for permanent s-off.
 
You want to be able to revert using the RUU, and never take an ota if you're rooted. If you don't do either of these things then you have permanent root.
 
lordmage said:
here is a question for you experts....

the old s-off rev method was a permanent s-off approach.
j-bear from what i hear will go away when you run a RUU or get an OTA update.

is the above true. if so is it possible to use j-bear then downgrade hboot to trick the other tool for permanent s-off.
Click to expand...

you have heard incorrectly. juopunut bear is providing a patched hboot to allow extra fastboot commands,like revolutionary. running an ruu will overwrite the patched hboot,again like revolutionary. however,s-off does not go away. rest assured that jp bear is giving you the same radio s-off as revolutionary,there is no need to do anything.

you are free to run any ruu you wish,even take OTAs as long as you have the stock recovery in place. :)

if you wish to add the jpbear hboot back after running an ruu,unlimited.io has them available to download,and they are easy to install as a PG86IMG in hboot.

your radio s-off is permanent,and will stay until you issue a fastboot command to deliberately change it.
 
scotty85 said:
you have heard incorrectly. juopunut bear is providing a patched hboot to allow extra fastboot commands,like revolutionary. running an ruu will overwrite the patched hboot,again like revolutionary. however,s-off does not go away. rest assured that jp bear is giving you the same radio s-off as revolutionary,there is no need to do anything.

you are free to run any ruu you wish,even take OTAs as long as you have the stock recovery in place. :)

if you wish to add the jpbear hboot back after running an ruu,unlimited.io has them available to download,and they are easy to install as a PG86IMG in hboot.

your radio s-off is permanent,and will stay until you issue a fastboot command to deliberately change it.
Click to expand...
much clearer thank you... for reference where would i download the stock recovery if i ever want to take an ota...
i currently run a cm 10 private port anthrax edition and hboot 1/04 eng
 
lordmage said:
much clearer thank you... for reference where would i download the stock recovery if i ever want to take an ota...
i currently run a cm 10 private port anthrax edition and hboot 1/04 eng
Click to expand...

best place to get it would be from the ruu of the build number you were running at the time.

keep in mind,that an OTA will not happen,if the firmware isnt correct,and the build number one of the release versions.you also have to be fairly stock(i.e. not deletedsystem apps) so if youve mixed and matched hboots and radios and/or are on a custom rom,or even on a heavilly modded stock rom,you wont get an OTA no matter what recovery you run.


for example:
if you were on stock sprint ICS 2.89.651.2,and you installed a custom recovery,added root,and froze a couple system apps(but didnt delete),and an OTA notification popped up,you would need to:
-download 2.89.651.2 ruu
-extract it,and install the included stock recovery image
-unfreeze all your frozen system apps and files
*you do not need to remove superuser or its matching binary to allow the OTA,contrary to some popular belief. meeting the above criteria is all you need.

at this point,you could accept an OTA. the superuser app will remain,but the OTA will overwrite the binary,unrooting you in the process. as long as youre s-off,this isnt a big deal,you just:
-reinstall custom recovery
-flash superuser files
-refreeze all your bloat

and then you would have successfully OTAed to a new build/firmware without losing any personal data :)

example #2:
you are runing a custom rom and custom recovery(your situation) and want to upgrade to a firmware/build there is not RUU for.

you will need to:
-run an ruu for the most recent release build(currently 2.89.651.2)

this will correct all partitions,including all correct firmware,stock recovery,and all required system apps and files in place. within short order you should OTA.
at that point,since youre s off you can
-reinstall custom recovery
-flash superuser files
-freeze bloat,make a backup or whatever.
*alternately,you could simply flash a custom rom rather than flashing superuser

hope that clears it up :)
 
You must log in or register to reply here.
Back
Top Bottom