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.
Related
Hi all,
So I spent like the whole afternoon tryin to unlock bootloader on my MB860 (rooted) with no luck. This is international version with 2.3.4 system updated OTA.
I tried to unlock bootloader with fastboot - no luck:
Code:
OEM Unlock is not implemented
So i tried flash unlocked sbf file (intl-fix-try1.sbf), still no luck:
Code:
Failed to boot 1
So, I've flashed whole sbf file: 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
Phone started and all was same as before this operation,
next - I tried another full sbf's:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-Retail-GB.sbf
1FF-olympus_latam-user-2.3.6-4.5.2A-51_OLL-17.8-111109-release-keys-signed-BellMobility-CA-GAS_NA_OLYMPUSGBCANADABELL_P019.sbf
On both - failed to boot 1
so in the end only sbf that actually allows me to boot my cell is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
And the question is - how to get unlocked bootloader for this one?
You really should have searched and read up ahead of time. "Failed to boot XXX" is a perfectly normal and expected thing to happen when unlocking the BL. You shouldn't have messed with any more SBFs. You can still try running the fixer script as mentioned in that thread, hopefully you didn't mess it up too bad.
Thank you ravilov, but isn't this script only for ATT devices?
I am fairly certain it can be used on an international device as well.
Thanks, will try later on today, so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
stingu said:
so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
Click to expand...
Click to collapse
Yes.
stingu said:
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
Click to expand...
Click to collapse
Yeah, that's to be expected.
I think the worst case scenario would be that you won't be able to unlock, in which case you might be one of the unlucky people with the non-unlockable bootloader. If not, this script should help in unlocking your BL.
so, with the script and option number 3 i got the same thing:
Code:
(bootloader) OEM unlock is not implemented
OKAY [ -0.000s]
finished. total time: -0.000s
Or should i first flash small sbf and then use the script?
any other suggestions or am I stuck with soft 2.3.4?
You did flash the pudding/ihop SBF, right? If not, try doing that before you attempt to run oem unlock. If you did already... Well, I'm out of ideas then. I guess while waiting for someone else to chime in, you might as well start mentally preparing that you might indeed stay stuck with the stock firmware.
Well, made it unlocked, it was little bit tricky, so what I did:
-flashed IHOP
-got failed to boot 1 error message again - here, where i was not aware of - I pressed vol up and it switched to fastboot protocol support with boot error present
-did the script, fail to boot error was still there after reboot
-did those 2 points with flashboot application (whole instruction available here http://forum.xda-developers.com/showthread.php?t=1302423):
Code:
13.back in your command prompt window type "fastboot oem unlock" no quotes
14.You will now receive a warning along with a unique device ID
15.Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####•
fastboot oem unlock ####
fastboot reboot
Now its time to install CWM somehow...
I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
elijahkan14 said:
I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
Click to expand...
Click to collapse
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Kienan said:
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Click to expand...
Click to collapse
I can't get any of these methods to work
elijahkan14 said:
I can't get any of these methods to work
Click to expand...
Click to collapse
1. Make sure you are on the latest software: 2.17.605.2
2. Factory reset your phone
3. Slowly go through the manual instructions here: [Script] Automated Unlock/SuperCID/Temp-Root scripts for Windows and Linux
So, I've unlocked this phone before.
Just got a replacement.
EVERYTIME I put the token code in and summit I get failed!
screenshot of the error:
http://s28.postimg.org/z8obp6h58/Untitled.jpg
I tired a few different codes and nothing.
HELP?
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
BlowUpTheOutsideWorld said:
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
Click to expand...
Click to collapse
I was having difficulty with the SuperCID hack, and it appears that it was due to an OTA update. I was able to following the directions prescribed here, but I had HBOOT 1.15 and not 1.16. The basic idea is to
1. Gain "temp-root" access using the loop-restore trick together with the fake_backup.ab file.
The next steps were failing for me. I was able to verify that mmcblk0p4 had been copied over correctly, with the "modded" version, but each time the boot loader was rebooted, it would be replaced with the original version containing VZW__001, and not 11111111. However apparently all that needed to be done to reach S-OFF status was:
2. Run Rumrunner after obtaining temp-root status. The Rumrunner binary unlocks the phone and places it in S-OFF status.
Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.
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?
So I decided to flash M and while doing the flash-all.sh, I got a fastboot error stating malloc something and then did a factory reset, relock bootloader doh!!!!!, flashing manually individual items up until the last one system. It errored out saying something is too large blah blah, and the tablet is now unbootable without any OS and can't flash anything cuz bootloader is LOCKED (Doh! again).
I can only get into stock recovery and only can do adb sideload but tried cyanogenmod but can't get pass the signature validation. So here I am sitting duck with my zombie tablet.
Questions:
1. Will I be able to file for warranty with Google given it's only < 1 year old?
2. Is there an update.zip that you know of which can allows me to adb sideload?
TIA
vboyz103 said:
So I decided to flash M and while doing the flash-all.sh, I got a fastboot error stating malloc something and then did a factory reset, relock bootloader doh!!!!!, flashing manually individual items up until the last one system. It errored out saying something is too large blah blah, and the tablet is now unbootable without any OS and can't flash anything cuz bootloader is LOCKED (Doh! again).
I can only get into stock recovery and only can do adb sideload but tried cyanogenmod but can't get pass the signature validation. So here I am sitting duck with my zombie tablet.
Questions:
1. Will I be able to file for warranty with Google given it's only < 1 year old?
2. Is there an update.zip that you know of which can allows me to adb sideload?
TIA
Click to expand...
Click to collapse
1. Maybe. Better try, because it's your only option, since you chose to relock your bootloader.
2. No.
vboyz103 said:
So I then did a factory reset, relock bootloader doh!!!!!
Click to expand...
Click to collapse
So what your saying is you attempted to flash the M preview image, it didn't flash properly and you did a "fastboot oem lock" ???
vboyz103 said:
So I decided to flash M and while doing the flash-all.sh, I got a fastboot error stating malloc something and then did a factory reset, relock bootloader doh!!!!!, flashing manually individual items up until the last one system. It errored out saying something is too large blah blah, and the tablet is now unbootable without any OS and can't flash anything cuz bootloader is LOCKED (Doh! again).
Click to expand...
Click to collapse
I'm confused about the order of things. If the "system is too large" error happened after you BELIEVE you re-locked, then I think you might not really be locked...
The system part often on a lot of Nexii give that error. The solution is to extract the archive and fastboot flash the content images individually.
Update: I called HTC and it was still under warranty. Shipped the device to them and thought that they'll repair it. In fact, they shipped me a brand new one.
A happy camper here and thanks HTC.