[HELP] Unlock bootloader without OEM Unlock (Phone doesn't start)

[HELP] Unlock bootloader without OEM Unlock (Phone doesn't start) - HTC Desire 10 Questions & Answers

¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.

CheckS86 said:
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Click to expand...
Click to collapse
did you get the solution ?? I'm in the same situation help

CheckS86 said:
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Click to expand...
Click to collapse
did u find the solution? i have the same problem with my note 20 ultra cant start the phone and the OEM is ON (L)

Wow. With a little more time another user (HTC U11+) enters the queue of the mishaps! Any Luck anyone? HTCDev also seem to have given up with no option to login to their website.

Related

[Q] Google Nexus One Stuck into boot screen

Hi Guys, i my Google nexus one stuck on boot screen.i had read lots of post on XDA to solve this problem but not able to solve.
My Nexus one has unlocked bootloader.
I flash recovery from fastboot and it successfully flashed.
but when i try to boot into recovery mode, device stuck on boot screen with lock symbol below, which denots unlock bootloader.
Please can any buddy tell what the problem or how can it flash custome rom into it .
Thanks .

try wipe all partition again
Code:
fastboot -w
fastboot erase recovery
fastboot reboot-bootloader
and reflash recovery
must use 4ext recovery
Edited: fixed

Replace hboot with fastboot in the above commands
Sent from my Nexus 4 using xda premium

HTC Nexus One Problems- All Self-inflicted
demkantor said:
Replace hboot with fastboot in the above commands
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hi, First off, I'm so damn new I don't even qualify yet to be called "Noob". I bought an HTC Nexus One on eBay and it was loaded with 2.3.4. But I could not get it to update. I then took a look at the build # "3.11.405.2CL81940" with "release keys" added in a line below. Google came up with two or three hits, all starting with "Weird Build....", so I decided to get rid of it by rooting the phone. Over three days of fooling around with it and I am asking for help: after doing ALL KINDS OF THINGS (can't even remember the sequence), I'm stuck with a phone which when powered on no longer goes to the "X" splash screen but to "htc" with small yield signs with exclamation points in the four corners of the screen. The only way to power it down is to remove the battery. If I connect it to my Windows PC, it is recognized (I've downloaded the drivers, SDK Manager and AVD Manager) and I can perform certain functions using the command line within the SDK. But I can't format and start all over with a "stock" release let alone Jelly Bean which was my goal when starting all this. Additional information I can provide: when I remove the phone from the USB, the Black "htc" screen disappears and a white screen replaces it with the following: Line 1) BlackRose-Made by LeCache dl95244; line 2) STOCK 145/95/196; line 3) NEXUS ONE PV(or U)T S-off; line 4) HBOOT 7.3.5.5017 (PB9910000); line 4) TOUCHPANEL SYNT0103; line 5) RADIO-5.12.00.00; line 6) Apr 21 2012, 04:53:16; line 7) RUU. Line one, "BlackRose...", is black with white characters. Lines 2-6 are green characters on a white background (resembling the old boot screen) and finally, line 7, the "RUU" characters are white in an orange background, as though it's highlighted, asking for something. As said above, no buttons work (Track ball, Vol up/Vol down), and this is where the battery has to be pulled to power it down. Can anyone help?? I'll do my best to reply with any specifics that I DO remember, but I've done so many, many things in the past three days I've lost track. Thanks.

When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium

In response to your question:
demkantor said:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Let me describe it from the start. After insuring the device is fully charged I power it off the only way I can, pulling the battery, waiting 5 seconds, then reassembling the battery and back.
I get out the USB cord and insert it into the Windows PC. Then, (either powered on BEFORE insertion of the Micro USB or AFTER), when the device is powered on it goes to a new splash screen with "htc" in white on a gray/black background with caution signs at each corner of the screen. The device will stay that way for hours, plugged into a PC or powered on without tethering. THE ONLY WAY to access the white screen (which resembles the old boot screen without skateboards) is to unplug the device from the USB/PC WHILE POWERED ON.
When you do this, you have the "BlackRose" in white on a black line, then the rest as described, with "RUU" in orange.
There is one additional detail I do remember doing: I downloaded and installed "HTC One (M7//T-Mobile/AT&T/Sprint) AIO Kit by Hasoon2000v2.1 and Flashed CWM (GSM Only) Recovery. That was the last time the screen was at all responsive: lot's of lines rolling upward and then the words, I think, "Update failed".
Hasoon2000, I believe, is a member of this Forum and lives in Orland Park, IL, a suburb frustratingly close to me, in Chicago!!
---------- Post added at 07:02 AM ---------- Previous post was at 06:55 AM ----------
demkantor said:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Short answer, yes: Device Manager recognizes it and I hear a "cer-chunk" when its plugged in.

now you can enter bootloader or not?

bootloader
hxq88 said:
now you can enter bootloader or not?
Click to expand...
Click to collapse
Yes. I can access bootloader. Just finished the following:
fastboot device HT0ALP801351
---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------
rickz41 said:
Yes. I can access bootloader. Just finished the following:
fastboot devices HT0ALP801351
Click to expand...
Click to collapse
OKAY [ 4.628s]
formatting 'userdata' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 2.230s]
formatting 'cache' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.019s]
finished. total time: 6.903s
C:\android-sdk\platform-tools>fastboot erase r
erasing 'recovery'...
OKAY [ 0.097s]
finished. total time: 0.099s
C:\android-sdk\platform-tools>

its ok . did you run commands in post #2?
let try full wipe all and try it from beginning 1 more time. or use PASSIMG method to fast restore stock rom.
edit: ok full wiped, now reflash recovery ( try 4ext or TWRP, sorry i dont know link, you can find in search forum )

Post 2
rickz41 said:
Yes. I can access bootloader. Just finished the following:
fastboot device HT0ALP801351
---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------
OKAY [ 4.628s]
formatting 'userdata' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 2.230s]
formatting 'cache' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.019s]
finished. total time: 6.903s
C:\android-sdk\platform-tools>fastboot erase r
erasing 'recovery'...
OKAY [ 0.097s]
finished. total time: 0.099s
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse
Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.

rickz41 said:
Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.
Click to expand...
Click to collapse
wrong command: it must be fastboot reboot-bootloader

command
hxq88 said:
wrong command: it must be fastboot reboot-bootloader
Click to expand...
Click to collapse
Success!!
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.028s]
finished. total time: 0.029s
C:\android-sdk\platform-tools>
(Phone powered off- heard PC disconnect then reconnect, now screen is still same: whit "htc", black background with caution marks, all four corners....

enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.
let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why )
edit: its the name of recovery, i miss some letter cuz fast type

additional info
hxq88 said:
enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.
let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why )
Click to expand...
Click to collapse
Here I must repeat, I am not even Newbie or Noob- I am less than Noob!! What is 4ext, TWRP?? I will download them and do as you say but give detailed instructions for I am only an infant!! (when it comes to this, at least!)
---------- Post added at 10:55 AM ---------- Previous post was at 10:09 AM ----------
THANK YOU SO VERY MUCH FOR GETTING ME THIS FAR!!
It is greatly appreciated.
I will leave for awhile now, but thank you again.

Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.
That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier
fastboot erase system -w
fastboot erase boot
fastboot flash recovery recovery.img
Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point
If you want to learn more about fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium

Progress thus far:
demkantor said:
Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.
That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier
fastboot erase system -w
fastboot erase boot
fastboot flash recovery recovery.img
Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point
If you want to learn more about fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you for joining in and I must say at that I am in complete agreement with your feelings re: apple/MAC/iOS, etc.: they can go to Hell.
Let me post the results after following your instructions above:
C:\android-sdk\platform-tools>fastboot erase system -w
erasing 'system'...
OKAY [ 3.406s]
erasing 'userdata'...
OKAY [ 4.608s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.023s]
erasing 'cache'...
OKAY [ 2.223s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.022s]
finished. total time: 10.293s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.054s]
finished. total time: 0.057s
C:\android-sdk\platform-tools>fastboot flash recovery recovery-RA-passion-v2.2.1
.img
sending 'recovery' (3366 KB)...
OKAY [ 0.483s]
writing 'recovery'...
OKAY [ 1.082s]
finished. total time: 1.570s
But the n1 is still showing the gray/black splash with htc and the caution/yield signs at the corner. The line: "Erase successful, but not automatically formatting. Can't determine partition type." when erasing user data and formatting cache, is this something to be looked into?
I've flashed, I believe, successfully, AmonRa before but when I try to flash a 'Stock' passion image, it fails.
I'll continue reading your most helpful guides and hope for a step-by-step reply- I feel as though I am very close to solving this!
Again, many thanks!

Update
Sorry to report I've not made any progress since my last post despite the Guides provided.
A couple important points:
a) I cannot enter to cmd prompt level, fir whatever reason
b) This leave me with Fastboot and when the device is again wiped and prepared, Fastboot is entered, and I type Fastboot update update.zip with the following results attempting different "Stock Passion Images":
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 7.35.5017
Baseband Version.....: 5.12.00.08
Serial Number........: HT0ALP801351
--------------------------------------------
checking mid...
OKAY [ 0.003s]
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is '7.35.5017'.
Update requires '0.35.2017' or '0.35.0017'.
finished. total time: 0.047s
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 7.35.5017
Baseband Version.....: 5.12.00.08
Serial Number........: HT0ALP801351
--------------------------------------------
checking mid...
OKAY [ 0.003s]
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is '7.35.5017'.
Update requires '0.35.2017' or '0.35.0017'.
finished. total time: 0.047s
Any further thoughts??
Also, USB debugging is OFF complicating thins a lot, preventing me from getting a token from HTC's site!!

Bootloader should be unlocked being you have black rose, try different RUUs
http://forum.xda-developers.com/showthread.php?p=7495397
You may also try to change your cid to 11111111 this will allow you to flash any version
Sent from my Nexus 4 using xda premium

Questions:
How would I change cid ?
I've been searching the universe for RUU's and came up with one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe . That's it. in your link I see a number of Factory Images. Which would you suggest?
---------- Post added at 03:03 PM ---------- Previous post was at 02:48 PM ----------
rickz41 said:
How would I change cid ?
I've been searching the universe for RUU's and came up with one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe . That's it. in your link I see a number of Factory Images. Which would you suggest?
Click to expand...
Click to collapse
Took the advice here:
http://forum.xda-developers.com/showthread.php?t=2264322
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
HT0ALP801351 fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files\Android\android-sdk\platform-tools>
---------- Post added at 03:20 PM ---------- Previous post was at 03:03 PM ----------
C:\Program Files\Android\android-sdk\platform-tools>cd c:\mini-adb
The system cannot find the path specified.
C:\Program Files\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
HT0ALP801351 fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvarcid
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 7.35.5017
(bootloader) version-baseband: 5.12.00.08
(bootloader) version-cpld: None
(bootloader) version-microp: 0c15
(bootloader) version-main: 2.16.405.1
(bootloader) serialno: HT0ALP801351
(bootloader) product: nexusone
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9910000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4162mV
(bootloader) partition-layout: STOCK-145/95/196
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 0c3a097c
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.024s
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem writecid 111111
11
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem writecid 111111
11
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 7.35.5017
(bootloader) version-baseband: 5.12.00.08
(bootloader) version-cpld: None
(bootloader) version-microp: 0c15
(bootloader) version-main: 2.16.405.1
(bootloader) serialno: HT0ALP801351
(bootloader) product: nexusone
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9910000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4162mV
(bootloader) partition-layout: STOCK-145/95/196
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 0c3a097c
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.019s
C:\Program Files\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.026s
C:\Program Files\Android\android-sdk\platform-tools>
It rebooted back to the same ole' 'htc' screen!

Try
fastboot oem getvar cid
To read it and
fastboot oem write cid 11111111
To write
As for which ruu to pick I'm not sure, never ran one on my n1, I did see a thread not to long ago where someone was trying to grab every official update from HTC, you can also try HTC directly and try to find the latest one
Sent from my Nexus 4 using xda premium

Stuck in Bootloader

I got this used HTC one. I had google edition ROM on it when I got it. Then I flashed AR HD Rom on it. Everything was going fine till I decided to flash the latest firmware since I wanted to go to ARHD 30 and everyone seems to recommend to flash the new firmware.
I was going thru the normal steps and saw that I need to relock my device. I did this:
C:\Program Files\Android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.110s
After this I noticed that I had relocked written in fastboot mode even though it said failed. So tried the next step:
C:\Program Files\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.040s
C:\Program Files\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (28338 KB)...
OKAY [ 2.566s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.843s
And any step that I try it fails. The most unfortunate thing is I can only boot in fastboot & bootloader mode. I can't go in recovery neither can I boot normally. These are my phone details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(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: 4137mV
(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.057s
I looked up online tried flashing recovery but now any step that I try to do in fastboot fails with following message:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I saw in some places people mentioned to use RUU. Not sure what it is but if some one can point me to a correct RUU or let me know any other steps it would be greatly appreciated. My phone is almost bricked now since i can't go past fastboot/bootloader.

awaitforitb said:
(bootloader) version-bootloader: 1.44.0000
Click to expand...
Click to collapse
You have no idea how lucky you are. Before you do anything, get S-OFF using revone. Just go into CWM (or re-flash recovery) so you can use adb. Once you have s-off, follow my guide :
This guide requires S-OFFImportant
*** If there are files you need to keep, you can always use adb pull to get them out before hand (let's say a nandroid backup or something important)
This guide assumes you have knowledge about how adb and fastboot command work and that your HTC drivers are up to date.
I am in NO WAY responsible for any possible damage that may happen to your phone, I am only trying to help
Start your phone in bootloader by typing
Code:
adb reboot bootloader
or by other means.
Select "Fastboot" so that it appears in red instead of HBOOT
On your computer, make sure fastboot sees your device, then type
Code:
fastboot erase cache
Type
Code:
fastboot erase cache
Type
Code:
fastboot erase userdata
Type
Code:
fastboot erase system
Type
Code:
fastboot erase linux
Type
Code:
fastboot erase recovery
Type
Code:
fastboot erase cache
Type
Code:
fastboot reboot-bootloader
Download the new firmware.zip
Type
Code:
fastboot oem rebootRUU
Once it's rebooted on a silver HTC logo, type :
Code:
fastboot flash zip [pathonyourcomputer/firmware.zip]
Wait until it is done on your computer. The green line on the phone will never reach the end.
Type
Code:
fastboot reboot-bootloader
Reflash your recovery (I recommend CWM). Might as well play it safe.
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Reboot into recovery (select the option in fastboot)
Wipe data/factory reset (you will loose everythng)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
Now you have 2 options :
Push (Preferred)
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !
Sideload (If you can't push for some reason)
Select "Install zip"
Select "Install zip from sideload"
Type
Code:
adb sideload [path/rom.zip]
Voila ! You should be good to go !

attanasi0 said:
You have no idea how lucky you are. Before you do anything, get S-OFF using revone. Just go into CWM (or re-flash recovery) so you can use adb. Once you have s-off, follow my guide :
Click to expand...
Click to collapse
@awaitforitb:
I agree with the S-Off part, just check the date of your bootloader it has to be pre June 2013. Also, in order for revone to work you need a functioning ROM (4.1.2... 4.3 will NOT work). Do you have one functioning device, or are you "stuck in bootloader" as the title says.
You could run the RUU found on androidruu http://www.androidruu.com/?developer=M7, I believe yours would be http://www.androidruu.com/getdownlo....20_10.40.1150.04_release_326691_signed_2.exe
That's an exe you run directly from your PC, and it will walk you through the steps, this will wipe your phone completely! and restore everything back to 100% stock.
After that you should get S-Off, and then proceed to whatever your end goal is.
@attanasi0 just a couple of questions, why do you recommend all the "fastboot erase userdata/linux/system/recovery" ?
Also, please remember that when using "fastboot flash zip <name of firmware>.zip", in most cases, you have to do it twice after each other, the first will push the zip and say "failed, flush image again" (or something along those lines), the second flash will actually start the installation and should report success.
I usually use firmwares from @vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506 as they have the dzdata files removed, as well as the stock boot.img and recovery.img removed.

nkk71 said:
@attanasi0 just a couple of questions, why do you recommend all the "fastboot erase userdata/linux/system/recovery" ?
Also, please remember that when using "fastboot flash zip <name of firmware>.zip", in most cases, you have to do it twice after each other, the first will push the zip and say "failed, flush image again" (or something along those lines), the second flash will actually start the installation and should report success.
I usually use firmwares from @vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506 as they have the dzdata files removed, as well as the stock boot.img and recovery.img removed.
Click to expand...
Click to collapse
You're about pushing the zip at first, forgot about that.
I honestly don't know why I recommend that. I guess it's to make sure the phone is a clean slate and no conflict will be created TL;DR : Paranoia

Problem bootloader shows in OS-

The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
On the device ViperOne running 3.5.0 (4.3)
Now to the problem:
Flashing a recovery is performed, also displayed as OK, but it remains the old (TWRP 2.6.3.3)
Bootloader not lock possible:
(bootloader) Lock successfully ...
(boot loader) mipi display off
(boot loader) mipi_dsi_cmds_tx_ext
(boot loader) pm8921_vreg_disable function, vreg_id = 38
(boot loader) pm8921_vreg_disable function, vreg_id = 1
(boot loader) TZ_HTC_SVC_DISABLE ret = 534 642 044 (0x1FDDFD7C)
(boot loader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.139s
Flashing via sideload possible, unfortunately, according to Rome, it passes through or terminates. After the restart, but is ancient Rome it.
Getvar all the following shows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3893mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.047s
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you

Fooox1 said:
The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you
Click to expand...
Click to collapse
So if I understand correctly, you don't like the fact that firmware version not showing up; so I guess you have a couple of options:
1- (recommended in my opinion) get s-off using rumrunner
2- download this OTA: http://www.htc1guru.com/dld/ota_m7_..._p_release_325133_signedlqk8p6c09r7kmir2-zip/
and extract the "firmware.zip" inside, then flash that in fastboot ruu mode (TWICE in a row)
(you may need to relock bootloader for that)

Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.

Fooox1 said:
Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.
Click to expand...
Click to collapse
rumrunner should work just fine, but you're not on 4.3 (firmware); you're hboot 1.54 would imply that you are running a 2.24 firmware, so you need a ROOTED 2.24 ROM with unsecured kernel; try this one: oops, looks like mega is down at the moment
find a 2.24 based ROM, rooted, with unsecured kernel, and rumrunner should work fine. maybe try Maximus 10 or 11: http://llabtoofer.com/category/devices/htc-one/page/2/

However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.

Fooox1 said:
However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.
Click to expand...
Click to collapse
1- I understand your current ROM is 4.3, but that has nothing to do with firmware; firmware is <empty>, but hboot is 1.54, so it implies a 2.24 ROM.
2- to get rumrunner to work, you will need a 2.24 RUM
3- can you please boot to bootloader screen and make sure it says UNLOCKED (a screenshot would be nice )

So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.

Fooox1 said:
So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.
Click to expand...
Click to collapse
keep bootloader UNLOCKED!!
download TWRP 2.6.3.0: http://techerrata.com/browse/twrp2/m7
verify MD5
go to bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, then flash one of the maximus 10 or 11 roms.
then go for rumrunner.

Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.

Fooox1 said:
Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.
Click to expand...
Click to collapse
sounds too much like a locked bootloader, would you mind copy/paste command prompt, for example:
Code:
C:\ADB2>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/COLOR][/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\ADB2>

No problem:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C: \ Windows \ system32> cd ..
C: \ Windows> cd ..
C: \> cd fastboot
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.

Fooox1 said:
No problem:
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.
Click to expand...
Click to collapse
1- yes, i am aware that it can be renamed, though I usually just type the first letter of the filename (for example "o") and then press tab, eg:
Code:
C:\ADB2>fastboot flash recovery o
then press TAB, and:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
2-
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
Click to expand...
Click to collapse
mine gives me a lot more info:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
3- 8432KB

What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made a backup is running, I want to restore it, is nothing.

Fooox1 said:
What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made a backup is running, I want to restore it, is nothing.
Click to expand...
Click to collapse
thanks for your kind comments, can i ask one more thing: MD5 of your "recovery.img"

The MD 5 Total:
84F04BFE70C03825689A457009235AD4

Fooox1 said:
The MD 5 Total:
84F04BFE70C03825689A457009235AD4
Click to expand...
Click to collapse
hmm, interesting I now have two versions of 2.6.3.0, one 10570KB and one 8432KB, but both worked fine:
Code:
C:\ADB2>fastboot flash recovery "openrecovery-twrp-2.6.3.0-m7 (2).img"
sending 'recovery' (8432 KB)...
OKAY [ 1.216s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.897s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.059s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.054s
-> bootloader -> recovery and it's there
have you tried using the unlocktocken again? maybe the phone is "semi-locked"

Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?

Fooox1 said:
Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?
Click to expand...
Click to collapse
1- so i just tried the lock command:
Code:
C:\ADB3>[B]fastboot oem lock[/B]
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.126s
--> it rebooted back to the ROM, i went back to bootloader and sure enough it said RELOCKED
2- "I have the internal SD card into suspicion", we could check the partitions, but I doubt that it has anything to do with it, otherwise you would be experiencing a lot of random reboots.
3- also, have you tried other "tools" that work in custom recovery, such as: http://forum.xda-developers.com/showthread.php?t=1646108
just to see if recovery is working
4- did you flash any "boot.img" (kernel)?
5- have you tried "fastboot oem unlock"
6- have you tried flashing firmware (extracted from signed OTA) in ruu mode as mentioned in post #2?

2 The suspicion arises for me, since deleted, can be moved, but the device is, after rebooting, does not run or crashes. I have already backup, Rom.zip placed on the SD, but after rebooting into recovery they're gone.
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
4 I have already tried e.g. from Vodafone Rome. As usual, Ok, Ok, but not adopted.
5 At the command fastboot oem unlock:
C: \ fastboot> fastboot oem unlock
... INFO [ERR] Command error!
OKAY
6 I have tried (OTA_M7_UL_JB_50_Vodafone_UK_1.29.161.11-1.28.161.7_release_315813_signedoj2qp335qmm8qjso) unzipped and used the firmware.zip.
Have the One_All-in One_Kit tried using the. But yes you use Flash Factory RUU zip. In this case, however, the device can not connect. About sideload's not the point. Will be transmitted to mobile phones, but the flash stops.
I also tried to flash the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe . Device is detected and goes to the black screen (HTC ), of course aborts then , since it is not the correct CID .

Fooox1 said:
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
Click to expand...
Click to collapse
It almost sounds like a secured kernel, can u post exact details of the ROM you're running, including link.
Did u ever flash a "boot.img" ?
Sent from my HTC One using Tapatalk

[Q] Bricked HTC One M7 after attempting to restore to stock using YouTube video guide

I am looking for some help in getting my HTC One M7 back up and working.
I used the online Cyanogenmod installer on my at&t HTC One M7 and it worked for the most part including where it contacts the HTC site to place the phone in developer mode.
Unfortunately the radio was far weaker and was losing it's signal all the time. I tried a few nightly's in hopes it was a bug that would be addressed but the issue with radio strength continued. Then an alert about an update from Cyanogen popped up and I trustingly clocked OK thinking that perhaps THIS would fix the radio stregth issue and I can keep my rooted ROM. Instead it broke Bluetooth entirely.
So I watched a YouTube video on restoring to stock. Apparently I can't post the link,
I got all the way to the part where I use fastboot to install the zip, HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
It failed but not in the manner described in the video I believe it is due to the phone security set to S-ON but I have yet to find a way to set it back to S-OFF from where things are now.
This was the steps from the video I followed starting with fastboot getvar version-main and the fastboot oem lock
I then went through the following commands
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.054s
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
sending 'zip' (1249780 KB)...
OKAY [ 47.434s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.191s
And so it failed. The HTC screen came up but there was no progress bar so I know that fast boot is talking to the phone. I have been looking for a fix ever since and I am presently using a flip phone while working on getting the HTC One back.
Presently the phone boots directly into fastboot and will not allow me to do anything but reboot or power down but I can still use fastboot.
Revolutionary just sits at waiting for device.
The HTC One Toolkit is of no use as it also cannot see the device.
This is what is on the screen presently. Any help would be appreciated.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048MB
Apr 22 2014,01:10:58.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is the results for fastboot getvar all
C:\fastboot>fastboot getvar all
(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) serialno: XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4290mV
(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
all: Done!
finished. total time: 0.048s

TexMachina said:
I am looking for some help in getting my HTC One M7 back up and working.
I used the online Cyanogenmod installer on my at&t HTC One M7 and it worked for the most part including where it contacts the HTC site to place the phone in developer mode.
Unfortunately the radio was far weaker and was losing it's signal all the time. I tried a few nightly's in hopes it was a bug that would be addressed but the issue with radio strength continued. Then an alert about an update from Cyanogen popped up and I trustingly clocked OK thinking that perhaps THIS would fix the radio stregth issue and I can keep my rooted ROM. Instead it broke Bluetooth entirely.
So I watched a YouTube video on restoring to stock. Apparently I can't post the link,
I got all the way to the part where I use fastboot to install the zip, HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
It failed but not in the manner described in the video I believe it is due to the phone security set to S-ON but I have yet to find a way to set it back to S-OFF from where things are now.
This was the steps from the video I followed starting with fastboot getvar version-main and the fastboot oem lock
I then went through the following commands
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.054s
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
sending 'zip' (1249780 KB)...
OKAY [ 47.434s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.191s
And so it failed. The HTC screen came up but there was no progress bar so I know that fast boot is talking to the phone. I have been looking for a fix ever since and I am presently using a flip phone while working on getting the HTC One back.
Presently the phone boots directly into fastboot and will not allow me to do anything but reboot or power down but I can still use fastboot.
Revolutionary just sits at waiting for device.
The HTC One Toolkit is of no use as it also cannot see the device.
This is what is on the screen presently. Any help would be appreciated.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048MB
Apr 22 2014,01:10:58.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is the results for fastboot getvar all
C:\fastboot>fastboot getvar all
(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) serialno: HT3xxxxxxxxxxxxxx
(bootloader) imei: 354xxxxxxxxx
(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: 4290mV
(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
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Ok
First thing .. edit your post above and remove the Serialno and IMEI
second the file you downloaded is my TWRP Backup and has to be restored using TWRP ...not flashed
it would be easier for you to use the Guru Reset I made
here >> http://www.androidfilehost.com/?fid=23501681358545274
So unlock your bootloader and flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload the Guru Reset from within TWRP
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
Ok
First thing .. edit your post above and remove the Serialno and IMEI
Click to expand...
Click to collapse
Whooops!
Thanks for the heads up on that. I'll get to work on the fix and post an update later.

I am getting the signature verify fail error when attempting to load the recovery image now. Is this due to security being set on, S-ON?
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.
3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.116s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.863s
I made sure the images were in the fastboot directory.
Directory of C:\fastboot
08/23/2014 12:56 PM <DIR> .
08/23/2014 12:56 PM <DIR> ..
04/05/2012 05:49 AM 162,816 adb.exe
04/05/2012 05:49 AM 96,256 AdbWinApi.dll
04/05/2012 05:49 AM 70,144 fastboot.exe
08/23/2014 12:48 PM 986,880,264 Guru_Reset_M7_5.12.502.2_clsA.zip
08/23/2014 12:42 PM 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
5 File(s) 996,613,896 bytes

TexMachina said:
I am getting the signature verify fail error when attempting to load the recovery image now. Is this due to security being set on, S-ON?
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.
3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.116s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.863s
I made sure the images were in the fastboot directory.
Directory of C:\fastboot
08/23/2014 12:56 PM <DIR> .
08/23/2014 12:56 PM <DIR> ..
04/05/2012 05:49 AM 162,816 adb.exe
04/05/2012 05:49 AM 96,256 AdbWinApi.dll
04/05/2012 05:49 AM 70,144 fastboot.exe
08/23/2014 12:48 PM 986,880,264 Guru_Reset_M7_5.12.502.2_clsA.zip
08/23/2014 12:42 PM 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
5 File(s) 996,613,896 bytes
Click to expand...
Click to collapse
no your doing fine.. just unlock the bootloader

clsA said:
no your doing fine.. just unlock the bootloader
Click to expand...
Click to collapse
I'm not sure I am doing this right. I am getting what appears to be a syntax error.
C:\fastboot>fastboot devices
HT34XXXXXXXX fastboot
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.023s]
finished. total time: 0.023s
This is the command I sued from the original YouTube video on locking it for stock ROM. It shows it as having already been locked now.
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.002s]
finished. total time: 0.002s
Stupid me, sorry. I had Cyanogenmod do it for me last time. I am on HTCDev getting my unlock token now.

TexMachina said:
I'm not sure I am doing this right. I am getting what appears to be a syntax error.
C:\fastboot>fastboot devices
HT34XXXXXXXX fastboot
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.023s]
finished. total time: 0.023s
This is the command I sued from the original YouTube video on locking it for stock ROM. It shows it as having already been locked now.
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
no you have to go back to HTCDEV.com and get the unlock token from htc

clsA said:
no you have to go back to HTCDEV.com and get the unlock token from htc
Click to expand...
Click to collapse
Sorry about that. I had the Cyanogenmod install site do it for me last time.
I completed the unlocking but the Android Debug Bridge does not recognize the sideload command. It just spits back the help menu.
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.146s
C:\fastboot>fastboot devices
HT34xxxxxxxx fastboot
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.718s]
finished. total time: 1.833s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\fastboot>adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
Android Debug Bridge version 1.0.29
... <entire help menu>
Perhaps my adb version is not correct. I did find reference to a push command in the help menu.
adb push <local> <remote> - copy file/dir to device
Also, there is that fastboot command I attempted to use before I unlocked the bootloader.
Also also, thanks for all the help.
edit: I didn't reboot into recovery. I did now but it is asking for a password

TexMachina said:
Sorry about that. I had the Cyanogenmod install site do it for me last time.
I completed the unlocking but the Android Debug Bridge does not recognize the sideload command. It just spits back the help menu.
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.146s
C:\fastboot>fastboot devices
HT34xxxxxxxx fastboot
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.718s]
finished. total time: 1.833s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\fastboot>adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
Android Debug Bridge version 1.0.29
... <entire help menu>
Perhaps my adb version is not correct. I did find reference to a push command in the help menu.
adb push <local> <remote> - copy file/dir to device
Also, there is that fastboot command I attempted to use before I unlocked the bootloader.
Also also, thanks for all the help.
edit: I didn't reboot into recovery. I did now but it is asking for a password
Click to expand...
Click to collapse
theirs no password on TWRP
To sideload
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
theirs no password on TWRP
To sideload
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
I appreciate all the help and I don't want to appear difficult but when I run the adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip with the rom in the same folder adb simply refuses to recognize the sideload command. It spits back the help menu and I can't find sideload in said menu.
edit: I am using adb push to place the rom on the phones /sdcard directory and I am gong to use TWRP to install while in recovery mode. The copy is taking a while so if this is going to brick my phone let me know.
edit 2: now I don;t think I want to do this. The online resource don't mention anything specifically about installing a ROM using this method.
edit 3: I tried using the HTC One Toolkit which comes with adb 1.0.31. It gave me the following error
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT34xxxxxxxx recovery
adb sideload "File Path..."
* cannot read 'sideload' *
adb sideload "C:\fastboot\Guru_Reset_M7_5.12.502.2_clsA.zip"
error: closed
I am going to the gym to clear my head. Thanks again for all the help so far.

TexMachina said:
I appreciate all the help and I don't want to appear difficult but when I run the adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip with the rom in the same folder adb simply refuses to recognize the sideload command. It spits back the help menu and I can't find sideload in said menu.
edit: I am using adb push to place the rom on the phones /sdcard directory and I am gong to use TWRP to install while in recovery mode. The copy is taking a while so if this is going to brick my phone let me know.
edit 2: now I don;t think I want to do this. The online resource don't mention anything specifically about installing a ROM using this method.
Click to expand...
Click to collapse
your doing fine ..what was the error and why is sideload not in your version of TWRP ?
Is this the same resource that suggested flashing a TWRP recovery file with fastboot ? ... trust me you in good hands now ..just push the rom and flash it
during install choose no to install stock recovery and yes to Root the phone.
unless of coarse you want a stock unrooted phone

clsA said:
your doing fine ..what was the error and why is sideload not in your version of TWRP ?
Is this the same resource that suggested flashing a TWRP recovery file with fastboot ? ... trust me you in good hands now ..just push the rom and flash it
during install choose no to install stock recovery and yes to Root the phone.
unless of coarse you want a stock unrooted phone
Click to expand...
Click to collapse
I didn't realize the thread went to page 2. I thought you just dropped off the tread.
Sideload is in TWRP but it does ask for a password. I loaded TWRP 2.6.3.0 and it doesn't ask for a password.
I am pushing the Guru_Reset_M7_5.12.502.2_clsA.zip to /sdcard again. I will try the install once it is there.

TexMachina said:
I didn't realize the thread went to page 2. I thought you just dropped off the tread.
Sideload is in TWRP but it does ask for a password. I loaded TWRP 2.6.3.0 and it doesn't ask for a password.
I am pushing the Guru_Reset_M7_5.12.502.2_clsA.zip to /sdcard again. I will try the install once it is there.
Click to expand...
Click to collapse
I can't tell you if TWRP 2.6.3.0 will work with the Guru Reset ..it's very old and untested
if you saw a password in TWRP 2.6.3.3 you just swipe to make it go away

clsA said:
I can't tell you if TWRP 2.6.3.0 will work with the Guru Reset ..it's very old and untested
if you saw a password in TWRP 2.6.3.3 you just swipe to make it go away
Click to expand...
Click to collapse
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.

TexMachina said:
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
Click to expand...
Click to collapse
Yeah have a great night.
When you get back >>
Is you phone sdcard full ?
have you done factory reset and or format data partition in TWRP?
If it's too full to push / sideload a rom.
TWRP does have a file manager feature you may need to free up space using it. adb 1.0.31 is the version i use all the time... never an issue.
you would get mounting errors if the partitions were formatted or erased...it's ok the new rom recreates them

TexMachina said:
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
Click to expand...
Click to collapse
Point D here: http://forum.xda-developers.com/showpost.php?p=53270352&postcount=21

clsA said:
Yeah have a great night.
When you get back >>
Is you phone sdcard full ?
have you done factory reset and or format data partition in TWRP?
If it's too full to push / sideload a rom.
TWRP does have a file manager feature you may need to free up space using it. adb 1.0.31 is the version i use all the time... never an issue.
you would get mounting errors if the partitions were formatted or erased...it's ok the new rom recreates them
Click to expand...
Click to collapse
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.

TexMachina said:
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
Click to expand...
Click to collapse
Great !! Thank you !

TexMachina said:
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
Click to expand...
Click to collapse
clsA said:
Great !! Thank you !
Click to expand...
Click to collapse
a few months late to the party but how did you clear the partitions because I'm getting
E: Unable to mount '/cashe'
edit: Finished the adb push but HTC One still goes into Cyanogenmod......hopefully i can just leave this alone for a while cause atleast it turns on now

xaviergreaux said:
a few months late to the party but how did you clear the partitions because I'm getting
E: Unable to mount '/cashe'
edit: Finished the adb push but HTC One still goes into Cyanogenmod......hopefully i can just leave this alone for a while cause atleast it turns on now
Click to expand...
Click to collapse
after pushing a file you still have to install it
adb sideload copy's the file and installs it. Push does not

Stuck at Silver logo screen

Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!

klaymeb said:
Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!
Click to expand...
Click to collapse
seems your using a custom firmware, try this one >> https://www.androidfilehost.com/?fid=95916177934533542
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot

So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....

klaymeb said:
So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....
Click to expand...
Click to collapse
This is my fastboot getvar all
(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.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

klaymeb said:
This is my fastboot getvar all
(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.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
!!!!read all steps first!!!!
1. unlock your bootloader
2. flash custom recovery TWRP 2.8.5.0 ("fastboot flash recovery twrp.img" then "fastboot erase cache" finally "fastboot reboot-bootloader")
3. download this rom https://basketbuild.com/dl/devs?dl=Artur0588/M7_7.19.401.2.zip and put it on the fastboot/adb folder
4. extract firmware.zip (thread #2) and copy boot.img in the fastboot folder
5. extract from the firmware.zip (that you've downloaded in thread #2) recovery.img and paste in the fastboot/adb folder
6. "adb devices" to verify that your device is connected, then "adb push rom.zip /sdcard/" it will take about 5 min.
7. now "fastboot flash boot boot.img" then "fastboot reboot-bootloader"
8. enter to recovery mode and make full wipe (data/dalvick/chache)
9. choose install >> select rom.zip and swipe.
10. when installation finish up flash the stock recovery "fastboot flash recovery recovery.img" , "fastboot erase cache" , "fastboot oem lock" and "fastboot erase cache"

Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.

klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Write the unlock command that you are using here, and the error message too.

klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Are you using the correct drivers for Windows 8.1?
In your device manager is your phone detected?
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
Also, use USB 2.0 rather than 3.0

VoynichJimmy said:
Write the unlock command that you are using here, and the error message too.
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error

klaymeb said:
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error
Click to expand...
Click to collapse
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there? Does the command fastboot devices show your serial no?

stovie_steve said:
Are you using the correct drivers for Windows 8.1?
Driver Version: 2.0.7.27
In your device manager is your phone detected?
Yes.
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
FA426W904521 fastboot
Also, use USB 2.0 rather than 3.0
Click to expand...
Click to collapse
Ok Thanks, I thought that might be the case with it.

stovie_steve said:
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there?
Does the command fastboot devices show your serial no?
Click to expand...
Click to collapse
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code

stovie_steve said:
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code
Click to expand...
Click to collapse
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.

klaymeb said:
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.
Click to expand...
Click to collapse
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC

stovie_steve said:
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC
Click to expand...
Click to collapse
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?

klaymeb said:
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?
Click to expand...
Click to collapse
What is the folder directory where you have your adb and fastboot files?

stovie_steve said:
What is the folder directory where you have your adb and fastboot files?
Click to expand...
Click to collapse
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s

klaymeb said:
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s
Click to expand...
Click to collapse
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s

klaymeb said:
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s
Click to expand...
Click to collapse
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.

Seanie280672 said:
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.
Click to expand...
Click to collapse
So this is what I did, And I still end up back at the bootloader.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Device was already locked!
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.032s]
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1264453 KB)...
OKAY [ 41.892s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 122.212s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Database Develop

welcome