Database Develop

[SOLVED]Unable to unlock my bootloader

Here's my problem.
I've originally S-OFF my phone, Super CID afterwards. A week ago i sent my phone to warranty so made the humongous mistake to S-ON it.
Of course S-OFF didn't work again on 1.44 so i flashed some Asian RUU, S-OFF didn't work either(still 1.44 bootloader).
This is the time when i started considering unlocking my bootloader. Big surprise, the procedure completes successfully, i select yes, the phone reboots but the bootloader stays locked.
I applied the Dev Edition RUU, HBOOT 1.55 same problem.
Any solutions?
The solution is to restore your original CID

Wait, which ruu you've flashed?
However, it's stange, which cid do you have now?

I started with 1.29.401.11 then RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed and the latest was RUU_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.
I am currently super CID

Try this command:
Code:
fastboot getvar all
, remove the imei and the serial number of your phone and post here the log

version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.22.1540.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 3792mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-fe1214a4f2
hbootpreupdate: 11
gencheckpt: 0

So, you're s-on with super cid...
If you try to reflash the first ruu you said, you can flash it or you've an error?

Yes,
I get an error.
What i can't understand is why i can't unlock it.

andrdnl said:
Yes,
I get an error.
What i can't understand is why i can't unlock it.
Click to expand...
Click to collapse
Are you using an old token? I recommend getting a new token from HTCdev, and try again to unlock.
But you still have a problem of being S-On and SuperCID, you will not be able to change that even if you unlock bootloader again. revone will only work with hboot 1.44.

I did get a new token about 7 times. It's not the problem i think.
I am convinced i can't get S-OFF for the moment but at least i wish i could unlock the bootloader.

andrdnl said:
I did get a new token about 7 times. It's not the problem i think.
I am convinced i can't get S-OFF for the moment but at least i wish i could unlock the bootloader.
Click to expand...
Click to collapse
Could be because of SuperCID. I know that the unlock token is tied to your CID as well as other things, but thought if you got a new one it could work.
And with 1.54/1.55 there is no way to get s-off at the moment, unless you can find someone with a Java Card.

This is the only logical explanation that i can found.

andrdnl said:
This is the only logical explanation that i can found.
Click to expand...
Click to collapse
how did you solve this?

slimldj said:
how did you solve this?
Click to expand...
Click to collapse
+1

slimldj said:
how did you solve this?
Click to expand...
Click to collapse
stoned99 said:
+1
Click to expand...
Click to collapse
Go S-OFF and change the cid, with your original CID...

Guich said:
Go S-OFF and change the cid, with your original CID...
Click to expand...
Click to collapse
bootloader is locked.. how can i then get S-OFF?
my issue is to unlock bootloader again. btw. i have my original CID

slimldj said:
bootloader is locked.. how can i then get S-OFF?
my issue is to unlock bootloader again. btw. i have my original CID
Click to expand...
Click to collapse
He solved restoring his stock CID.
Which hboot do you have?
And you had S-OFF in past?

Guich said:
He solved restoring his stock CID.
Which hboot do you have?
And you had S-OFF in past?
Click to expand...
Click to collapse
Yes i was unlocked and had s-off in the past
I had to return it to stock for warranty to change the camera and it came back.
I want to unlock back now and cant.
Hboot is 1.54

slimldj said:
Yes i was unlocked and had s-off in the past
I had to return it to stock for warranty to change the camera and it came back.
I want to unlock back now and cant.
Hboot is 1.54
Click to expand...
Click to collapse
You've the same error of the guy?
So, after the flash of the unlock_code your bootloader won't be unlocked?

Guich said:
You've the same error of the guy?
So, after the flash of the unlock_code your bootloader won't be unlocked?
Click to expand...
Click to collapse
After i flash the Unlock_code.bin i get this result:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.150s
Next step is for disclaimer to pop up on phone screen but it doesnt.. it just remains on the hboot screen.

slimldj said:
After i flash the Unlock_code.bin i get this result:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.150s
Next step is for disclaimer to pop up on phone screen but it doesnt.. it just remains on the hboot screen.
Click to expand...
Click to collapse
Strange...
Have you tried to request another unlock code?

Unable to unlock relocked hboot

I re-locked my phone with a custom recovery and attempted to unlock again and goes through successful though the unlock screen does not show up.(Probably because I have no OS installed?)
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check [COLOR="DeepSkyBlue"]successfully[/COLOR]
OKAY [ 0.003s]
finished. total time: 0.144s
My current information is:
*** Tampered ***
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Code:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXX
imei: XXXXXXXXXXXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum:[COLOR="DeepSkyBlue"]GOOGL001[/COLOR]
battery-status: good
battery-voltage: 4288mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
Ive tried the method below with a few RUU's though I keep getting the error "FAILED (remote: 12 signature verify fail)" Their must some RUU that I can flash that correlates to my above information?
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <path to zip>
Code:
C:\Users\chanik\Desktop\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fa
stboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (388870 KB)...
OKAY [ 15.220s]
writing 'zip'...
(bootloader) signature checking...
[COLOR="Red"]FAILED (remote: 12 signature verify fail)[/COLOR]
finished. total time: 53.263s
If someone could confirm I have fully bricked my device that be great so i can move on with my life

I foundout that i dont have a mainvar... is tjis bad?

ronniereiff said:
I foundout that i dont have a mainvar... is tjis bad?
Click to expand...
Click to collapse
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk

nkk71 said:
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Twrp, though i am unable to use it due to being relocked..

ronniereiff said:
Twrp, though i am unable to use it due to being relocked..
Click to expand...
Click to collapse
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please

nkk71 said:
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please
Click to expand...
Click to collapse
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread

ronniereiff said:
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread
Click to expand...
Click to collapse
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).

nkk71 said:
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).
Click to expand...
Click to collapse
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.

ronniereiff said:
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.
Click to expand...
Click to collapse
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.

nkk71 said:
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.
Click to expand...
Click to collapse
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.

ronniereiff said:
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.
Click to expand...
Click to collapse
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)

nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
I have successfully unlocked after flashing the 3.58.1700.5 kitkat firmware Just need to see how to get kitkat now

nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.

ronniereiff said:
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.
Click to expand...
Click to collapse
Cache unable to mount is ok, it's because it's wiped, so don't worry about that.
To be able to flash a 4.4 ROM, you need TWRP 2.6.3.3 or above, but since you're S-On you cannot flash a GPE 4.4 ROM as they require S-Off.
Use adb sideload, adb push, or OTG cable to get a ROM to TWRP.
Hit the thanks button if i've helped

nkk71 said:
Hit the thanks button if i've helped
Click to expand...
Click to collapse
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff

ronniereiff said:
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff
Click to expand...
Click to collapse
Can you post where did you get the rom you flashed?

[Q] active cmdline overflow problem and no comment working...PLEASE HELP

hello all,
my friend wanted me a favour for making his ONE working but i couldn't do it so any advice will be appreciated...here is the situation...
while he's charging, phone suddenly stopped and now it is not working...i open command line, but couldn't find the device anymore. he said he's sure that he checked "usb debugging" and "unknown sources". also it's not charging anymore.
i tried downgrade hboot then flash RUU.exe but no comment was working...
what should i do? PLEASE HELP ME

ayk33 said:
hello all,
my friend wanted me a favour for making his ONE working but i couldn't do it so any advice will be appreciated...here is the situation...
while he's charging, phone suddenly stopped and now it is not working...i open command line, but couldn't find the device anymore. he said he's sure that he checked "usb debugging" and "unknown sources". also it's not charging anymore.
i tried downgrade hboot then flash RUU.exe but no comment was working...
what should i do? PLEASE HELP ME
Click to expand...
Click to collapse
let me get this right. the phone does NOT power on and does not charge ?

baadnewz said:
let me get this right. the phone does NOT power on and does not charge ?
Click to expand...
Click to collapse
it does stuck on bootloader only and does not charge...whatever i do, it turns again to bootloader. I tried many things but since device could not be found, the commands aren't accepted. all i can do is RUU.exe but it gives me error 155 (which means the RUU is not the right RUU) and i couldn't find the right RUU.exe...
This is my friend's ONE and as he said, he last flashed your rom;
on bootloader screen, it says;
*** TAMPERED ***
*** RELOCKED ***
M7_U UNKNOWN SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
etc
etc

ayk33 said:
it does stuck on bootloader only and does not charge...whatever i do, it turns again to bootloader. I tried many things but since device could not be found, the commands aren't accepted. all i can do is RUU.exe but it gives me error 155 (which means the RUU is not the right RUU) and i couldn't find the right RUU.exe...
This is my friend's ONE and as he said, he last flashed your rom;
on bootloader screen, it says;
*** TAMPERED ***
*** RELOCKED ***
M7_U UNKNOWN SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
etc
etc
Click to expand...
Click to collapse
It's giving you error 155 because hboot is 1.56; RUU.EXE downgrade will fail with hboot 1.55+
post a "fastboot getvar all" (except IMEI and s/n)
and WTH is "M7_U UNKNOWN SHIP S-OFF RH", were you messing around with an ENG hboot?

nkk71 said:
It's giving you error 155 because hboot is 1.56; RUU.EXE downgrade will fail with hboot 1.55+
post a "fastboot getvar all" (except IMEI and s/n)
and WTH is "M7_U UNKNOWN SHIP S-OFF RH", were you messing around with an ENG hboot?
Click to expand...
Click to collapse
all getvar is this;
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.2
version-misc: UNKNOWN SHIP S-OFF
serialno: ü;üåÏ*úëR_Ó´%Zè
imei: xxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: 0←♦ê►ê4ç8çõ*☼♀‼áDç
cidnum: 11111111
battery-status: good
battery-voltage: 4279mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
beside these, believe me i have no idea what he has flashed so far but i've always told him to use IC roms, probably he did what was written there
and since i can't enter any command, i cannot change hboot to 1.44 because of unknown device problem

ayk33 said:
all getvar is this;
imei: XXX
Click to expand...
Click to collapse
Hide this

ayk33 said:
all getvar is this;
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.2
version-misc: UNKNOWN SHIP S-OFF
serialno: ü;üåÏ*úëR_Ó´%Zè
imei: 35xxxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: 0←♦ê►ê4ç8çõ*☼♀‼áDç
cidnum: 11111111
battery-status: good
battery-voltage: 4279mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
beside these, believe me i have no idea what he has flashed so far but i've always told him to use IC roms, probably he did what was written there
and since i can't enter any command, i cannot change hboot to 1.44 because of unknown device problem
Click to expand...
Click to collapse
^^^^ WOW, never seen a system that messed up before!!
can you post a screenshot of bootloader,
but you definitely have one or more low-level partitions really messed up, I don't know if this is fixable.

I've already told my friend to say goodbye but i wanna surprise him i will post screenshot as soon as i can...
Thanks one more time
Sent from my HTC One using xda app-developers app

This is the photo of the trouble
Sent from my HTC One using xda app-developers app

ayk33 said:
This is the photo of the trouble
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
well i'm off for tonight, but i do have to say WOW.... sorry if that comes across in a bad way, not trying to be an ass or anything.
I'll give it some thought, but so far, looks like some really low level partitions are f**ed, including:
mmcblk0p3, mmcblk0p6, maybe mmcblk0p7, and mmcblk0p19
(not to mention hboot)
eventually, you're going to have to end up using an ruu.zip in "fastboot oem rebootRUU" mode, but not sure how much this is going to fix your low-level partitions..... it's amazing you still have an IMEI.

nkk71 said:
well i'm off for tonight, but i do have to say WOW.... sorry if that comes across in a bad way, not trying to be an ass or anything.
I'll give it some thought, but so far, looks like some really low level partitions are f**ed, including:
mmcblk0p3, mmcblk0p6, maybe mmcblk0p7, and mmcblk0p19
(not to mention hboot)
eventually, you're going to have to end up using an ruu.zip in "fastboot oem rebootRUU" mode, but not sure how much this is going to fix your low-level partitions..... it's amazing you still have an IMEI.
Click to expand...
Click to collapse
Thanks anyway...waiting for an answer
Sent from my HTC One using xda app-developers app

cmdline overflow usually happens when your kernel cmdline is longer that it must be. can you try to flash another boot.img. preferably a stock one. or downgrade hboot to 1.44

baadnewz said:
cmdline overflow usually happens when your kernel cmdline is longer that it must be. can you try to flash another boot.img. preferably a stock one. or downgrade hboot to 1.44
Click to expand...
Click to collapse
Since i have "unknown device" issue, i can't flash anything i guess he has dead ONE
Sent from my HTC One using xda app-developers app

ayk33 said:
Since i have "unknown device" issue, i can't flash anything i guess he has dead ONE
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well it's probably going to be a futile exercise, but WTH, download this:
http://www.htc1guru.com/dld/ruu-zip...0-01_release_311663_signed_2_4_decrypted-zip/
rename it to ruu.zip and put it in your adb/fastboot folder, go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
again
fastboot flash zip ruu.zip
fastboot reboot-bootloader
copy/paste output here.

nkk71 said:
Well it's probably going to be a futile exercise, but WTH, download this:
http://www.htc1guru.com/dld/ruu-zip...0-01_release_311663_signed_2_4_decrypted-zip/
rename it to ruu.zip and put it in your adb/fastboot folder, go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
again
fastboot flash zip ruu.zip
fastboot reboot-bootloader
copy/paste output here.
Click to expand...
Click to collapse
aaaaand what i got is here;
C:\Users\Aykal\Desktop\fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1009472 KB)...
OKAY [ 42.950s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 43.375s
can it be sth related with cid? should i change it since model id fail

ayk33 said:
aaaaand what i got is here;
C:\Users\Aykal\Desktop\fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1009472 KB)...
OKAY [ 42.950s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 43.375s
can it be sth related with cid? should i change it since model id fail
Click to expand...
Click to collapse
It is not related to CID because your CID is 1111111 (SuperCID)
So you have to add your MID to the android-info.txt file...
And since your MID is:
Code:
0←♦ê►ê4ç8çõ*☼♀‼áDç
Just add exactly that to your android-info.txt and if you now have something new on your getvar all output.. just add the result you get related to "modeliid"
P.S.
android-info.txt is inside the RUU.zip file.... just extract it... add your MID with the same syntaxis like the other MIDs and repack everything..

LibertyMarine said:
It is not related to CID because your CID is 1111111 (SuperCID)
So you have to add your MID to the android-info.txt file...
And since your MID is:
Code:
0←♦ê►ê4ç8çõ*☼♀‼áDç
Just add exactly that to your android-info.txt and if you now have something new on your getvar all output.. just add the result you get related to "modeliid"
P.S.
android-info.txt is inside the RUU.zip file.... just extract it... add your MID with the same syntaxis like the other MIDs and repack everything..
Click to expand...
Click to collapse
BIG BIG THANK YOU well we eliminate step one, let's do the rest :fingers-crossed: new output;
C:\Users\Aykal\Desktop\fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1006864 KB)...
OKAY [ 43.471s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 43.752s

ayk33 said:
BIG BIG THANK YOU well we eliminate step one, let's do the rest :fingers-crossed: new output;
C:\Users\Aykal\Desktop\fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1006864 KB)...
OKAY [ 43.471s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 43.752s
Click to expand...
Click to collapse
Not really the way I would have done it, but can you check your inbox please.

nkk71 said:
Not really the way I would have done it, but can you check your inbox please.
Click to expand...
Click to collapse
I'm interested, how would you do it?

LibertyMarine said:
I'm interested, how would you do it?
Click to expand...
Click to collapse
Hi LibertyMarine
actually my bad,
* he has a locked bootloader
* and no custom recovery
we tried a bit earlier, but didnt get very far, maybe he'll come back later and we'll give it another shot.
I need a custom recovery on it, to be able to see a few things :cyclops::cyclops:

Help getting back to stock!

Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
ERROR [140]: BOOTLOADER VERSION ERROR

Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
Click to expand...
Click to collapse
Post getvar all.
Post screen shot of bootloader.
Are you unlocked/relocked/locked.
Are you S-On/S-Off.
Have you changed Cidnum or modelid.
What rom are you currently using, is it original stock/custom.
Tell the buyer that you have a custom rom installed and would he/she like you to return it to stock.
He/she might want to root it the moment they buy it.
Sent from my Nexus 7 using XDA Premium HD app

bored_stupid said:
Post getvar all.
Post screen shot of bootloader.
Are you unlocked/relocked/locked.
Are you S-On/S-Off.
Have you changed Cidnum or modelid.
What rom are you currently using, is it original stock/custom.
Tell the buyer that you have a custom rom installed and would he/she like you to return it to stock.
He/she might want to root it the moment they buy it.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Relocked
hboot 1.44
S-On
Didn't change cid or modelid
Latest Venom Rom was on it..

This is what I get trying installing RUU I downloaded:
ERROR [140]: BOOTLOADER VERSION ERROR

Rolando88 said:
Guyes i need to sell my phone so I can buy M8
I someone who want it but I cant get back to stock!
I relocked..
but i'm getting error message trying to install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Im from the Netherlands and this is te error message I get:
ERROR [140]: BOOTLOADER VERSION ERROR
Click to expand...
Click to collapse
that RUU is no good in any case, you need to use the 1.28.401.7 version (provided you meet the requirements, which can only be checked using the output of "fastboot getvar all")
and with S-On, your phone will only show RELOCKED not LOCKED, so the buyer will know that you had it unlocked at one point.

Post a fastboot getvar all please
Sent from my Nexus 7 using XDA Premium HD app

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW909481
(bootloader) imei: *************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3879mV
(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.042s

Try this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
And this guide to flash the RUU
http://www.htc1guru.com/downloads/ruu-zip-downloads/
Sent from my Nexus 7 using XDA Premium HD app

bored_stupid said:
Try this
http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
And this guide to flash the RUU
http://www.htc1guru.com/downloads/ruu-zip-downloads/
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s

Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
Of course it fails. You are trying to downgrade your phone while you are S-ON.
You are trying to flash:
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4
but you version is 1.29.xxxxx.
1.20 is less than 1.29. You could only do that if you were S-OFF. So you need to download the same version or higher than yours...so 1.29.401.12 or higher.

Deleted

Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
You need to unlock your bootloader again. Flash recovery and then s-off follow this guide
http://www.htc1guru.com/guides/get-s-off/
Then follow the guides to return to stock.
Sent from my HTC One using XDA Premium HD app

gartner83 said:
Of course it fails. You are trying to downgrade your phone while you are S-ON.
You are trying to flash:
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4
but you version is 1.29.xxxxx.
1.20 is less than 1.29. You could only do that if you were S-OFF. So you need to download the same version or higher than yours...so 1.29.401.12 or higher.
Click to expand...
Click to collapse
I got this error message when I tried to flash
RUU Zip M7 UL JB 50 HTC Europe 1.29.401.16 R Radio 4A.14.3250.13 10.33.1150.01 Release 318486 Signed 2 4 Decrypted

Rolando88 said:
C:\Users\rolandob\Desktop\htc>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 46.379s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 152.193s
Click to expand...
Click to collapse
Easiest thing to do is S-OFF the phone, then you can flash any ruu you want without an issue.
Then once you've flashed it, you can put s-on back on if you want.
That's what I did when sent my phone back to HTC for warranty.

danlat1415 said:
Easiest thing to do is S-OFF the phone, then you can flash any ruu you want without an issue.
Then once you've flashed it, you can put s-on back on if you want.
That's what I did when sent my phone back to HTC for warranty.
Click to expand...
Click to collapse
I agree, this I think also, is the best solution. After that, you can also set your booloader status to "LOCKED", as if it was never touched.

gartner83 said:
I agree, this I think also, is the best solution. After that, you can also set your booloader status to "LOCKED", as if it was never touched.
Click to expand...
Click to collapse
You can even leave leave the phone as s-off.
Won't be an issue, still covered by HTC warranty. They only care about boot loader status.

I tried with the all in one tool pffff
\adb push revone /data/local/tmp/
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
adb reboot
adb shell /data/local/tmp/./revone -s 0 -u
still S-On this should work for hboot 1.44

Rolando88 said:
I tried with the all in one tool pffff
\adb push revone /data/local/tmp/
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
adb reboot
adb shell /data/local/tmp/./revone -s 0 -u
still S-On this should work for hboot 1.44
Click to expand...
Click to collapse
what ROM are you on?
Recommend this one for revone: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=250
otherwise try http://firewater-soff.com/

ok it finally worked!! got S-Off with rumrunner!
Now i Installed RUU but when i started Phone and walked through the wizard i got on a page with:
Tell HTC:
This is a test device: Tell HTC is automatically enabled so that HTC can collect critical information aboout the device during testing. It is not possible to turn this ffeature on on this Phone...
I guess I still don't have a stock rom on it now!!!? Anyone knows what i have to do?!

Rolando88 said:
ok it finally worked!! got S-Off with rumrunner!
Now i Installed RUU but when i started Phone and walked through the wizard i got on a page with:
Tell HTC:
This is a test device: Tell HTC is automatically enabled so that HTC can collect critical information aboout the device during testing. It is not possible to turn this ffeature on on this Phone...
I guess I still don't have a stock rom on it now!!!? Anyone knows what i have to do?!
Click to expand...
Click to collapse
This is normal, it's due to s-off.
Sent from my HTC One using Tapatalk

[Q] Can't S-ON?

After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!

Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082

nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.

Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.

nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.

Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)

nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?

Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.

nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.

Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware

nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.

Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe

nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.

Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.

nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-