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.. -_-
Related
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:
I'm having a problem flashing the latest firmware - 4.19.401.11 (currently on 4.19.401.8).
I get:
Code:
sending 'zip' (71868 KB)...
OKAY [ 4.936s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.410s
I then try to write again immediately and it just hangs on
Code:
sending 'zip' (71868 KB)...
(the file size is obviously different I just copied the code from Vomer's thread).
Eventually I have to just reset my phone. Any ideas?
I've never had any problems flashing firmware in the past.
I have checked the MD5 (it matches), i've tried downloading it again and tried on different PCS (both running Windows 7) with different USB cables.
Currently running Viperone 5.8.0
Thanks in advance.
Any ideas?
How are you trying to flash the firmware?
Post link to firmware please.
Post a fastboot getvar all
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hi there,
I'm using the guide that Vomer has posted and the latest firmware on the following page (I have followed this process many times):
http://forum.xda-developers.com/showthread.php?t=2365506
My getvar:
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.23.3263.28
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.19.401.8
INFOversion-misc: PVT SHIP S-OFF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4228mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.074s
Thanks!
Ardmanz said:
Hi there,
I'm using the guide that Vomer has posted and the latest firmware on the following page (I have followed this process many times):
http://forum.xda-developers.com/showthread.php?t=2365506
My getvar:
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.23.3263.28
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.19.401.8
INFOversion-misc: PVT SHIP S-OFF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
[COLOR="Red"]INFOproduct: m7_ul[/COLOR]
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4228mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.074s
Thanks!
Click to expand...
Click to collapse
You do realise that is for HTC HTC One Dual Sim(M7C_DUG) You have a m7ul single sim.
Get the firmware from here and follow the guide
No need to lock your bootloader,{ your S-Off }
http://forum.xda-developers.com/showthread.php?t=2182823
The version is exactly the same as the one you have linked me to?
Vomer has never posted up dualsim firmwares before?
Here is the link to the specific firmware I am trying to use:
http://www.androidfilehost.com/?fid=23329332407579996
Ardmanz said:
The version is exactly the same as the one you have linked me to?
Vomer has never posted up dualsim firmwares before?
Here is the link to the specific firmware I am trying to use:
http://www.androidfilehost.com/?fid=23329332407579996
Click to expand...
Click to collapse
Read underneath fw_4.19.401.11_custom.zip
for the HTC HTC One Dual Sim(M7C_DUG), by vomer
DUEL SIM
You need this one
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
bored_stupid said:
Read underneath fw_4.19.401.11_custom.zip
for the HTC HTC One Dual Sim(M7C_DUG), by vomer
DUEL SIM
You need this one
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Click to expand...
Click to collapse
Wow, I missed that. I feel like an idiot! Haha.
I'll try the one you posted. Thank you very much!
Let me know how you get on
Dont feel to bad, I almost download that at one time too
bored_stupid said:
Let me know how you get on
Dont feel to bad, I almost download that at one time too
Click to expand...
Click to collapse
Hmm, same thing again.
I've noticed something weird in my HBOOT though..
It's in red text:
OS-4.19.401.8 (4.19.401.11)
Does this have anything to do with it?
Edit - I've also tried the .9 firmware and it's giving me the same problem however, the red message above now has the .9 firmware in brackets???
Edit - Also, my phone works fine, I just can't flash any firmwares.
Ardmanz said:
Hmm, same thing again.
I've noticed something weird in my HBOOT though..
It's in red text:
OS-4.19.401.8 (4.19.401.11)
Does this have anything to do with it?
Click to expand...
Click to collapse
Because you only ran the "fastboot flash zip <name of firmware>.zip" once, your firmware is in a state of limbo.
Flash the firmware again
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your firmware.zip file is in your adb/fastboot folder
fastboot flash zip firmware.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
fastboot flash zip firmware.zip
Let it run and it should finish this time
fastboot reboot
bored_stupid said:
Because you only ran the "fastboot flash zip <name of firmware>.zip" once, your firmware is in a state of limbo.
Flash the firmware again
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your firmware.zip file is in your adb/fastboot folder
fastboot flash zip firmware.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
fastboot flash zip firmware.zip
Let it run and it should finish this time
fastboot reboot
Click to expand...
Click to collapse
The above is exactly what I'm doing. I flash the second time but it does nothing. Maybe I'll leave it longer but it's never taken more than about 30 seconds to send it to my phone previously. I'll leave it for a good 5 mins and see how I go.
Ardmanz said:
The above is exactly what I'm doing. I flash the second time but it does nothing. Maybe I'll leave it longer but it's never taken more than about 30 seconds to send it to my phone previously. I'll leave it for a good 5 mins and see how I go.
Click to expand...
Click to collapse
Flash 1.44 hboot firmware
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
See if that works
if it does then you can reflash the latest firmware
bored_stupid said:
Flash 1.44 hboot firmware
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
See if that works
if it does then you can reflash the latest firmware
Click to expand...
Click to collapse
Flash that as I would the normal firmware then try flashing the newest firmware?
Ardmanz said:
Flash that as I would the normal firmware then try flashing the newest firmware?
Click to expand...
Click to collapse
Yes flash as normal firmware
You might be interested in this though
I have Hboot 1.44 and latest radio firmware
The radio is flashed in recovery
http://d-h.st/7ci
bored_stupid said:
Yes flash as normal firmware
You might be interested in this though
I have Hboot 1.44 and latest radio firmware
The radio is flashed in recovery
http://d-h.st/7ci
Click to expand...
Click to collapse
Would I be safer using an RUU then flashing the latest firmware?
Ardmanz said:
Would I be safer using an RUU then flashing the latest firmware?
Click to expand...
Click to collapse
Any flashing to a phone involves risks
This is the main thread to the flashable radios i refereed too
http://forum.xda-developers.com/showthread.php?t=2419699
bored_stupid said:
Any flashing to a phone involves risks
This is the main thread to the flashable radios i refereed too
http://forum.xda-developers.com/showthread.php?t=2419699
Click to expand...
Click to collapse
I realise the risk but RUU is like starting from fresh. May give it a go, it's a pain though!
Ardmanz said:
I realise the risk but RUU is like starting from fresh. May give it a go, it's a pain though!
Click to expand...
Click to collapse
I think it maybe your only hope if the hboots wont take.
Its just that some users have had some luck by flashing 1.44 hboot
I just hope that trying to flash the wrong firmware hasn't corrupted the hboot.
Backup your user apps with TB
Also if your using 4.4.2 RUU then dont sign into google when setting up the phone.
Once setup has finished then sign into Google.
Your notifications will work then.
bored_stupid said:
I think it maybe your only hope if the hboots wont take.
Its just that some users have had some luck by flashing 1.44 hboot
I just hope that trying to flash the wrong firmware hasn't corrupted the hboot.
Backup your user apps with TB
Also if your using 4.4.2 RUU then dont sign into google when setting up the phone.
Once setup has finished then sign into Google.
Your notifications will work then.
Click to expand...
Click to collapse
I was planning on using this one:
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Hi,
I`ve had my fun tuning my htc one, but i`ve no clue how to get it to normal m7 phone with sense 6 lol.
I`ve got TWRP and running the OTA rom does not do anything. Am I trying with the incorrect rom or what?
Thanks for any feedback!
sycorax1337 said:
Hi,
I`ve had my fun tuning my htc one, but i`ve no clue how to get it to normal m7 phone with sense 6 lol.
I`ve got TWRP and running the OTA rom does not do anything. Am I trying with the incorrect rom or what?
Thanks for any feedback!
Click to expand...
Click to collapse
First, we will need to see a fastboot getvar all with the imei and serialno removed. This is needed to know which variant/version of the HTC One M7 you have, so we can point you in the right direction.
Second, OTA's are update files for stock roms with stock recovery for specific versions. If you don't have the correct combination then it will not run properly.
Third, here is a guide for going back to stock. You probably don't want to go to 100% stock but it shows you the proper steps.
majmoz said:
First, we will need to see a fastboot getvar all with the imei and serialno removed. This is needed to know which variant/version of the HTC One M7 you have, so we can point you in the right direction.
Second, OTA's are update files for stock roms with stock recovery for specific versions. If you don't have the correct combination then it will not run properly.
Third, here is a guide for going back to stock. You probably don't want to go to 100% stock but it shows you the proper steps.
Click to expand...
Click to collapse
Sorry, my bad
Code:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: H3G__001
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
sycorax1337 said:
Sorry, my bad
Code:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: H3G__001
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
I can not find a RUU for your phone but I did find a GURU Stock Reset: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
Guru Reset file are simply Stock ROM’s packaged with the nice graphical interface of the aroma installer. They include the stock radio and stock recovery, so if you are still S-on then this is best way to reset to stock. It can’t change your firmware but it can get the stock ROM installed with the stock recovery so that you can get OTA updates and it should also remove the Tampered text from your bootloader.
Click to expand...
Click to collapse
There is an OTA at this site for your phone.
I would try to get S-OFF before doing the Stock Reset it would give you more flexibility. If firewater doesn't work to get S-OFF then view this post about a service in the UK.
majmoz said:
I can not find a RUU for your phone but I did find a GURU Stock Reset: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
There is an OTA at this site for your phone.
I would try to get S-OFF before doing the Stock Reset it would give you more flexibility. If firewater doesn't work to get S-OFF then view this post about a service in the UK.
Click to expand...
Click to collapse
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?
sycorax1337 said:
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?
Click to expand...
Click to collapse
Try the sideload method. Make sure HTC Drivers are installed and ADB is already working. If not, then check out this FAQ Post.
1. Reboot into TWRP
2. In TWRP, hit ADVANCED and find SIDELOAD
3. Swipe to start the SIDELOAD
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. Type adb devices and it should show your device connected and say SIDELOAD
6. Your ZIP file should already be in your adb folder
7. You are now ready to push the zip.....
8. Type adb sideload nameofzip.zip
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. If adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
sycorax1337 said:
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?
Click to expand...
Click to collapse
You can't use that guru reset file, it's too low for your hboot version, the only way you can use it is to downgrade your hboot and the only way you can do that is to get s-off, the otas are putting you into a bootloop because they are trying to upgrade your hboot and as you already have the latest hboot they can't complete that task.
Your stuck with custom roms unless you can get your phone s-off, or find a nandroid backup of your latest rom.
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
as for your driver problem, see FAQ 2 here by nkk71 http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Mate I have same problem like you. No way to bring a phone to life. I try a custom and lot of ruu, but nothing with some ruu i got error 155, and 130. With CyanogenMod, using sideload i got error on the phone, and nothing instal.
Hire is my getvar all.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.00
INFOversion-baseband: 4T.27.321
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-OF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4331mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e47fb74b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.069s
C:\ADB>
People help us to get alive our phones...
Errornt said:
Mate I have same problem like you. No way to bring a phone to life. I try a custom and lot of ruu, but nothing with some ruu i got error 155, and 130. With CyanogenMod, using sideload i got error on the phone, and nothing instal.
Hire is my getvar all.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.00
INFOversion-baseband: 4T.27.321
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-OF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4331mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e47fb74b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.069s
C:\ADB>
People help us to get alive our phones...
Click to expand...
Click to collapse
First, remove the imei and serialno from your original post!
Second, I have had problems running RUU because the hboot was too high. Since, you are S-OFF you can downgrade your hboot then install the RUU. This post will explain the procedure. When the RUU executes it will change your hboot to that of the RUU.
Ok thx mate, I downgrade my Hboot to 1.44.000. Here is log.
Code:
C:\ADB>fastboot flash zip 1.29.401.12_hboot_1.44.zip
sending 'zip' (501 KB)... OKAY [ 0.261s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,50
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
OKAY [ 2.339s]
finished. total time: 2.602s
C:\ADB>
Then I try flash firmware above in this theard, and got faill in CMD, hire is log.
Code:
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 48.690s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 55.696s
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 48.494s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 55.753s
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 66.921s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 74.199s
Is it possible to my eMMC-boot is death. There is no size text. Look @ picture.
After i flash a new HBOOT text has gone 2048MB
Did you put your phone into ruu mode before trying to flash the firmware ?
Code:
fastboot oem rebootRUU
Seanie280672 said:
Did you put your phone into ruu mode before trying to flash the firmware ?
Code:
fastboot oem rebootRUU
Click to expand...
Click to collapse
Yes mate, the black screen with HTC text.
Can somebody tell me what region is my phone, i buy it from internet and I dont know what RUU to download, to try flash it.
Errornt said:
Yes mate, the black screen with HTC text.
Can somebody tell me what region is my phone, i buy it from internet and I dont know what RUU to download, to try flash it.
Click to expand...
Click to collapse
Well your on 401 which is WWE Europe, same as the hboot you flashed, so you need to flash an ruu or a firmware which is 4.xx.401.xx however I see what your problem is, you have super cid, 401 android-info.txt doesn't have super cid in it, change your cid to HTC__001 then reboot bootloader and try flash the firmware zip again.
Seanie280672 said:
Well your on 401 which is WWE Europe, same as the hboot you flashed, so you need to flash an ruu or a firmware which is 4.xx.401.xx however I see what your problem is, you have super cid, 401 android-info.txt doesn't have super cid in it, change your cid to HTC__001 then reboot bootloader and try flash the firmware zip again.
Click to expand...
Click to collapse
Ok so i need to change my cid to HTC__001 and then flash Some WWE Europe RUU, can you give me a link of some ruu that you thing its good for me. (thx).
Sorry for my bad English.
Edit: I edited my CID to HTC__001 so now I need good RUU to flash it. I woud like to have a orginal rom, but i will be happy if I get my phone on with any custom rom if not with oem.
Errornt said:
Ok so i need to change my cid to HTC__001 and then flash Some WWE Europe RUU, can you give me a link of some ruu that you thing its good for me. (thx).
Sorry for my bad English.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
You may need to find the 4.19.401.9 firmware and flash that first.
I got ERROR 158 IMAGE ERROR, when i try to flash this RUU.
My radio is 4T, and this RUU is 4A is that problem?
Errornt said:
I got ERROR 158 IMAGE ERROR, when i try to flash this RUU.
My radio is 4T, and this RUU is 4A is that problem?
Click to expand...
Click to collapse
Nope, you need to find the corrisponding firmware and flash that first like I said before , you need 4.19.401.9 firmware.zip, flash that first then run the ruu
Seanie280672 said:
Nope, you need to find the corrisponding firmware and flash that first like I said before , you need 4.19.401.9 firmware.zip, flash that first then run the ruu
Click to expand...
Click to collapse
Can you give me more details how to make that to flash 4.19.401.9 firmware.zip, and how to flash it, with cmd? fastboot? Should be unlocked or relocked? when flashing that firmware, and can you help me to find that firmware on the net, because i dont know what i need to search. :angel:
Errornt said:
Can you give me more details how to make that to flash 4.19.401.9 firmware.zip, and how to flash it, with cmd? fastboot? Should be unlocked or relocked? when flashing that firmware, and can you help me to find that firmware on the net, because i dont know what i need to search. :angel:
Click to expand...
Click to collapse
You will have to wait till I get home from work in a few hours for all of that or do a bit of reading and searching
what firmware are you after?
Hi,
I'm trying to return my HTC One m7 to stock.
I followed this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
and didn't realise this wouldn't work for HBOOT 1.57.
Subsequently my bootloader status currently shows as
*** Tampered ***
**** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
Radio-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048mb
Click to expand...
Click to collapse
How can I remove the tampered state and return this to locked? All the guides I've been able to find only show how to do it for HBOOT 1.44 up to 1.55.
Edit: Solved this by following alray's advice to use nkk71's superguide: http://forum.xda-developers.com/showthread.php?t=2541082
WastedJoker said:
Hi,
I'm trying to return my HTC One m7 to stock.
I followed this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
and didn't realise this wouldn't work for HBOOT 1.57.
Subsequently my bootloader status currently shows as
How can I remove the tampered state and return this to locked? All the guides I've been able to find only show how to do it for HBOOT 1.44 up to 1.55.
Click to expand...
Click to collapse
you first need to achieve s-off and then follow nkk71's guide to return stock (link in my signature)
I'm almost there but because I'm on hboot 1.44 and using Win 8.1, I can't move to s-on.
I'll try the final step (fastboot oem writesecureflag 3) from my work pc tomorrow which is on win 7.
WastedJoker said:
I'm almost there but because I'm on hboot 1.44 and using Win 8.1, I can't move to s-on.
I'll try the final step (fastboot oem writesecureflag 3) from my work pc tomorrow which is on win 7.
Click to expand...
Click to collapse
you can use a linux live usb (instructions are in the FAQ section of my guide)
how were you able to do all the other steps with Win8.1??; if you were following my guide the hboot downgrade would only be one of the first steps.
I used your guide to get back to 1.44 then revone to remove tampered and unlocked states. I also used firewater to get s-off for part of the steps.
I didn't realise i could downgrade the hboot so that's basically where i was going wrong.
WastedJoker said:
I used your guide to get back to 1.44 then revone to remove tampered and unlocked states. I also used firewater to get s-off for part of the steps.
I didn't realise i could downgrade the hboot so that's basically where i was going wrong.
Click to expand...
Click to collapse
depending on which method you are using, once hboot is downgraded to 1.44, that would only be the first "fastboot flash zip ruu.zip", the second one also needs to be completed
I'm not sure at what stage and method you are at, but going s-on sounds like a very bad idea at the moment
Currenttly I have ARHD 53 installed.
Bootloader is *** LOCKED *** with hboot 1.44.
My CID is 1111111 and I'll be using an o2 UK RUU.
The linux live cd method is handy but I'll just wait til I get to work tonight to work in bootloader from my win7 machine there.
According to this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/ I only need to get back to s-on then flash the RUU.
but according to your guide I have to flash RUU first then s-on is optional?
WastedJoker said:
Currenttly I have ARHD 53 installed.
Bootloader is *** LOCKED *** with hboot 1.44.
My CID is 1111111 and I'll be using an o2 UK RUU.
The linux live cd method is handy but I'll just wait til I get to work tonight to work in bootloader from my win7 machine there.
According to this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/ I only need to get back to s-on then flash the RUU.
but according to your guide I have to flash RUU first then s-on is optional?
Click to expand...
Click to collapse
my guide uses decrypted ruu.zip(s), which can only be flashed with S-OFF. and I leave going from S-OFF to S-ON as the last step, just in case something didn't work correctly.
if you are going to use the 4.20.206.16 RUU.EXE then you can/should go S-ON first, and hope it works (the 4.xx RUUs have been known to sometimes give trouble depending on the PC configuration)
nkk71 said:
my guide uses decrypted ruu.zip(s), which can only be flashed with S-OFF. and I leave going from S-OFF to S-ON as the last step, just in case something didn't work correctly.
if you are going to use the 4.20.206.16 RUU.EXE then you can/should go S-ON first, and hope it works (the 4.xx RUUs have been known to sometimes give trouble depending on the PC configuration)
Click to expand...
Click to collapse
Your way makes a lot of sense! I'll get the RUU from your guide links
WastedJoker said:
Your way makes a lot of sense! I'll get the RUU from your guide links
Click to expand...
Click to collapse
for O2, you'd need to use the CWM restore method, which is a bit longer.
But here's a thought, why not stay S-OFF, try the 4.20 RUU.EXE on the Win7 PC you have, if it works then you can downgrade hboot again, go S-ON and run it again.
(because I don't recommend you go from S-Off to S-On on hboot above 1.54, as i mentioned in my guide)
if you do want to use the CWM method of my guide, let me know, and I'll link the files you'll need
EDIT: remember to change your cid back to the original, before any of this
nkk71 said:
for O2, you'd need to use the CWM restore method, which is a bit longer.
But here's a thought, why not stay S-OFF, try the 4.20 RUU.EXE on the Win7 PC you have, if it works then you can downgrade hboot again, go S-ON and run it again.
(because I don't recommend you go from S-Off to S-On on hboot above 1.54, as i mentioned in my guide)
if you do want to use the CWM method of my guide, let me know, and I'll link the files you'll need
EDIT: remember to change your cid back to the original, before any of this
Click to expand...
Click to collapse
I'll use the CWM restore method then (http://forum.xda-developers.com/showpost.php?p=47794219&postcount=5 - posting this link for my own reference)
WastedJoker said:
I'll use the CWM restore method then (http://forum.xda-developers.com/showpost.php?p=47794219&postcount=5 - posting this link for my own reference)
Click to expand...
Click to collapse
I've posted the files you'll need directly in my thread:
http://forum.xda-developers.com/showthread.php?p=54857652&postcount=1068
nkk71 said:
I've posted the files you'll need directly in my thread:
http://forum.xda-developers.com/showthread.php?p=54857652&postcount=1068
Click to expand...
Click to collapse
I'm stuck at this step:
Step 3: restore nandroid
fastboot boot CWM.img
Error in cmd:
fastboot boot cwm.img
downloading 'boot.img'...
OKAY [ 1.120s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.120s
What's going on here?
WastedJoker said:
I'm stuck at this step:
Step 3: restore nandroid
fastboot boot CWM.img
Error in cmd:
fastboot boot cwm.img
downloading 'boot.img'...
OKAY [ 1.120s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.120s
What's going on here?
Click to expand...
Click to collapse
You are locked / relocked, that comes later in CWM restore method.
If you don't wanna use unlock token, check the last few pages in my thread about masked firmware and adb commands to unlock
nkk71 said:
You are locked / relocked, that comes later in CWM restore method.
If you don't wanna use unlock token, check the last few pages in my thread about masked firmware and adb commands to unlock
Click to expand...
Click to collapse
I had the bin file handy and just tried the unlock:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
Gonna look in your thread for those other methods
here's my getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.076s
I retried the unlocking and it worked this time.
Weird.
WastedJoker said:
I had the bin file handy and just tried the unlock:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
Gonna look in your thread for those other methods
here's my getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.076s
Click to expand...
Click to collapse
I'm on my mobile, so can't help you right now, but it should be on one of the last pages.
Also after a getvar all on hboot 1.44 bootloader will freeze, so you need to unplug and replug the USB cable
nkk71 said:
I'm on my mobile, so can't help you right now, but it should be on one of the last pages.
Also after a getvar all on hboot 1.44 bootloader will freeze, so you need to unplug and replug the USB cable
Click to expand...
Click to collapse
Yeah, I saw that on your thread.
I'm back on track now - just pushing the nandroid. Thank you so much for your help, you've been amazing!
WastedJoker said:
Yeah, I saw that on your thread.
I'm back on track now - just pushing the nandroid. Thank you so much for your help, you've been amazing!
Click to expand...
Click to collapse
Ah good luck then, cause I'm getting some bad looks here, texting right now
nkk71 said:
Ah good luck then, cause I'm getting some bad looks here, texting right now
Click to expand...
Click to collapse
All done, thanks again
WastedJoker said:
All done, thanks again
Click to expand...
Click to collapse
Nice :laugh:
could you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title
Hey guys,
I was trying to change my MID using this thread http://forum.xda-developers.com/showthread.php?t=2322820
Here is the log
C:\sdk tools\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT354W913005
(bootloader) imei: 356378050014257
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3925mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
C:\sdk tools\sdk-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.051s
C:\sdk tools\sdk-tools>fastboot flash zip aman.zip
target reported max download size of 1526722560 bytes
sending 'zip' (479 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,43
(bootloader) [RUU]UZ,hboot,99
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.125s]
finished. total time: 2.375s
C:\sdk tools\sdk-tools>fastboot oem writemid PN0712000
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk tools\sdk-tools>fastboot oem writecid BS_US001
...
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.063s]
finished. total time: 0.063s
C:\sdk tools\sdk-tools>fastboot oem writemid PN0712000
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZKsM1BVUJvaEViZ2loRy0yQlk/view?usp=sharing.The bootloader is working even with the screen stuck like this but when i try to write fastboot oem rebootRUU the device switches off.Any help will be appreciated.
P.S.- Is this device soft bricked or hard bricked?
General Al Capo said:
Hey guys,
I was trying to change my MID using this thread http://forum.xda-developers.com/showthread.php?t=2322820
Here is the log
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZKsM1BVUJvaEViZ2loRy0yQlk/view?usp=sharing.The bootloader is working even with the screen stuck like this but when i try to write fastboot oem rebootRUU the device switches off.Any help will be appreciated.
P.S.- Is this device soft bricked or hard bricked?
Click to expand...
Click to collapse
Why did you use a 2 year old method to change MID ? and why change the MID at All ?
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
Click to expand...
Click to collapse
You need to reflash a good hboot .. that thing you flashed is really really old
this RUU may save you
http://forum.xda-developers.com/showthread.php?t=2358781
This is how you change the MID
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
It works in custom recovery
clsA said:
Why did you use a 2 year old method to change MID ? and why change the MID at All ?
You need to reflash a good hboot .. that thing you flashed is really really old
this RUU may save you
http://forum.xda-developers.com/showthread.php?t=2358781
This is how you change the MID
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
It works in custom recovery
Click to expand...
Click to collapse
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
General Al Capo said:
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
Click to expand...
Click to collapse
your phone was Google play edition ... I hope you did not relock the bootloader, their is no way to unlock a bootloader on the GPe
the fastboot flash zip aman.zip may have been the fatal mistake. If you can not flash another hboot over it your screwed as far as I can tell.
Maybe @alray or @Danny201281 or @nkk71 can help you
General Al Capo said:
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
Click to expand...
Click to collapse
Even if you had your own reason to change the MID I don't understand why you took the risk to use this method even if its clearly mentioned in the OP you shouldn't:
MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
Click to expand...
Click to collapse
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZ...ew?usp=sharing.
Click to expand...
Click to collapse
The device should already be rebooted to that screen before attempting to change the MID.
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
And you will obviously need to use a RUU.exe like said in the guide (not so clearly I agree) : "Run the ruu" ( as opposed to flash the ruu) is insinuating that you must use a ruu.exe.
alray said:
Even if you had your own reason to change the MID I don't understand why you took the risk to use this method even if its clearly mentioned in the OP you shouldn't:
The device should already be rebooted to that screen before attempting to change the MID.
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
And you will obviously need to use a RUU.exe like said in the guide (not so clearly I agree) : "Run the ruu" ( as opposed to flash the ruu) is insinuating that you must use a ruu.exe.
Click to expand...
Click to collapse
I am trying to run the RUU .exe but it is not recognizing my device as i am using windows 8.1. I also have the latest HTC Sync manger and drivers.It seems that ill have to give it a go in Windows 7.
General Al Capo said:
I am trying to run the RUU .exe but it is not recognizing my device as i am using windows 8.1. I also have the latest HTC Sync manger and drivers.It seems that ill have to give it a go in Windows 7.
Click to expand...
Click to collapse
Uninstall HTC Sync leave the driver
What happened to the Google play RUU.zip I linked you too?
Your not ready to flash the Developer RUU yet.
Get the phone back working with the RUU I linked first.
I use Windows 8.1 every day it only affects HTC One with hboot 1.44
You have hboot 1.54 it should work fine
clsA said:
You have hboot 1.54 it should work fine
Click to expand...
Click to collapse
Not after he flashed the modded hboot. He is now on Hboot 1.43 so he will need win 7
The problem is everytime i write fastboot oem rebootRUU the device restarts.
General Al Capo said:
The problem is everytime i write fastboot oem rebootRUU the device restarts.
Click to expand...
Click to collapse
I see potential problem.
1- asked you a question in post #5, you did not answered.
2- Told you have to use a ruu.exe so why are you still trying to "fastboot oem rebootRUU" ? You must change your MID while booted in bootloader (when you can see that messed gray screen). Once you have correct CID and MID combination, launch the RUU.exe (with the phone still bootloader mode, not in "fastboot oem rebootRUU" mode).
alray said:
I see potential problem.
1- asked you a question in post #5, you did not answered.
2- Told you have to use a ruu.exe so why are you still trying to "fastboot oem rebootRUU" ? You must change your MID while booted in bootloader (when you can see that messed gray screen). Once you have correct CID and MID combination, launch the RUU.exe (with the phone still bootloader mode, not in "fastboot oem rebootRUU" mode).
Click to expand...
Click to collapse
I did that.At the end it says error-please get the correct rom utility.
General Al Capo said:
I did that.At the end it says error-please get the correct rom utility.
Click to expand...
Click to collapse
still not answered my crucial question from post #5 :
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
Click to expand...
Click to collapse
+ I must know what ruu exactly you are trying to flash (complete file name + link to the file)
Also post your "fastboot getvar all" again so we can double check you current situation.
Andriod info of RUU
modelid: PN0712000
cidnum: BS_US001
cidnum: BS_US002
mainver: 7.17.1540.7
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
getvar all
C:\abc\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT ENG S-OFF
(bootloader) serialno: HT354W913005
(bootloader) imei: 356378050014257
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.130s
C:\abc\sdk-tools>
Click to expand...
Click to collapse
alray said:
still not answered my crucial question from post #5 :
+ I must know what ruu exactly you are trying to flash (complete file name + link to the file)
Also post your "fastboot getvar all" again so we can double check you current situation.
Click to expand...
Click to collapse
Yes you are right.I was following that guides DOS image so i did changed the MID while in RUU and it gave error.Later i did it in bootloader and it was fine.
General Al Capo said:
Andriod info of RUU
getvar all
Yes you are right.I was following that guides DOS image so i did changed the MID while in RUU and it gave error.Later i did it in bootloader and it was fine.
Click to expand...
Click to collapse
Why is your version-main now 7.17.1540.7 when it was 5.11.1700.3? The 7.17.1540.7 ruu flashed partially?
So if I understand right, you are trying to flash the 7.17.1540.7 ruu.exe when booted in bootloader mode and gives you the error to re-try with the correct rom update utility?
alray said:
Why is your version-main now 7.17.1540.7 when it was 5.11.1700.3? The 7.17.1540.7 ruu flashed partially?
So if I understand right, you are trying to flash the 7.17.1540.7 ruu.exe when booted in bootloader mode and gives you the error to re-try with the correct rom update utility?
Click to expand...
Click to collapse
My version main on my first try with ruu was 5.11.1700.3 and it said ENG boot .Then after running the ruu install ,it didnt recognize my device and so after that i installed Windows 7 and now it fails at updating data (1/5) and says ,please use the correct ROM utility.
General Al Capo said:
My version main on my first try with ruu was 5.11.1700.3 and it said ENG boot .Then after running the ruu install ,it didnt recognize my device and so after that i installed Windows 7 and now it fails at updating data (1/5) and says ,please use the correct ROM utility.
Click to expand...
Click to collapse
try with this RUU:http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-exe/. Then if it doesn't work there might be another option but im not 100% confident it will work. I think the 7.17.1540.7 ruu.exe won't flash because the hboot version is to old (1.43). We used 1.xx.xxx.xx RUU when converting phones using this procedure back in 2013, no one ever attempted to flash a 7.xx.xxx.x ruu while on the (1.43) eng hboot yet, you're the first one.
And btw, you'll definitively need to use win 7 as long as your hboot is not a least version 1.54.
alray said:
try with this RUU:http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-exe/. Then if it doesn't work there might be another option but im not 100% confident it will work. I think the 7.17.1540.7 ruu.exe won't flash because the hboot version is to old (1.43). We used 1.xx.xxx.xx RUU when converting phones using this procedure back in 2013, no one ever attempted to flash a 7.xx.xxx.x ruu while on the (1.43) eng hboot yet, you're the first one.
And btw, you'll definitively need to use win 7 as long as your hboot is not a least version 1.54.
Click to expand...
Click to collapse
Thanks for your help:good:.Will try this RUU after downloading it.
The RUU you gave me worked like a charm.Thank you for your assistance.
General Al Capo said:
The RUU you gave me worked like a charm.Thank you for your assistance.
Click to expand...
Click to collapse
glad to know everything is fine now. Don't forget if you want to convert your device again to another version, use the method clsA posted at first page. Very much easier and safer. The whole procedure is now done using a GUI (aroma installer) from a custom recovery.