I did the HTC Dev Bootloader Unlock;I installed custom recovery; and I installed a rom via fastboot that had everything....... including the hacked 1.05 hboot now i keep getting boot loop and forsome reason even though the bootloader says ***UNLOCKED***" at the top; it still says S-on.... any help?
Sorry I don't know the answer but maybe you'd get a quicker and better response in the Rooting thread in the Dev section.
Did you downgrade the software if it was @ the most current OTA version?
http://forum.xda-developers.com/showthread.php?t=1401959
Sent from my HTC ThunderBolt using XDA Premium App
yeah from .9 to .5 then unlocked bootloader
smtom said:
Did you downgrade the software if it was @ the most current OTA version?
http://forum.xda-developers.com/showthread.php?t=1401959
Sent from my HTC ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
You install (flash) the super user app?
Sent from my HTC ThunderBolt using XDA Premium App
You downgraded and then you unlocked the bootloader? Had never heard of doing any phone in that order
FWIK and from my personal experience with HTCDEV unlock is that you will never have S-Off, not without an Eng-HBoot. Hacked HBoot's and other exploits can help gain it but "S-On" is in reference to a security feature in relation to the kernel and recovery partition, it was a safety measure to (in theory) keep you from bricking your phone by flashing an unstable kernel on it through recovery mode and possibly being unable to restore your previous nand by effing your recovery up. That is a simplified explanation and not all the reasons but you get the idea. I hope you can get it fixed. Best way to try to fix it is to go back and start from the beginning with just getting an Eng-HBoot or a hacked one that will allow writing to the secure kernel partition through recovery (one that will allow you to copy the NAND part of your device and it's kernel, htcdev unlock only allows nand no matter what the recovery's log says), if you can't do that then try using fastboot in a cmd window to boot a saved recovery image from the fastboot directory on your computer, that may allow you to fix your issues, good luck, hope it helps
if i get the eng hboot how am i going to flash it if its not letting me run pc'img's?
loveableterrorepic4g said:
You downgraded and then you unlocked the bootloader? Had never heard of doing any phone in that order
FWIK and from my personal experience with HTCDEV unlock is that you will never have S-Off, not without an Eng-HBoot. Hacked HBoot's and other exploits can help gain it but "S-On" is in reference to a security feature in relation to the kernel and recovery partition, it was a safety measure to (in theory) keep you from bricking your phone by flashing an unstable kernel on it through recovery mode and possibly being unable to restore your previous nand by effing your recovery up. That is a simplified explanation and not all the reasons but you get the idea. I hope you can get it fixed. Best way to try to fix it is to go back and start from the beginning with just getting an Eng-HBoot or a hacked one that will allow writing to the secure kernel partition through recovery (one that will allow you to copy the NAND part of your device and it's kernel, htcdev unlock only allows nand no matter what the recovery's log says), if you can't do that then try using fastboot in a cmd window to boot a saved recovery image from the fastboot directory on your computer, that may allow you to fix your issues, good luck, hope it helps
Click to expand...
Click to collapse
Have you tried using fastboot as a way to reboot the bootloader? I mean, my big thing is if you can get the pg img for the eng-hboot then you should be able to put it on your SD and then reboot the bootloader to let it try to boot the Pg, I know that I had a panic moment on the original EVO before they figured out a downgrade fix that I nearly bricked it, it wouldn't run the PG img check on first boot of the bootloader until I used fastboot to actually reflash the partitions on the phone (i may hate heimdall when I am working with samsungs but fastboot damn near broke me ha) the best thing to do it get a more intimate knowledge of the process and of fastboot and adb, they are great things to know how to use. Like I said I don't have a Thunderbolt but in dealing with HTC and HTCDEVs unlock tool I am pretty knowledgeable after working with it multiple times, I do know I had to downgrade my EVO (original) by manual partition flashing after I used the HTCDEV unlock tool, it unlocked the bootloader to allow me to boot what I flashed, but the kernel partition was still secure (S-On) this is what the tool, it seems that it was an attempt to cover their ass to ensure that those who don't know what their doing couldn't fully eff things up without more knowledge of the system and could reverse anything that may be unstable.
My phone has Android 2.2.2 but with HBoot 1.03, so whenever I try Revolutionary or uNRevoked, it tells me that my firmware is too new. I've been searching through the forums for a few days without much success, but if I've missed something somewhere, I apologize in advance for not spotting it sooner. Thank you for any help you can provide.
Scott
Since you upgraded to 1.03, you will have to unlock the bootloader using HTC's method: http://www.htcdev.com/bootloader/unlock-instructions (You will have to create an account on their site and log in to view the instructions.)
Where do we go from here?
I've unlocked the bootloader on my Aria, and it says that hboot is at version 1.03. How can I install a custom ROM from here (cyanogenmod)?
Adam_J_T said:
I've unlocked the bootloader on my Aria, and it says that hboot is at version 1.03. How can I install a custom ROM from here (cyanogenmod)?
Click to expand...
Click to collapse
Follow the instructions here: http://forum.xda-developers.com/showthread.php?p=14693680.
NB: Read all instructions before starting.
Getting a recovery on to an unlocked bootloader
Okay, I followed those instructions, but they posted the wrong recovery. It's for those who have just run revolutionary, and since my HBOOT was at 1.03.0000, it was impossible for me.
Here's what I did first:
1. I restored to default AT&T FroYo firmware, a download from HTC's Website.
2. I went to htcdev.com/bootloader to start the process. The Aria had to have an HBOOT upgrade from 1.02.0000 (what I was on because of the FroYo restore, although if I had known it then I would've just run revolutionary) to 1.03.0000.
*An aside: I've not had S-OFF before because for some reason I was running a totally different HBOOT. I got this phone used and that's probably why.
3. I unlocked the 1.03.0000 bootloader and realized I was screwed, because I had a) no root b) no recovery and c) no easy way to get back to the other HBOOT or load a recovery.
4. After unlocking the bootloader using HTC's methods (you have to register for a developer account, and they tell you to get three files that they provide: adb.exe, AdbWinApi.dll, and fastboot.exe) I was at stock FroYo.
5. I found a clockworkmod recovery image for the Aria on the internet. I've attached it for convenience.
6. I booted the Aria to HBOOT, plugged it in, and went to fastboot. It said "FASTBOOT USB" above my options. I already had the drivers installed, so no big deal.
7. Using the instructions in this thread, I was able to flash an alternate recovery. It's easy enough to get the .zip of the recovery off of clockworkmod's website, but I just decided not to do that for one reason or another. I didn't think about flashing a .zip, but it's easy enough. Same procedure.
8. I navigated to the directory I had all my files in from HTC's bootloader unlock process. I ran this:
fastboot flash recovery cwm-recovery.img
alternatively, you can run
fastboot flash zip <clockworkmod recovery for aria>.zip
9. I was successfully able to boot clockworkmod recovery and restore my backup of CM7.2.
I guess, if you wanted, you could flash CM7 or some other firmware with the same method through fastboot without going through recovery. I've not had much experience and I didn't want to brick my phone seeing as I don't have a backup device.
Adam_J_T said:
Okay, I followed those instructions, but they posted the wrong recovery. It's for those who have just run revolutionary, and since my HBOOT was at 1.03.0000, it was impossible for me.
Click to expand...
Click to collapse
I was referring to the instructions .
Adam_J_T said:
3. I unlocked the 1.03.0000 bootloader and realized I was screwed, because I had a) no root b) no recovery.
Click to expand...
Click to collapse
Unlocking a device's bootloader does not provide these things (it can allow you to get them though ).
Theonew said:
Unlocking a device's bootloader does not provide these things (it can allow you to get them though ).
Click to expand...
Click to collapse
I didn't expect it to, but I had no idea where to go from there; like I said previously, I'm kind of new. Thanks for all the help!
I've search around online about this but I don't know if the information is out dated.
I've looked at AlphaRev and "Revolutionary" both indicate it's not supported at this time.
I've got ROOT & a custom ROM, but S-OFF would make things so much easier.
Don't worry about s-off hboot 1.01 can't be done unless you use xtclip.
Go and look at the threads about hboot 1.02 that's the free way to unlock bootloader, this is almost the same as s-off.
sent from my legend, currently using zeubea ics beta 2.4 :-D
I think that HTC now support this with an updated boot loader.
I checked: www htcdev com / bootloader
and the HTC Legend is now listed.
Unfortunately I'll need to Unroot first.
Has anyone tried this successfully?
No you do not need to unroot your phone, look for a post by blay0, tells u exactly what to do.
sent from my legend, currently using zeubea ics beta 2.4 :-D
If this is the Quote you are referring to, it makes much more sense now.
BlaY0 said:
And guys, you don't need to complicate that much with all that flashing back and forth. It works with any custom ROM rooted or not, you just need to make the right approach. You don't even need to remove the battery. The only requirements are account on HTCdev, bootloader RUU and operational adb/fastboot environment. And NO, you will not loose the root.
So here are the steps:
do a nandroid (at least data partition)
download the bootloader RUU from HTCdev and run it
search for rom.zip in your profile directory (it was extracted from RUU after you had run it)
connect the phone to your computer
copy that rom.zip to phone's sdcard renaming it to LEGEIMG.zip (mind the case)
reboot to bootloader from command prompt (adb reboot bootloader)
current bootloader should find the LEGEIMG.zip and ask you to upgrade bootloader
after upgrade is done switch to fastboot (use up/down and power buttons)
reboot bootloader from command prompt (fastboot reboot-bootloader)
at this point you end up in new bootloader which is still locked
follow the instructions on HTCdev from Step 8 to unlock
After that you need to boot into recovery, restore data partition and you're back in the saddle.
Click to expand...
Click to collapse
Crap, I stuffed up...
My Nandroid Backup Failed (probably out of space).
now I have to re-configure my phone from scratch...
Yeah that's exactly the post I was talking about :thumbup:
I always find it a good idea to keep a copy of the nandroid on my PC too, the original is located on the SD card under /clockworkmod/backup/"backup name"
sent from my legend, currently using zeubea ics beta 2.4 :-D
If anyone finds this thread instead of the original discussion from Feb.
I successfully unlocked my bootloader which allows writing to system from a booted Rom instead of just from clockwork recovery or fastboot / adb.
key items,
you need to compete HTC's procedure excluding step 14(re locking)
if your on a custom Rom, make a android backup
follow BlaY0 instructions as a workaround of HTC's update program.
now i tested with Adaway successfully.
as for my data partition, i might have an old copy backed up but this might be a good excuse to partition my sd card so i can install more apps. I've heard 512MB would be a good size for my 4GB card.
(I have a 8GB card but my legend informs me that it has been ejected when the camera app tried to write a photo. where i had used that card in Nokia phones for years. anyone with a legend knows how physically unpractical that is without the battery being disconnected.)
ranger4740 said:
Don't worry about s-off hboot 1.01 can't be done unless you use xtclip.
Go and look at the threads about hboot 1.02 that's the free way to unlock bootloader, this is almost the same as s-off.
sent from my legend, currently using zeubea ics beta 2.4 :-D
Click to expand...
Click to collapse
What is the difference between s-off and unlocked bootloader?
Unlocked bootloader gives write access to the system partition which s-on would protect if it was mounted read only.
S-off disables the protection feature including being able to unlock your phone from your service provider ( if it happens to be).
I just needed write access to system to make updates easier (adaway, ad-hoc enabler, etc)
Sent from my GT-P7510 using XDA
brb8two said:
Unlocked bootloader gives write access to the system partition which s-on would protect if it was mounted read only.
S-off disables the protection feature including being able to unlock your phone from your service provider ( if it happens to be).
I just needed write access to system to make updates easier (adaway, ad-hoc enabler, etc)
Sent from my GT-P7510 using XDA
Click to expand...
Click to collapse
That's good news then since the reason I wanted S-OFF is so I can install stuff or remove stuff from the ROM I am currently using without manually removing and installing the apps onto a ROM from my PC then install it on the phone.
I'm now using S-ON Unlocked and AdAway didn't crash so it's working for me now.
The sole reason I wanted to root now works.
2 years wait but finally it works, I can now store my alarms, ringtones on the phone and don't have to worry about using USB diskdrive without losing the ringtones since the SD card is in use.
What guide did you use to unlock your bootloader? Was it complicated? And does having a custom rom (CM9 Beta) matter when unlocking it.
Fragda said:
What guide did you use to unlock your bootloader? Was it complicated? And does having a custom rom (CM9 Beta) matter when unlocking it.
Click to expand...
Click to collapse
First of all the rom you choose to flash has nothing to do with unlocking bootloader (not sure what you meant there). I've rooted my phone a year ago so the boot locker method wasn't available then but I can tell you the previous method was a lot more tedious and took a few days to figure it out. The boot loader guides are already posted in this forum section so check it asap
Sent from my Legend using xda premium
What guide did you use to unlock your bootloader? Was it complicated? And does having a custom rom (CM9 Beta) matter when unlocking it.
Click to expand...
Click to collapse
Custom Rom is fine, you just need to read this whole thread ( much shorter than others) for an outline of the procedure.
Check your backup is successful before completing our you may not restore your phone back to the way it was.
Sent from my GT-P7510 using XDA
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!
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0