I created a detailed set of step by step instructions for unlocking and rooting the HTC One (M8). This process will work for other HTC models as well, however, obviously I have not tested every phone, and as I have just upgraded to the M8, this process will apply directly to it. I apologize in advance if this steps on anyone's toes, as I will be including download links for specific tools needed. These steps can be found in different threads and guides, but I had not seen one that detailed the entire process from start to finish. Basically, I wrote it in layman's terms so that I was easily able to understand the process. Hopefully this will help anyone having any sort of issues. If anyone feels that this guide is inappropriate, please feel free to delete it, as this is my first "how to"
- Unlocking your AT&T HTC One (M8)
The first thing you will need to do is create a folder labeled "Android". Different guides recommend that you place it on your desktop for easy reference, however, it can actually be placed wherever you wish, as long as you feel confident in navigating to the folder via a command prompt or terminal. For my purposes, I host the folder on my D:\ drive. If you are unable to navigate folders using a command prompt or terminal, Windows 7 and Windows 8 will allow you to right click on a folder and open a command prompt that way.
Downloading the necessary drivers - Drivers can be found by following the link found here:
http://forum.xda-developers.com/showthread.php?t=2019615
CNexus was nice enough to point out that HTC Sync is a lot of bloatware and not required, but can be downloaded if you wish. I opted to download the drivers only. This is a matter of personal preference for me. If you wish to install HTC Sync, then by all means do so.
You will also need to download the ADB/Fastboot files for Windows which can be found here:
ADB/Fastboot files for Windows: https://dl.dropboxusercontent.com/u/1360819/adb-windows.zip
01. Determine if your system is 32-bit or 64-bit and follow the installation instructions for the appropriate software/drivers.
(If drivers have already been installed, then skip this installation step and start with the next).
02. Extract the contents of adb-windows.zip to your "Android" folder.
03. Open a command prompt in, or use a command prompt to browse to the "Android" folder you previously created.
04. On your HTC One (M8) go to Settings > Power, and then uncheck the "Fast Boot" option.
05. Once step 4 is completed, switch your device OFF.
06. Now that the device is powered down, Press the Volume Down and the Power buttons simultaneously to boot the HTC One (M8) into "HBOOT" mode.
07. Using the Volume buttons, navigate to the "Fastboot" option and select it using the Power button.
08. Connect your HTC One (M8) to your PC.
09. On the command prompt you previously opened in step 2, type in the following command "fastboot devices" (do not include the quotation marks).
**At this point, if all steps have been followed properly, you should receive a message in the command window similar to the following:
C:\Users\XXX\Desktop\Android>fastboot devices 011aa0a1a01aaaa1 fastboot
10. Now we will need to go to the HTC Developer website to get an "Identifier Token" before the bootloader can be unlocked. The URL to the HTC Developer website is www.htcdev.com. If you do not already have an account, you will need to register and sign in before you're able to proceed.
11. Once your account has been created and you are logged in, click on the "Development Center" link at the top of the screen.
12. Under the "Unlock Bootloader" option in the center of the page, click on "Get Started".
13. Next, under "Supported Devices" click on "Select your Device" and find the HTC One (M8) and then select "Begin Unlock Bootloader". (This process works for several other HTC devices as well).
14. Accept all warnings and agreements and keep proceeding forward by clicking the "Next" button. When you reach step 8 on the site, enter the following command in the command prompt:
"fastboot oem get_identifier_token" (without the quotation marks).
15. Copy the message seen in the command prompt to notepad or your clipboard.
16. ONLY KEEP THE RANDOM SERIES OF ALPHANUMERICS FROM THE OUTPUT YOU JUST COPIED. Remove everything else such as <<<, (bootloader), Info, or any other piece of text. DO NOT EDIT THE IDENTIFIER TOKEN START OR END LINE!!!
Example:
<<<< Identifier Token Start >>>>
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
<<<<< Identifier Token End >>>>>
17. Paste the edited output inside the "My Device Identifier Token" box on the HTC Developer website and press "Submit". Once you have submitted the identifier token, you will receive your unlock code binary file via email.
18. Upon receiving the "unlock_code.bin" file from HTC (this file is specific to your phone), transfer the file to your "Android" folder that was previously created at the start of this document.
19. With your command prompt still open, enter the following command:
"fastboot flash unlocktoken Unlock_code.bin" (without the quotation marks).
20. After entering this command, a message should appear on your HTC One (M8) screen asking if you really want to unlock the bootloader. Use the Volume key to highlight the YES option and press the Power button to select it.
21. At this point your phone's bootloader will be unlocked and it will restart automatically. The first boot could potentially take some time. If this happens, it is normal. Be patient and wait for the reboot.
22. After your device reboots, any previous settings that you may have saved will be lost with the unlocking of the bootloader. Be prepared for this, as you will need to redo them all. If it is your intention to unlock your bootloader, I highly suggest doing it on a fresh ROM install, so you only have to deal with it once. This means that "fastboot" will be re-enabled in the power settings. If you wish to continue to rooting your device, you will need to go to Settings > Power and un-check the "fastboot" option before proceeding.
- ROOTING YOUR DEVICE
The first thing you will need to do to root your device is to download the following files
TWRP Recovery for the AT&T (M8): http://androidfiles.org/getdownload.php?file=M8/Recoveries/openrecovery-twrp-2.7.0.4-m8_ul_ca.img
SuperSU: download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
1. Once downloaded it is advised to rename the TWRP Recovery file to either "twrp.img" or "m8recovery.img". (I renamed mine to m8recovery).
2. Once renamed, copy TWRP image file into your previously created "Android" folder.
3. Open a command prompt and browse to the same "Android" folder where you placed the adb/fastboot and TWRP Recovery files.
4. Make sure your HTC One (M8) is powered off. Boot the phone into fastboot mode by pressing the Volume down and Power buttons at the same time. Once booted, select "fastboot" by pressing the Power button.
5. Connect the HTC One (M8) to your PC.
6. Enter "fastboot devices" (without the quotation marks) in the command prompt to verify that the device has been detected by your PC. If the device is connected you should receive a message similar to the following:
C:\Users\XXX\Desktop\Android>fastbootdevices
010AA1A0A10AAAA1 fastboot
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
8. After TWRP Recovery has been successfully flashed, the device needs to be restarted manually. To do so, enter the command "fastboot reboot" (without the quotation marks).
9. Upon reboot, transfer the SuperSU zip file to the root directory of your HTC One (M8) via your PC.
10. Turn off your HTC One (M8) and reboot into Bootloader mode by holding the Volume Down and the Power button at the same time.
11. Navigate to the "Recovery" option and select it by pressing the power button. (After following this step, TWRP will load on the device rather than the stock HTC Recovery).
12. Now that TWRP Recovery has loaded, tap the "Install" button and select the UPDATE-SuperSU-v1.94.zip file you previously downloaded.
13. One the SuperSU zip file has been flashed, select the "Reboot System" option to reboot your device.
14. After the device restarts, you have successfully rooted your HTC One (M8). From here, you are now free to install custom Kernels, ROMs, and other mods as you see fit.
I hope this helps everyone out. I am not a developer, nor do I pretend to be. Please give thanks to the people that made all rooting and modding our phones possible
Special thanks to gdnewsevry1 for recognizing a missed step and command.
Very nicely written and well put together. Thank you for taking the time to share this.
Scott
Sent from my HTC One_M8 using XDA Free mobile app
This guide is very well made!
I did figure out that you can root the phone without unlocking the boot loader (with Towelroot modstrings), SOff that way, then just follow your instructions to get TWRP on. You might want to add that in to, for people who don't want to use HTCDev.
suggestion
Thanks for your guide. I just used it and it helped a ton. I would suggest the change and addition below based on my experience.
liquidaluminum said:
TWRP Recovery for the AT&T (M8)
[...]
7. Once verified, type "fastboot flash m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
Click to expand...
Click to collapse
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
liquidaluminum said:
9. Upon reboot, transfer the SuperSU zip file to the root directory of your HTC One (M8) via your PC.
10. Turn off your HTC One (M8) and reboot into Bootloader mode by holding the Volume Down and the Power button at the same time.
Click to expand...
Click to collapse
Insert: 9a. Turn off fastboot in settings.
gdnewsevry1 said:
Thanks for your guide. I just used it and it helped a ton. I would suggest the change and addition below based on my experience.
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
Insert: 9a. Turn off fastboot in settings.
Click to expand...
Click to collapse
Good observation. Thank you. I added a line item numbered 22 under the unlocking portion in substitution of 9a. I did it this way, because all settings are reset unlocking the bootloader. For those that are going to proceed to the rooting instructions, I thought it might be smart to go on and take care of disabling the fastboot options right off the bat, so it's no longer a concern.
You were 100% correct about adding the recovery line. I must have missed it while typing this up. Good looking out!
This is almost certainly the best guide I have seen on XDA to unlock/root a device.
I've added it to my Index thread under "Unlock Bootloader, ROOT, S-Off": http://forum.xda-developers.com/showthread.php?p=52653939
Also, one suggestion is to add an alternate section/branch to flash straight to a custom ROM (rather than stay stock and root).
redpoint73 said:
This is almost certainly the best guide I have seen on XDA to unlock/root a device.
I've added it to my Index thread under "Unlock Bootloader, ROOT, S-Off": http://forum.xda-developers.com/showthread.php?p=52653939
Also, one suggestion is to add an alternate section/branch to flash straight to a custom ROM (rather than stay stock and root).
Click to expand...
Click to collapse
I'm definitely thinking about doing that very thing. The only thing that prevented me originally is because of the way I have to use my phone. I've never owned an HTC device before, so I'm not sure if the same issue would exist, but in regards to ROM swapping, when I was running Samsung devices, I found a proprietary problem with the devices themselves that prevented me from running custom ROMs.
I have an Appradio 2 in my car that relies on the MHL output to mirror my device to my dash. When using custom ROMs of any kind (that I tried), I MHL never worked. I addressed the issue with a couple of developers, I was told that because MHL isn't used by many people, support for it isn't focused on. Since that has seemed to hold true for any of the ROMs that I've tried, I've always been limited to rooted stock ROMs. Hence my not including the suggested addition.
I see, it makes sense to write a guide for only what you know about.
I wouldn't necessarily avoid custom ROMs just for the MHL issue. There are a good number of great custom ROMs that are built on the "stock" Sense base, but with varying degrees of optimizations and cool customization options. Its just a gut feel, but with many of these ROMs I would think the MHL function would work fine. In any case, just make a nandroid backup of your current setup (which I highly recommend when flashing just about anything) and if you don't like the current ROM, its easy to revert.
Missing file
Nice writeup, thanks.
FYI, the M8 TWRP link is dead.
I'll see if I can find another. If not, I'll host it somewhere.
About to do this when I get home...
just wanted to know if anything has changed since the last time this was updated. Appreciate the time put into this guide!
Thank you so much. Directions and attatchments worked like a charm. I found another image to use as a recovery since your link was dead. :good:
Great write-up. I'm going to run through this with my new M8. Just one question - can Philz recovery be used with the HTC?
CanuckinPA said:
Just one question - can Philz recovery be used with the HTC?
Click to expand...
Click to collapse
Yes.
If you ever have time..perhaps you should write up a detailed thread about RUUs. There are a few good ones, but most of them written are from guys either stuck on HTC devices or have used android for years. It might knock out the traffic from unnecessary comments on Dev threads. Perhaps letting others know that you can flash RUUs without a computer simply by renaming to 0P6BIMG. AFAIK you can not change CID without access to a computer. I've tried finding out how I can, but I haven't found out anything. I wanted to do a straight GPE conversion considering I never use SENSE based Roms. A few weeks ago my computer crashed, and I figured that idea was out the window til wonder_never_cease told me to rename the file to 0P6BIMG, but to receive OTA updates I'd have to change the CID from SUPERcid to the google gpe CID
---------- Post added at 05:21 AM ---------- Previous post was at 05:20 AM ----------
Isn't philz recovery discontinued ?
hey, thanks for the detailed guide!
do your steps include s-off?
moreover, what is s-off (I am very new to m8) and is it necessary after rooting? what does it provide?
question #2, will I be able to get OTA updates (if I replace TWRP with stock recovery) ?
thanks in advance!
ksoze11 said:
do your steps include s-off?
moreover, what is s-off (I am very new to m8) and is it necessary after rooting? what does it provide?
question #2, will I be able to get OTA updates (if I replace TWRP with stock recovery) ?
Click to expand...
Click to collapse
1) Guide doesn't include s-off. Look for threads/guides on firewater or (more likely) sunshine s-off methods.
S-off is a HTC-specific security flag that means "all security off". S-off isn't required for most root functions, flashing ROMs, etc. Its only needed to flash some protected partitions (hboot, radio), SIM unlock, and a few other things.
S-off also means that things like device check and version check are bypassed. This can sometimes give you more recovery options (for instance "downgrade" by RUU which is not possible with S-on). But it also makes it possible for your to flash mods meant for other devices and possibly brick the phone. So care needs to be taken when s-off, and it shouldn't be taken lightly.
2) You need to be on the stock ROM (with no system files modified) and stock recovery to receive and install OTA. If you have that, it will OTA fine. But you will need to root again afterwards.
Help -- Phone Keeps Rebooting
I went through the entire procedure to unlock and root and all was fine for a week or so until earlier this week.
I'm not sure what I did prior to the problem, but suddenly the phone started rebooting every minute or so. I shut the phone down for a couple of hours, but when I restarted it the rebooting continued.
I booted into Philz recovery and did a restore to stock, reinstalled all of my apps and all was well until this morning. I have Link2SD and after installing Handcent I opened the Link2SD app. Then the reboot returned.
Is there a fix for this issue, or do I have to go back to stock again?
BTW - I haven't flashed a custom ROM yet, still running the stock ATT HTC ROM
CanuckinPA said:
I went through the entire procedure to unlock and root and all was fine for a week or so until earlier this week.
I'm not sure what I did prior to the problem, but suddenly the phone started rebooting every minute or so. I shut the phone down for a couple of hours, but when I restarted it the rebooting continued.
I booted into Philz recovery and did a restore to stock, reinstalled all of my apps and all was well until this morning. I have Link2SD and after installing Handcent I opened the Link2SD app. Then the reboot returned.
Is there a fix for this issue, or do I have to go back to stock again?
BTW - I haven't flashed a custom ROM yet, still running the stock ATT HTC ROM
Click to expand...
Click to collapse
If the phone was working fine for a week, then it must be due to some more recent change made to the phone or app your installed. Did you try to uninstall Link2SD?
Related
Well Guys,
I finally got my hands on my dream phone, the N1. Hope this guide helps some n00bs out there like me.
Here is how to unlock the bootloader, root and install clockworkmod on the baby.
DISCLAIMER
I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE AND THIS WILL VOID YOUR WARRANTY AND ALSO WIPE ALL YOUR DATA TO FACTORY SETTINGS.
CREDITS
TO ALL THE VARIOUS WEBSITES WHERE I READ ALL THE INFORMATION MENTIONED BELOW. NONE OF THE BELOW IS MY WORK AND I TAKE NO CREDIT FOR IT.
HATS OFF
To all the developers who made this possible. superboot is work of Paul from Modaco, clockworkmod is work of Koush.
Step - 001
Install Android SDK from here.
Step - 002
Connect your phone to the PC using the data cable provided. If the drivers are installed successfully well and good, else download the one's from here and point windows to the folder where you extract the above drivers.
Step - 003
Open
Code:
settings - about
and note down the build number
Step - 004
Download Superboot from here depending on the build number noted above.Extract the archive to a folder.
Step - 005
Turn off the phone, boot into bootloader mode [press track ball and after that press the power button]
The phone will go into download mode. Connect USB Cable.
Navigate to the folder of superboot above using Windows command prompt.
Issue the following command
Code:
fastboot-windows devices
If this line does not return anything, do not continue: Your computer does not detect your Nexus.
Unlocking the Bootloader(this will void the warranty and also do a factory reset)
Code:
fastboot-windows oem unlock
The phone will display a warning, use the volume up down button to toggle between yes and no, we need to select yes, once yes is selected press the power button to confirm your decision.
The phone will reboot.
if you get the following error
FAILED <command write failed <Too many links>> error
ignore it and try giving the oem unlock command again and it should say bootloader already unlocked. Do not proceed until your bootloader has been unlocked.
Rooting
Boot the phone into bootloader mode. naviagte to the "superboot" folder in windows explorer. Double click the file "install-superboot-windows.bat" and viola you are rooted.
Installing recovery (I used clockworkmod, you can also use AmonRA)
Download the latest CWM from here, download the .img file and once downloaded check the md5 with the one on the link above. (passion is the name for Nexus One).
Put the above downloaded .img file in the 'superboot' folder and rename it to a simple name say "cwm.zip" (without the quotes)
Boot the phone into bootloader mode again.
Navigate to the superboot folder from Windows command prompt.
Issue the following command
Code:
fastboot-windows flash recovery cwm.img
You are now rooted and have installed ClockworkMod recovery.
I would advice you to flash a new custom ROM right away, do not boot into the stock ROM as it would end up breaking CWM. In case you want to be on stock ROM and still have recovery you need to do the following.
Boot into the stock ROM.
Connect USB.
Navigate to the superboot folder.
Give the following commands.
Code:
adb-windows shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
Now flash CWM again as described in the step above.
How to boot into CWM when phone is switched off.
press the volume power down button and while it is pressed press the power button.
The phone will boot into a white screen, wait for some time (7-8) seconds, some checks will take place, once those checks are complete use the volume buttons to go to recovery option and use the power button to select and you are into ClockworkMod.
Moderators Please move this to correct section if I posted in the wrong section.
Excellent post! Thanks for taking the time to put it together, i could've done with this a few months ago when i first got my n1... Nice one
tina333 said:
Excellent post! Thanks for taking the time to put it together, i could've done with this a few months ago when i first got my n1... Nice one
Click to expand...
Click to collapse
thanks a lot , have been waiting all day for a feedback and finally I got one .
Good one ..
siddharthsai said:
Good one ..
Click to expand...
Click to collapse
Thanks man .. it's an honor to get a nod from you ...
i guess unlocking the bootloader is very conventional..
no one unlocks the bootloader now....
there are many direct rooting methods available including one click root , universal androot, superoneclick etc, where we can root and also unroot afterwards thus the warranty is not void..
but in unlocking bootloader warranty is void and is also not very safe method .
while other methods are extremely safe, requires only one click...
you should have researched before unlocking the bootloader.
though you are from india like me so warranty void is no criteria as nexus one is not sold here officialy.
abhi0n0nakul said:
i guess unlocking the bootloader is very conventional..
no one unlocks the bootloader now....
there are many direct rooting methods available including one click root , universal androot, superoneclick etc, where we can root and also unroot afterwards thus the warranty is not void..
Click to expand...
Click to collapse
Precisely.
Although I never heard of HTC denying warranty(with unlocked bootloader), unlocking the bootloader is not necessary.
Just start with Rooting(super one click, or z4root), install recovery with adb or android shell, and go from there.
abhi0n0nakul said:
i guess unlocking the bootloader is very conventional..
no one unlocks the bootloader now....
there are many direct rooting methods available including one click root , universal androot, superoneclick etc, where we can root and also unroot afterwards thus the warranty is not void..
but in unlocking bootloader warranty is void and is also not very safe method .
while other methods are extremely safe, requires only one click...
you should have researched before unlocking the bootloader.
though you are from india like me so warranty void is no criteria as nexus one is not sold here officialy.
Click to expand...
Click to collapse
I guess it depends what you want your device to ultimately be capable of doing.... Being a person who has also researched... I personally needed to unlock the bootloader to flash a custom rom, although rooting is a vital aspect when customising devices, if you want to maximise the potential then sometimes voiding warrantee's is to be expected (note there are also ways and means of reverting most mods back to factory standard if needed )
Each to their own
Well it was my personal choice to unlock the bootloader, I wanted to do it just for the heck of doing it
The tutorial was made so as to help others and that is why "the void warranty" thing was mentioned in bold and red.
I was aware of methods which will root and not void the warranty but I wanted to "void the warranty" as we do not have it in India and yes the main reason was custom ROMS, my first phone the Samsung Spica (still own it) ran stock ROM for only a month and the N1 ran a stock for only 12 hours ...
tina333 said:
I guess it depends what you want your device to ultimately be capable of doing.... Being a person who has also researched... I personally needed to unlock the bootloader to flash a custom rom, although rooting is a vital aspect when customising devices, if you want to maximise the potential then sometimes voiding warrantee's is to be expected (note there are also ways and means of reverting most mods back to factory standard if needed )
Each to their own
Click to expand...
Click to collapse
can you tell me what things the rooted bootloader unlocked device can do that rooted bootloader locked device cant????
munchy_cool said:
Thanks man .. it's an honor to get a nod from you ...
Click to expand...
Click to collapse
LOL, I'm just like everyone else... anyways hard work should always be appreciated.
abhi0n0nakul said:
can you tell me what things the rooted bootloader unlocked device can do that rooted bootloader locked device cant????
Click to expand...
Click to collapse
well, for one thing... the methods to soft-root exploit software issues which are quite often patched...
Here is a thread showing how to LOCK the bootloader on n1 again.
http://forum.xda-developers.com/showthread.php?t=934965
[WIP] Nexus One - S-OFF (locking bootloader again)
Thanks, Please edit the link do download the CWM recovery by using this latest link from the Cyanogenmod Servers
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.0.5-passion.img
Click to expand...
Click to collapse
Or By now linking this guide to the Nexus One Cyanogenmod Wiki where a full and updated tutorial is posted.
Thanks
i would like to know what everything means in htc's bootloader, whats fastboot? and whats does hboot mean, and what does everything thing in the bootloader mean and do? and why do we rename roms to PG05IMG... is that htc's way, like we like to use update.zip in custom recoverys.. thanks
anyone?????????
marcogiudice said:
anyone?????????
Click to expand...
Click to collapse
You're probably not getting a reply because these types of questions have been answered numerous times over the years - and people would probably rather ignore it than be a jerk by saying "ever heard of the search button??". Anyway... jsut Google "ADB for noobs", or "beginners guide to ADB" and you will probably find what you are looking for.
Lipmonger said:
You're probably not getting a reply because these types of questions have been answered numerous times over the years - and people would probably rather ignore it than be a jerk by saying "ever heard of the search button??". Anyway... jsut Google "ADB for noobs", or "beginners guide to ADB" and you will probably find what you are looking for.
Click to expand...
Click to collapse
i see what your saying i did google it before i posted and didnt find what i was looking for, i got adb setup correctly and have been using for it for 16 months but coming across htc bootloader it way different then motos or samsung's with some things in there that would help all the new tb users and should be posted and stickied or in the wiki thread
ok i found half my answer... this for other acquiring minds like me
Here's some (hopefully useful) information about the bootloader:
What's HBOOT?
It's immediately loaded when the phone is switched on. It's mostly responsible for checking and initialising the hardware and starting the phone's software, for flashing official software releases (RUUs via Fastboot), as well as a few other things. In some ways it's comparable to the BIOS on a PC.
How do I root HBOOT?
You can't, it makes no sense. It's a bootloader, not Android. It's like trying to play a DVD on your kettle.
What does upgrading HBOOT do?
It may add extra hardware support for new phones (e.g. SLCD displays) and may fix a few bugs. HTC doesn't release information about it.
What does downgrading HBOOT do?
The opposite. So, if you flash an SLCD phone with an old version of HBOOT that doesn't have the support, the screen won't work.
But rooting depends on HBOOT version?
It doesn't.
Why does upgrading HBOOT remove root?
It doesn't. When you flash an official update your ROM is replaced with an official one, which is why root is lost.
How do I change HBOOT version?
By installing an official RUU/update. There's no other way - the bootloader is protected by the phone's hardware security because a corrupt bootloader means a bricked phone with no way to recover. RUUs contain a version of the bootloader, which is automatically flashed.
Why do I need to downgrade HBOOT to root 0.92?
You don't. You had to downgrade Android because unrevoked3 couldn't root froyo. The new release can, so it works.
Why all the talk about HBOOT then?
Because it is confused with software release, which is the important part. An RUU won't work if the installed software is a higher version (e.g. 1.20.x won't work if you have 1.21.x), and people have mistaken that check for HBOOT version.
What about the xda 0.92 to 0.80 downgrade? It runs on froyo.
It's an engineering/test release from HTC that was leaked. It fakes its software version to 2.09.405.8 so it will run on froyo and downgrade the ROM, so long as you're not on a higher release than that. The process has nothing to do with HBOOT, but it does downgrade the bootloader to 0.80 as a side effect - and results in a dead screen on SLCD phones. It's generally a bad idea to use this hack.
Why would any of this matter?
Because instructions based only on HBOOT version are not reliable. They may not work, or may cause your phone to stop working.
OK NOW FOR FASTBOOT........
Fastboot
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images. It is disabled in the production G1 devices since USB support is disabled in the bootloader[1]. This can be changed if you get root on the device. See also [2]
Fastboot prerequisites
To be able to use fastboot, you need to be running either an ADP1 or the Engineering Bootloader on your G1.
If you are developing on a linux host, you may need to tweak UDEV to recognize the phone in fastboot mode. You may already have done this to get the phone recognized in Eclipse, but you need to do it again for fastboot, since fastboot uses a different device ID: 0bb4:0c01. The warning sign is that fastboot says "< waiting for device >" forever, even when you have the "FASTBOOT" message on the phone; if this happens, try adding the device ID 0bb4:0c01 to your UDEV configuration for Android.
For Opensuse 11.1, the following config file, in /etc/udev/rules.d/11-android.rules, seems to work:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666", OWNER="mylogname"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", MODE="0666", OWNER="mylogname"
NOTE: change "mylogname" to your Linux login ID. Also note that the product ID bit is optional (probably easier to leave it out), and you need to change "0bb4" to the vendor ID for your phone if it isn't made by HTC (whose vendor ID is 0bb4). You can find the vendor id using 'lsusb'. An alternative to this is just to run fastboot as root, using sudo.
Starting Fastboot
On the G1: To start fastboot, first get to the bootloader: turn off your phone and hold down the "camera" button while powering it back on. You will see a white screen with skateboarding bugdroids. If you just see the normal multicolored bootloader screen, you need to get the device side of fastboot working as noted above. Plug your phone into the usb and if you see "serial0" hit the "back" key. You should now see "fastboot" on the screen.
On the Samsung Galaxy: power down the phone, then long-press the two Call buttons. Beware that fastboot mode will continue to reboot the phone after ~30 seconds of inactivity.
Fastboot Binary
To make use of fastboot, you also need the fastboot program compiled for your host computer. If you have already built Android, you will have this file already. Its location should be:
<android source location>/out/host/{os}_{arch}/bin/fastboot
If you do not have fastboot built, you can either compile the Android source or try DarkriftX's precompiled fastboot (compiled on kubuntu x86)
Fastboot Commands
Here are the commands you can run on your host after fastboot has been started on a device connected via USB. This is a paste directly from the fastboot binary's "--help" command:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Forcing fastboot to load on every boot
Developers who are creating new images to try out very often can remove their boot and recovery images which will force the phone to enter bootloader mode every time you boot. To fix this, you would reflash the boot and recovery images back allowing the phone to boot normally.
$ fastboot erase boot
$ fastboot erase recovery
NOW,
SO WHY DO WE CHANGE RUU.'S TO PG05IMG??????????
AND THE COUPLE OF OTHER OPTIONS DO IN BOOTLOADER?
THANK U!
I'm guessing it's because that's what it looks for. Kind of like the apply update.zip on stock android recovery. If you notice when you flash, it goes through PG05IMG.X with various file extensions trying to find it and gives a not found error before it finally gets to .zip
PJnc284 said:
I'm guessing it's because that's what it looks for. Kind of like the apply update.zip on stock android recovery. If you notice when you flash, it goes through PG05IMG.X with various file extensions trying to find it and gives a not found error before it finally gets to .zip
Click to expand...
Click to collapse
right, so ok then i was guessing right its like update.zip for stock recovery
thanks
Somewhat of an explanation of our signature checking bootloader can be found here
http://forum.xda-developers.com/showthread.php?t=1008210
I am rooted, have TWRP, am running stock sense 6 with 4.4.2, s-on. I want to completely get rid of anything and everything including the root. Is there a foolproof, simple way to do that? Just a heads up I am not very good at any of this, installing an RUU or anything of the like is way out of my level. All im asking is a simple breakdown of what I have to do. I also have a Mac, so some options seem to be crossed out for me.
RUU is not above your head. Especially if you unlocked the bootloader, rooted, etc. yourself. Even if not, the RUU is a tool issued by HTC for "regular" folks (with no knowledge whatsoever of modding phones) to recover their devices in various situations.
RUU is easy:
- Relock the bootloader with the command: fastboot oem lock
- Connect the phone to PC
- Run the RUU, and the RUU program leads you through the rest.
I know you said you have a Mac, but surely you have a friend or family member with a PC that you can use for a half hour.
Honestly, IMO opinion its still easier than returning to stock by other methods, which would require:
- Finding the right stock ROM or stock nandroid for your firmware number
- Putting the stock ROM on the phone and flash with TWRP
- Find the right stock recovery for your stock ROM
- Flash using fastboot
- Relock the bootloader (depending on how "full stock" you want to go)
- Additionally, if you intend to update to current OS (Lollipop) you then need to install 4.4.4 and 5.0 OTAs to get fully current. RUU will update everything at one time.
With the above method, finding the right files is the potential pitfall; and one where many folks have trouble. So in addition to just having more steps, there is also much more potential for having problems with those steps (making the process even more time consuming and stressful).
On another note, you haven't given any background why you want to return to "stock". Once a phone is rooted, I seldom recommend going back to stock, with the exceptions of:
- You are selling or giving the phone away (you should still tell the buyer that the phone was previously modded)
- The phone was rooted by a previous owner, you have no intent to use such features, and just want to return to a fully stock condition
- You are suffering some issue that you think a return to stock will resolve (RUU is better in this case)
redpoint73 said:
RUU is not above your head. Especially if you unlocked the bootloader, rooted, etc. yourself. Even if not, the RUU is a tool issued by HTC for "regular" folks (with no knowledge whatsoever of modding phones) to recover their devices in various situations.
RUU is easy:
- Relock the bootloader with the command: fastboot oem lock
- Connect the phone to PC
- Run the RUU, and the RUU program leads you through the rest.
I know you said you have a Mac, but surely you have a friend or family member with a PC that you can use for a half hour.
Honestly, IMO opinion its still easier than returning to stock by other methods, which would require:
- Finding the right stock ROM or stock nandroid for your firmware number
- Putting the stock ROM on the phone and flash with TWRP
- Find the right stock recovery for your stock ROM
- Flash using fastboot
- Relock the bootloader (depending on how "full stock" you want to go)
- Additionally, if you intend to update to current OS (Lollipop) you then need to install 4.4.4 and 5.0 OTAs to get fully current. RUU will update everything at one time.
With the above method, finding the right files is the potential pitfall; and one where many folks have trouble. So in addition to just having more steps, there is also much more potential for having problems with those steps (making the process even more time consuming and stressful).
On another note, you haven't given any background why you want to return to "stock". Once a phone is rooted, I seldom recommend going back to stock, with the exceptions of:
- You are selling or giving the phone away (you should still tell the buyer that the phone was previously modded)
- The phone was rooted by a previous owner, you have no intent to use such features, and just want to return to a fully stock condition
- You are suffering some issue that you think a return to stock will resolve (RUU is better in this case)
Click to expand...
Click to collapse
What you said about how infuriating it is finding the right files and all is what motivated me to want to start anew, maybe I will keep root then. I read up some guides online and have a better understanding of how RUUs work now. I only have one question left, how would I input the command to relock the bootloader? I understand you have to go into the command prompt window, but do i just type it in? I thought I had to navigate to my phone through it somehow. Hopefully that made sense in some way.
xeamless said:
I only have one question left, how would I input the command to relock the bootloader? I understand you have to go into the command prompt window, but do i just type it in? I thought I had to navigate to my phone through it somehow. Hopefully that made sense in some way.
Click to expand...
Click to collapse
You still haven't provided any background on whether you rooted the phone yourself. If you did, you should already have fastboot setup on your computer; as you would have needed it to issue the bootloader unlock command. So open the command prompt, than you need to change directory to whatever folder your fastboot files (fastboot.exe if on a PC) are located. Then simply type the command.
If you don't have fastboot setup on your computer, that is a different story, and you would need to do so (can give details if you indicate that is the case).
redpoint73 said:
You still haven't provided any background on whether you rooted the phone yourself. If you did, you should already have fastboot setup on your computer; as you would have needed it to issue the bootloader unlock command. So open the command prompt, than you need to change directory to whatever folder your fastboot files (fastboot.exe if on a PC) are located. Then simply type the command.
If you don't have fastboot setup on your computer, that is a different story, and you would need to do so (can give details if you indicate that is the case).
Click to expand...
Click to collapse
So I followed everything you said and it all worked out! Thanks
xeamless said:
So I followed everything you said and it all worked out! Thanks
Click to expand...
Click to collapse
Sweet, glad it worked out for you. You're quite welcome.
I am a total newbie to Android modifications, and tried to find a way of specifying custom notifications on my HTC One Max. I have later found the application Ringdroid that fixes everything that I needed, but before I did that, I believed that I had to root the phone to achieve this. So, I read a lot of stuff, downloaded a lot of files, messed with adb, clockworkmod, rumrunner etc. without really knowing what I was doing, and in the end gave up, since it didn't look like I managed to root the phone properly after all. But, anyway, I understood that something had changed, since a couple of applications were missing. Anyway, the phone has worked fine since then, until recently, when I got a notice that software update 4.13.401.7, containing Android 5.0 Lollipop, and various other stuff, was ready for installation. So, I downloaded the update, and told it to install. The phone reboots, and then I get the following message:
CWM-based Recovery v6.0.5.1
E: Invalid command argument
E: Invalid command argument
Finding update package...
E: unknown volume for path [INTERNALSDCARD:0/Do
wnload/OTA_T6_UL_L50_SENSE60_MR_HTC_Europe_4.1
3.401.7-3.23.401.1_release_4360116ezjvoz69qm8r
zky.zip]
E: Can't mount INTERNALSDCARD:0/Download/OTA_T6
_UL_L50_SENSE60_MR_HTC_Eutope_4.13.401.7-3.23.
401.1_release_4360116ezjvoz69qm8rzky.zip
Installation aborted.
Rebooting...
Is there a way of letting me a) reset my phone to the default settings, thus allowing me to perform the Lollipop upgrade? (the preferred solution), or b), perform this upgrade without resetting it?
If not s-off,locked mudt flash stock recovery,must relock boot loader imo unroot and then take the update
[email protected] said:
I am a total newbie to Android modifications, and tried to find a way of specifying custom notifications on my HTC One Max. I have later found the application Ringdroid that fixes everything that I needed, but before I did that, I believed that I had to root the phone to achieve this. So, I read a lot of stuff, downloaded a lot of files, messed with adb, clockworkmod, rumrunner etc. without really knowing what I was doing, and in the end gave up, since it didn't look like I managed to root the phone properly after all. But, anyway, I understood that something had changed, since a couple of applications were missing. Anyway, the phone has worked fine since then, until recently, when I got a notice that software update 4.13.401.7, containing Android 5.0 Lollipop, and various other stuff, was ready for installation. So, I downloaded the update, and told it to install. The phone reboots, and then I get the following message:
CWM-based Recovery v6.0.5.1
E: Invalid command argument
E: Invalid command argument
Finding update package...
E: unknown volume for path [INTERNALSDCARD:0/Do
wnload/OTA_T6_UL_L50_SENSE60_MR_HTC_Europe_4.1
3.401.7-3.23.401.1_release_4360116ezjvoz69qm8r
zky.zip]
E: Can't mount INTERNALSDCARD:0/Download/OTA_T6
_UL_L50_SENSE60_MR_HTC_Eutope_4.13.401.7-3.23.
401.1_release_4360116ezjvoz69qm8rzky.zip
Installation aborted.
Rebooting...
Is there a way of letting me a) reset my phone to the default settings, thus allowing me to perform the Lollipop upgrade? (the preferred solution), or b), perform this upgrade without resetting it?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
If not s-off,locked mudt flash stock recovery,must relock boot loader imo unroot and then take the update
Click to expand...
Click to collapse
Thanks a lot, Wonders_Never_Cease. However, as stated in my original post, I'm a total newbie here, so I need detailed instructions on how to "flash stock recovery", "relock boot loader" etc. If you (or anyone else) could be so kind as to provide me with detailed step-by-step instrucions, I would be eternally grateful.
Sigurd
Command would be the same as when flashed clockwork mod recovery
Download stock recovery for your build that's on the phone now
Reboot device into bootloader
Open command prompt
CD to where adb/fastboot is located
Copy downloaded stock recovery to that location
Connect phone to computer
Type into command prompt window "fastboot flash (recovery name)" minus parentheses)
Once it finishes type in command prompt "fastboot reboot-bootloader" (minus parentheses)
Once device reboots into bootloader
Type into command prompt "fastboot oem lock" (minus parentheses) this will relock the bootloader
Should be able to take ota without incident
Now you will probably have to redo the unlock process via htc site, or you may be able to use original bin you unlocked device to begin with, unsure...
hopefully I covered all steps been awhile
Good luck
WNC
[email protected] said:
Thanks a lot, Wonders_Never_Cease. However, as stated in my original post, I'm a total newbie here, so I need detailed instructions on how to "flash stock recovery", "relock boot loader" etc. If you (or anyone else) could be so kind as to provide me with detailed step-by-step instrucions, I would be eternally grateful.
Sigurd
Click to expand...
Click to collapse
Is there a way to downgrade the stock ROM to use rumrunner? I foolishly installed the latest ota and rumrunner won't work. $25 for sunshine seems a bit steep.
Hi
help me how to install .bin file
Standin.Weed said:
Hi
help me how to install .bin file
Click to expand...
Click to collapse
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Davey126 said:
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Click to expand...
Click to collapse
I have the kindle fire hdx 7 13.3.2.4 and I also have file:
mod-update-kindle-thor-13.3.2.8_user_713328020.bin
I do not know how to manually install this file
these words are translated by google because I have bad english
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Cl4ncy said:
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Click to expand...
Click to collapse
teach me how to install 13.3.1.0 install TWRP, update the bootloader to 3.2.3.2
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelihood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Cl4ncy said:
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelyhood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade Images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Click to expand...
Click to collapse
I do not know to do this step:
cuberHDX from here: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands):
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
this is not have to be?
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Cl4ncy said:
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Click to expand...
Click to collapse
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Standin.Weed said:
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Click to expand...
Click to collapse
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Cl4ncy said:
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Click to expand...
Click to collapse
tks you so much.
I did all :laugh:
Standin.Weed said:
tks you so much.
I did all :laugh:
Click to expand...
Click to collapse
You're welcome - enjoy your "free" HDX.