Database Develop

[GUIDE] Return to stock for Canadian HTC One Users

This guide is for Canadian HTC One Bell Rogers Telus users who need to go back to stock firmware for warranty after flashing custom recovery/rom. If you have installed Open EU, Google, Dev, ATT, or any other kind of RUU, see post #2.
Requirements:
1. Your HBOOT is 1.55.
2. You received OTA to JB 4.3 from Rogers Bell Telus
3. Your main version is 3.x.661.x, 3.x.666.x, 3.x.631.x,
4. Some working knowledge of ADB/Fastboot.
Steps to restore stock:
1. Download your respective nandroid backup from below:
Rogers Nandroid: Stock_JB_4.3_ROGER001_TWRP_3.22.631.1.zip - http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-roger001-3-22-631-1-zip/
Bell Nandroid: Stock_JB_4.3_BM___001_TWRP_3.23.666.1.zip - http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-bm___001-3-23-666-1-zip/
Telus Nandroid: Stock_JB_4.3_TELUS001_TWRP_3.22.661.1.zip - http://goo.gl/sYoqei
Telus RUU ZIP: http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Run fastboot oem rebootRUU.
Then, flash the RUU with the command fastboot flash zip filename
Click to expand...
Click to collapse
2. Download latest TWRP from: http://techerrata.com/browse/twrp2/m7
3. Reboot your device in fastboot and flash TWRP recovery. I used 2.6.3.0.
4. Reboot into recovery and do a backup of what you have working now (very important)
5. Boot back into OS
6. Unzip the nandroid backup folder and copy it to your \\SDCARD\TWRP\BACKUPS\######\somefolder\
7. Reboot back into TWRP, and restore the nandroid file
8. Reboot, your phone should be booting into your carrier firmware
9. Root
10. S-Off: Rumrunner thread, link: http://forum.xda-developers.com/showthread.php?t=2488772
11. Verify all is WORKING OK, then flash stock recovery, Link: http://goo.gl/2Kntxz
12. Remove *Tempered* from boot thread, link: http://forum.xda-developers.com/showthread.php?t=2477792
13. Unroot from SuperSU app.
14. S-On if you must, highly NOT suggested. command: fastboot oem writesecureflag 3
15. All should be good now.
Click to expand...
Click to collapse

** I am working from theory, and NOT actual experience with this **
Guide for HBOOT 1.44 (4.1.2) & those on DEV/GPE/ATT/INTL RUU based firmwares
Bell: 1.29.666.5 - http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
Rogers: 1.29.631.4 - http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-roger001-1-29-631-4-2013-06-03-zip/
Telus: 1.29.661.5 - http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-telus001-1-29-661-5-rar/
Stock Recovery for 1.44 HBOOT: http://goo.gl/Yzkwtl
1.44 HBOOT (S-Off required): http://d-h.st/qfc
Assumptions:
1. You have S-Off
2. You have 1.44 HBOOT
3. You know how to use fastboot/adb commands.
Steps to revert to 4.1.2 HTC One:
1. Install earliest possible RUU for Dev edition.. 1.29.1540.3 http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-zip/
Make sure your CID is 11111111 and MID is PN0712000.
1a. If it fails to install, install the 1.44 HBOOT from above: fastboot flash zip hboot.zip and then re-flash the DEV zip file as fastboot flash zip devruu.zip
2. Install recovery. CWM for Bell & Rogers, TWRP for Telus. Do a backup from custom recovery (mostly to generate a backup path to use in step 4)
3. Reboot back into OS
4. Unzip the nandroid backup folder and copy it to your \\SDCARD\TWRP\BACKUPS\######\somefolder\ or \\data\media\clockworkmod\ .... (I am hazy on the path detail for CWM) You may need to use ES File Explorer to move the folder around if cwm is using 0\clockworkmod folder.
5. Reboot into recovery, select restore, and restore the nandroid file.
6. You should be booting into the earliest HTC OS for Rogers, Bell, Telus. (Your fastboot getvar all will still say 1.29.1540.3, this will change after an OTA)
7. Change your CID to Rogers001, BM___001, or TELUS001 accordingly in fastboot.
8. If you are rooted, either unroot supersu, or flash this file unroot-flashable.zip from recovery: http://goo.gl/JBmJVQ
9. Install stock recovery from fastboot http://goo.gl/Yzkwtl. Do a factory reset to verify that recovery has installed. You should NOT see CWM or TWRP during reset process.
10. Reboot back into OS and check for OTA, your OTA should come through and install itself, your fastboot getvar all should now result in the correct 1.29.x.17 main version.
11. At this time, you are stock, with S-Off and unlocked bootloader. If you want to continue further to lock bootloader and S-ON, start from step 9 in post 1.
Click to expand...
Click to collapse

Miscellaneous tips and tricks:
If you can NOT mount /sdcard in recovery
Download your Non-Canadian recoveries from: http://d-h.st/users/guich/?fld_id=29380#files or http://forum.xda-developers.com/showthread.php?t=2545227
Download Canadian 1.55 HBOOT recovery: http://goo.gl/2Kntxz
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<< Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to go now.
Click to expand...
Click to collapse
Radio/Modem files
Radio for Bell/Rogers/Telus for 3.x.x.x firmware (hboot 1.55): http://forum.xda-developers.com/showpost.php?p=46513020&postcount=12 - Tested
Radio fro Bell/Rogers/Telus for 1.x.x.x firmware (hboot 1.44): http://forum.xda-developers.com/showpost.php?p=45360195&postcount=5 - Not Tested
Click to expand...
Click to collapse

Thanks for the help! was looking for the nandroid back ups. will check back when you have the 1.44 written up. Is there a way i can upgrade my hboot to 1.55 from 1.44 in order to use the nandroid in post 1. If load the 1.29 nandroid my touch screen wont work and i need to go buy a otg cable in order to accept whats on the screen.

Thank You so much!!
I've been searching for the ROGERS RUU or Nandroid all day, new to Android so I didn't think of making a "nandroid" backup before flashing ROMs, but you saved me mate
Cheers!

Rogers htc one stuck on fastboot screen
Rogers htc one stuck on fastboot screen.

What have you tried so far? How did it get stuck?

Stuck on fastboot
SaHiLzZ said:
What have you tried so far? How did it get stuck?
Click to expand...
Click to collapse
Before following your instructions today, i relocked the bootloader and tried few exe and zip ruu yesterday. After that its stuck on fastboot screen.

What's the output of fastboot getvar all ?

SaHiLzZ said:
What's the output of fastboot getvar all ?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.631.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3983mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s

1. Unlock boot loader and download rogers nandroid and unzip.
2. Flash TWRP
3. Boot into TWRP
4. Run a fake backup. If it fails.. Got a SD card issue, let me know so I can guide you through it.
5. On computer type adb devices. Should come back with device in recovery mode
6. AD

6. Adb shell, then CD SDCARD, CD TWRP, CD BACKUP, note the path
7. Adb push rogersback \SDCARD\TWRP\BACKUPS\######\somefolder

Rogers Htc One stock rom
Thanks Sahilzz, I fixed it. Everything is back to normal. I was able to bring it back to stock rom.
Thanks a lot.

how do I install CWM I have twrp recovery. When I tried to install it. It said on CMD, but the phone keeps rebooting

Retry. Sometimes it takes a few tries for recovery to stick. Are you following post #2?
What's your fastboot getvar all output?

HELP! Blue screen, can't get past bootloader
I tried installing an OTA update that came through and now I am stuck on a blue screen. I can get to bootloader and fastboot but nothing I do can get past that. I want to return to stock or even just flash another ROM but I can't as my computer won't recognize the phone either. My HTC One is unlocked, S-On, TWRP recovery and HBOOT 1.44 . I've tried doing a fastboot getvar all but as I said, the computer won't recognize the phone so command prompt just sits there.

Move to a windows 7 machine and retry. Can't help if fastboot/adb doesn't work

SaHiLzZ said:
This guide is for Canadian HTC One Bell Rogers Telus users who need to go back to stock firmware for warranty after flashing custom recovery/rom. If you have installed Open EU, Google, Dev, ATT, or any other kind of RUU, see post #2.
Requirements:
1. Your HBOOT is 1.55.
2. You received OTA to JB 4.3 from Rogers Bell Telus
3. Your main version is 3.x.661.x, 3.x.666.x, 3.x.631.x,
4. Some working knowledge of ADB/Fastboot.
Steps to restore stock:
1. Download your respective nandroid backup from below:
Rogers Nandroid: Stock_JB_4.3_ROGER001_TWRP_3.22.631.1.zip - http://goo.gl/7702AM
Bell Nandroid: Stock_JB_4.3_BM___001_TWRP_3.23.666.1.zip - http://goo.gl/hw7Bj7
Telus Nandroid: Missing..
2. Download latest TWRP from: http://techerrata.com/browse/twrp2/m7
3. Reboot your device in fastboot and flash TWRP recovery. I used 2.6.3.0.
4. Reboot into recovery and do a backup of what you have working now (very important)
5. Boot back into OS
6. Unzip the nandroid backup folder and copy it to your \\SDCARD\TWRP\BACKUPS\######\somefolder\
7. Reboot back into TWRP, and restore the nandroid file
8. Reboot, your phone should be booting into your carrier firmware
9. Root
10. S-Off: Rumrunner thread, link: http://forum.xda-developers.com/showthread.php?t=2488772
11. Remove *Tempered* from boot thread, link: http://www.htc1guru.com/guides/guru-bootloader-reset/ OR http://forum.xda-developers.com/showthread.php?t=2477792
12. Verify all is WORKING OK, then flash stock recovery, Link: http://goo.gl/2Kntxz
13. S-On if you must, highly NOT suggested. command: fastboot oem writesecureflag 3
14. All should be good now.
Click to expand...
Click to collapse
Noob here
Step 9 says root.....what do you mean bu it?
Thanks

Install custom recovery, and root...

SaHiLzZ said:
Install custom recovery, and root...
Click to expand...
Click to collapse
Thanks......when should i relock bootloader?

Weaksauce vs rumrunner [SOLVED]

I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?

chris9486 said:
I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?
Click to expand...
Click to collapse
start by posting a "fastboot getvar all" (excluding IMEI and s/n), and what ROM are you running?

I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3884mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Pretty sure rumrunner won't work on 1.57. Either Firewater or sunshine

chris9486 said:
I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
Click to expand...
Click to collapse
@nateboi81 is right, your only options are:
a) sunshine (costs $25) on stock rom
or
b) firewater (free) on rooted ROM (and possibly bulletproof kernel)
if firewater gives you "whelp this sucks, etc" error then only sunshine will work

chris9486 said:
I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?
Click to expand...
Click to collapse
I s-off my rooted htc one hboot 1.57 using firewater. Must be on custom rom I think. Download link in case you need it, other links didn't work for me;
Firewater
- adb reboot <-- Important
- adb wait-for-device push firewater /data/local/tmp <--- When the phone restarts enter this
- adb shell
- su
- chmod 755 /data/local/tmp/firewater
- /data/local/tmp/firewater
Wait for prompt and type Yes, must be capital 'Y'

Thanks for the replies. I have just spent the best part of the last hour going through the guide I posted a link to. The links for htc1 guru do not work, keep timing out. And a lot of the stuff I don't understand which steps I need to take. The guide is great but not well structured for the less confident. I will just turn off the system updates on my phone and delete the update so it doesn't keep bugging me.
Firewater didn't work. It said I need to run it as SU or FU. I followed all the commands on the firewater s-off site.
From Firewater attempt. I am aware that $ in adb shell means it is not rooted. So I think there's just a big issue with if it is or not rooted. Like the original post, one says I am and one says I am not. So I am giving up!
C:\adb>adb devices
List of devices attached
S**************0 device
C:\adb>adb reboot
C:\adb>adb wait-for device push firewater /data/local/tmp
C:\adb>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $

chris9486 said:
Thanks for the replies. I have just spent the best part of the last hour going through the guide I posted a link to. The links for htc1 guru do not work, keep timing out. And a lot of the stuff I don't understand which steps I need to take. The guide is great but not well structured for the less confident.
Click to expand...
Click to collapse
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
chris9486 said:
Firewater didn't work. It said I need to run it as SU or FU. I followed all the commands on the firewater s-off site.
From Firewater attempt. I am aware that $ in adb shell means it is not rooted. So I think there's just a big issue with if it is or not rooted. Like the original post, one says I am and one says I am not. So I am giving up!
C:\adb>adb devices
List of devices attached
S**************0 device
C:\adb>adb reboot
C:\adb>adb wait-for device push firewater /data/local/tmp
C:\adb>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $
Click to expand...
Click to collapse
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)

nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)
Click to expand...
Click to collapse
Sorry, I didn't mean to offend you. The article is great like I said. Just sometimes there's some information about something else and I just couldn't work out if it applies or not. A little bit more description would help.
I thought about doing that but I am reluctant to fiddle about too much now. I'm being super cautious with all things technology wise. I lost a hard drive last week and then the backup of it two days later when I tried to put it on a new drive. Through no fault of my own and it's costing £540 for it to be recovered by a professional company. I don't want to f-up anything else because I can't afford another phone. My contract is up in Jan so I'll just stay on this till I can upgrade. My phone hasn't prompted me to upgrade ota again yet. So it's not a necessity to return to stock.

chris9486 said:
Sorry, I didn't mean to offend you. The article is great like I said. Just sometimes there's some information about something else and I just couldn't work out if it applies or not. A little bit more description would help.
Click to expand...
Click to collapse
I wasn't offended at all, just wondering what should be written differently.
chris9486 said:
I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
Click to expand...
Click to collapse
To get the wake gestures, you would need a custom kernel such as elementalX (possibly in conjunction with Xposed + Sense6Toolbox).

nkk71 said:
I wasn't offended at all, just wondering what should be written differently.
Click to expand...
Click to collapse
I like to think I am not stupid. But sometimes when I am using something new like adb, then I just daren't do something, since I have the possibility to wreck my phone.
This confused me. I didn't know if I had to reboot my phone or whether I needed to type reboot bootloader/fasboot usb into adb.
Reboot to bootloader/FASTBOOT USB, then:
fastboot getvar all
Then this confused me. I didn't know if I needed to do these?
Common downloads for all methods:
download CWM from here: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
rename the file to CWM.img (careful about .img.img in Windows)
this is originally from: http://forum.xda-developers.com/show....php?t=2173863
I'm using the 6.0.4.5 version because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.
download Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
----> if Guru Bootloader Reset gives you a hard time (freezes), use alternate method from FAQ #8
nkk71 said:
To get the wake gestures, you would need a custom kernel such as elementalX (possibly in conjunction with Xposed + Sense6Toolbox).
Click to expand...
Click to collapse
I realised after installing xposed and sense6toolbox that I needed a custom kernel. I was lost in a world of roms, roots, custom recovery, xposed and just gave up because I couldn't find out what I needed to do re. the kernel.
I am downloading ARHD and I am ready to flash it, I will try to s-off with firewater. If it doesn't work, I will just keep ARHD on and be fine till I can upgrade to a new phone. Not sure which one yet. Torn between Z2 and M8.

nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
Click to expand...
Click to collapse
Can I ask, is this the correct ruu for my phone mid and cid?

nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)
Click to expand...
Click to collapse
I downloaded arhd 31.6. Flashed. Cleared cache. Now I am stuck in a bootloop, cannot get into recovery and none of my computers will recognise the phone in ADB even though they did before!
I get nothing under adb devices.
:crying:

chris9486 said:
I like to think I am not stupid. But sometimes when I am using something new like adb, then I just daren't do something, since I have the possibility to wreck my phone.
This confused me. I didn't know if I had to reboot my phone or whether I needed to type reboot bootloader/fasboot usb into adb.
Reboot to bootloader/FASTBOOT USB, then:
fastboot getvar all
Click to expand...
Click to collapse
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
{
"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"
}
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
chris9486 said:
Then this confused me. I didn't know if I needed to do these?
Common downloads for all methods:
download CWM from here: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
rename the file to CWM.img (careful about .img.img in Windows)
this is originally from: http://forum.xda-developers.com/show....php?t=2173863
I'm using the 6.0.4.5 version because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.
download Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
----> if Guru Bootloader Reset gives you a hard time (freezes), use alternate method from FAQ #8
Click to expand...
Click to collapse
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
chris9486 said:
I realised after installing xposed and sense6toolbox that I needed a custom kernel. I was lost in a world of roms, roots, custom recovery, xposed and just gave up because I couldn't find out what I needed to do re. the kernel.
Click to expand...
Click to collapse
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
chris9486 said:
Can I ask, is this the correct ruu for my phone mid and cid?
Click to expand...
Click to collapse
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
chris9486 said:
I downloaded arhd 31.6. Flashed. Cleared cache. Now I am stuck in a bootloop, cannot get into recovery and none of my computers will recognise the phone in ADB even though they did before!
I get nothing under adb devices.
:crying:
Click to expand...
Click to collapse
did you check md5 on the download? also which recovery are you using (name and version)
adb only works in custom recovery, or booted up ROM with USB debugging enabled.
why can't you get to recovery?
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
then enter RECOVERY

nkk71 said:
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
Click to expand...
Click to collapse
Did you see my post above? I have now bricked my phone and a little stuck on how to get out of it. Please can you help?
I can enter bootloader. Go into fastboot. Connect to PC (W7). PC beeps, fastboot usb appears on the phone. ADB shows no devices! Rebooted pc on numerous occasions. Still no luck. I have uninstalled the drivers, installed HTC ones, reinstalled ADB etc, still nothing. It worked fine yesterday in ADB.
I cannot enter recovery either. I don't know what to do.

chris9486 said:
Did you see my post above? I have now bricked my phone and a little stuck on how to get out of it. Please can you help?
I can enter bootloader. Go into fastboot. Connect to PC (W7). PC beeps, fastboot usb appears on the phone. ADB shows no devices! Rebooted pc on numerous occasions. Still no luck. I have uninstalled the drivers, installed HTC ones, reinstalled ADB etc, still nothing. It worked fine yesterday in ADB.
I cannot enter recovery either. I don't know what to do.
Click to expand...
Click to collapse
I already answered above

nkk71 said:
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
did you check md5 on the download? also which recovery are you using (name and version)
adb only works in custom recovery, or booted up ROM with USB debugging enabled.
why can't you get to recovery?
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)​
then enter RECOVERY
Click to expand...
Click to collapse
I've never checked md5 in my life of using computers and the internet. I am an idiot I know.
ADB was working on fastboot USB in the bootloader yesterday. I didn't enter recovery once yesterday.
When I try to go to recovery (cwm) it just flashes for a second then reboots.
I will try the force reboot but not confident.

Do I try the force reboot when the phone is off, in the boot loop or in the bootloader. Because all three just send me back to the bootloader after about 10 seconds and none cause the phone to reboot.

nkk71 said:
I already answered above
Click to expand...
Click to collapse
Sorry I crossed posts, I wasn't sure if you'd seen it.
When it is in the bootloop it tries to enter recovery itself, it says something like no context file or something. It flashes for a second and that's it, it returns to a bootloop. It does the same if I try enter recovery from the bootloader.
When do I do the force reboot. No matter what I try it just enters the bootloader screen.

chris9486 said:
Sorry I crossed posts, I wasn't sure if you'd seen it.
When it is in the bootloop it tries to enter recovery itself, it says something like no context file or something. It flashes for a second and that's it, it returns to a bootloop. It does the same if I try enter recovery from the bootloader.
When do I do the force reboot. No matter what I try it just enters the bootloader screen.
Click to expand...
Click to collapse
please change your recovery to twrp 2.6.3.3 as mentioned below:
A) Having Problems? Rule #1: check MD5 on all your downloads; one single corrupt download can keep you trying for hours on end for nothing!
https://www.google.com/#q=MD5 ; Basically (in our context), MD5 checksums are to verify that the file you downloaded isn't corrupt
on Mac, Linux, and Android terminals it's already built in:
Mac: in terminal, just type md5 <name of file>
----> MD5 (<name of file>) = 12345678901234567890123456789012
Linux: in terminal, just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>
Android: in "adb shell", just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>
Windows (seems not built-in!?!?): you can use programs such as http://winmd5.com/ , http://implbits.com/hashtab.aspx , http://www.pc-tools.net/win32/md5sums/ or any other one of your choosing.
C) Problems installing a ROM (in particular 4.4+ versions, and getting permission/set_metadata errors)
for M7_U/UL models, get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
Note: at the time of this writing these are the most reliable versions, even the 2.7.x.x series seem to still have problems
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY and install the ROM​

[Q] Messed up trying to wipe / update. Need a hand

Here's the details. Phone was rooted in 2013. I have my unlockcode.bin file saved from then.
I wanted to install a new ROM and reaslied I needed to be on a new kernal for it to work.
I tried to update using the standard options menu on the phone, didn't work, just looped.
So I backed up my media to PC, at present I can happily lose everything on the phone and go back to square 1.
I ended up looking at Team Win recovery project V2.6.3.3 which is what was used when I originally rooted it, I decided the best thing to do is was to select wipe all.
Looks like I removed the OS too as it just shows the logo when I boot normally, but I can access the bootloader menu and team win recovery menu.
Phone is connected to my PC and I have the Android SDK working and can connect to my phone using the CMD promt.
Please help, I'm computer literate but useless with phones.
Thanks

Is the phone s-off? Did you make any backups with twrp before you wiped?

ANGRY_robert said:
Is the phone s-off? Did you make any backups with twrp before you wiped?
Click to expand...
Click to collapse
I don't know what S-off means.
I did have backups on the phone but they've obviously been wiped. I have a file called backup.ab on my computer so I hope I can somehow use that

Look at your bootloader screen. At the very top under "unlocked" it will either say M7_Ux PVT SHIP S-ON or S-OFF.
You did have backups, but never copied any to a pc......

Niall44 said:
I don't know what S-off means.
I did have backups on the phone but they've obviously been wiped. I have a file called backup.ab on my computer so I hope I can somehow use that
Click to expand...
Click to collapse
download a rom and push it to your phone, then install it using twrp. Instructions posted below:
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 anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt 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

ANGRY_robert said:
Look at your bootloader screen. At the very top under "unlocked" it will either say M7_Ux PVT SHIP S-ON or S-OFF.
You did have backups, but never copied any to a pc......
Click to expand...
Click to collapse
It says M7-UL PVT SHIP S-ON RH
I take it this is bad.
As for the backups, are you saying the backup.ab file on my PC is useless?

alray beat me to it. Follow the instructions in his post. S-ON is not bad, it's standard (security on). Just can be a bit limiting depending upon the situation.

alray said:
download a rom and push it to your phone, then install it using twrp. Instructions posted below:
​
Click to expand...
Click to collapse
Looks promising, I will try this now. Will my choice of rom be affected by the fact my phone was on an old kernal? Something like 4.1.1 iirc

Niall44 said:
Looks promising, I will try this now. Will my choice of rom be affected by the fact my phone was on an old kernal? Something like 4.1.1 iirc
Click to expand...
Click to collapse
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.

When you say kernel 4.1.1, I think you mean android os jellybean and not kernel. I'm trying to not confuse you here. Try and find an older rom on here that is based off jellybean and go from there.
---------- Post added at 06:38 PM ---------- Previous post was at 06:36 PM ----------
alray beat me again. I think I'll leave you in his hands.

alray said:
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.
Click to expand...
Click to collapse
ANGRY_robert said:
When you say kernel 4.1.1, I think you mean android os jellybean and not kernel. I'm trying to not confuse you here. Try and find an older rom on here that is based off jellybean and go from there.
---------- Post added at 06:38 PM ---------- Previous post was at 06:36 PM ----------
alray beat me again. I think I'll leave you in his hands.
Click to expand...
Click to collapse
Understood about kernals, I'm used to modded xbox's so I assumed the term would translate.
Having trouble reading the info, it keeps crashing or just hanging with "waiting for device".
I think it's more a problem my end with faulty USB ports. I'll have to try it on another PC

alray said:
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.
Click to expand...
Click to collapse
Got it.
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.61.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4075mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s

Niall44 said:
Got it.
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.61.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4075mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
Click to expand...
Click to collapse
There is not much useful files on the web fo orange (x.xx.61.x). If you want to update your firmware to the latest version to ensure the best stability with newer Roms, you could flash an older rom and s-off your phone using Revone. Then you'll be free to flash a newer firmware even if its not based on x.xx.61.x, the latest x.xx.401.x firmware should do the job ( I think its 6.09.401.11 or .12)

alray said:
There is not much useful files on the web fo orange (x.xx.61.x). If you want to update your firmware to the latest version to ensure the best stability with newer Roms, you could flash an older rom and s-off your phone using Revone. Then you'll be free to flash a newer firmware even if its not based on x.xx.61.x, the latest x.xx.401.x firmware should do the job ( I think its 6.09.401.11 or .12)
Click to expand...
Click to collapse
Thanks for looking, so I need to find a rom with x.xx.61.x or lower in the title and install that to get started?

Niall44 said:
Thanks for looking, so I need to find a rom with x.xx.61.x or lower in the title and install that to get started?
Click to expand...
Click to collapse
no and you won't find roms based on x.xx.61.x anyway there are usually based on x.xx.401.x (international version)
arhd 31.6 will work fine on your current firmware version,
Then if you want to achieve S-OFF, all you will need is to follow instructions in Revone thread.

alray said:
no and you won't find roms based on x.xx.61.x anyway there are usually based on x.xx.401.x (international version)
arhd 31.6 will work fine on your current firmware version,
Then if you want to achieve S-OFF, all you will need is to follow instructions in Revone thread.
Click to expand...
Click to collapse
Marvelous. I got the ROM installed and working. I'll start on the S-Off, updating and fancy new ROM tomorrow. But it's way past my bedtime.
Thank you very much for being patient

Glad we, uhm .... I mean alray could help.

ANGRY_robert said:
Glad we, uhm .... I mean alray could help.
Click to expand...
Click to collapse
your help is also appreciated mate :good: keep up good work

Can't seem to get Revone to work. File is in the correct directory but I'm getting error 1 when I try "./revone -P"
I saw in another thread that installing another ROM would help, but it didn't. So I've reflashed the arhd 31.6 ROM I was given but can't seem to get any headway into getting it to work.

Trying to achieve s-off has different methods. Each method is a little different. It all depends on what hboot version you are running. Your hboot version is displayed on the bootloader screen.
Examples: 1.44, 1.54, 1.56, 1.57
See what your version is and report back.

HTC One M7 Stuck in a Boot Loop

Alright, I recently purchased a phone that was stuck at the screen with the download icon in the arrow circle (http://forum.xda-developers.com/album.php?albumid=11886). When it is like this is can not be put into hboot. I then somehow got the phone into a boot loop. I did wipe the cache and that did not fix the problem. I did a factory reset via hboot, and it sent me back to the screen I mentioned before (http://forum.xda-developers.com/album.php?albumid=11886). I've now gotten the phone back into boot looping so I can access hboot. Recovery does work and you can access all the options. This phone is basically a stock HTC One M7. Has not been rooted, is locked, and it S-ON. Any help would be appreciated.
Thank you!

Flash a RUU

jdgreat4 said:
Flash a RUU
Click to expand...
Click to collapse
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?

CloudHD said:
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?
Click to expand...
Click to collapse
post the output of "fastboot getvar all", remove your imei and serialno before posting it

alray said:
post the output of "fastboot getvar all", remove your imei and serialno before posting it
Click to expand...
Click to collapse
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.

CloudHD said:
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.
Click to expand...
Click to collapse
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?

alray said:
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?
Click to expand...
Click to collapse
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.

CloudHD said:
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.
Click to expand...
Click to collapse
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later

alray said:
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

CloudHD said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:

Danny201281 said:
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:
Click to expand...
Click to collapse
Followed your instructions. Everything went good. I did a factory reset and the phone actually ended up rebooting. It's now just sitting here, and seems to be stuck at the htc logo. Going to go ahead and follow the steps to unlock my bootloader then report back.

@Danny201281 Boot loader is now unlocked!

CloudHD said:
@Danny201281 Boot loader is now unlocked!
Click to expand...
Click to collapse
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient

Danny201281 said:
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient
Click to expand...
Click to collapse
Thank you! My friend wanted to ask about soff and root for his device

CloudHD said:
Thank you! My friend wanted to ask about soff and root for his device
Click to expand...
Click to collapse
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.

Danny201281 said:
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.
Click to expand...
Click to collapse
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220

CloudHD said:
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220
Click to expand...
Click to collapse
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes

Danny201281 said:
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes
Click to expand...
Click to collapse
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.

CloudHD said:
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.
Click to expand...
Click to collapse
Reboot Recovery and then copy over and install the rom :good:
When you format data it is like repartitioning the phone. All the partitions are gone until you reboot. That's the reason they won't mount

Danny201281 said:
Reboot Recovery and then copy over and install the rom :good:
Click to expand...
Click to collapse
Alright, Thank you very much!!!
Will update how it all wetn when finished.

[Q] ADB can't find phone

So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44) as that is needed to update the firmware however it cannot connect to my phone either (same adb problem)
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables. I've tried uninstalling and reinstalled different HTC drivers, I also tried installing the google usb drivers.
I need helps

Cofffey said:
So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in
Click to expand...
Click to collapse
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
To achieve s-off on hboot 1.44 use Revone
as that is needed to update the firmware
Click to expand...
Click to collapse
S-OFF is only needed if you flash a custom firmware.
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables.
Click to expand...
Click to collapse
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps[/QUOTE]

alray said:
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
To achieve s-off on hboot 1.44 use Revone
S-OFF is only needed if you flash a custom firmware.
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps
Click to expand...
Click to collapse
[/QUOTE]
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive

Cofffey said:
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive
Click to expand...
Click to collapse
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.

alray said:
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.
Click to expand...
Click to collapse
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?

Cofffey said:
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?
Click to expand...
Click to collapse
you are s-off now?

alray said:
you are s-off now?
Click to expand...
Click to collapse
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)

Cofffey said:
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)
Click to expand...
Click to collapse
Change your CID to GOOGL001:
boot in bootlaoder / fastboot usb mode
using fastboot enter these commands:
Code:
fastboot oem writecid GOOGL001
fastboot reboot-bootloader
Then confirm your cid is now GOOGL001:
Code:
fastboot oem readcid
output must be "GOOGL001"
reboot in ruu mode:
Code:
fastboot oem rebootRUU
flash this firmware, not the one you have linked above:
Code:
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot reboot-bootloader
then reflash twrp:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot in recovery, push the GPE rom to your phone and flash it. Reboot and your phone should boot in the 5.1 rom (first boot can take up to 10-15 mins, will be stuck at htc splash screen)
Dont forget to backup your important files before, the firmware flash will wipe your phone.

alray said:
Wait, I'll make some modification to the firmware so it can be flashed on your phone and I'll send it to you in a few minutes.
Click to expand...
Click to collapse
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?

Cofffey said:
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?
Click to expand...
Click to collapse
see edited post above. (#8)

alray said:
see edited post above. (#8)
Click to expand...
Click to collapse
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?

Cofffey said:
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?
Click to expand...
Click to collapse
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)

alray said:
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)
Click to expand...
Click to collapse
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?

Cofffey said:
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?
Click to expand...
Click to collapse
If you need some of elementalX features then yes flash it, you can always revert back to the previous kernel that comes with the rom by extracting it from the rom.zip and flashing it using fastboot:
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
ElementalX kernel must be flashed in recovery.