Database Develop

[Q] Stuck on HBoot during Unroot

Hello,
Last week I rooted my HTC One and installed the Android Revolution HD ROM. Although I loved it, I needed to get back to stock ROM. I followed a YouTube video to unroot my mobile and now it's stuck on HBoot screen. I've tried various RUU and Recover.zip's but no go. Please help!!
Thank you in advance.
Details:
(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.707.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367W901515
(bootloader) imei: 354435054464524
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4014mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0

Which RUU did you try and how did it fail?
Your version-main is they key.

Stuck on HBoot during unrooting - HTC One
BenPope said:
Which RUU did you try and how did it fail?
Your version-main is they key.
Click to expand...
Click to collapse
Hello Ben,
Thank you for writing. I'd like you to know that I'm not very techie... This RUU 'RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16' failed, and these recoveries: 2013-03-30.16.15.27, and a few more. I've been looking for my One's version main (1.29.707.17) and don't seem to have any luck. Thank you for your assistance.
Is there anyway I could downgrade or install a custom ROM? Anything to bring One back to life....
Currently, One is stuck on this screen: **Tampered** **Relocked** **Security Warning*

You'll need twrp recovery to install this backup
http://bugsylawson.com/files/file/1841-m7-twrp-nandroid-backup-cid-htc-044-12970716/

Stuck on HBoot during unrooting - HTC One
BenPope said:
You'll need twrp recovery to install this backup
Started download. Thanks, Ben. Could you point me to a step-by-step article for this recovery please?
Also, when I click 'Recovery', the phone just reboots...
Click to expand...
Click to collapse

Look in the original development section for the twrp recovery thread?
Also try
fastboot erase cache
That should sort your recovery out.

Stuck on HBoot during unrooting - HTC One
BenPope said:
Look in the original development section for the twrp recovery thread?
Also try
fastboot erase cache
That should sort your recovery out.
Click to expand...
Click to collapse
Thank you, Ben. You give me hope!! I had almost given up
I'll try the recover and revert shortly. Thanks again!

Stuck on HBoot during unrooting - HTC One
mirali7 said:
Thank you, Ben. You give me hope!! I had almost given up
I'll try the recover and revert shortly. Thanks again!
Click to expand...
Click to collapse
Ben, bad news. I did a quick read on TWRP and ran these commands. It failed. Since I couldn't find a img file, I used a .win. Please tell if I made a mistake. (new in Android world...)
fastboot.exe erase cache
erasing 'cache'... OKAY [ 0.519s]
finished. total time: 0.520s
fastboot.exe flash recovery system.ext4.win
sending 'recovery' (932728 KB)... OKAY [104.691s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 174.315s

Flashing random files is probably a bad idea. You need stock recovery.

Stuck on HBoot during unrooting - HTC One
BenPope said:
Flashing random files is probably a bad idea. You need stock recovery.
Click to expand...
Click to collapse
How do I perform a stock recovery? Please assist

RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16 is a developer RUU .. Your device MID (PN0711000) and CID (HTC__038) suggest it's an asian device ..
try installing this and update via OTA .. and remember, do not install any RUU other than x.xx.709.x ..

Do s-off and flash the ruu, that will give you full stock
Sent from my HTC One™

Rocker19943 said:
Do s-off and flash the ruu, that will give you full stock
Sent from my HTC One™
Click to expand...
Click to collapse
Rocker, can I do a S-Off when I'm stuck on the **Tampered** **Relocked** **Warning Security** screen? How? Please assist.

mirali7 said:
Rocker, can I do a S-Off when I'm stuck on the **Tampered** **Relocked** **Warning Security** screen? How? Please assist.
Click to expand...
Click to collapse
Thank you, Shahriar. Will try the same and revert

S-off
mirali7 said:
Thank you, Shahriar. Will try the same and revert
Click to expand...
Click to collapse
You need S-off and then need to change your CID to 11111111. That's the super CID and then
you can flash any stock firmware.
CC

I had Warning Security screen, i didnt know the reason of it, but it disappeared after unlocking bootloader again, so now try to unlock it using htcdev binary and your phone will boot up normally! Then do your job, but if you want to lock it again, use revone

Rocker19943 said:
I had Warning Security screen, i didnt know the reason of it, but it disappeared after unlocking bootloader again, so now try to unlock it using htcdev binary and your phone will boot up normally! Then do your job, but if you want to lock it again, use revone
Click to expand...
Click to collapse
Rocker, I'm 2 weeks into Android and I'm unsure of how to unlock using HTC Binary. Can you point me to a helpful article please?

rhtzshahriar, I downloaded the RUU but am unable to run it. The exe just doesn't start up. I've tried double-clicks, from cmd, run-as administrator. Rebooted laptop as well. Please advice

mirali7 said:
rhtzshahriar, I downloaded the RUU but am unable to run it. The exe just doesn't start up. I've tried double-clicks, from cmd, run-as administrator. Rebooted laptop as well. Please advice
Click to expand...
Click to collapse
Hi, I've started to download the following files:
RUU_M7_U_JB_50_hTC_Asia_TW_1.20.709.101_Radio_4A.13.3227.06_10.27.1127.01_release_307831_signed_2_4.exe
PN07IMG_M7_U_JB_50_hTC_Asia_TW_1.29.709.4.zip
Please see the screenshots of my phone. I'm unable to write anything from fastboot. But fastboot can read\detect my phone (fastboot devices). Any assistance is highly appreciated.

cc999 said:
You need S-off and then need to change your CID to 11111111. That's the super CID and then
you can flash any stock firmware.
CC
Click to expand...
Click to collapse
Hi, I'm unable to S-Off the device. When I run adb push revone /data/local/tmp/ - I get "device not found" error. Please assist

[Q] Returning to stock for warranty repair

Hi All,
I want to return ENTIRELY to stock so that it is untraceable that I ever wasn't on stock. I have to send my phone to HTC for repair and do not want to be charged for the repairs.
I appreciate there are many threads for this, mainly this one: http://forum.xda-developers.com/showthread.php?t=2358738
However I wanted to confirm this will work for me and be untraceable. I understand I can provide you with information about my phone which may be required?
Any assistance greatly appreciated.

Jimzoaar said:
Hi All,
I want to return ENTIRELY to stock so that it is untraceable that I ever wasn't on stock. I have to send my phone to HTC for repair and do not want to be charged for the repairs.
I appreciate there are many threads for this, mainly this one: http://forum.xda-developers.com/showthread.php?t=2358738
However I wanted to confirm this will work for me and be untraceable. I understand I can provide you with information about my phone which may be required?
Any assistance greatly appreciated.
Click to expand...
Click to collapse
you can also check out my guide: http://forum.xda-developers.com/showthread.php?t=2541082
and see if that makes sense to you
Let me know if you have questions.

nkk71 said:
you can also check out my guide: http://forum.xda-developers.com/showthread.php?t=2541082
and see if that makes sense to you
Let me know if you have questions.
Click to expand...
Click to collapse
Thank you.
Currently backing up, will kick it off after. Should this be undetectable by HTC?

Jimzoaar said:
Thank you.
Currently backing up, will kick it off after. Should this be undetectable by HTC?
Click to expand...
Click to collapse
if you have s-off, you'll be able to run a full ruu (and possibly restore a nandroid backup, depending on which method you're using), and be able to remove TAMPERED set the phone to LOCKED and even go S-On, if you really insist.
==> result, the phone is 100% "out of the box"
If you are going to go S-On, please follow the guide properly, because it has to be done at a specific point in time, too soon is BAD, too late is BAD!
if you need more help, post a "fastboot getvar all" (remove IMEI and s/n), either here or in the guide and i'll help out as best i can.

nkk71 said:
if you have s-off, you'll be able to run a full ruu (and possibly restore a nandroid backup, depending on which method you're using), and be able to remove TAMPERED set the phone to LOCKED and even go S-On, if you really insist.
==> result, the phone is 100% "out of the box"
If you are going to go S-On, please follow the guide properly, because it has to be done at a specific point in time, too soon is BAD, too late is BAD!
if you need more help, post a "fastboot getvar all" (remove IMEI and s/n), either here or in the guide and i'll help out as best i can.
Click to expand...
Click to collapse
Excellent, thank you.
I am S-OFF. I will provide full details below.
Sorry, I wasn't too clear in my original question, can you also confirm that once I FULLY go back to stock (s-on included) and HTC repair it, that i can then go back to rooted with a custom ROM?
Please see details below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3942mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Also, just to confirm, that now I am S-off I can proceed with downgrading the HBOOT by runing the 1.44 exe?
Many thanks.

Jimzoaar said:
Excellent, thank you.
I am S-OFF. I will provide full details below.
Sorry, I wasn't too clear in my original question, can you also confirm that once I FULLY go back to stock (s-on included) and HTC repair it, that i can then go back to rooted with a custom ROM?
Click to expand...
Click to collapse
You should be able to unlock it again using HTCdev, and then rumrunner S-Off.
Jimzoaar said:
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
finished. total time: 0.068s
Also, just to confirm, that now I am S-off I can proceed with downgrading the HBOOT by runing the 1.44 exe?
Many thanks.
Click to expand...
Click to collapse
Yes, you can go ahead and continue following the guide.
Best to use the CWM recovery I posted in post #7 as other versions have some issues when used in "fastboot boot CWM.img" mode.
As for the S-On part, please follow the guide exactly, you go S-Off to S-On, after the 1st successful OTA update, but BEFORE any update to 3.xx; because in 3.xx (hboot 1.55) going S-Off to S-On will result in a "tamper detected - rebooting" and TAMPERED is back.
By the way, from what I've read, the UK carriers & repair centers are very lenient, and don't really care about S-Off etc. especially if it's a hardware issue; but then again it's your decision.

nkk71 said:
You should be able to unlock it again using HTCdev, and then rumrunner S-Off.
Yes, you can go ahead and continue following the guide.
Best to use the CWM recovery I posted in post #7 as other versions have some issues when used in "fastboot boot CWM.img" mode.
As for the S-On part, please follow the guide exactly, you go S-Off to S-On, after the 1st successful OTA update, but BEFORE any update to 3.xx; because in 3.xx (hboot 1.55) going S-Off to S-On will result in a "tamper detected - rebooting" and TAMPERED is back.
By the way, from what I've read, the UK carriers & repair centers are very lenient, and don't really care about S-Off etc. especially if it's a hardware issue; but then again it's your decision.
Click to expand...
Click to collapse
Thanks for your prompt and detailed response.
Just to clarify, I presume you mean Android 3.x.x. I hope you understand me questioning this because obviously the HTC one was shipped with Android4.0+. Am I right in querying whether this is still going to work?
Many thanks.

Jimzoaar said:
Thanks for your prompt and detailed response.
Just to clarify, I presume you mean Android 3.x.x. I hope you understand me questioning this because obviously the HTC one was shipped with Android4.0+. Am I right in querying whether this is still going to work?
Many thanks.
Click to expand...
Click to collapse
no, 3.x.x refers to the software number, not the android version. If ur going to complete stock and if u are gonna change S-OFF TO S-ON, then change it to S-ON bfor u install the 4.3 update. Preferably, as soon as the RUU restore completes, do the S-ON procedure first.

nkk71, i would appreciate your help as well if you could help me to identify which RUU to download because I am really confused with so many versions of RUU. I would like to go back to stock to claim warranty on the camera's purple tint issue. BTW, im running on TWRP recovery.
Thank you in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35WW9*****
(bootloader) imei: 3558590502*****
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4142mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

raghav kapur said:
no, 3.x.x refers to the software number, not the android version. If ur going to complete stock and if u are gonna change S-OFF TO S-ON, then change it to S-ON bfor u install the 4.3 update. Preferably, as soon as the RUU restore completes, do the S-ON procedure first.
Click to expand...
Click to collapse
Where can I check this? I am patient and will gladly check at multiple steps to ensure I am doing it at the correct one.
Also, I will be using the CWM nandroid method, can you confirm you mean after step one when I have installed the Sense 5 RUU?

nkk71 said:
if you have s-off, you'll be able to run a full ruu (and possibly restore a nandroid backup, depending on which method you're using), and be able to remove TAMPERED set the phone to LOCKED and even go S-On, if you really insist.
==> result, the phone is 100% "out of the box"
If you are going to go S-On, please follow the guide properly, because it has to be done at a specific point in time, too soon is BAD, too late is BAD!
if you need more help, post a "fastboot getvar all" (remove IMEI and s/n), either here or in the guide and i'll help out as best i can.
Click to expand...
Click to collapse
Please see below response when trying to flash the 1.44 HBoot (this is with s-off)
Do you have any ideas?
C:\Users\james.mildren>fastboot flash zip C:\Users\james.mildren\Desktop\1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.246s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.732s

Jimzoaar said:
Where can I check this? I am patient and will gladly check at multiple steps to ensure I am doing it at the correct one.
Also, I will be using the CWM nandroid method, can you confirm you mean after step one when I have installed the Sense 5 RUU?
Click to expand...
Click to collapse
see, you will be able to check this only once ur RUU restore is complete. Once u can boot into the stock firmware, go to Settings-About-Software Information-Software Number.
---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------
hmgan said:
nkk71, i would appreciate your help as well if you could help me to identify which RUU to download because I am really confused with so many versions of RUU. I would like to go back to stock to claim warranty on the camera's purple tint issue. BTW, im running on TWRP recovery.
Thank you in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35WW911268
(bootloader) imei: 355859050240456
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4142mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
go to this link http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/

Jimzoaar said:
Please see below response when trying to flash the 1.44 HBoot (this is with s-off)
Do you have any ideas?
C:\Users\james.mildren>fastboot flash zip C:\Users\james.mildren\Desktop\1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.246s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.732s
Click to expand...
Click to collapse
yes, no problem, just change CID (you're going to have to do it anyway for the RUU):
fastboot oem writecid HTC__001 <- two underscores
fastboot reboot-bootloader
then downgrade hboot will work just fine.

nkk71 said:
yes, no problem, just change CID (you're going to have to do it anyway for the RUU):
fastboot oem writecid HTC__001 <- two underscores
fastboot reboot-bootloader
then downgrade hboot will work just fine.
Click to expand...
Click to collapse
I am now recieving the below after changing CID to HTC__001, thank you for your previous response, any ideas on this?
C:\Users\james.mildren>fastboot flash zip C:\Users\james.mildren\Desktop\1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.247s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.284s

Jimzoaar said:
Thanks for your prompt and detailed response.
Just to clarify, I presume you mean Android 3.x.x. I hope you understand me questioning this because obviously the HTC one was shipped with Android4.0+. Am I right in querying whether this is still going to work?
Many thanks.
Click to expand...
Click to collapse
I'm referring to the base version, which starts at
1.xx (for Android 4.1.2)
2.xx (for Android 4.2.2)
3.xx (for Android 4.3)
---------- Post added at 05:21 PM ---------- Previous post was at 05:20 PM ----------
Jimzoaar said:
I am now recieving the below after changing CID to HTC__001, thank you for your previous response, any ideas on this?
Click to expand...
Click to collapse
didnt see any output.
---------- Post added at 05:27 PM ---------- Previous post was at 05:21 PM ----------
Jimzoaar said:
I am now recieving the below after changing CID to HTC__001, thank you for your previous response, any ideas on this?
C:\Users\james.mildren>fastboot flash zip C:\Users\james.mildren\Desktop\1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.247s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.284s
Click to expand...
Click to collapse
have you "fastboot oem rebootRUU"?
Don't want to sound nasty or anything, but please make sure you've read through the guide once or twice (including post #7 which has command outputs and examples).

nkk71 said:
I'm referring to the base version, which starts at
1.xx (for Android 4.1.2)
2.xx (for Android 4.2.2)
3.xx (for Android 4.3)
---------- Post added at 05:21 PM ---------- Previous post was at 05:20 PM ----------
didnt see any output.
---------- Post added at 05:27 PM ---------- Previous post was at 05:21 PM ----------
have you "fastboot oem rebootRUU"?
Don't want to sound nasty or anything, but please make sure you've read through the guide once or twice (including post #7 which has command outputs and examples).
Click to expand...
Click to collapse
Not nasty at all, believe it or not I actually work in IT support and understand your frustrations when people don't listen. A small note though, obviously I seem to have hit a stumbling block on most steps, I know this sounds incredibly noobish, but also that is what these guides are aimed at, it may be reiterating that you either need to be in or re enter the RUU mode for certain steps, as obviously applying different fixes to bespoke problems leaves you in a different place to the guide which relys on it going smoothly.
Anyway, you are a genius, as expected, and that has worked. I will let you know of any more issues, thank you again for your help.

Jimzoaar said:
Not nasty at all, believe it or not I actually work in IT support and understand your frustrations when people don't listen. A small note though, obviously I seem to have hit a stumbling block on most steps, I know this sounds incredibly noobish, but also that is what these guides are aimed at, it may be reiterating that you either need to be in or re enter the RUU mode for certain steps, as obviously applying different fixes to bespoke problems leaves you in a different place to the guide which relys on it going smoothly.
Anyway, you are a genius, as expected, and that has worked. I will let you know of any more issues, thank you again for your help.
Click to expand...
Click to collapse
no problem, let me know how everything goes.
Good luck and remember not to rush things

nkk71 said:
no problem, let me know how everything goes.
Good luck and remember not to rush things
Click to expand...
Click to collapse
So I have now changed my CID and flashed CWM recovery, when trying to push the backup i get the follow:
C:\Users\james.mildren>adb push c:\users\james.mildren\desktop\2013-04-20.21.00.
00 /data/media/clockwordmod/backup/2013-04-20.21.00.00
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\james.mildren>adb push c:\users\james.mildren\desktop\2013-04-20.21.00.
00 /data/media/clockwordmod/backup/2013-04-20.21.00.00
push: c:\users\james.mildren\desktop\2013-04-20.21.00.00/system.ext4.tar.b -> /d
ata/media/clockwordmod/backup/2013-04-20.21.00.00/system.ext4.tar.b
failed to copy 'c:\users\james.mildren\desktop\2013-04-20.21.00.00/system.ext4.t
ar.b' to '/data/media/clockwordmod/backup/2013-04-20.21.00.00/system.ext4.tar.b'
: No such file or directory
Any ideas?

Jimzoaar said:
So I have now changed my CID and flashed CWM recovery, when trying to push the backup i get the follow:
C:\Users\james.mildren>adb push c:\users\james.mildren\desktop\2013-04-20.21.00.
00 /data/media/clockwordmod/backup/2013-04-20.21.00.00
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\james.mildren>adb push c:\users\james.mildren\desktop\2013-04-20.21.00.
00 /data/media/clockwordmod/backup/2013-04-20.21.00.00
push: c:\users\james.mildren\desktop\2013-04-20.21.00.00/system.ext4.tar.b -> /d
ata/media/clockwordmod/backup/2013-04-20.21.00.00/system.ext4.tar.b
failed to copy 'c:\users\james.mildren\desktop\2013-04-20.21.00.00/system.ext4.t
ar.b' to '/data/media/clockwordmod/backup/2013-04-20.21.00.00/system.ext4.tar.b'
: No such file or directory
Any ideas?
Click to expand...
Click to collapse
1- you mean booted into CWM not "flashed CWM recovery" right!!
2- are you using CWM 6.0.4.5 (the one i suggested in post 7), other versions have some issues with certain adb commands in "boot" mode
3- try updating adb & fastboot: http://goo.gl/T6InE
4- I recommend you put all files & folders in a short path, such as "C:\ADB" that would avoid long filename problems
try those and let me know

nkk71 said:
1- you mean booted into CWM not "flashed CWM recovery" right!!
2- are you using CWM 6.0.4.5 (the one i suggested in post 7), other versions have some issues with certain adb commands in "boot" mode
3- try updating adb & fastboot: http://goo.gl/T6InE
4- I recommend you put all files & folders in a short path, such as "C:\ADB" that would avoid long filename problems
try those and let me know
Click to expand...
Click to collapse
1 - Sorry, yes I did try the original way (booting into CWM not flashing) and when i got the aforementioned error I tried flashing, for your info I have now reflashed TWRP and am using CWM only to boot from.
2 - No I wasnt, I was user 6.0.4.6, I have now downgraded and still receive the same error.
3 - Fully updated
4- I am for the most part using my desktop, I know it just leads to more chance of an error but I have made sure there are no typos.
Just a quick query, I cannot perform the adb push when in CWM recovery....is that right? When I am in CWM my HTC does not show on the list of attached devices either. I have to boot into system before the push returns the above error, is that correct?

[SOLVED] No imei and ROM install seems incomplete

Hi all,
First, i would like to apologize for my poor english.
Then, i have some problems with my HTC M7.
Yesterday, when i woke up, my phone was shut down. I thought that i had no battery anymore. (i had less than 10% when i went to bed so, it's possible).
Well, plug my phone in the charger, and wait... and, when he booted, i could not use my phone as usually: no PIN code, no ability to make phone call... After a few minutes, i saw that the IMEI zone was empty.
I was not worrying, and though that a simple cache cleearing could help me... Well, it was not...
Now, i'm not able to use my phone AT ALL.
He's rooted, S-OFF, and i tried to install 3 or 4 different roms but same problem.
The ROM install has some difficulties to be finished: in fact, on each rom i tried to install, i have now the same problem;
-> No IMEI
-> When i want to compose a phone number, the dialer does not appear
-> A message "com.htc.htcdialer isn't responding" appears every minute...
I tried to install another dialer, same problem...
I'm really lost.
hope that somebody could help me?
Regards,
Cyril
PS: For information, after the incident, my phone was not rooted anymore and was S-ON, i don't know if it was already the case before the incident...

UPDATE: Finally, i succeed to install a rom.
Everything works fine now, but still no imei present...

This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.

Slim Shady said:
This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.
Click to expand...
Click to collapse
Hi,
I've just started to work, but i will send you these informations as soon as possible.
Thanks a lot.

Slim Shady said:
This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.
Click to expand...
Click to collapse
Re Slim Shady,
Here are the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm not sure about what to do.
May i have to switch on s-on? Or relock the bootloader?
I don't really know how to install a new firmware...

an idea?

Leodagan said:
Re Slim Shady,
Here are the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm not sure about what to do.
May i have to switch on s-on? Or relock the bootloader?
I don't really know how to install a new firmware...
Click to expand...
Click to collapse
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .

Slim Shady said:
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .
Click to expand...
Click to collapse
just a quick note, he's s-off, personally I would go with a 1.xx ruu (except 1.20.xxx.x)

Slim Shady said:
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .
Click to expand...
Click to collapse
Done for IMEI and Serial NO, thx.
I've started to download it.
nkk71 said:
just a quick note, he's s-off, personally I would go with a 1.xx ruu (except 1.20.xxx.x)
Click to expand...
Click to collapse
Ok, so have i to switch on s-on?
Also, have i stay on unlocked mode?
Thanks guys, really.

Guys,
I tried to install the RUU but it failed:
Update from 3.62.1700.1 to 4.19.401.9, i click on next, then next, then a message (in french so i translate to you):
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
Then, i can only click on ReadMe or Recovery, but nothing relevant after that.

Leodagan said:
Ok, so have i to switch on s-on?
Click to expand...
Click to collapse
Nooooo, do not go s-on!!

nkk71 said:
Nooooo, do not go s-on!!
Click to expand...
Click to collapse
Ok, i haven't done that, thanks ^^
So, now i'm stucked, i don't know what to do. Try another ruu?
I'm actually downloading RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe, is it ok?

Well, it's not ok, with this rom too i can't update my phone...
Maybe should i have to find a 3.62 RUU in order to update?

Leodagan said:
Well, it's not ok, with this rom too i can't update my phone...
Maybe should i have to find a 3.62 RUU in order to update?
Click to expand...
Click to collapse
What do you mean, can't update... you mean the ruu isn't working?
if so, then get this one: ruu_m7ul_1.28.401.7.zip
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
then (after making sure MD5 is correct), rename the file to ruu.zip, and:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
there is no need to relock bootloader or anything else with S-OFF (and stay S-OFF, don't even think about S-On!!)
if you want to see what kind of output to expect, check my guide http://forum.xda-developers.com/showthread.php?p=47794257&postcount=8 (post 8) which has a some visual feedback of what to expect. (disregard the guide, i'm just linking it for you to get an idea of what kind of output to expect)
Oh and you cannot do this on Win 8.1!!! http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 FAQ#1

nkk71 said:
What do you mean, can't update... you mean the ruu isn't working?
Click to expand...
Click to collapse
Yep, same message than the other ruu:
Update from 3.62.1700.1 to 1.2*******, i click on next, then next, then a message :
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
I'll try your last post, i let you know when finished.

Leodagan said:
Yep, same message than the other ruu:
Update from 3.62.1700.1 to 1.2*******, i click on next, then next, then a message :
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
I'll try your last post, i let you know when finished.
Click to expand...
Click to collapse
HELL YES IT WORKS!!!
Thank you thank you !!
(well for the moment i'm in 4.1.2, i will wait a moment before flashing a new recovery, a new rom and all the stuff :laugh::laugh::laugh

Leodagan said:
HELL YES IT WORKS!!!
Thank you thank you !!
(well for the moment i'm in 4.1.2, i will wait a moment before flashing a new recovery, a new rom and all the stuff :laugh::laugh::laugh
Click to expand...
Click to collapse
and IMEI, baseband etc are all working again?

Yep, all is functional again... thanks again !

Leodagan said:
Yep, all is functional again... thanks again !
Click to expand...
Click to collapse
:good: :good: my pleasure.
BTW, if you going for 4.4 ROMs, use TWRP: 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)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
PS: for future reference about s-off vs s-on, check here http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 (under Not so FAQ #2)
if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title

Done.
Thank you again, guys.

I need help with my htc m7

Actually its my friends mobile. it was on a custom rom . It has a "tampered unlocked" bootloader. He wanted to go back for stock rom so i relocked the bootloader and now i cant turn on it to flash from RUU. now i want to know how can i go back to previous rom or how to flash stock rom. Please needed help

kolithakasun said:
Actually its my friends mobile. it was on a custom rom . It has a "tampered unlocked" bootloader. He wanted to go back for stock rom so i relocked the bootloader and now i cant turn on it to flash from RUU. now i want to know how can i go back to previous rom or how to flash stock rom. Please needed help
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
Please remove the IMEI and Serial numbers before posting :good:
Sent from my HTC One using Tapatalk

Danny201281 said:
Can you please post the output of
Code:
fastboot getvar all
Please remove the IMEI and Serial numbers before posting :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Hey, I'm still lurking if you need anything you know what to do.
 @alray still around ? I see @nkk71 in the M9 forums on occasion
Code:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: *******************
(bootloader) version-main: 1.32.617.6
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US002
all:
finished. total time: 0.013s
C:\adb>adb devices
:silly::silly::silly: :good:

clsA said:
Hey, I'm still lurking if you need anything you know what to do.
@alray still around ? I see @nkk71 in the M9 forums on occasion
Code:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: *******************
(bootloader) version-main: 1.32.617.6
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US002
all:
finished. total time: 0.013s
C:\adb>adb devices
:silly::silly::silly: :good:
Click to expand...
Click to collapse
Hello mate , I'll be heading to the M9 forums soon. Should get my upgrade in a week or so. Was thinking of going with the M8 but probably will take the M9
Sent from my HTC One using Tapatalk

Danny201281 said:
Hello mate , I'll be heading to the M9 forums soon. Should get my upgrade in a week or so. Was thinking of going with the M8 but probably will take the M9
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
the M9 forums are dead compared to the action here back in the day. it's a Great phone though, just not very popular.
I think we lost a bunch of people to the samsung s6 / note 5 / s6+ / nexus / lg G4 / Moto x pure/style ...ect ect

clsA said:
Hey, I'm still lurking if you need anything you know what to do.
@alray still around ? I see @nkk71 in the M9 forums on occasion
:silly::silly::silly: :good:
Click to expand...
Click to collapse
Yep still here

Danny201281 said:
Can you please post the output of
Code:
fastboot getvar all
Please remove the IMEI and Serial numbers before posting :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
After unlocking the bootloader its booted again. thank you for your reply

clsA said:
Hey, I'm still lurking if you need anything you know what to do.
@alray still around ? I see @nkk71 in the M9 forums on occasion
Code:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: *******************
(bootloader) version-main: 1.32.617.6
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US002
all:
finished. total time: 0.013s
C:\adb>adb devices
:silly::silly::silly: :good:
Click to expand...
Click to collapse
wrong place, this is for the HTC One M7, you have a HTC One M9 :silly::silly::silly::cyclops::cyclops:
havent had much time lately, been travelling quite a bit, and now i need to catch up on some work
not to mention my old laptop died, so reinstalling all the programs and moving everything to a new laptop, is an excessivly time consuming thing imo
hope you guys are all doing well :fingers-crossed:

Help - Bricked HTC One (M7) - No Recovery - No Operating System - Only Fastboot

Close this thread mod.
I will move to my old thread: http://forum.xda-developers.com/htc-one/help/planning-to-buy-bricked-htc-one-m7-t3376521

MihailMojsoski said:
So, my HTC One M7 is bricked.
This is all the information:
I can get ONLY into fastboot and hboot.
The is is all the data from the phone when i go to hboot:
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.18.161.51
eMMC-boot 2048MB
Nov 18 2015, 13:59:56.22095
Recovery is not working,
also when i start the phone it boots to HBOOT or FASTBOOT
Click to expand...
Click to collapse
And what was done to the phone before it got bricked?

alray said:
And what was done to the phone before it got bricked?
Click to expand...
Click to collapse
Don't know.
I got this phone from a friend.
Edit: Also when i try to flash recovery i get error:
FAILED (remote: signature verify fail)

MihailMojsoski said:
Don't know.
I got this phone from a friend.
Click to expand...
Click to collapse
So this is the broken phone you was planning to buy like you have explained in your other thread, why creating a new thread for this? You already have one with post #2 reserved by yourself for this purpose....
"your friend" probably relocked the bootloader with a custom recovery/rom installed. The phone can't boot custom software when the bootloader is locked. You'll have to unlock the bootloader or flash a ruu.
If a custom recovery was installed you'll probably not be able to unlock it since the unluck process requires the stock recovery installed on the phone.
This phone is s-on so you can only flash ruu same or newer version as the current version installed and unfortunately there is no ruu for this version. There's a way to bypass this but you'll need a custom working custom recovery......
Let's try to unlock your bootloader first using htcdev.com then report in your original thread and close this one.
Sent from my HTC One using XDA Labs
Edit: Also when i try to flash recovery i get error:
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
The bootloader is locked, you can't flash the recovery partition on a locked bootloader.

alray said:
So this is the broken phone you was planning to buy like you have explained in your other thread, why creating a new thread for this? You already have one with post #2 reserved by yourself for this purpose....
"your friend" probably relocked the bootloader with a custom recovery/rom installed. The phone can't boot custom software when the bootloader is locked. You'll have to unlock the bootloader or flash a ruu.
If a custom recovery was installed you'll probably not be able to unlock it since the unluck process requires the stock recovery installed on the phone.
This phone is s-on so you can only flash ruu same or newer version as the current version installed and unfortunately there is no ruu for this version. There's a way to bypass this but you'll need a custom working custom recovery......
Let's try to unlock your bootloader first using htcdev.com then report in your original thread and close this one.
Sent from my HTC One using XDA Labs
The bootloader is locked, you can't flash the recovery partition on a locked bootloader.
Click to expand...
Click to collapse
Hey, so i tried finding the right RUU but i failed.
Also this is my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT**********
(bootloader) imei: ***HIDE***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Edit: Also would this work: https://www.androidfilehost.com/?fid=24052804347763901
Edit2: I tried unlocking the bootloader, but when i selected "YES", it got stucked on a screen with 3 androids and when i pressed the power button it vibrated. I will try again but i will give it some time, and i will tell you if it will work.

Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.

monrokhoury said:
Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.
Click to expand...
Click to collapse
I unlocked the phone, but i fail to install a recovery.
Code:
C:\Users\User\Desktop>fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9594 KB)...
OKAY [ 1.227s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.338s

monrokhoury said:
Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.
Click to expand...
Click to collapse
Also i live in Macedonia, so i can't send them the phone.
I can only fix it manually.