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

Root [CDMA] Complete Newbie's Guide to rooting and flashing Evo 3D ROMs/Kernels using fastboot

xevious said:
I've used ROM Manager just fine with S-ON. I've rooted, loaded custom ROM images, and even replaced ROM Manager with TWRP without having S-OFF.

I do understand that flashing some images may require S-OFF, but so far I haven't run into any.

Incidentally, there's tons of info out there about how to switch off security... but how about turning it back on? It's my understanding that having it ON protects your system software configuration against catastrophic changes. After doing whatever is necessary with it OFF, I'd feel more comfortable switching it back on. Is that possible?
Click to expand...

Using fastboot commands you can use the command

Code: 
fastboot oem writesecureflag 3

That should make you s-on.

If you aren't familiar with fastboot you can use the guide in the first post to obtain all the drivers and software needed and how to get into fastboot.
 
Christine484 said:
Is this for cdma phones or gsm phones?
zamz2.jpg
09dh.jpg
09ht.jpg
09ax.jpg
09jh.jpg
09bh.jpg
Click to expand...

I can't see your images so I am not sure what you are asking about. If you mean the guide there are two versions. One for gsm one for cdma. What do you have?
 
Brian706 said:
Using fastboot commands you can use the command

Code: 
fastboot oem writesecureflag 3

That should make you s-on.

If you aren't familiar with fastboot you can use the guide in the first post to obtain all the drivers and software needed and how to get into fastboot.
Click to expand...
Thank you very much, Brian. This is really good to know. :thumb:

Incidentally, I discovered that you can execute commands in the Terminal app on the phone, which bypasses having to set up a client with the software. While the terminal window is terrible for typing/editing, you can write all of your commands in a text editor, then copy/paste into the terminal window. Works like a charm.
 
xevious said:
Thank you very much, Brian. This is really good to know. :thumb:

Incidentally, I discovered that you can execute commands in the Terminal app on the phone, which bypasses having to set up a client with the software. While the terminal window is terrible for typing/editing, you can write all of your commands in a text editor, then copy/paste into the terminal window. Works like a charm.
Click to expand...


Cool, thanks for sharing that. I will have to try it out sometime!
 
I'm having a problem unlocking. I get to this step from the guide:
"Now go to HTCdev - Unlock Bootloader and fill out the forms and paste the code into the device identifier token box and submit. If you're having trouble with the HTC dev site, please disable any pop up blockers, anti-viruses, and/or firewalls (temporarily). You'll get an email (check your spam folder) with your unlock_code.bin. Once your receive it, transfer that file into your C:\sdk-tools\ folder. Now go back to your command window and type:

Code:
fastboot flash unlocktoken Unlock_code.bin
The unlock token should give you a prompt to accept the unlock code or not on the phone. Push volume up to accept."

And I get the success message in the CMD window but the phone never reboots and brings up the volume select splash screen.

It just stays in fastboot USB mode and the phone does nothing else.

Any tips? Going to bed, will check when I wake up...thanks in advance!
 
If I'm not mistaken, in the guide it says that after you try to flash the unlock code.bin and pretty much nothing happens as with you case, you can run an ruu then re flash the unlock code. Have you tried that?

Edit http://androidforums.com/showthread.php?t=539091
HBOOT 1.5 Firmware Upgrade / RUU Flash / Unbricking Guide

Follow the directions to flash the ruu then try to re flash the unlock code.

I had the same problem and had to do the ruu and fixed the problem for me

Edit 2: did you manually battery pull and enter bootloader to check if you was locked or unlocked?

Sent From My HTC Evo 3D Using TapaTalk 2
 
I'm sorry Crodley. I frequent this area and I don't know how I missed your post. Go ahead and try dragonslayer's advice and then if you are still having problems check back in and myself or someone will be here to help. If you have any questions before starting this, i will be checking in for another half hour or so before going to bed.

Crodley said:
Yikes, nearly 24 hours and no replies, it may be that rooting isn't in my future :(
Click to expand...
 
Got a late start tonight, thanks for the RUU suggestion, will try it tomorrow night when I have free hours ahead for banging my head against the keyboard. :)
 
Sorry it took a few days to get enough free time to move on. Running the RUU and starting over again worked, thanks SO much to all that helped. :)
 
im trying to root it but it wont read the .img for the recovery. yes its unzipped and in the mini adb folder and I renamed to recovery.img help??? thanks!
 
whbisondtr said:
im trying to root it but it wont read the .img for the recovery. yes its unzipped and in the mini adb folder and I renamed to recovery.img help??? thanks!
Click to expand...

What is the exact error? Any way you could post a screenshot of your command prompt after trying to flash the recovery.img?
 
Well, I did something really stupid. I had the original firmware on my Virgin Mobile HTC EVO 3d and wanted to root it. I installed the android SDK, installed TWRP and the SU patch. Everything was golden. The only reason I wanted SU was to install WiFi Tether for the one major road trip I make every year.

Fast forward 6 months. The old PC I had made all my backups on took a dump and the regular backups I made were corrupted, so I don't have the original ROM. I had turned of firmware update notifications originally and realized that ICS has been released so I figured I'd do the OTA update last night.

Update was installed on my phone, now my WiFi can't turn on. It only shows Error. From my research it is because there is a permission issue between the current wifi files and whatever the update was installing. At least that's what I have gathered.

So, as of now my status is:

UNLOCKED
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012,17:39:22

Does anybody know if I installed the Stock Deodex ROM, would it be possible to get WiFi access back, or am I screwed. I did read it may be possible to inject another wifi module into the firmware that will resolve the problem, but I no longer have the ICS OTA update file and can't re-download it.

Any help would be appreciated.
 
1991Syclone said:
So, as of now my status is:

UNLOCKED
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012,17:39:22

Does anybody know if I installed the Stock Deodex ROM, would it be possible to get WiFi access back, or am I screwed. I did read it may be possible to inject another wifi module into the firmware that will resolve the problem, but I no longer have the ICS OTA update file and can't re-download it.

Any help would be appreciated.
Click to expand...

I think (my wife would say therefore I'm wrong :rolleyes:) that since you're S-ON, you can relock, flash an older RUU with firmware (of course), then unlock again. A bit lengthy, but one of the costs of S-ON. That should get you back to where you were. I think! ;)
 
1991Syclone said:
UNLOCKED
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012,17:39:22

Does anybody know if I installed the Stock Deodex ROM, would it be possible to get WiFi access back, or am I screwed. I did read it may be possible to inject another wifi module into the firmware that will resolve the problem, but I no longer have the ICS OTA update file and can't re-download it.

Any help would be appreciated.
Click to expand...
That would certainly be the easiest thing to try. Format all partitions (except sd card) and do a fresh install. If it doesn't help, you will need to flash the SetMainVersionLow.zip through recovery and then run the RUU. It will return you completely stock, but will likely fix any problems you are having.


toad6386 said:
I think (my wife would say therefore I'm wrong :rolleyes:) that since you're S-ON, you can relock, flash an older RUU with firmware (of course), then unlock again. A bit lengthy, but one of the costs of S-ON. That should get you back to where you were. I think! ;)
Click to expand...
It depends on the OTA update he took. From the looks of it, he only took the November update. Normally s-on users cannot use an older version RUU. Luckily there is a zip file that can be flashed through recovery that allows you to run the one and only available ruu. If you have taken the Match OTA, it upgrades your hboot to 1.58 and at that point you are stuck without an RUU :(
 
Hi, I'm still noob in HTC's Android, and EVO 3D is my 2nd handset after G1 long long ago hehehe...

I tried to unlocking bootloader on hboot 1.58 to get root, but after I've read the instruction after getting unlock code from HTCdev it need to factory reset the handset to get unlocked. From what I've read earlier that factory reset using ##RTN# will revert the SPC back to factory default, is this procedure the same as factory reset using ##RTN#? Is this HTCdev unlock also reset the MIN, MDN, and PRL to factory default also?
 
This is a bit late, not sure if you've went forward from here or not, but it factory resets itself once the phone accepts the unlock token and is successfully unlocked.
 
I have a rooted evo3d. Sprint is trying to download the latest update, and when I tell it to install, it shuts down the phone and boots to the Install zip selection screen...did I do something wrong?
 
kmbutts said:
I have a rooted evo3d. Sprint is trying to download the latest update, and when I tell it to install, it shuts down the phone and boots to the Install zip selection screen...did I do something wrong?
Click to expand...

You likely can't take the OTA while rooted! It requires the stock recovery and also you pretty much need to have all the bloatware and be basically stock with root to take the OTA. Any changes to /system or lack of stock recovery will cause the ota to fail.

If s-off you can flash the firmware from the ota. Otherwise you can run the latest ruu to return to stock and take the OTA. Be warned though that if you take the OTA and you are s-on there will not be an ruu available to you anymore.
 
Excuse my ignorance, but how do I know if I have S-on vs S-off? Am in the process of installing 4ext paid version. hopes it helps with bluetooth not working either.
 
You would probably know because unless you had an older original release evo and were lucky enough to get revolutionary s-off, you'd have had to do the wire trick. But to check, go into your bootloader (battery pull then hold volume down + power). Should say right at the top in those few lines of text :)

No worries about ignorance. We're all here to learn. Even i learn new things all the time here ;) we all start somewhere and no matter what it seems like, nobody knows everything.
 
It is S-on....I think I really screwed things up.....I don't have 4G or Bluetooth anymore! Any suggestions? I am beginning to think this was not such a good idea!
 
Well sometimes things don't work on certain roms. Not sure what rom you are on? The fix all is the ruu. No need to panic when you have an ruu available. It returns you to stock but will fix everything. That's also why I suggest not updating unless s-off because then you don't have the luxury of an ruu :)
 
You must log in or register to reply here.
Back
Top Bottom