Database Develop

[Q] Trying to flash zip, now fastboot doesn't work

Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.

Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?

SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.

[GUIDE][FIX] Solve Bootloops and no OS on phone!

Hello XDA-Community!
Because of the high amount of people having this particular problem, I decided to make this guide. Here it goes:
< < < ! ! ! WARNING ! ! ! > > >
THIS THREAD DOESN'T TEACH YOU HOW TO USE YOUR RICE COOKER, USE IT ON YOUR OWN RISK​
This guide is for you if you are in the following situation:​​
S-ON or S-OFF
UNLOCKEDor (RE)LOCKED Bootloader
NO ROM installed or a nasty BOOTLOOPor you just need METAPHYSICAL SUPPORT
You can get to fastboot!
Maybe you don't even know that you are able to enter fastboot, check FAQ in the 2nd post for that
​​
​
No matching and working ROM.zip? No Problem​​
Now there are several ways to do that. If you are S ON or S OFF download one of these ROM's and read the rest of the guide while the ROM is downloading in the background.
HTC Sense ROM KitKat:
http://www.androidrevolution.nl/downloader/download.php?file=One_4.19.401.8_odexed.zip
(Thanks to @mike1986.)
HTC Sense ROM JellyBean 4.3:
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
(Thanks to guru reset)
Google Play Edition KitKat(S OFF needed):
http://forum.xda-developers.com/showthread.php?t=2341395 (Go there and hit the thanke button if you use this)
https://mega.co.nz/#!3BtCBD6T!ViZfS1MwhR4ttcPEkB3XrDVv9Asardy4e01UJO-5ZB0
(Thanks to @bigxie)
Omni ROM:
http://forum.xda-developers.com/showthread.php?t=2488216 (Go there to and punch the thanks button if you use this)
http://dl.omnirom.org/m7ul/ (Official nightlies (download the ZIP file!!))
Or just download the homebrew ... I personally prefere this one(It's in the thread linked above)
CyanogenMod:
http://download.cyanogenmod.org/?device=m7ul
​
No drivers working? No Problem​​
This here works for Windows Vista/7/8 and Mac as far as I know !
Try using a different USB Port
Uninstall all the drivers related to android devices!
Download the HTCSync manager here (HTC Sync Manager)
Install the HTCSync Manager with ALL compomnents
Restart the computer
Uninstall the HTCSync Manager BUT do NOT uninstall the drivers!
Reboot your computer
Now the phone should be recognized properly.
Otherwise try using a different USB cable and a USB port directly on the motherboard of the PC
For those of you (windows users) that just want to install the drivers without the HTCSync procedure, you can download the drivers directly from this post here:
[Drivers] HTC Drivers for Windows - Several Versions
(Thanks @nkk71 for this hind and thanks @mdmower for providing HTC Drivers!)
If you have this particular issue here(Thanks @nkk71 check out his guide [GUIDE] nkk71's SuperGUIDE to returning 100% back to stock and punch the thanksbutton as often as you can!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then follow this procedure:
THIS SECTION IS FULLY COPY&PASTED FROM @nkk71 FROM THIS POST [GUIDE] nkk71's SuperGUIDE to returning 100% back to stock
If this works (and even if it doesn't) please go to his thread and punch the thanks button to death !
I did some small changes to it, so if there's a fault, it might just be LibertyMarine who made a mistake
​
When you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
Follow the steps below to fix it:
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
for those who like a visual guide:
As you can see, the drivers didn't install properly:
To solve this issue, open the Device Manager with Administrator permissions
Look, there's the culprit -.-
Right click One and select Update Driver Software
Next, select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer in the following menu
Choose Android USB Devices
Select My HTC ... (if you have more than one version, choose the latest)
There's a warning, select Yes and ignore it
Let's hope for a successful installation
Now it looks better
We can now confirm that you have a stable ADB connection from your PC to your phones recovery
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
This works in 99% of all cases. Otherwise these guides may help you further:
[FIX] Working Fastboot Drivers for Windows 8.1 x64
[FIX] Fastboot problems on Windows 8 x64 with USB 3.0? Solution inside
[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!)
Easily Set Up FASTBOOT and ADB on a MAC for Android Smartphones Youtube Turorial
Other guides will come soon!
​
RELOCKED or even LOCKED and even S ON? No Problem!​
For some unknow reason, you are relocked or even locked... yeah... and your bootloader is locked... you have no operating system installed and you think you are hard bricked.
To solve this problem, you just have to Unlock the bootloader again using HTCdev. I though this is pretty logic but there are still people that think they can't unlock it again. No that's wrong. So basically -> Just head over to: HTC Dev
And for those that want some pictures:
1) Chose All other supported models:
2) Chose the option: Begin Unlock Bootloader:
3) Press OK, then this screen appears, you have to accept both and continue:
4) Now.. Boot your phone into the bootloader holding power and vol down button at the same time while booting after having shutdown your phone
5) Since you must have fastboot installed because you followed the above descripted procedure... issue this command:
6) You'll get such an ouput(credit to htc because of privacy issues):
7) Enter the string on the bottom of the page(you need an account):
http://www.htcdev.com/bootloader/unlock-instructions/page-2
8) Follow the instructions given by mail from HTC...
And now for the case if you are S OFF and Locked or Relocked:
You can either use this toolkit: http://www.htc1guru.com/guides/guru-bootloader-reset/
Or follow this thread: [how to] lock/unlock your bootloader without htcdev(s-off required)
Both needs a recovery.. and how to flash a recovery with locked bootloader and s off, just look a few lines below ​
No Recovery? No Problem​​
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
​
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​
You want to have stock software again? No Problem​
This section here doesn't tell you how to go 100% stock. Here you find instructions for how to run a RUU or a FUU. If you want to go back to to a factory fresh device use this guide here instead:
[GUIDE] nkk71's SuperGUIDE to returning 100% back to stock
by @nkk71​
RUU - ROM Update Utility:​
A RUU will reset your phone back to stock software and you'll be able to get OTAs. But a RUU won't set you LOCKED and S ON!
PAY ATTENTION IF YOU ARE ON WINDOWS 8.1 AND READ FAQ FIRST IN SECOND POST!
First, find a matching RUU. There are several sources for RUUs, here are the most popular ones:
AndroidRUU | The #1 source for Android RUU files
Collection of HTC One RUU Zip File Downloads. Reset device to Stock (By HTC1Guru, if anyone know what his XDA account name is, tell it, I wanna mention him)
Now, here the step by step GUIDE goes:
THIS WILL DELETA ALL USERDATA​
Make a backup using TWRP or CWM
Copy the backup to your PC and copy your whole SDCard content to the PC too
Boot your phone to the bootloader and enter fastboot
Reboot to the RUU mode using this command:
Code:
fastboot oem rebootRUU
Check the connection:
Code:
fastboot devices
The output should look like this:
Code:
C:\Users\Obama\> fastboot devices
List of devices attached
<serial number> fastboot
Then flush your RUU.zip using this command(Windows users, pay attention to ruu.zip.zip):
Code:
fastboot flash zip "C:\<path>\<ruu_name.zip">
This should be the output, check that the red marked text is 100% exactly like this and ensure that you don't get any error during hboot flash, a failed hboot flash will UNEVITABLY lead into a hardbricked device if you reboot. For that check the FAQ section in my second post !
Code:
C:\User\Cheese\>fastboot flash zip "C:\<path>\<ruu_name.zip>"
sending 'zip' (100322311 KB)...
OKAY [ 30.124s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [COLOR="red"][RUU]WP,hboot,0[/COLOR]
(bootloader) [COLOR="red"][RUU]WP,hboot,99[/COLOR]
(bootloader) [COLOR="red"][RUU]WP,hboot,100[/COLOR]
(bootloader) [COLOR="Red"]...... Successful[/COLOR]
[COLOR="Red"]FAILED [/COLOR](remote: 90 hboot pre-update! [COLOR="Blue"]please flush image again immediately[/COLOR])
finished. total time: 35.231s
Reflash zip file again after the phone has automatically rebooted itself back to the RUU mode:
Code:
fastboot flash zip "C:\<path>\<ruu_name.zip">
Here, we won't flash any too cricital software parts, so check that the output looks approximately like this, it's ok that several partitions are bypassed.. just make sure it isn't the system or other partitions you'd like to reset back to stock. Ok, output looks like this:
Code:
C:\User\Cheese\>fastboot flash zip "C:\<path>\<ruu_name.zip>"
sending 'zip' (100322311 KB)...
OKAY [ 31.293s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
[...lot's of flashing...]
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... [COLOR="Blue"]Bypassed[/COLOR]
[...that's ok...]
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 230.443s]
finished. total time: 230.444s
Then reboot your phone to the bootloader:
Code:
fastboot reboot-bootloader
Check, that hboot is 1.44 and reboot your phone normally and enjoy stock software !
​
FUU - Firmware Update Utility:​
Was once WIP - Work in Progress !
But now, this section is shut down too.
​
I hope this guide helped you. Ask everything(except said differently) in the comments!​
Disclaimer:
I AM NOT RESPONSIBLE FOR ANY LOSS OF DATA BECAUSE YOU FOLLOWED THIS GUIDE
I AM NOT RESPONSIBLE FOR ANY HARD BRICKED DEVICES, TOASERS, RICE COOKERS!
I AM NOT RESPONSIBLE FOR ANY KIND OF NUCLEAR WAR DECLARED BY YOUR DOG/CAT​​

! Once this section was constantly growing !
​
Basic issues and troubleshooting? Here it goes​
Q: I can't start up my device, not even the soft buttons are lighting up!
A: I know, it sound strange, but you have to do the following thing:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!​
Q: I still can't boot up my device!
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again​
Q: I tried flashing the RUU and I got an error while flashing hboot, what can I do?
A: JUST DON'T REBOOT try reflashing, try a different hboot... use a different computer/usb cable, just don't reboot, rebooting will lead into a hard-bricked device!
The following Errors are save to reboot(Thanks @Sneakyghost, http://forum.xda-developers.com/showthread.php?t=2316726):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 seems to indicate different things, always relating to your phone not being eligible for a certain update. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match - there is no conclusive evidence yet, only hints. I can for now not see the commands being run by a RUU and determine which check exactly fails, so i am left guessing for now.​
Q: What do I have to pay attention to using Windows 8.1 ?
A: Actually, there are no more driver issues with Windows 8 or Windows 8.1. But if your HTC One is on hboot 1.44 or even below hboot 1.44 you can't get a fastboot connection to your HTC One. This means if you're using one of the older RUU's that downgrade to hboot 1.44 you'll be stuck after the first hboot preupdate:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
And you won't be able to reflash the RUU to complete the RUU process.. This means that you have to find a Windows 7 Computer to complete the RUU process. What does this exactly mean?
Never flash a 1.44 firmeware or RUU package to your device using Windows 8+ or you'll be stuck!
​
Q: What do I have to check when choosing an RUU?
A: That's pretty easy. But the best thing is to explane it with an example.. Ok, I downloaded this file here from HTC1Guru and it's called like this:
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.zip
Click to expand...
Click to collapse
Now, the red marked text has to be the same as your device was on stock.
x.xx.401.x stands for your location. It's also written before... like above "Europe"
And the blue text is also important ​
Q: What issues might come with newer hboots?
A: Ok, new hboots give you more performance and better stability. But the downside of one of these hboots is the newly introduced Tamper detected on hboot 1.55. This basically means that when going back to stock with a RUU Locking and Untampering and taking all OTAs up to hboot 1.55+ and then going back S ON(Highly NOT recommanded) will lead into a tamper dectected and you'll see this tampered flag again. What means, a lot of work: Unlocking, S offing, RUUing and Locking going S ON the right time again.. The particular right time is:
After hboot 1.44 but before hboot 1.55... this means the best hboot to use is 1.54.. you did an OTA and this means that the bootloader is more than stock and so most likely safe to go back s on and you are on a version before hboot 1.55 what means you won't get a tamper detected!
Also: Going back S ON with a altered bootloader is inevitably going to lead into a hard bricked device !
Summary:
NEVER GO S-ON WITH A MODIFIED HBOOT AND A HBOOT VERSION HIGHER THAN 1.54​

Reserved 2 is not needed anymore and won't be needed in the near future. So give him a snickers that this post is happy again !

Saying Thanks, Why not?​​
Ok, here I list the people that helped me building this thread, people that helped me gaining knowledge in such a short time, people that gave me advice, people that I used as a source in this thread.
Why do I do that? People say too seldon thanks, and I'll most likely leave the HTC One section because of problems I don't wanna mention.
I think I have to thank him first because:
@nkk71 He helped me dozens of times and and I used him as a source for this thread, as you can see, so Thanks very much
I also wanna really say thanks to:
@Sneakyghost Because I used him as a source on this thread and he gave me valuable advice to improve the threads content
And also a very big thanks to:
@kamilmirza for giving me advice and stealing my thread into his signature
But the bigges thanks goes to my:
@rice_cooker because it supports me through my every day life and provides the best rice!
​Sources and Very important links​​
For going back to a factory fresh HTC One for sending in for warranty claims:
[SOURCE]
[GUIDE] nkk71's SuperGUIDE to returning 100% back to stock
Custom hboots without red warning after S OFF, Firmware Update Utilities:
[SOURCE]
[GUIDE] [MOD] GSM Firmware Flashing & Hboots red warning gone
RUU Source, not only HTC One:
AndroidRUU | The #1 source for Android RUU files
CWM Backup, RUU, ROM.zip Source, basically everything for going back to stock:
HTC1Guru - HTC One Downloads
Installing ADB and FASTBOOT automatically:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1
​

nice
keep up the good work :good:

Nice work mate, i'm sure that'll help some noobies like us ourselves haha.
commenting on this: pushing ROM to path /data/media/0 resulted in permission and SU errors for me in the past, partly due to an imperfect SU which needed to be adjusted for Android 4.3 and then again for Android 4.4
What helped me there was trying different pathes, since we got at least 3 ways to access the SDCard:
/data/media/0
/storage/emulated/0
/sdcard
there might still be more. /sdcard should be the default way to address this so i recommend changing your adb command to /sdcard/rom.zip instead but provide the other two pathes as alternatives for people who experience issues with file and directory permissions after the flash or while flashing the ROM.
Regards,
Sneaky

Sneakyghost said:
Nice work mate, i'm sure that'll help some noobies like us ourselves haha.
commenting on this: pushing ROM to path /data/media/0 resulted in permission and SU errors for me in the past, partly due to an imperfect SU which needed to be adjusted for Android 4.3 and then again for Android 4.4
What helped me there was trying different pathes, since we got at least 3 ways to access the SDCard:
/data/media/0
/storage/emulated/0
/sdcard
there might still be more. /sdcard should be the default way to address this so i recommend changing your adb command to /sdcard/rom.zip instead but provide the other two pathes as alternatives for people who experience issues with file and directory permissions after the flash or while flashing the ROM.
Regards,
Sneaky
Click to expand...
Click to collapse
Thanks Sneakyghost !
Yeah, I made this guide because quite a lot of people are complaining about having no OS and so on
I added this hint about the different paths to the guide I personally haven't had this issue but it's the best to provide solutions for as many cases as possible .. (sorry for my bad english)
Have a great evening,
LibertyMarine

Hi @LibertyMarine
nice work :good::good: (i did press the thanks before, bot only now actually got to reading it all)
If you don't mind, a few notes (just trying to help)
Let them check MD5 on anything they download, a lot of times, just turns out to be a bad download.
No matching and working ROM.zip? No Problem
"HTC Sense ROM KitKat(S OFF needed)" by @mike1986. doesn't actually need S-OFF,
but "Google Play Edition KitKat" by @bigxie needs S-OFF,
if I'm not mistaken.
No drivers working? No Problem
HTC Drivers for Windows (without HTCSync), can be found here: http://forum.xda-developers.com/showthread.php?t=2089508
also, if the phone is just recognized as:
check my (updated ) Guide, Post #1, FAQ #2 on how to fix that.... feel free to incorporate it (or relevant parts) into your guide.
No Recovery? No Problem
"For some stupid reason you are s off (that's a MUST) and Relocked" the firmware package you posted works only for CID: 11111111 , T-MOB010 CWS__001 , BS_US001 and maybe GOOGL001; it wont work for HTC__001 and HTC__002 due to missing line break
so
1- let them first change CID to SuperCID then flash it
2- (in my humble opinion) once in custom recovery, let them unlock bootloader using @scotty1223 adb commands ( http://forum.xda-developers.com/showthread.php?t=2475914 ), or whatever method you find appropriate
keep up the good work :highfive:

thanks for your post.. nice post

nkk71 said:
Hi @LibertyMarine
nice work :good::good: (i did press the thanks before, bot only now actually got to reading it all)
If you don't mind, a few notes (just trying to help)
Let them check MD5 on anything they download, a lot of times, just turns out to be a bad download.
No matching and working ROM.zip? No Problem
"HTC Sense ROM KitKat(S OFF needed)" by @mike1986. doesn't actually need S-OFF,
but "Google Play Edition KitKat" by @bigxie needs S-OFF,
if I'm not mistaken.
No drivers working? No Problem
HTC Drivers for Windows (without HTCSync), can be found here: http://forum.xda-developers.com/showthread.php?t=2089508
also, if the phone is just recognized as:
check my (updated ) Guide, Post #1, FAQ #2 on how to fix that.... feel free to incorporate it (or relevant parts) into your guide.
No Recovery? No Problem
"For some stupid reason you are s off (that's a MUST) and Relocked" the firmware package you posted works only for CID: 11111111 , T-MOB010 CWS__001 , BS_US001 and maybe GOOGL001; it wont work for HTC__001 and HTC__002 due to missing line break
so
1- let them first change CID to SuperCID then flash it
2- (in my humble opinion) once in custom recovery, let them unlock bootloader using @scotty1223 adb commands ( http://forum.xda-developers.com/showthread.php?t=2475914 ), or whatever method you find appropriate
keep up the good work :highfive:
Click to expand...
Click to collapse
ok, thanks thousand times !!
I'll add these hints to my guide ... just need some time
What you said about @scotty1223's guide... I tried it once in the custom recovery... but it didn't work for me... but I'll add it... and I'll try to get it working for me.. so I can give them my experience... or whatever
Anyways, THANKS !!
Have a great evening,
LibertyMarine

LibertyMarine said:
ok, thanks thousand times !!
I'll add these hints to my guide ... just need some time
What you said about @scotty1223's guide... I tried it once in the custom recovery... but it didn't work for me... but I'll add it... and I'll try to get it working for me.. so I can give them my experience... or whatever
Anyways, THANKS !!
Have a great evening,
LibertyMarine
Click to expand...
Click to collapse
how come it didnt work
worked for me, there are more than one way to unlock bootloader with S-Off (maybe "safest" and easiest to use is http://www.htc1guru.com/guides/guru-bootloader-reset/ )
but there are other ways too (GPE 4.2.2 RUU -> fastboot oem unlock ) as long as s-off

WIP, I am making all the screenshots and I'll upload them as fast as I can, because just using the screenshots from nkk71 would be some kind of stealing, so I wanna quickly do it on my own
Click to expand...
Click to collapse
@LibertyMarine no problem, you can use the pictures (since you're already mentioned where it came from :laugh: ). Let me know if you want the text too, i can PM you the whole section (including the IMG pictures links)

nkk71 said:
@LibertyMarine no problem, you can use the pictures (since you're already mentioned where it came from :laugh: ). Let me know if you want the text too, i can PM you the whole section (including the IMG pictures links)
Click to expand...
Click to collapse
ok, thanks ! this saves a lot of work !! :good::victory:
oh, you don't need to send me the section with PM, I think I can copy paste it when I try to quote your post Thanks anyways for this offer !
If you know another way I can mention you, just tell it, I'll do it !

LibertyMarine said:
Thanks Sneakyghost !
Yeah, I made this guide because quite a lot of people are complaining about having no OS and so on
I added this hint about the different paths to the guide I personally haven't had this issue but it's the best to provide solutions for as many cases as possible .. (sorry for my bad english)
Have a great evening,
LibertyMarine
Click to expand...
Click to collapse
I think there's another path you can use but I haven't tested it, just seen it being there: /mnt/sdcard
mobile Viper bite

I ****ed up my phone. I think I need to just get a rom onto my phone but its basically stuck in recovery. Can someone explain how to get a rom onto my phone? Is it adb sideload? And if it is I can't figure out how to work that.

lilfil3 said:
I ****ed up my phone. I think I need to just get a rom onto my phone but its basically stuck in recovery. Can someone explain how to get a rom onto my phone? Is it adb sideload? And if it is I can't figure out how to work that.
Click to expand...
Click to collapse
As I understood, you can get to the recovery.
If you already have a ROM downloaded to your computer, just go to this section of the first post in this thread called:
Bootloop, No OS, Totally f*cked up OS? No Problem​​
Lots of instructions​
But if you don't have any OS downloaded, go to this section and download one
No matching and working ROM.zip? No Problem​​
Lots of roms​
If this doesn't work, just call me again with a mention or a post.. whatever

lilfil3 said:
I ****ed up my phone. I think I need to just get a rom onto my phone but its basically stuck in recovery. Can someone explain how to get a rom onto my phone? Is it adb sideload? And if it is I can't figure out how to work that.
Click to expand...
Click to collapse
Is this what's supposed to happen? And thanks for all the help by the way!
(Attachment below)

lilfil3 said:
Is this what's supposed to happen? And thanks for all the help by the way!
(Attachment below)
Click to expand...
Click to collapse
you forgot the space .. you wrote
Code:
adb push C:\Users\filic_000\One_blabla.[COLOR="Red"]zip/sdcard[/COLOR]/One_blabla.zip
instead of
Code:
adb push C:\Users\filic_000\One_blabla.[COLOR="Red"]zip /sdcard[/COLOR]/One_blabla.zip
in the second one there's a space between .zip /sdcard

LibertyMarine said:
you forgot the space .. you wrote
Code:
adb push C:\Users\filic_000\One_blabla.[COLOR="Red"]zip/sdcard[/COLOR]/One_blabla.zip
instead of
Code:
adb push C:\Users\filic_000\One_blabla.[COLOR="Red"]zip /sdcard[/COLOR]/One_blabla.zip
in the second one there's a space between .zip /sdcard
Click to expand...
Click to collapse
Ok now it said error: device not found

lilfil3 said:
Ok now it said error: device not found
Click to expand...
Click to collapse
are you in recovery? if yes... try this section in the first post:
No drivers working? No Problem​​Lot's of instructions​

[Q] Stuck in RElocked bootloader cannot unlock

Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!

FURTHER to the above
jaqzilch said:
...
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,

jaqzilch said:
Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
Ok...
First flash a recovery(use Case 2):
No Recovery? No Problem​​
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
​
now you are unlocked and s off... so what we're gonna do depends on what you want to achieve... I didn't really get what you meant in the first post.. you want to be again 100% stock on a Asian ROM ?
with the unlocked bootloader and s off and the custom recovery you are pretty much able to flash the rom you want to the device... how to do this:
http://forum.xda-developers.com/showthread.php?t=2632736
or:
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
jaqzilch said:
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,
Click to expand...
Click to collapse
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs

LibertyMarine said:
Ok...
First flash a recovery(use Case 2):
...
[/INDENT][/INDENT]
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs
Click to expand...
Click to collapse
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
and nothing happens on my phone.
Re: Case two-- I'm one of those poor S-on folks so…
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!

jaqzilch said:
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
Click to expand...
Click to collapse
yeah.. that's because you are locked ....
jaqzilch said:
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
Click to expand...
Click to collapse
hmmm... have you tried redownloading/rerequesting a unlock token ?
try that... try requesting a new one and try flashing this one...
jaqzilch said:
and nothing happens on my phone.
Click to expand...
Click to collapse
haven't had such an issue.. I'll do some research on this topic..
jaqzilch said:
Re: Case two-- I'm one of those poor S-on folks so…
Click to expand...
Click to collapse
I don't know why.. I though you were s off... sorry... I must have commuted you with an other guy
jaqzilch said:
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!
Click to expand...
Click to collapse
Yeah... case 3 needs a custom recovery.. but you won't need that one anyways.. because your data partition seems to be OK

Phone keeps rebooting after ROM flash.

Hey. I got a problem with my beloved M7. Few days ago I gave a chance to CM12, but I got bored of it and tried to flash InsertCoin 4.0.5. Everything went well but now my phone boots up and locks the screen. If I unlock the screen, a green HTC logo on white background appears. After few seconds of showing the logo the phone reboots and locks the screen again. I can freely access the TWRP, but I have no backup and I lost CM12 installing files. Please can someone help me bring my lovely phone back to life?
P.S sorry for my English

Taurenom said:
Hey. I got a problem with my beloved M7. Few days ago I gave a chance to CM12, but I got bored of it and tried to flash InsertCoin 4.0.5. Everything went well but now my phone boots up and locks the screen. If I unlock the screen, a green HTC logo on white background appears. After few seconds of showing the logo the phone reboots and locks the screen again. I can freely access the TWRP, but I have no backup and I lost CM12 installing files. Please can someone help me bring my lovely phone back to life?
P.S sorry for my English
Click to expand...
Click to collapse
Just follow this guide, it should help:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone any ways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didn't install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Taurenom said:
Hey. I got a problem with my beloved M7. Few days ago I gave a chance to CM12, but I got bored of it and tried to flash InsertCoin 4.0.5. Everything went well but now my phone boots up and locks the screen. If I unlock the screen, a green HTC logo on white background appears. After few seconds of showing the logo the phone reboots and locks the screen again. I can freely access the TWRP, but I have no backup and I lost CM12 installing files. Please can someone help me bring my lovely phone back to life?
P.S sorry for my English
Click to expand...
Click to collapse
Sounds like another one with Unknown IMEI and baseband
Follow @alray guide as posted by @majmoz if the problem persists try flashing CM11 then go to Settings>About>Phone Identity and check your IMEI is displayed correctly there. Also check baseband in Settings>About>Software Information>More.

Danny201281 said:
Sounds like another one with Unknown IMEI and baseband
Follow @alray guide as posted by @majmoz if the problem persists try flashing CM11 then go to Settings>About>Phone Identity and check your IMEI is displayed correctly there. Also check baseband in Settings>About>Software Information>More.
Click to expand...
Click to collapse
I managed to somehow flash CM12 back. ^^ My baseband is 4A.17.3250.14_10.39.1150.04L. And here comes another question. How can I get back to 4.4.3 with Sense ROMs without reboots which happened earlier? I have seen that I have to flash certain firmware, but I am not sure which one.
P.S @majmoz Thanks for help, you saved my One!

Taurenom said:
I managed to somehow flash CM12 back. ^^ My baseband is 4A.17.3250.14_10.39.1150.04L and IMEI 3578640528003796. And here comes another question. How can I get back to 4.4.3 with Sense ROMs without reboots which happened earlier? I have seen that I have to flash certain firmware, but I am not sure which one.
P.S @majmoz Thanks for help, you saved my One!
Click to expand...
Click to collapse
First you should edit you post and remove your imei. You don't want to make that public
If you could post the output of
Code:
fastboot getvar all
it would be helpful you should also remove your imei and serial number before posting :good:
but the fact the imei and baseband don't display Unknown in settings is good

Danny201281 said:
First you should edit you post and remove your imei. You don't want to make that public
Click to expand...
Click to collapse
Got it done As I wrote earlier, I would like to get back to 4.4.3 Sense. I found a guide for m8
HTML:
http://forum.xda-developers.com/showthread.php?t=2733523
., which I guess would work on m7 too, but I'm not sure which firmware is required to make 4.4.3 properly work.

Taurenom said:
Got it done As I wrote earlier, I would like to get back to 4.4.3 Sense. I found a guide for m8
HTML:
http://forum.xda-developers.com/showthread.php?t=2733523
., which I guess would work on m7 too, but I'm not sure which firmware is required to make 4.4.3 properly work.
Click to expand...
Click to collapse
It depends on which variant of the HTC One you have, see the edit in my post above

Well, I struggled almost 2 hours in order to get "getvar all" logs and nothing happened. When I enter ADB command - "adb devices" it lists my phone below but as an offline device. I tried over and over using guides linked by majmoz and this one -
HTML:
https://www.youtube.com/watch?v=rfC9_HXaI_U
. Is there any other possible way to get logs excepting via ADB/fastboot on PC?

Taurenom said:
Well, I struggled almost 2 hours in order to get "getvar all" logs and nothing happened. When I enter ADB command - "adb devices" it lists my phone below but as an offline device. I tried over and over using guides linked by majmoz and this one -
HTML:
https://www.youtube.com/watch?v=rfC9_HXaI_U
. Is there any other possible way to get logs excepting via ADB/fastboot on PC?
Click to expand...
Click to collapse
To get the getvar info your Device should be in the bootloader in fastboot usb mode.
Then send the fastboot getvar all command.

@Danny201281 Yeah, I tried to do this in fastboot mode. Windows pop up says that there is unrecognized device connected, what shouldn't have even happened because I have the latest HTC drivers(2.0.7.27) from HTC Sync.

Taurenom said:
Yeah, I tried to do this in fastboot mode. Windows pop up says that there is unrecognized device connected, what shouldn't even happened because I have the latest HTC drivers(2.0.7.27) from HTC Sync.
Click to expand...
Click to collapse
See Q(2 in this faq post to fix the drivers http://forum.xda-developers.com/showthread.php?p=52135024
It's common for Windows drivers to fail like this. You can check in device manager you phone should be listed a "MY HTC"
Other than that try connecting to a different usb port. USB2.0 ports are best. :good:

Danny201281 said:
See Q(2 in this faq post to fix the drivers http://forum.xda-developers.com/showthread.php?p=52135024
It's common for Windows drivers to fail like this. You can check in device manager you phone should be listed a "MY HTC"
Other than that try connecting to a different usb port. USB2.0 ports are best. :good:
Click to expand...
Click to collapse
My hboot version is 1.54.0000; device manager lists the phone as "MY HTC" with exclamation mark in a triangle, and yes I'm using USB 2.0 port.
P.S won't this command work if I'm S-ON?

Taurenom said:
My hboot version is 1.54.0000; device manager lists the phone as "MY HTC" with exclamation mark in a triangle, and yes I'm using USB 2.0 port.
P.S won't this command work if I'm S-ON?
Click to expand...
Click to collapse
We need to know your CID, MID and Version Main which is all in the getvar. In any case you will need fastboot working to flash your firmware.
If your Device is s-off that's good you don't want to go back to s-on for any reason. In any case going back to s-on also requires fastboot. Try this http://forum.xda-developers.com/showthread.php?p=54272479
This is my guide for setting up Linux on a bootable usb pen drive. It will eliminate any driver issues

Danny201281 said:
We need to know your CID, MID and Version Main which is all in the getvar. In any case you will need fastboot working to flash your firmware.
If your Device is s-off that's good you don't want to go back to s-on for any reason. In any case going back to s-on also requires fastboot. Try this http://forum.xda-developers.com/showthread.php?p=54272479
This is my guide for setting up Linux on a bootable usb pen drive. It will eliminate any driver issues
Click to expand...
Click to collapse
I tried to follow your guide on virtual machine because I simply don't know how to boot from pendrive on my laptop. Now Linux can't even see my One After typing "sudo adb devices" command, there is blank list of devices attached, and when I typed "sudo adb reboot bootloader" an error popped up "error: device not found".

Taurenom said:
I tried to follow your guide on virtual machine because I simply don't know how to boot from pendrive on my laptop. Now Linux can't even see my One After typing "sudo adb devices" command, there is blank list of devices attached, and when I typed "sudo adb reboot bootloader" an error popped up "error: device not found".
Click to expand...
Click to collapse
Sorry i can't help with adb/fastboot problems when running Linux as a VM. I've never used linux as a virtual machine in windows, and your knowledge of Windows it's self is probably better than mine especially Windows 8. I'm confident there is no problem with your device this is a connectivity issue most probably caused by drivers. Hopefully @majmoz or @clsA can help you get it working on windows 8.
Although booting your laptop from a usb shouldn't be that difficult. You just need to change the boot order in the bios. The bios can be accessed normally by pressing "Delete" or "F2" during the first boot screen on your laptop. Then change the boot settings so that USB is the first boot device. What make is your laptop?

Danny201281 said:
Sorry i can't help with that adb/fastboot. I've never used linux as a virtual machine in windows, and your knowledge of Windows it's self is probably better than mine especially Windows 8. I'm confident there is no problem with your device this is a connectivity issue most probably caused by drivers. Hopefully @majmoz or @clsA can help you get it working on windows 8.
Although booting your laptop from a usb shouldn't be that difficult. You just need to change the boot order in the bios. The bios can be accessed normally by pressing "Delete" or "F2" during the first boot screen on your laptop. Then change the boot settings so that USB is the first boot device. What make is your laptop?
Click to expand...
Click to collapse
It's Lenovo y50-70; bios is completly hidden from the user - that's why I can't boot it from pendrive. I will try to follow your hints asap as I get access to my PC at home

Taurenom said:
It's Lenovo y50-70; bios is completly hidden from the user - that's why I can't boot it from pendrive. I will try to follow your hints asap as I get access to my PC at home
Click to expand...
Click to collapse
Ok cool, Sorry man i'm not big on Windows. I use linux as my main OS although my pc dual boot Windows 7 but I use that mainly for gaming. If linux got a little more gamer love I wouldn't use windows at all
As far as I know Windows 8 can bit a bit finicky when it comes to android phones although I know there are plenty that use it without any problems.

Taurenom said:
It's Lenovo y50-70; bios is completly hidden from the user - that's why I can't boot it from pendrive. I will try to follow your hints asap as I get access to my PC at home
Click to expand...
Click to collapse
Danny201281 said:
Ok cool, Sorry man i'm not big on Windows. I use linux as my main OS although my pc dual boot Windows 7 but I use that mainly for gaming. If linux got a little more gamer love I wouldn't use windows at all
As far as I know Windows 8 can bit a bit finicky when it comes to android phones although I know there are plenty that use it without any problems.
Click to expand...
Click to collapse
Their is only one problem using windows 8.1 and that is hboot 1.44 and that is still fixable with a little searching
My windows 8.1 PC only uses 3 files you can download and install them from here > http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
And the HTC Driver from here >> https://mega.co.nz/#!9cpz0Soa!rZH0H5djENbFN2xkS9S7yUlXzX_vcC5yOHhmUR55kUM
I just did a brand new Blue HTC One on hboot 1.44 Last week with this setup ... It Works !

clsA said:
Their is only one problem using windows 8.1 and that is hboot 1.44 and that is still fixable with a little searching
My windows 8.1 PC only uses 3 files you can download and install them from here > http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
And the HTC Driver from here >> https://mega.co.nz/#!9cpz0Soa!rZH0H5djENbFN2xkS9S7yUlXzX_vcC5yOHhmUR55kUM
I just did a brand new Blue HTC One on hboot 1.44 Last week with this setup ... It Works !
Click to expand...
Click to collapse
Thanks @clsA that's exactly why I tagged you in my post. I know from previous posts that you use Windows 8 without problems :good: I don't know where to start with Windows 8. Never used it and doubt I ever will. If it was in front of me I dare say I could figure it out. But over the forum I'm just poking around in the dark when it comes to windows 8

Help - cannot enter system after clean installation of Android Revolution

So aftter downloading the Android Revolution and wiping the data, I tried installing the ROM.
However it keeps booting into recovery mode. I have no idea how to fix this.
The phone tries to boot up normally, but fails to do so. It restarts and boots into recovery. (TWRP 2.5.0.0)
I have tried deleting installing a few times. Where I cleared both the cache and dalvik cache.
Still nothing. Is there any way to get another ROM onto my phone now? My computer doesn't recognize the device anymore.
After the installation it says complete, but shows an error: "set_metadata_recursive: some changes failed"
after this it says: "installation was succesful!" and tells me to do 1 full system boot before flashing mods.:crying::crying:
"Update, I found out I used a rom designed for M8 and not M7.
If anyone could help me getting ADB to work and a rom I can flash and pretty much a tutorial. I would be super grateful

So I found a m7 rom. But when trying to push it using ADB it takes a really long time and ends in protocol error.

Aisu64 said:
boots into recovery. (TWRP 2.5.0.0)
Click to expand...
Click to collapse
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
make sure you have the latest adb version (1.0.32) using the command:
Code:
adb version
If not update your android sdk-tools: https://developer.android.com/sdk/index.html#Other
Also make sure you have the latest htc drivers installed on your computer
With the latest twrp and drivers you'll be able to transfer a rom to your phone using MTP protocol when booted in twrp main menu (simply drag and drop your file from your computer to your phone storage).
If using newer roms (android 5.0.2) your phone must have a 7.xx.xxx.x firmware installed on it. Older firmware running new roms cam have issues. To determine your firmware version, use the command "fastboot getvar version-main" or "fastboot getvar all"

Finally pushed the files to the phone.
But after installing my phone still keeps entering recovery mode (twrp).

Aisu64 said:
Finally pushed the files to the phone.
But after installing my phone still keeps entering recovery mode (twrp).
Click to expand...
Click to collapse
Did you updated your twrp recovery?

alray said:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Can you help me a little bit? I can't see the device connected unless I'm in recovery. Can I flash a recovery in recovery?
Click to expand...
Click to collapse

Aisu64 said:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Can you help me a little bit? I can't see the device connected unless I'm in recovery. Can I flash a recovery in recovery?
Click to expand...
Click to collapse
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.

alray said:
Aisu64 said:
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.
Click to expand...
Click to collapse
I have tried deleting, restarting and reinstalling the drivers. But my phone wont show up under devices anymore. I really appreciate your help, but I really have to go to bed as I have a long day at work tomorrow.
Click to expand...
Click to collapse

Aisu64 said:
I have tried deleting, restarting and reinstalling the drivers. But my phone wont show up under devices anymore. I really appreciate your help, but I really have to go to bed as I have a long day at work tomorrow.
Click to expand...
Click to collapse
No problem, go take some rest and I'll help you later :good:

alray said:
No problem, go take some rest and I'll help you later :good:
Click to expand...
Click to collapse
So I've been playing around installing and reinstalling and deleting and restarting my computer.
My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.
Is it possible to flash the phone while in recovery?

Aisu64 said:
So I've been playing around installing and reinstalling and deleting and restarting my computer.
My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.
Click to expand...
Click to collapse
you won't get any adb connectivity when booted in bootloader / fastboot usb mode. ADB only works from a booted rom with usb debug turned on or from a custom recovery. In bootloader you must use fastboot commands. To see if your phone is detected by your computer when in bootlaoder / fastboot usb mode, use the command "fastboot devices"
If your phone isn't listed with this command, please post a screenshot of your Windows devices manager with the phone connected and booted in bootloader / fastboot usb mode. Also need to know what is your bootloader version? 1.44/1.54/1.55/1.56/1.57 or 1.61 ? You can see this info when booted in bootloader mode
Is it possible to flash the phone while in recovery?
Click to expand...
Click to collapse
You might want to read what I said again:
You won't be able to flash any recent rom using twrp 2.5.0.0
You can't flash a new recovery using twrp 2.5.0.0, you must use fastboot
:good:

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says Hboot - 1.44
atm I can't even get it to show up in recovery.
Screenshot: http://imgur.com/So88OLm

Aisu64 said:
It says Hboot - 1.44
atm I can't even get it to show up in recovery.
Screenshot: http://imgur.com/So88OLm
Click to expand...
Click to collapse
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?

alray said:
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?
Click to expand...
Click to collapse
Yes I do. A super ancient one.
Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66

Aisu64 said:
Yes I do. A super ancient one.
Click to expand...
Click to collapse
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.
Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66
Click to expand...
Click to collapse
Everything is fine here.

alray said:
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.
Everything is fine here.
Click to expand...
Click to collapse
You might aswell type the next part. Cuz this will be taking a few hours ^^

Aisu64 said:
You might aswell type the next part. Cuz this will be taking a few hours ^^
Click to expand...
Click to collapse
well I need to see your "fastboot getvar all" before i can tell anything more.

alray said:
well I need to see your "fastboot getvar all" before i can tell anything more.
Click to expand...
Click to collapse
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?
one more thing. I can't get it to show it's connected to ADB while in recovery.

Aisu64 said:
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?
one more thing. I can't get it to show it's connected to ADB while in recovery.
Click to expand...
Click to collapse
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339

alray said:
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
Click to expand...
Click to collapse
I borrowed a friends win7 computer and fastboot works! After installing the drivers you linked me to. Here is a screenshot! http://imgur.com/CN0uLu6