Related
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
Just started reading up on EVO 4G LTE, i see how to root, but also S-Off. Do i need to do both? Do i need to do one before the other?
Any suggestions? I've had the original EVO and HTC Thunderbolt, i just rooted and i think it did root and S-off all at once.
What's S-OFF needed for? Sorry thought i knew what i was doing, used to flash a ROM every week on original EVO but now i'm a bit confused.
thanks in advance.
pdub110 said:
Just started reading up on EVO 4G LTE, i see how to root, but also S-Off. Do i need to do both? Do i need to do one before the other?
Any suggestions? I've had the original EVO and HTC Thunderbolt, i just rooted and i think it did root and S-off all at once.
What's S-OFF needed for? Sorry thought i knew what i was doing, used to flash a ROM every week on original EVO but now i'm a bit confused.
thanks in advance.
Click to expand...
Click to collapse
You don't need to S-OFF to flash roms but... it makes other tasks easier such as flashing the firmware bits (radio,PRI,ect)
Oh and the other advantage with being S-OFF you don't need to flash kernels separatly if there is not a kernel installer added to the rom script.
The term "Rooting" is usually used to describe the process of unlocking the bootloader and installing binaries that give you root access to the android operating system. Unlocking the bootloader gives you the ability to modify some partitions in the phone's internal memory (which is required to flash custom roms). Pretty much every custom ROM has the superuser binaries already included, so all you really need to do is unlock the bootloader and flash a custom ROM to be rooted.
S-off allows you to modify ALL partitions on the internal memory, so it's preferable to simply unlocking...but it's a more involved process and there's some risk associated with it.
Check out the OP of this thread, it has lots of good info for new users of this phone (and android phones on general):
http://forum.xda-developers.com/showthread.php?t=1869377
Sent from my EVO LTE
pdub110 said:
Just started reading up on EVO 4G LTE, i see how to root, but also S-Off. Do i need to do both? Do i need to do one before the other?
Any suggestions? I've had the original EVO and HTC Thunderbolt, i just rooted and i think it did root and S-off all at once.
What's S-OFF needed for? Sorry thought i knew what i was doing, used to flash a ROM every week on original EVO but now i'm a bit confused.
thanks in advance.
Click to expand...
Click to collapse
I quote from this thread:
xmoo said:
HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Click to expand...
Click to collapse
In short, there's not really an argument against going through the process. It'll make your life easier. If you do want both S-OFF and root, go through the S-OFF process completely first before you install a custom recovery and superuser.
I'm assuming you have a newer device, so you probably have HBOOT 1.15 or 1.19, in which case you should go here for S-OFF. You'll need a Windows machine for that. Give the instructions a good once over before going through the process; follow them to the letter and you won't have any problems.
If your firmware version is 1.22.651.3 or higher, use this method to root. Again, give the instructions a once over before going through the process.
HTC EVO 4G LTE Hboot Versions & Info
I am not a developer-this is simply my contribution to the HTC EVO 4G LTE community as a way to help users have a basic understanding of what Hboot is, and understand the differences and capabilities between Hboot versions. In addition to information regarding the various Hboot versions, I have included a guide on how to update firmware (since this is done through the bootloader). Also included is a section on kernel flashing for those who haven't taken the plunge and gained S-off yet. You are free to include my work if you are putting together a guide or FAQ of your own, I only ask that you give credit where credit is due. I've taken a lot of time and put some effort into making this guide as complete as possible, but if you see something you'd like to have added or have a question or comment, feel free to do so. You can also reach me via PM. As I currently own this device, I will try my best to keep this guide up to date. I am not responsible for any misinterpretations of the information contained within this guide, and I will not be held liable or responsible should you damage your phone or cause an act of war. Now, let's get started.
What is Hboot? Without getting too technical, Hboot is your bootloader. Its functions are similar to that of the BIOS (Basic Input/Output System) on a PC. The bootloader provides a level of security for your phone by preventing unsigned software and firmware from being installed on your phone. At times, the bootloader will be updated to provide bug fixes and security patches. This sounds like a good thing, but it's really just a roadblock for those of us who like to tinker with our phones. This is where unlocking the bootloader comes in to play. Unlocking the bootloader allows us to install custom recoveries, from which we can flash custom ROM's to our phones. Still, however, depending upon the bootloader security, you are still limited to what you can do once the bootloader is unlocked. Unlocking the bootloader on the HTC EVO 4G LTE is accomplished using HTC Dev, or by using one of the tools provided by developers here on XDA (the toolkits, often referred to as "one-clicks", still use HTC Dev to unlock-there is no way around it). I won't delve into the actual process of unlocking the bootloader, as there are countless places here on XDA and elsewhere that guide you through the process.
S-on vs. S-off. When you received your HTC EVO 4G LTE new, it shipped with a locked bootloader and was S-on, which meant that bootloader security was on. While true that unlocking the bootloader gives some added functionality, like being able to install a custom recovery such as TWRP (Team Win Recovery Project) or CWM Touch, and allowing the flashing of a custom ROM, there are still limitations based on the bootloader (Hboot) version. This is where S-off comes in to play. If S-on means security on, then yes, S-off means security off. Once S-off, the bootloader's security is turned off. Kernels, splash screens and unsigned firmware can be flashed with relative ease. As more than one developer has put it, you are essentially future-proofing your device. This is especially true given the restrictions that HTC has put in place on the newer bootloaders. Think of bootloader unlocking and S-off like a bank. Bootloader unlocking gets you in the front door; S-off gets you into the vault. Currently, there are four ways to gain S-off on the EVO LTE: Dirty Racun, Facepalm, Moonshine and Rumrunner. For more information regarding S-off, check out this thread here.
The bootloader screen
View attachment 1924777
How do you access the bootloader menu? If you're running a Sense ROM, make sure you have fastboot disabled in settings. You can go to Menu>Settings>Power and make sure fastboot isn't enabled. Don't confuse the fastboot setting with fastboot in the bootloader-they are not the same. Power your phone completely off. Press and hold the volume down button, then press and hold the power button (most custom ROM's normally let you reboot to the bootloader from the power menu, also). After several seconds you will be presented with a white screen with some information in the top left corner of the screen. Stock, the top line will say "Locked". Once unlocked, the top line will read "Unlocked". If the bootloader has been relocked, the top line will read "Relocked". Once unlocked or relocked, there will also be a "Tampered" warning, as well. Below that is the HTC device codename, which is Jewel. On this same line, you will see whether the phone is S-on or S-off. The fourth line from the top is the Hboot version, and below that is the radio (baseband) version. From the bootloader menu there are also options to power off the phone, reboot the bootloader, enter fastboot mode, factory reset and go to recovery. To navigate the menu, simply use the volume keys to move up and down, and use the power button to select (note in the picture above I have used regaw_leinad's bootloader customizer to customize the Hboot info). From the bootloader screen you can select the "fastboot" option, whereby you can connect your phone to your PC and issue commands via fastboot USB if you have the correct drivers installed on your computer. You have to have a properly working ADB (Android Debug Bridge) & Fastboot environment set up on your computer first in order to do so. You also haveit when using HTC Dev to unlock your bootloader, so it comes in handy in more ways than one and doesn't hurt to have it on your computer should you ever need to use it. If you're ever stuck in a boot loop you can simply wait until the phone's screen goes black and hold the volume down button until the bootloader screen appears.
Below is a list of current Hboot versions for the HTC EVO 4G LTE:
Hboot 1.12: S-on (Security on) allows flashing of modified firmware and kernels. Kernel does not have to be flashed separately from ROM. Least restrictive Hboot for the EVO LTE. S-off can be obtained via Dirty Racun or Facepalm.
Hboot 1.15: S-on, kernel must be flashed separately from ROM either via Flashify or Fastboot. S-off can be obtained via Dirty Racun or Facepalm.
Hboot 1.19: Same info as Hboot 1.15.
Hboot 2.09: Permanent write to system partition disabled when S-on. Kernel must be flashed separately via Fastboot or Flashify. S-off can be obtained via Dirty Racun or Facepalm if on software version 3.15 (baseband ending in 1119)/Dirty Racun if on software version 3.16 (baseband ending in 1210). You can use Baby Racun to downgrade from 3.16 to 3.15, at which time you can use Facepalm. You can also use Moonshine S-off for software version 3.16. Use Rumrunner S-off for software version 3.17.651.4 (baseband ending in 0830) & 3.17.651.5.
Hboot 2.10: Software version 4.13.651.1 (.3/.4)/Firmware version 1.13.11.1105: Ability to downgrade from this version to a previous version can be done via RUU if S-off. S-off with Rumrunner. For further information, look at this thread here.
***The OTA update for software version 3.16.651.3 included a touch panel driver update. If you are on this update, you can only use ROM's based on software version 3.16 & 3.17, otherwise the touch screen will not respond to touch input. You must also use TWRP 2.4+ with the updated touch panel driver. You can downgrade the touch panel driver to the previous version if you're S-off. AOSP ROM's utilizing the 3.4 kernel support the updated touch panel driver and does not require downgrading***
Bootloader unlocking tools:
HTC Dev
WinDroid toolkit
qbking77's bootloader unlocking video
How to obtain S-off:
Dirty Racun-No longer supported
Facepalm-No longer supported
Moonshine
Rumrunner
I take no credit for any of the tools or methods listed above. The above listed tools are the property of their respective developers/contributors.
S-off vs. Root
There always seems to be some confusion among some users regarding root and S-off. First off, they are not the same thing. Root is a method by which users can run privileged commands on their device.
Rooting is typically accomplished by a security exploit that allows the su (superuser) binary to be installed on the device, which in turn installs either the SuperUser or SuperSU app on the device. Both of these apps give the user the ability to grant or deny root apps to function. In addition to running certain apps (like WiFi tether, Root Explorer or Titanium Backup), root privilege can also allow the removal of files and apps which could not be removed by a user with an unrooted phone (for example, removing carrier-installed "bloatware").
Some users think that you must be S-off in order to have what they call "full root", which is simply not the case, as root and S-off are independent of one another. It's actually quite the contrary, as you can have a phone that is S-off but does not have root access. How is this so? Remember, S-off simply means that the bootloader's security is off. In order to root a phone, you must have a custom recovery installed and have the proper superuser binary in place for root to work. S-off methods are not always available when a new phone is released (or when a phone receives updated software and/or firmware), which is why we have methods like HTC Dev to unlock our bootloader.
If a method to gain S-off is available, it's best to use it. Like I stated earlier, S-off is virtually future-proofing your phone, so regardless of any updates that may come out, once you're S-off, that's it: you're S-off until a method is released to put the device back to S-on, and that's something the device user typically initiates (for example, the VipeRUU tool). S-off trumps bootloader unlocking because being simply bootloader unlocked, there are still security restrictions on the bootloader. S-off removes those restrictions. But, as stated earlier, without a custom recovery and superuser in place, the device is not rooted. The ideal situation is to be rooted and S-off. Gaining S-off allows the user to flash a ROM and not have to flash the kernel separately when on Hboot 1.15+, allows for changing the splash screen, customizing the bootloader, getting rid of the red development disclaimer text & flashing firmware updates, just to name a few benefits.
A quick word of caution regarding S-off. With the bootloader's security off, there is no longer any protection should you flash a corrupt or incompatible file to your device, so know & understand what you're doing and don't do something foolish to turn your device in to an expensive paperweight.
On the HTC EVO 4G LTE, the root method is the same regardless of the Hboot or software version.
Firmware Updates
From time to time, it may be necessary to update your phone's firmware, sometimes referred to as your radios or your baseband. This can be done for a number of reasons, ranging from call quality or data connection issues or poor battery life due to outdated firmware, just to name a few things. Personally, I like to keep my firmware version updated to whatever the newest corresponding software version is at the time. Keep in mind that firmware and software are not the same. Software is the ROM you flash via recovery. Firmware is the radios, PRI and whatever other bits a developer chooses to include. The only time you get both packaged together is in a OTA (Over The Air) update sent out by the phone carrier, or by RUU. Since rooted users don't typically take OTA updates, we have to rely on developers to pull the firmware from the update package and re-package it for our use. You must be S-off to install modified firmware on your device. To update your firmware, first download the applicable firmware package. You can download the file to either your phone or your computer. Typically, the file will have an MD5 sum that acts as a fingerprint to verify that your download matches that of the original. You can use an app like Android File verifier to check the MD5 of the downloaded file versus that of the original file. If the MD5's match, you're good to go. If not, you need to download the file again, making sure you check the MD5 again. This is important, as you don't want to screw up a firmware update. A bad firmware flash is a good way to turn your phone into an expensive paperweight. Once you have the file downloaded you need to transfer it to the root (not in a folder) of your external microSD card. Firmware updates cannot be run from the phone's internal memory. Check and make sure that the file is named PJ75IMG.zip (If using your computer, Windows often hides the .zip extension so if you don't see it on your computer, right-click on the file and select "Properties" to see if the .zip extension is there, which it should be). If you downloaded the file directly to your phone, you can use a file manager like Astro file manager or Root Explorer to check that the file is properly named. The bootloader will be looking for the file named PJ75IMG and, if improperly named, will not locate it. Sometimes the file won't require renaming but it's important to check and make sure, to save you some headache down the road. Make sure you also have a decent charge on your battery, because if your phone dies during the firmware update, you'll end up with a bricked device, most likely. Now, you need to reboot to the bootloader, which was discussed previously. Your phone should reboot to Fastboot mode. Use the volume buttons to navigate to the "Bootloader" option in the menu, and press the power button to make your selection. The bootloader will now scan for the firmware update on your SD card, and once it finds it, will prompt you as to whether or not you wish to start the update. Once again, use the volume buttons to make your choice. The update may take a couple of minutes to complete, at which time you'll be prompted to either power off the phone or reboot. Reboot the phone, then go to Menu>Settings>About Phone>Software info and check your baseband version and see if it corresponds to the firmware update you just installed. Once you've done this and confirmed that the update was successful, delete the PJ75IMG file from your SD card (if you don't do this, you will be prompted to update your firmware every time you reboot to the bootloader). If the update fails from the bootloader, go back through the steps outlined above and double-check that you have done everything correctly. For more information regarding firmware updates, see Captain Throwback's firmware thread, which I have provided a link to at the bottom of this post.
A quick note about the bootloader. With an SD card installed in your phone, the bootloader will always scan for a PJ75IMG file, as shown by the green text that says "No image or wrong image". This is normal as long as an SD card is installed. If you are attempting to update firmware and see this text but don't get prompted to update, make sure the file is named correctly. Otherwise, it's not an error and shouldn't be confused as such.
RUU's
Occasionally, you may encounter an issue which requires a RUU (ROM Update Utility). This is an update package released either by a OEM (like HTC) or a developer. It is designed to put the phone back to stock condition. This can be done for a variety of reasons including updating to a newer software version or for returning the phone back to stock to have the device serviced by the carrier or manufacturer. Note that if your device is S-on, you can only run a RUU with the same software/firmware version that you're currently running, or a newer version. If you're S-off, the same applies, and in addition, you can also downgrade to an older version than what's installed on your device. Running a RUU will re-lock your bootloader and unroot your phone. To root again, you'll need to unlock the bootloader, install a custom recovery and install the necessary SU binary. On S-off phones, the device will remain S-off but the bootloader will need to be unlocked again with HTC Dev. See the bottom of this post for a complete list of links to current available RUU's.
To run a RUU, simply download the RUU you wish to install to your PC, then connect your phone and PC via USB cable. While booted to the Android OS, simply double-click the RUU file on your computer to start the installer, then follow the on-screen instructions. Normally, a RUU is run while the phone is booted to the OS but alternatively, can be run while the phone is connected to the computer via Fastboot USB mode. Simply connect the phone and PC via Fastboot USB mode, then double-click the RUU file on your computer to start the installer. If your device is S-on you will need to relock your bootloader to run a RUU. Use the command "fastboot oem lock" to relock your bootloader (without quotation marks). You need to install HTC Sync to your computer to get the proper drivers installed to help connect your device to your computer.
S-on Kernel Flashing
Below is a short guide on how to flash kernels while S-on using Hboot 1.15 & up. First, check out the link below for an easy how-to on setting up ADB on your computer (credit to Jerry Hildenbrand at Android Central for the write-up). The guide also includes a basic set of commands that users might find useful while using ADB. If you need device drivers for your PC, I have provided a link at the bottom of this thread. You can also install the latest version of HTC Sync to get the latest drivers installed on your computer.
How to set up ADB and ADB commands
Some developers include an S-on kernel flasher in their ROM's to simplify ROM flashing (such as xHausx's kernel installer). Simply follow the instructions in the ROM's OP, as methods may vary.
If no kernel installer is included as part of the ROM, there are two basic ways to flash a kernel to your phone while S-on. The first method is using an app from the Play store called Flash Image GUI. Simply follow the instructions in the app. The second method is to flash the kernel via Fastboot, which I will explain below.
First, download the ROM of your choosing to your phone. Once you've done this, navigate to where you downloaded the ROM on your computer and extract the boot.img from the ROM zip file. Place it in your ADB tools folder. The boot.img is the ROM's kernel, which is needed for the ROM to work. Without getting too technical, the kernel allows the phone's hardware and software to work together. Boot into recovery and flash the ROM zip. Then, reboot into the bootloader. Your phone should say Fastboot, highlighted in red. If not, use your volume keys to highlight the Fastboot option from the menu we discussed previously, then use the power button to select. You should then see the word Fastboot highlighted in red. Connect your phone and PC via USB cable. Once the connection is complete, you will see "Fastboot" change to "Fastboot USB". Open up your ADB/Fastboot terminal (Shift+Right click on the folder, then choose the option to open up a command line), then follow the instructions below:
Type:
Code:
fastboot devices
Press enter. Your phone's serial number should be output on the line below, so now you know that fastboot recognizes your phone.
Now, type:
Code:
fastboot flash boot boot.img
Press enter. The kernel should then be flashed to your phone, unless you get an error message in the command terminal. After flashing the kernel via fastboot, you can reboot your phone.
You can also use the HTC Dumlock feature in TWRP recovery to flash a kernel while S-on. You can find information on Team Win's site in the link below.
TWRP Dumlock
Hopefully after reading all this you have a better-or at least basic-understanding of what Hboot is and what the bootloader does on this device.
Thanks to:
@Sloth Please check out his FAQ.
@om4 You can check out his "Don't Panic" guide here.
@WindyCityRockr for his Windroid toolkit
@qbking77 for his Youtube video.
@Captain_Throwback for his firmware thread, which you can find here.
If you're looking for the latest drivers for your computer, check out this thread here. Thanks @CNexus for making this thread. You can also install the latest version of HTC Sync to get the drivers you need.
@regaw_leinad for his thread explaining S-off.
RUU links:
HTC EVO 4G LTE Shipped ROM's
3.17.651.4 RUU
4.13.651.4 RUU ***Please note that this RUU changes the partition of the internal storage. Prior to this RUU, internal storage was broken up into two separate partitions, (Internal storage+Media storage). This RUU changes the partition setup to where there is only Internal storage. Approximately 12GB is available via this partition setup. Also note that while there were two previous RUU's for the Android 4.3 update, this one has data roaming working properly and is the reason I included it and not the previous ones.***
VipeRUU (based on 3.16.651.3) Please note that VipeRUU ONLY works if the device is S-off and can be used to return the device to a totally stock, unrooted state.
Enjoy
Excellence. Now I don't need to make this post. much appreciated.
Delakit said:
Excellence. Now I don't need to make this post. much appreciated.
Click to expand...
Click to collapse
Just glad to contribute to the good of the order
Sent from my EVO using xda premium
Fin, thanks for the link to the ADB guide. I need to set it up on a new computer and couldn't remember how I did it on my old one. (Particularly in terms of setting up the paths so you can run commands from any location). :thumbup:
Sent from my EVO using xda premium
scottspa74 said:
Fin, thanks for the link to the ADB guide. I need to set it up on a new computer and couldn't remember how I did it on my old one. (Particularly in terms of setting up the paths so you can run commands from any location). :thumbup:
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Not a problem
Sent from my EVO using xda premium
Nice work bro
Sent from Blues and Jazz One
Updated with link's to om4's "Don't Panic" guide & bigdaddy619's Q&A guide. Also added some more info about S-on/S-off and bootloader menu info, and added a link to HTC Dev. Added a poll, as well.
Just trying to be thorough
Can you please add info on how to install/run Linux/wubi from a USB or a cd or a dual boot? I think we need a noob guide on how to do that since the guys that gave us s-off (big thanks to Team Unlimited) only support Linux, thanks for this guide...
jocarog said:
Can you please add info on how to install/run Linux/wubi from a USB or a cd or a dual boot? I think we need a noob guide on how to do that since the guys that gave us s-off (big thanks to Team Unlimited) only support Linux, thanks for this guide...
Click to expand...
Click to collapse
What Hboot & software version are you currently on?
Edit: Disregard that, I was using the app when I replied and didn't see you signature. Having said that, I haven't messed with Linux and wouldn't feel comfortable putting something like that together, not to mention that it would go against Team Unlimited and the rules they have set forth regarding the use of their tools.
Sent from my EVO using xda premium
FinZ28 said:
What Hboot & software version are you currently on?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
^^^^^^ Linux noob
bigdaddy619 said:
^^^^^^ Linux noob
Click to expand...
Click to collapse
I wouldn't even go that far
I was on the original hboot, but my Bluetooth stopped working and I'm waiting for a replacement, probably will end up with latest hboot :crying::crying:
I've used viperruu to get my evo back to stock when I took it back to sprint, so it's on 2.09, not even rooted, I have a dual boot desktop with the latest wubi version, the easiest way for me to use Linux, just for things like the s-off process, I used lazy panda on windows, but I'm still learning on how to use Linux, I'm a noob!
jocarog said:
I was on the original hboot, but my Bluetooth stopped working and I'm waiting for a replacement, probably will end up with latest hboot :crying::crying:
I've used viperruu to get my evo back to stock when I took it back to sprint, so it's on 2.09, not even rooted, I have a dual boot desktop with the latest wubi version, the easiest way for me to use Linux, just for things like the s-off process, I used lazy panda on windows, but I'm still learning on how to use Linux, I'm a noob!
Click to expand...
Click to collapse
I understand. Your best bet is to hit up Team Unlimited on their IRC channel and get help when the time comes. I've heard that the support for their tools is excellent
Updated 5/3/2013 with info & link for HTC Dumlock
I've personally never used this feature but I've read where it can be helpful for users who are S-on and I thought it would be a good idea to include it in the guide.
Thanks for the writeup.
I was lucky to be able to get in under the wire and avoided even using HTC dev to go S-Off on my LTE and still have hboot 1.12. Is there utility to any of the bug fixes you mention in the later bootloader versions? It may be helpful to say whether or not the bug fixes apply to anything outside the bootloader itself because the natural assumption I make when someone mentions "bug fixes" is to think an upgrade may make sense. If its a trade-off to upgrade and may better to stay on 1.12 unless you have issues with the device, saying that in the guide would also be helpful.
APDRJRD said:
Thanks for the writeup.
I was lucky to be able to get in under the wire and avoided even using HTC dev to go S-Off on my LTE and still have hboot 1.12. Is there utility to any of the bug fixes you mention in the later bootloader versions? It may be helpful to say whether or not the bug fixes apply to anything outside the bootloader itself because the natural assumption I make when someone mentions "bug fixes" is to think an upgrade may make sense. If its a trade-off to upgrade and may better to stay on 1.12 unless you have issues with the device, saying that in the guide would also be helpful.
Click to expand...
Click to collapse
Like I stated in the guide, there is no reason to upgrade or downgrade, particularly since there are S-off methods for all Hboot versions. If you're on 1.12 (like myself and many others), your best bet is to stay on it. Having said that, though, you could RUU to a newer software version and upgrade your Hboot and still be S-off, but I don't see the point unless you're one of those people that has to have the newest everything (including Hboots)
I modified the guide based on the fact that honestly I don't know what "bug fixes" were truly implemented in the newer bootloaders, and I don't want to mislead anybody. If and when I can come up with better info for each version I'll be happy to share it.
The guide honestly started off as an effort to help those people who were having issues flashing while S-on, and it just grew from there. I feel like it's pretty complete without having too much info in it.
Thanks for your comments
Edit: I reached out to HTC in an effort to obtain more information regarding the topic of bootloader versions and the differences between the versions. Here is an excerpt from the email I received today (5/5/2013) from HTC employee Andres:
"I apologize, for any inconvenience that this may cause. Hboot is your bootloader. Its functions are similar to that of the BIOS on a PC. The bootloader provides a level of security for your phone by preventing unsigned software and firmware from being installed on your phone. At times, the bootloader will be updated to provide bug fixes and security patches.
Currently the versions for the HTC EVO 4G LTE are:
•Hboot 1.12
•Hboot 1.15
•Hboot 1.19
•Hboot 2.09
Keep in mind that these versions might have change depending on the updates release by the carrier.
If you have any other questions about your device please feel free to contact us via email at any time."
Looks familiar
I wonder how often HTC employees reach out to places like XDA for information?
Sent from my EVO using xda premium
FinZ28 said:
Edit: I reached out to HTC in an effort to obtain more information regarding the topic of bootloader versions and the differences between the versions. Here is an excerpt from the email I received today (5/5/2013) from HTC employee Andres:
"I apologize, for any inconvenience that this may cause. Hboot is your bootloader. Its functions are similar to that of the BIOS on a PC. The bootloader provides a level of security for your phone by preventing unsigned software and firmware from being installed on your phone. At times, the bootloader will be updated to provide bug fixes and security patches.
Currently the versions for the HTC EVO 4G LTE are:
•Hboot 1.12
•Hboot 1.15
•Hboot 1.19
•Hboot 2.09
Keep in mind that these versions might have change depending on the updates release by the carrier.
If you have any other questions about your device please feel free to contact us via email at any time."
Looks familiar
I wonder how often HTC employees reach out to places like XDA for information?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
That's pretty hilarious. Always comforting to know that customer support has to resort to a Google search when answering pretty basic questions about their own software.
APDRJRD said:
That's pretty hilarious. Always comforting to know that customer support has to resort to a Google search when answering pretty basic questions about their own software.
Click to expand...
Click to collapse
Yup
Updated on 5-27-2013 to include information regarding the updated touch panel driver that came with the latest OTA (software version 3.16, baseband 1210).
Sent from my EVO using xda premium
What would you do?
FinZ28 said:
HTC EVO 4G LTE Hboot Versions & Info
First off, I'm not a developer in any way, shape, form or fashion. I simply decided to write this guide for people to have a basic understanding of what Hboot is, and understand the differences and capabilities between Hboot versions, as well. In addition, there is a guide on how to flash kernels while S-on. If you feel I've missed something or would like to see something added, please feel free to PM me or leave a comment. Also, if you are making a guide and wish to include my guide as part of your work, feel free to do so. I only ask that you give credit where credit is due.
What is Hboot? In a nutshell, Hboot is your bootloader. Its functions are similar to that of the BIOS (Basic Input/Output System) on a PC. The bootloader provides a level of security for your phone by preventing unsigned software and firmware from being installed on your phone. At times, the bootloader will be updated to provide bug fixes and security patches. This sounds like a good thing, but it's really just a roadblock for those of us who like to tinker with our phones. This is where unlocking the bootloader comes in to play. Unlocking the bootloader allows us to install custom recoveries, from which we can flash custom ROM's to our phones. Still, however, depending upon the bootloader security, we may be limited to what we can do once the bootloader is unlocked. Unlocking the bootloader on the HTC EVO 4G LTE is accomplished using HTC Dev, or by using one of the tools provided by developers here on XDA. I'm not going to delve into the actual unlocking process here, as there are countless places here on XDA and elsewhere that outline how to use HTC Dev.
What is S-off? When you received your HTC EVO 4G LTE new, it shipped with a locked bootloader and was S-on, which means that bootloader security is on. While true that unlocking the bootloader gives some added functionality, like being able to install a custom recovery such as TWRP (Team Win Recovery Project) and allowing the flashing of a custom ROM, there are still limitations based on the bootloader (Hboot) version. This is where S-off comes in to play. If S-on means security on, then yes, S-off means security off. Once S-off, the bootloader's security is turned off. Kernels, splash screens and firmware can be flashed with relative ease. As more than one developer has put it, you are essentially future-proofing your device. This is especially true given the restrictions that HTC has put in place on the newer bootloaders. Think of bootloader unlocking and S-off like a bank. Bootloader unlocking gets you in the front door; S-off gets you into the vault. As of this write-up, there are two ways to gain S-off on the HTC EVO 4G LTE: Dirty Racun and Facepalm.
The bootloader screen
View attachment 1924777
How do you check your Hboot version? Make sure you have fastboot disabled in settings (not to be confused with Fastboot USB). Go to Menu>Settings>Power and make sure Fastboot isn't enabled. Power your phone completely off. Press and hold the volume down button, then press and hold the power button (most custom ROM's normally let you reboot to the bootloader from the power menu, also). After several seconds you will be presented with a white screen with some information in the top left corner of the screen. Stock, the top line may say "Locked", "Unlocked" or "Relocked", depending on whether or not the bootloader has been unlocked. Below that is the HTC device codename, which is the Jewel in the case of the EVO 4G LTE. The fourth line from the top is the Hboot version, and below that is the radio (baseband) version. From the bootloader menu there are also options to power off the phone, reboot the bootloader, enter fastboot mode, factory reset and go to recovery. To navigate the menu, simply use the volume keys to move up and down, and use the power button to select (note in the screenshot above I have used regaw_leinad's bootloader customizer to change the top line of the bootloader to my XDA screen name). From the bootloader screen you can select the "fastboot" option, whereby you can connect your phone to your PC and issue commands via fastboot USB if you have the correct drivers installed on your computer. You have to have ADB (Android Debug Bridge) set up on your computer first in order to do so. You also have to use ADB when using HTC Dev to unlock your bootloader, so it comes in handy in more ways than one and doesn't hurt to have it on your computer should you ever need to use it.
Below is a list of current Hboot versions for the HTC EVO 4G LTE:
Hboot 1.12: S-on (Security on) allows flashing of radios and kernels. Kernel does not have to be flashed separately from ROM. Least restrictive Hboot for the EVO LTE. S-off can be obtained via Dirty Racun or Facepalm. Lazy Panda is no longer supported as of this write-up.
Hboot 1.15: When S-on, kernel must be flashed separately from ROM either via Flash Image GUI or Fastboot. S-off can be obtained via Dirty Racun or Facepalm.
Hboot 1.19: Same info regarding S-on kernel flashing as Hboot 1.15. S-off can be obtained via Dirty Racun or Facepalm.
Hboot 2.09: Permanent write to /system disabled. S-off can be obtained via Dirty Racun or Facepalm if on software version 3.15 (baseband ending in 1119)/Dirty Racun (Baby Racun) if on software version 3.16 (baseband ending in 1210). Kernel must be flashed separately from ROM if S-on.
***The latest OTA from Sprint (software version 3.16, baseband 1210) included a touch panel driver update. If you are on this update and are S-on, you can only run 3.16-based ROM's, otherwise the touch screen will not respond to touch input. You must also use TWRP 2.4+ with the updated touch panel driver. You can downgrade the driver once obtaining S-off.***
Is it necessary to downgrade your Hboot? At the moment, no. In the past, prior to Dirty Racun, it was necessary to downgrade your Hboot if you were on Hboot 1.15 or 1.19 so that you could run Lazy Panda to gain S-off. Currently, this is not the case and is generally ill-advised to do so. It's also not necessary to upgrade your Hboot unless you are on Hboot 1.12 and wish to S-off your device using Dirty Racun, since Lazy Panda is no longer supported.
Bootloader unlocking tools:
HTC Dev
hasoon2000's All-In-One toolkit
How to obtain S-off:
Facepalm
Dirty Racun
I take no credit for any of the tools listed above.
S-off vs. Root
There seems to be some confusion regarding root and S-off. First off, they are not the same thing. Root is a method by which users can run privileged commands on their device.
Rooting is typically accomplished by a security exploit that allows the root software to be installed on the device. In addition to running certain apps (like WiFi tether or file managers), root privilege can also allow the removal of files and apps which could not be removed by a user with an unrooted phone (for example, the removal of carrier-installed "bloatware"). Root privilege is typically granted by one of two apps, Superuser and SuperSU. These apps, which require root to work, allow the user to grant or deny root apps permission to operate.
Root access is not the same as S-off, however, and some users think that you must be S-off in order to be rooted, which is simply not the case. It's actually quite the contrary, as you can have a phone that is S-off but does not have root access. How is this so? Remember, S-off simply means that the bootloader's security is off. In order to root a phone, you must have a custom recovery installed and have the proper superuser binary in place for root to work. S-off methods are not always available when a new phone is released (or when a phone receives updated software and/or firmware), which is why we have methods like HTC Dev to unlock our bootloader.
If a method to gain S-off is available, it's best to use it. Like I stated earlier, S-off is virtually future-proofing your phone, so regardless of any updates that may come out, once you're S-off, that's it: you're S-off until a method is released to put the device back to S-on, and that's something the device user typically initiates. S-off trumps bootloader unlocking because being simply bootloader unlocked, there are still security restrictions on the bootloader. S-off removes those restrictions. But, as stated earlier, without a custom recovery and superuser in place, the device is not rooted. The ideal situation is to be rooted and S-off. Gaining S-off allows the user to flash a ROM and not have to flash the kernel separately when on Hboot 1.15+, allows for changing the splash screen, customizing the bootloader, getting rid of the red development disclaimer text & flashing firmware updates, just to name a few benefits.
S-on Kernel Flashing
Below is a short guide on how to flash kernels while S-on using Hboot 1.15 & up. First, check out the link below for an easy how-to on setting up ADB on your computer (credit to Jerry Hildenbrand at Android Central for the write-up). The guide also includes a basic set of commands that users might find useful while using ADB.
How to setup ADB and ADB commands
Some developers include an S-on kernel flasher in their ROM's to simplify ROM flashing (such as xHausx's kernel installer). Simply follow the instructions in the ROM's OP, as methods may vary.
If no kernel installer is included as part of the ROM, there are two basic ways to flash a kernel to your phone while S-on. The first method is using an app from the Play store called Flash Image GUI. Simply follow the instructions in the app. The second method is to flash the kernel via Fastboot, which I will explain below.
First, download the ROM of your choosing to your computer. Once you've done this, navigate to where you downloaded the ROM and extract the boot.img from the ROM folder and place it in your ADB tools folder. The boot.img is the ROM's kernel, which is needed for the ROM to work. Place the ROM on your phone so that you can flash it via recovery. Flash the ROM like normal. Once completed, reboot to the bootloader (if using TWRP recovery you can do this from the reboot menu). Your phone should say Fastboot, highlighted in red. If not, use your volume keys to select the Fastboot option from the menu we discussed previously, then use the power button to select. You should then see the word Fastboot highlighted in red. Connect your phone and PC via USB cable. Once the connection is complete, you will see "Fastboot" change to "Fastboot USB". Open up a command prompt in ADB and type "fastboot flash boot boot.img" (without quotation marks). The kernel should then be flashed to your phone, unless you get an error message in the command terminal. Once successful you can then reboot your phone either via the command "fastboot reboot" (again without quotation marks) or by using the volume keys to select the reboot option in the bootloader menu and then pressing the power button. Once it begins to reboot, disconnect your phone from your PC.
You can also use the HTC Dumlock feature in TWRP recovery to flash a kernel while S-on. You can find information on Team Win's site in the link below.
TWRP Dumlock
Hopefully after reading all this you have a better-or at least basic-understanding of what Hboot is and what the bootloader does on this device.
Thanks to: om4 for his "Don't Panic" Guide and bigdaddy619 for motivation and technical support. You can check out his Q&A guide here. Thanks also to hasoon2000 for allowing me to include his all-in-one toolkit as part of this guide.
Enjoy
Click to expand...
Click to collapse
I have never updated my HTC Evo 4G LTE since I bought it - quite a while back when they first came out at Sprint. From doing a little looking around here, this is what I have:
HTC Evo 4G LTE
Hboot 1.12
Hardware Version 0003
Software Version 1.13.651.1 710rd
Android Version 4.0.3
HTC Sence Version 4.0
HTC SDK API level 4.20
HTC extension version 403_1_GA_8
PRI version 2.28_003
PRL version 25014
I have never updated it because from very early on I wanted to root this phone and read some place that updating it might make rooting more difficult. Reading this forum makes me think otherwise though, maybe more difficult for a day or two before someone has it figured out. If I am reading things correctly though maybe it does make the job more simple?
Given this set of information, what would you do? Knowing that I am sick and tired of the same things everyone is when they decide to pull the trigger and root. It worries me a little but you folks know more than anyone on the planet so I am asking for your advice. Right now I know just enough to be dangerous!
Howdy,
I've currently got an Evo 3D CDMA on Sprint, Revolutionary S-Off and downgraded HBoot. I'm experiencing issues when I try to run any ROM that isn't Sense-based, or any Jelly Bean ROM, I'm not sure. I've tried several of the "current" ROMs out there (Dirty Unicorns, PACMan, Wild for the Night, etc.) that have 4.2 and none of them allow me to receive SMS or MMS, or place or receive phone calls. I can apparently send SMS correctly, however, which is interesting. I've tried (and am currently using) booting up a Sense ROM just so I can update my profile and radios and all that jazz, but even after verifying my network settings are correct, once I go back to anything nonSenseical, I lose all my phone's capabilities.
I posted this over in the general forum, but nobody had anything intelligent to say. I'd really appreciate suggestions - anything helps!
I hate doing it, but bump for great justice. I know this isn't exactly the most pressing issue in the whole wide world, but I'd love an answer...
You never mentioned flashing a firmware.
It sounds like a radio issue.
Find your relevant firmware here:
http://forum.xda-developers.com/showthread.php?t=1447839
Make sure you have a ROM ready to flash and a backup of any important files before proceeding. Can't remember if it wipes phone or not.
-----------------------
Facebook: http://www.Facebook.com/d3xp2pc
Google+: http://gplus.to/d3xp2pc
d3xp2pc said:
You never mentioned flashing a firmware.
It sounds like a radio issue.
Find your relevant firmware here:
http://forum.xda-developers.com/showthread.php?t=1447839
Make sure you have a ROM ready to flash and a backup of any important files before proceeding. Can't remember if it wipes phone or not.
Click to expand...
Click to collapse
These are just RUUs, yes? I did flash several RUUs as part of this process, are these different? Also, won't these re-upgrade my HBoot?
DavisJ3608 said:
These are just RUUs, yes? I did flash several RUUs as part of this process, are these different? Also, won't these re-upgrade my HBoot?
Click to expand...
Click to collapse
Nope RUUs and radios are different.
Flashing a radio won't upgrade your Hboot.
RUUs are rom packages from HTC which can for example upgrade your version of android, hboot etc
Radios refer to the android radio layer which is responsible for data connection, voice etc. Just make sure you flash the right radio for your location etc.
If in doubt which one to flash then ask. Flashing the wrong radio can brick your device.
-----------------------
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup
-----------------------
Copy: get 20GB free permanent cloud storage. For every person you get to sign-up earn another 5GB https://copy.com?r=m3asrR
d3xp2pc said:
Nope RUUs and radios are different.
Flashing a radio won't upgrade your Hboot.
RUUs are rom packages from HTC which can for example upgrade your version of android, hboot etc
Radios refer to the android radio layer which is responsible for data connection, voice etc. Just make sure you flash the right radio for your location etc.
If in doubt which one to flash then ask. Flashing the wrong radio can brick your device.
Click to expand...
Click to collapse
Makes sense. However, when I downloaded the correct file from the link you provided, it flashed what very much appeared to be an RUU (trying to update my system, bootloader, recovery, etc.), and now my phone freezes at the HTC logo when it tries to turn on, and I don't have 4EXT installed on my device anymore. I'm currently trying to run the file through again, but it gets stuck at SYSTEM, unzipping and updating over and over again.
EDIT: All right, it now says OK on every bit except for "SYSTEM" where I see "Fail-UZ", and the 1st "TP" where it says "Bypassed."
All right, here's where I'm at now. After flashing this file to my device, my phone lost its recovery software and wouldn't boot, as well as not telling me "Locked," "Unlocked," "Relocked," or "Revolutionary" as it had before. I thought I might need to HTC unlock my device again, but flashing my unlock token didn't work, and I got an error when trying to install recovery software that the phone wouldn't allow it. I ended up flashing a 1.13 RUU simply to have something that works for now - currently when I boot into Fastboot I see HBOOT 1.40.0000 (which I had before), RADIO 0.97.10.0530, and I've got Gingerbread installed as my ROM. I'm going to try to reinstall CWM or 4EXT and put ICS back on at the very least.
EDIT: OK, when I try to flash Recovery I'm still seeing the same message "FAILED (remote: not allowed)." Apparently I've lost Root?
This is a strange one but from what your describing it seems that you have lost root.
If you can get an ICS RUU flashed and rooted you shouldn't have any problems with JB roms.
Edit: been doing some further research, these links may help.
HBOOT: http://forum.xda-developers.com/showthread.php?t=1817513
Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 10-13-12
Firmware: http://d-h.st/A4q
-----------------------
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup
-----------------------
Copy: get 20GB free permanent cloud storage. For every person you get to sign-up earn another 5GB https://copy.com?r=m3asrR
So I ran a 1.13 RUU to get myself back to a working state, re-ran Revolutionary to get my "Revolutionary" banner back, and flashed a recovery. Then I flashed the 2.95 radios, and finally cleared everything and installed a 4.2 ROM with the latest gapps. Everything seems to be working, I can apparently call and text no problem - thanks for the tip on updating my radios.
I am trying to convert a user app (cerberus anti-theft) to a system app using link2sd (also tried titanium). Worked perfect on my other phone with link2sd.
Does this require S-off? If not, any help or pointers would be appreciated.
I have android 5.0.2 I checked and I do have enough space on my system partition. I know I can flash zip file, have done that, but not what I am trying to do.
System partition is write-protected on this device, even with unlocked bootloader and root.
S-off is one way, but I don't personally suggest spending $25 on sunshine s-off just to remove system write protection; since it can be accomplished with s-on and the proper kernel mod.
What you need is the wp_mod kernel mod. I don't think the specific mod was ever posted for Lollipop. But since most custom ROMs have this kernel mod applied; you can extract boot.img from a custom ROM with same/similar software number, and flash in fastboot. Or just use a custom ROM to begin with.
Make a TWRP backup before trying to restore a modded kernel, just in case you need to revert. I've seen a couple folks fail to boot afterward, and while I'm not sure why that happened; I don't want you getting unnecessarily stuck due to a recommendation of mine.
Thank you so much for you answer. My confusion was the fact that I did not think with the HTC M8, S-on, that you could flash custom ROM's.
rockfordpi said:
My confusion was the fact that I did not think with the HTC M8, S-on, that you could flash custom ROM's.
Click to expand...
Click to collapse
That is not true. Custom ROMs flash fine with s-on. The only exception is the Verizon M8; for which indeed you cannot unlock the bootloader or flash custom ROMs unless you s-off first.
Your firmware (hboot, radio, etc.) also needs to be up-to-date (compatible with the custom ROM). Updating firmware is "easier" with s-off; but it can also be done by s-on by installing OTA or RUU update.
Yes, I have flashed the official RUU updates, I knew that could be done, it was the custom ROM issue that confused me. I think a lot of my confusion was semantics. I am slowly learning.