Database Users

[Guide][Unlock][Root]HTC EVO4g, unlock and root with HTCdev and su binaries

I am getting a ton of hits on my blog for this link! Please if you use the link, say hi to me or click the thanks button or at least leave feed back!
Also, ads help me out and want to do more writing!!!
Thank you everyone!
Click to expand...
Click to collapse
I decided to downgrade everything on my device and take the latest OTA, including the 2.18 hboot. This version is unlockable through the HTCdev website. From there you can simply flash a custom recovery and install the su binaries.
I have guides written up, on both, on my blog, and encourage you to check them out!
To unlock your bootloader, start HERE. Credit to HTCdev obviously for their attempt to give their customers what they want.
Next, to flash recovery and install su binaries check out THIS. Credit to chainsDD for his awesome work and continued devotion to root.
Note: This will not give you S-off, this does come with some limitations but I have not been hindered too much. The one thing I have not been able to do is flash a custom splash screen, because you have to do it through bootloader and it will not get past security. Other wise you can flash anything you would normally do in recovery.
My goal in doing this was to gain the experience, as many of the newer HTC devices only have this option available to them and I want to see the ins and outs as well as the downsides. I know there are methods of reverting back to froyo and using unrEVOked, which is tempting but I like the knowledge.
I already feel much more comfortable with SDK, fastboot and adb commands. This makes me feel more in tune with the Android OS and more comfortable to begin delving into development. I am a curious person and like to know what is going on with my device.
A discussion here would also be welcomed, for anything relating to using the unlocked bootloader. I will be glad to share my findings and try out some of the other things people are doing in order to use the phone in this state.
First off, any ideas on getting the splash screen changed? I was thinking, maybe a flashable zip? Or pushing through fastboot?

You won't be able to change the splash screen without S-OFF. You can only update the partitions that HTC has unlocked, which are boot, system, and recovery. The others still require signature verification, which means an unsigned zip won't write successfully. I don't know of any way around that, besides the obvious method of downgrading the HBOOT/Baseband and using a full NAND unlock method.

Captain_Throwback said:
You won't be able to change the splash screen without S-OFF. You can only update the partitions that HTC has unlocked, which are boot, system, and recovery. The others still require signature verification, which means an unsigned zip won't write successfully. I don't know of any way around that, besides the obvious method of downgrading the HBOOT/Baseband and using a full NAND unlock method.
Click to expand...
Click to collapse
So where is the splash screen located? I am fairly new to the insides of this stuff, really just dl and flash what sounds good.
Could you make a signed zip that would push the image?

imheroldman said:
So where is the splash screen located? I am fairly new to the insides of this stuff, really just dl and flash what sounds good.
Could you make a signed zip that would push the image?
Click to expand...
Click to collapse
Not exactly sure, but I think it has it's own home (separate from the unlocked partitions, that is). And we cannot make a signed zip that will update a locked partition because we don't have HTC's signature.

Wouldn't you be able to change the splash image 1 from a ruu with the splash screen and then run the ruu to get the splash screen
Sent from my swiper using XDA App

evo4gnoob said:
Wouldn't you be able to change the splash image 1 from a ruu with the splash screen and then run the ruu to get the splash screen
Sent from my swiper using XDA App
Click to expand...
Click to collapse
An RUU still authenticates through the bootloader and needs to have HTC's signature. There aren't any EVO HTC-signed RUUs with a splash screen different than the one we have.

Captain_Throwback said:
An RUU still authenticates through the bootloader and needs to have HTC's signature. There aren't any EVO HTC-signed RUUs with a splash screen different than the one we have.
Click to expand...
Click to collapse
If you go to the 3vo forums I believe there is a workaround for hboot 1.5 so I think it can be applied to us also
Sent from my swiper using XDA App

evo4gnoob said:
If you go to the 3vo forums I believe there is a workaround for hboot 1.5 so I think it can be applied to us also
Sent from my swiper using XDA App
Click to expand...
Click to collapse
Can you find it?

I am getting a ton of hits on my blog for this link! Please if you use the link, say hi to me or click the thanks button or at least leave feed back!
Also, ads help me out and want to do more writing!!!
Thank you everyone!

[INTERNATIONAL]Unlock Your Bootloader!

This process has been done with the HTC International version available in Australia.
Im sure everyone would appreciate follow up from others to confirm which versions of the phone this process works with.
The process below assumes a small amount of familiarity with HTC unlock process AND WILL WIPE THE DATA FROM YOUR PHONE!
The process is basically the same as ever with a few variations
Install adb
Go to http://www.htcdev.com/bootloader and sign up, click unlock bootloader
In the device selection drop-down select "any other supported device"
Boot into "Download Mode" - Which is the equivalent of fastboot. (shutdown your phone, hold power+volume down until you boot into this mode). This is the mode with the black background and red text
Connect phone to PC, and issue "fastboot oem get_identifier_token"
Copy the code into the returned by adb into space on HTCs website
Get the email, download the attachment and issue "fastboot flash unlocktoken Unlock_code.bin"

I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.

Always good to know we can root the new flagship

Super-Veloce said:
I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.
Click to expand...
Click to collapse
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..

jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Really?? Damn..

I keep getting:
Code:
C:\WINDOWS\system32>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Tried it on 2 different systems :S

What mode was your phone in? Were you in download mode? Or in the bootloader?

daveh86 said:
What mode was your phone in? Were you in download mode? Or in the bootloader?
Click to expand...
Click to collapse
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...

EndoSurf said:
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...
Click to expand...
Click to collapse
Thanks, I've added a note in my comment that mentions that download mode is the one with black background and red text.

And how i will make it S-Off?

Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
By being patient... the device is not even available in most regions yet, give developers a little time would you.

For Verizon test M9's, can't even pull identifier token. Fastboot command yields "FAILED (remote: unknown command)," which is interesting because I used fastboot to successfully flash TWRP then root.

jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Is there a way to s-off? Ive seen some have already done it, but how?

Test devices come S-OFF.

hgoldner said:
Test devices come S-OFF.
Click to expand...
Click to collapse
Or you can give the Phone to a shop / repair centre to s-off it
In Germany you can do it at:
http://www.gsm-europe.de/epages/635...3/Products/htc_soff/SubProducts/htc_soff-0001
Its a shop in Berlin they do s-off and supercid
And they can do it on the Onde M9
Only bad thing they cant Unlock bootloader it without HTC Dev.
So You get your phone back with S-Off and with Super Cid but Boodloader is Locked and you must Unlock it via HTC dev
because for Unlock via Fastboot you need root on Android 5

I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?

Prasad said:
I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?
Click to expand...
Click to collapse
Didn't notice any loss after unlocking M9 ..

jauhien said:
Didn't notice any loss after unlocking M9 ..
Click to expand...
Click to collapse
Thank you! Now I can confidently proceed when the device arrives in a couple hours.

Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
you're gonna have to wait a while for that

Been a long time since I unlocked a bootloader. But I don't lose any OTA functionality do I?
Sent from my HTC One M9 using XDA Free mobile app

-____-

After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..

Mohit M'S said:
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Click to expand...
Click to collapse
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?

DJBhardwaj said:
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
Click to expand...
Click to collapse
Your device is corrupt and can't be checked for corruption

Mohit M'S said:
Your device is corrupt and can't be checked for corruption
Click to expand...
Click to collapse
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?

DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Device is locked

Mohit M'S said:
Device is locked
Click to expand...
Click to collapse
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.

DJBhardwaj said:
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
Click to expand...
Click to collapse
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues

Mohit M'S said:
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Click to expand...
Click to collapse
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.

Heisenberg said:
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Click to expand...
Click to collapse
OK OK but after unlocking it there is any way to relock it and remove this error message

Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, of course. Infact that's the reason I asked you about the lock status on the first place. Stock ROM with locked bootloader shouldn't give this warning. It should make it go away.
That is why, I asked you to perform a flash manually. Please refer to Heisenberg's guide for the steps.
Here is the link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, after locking the bootloader the message should disappear. But, I'd strongly recommend leaving it unlocked and just dealing with the message. If an OTA ever fails or something else goes wrong you'll need fastboot to flash the factory images to recover your device, you'll be forced to unlock the bootloader, this will wipe the device and you'll lose all of your data because there'll be no way to back it up first.

DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Sorry message is Device can't be trusted or it may not work properly

Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
Did you reflash manually?

DJBhardwaj said:
Did you reflash manually?
Click to expand...
Click to collapse
Nope gonna do this by today or tomorrow

Mohit M'S said:
Nope gonna do this by today or tomorrow
Click to expand...
Click to collapse
Sure and then let us know. And keep the bootloader unlocked, it will help you to deal with a few issues (if any), in the future, as already mentioned above by Heisenberg.

-_____- why do people still use toolkits? Try getting use to Adb; it would save you a lot of time dealing with errors.

Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.

uicnren said:
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
Click to expand...
Click to collapse
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..??
Ruined my phone

Mohit M'S said:
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..
Ruined my phone
Click to expand...
Click to collapse
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.

uicnren said:
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
Click to expand...
Click to collapse
U didn't understand what I said I have already reverted my to stock ROM and relocked the bootloader but even then message is coming device can't be trusted or may not work properly and I'm not even getting any updates not even April update and all friends got this I'm currently pure stock
Problem are:-
Message is still there
Updates r not coming

S-Off Achieved by Firewater Devs

https://www.xda-developers.com/firewater-devs-htc-u11-s-off/
https://twitter.com/firewaterdevs/status/889118758865960961
Exciting.:good:
don't bug them, but this is good news.

riggsandroid said:
https://www.xda-developers.com/firewater-devs-htc-u11-s-off/
https://twitter.com/firewaterdevs/status/889118758865960961
Exciting.:good:
don't bug them, but this is good news.
Click to expand...
Click to collapse
We will need to learn how to work around having temporary S-Off, so paying attention to the new flashing instructions is going to be important.

nice! :good:
no we can install AOSP to replace the factory version, and or install Lineage OS

Kisakuku said:
We will need to learn how to work around having temporary S-Off, so paying attention to the new flashing instructions is going to be important.
Click to expand...
Click to collapse
Well they'll for sure dig a little bit further until they release it. So let's see if temporary may become permanent on the initial, or any follow up, release. First of I'm glad to see that they found out how to do it. Those are the great news many have been waiting for.
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
Well they'll for sure dig a little bit further until they release it. So let's see if temporary may become permanent on the initial, or any follow up, release. First of I'm glad to see that they found out how to do it. Those are the great news many have been waiting for.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Unfortunately the only way to get permanent S-OFF is an updated firmware that supports it. I was reading about it in the XTC2Clip forums. The product manager said that HTC may backtrack on it though because it's causing problems but didnt go into any further details. Also, it's impossible to set the phone back to factory right now. If you unlock the bootloader, the only thing that you can do is set the relocked flag thanks to temporary S-OFF which sucks considering HTC went back on their "U11 warranty even with unlocked bootloader" selling point. They say they are working on fixing that problem as well as adding SIM unlock in a future software update for the clip.
Things that the XTC2Clip can do right now with all the modules on the U11 (a 175 USD investment) - change CID, MID, downgrade firmware with temp S-OFF, unlock bootloader, etc.
If we don't get an engineering leak or HTC doesn't change course and put S-OFF back in, I doubt we will see it for awhile from the SunShine devs. Just because they got temp S-OFF doesn't mean they can make a nice easy to use tool. The phone now not only checks when the command is issued, it checks at boot and resets the flag. Trusted Reboot only works on that boot. It's going to be very easy to brick since the device goes right back to S-ON. If something wasn't successful, you've got a brick as soon as it reboots just like when people forgot to flash a RUU to go back to stock before going back to S-ON after modifying the firmware.
HTC engineering leaks have happened in the past when S-OFF couldn't be achieved so we will have to wait and see.

EtherealRemnant said:
Unfortunately the only way to get permanent S-OFF is an updated firmware that supports it. I was reading about it in the XTC2Clip forums. The product manager said that HTC may backtrack on it though because it's causing problems but didnt go into any further details. Also, it's impossible to set the phone back to factory right now. If you unlock the bootloader, the only thing that you can do is set the relocked flag thanks to temporary S-OFF which sucks considering HTC went back on their "U11 warranty even with unlocked bootloader" selling point. They say they are working on fixing that problem as well as adding SIM unlock in a future software update for the clip.
Things that the XTC2Clip can do right now with all the modules on the U11 (a 175 USD investment) - change CID, MID, downgrade firmware with temp S-OFF, unlock bootloader, etc.
If we don't get an engineering leak or HTC doesn't change course and put S-OFF back in, I doubt we will see it for awhile from the SunShine devs. Just because they got temp S-OFF doesn't mean they can make a nice easy to use tool. The phone now not only checks when the command is issued, it checks at boot and resets the flag. Trusted Reboot only works on that boot. It's going to be very easy to brick since the device goes right back to S-ON. If something wasn't successful, you've got a brick as soon as it reboots just like when people forgot to flash a RUU to go back to stock before going back to S-ON after modifying the firmware.
HTC engineering leaks have happened in the past when S-OFF couldn't be achieved so we will have to wait and see.
Click to expand...
Click to collapse
Yeah that's exactly what I thought but didn't explicitly state in my post above.
Sent from my htc_pmeuhl using XDA Labs

EtherealRemnant said:
Unfortunately the only way to get permanent S-OFF is an updated firmware that supports it.
Click to expand...
Click to collapse
Unless the development fuse isn't blown.

Patiently waiting

Kisakuku said:
Unless the development fuse isn't blown.
Click to expand...
Click to collapse
Which helps practically nobody. So again, it's back to the drawing board.

If testers are needed I am willing to have a crack at it. I have Australian Telstra firmware if that's of any use

Here you go.

Recovering from Idiocy - Relocked Bootloader with TWRP Recovery and Custom Rom in Pla

I'm posting this here half for help and half as a warning to others. Got burnt tinkering a bit to carelessly.
The story in short: unlocked bootloader, TWRP and Leedroid. Wanted to remove the start up "Unlocked Bootloader" message + possibly gain use of GPay. Googling around XDA stories of both bricked devices and people who had no problems. I figured I'd see what happened if I locked the boot loader and if I had problems I could just unlock it again, right? Wrong. After flashing Leedroid developer options, of course, had defaulted to disabled as well as 'Allow OEM unlock'. So after my device refused to boot, as I half expected it would, it also wouldn't let me un-lock it again, which I didn't expect.
So here I am stuck with a bricked device that has S-On and won't boot (corrupted device message). Only way out is Stock RUU from the original carrier of my device (Telstra, Australia). Unfortunately that seemingly doesn't exist on the internet for gods knows why and because S-ON can't change CID (TELST001) to flash something else.
I do have one half-baked idea that I don't see robustly covered already. I happen to have a second Telstra U11. My thought was to perhaps take that, image it using nandroid and then flash that image onto the bricked device via fastboot. Is that an option, or is that a no-go for some other reason?
Moral of the story: Don't play with fire unless your sure you have a fire extinguisher. And don't try and re-lock your bootloader no matter how much that warning bugs you.
Neil

Does anyone know whether I could nandroid image the stock U11 and use fastboot to flash that image to the soft bricked device?

You may try that, as in theory you can boot into system with original system IMAGE (bit-perfect) and boot image(kernel). And you may also want to s-off your device after successful boot.

TeroZ said:
You may try that, as in theory you can boot into system with original system IMAGE (bit-perfect) and boot image(kernel). And you may also want to s-off your device after successful boot.
Click to expand...
Click to collapse
No permanent S-OFF available, so no point in performing S-OFF as it doesn't save you of such a problem...
Sent from my HTC U12+ using XDA Labs

@TeroZ seems that with the bootloader re-locked any fastboot flash x.img command is rejected by default. Seems you can only flash in RUU mode. Does that make sense to you? That closes the only other alternative to sending it back to the official repairer just to have them rather than me flash the official RUU. What a scam.

5m4r7ph0n36uru said:
No permanent S-OFF available, so no point in performing S-OFF as it doesn't save you of such a problem...
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
I mean you could temporarily soff and change the cid and mid to debrand the phone and have access to usable RUU.

TeroZ said:
I mean you could temporarily soff and change the cid and mid to debrand the phone and have access to usable RUU.
Click to expand...
Click to collapse
I contacted the Sunshine guys and the s-off can only be done from within android (ie not download mode etc) so kills that as an option as well.
HTC won't provide Telstra RUU and also won't allow me to send it to repair center as it was apparently originally a demo device (to my suprise). So short of the Telstra RUU its officially soft bricked. Can't say I've ever been quite this burnt before flashing on ROM's etc. I'm more familiar with computer land and am just not used to the possibility of actually killing your computer via messing around in software (OC'ing is another kettle of fish of course). As long as it boots your fine.
Not so in the android world!
I'm open to trying anything at this point. There really is nothing left to lose.
N

Try contacting Telstra customer service instead and see if they provides ruu.

ngodber said:
I contacted the Sunshine guys and the s-off can only be done from within android (ie not download mode etc) so kills that as an option as well.
HTC won't provide Telstra RUU and also won't allow me to send it to repair center as it was apparently originally a demo device (to my suprise). So short of the Telstra RUU its officially soft bricked. Can't say I've ever been quite this burnt before flashing on ROM's etc. I'm more familiar with computer land and am just not used to the possibility of actually killing your computer via messing around in software (OC'ing is another kettle of fish of course). As long as it boots your fine.
Not so in the android world!
I'm open to trying anything at this point. There really is nothing left to lose.
N
Click to expand...
Click to collapse
Try this thread. Similar sort of issue with bricking. HTC 10 Batch tool was used
https://forum.xda-developers.com/u11/help/help-ruu-firmware-t3716144/post77822986#post77822986