Database Develop

[SOLVED] RUU Problem

Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
So here is my fix..
I flashed a bone stock rom with no root found here... or restore nandroid. I usually make a nandroid backup before i flash su.zip. but anyway, after the restore i booted into the bootloader and types fastboot oem lock. then i proceeded to reboot, but my device kept booting into bootloader. i tried fastboot erase cache which didn't help. so i grabbed the firmware from this thread http://forum.xda-developers.com/showthread.php?t=2368907 . In the bootloader type...
fastboot oem reboot RUU
now you should be in a black screen with the htc logo
fastboot flash zip /navigate/to/zip/file
you will get fail the first time(pre-hboot update: please flush immediately)
just make sure your device is still in the RUU mode(black screen with htc logo, if not redo first step)
fastboot flash zip /navigate/to/zip/file
it should proceed to flash and get flash successful!
oh you might get a loading bar underneath the htc logo. this is normal. just make sure that in the terminal it said successful.
unplug and hold the power till it restarts.
now you are bone stock with stock recovery. this is the closest I've came to being stock since there currently isn't a RUU tool for the latest firmware. hope this helps. BIG THANKS TO bigdaddy619 for the input!

Techno Droid said:
Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
Click to expand...
Click to collapse
s-off should let you ruu any image

Techno Droid said:
Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
Click to expand...
Click to collapse
The Software Version - 1.29.651.10 refers to the software version of the rom you are running if you were to flash a rom based on 1.31.651.2 your software version in settings would reflect that.
Since you are s-on your phone most likely came with 1.31.651.2 why are you trying to go backwards? If you just want to go back to stock there is a stock 1.31.651.2 rom(rooted and unrooted) in Indirects thread.

bigdaddy619 said:
The Software Version - 1.29.651.10 refers to the software version of the rom you are running if you were to flash a rom based on 1.31.651.2 your software version in settings would reflect that.
Since you are s-on your phone most likely came with 1.31.651.2 why are you trying to go backwards? If you just want to go back to stock there is a stock 1.31.651.2 rom(rooted and unrooted) in Indirects thread.
Click to expand...
Click to collapse
BC I need to send it back to sprint and plus in want to learn the process so I know exactly what im doing. Is there and ruu for the version my boot loader reflects?
Sent from my One using Tapatalk 2

Techno Droid said:
BC I need to send it back to sprint and plus in want to learn the process so I know exactly what im doing. Is there and ruu for the version my boot loader reflects?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
There is not an RUU for 1.31.651.2
I would suggest unlocking again
flash twrp 2.5.0.0
flash the Stock(no root) 1.31 rom in Indirect's thread
then relock again(your bootloader will say RE-LOCKED not LOCKED)

I kinda figured that I just had a brain fart about it. But when I flash a stock rom and relock bootloader it won't boot up I just keep booting into the bootloader. So if in was on an earlier version of 1.29.651.10 I would be able to relock and be stock, right?
Sent from my One using Tapatalk 2

Techno Droid said:
I kinda figured that I just had a brain fart about it. But when I flash a stock rom and relock bootloader it won't boot up I just keep booting into the bootloader. So if in was on an earlier version of 1.29.651.10 I would be able to relock and be stock, right?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Did you check the MD5 on the stock rom you were trying to flash maybe it was a bad download?

In was on it running and all. Then I proceeded and relocked. Or did I do something wrong here?
Sent from my One using Tapatalk 2

Techno Droid said:
In was on it running and all. Then I proceeded and relocked. Or did I do something wrong here?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Check PM

Same Issue As Techno Droid - ! SOS ! - 7 day old brick
Hi all,
I'm hoping someone can assist me here, its been a week now without my phone due to my botched attempts to flash a custom rom. I have the exact same situation as TechnoDroid's initial post, and same exact fails. I tried Techno Droids fix, but am getting the following error from this command:
fastboot oem reboot RUU
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.003s.
I've flashed the 1.31 stock ROM from Indirect's thread, and re-locked the bootloader, but I always get an OS that has no apps and begins a system boot loop after a few minutes.
Also, if I can find a compatible nandroid backup and flash it through TWRP would that be a possible fix?
Any help is greatly appreciated, I'll be looking into purchasing a backup phone from my MVNA, but would really like to unbrick this one since I paid full boat for an unlocked version!
- cheers

dancesWitShoes said:
Hi all,
I'm hoping someone can assist me here, its been a week now without my phone due to my botched attempts to flash a custom rom. I have the exact same situation as TechnoDroid's initial post, and same exact fails. I tried Techno Droids fix, but am getting the following error from this command:
fastboot oem reboot RUU
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.003s.
I've flashed the 1.31 stock ROM from Indirect's thread, and re-locked the bootloader, but I always get an OS that has no apps and begins a system boot loop after a few minutes.
Also, if I can find a compatible nandroid backup and flash it through TWRP would that be a possible fix?
Any help is greatly appreciated, I'll be looking into purchasing a backup phone from my MVNA, but would really like to unbrick this one since I paid full boat for an unlocked version!
- cheers
Click to expand...
Click to collapse
Check PM

BD619 said:
Check PM
Click to expand...
Click to collapse
having the same issue: stock deodexed flashed but unable to get ruu,, tsk (Sprint HTC One 1.29.651.10!)
pls help,,

[Q] Returning to stock for warranty repair

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Corrupt serial number and model ID

So I can't seem to find a solution to my specific issue. A little background first. I was on Modaco switch beta 13 and decided I'd move on to something else because 1) hadn't been an update for quite a while and 2) I really didn't switch back to Sense except when I wanted to play around with Zoe. I restarted into CWM recovery and tried to flash CM 11. It gave me an error and I realized I was downlevel on CWM recovery. I tried to flash an updated CWM and now only have access to fastboot. When I try to boot to recovery it gives me the HTC splashscreen and hangs. I tried TWRP, CWM, and stock with the same results.
Checking fastboot getvar I noticed some really strange entries. serialno and modelid were corrupt. Here is the output of fastboot getvar all
Code:
# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.3
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ߞ�X�C
w\ `2�#
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.063s
# fastboot getvar mid
mid: �
finished. total time: 0.002s
# fastboot getvar serialno
serialno: ߞ�X�C
w\ `2�#
finished. total time: 0.002s
I read the following post to recover my serial number
http://forum.xda-developers.com/showthread.php?t=1724475
I don't believe I had the ENG hboot so I get the following:
Code:
fastboot oem writemid PN07120
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
# fastboot oem writeserialno 1234567890
...
FAILED (status malformed (0 bytes))
finished. total time: 1.000s
I tried flashing the ENG hboot, but....
Code:
# fastboot flash zip ENG_hboot.zip
sending 'zip' (475 KB)...
OKAY [ 0.242s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.648s
Yep, catch 22. Corrupt model ID, so it won't flash.
Another interesting thing I noticed was the 2nd line on the display in fastboot
Code:
**** UNLOCKED ****
M7_UL UNKNOWN SHIP S-OFF RH
CID=BS_US001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
...
Anyway one of the messages in the forums said that once they resolved the model ID and serial number everything worked.
Unfortunately this is my main phone and I'd like to use it. Not very useful right now. Anyone have any ideas?

vmcp said:
So I can't seem to find a solution to my specific issue. A little background first. I was on Modaco switch beta 13 and decided I'd move on to something else because 1) hadn't been an update for quite a while and 2) I really didn't switch back to Sense except when I wanted to play around with Zoe. I restarted into CWM recovery and tried to flash CM 11. It gave me an error and I realized I was downlevel on CWM recovery. I tried to flash an updated CWM and now only have access to fastboot. When I try to boot to recovery it gives me the HTC splashscreen and hangs. I tried TWRP, CWM, and stock with the same results.
Checking fastboot getvar I noticed some really strange entries. serialno and modelid were corrupt. Here is the output of fastboot getvar all
Code:
# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.3
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ߞ�X�C
w\ `2�#
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.063s
**** UNLOCKED ****
M7_UL UNKNOWN SHIP S-OFF RH
CID=BS_US001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
...
Anyway one of the messages in the forums said that once they resolved the model ID and serial number everything worked.
Unfortunately this is my main phone and I'd like to use it. Not very useful right now. Anyone have any ideas?
Click to expand...
Click to collapse
Maybe you can edit the android-info.txt of the eng hboot. I.E replacing the ''MODELID: PN0710000'' for ''MODELID: ********* '' don't forget to add your CID too (BS_US001). Or maybe replacing the MODELID with your corrupted MID: (MODELID: �)
Which eng hboot are you trying to flash? There are some rumrunner hboot with eng commands set (full set of fastboot oem commands) here: http://rumrunner.us/hboots/
or maybe with the eng hboot from here
edit: Did you erased cache after flashing recovery?
if you can get recovery to boot then you could use this tool to change MID
did you tried a ruu.zip? even if im almost sure it will output the same model id error...

alray said:
Maybe you can edit the android-info.txt of the eng hboot. I.E replacing the ''MODELID: PN0710000'' for ''MODELID: ********* '' don't forget to add your CID too (BS_US001). Or maybe replacing the MODELID with your corrupted MID: (MODELID: �)
Click to expand...
Click to collapse
I was actually thinking/wondering about that. I guess that'll be my next step. I wasn't sure what to put for the MODELID since mine currently is corrupt. But I suppose I could try both. Good idea.
Which eng hboot are you trying to flash? There are some rumrunner hboot with eng commands set (full set of fastboot oem commands) here: http://rumrunner.us/hboots/
or maybe with the eng hboot from here
Click to expand...
Click to collapse
I have the ENG hboot from the 2nd link. I haven't tried rumrunner hboot. I'll d/l and give that a go too.
edit: Did you erased cache after flashing recovery?
if you can get recovery to boot then you could use this tool to change MID
Click to expand...
Click to collapse
Yes, I did erase cache. Don't know if I need to, but usually do that every time I try something.
Yeah, saw that thread too. I thought it'd be easy to do if I had adb/recovery.
did you tried a ruu.zip? even if im almost sure it will output the same model id error...
Click to expand...
Click to collapse
Yep. same result.
Thanks for the ideas, I'll give 'em a try.
EDIT: So I tried the rumrunner hboot and the ENG hboot.
Code:
# fastboot flash zip ENG_hboot.zip
< waiting for device >
sending 'zip' (474 KB)...
OKAY [ 0.241s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.648s
I got the same thing even when I tried to add the corrupt entry in the android-info.txt. Is there any way to bypass the model ID check?

DO NOT lock bootloader or go S-ON.
You should flash the HTC DEV edition firmware. Also use a different computer/USB/port to ensure this problem is in the phone

SaHiLzZ said:
DO NOT lock bootloader or go S-ON.
Click to expand...
Click to collapse
Yeah, no joke!
You should flash the HTC DEV edition firmware. Also use a different computer/USB/port to ensure this problem is in the phone
Click to expand...
Click to collapse
Yes, I tried the RUU from HTC's site for the developer edition and it claimed my battery was low. I'll charge and try again.
It was a good idea to try a different computer. I had already tried two different USB cables and a different port. All with the same results. Even the other computer gave me the same response.
So I had a few ideas. 1) modify the fastboot source to ignore the error for incorrect mid and flash anyway. After trying a few hacks with the code I read the protocol.txt and determined that it wasn't fastboot that was complaining but the bootloader. So that left my other idea (which was actually the first idea I had). Find out what that gibberish was and put that in the android-info.txt as my modelid then hope the bootloader did a compare with the gibberish I had in the android-info.txt. Unfortunately that didn't work either. I re-compiled fastboot with a few mods of my own so I could get the full details of the gibberish. I modified the output to give me the hex values of what the phone thought it's serial number and model id was. Here is the output:
Code:
# ./fastboot getvar modelid
modelid: �
b8
finished. total time: 0.002s
root# ./fastboot getvar serialno
serialno: ߞ�X�C
w\ `2�#
df9ef4588043d60a775c096032ea23
finished. total time: 0.002s
So I even tried an android-info.txt with the hex b8 value ctrl-code value, not the string b8, and got the same result...
Oh and yes I also tried with the wildcard modelid: *********
Same result.
Code:
# ./fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.071s]
finished. total time: 0.071s
# ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.042s
# ./fastboot flash zip ENG_hboot.zip
< waiting for device >
sending 'zip' (475 KB)...
OKAY [ 0.241s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.645s

vmcp said:
Yeah, no joke!
Click to expand...
Click to collapse
looks really messy in here!! :crying:
is there any way you can get to an "adb shell" (custom recovery or booted ROM)?
you have "(bootloader) version-bootloader: 1.44.0000"
can you please try
fastboot boot <name of custom recovery>.img
if you can get to adb working let me know...
---------- Post added at 09:47 PM ---------- Previous post was at 09:29 PM ----------
though just for info, last (actually, one and only attempt with such corrupt partitions), didnt work
FYI: http://forum.xda-developers.com/showpost.php?p=50067052&postcount=30

nkk71 said:
looks really messy in here!! :crying:
is there any way you can get to an "adb shell" (custom recovery or booted ROM)?
you have "(bootloader) version-bootloader: 1.44.0000"
can you please try
fastboot boot <name of custom recovery>.img
if you can get to adb working let me know...
---------- Post added at 09:47 PM ---------- Previous post was at 09:29 PM ----------
though just for info, last (actually, one and only attempt with such corrupt partitions), didnt work
FYI: http://forum.xda-developers.com/showpost.php?p=50067052&postcount=30
Click to expand...
Click to collapse
I tried this but got to the same white HTC splashscreen. Just sits there. Never seems to make it to recovery.
I've tried ADB commands, but it appears it isn't fully loaded so I'm not able to connect via ADB. I'll try flashing the RUU, but it sounds like that other person in that thread didn't have good results even after a successful RUU flash! :crying:
I'm really starting to get worried that there isn't much I can do to fix the issue. I'm going crazy without a phone.

vmcp said:
I tried this but got to the same white HTC splashscreen. Just sits there. Never seems to make it to recovery.
I've tried ADB commands, but it appears it isn't fully loaded so I'm not able to connect via ADB. I'll try flashing the RUU, but it sounds like that other person in that thread didn't have good results even after a successful RUU flash! :crying:
I'm really starting to get worried that there isn't much I can do to fix the issue. I'm going crazy without a phone.
Click to expand...
Click to collapse
I know!!! Spent 3 or 4 serious teamviewer sessions with him, after getting android-info.txt "fixed" (for that MID, if you can call it that), and successfully fully flashing ruu (from a to z), still nothing.
and without able to get (and eventually, if possible, write) to the specific partitions in question, then it looks like it will need a motherboard replacement.

nkk71 said:
I know!!! Spent 3 or 4 serious teamviewer sessions with him, after getting android-info.txt "fixed" (for that MID, if you can call it that), and successfully fully flashing ruu (from a to z), still nothing.
and without able to get (and eventually, if possible, write) to the specific partitions in question, then it looks like it will need a motherboard replacement.
Click to expand...
Click to collapse
uh oh! Perhaps the only saving grace for me is that I have an unlocked bootloader. I read about using hexedit to make a malformed android-info.txt. Perhaps I should try that. Although I'm a little worried because I kinda thought I tried that. But wasn't able to flash the ENG bootloader.

vmcp said:
uh oh! Perhaps the only saving grace for me is that I have an unlocked bootloader. I read about using hexedit to make a malformed android-info.txt. Perhaps I should try that. Although I'm a little worried because I kinda thought I tried that. But wasn't able to flash the ENG bootloader.
Click to expand...
Click to collapse
check
ROUND 2: was able to create a "good" (as you mentioned "malformed" android-info.txt), and able to flash anything and everything in ruu mode
ROUND 5: got the bootloader unlocked
==> still no joy
if you can get to read / write partitions, let me know, I know which ones i'm after, though only through adb; if there is a way doing it in fastboot i would love to know.
---------- Post added at 11:45 PM ---------- Previous post was at 11:18 PM ----------
hmm, am i thinking of what i'm thinking? would that even be possible?
OP
@ayk33
i'm gonna check something tomorrow
@ayk33 you still have that phone?

nkk71 said:
check
ROUND 2: was able to create a "good" (as you mentioned "malformed" android-info.txt), and able to flash anything and everything in ruu mode
ROUND 5: got the bootloader unlocked
==> still no joy
if you can get to read / write partitions, let me know, I know which ones i'm after, though only through adb; if there is a way doing it in fastboot i would love to know.
Click to expand...
Click to collapse
This is kinda scary. Looks like the exact same issue the other guy had!
So I found out I had a special char before the proper hex number. So I was able to flash the ENG bootloader. I've set my serial number and model ID via fastboot oem write* commands. Now getvar shows correct information:
Code:
# ./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: 1.29.401.12
(bootloader) version-misc: UNKNOWN ENG S-OFF
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN07120
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4239mV
(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!
Although all is NOT good. I still think that the model id is messed up somewhere. From the bootloader if I select "barcode", it displays correct IMEI and S/N. The Model ID is still all jacked up and has all sorts of gibberish. I don't get it because the getvar mid displays the correct model ID (PN07120).
I flashed recovery and tried to boot to recovery (also using the command you gave me), but hangs in the same spot. Still no ADB access! :crying:

vmcp said:
This is kinda scary. Looks like the exact same issue the other guy had!
So I found out I had a special char before the proper hex number. So I was able to flash the ENG bootloader. I've set my serial number and model ID via fastboot oem write* commands. Now getvar shows correct information:
Code:
# ./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: 1.29.401.12
(bootloader) version-misc: UNKNOWN ENG S-OFF
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN07120
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4239mV
(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!
Although all is NOT good. I still think that the model id is messed up somewhere. From the bootloader if I select "barcode", it displays correct IMEI and S/N. The Model ID is still all jacked up and has all sorts of gibberish. I don't get it because the getvar mid displays the correct model ID (PN07120).
I flashed recovery and tried to boot to recovery (also using the command you gave me), but hangs in the same spot. Still no ADB access! :crying:
Click to expand...
Click to collapse
Mid is 9 characters!
I'm gonna check something tomorrow... wicked!
Sent from my HTC One using Tapatalk

nkk71 said:
Mid is 9 characters!
I'm gonna check something tomorrow... wicked!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ah, that could have been my problem. I re-wrote the mid by the following:
Code:
# ./fastboot oem writemid PN0712000
...
(bootloader) Start Verify: 0
OKAY [ 0.073s]
finished. total time: 0.073s
But the model id is still messed up on the barcode.
One other thing to note is it still shows UNKNOWN instead of PVT for version-misc. I'd guess that be causing problems too. Sounds like more than just the mid and serialno got corrupt.

vmcp said:
Ah, that could have been my problem. I re-wrote the mid by the following:
Code:
# ./fastboot oem writemid PN0712000
...
(bootloader) Start Verify: 0
OKAY [ 0.073s]
finished. total time: 0.073s
But the model id is still messed up on the barcode.
One other thing to note is it still shows UNKNOWN instead of PVT for version-misc. I'd guess that be causing problems too. Sounds like more than just the mid and serialno got corrupt.
Click to expand...
Click to collapse
So any updates? The real problem is that the partition that got corrupted contains a lot of info, that cannot be found anywhere else on the phone (not only MID and serial number, much more)
I even think I've thought of a way to rewrite that partition, but the question is: with what information (MID, PID, s/n, etc).
Do you still have the box of the phone? (some of that info in that partition is on the original box, but not all of it)

nkk71 said:
I even think I've thought of a way to rewrite that partition, but the question is: with what information (MID, PID, s/n, etc).
Do you still have the box of the phone? (some of that info in that partition is on the original box, but not all of it)
Click to expand...
Click to collapse
Are you thinking mmcblk0p6, the mfg partition? I think that could work by dumping a known good one, flashing over the corrupt partition in fastboot or recovery and then using eng hboot to rewrite original sn, imei, mid, cid, etc.
Imei is etched on sim tray, other info can also be found in a couple of other partitions.

cschmitt said:
Are you thinking mmcblk0p6, the mfg partition? I think that could work by dumping a known good one, flashing over the corrupt partition in fastboot or recovery and then using eng hboot to rewrite original sn, imei, mid, cid, etc.
Imei is etched on sim tray, other info can also be found in a couple of other partitions.
Click to expand...
Click to collapse
Yep, exactly :good:
CID and IMEI, not worried about, the original ones can be found in two other partitions (unless CID was changed, but of little consequence), the bad ones (that don't seem to be anywhere else), are: MAC (hmm), MID, S/N, PID and the others I don't even know what they mean
and would the rest of the parameters in that partition (board version, gains, etc) matter.
PS: unfortunately can't seem to get to recovery in any way with a corrupt p6, trust me I tried

nkk71 said:
PS: unfortunately can't seem to get to recovery in any way with a corrupt p6, trust me I tried
Click to expand...
Click to collapse
But fastboot is OK? If so, eng hboot has a lot of commands, maybe possible to flash mfg info into p6 that way. Don't have access to my laptop atm, but can check it out later if you don't get to it first. ?

cschmitt said:
But fastboot is OK? If so, eng hboot has a lot of commands, maybe possible to flash mfg info into p6 that way. Don't have access to my laptop atm, but can check it out later if you don't get to it first. ?
Click to expand...
Click to collapse
actually, I was thinking of simply:
fastboot flash /dev/block/mmcblk0p6 <name of good p6>.img
(or /dev/mmcblk0p6 or mmcblk0p6, whatever would work)
but I would really like to pull the corrupted one first, since so many parameters are repeated in p6, then if it's only partially corrupted, one could (theoretically) reconstruct it.
Problem is, I have no idea how to "dd" it out, using only fastboot. in ENG hboot there are commands, but I've found zero (concrete) information about their use.

If the partition can be pulled using adb then it can be compared to a working file and being right information be inserted and written back to the device that is my theory.
sent from my mobile device
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
EFS professional allows this on samsung devices. Someone will need to check if the same is true on htc
sent from my mobile device

SaHiLzZ said:
If the partition can be pulled using adb then it can be compared to a working file and being right information be inserted and written back to the device that is my theory.
sent from my mobile device
Click to expand...
Click to collapse
no adb , that would make things a lot easier (maybe), only fastboot commands, so if anybody knows how to "dd" partitions using fastboot only please let us know.

[CLOSED] Finding the latest firmware update for my M7

Hey all,
I'm looking to get my phone up to date. I bought my AT&T M7 a month or two after it came out and I've never upgraded the firmware or anything besides the ROM since I bought it (2yr contract is up next week, if that helps with a timeframe). I'm looking to find the latest firmware.
Should I look for the absolute latest one, or does it depend on my ROM? I'm looking to try the Android Revolution HD ROMs and didn't see anything about a specific firmware, just that it's not a bad idea to update it.
Would there be repercussions of updating? I'm currently on an unlocked bootloader and S-ON, and I might as well leave it S-ON while I'm flashing firmware to prevent bricking (from what I read, it should work as long as everything matches, and I don't see how it could be a good idea to go S-OFF to "get around" that and risk bricking).
I could use help finding the latest firmware version, since I don't really know what to look for.
Output of "fastboot getvar all":
Code:
# fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: [omitted]
(bootloader) imei: [omitted]
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) security: on
(bootloader) build-mode: SHIP
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 170.344s
No, I'm not sure what keeps failing. The output changes everytime I run the command (different fields are shown each time, the numbers are consistent for the repeated ones). Sometimes it outputs nothing and says completed, and others it outputs some stuff like above and fails. If you know what this is indicative of, that'd be nice to know as well. Note that I'm on Debian Linux and not Windows, so I suspect my version of fastboot from the repos might not be the latest one or something like that. (I do have Win 7 and 8.1 64-bit VMs at my disposal though, so Windows only solutions should work fine too, no worries)
Thanks for any and all of your time!
jtaylor991

jtaylor991 said:
Hey all,
I'm looking to get my phone up to date. I bought my AT&T M7 a month or two after it came out and I've never upgraded the firmware or anything besides the ROM since I bought it (2yr contract is up next week, if that helps with a timeframe). I'm looking to find the latest firmware.
Should I look for the absolute latest one, or does it depend on my ROM? I'm looking to try the Android Revolution HD ROMs and didn't see anything about a specific firmware, just that it's not a bad idea to update it.
Would there be repercussions of updating? I'm currently on an unlocked bootloader and S-ON, and I might as well leave it S-ON while I'm flashing firmware to prevent bricking (from what I read, it should work as long as everything matches, and I don't see how it could be a good idea to go S-OFF to "get around" that and risk bricking).
I could use help finding the latest firmware version, since I don't really know what to look for.
Output of "fastboot getvar all":
Code:
# fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: [omitted]
(bootloader) imei: [omitted]
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) security: on
(bootloader) build-mode: SHIP
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 170.344s
No, I'm not sure what keeps failing. The output changes everytime I run the command (different fields are shown each time, the numbers are consistent for the repeated ones). Sometimes it outputs nothing and says completed, and others it outputs some stuff like above and fails. If you know what this is indicative of, that'd be nice to know as well. Note that I'm on Debian Linux and not Windows, so I suspect my version of fastboot from the repos might not be the latest one or something like that. (I do have Win 7 and 8.1 64-bit VMs at my disposal though, so Windows only solutions should work fine too, no worries)
Thanks for any and all of your time!
jtaylor991
Click to expand...
Click to collapse
If your s-on and unlocked bootloader your first step should be to achieve s-off, on hboot 1.44 you can use Revone or Rummruner. all you need is custom recovery TWRP 2.6.3.3 / Root / and a rom with insecure kernel. ARHD 31.6 should work.
After your s-off you can flash this RUU.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot flash zip RUU.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
followed by this 4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
and then this RUU.zip>> http://www.androidfilehost.com/?fid=23329332407580500
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot flash zip RUU.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
after that 1 OTA update and your on the most current version
5.12.502.2

clsA said:
and then this RUU.zip>> http://www.androidfilehost.com/?fid=23329332407580500
5.12.502.2
Click to expand...
Click to collapse
I got S-OFF and everything else has been fine up to this second RUU zip. Here's what happens:
Code:
# fastboot flash zip RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
fastboot: /tmp/buildd/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Aborted
I tried redownloading to no avail. Help?
Can I just OTA update from here since it boots (i.e. was the second RUU just to save time)? I'll wait until you say it's safe, since I'm worried that it'd mess up something somehow (as in accidentally re-lock or S-ON, etc).

I went ahead and just did the OTA update and skipped the last RUU zip and it all worked out fine. Thanks a million!
Sent from my HTC One using XDA Free mobile app

jtaylor991 said:
I went ahead and just did the OTA update and skipped the last RUU zip and it all worked out fine. Thanks a million!
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Great glad you got it all sorted out

HTC One M7 e801 bootup blankscreen

First of all, I got my m7 unlocked and stuffs. Then my supersu keep on appearing error for stop responding
Therefore I realize maybe my supersu was too old or something based on the tutorial, the zip was older version. I flashed with update-supersu.zip , thats where my nightmare begin.
I reboot after flashing it, HTC logo bootup appear then went on blankscreen. I tried to wiped data and factory reset still the same
Next I was trying to flash full firmware thought it should bring back my m7 to life, not successful, and tried different rom(Google stock rom), it all shows
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: not allowed)
Click to expand...
Click to collapse
I don't know what to do anymore, what did i miss to flash any rom or simply have my m7 works again, please help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader)
(bootloader)
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4102mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bf7e9305
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse

first of all, i figure out a few things here, maybe someone could help with my informations
If was planning to make it S-OFF but with Hboot 1.61 i will need to pay $25 for sunshine, X.
So the only way is that I flash stock M7_U 7.18.709.102 (HTC_Asia_TW), im not sure whats the correct way to do that. Or flash something ruu? I have no idea about that
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
what am I suppose to do? while the meantime im downloading the zip and its freaking slow, take very long (if someone got a better download website) due to the mirror
my recovery mode, fastboot and bootloader are functioning which is something im still happy for.
Please if someone could help me out

fungrian said:
first of all, i figure out a few things here, maybe someone could help with my informations
If was planning to make it S-OFF but with Hboot 1.61 i will need to pay $25 for sunshine, X.
So the only way is that I flash stock M7_U 7.18.709.102 (HTC_Asia_TW), im not sure whats the correct way to do that. Or flash something ruu? I have no idea about that
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
what am I suppose to do? while the meantime im downloading the zip and its freaking slow, take very long (if someone got a better download website) due to the mirror
my recovery mode, fastboot and bootloader are functioning which is something im still happy for.
Please if someone could help me out
Click to expand...
Click to collapse
Sometimes downloading things requires patience.
Im not sure exactly how S-ON flashing works but i did hear somewhere that something to do with boot image gets involved

I found out the best way to bring back my m7 is to use RUU method, but when i try to flash zip it shows "failed"
./fastboot-mac flash zip PN07IMG.zip
sending 'zip' (1975775 KB)...
FAILED (remote: 02 data length is too large)
Click to expand...
Click to collapse
FAILED (remote: 02 data length is too large)
maybe the RUU is not right for my phone?
Don't know whether is it i downloaded wrong rom file for my device

fungrian said:
I found out the best way to bring back my m7 is to use RUU method, but when i try to flash zip it shows "failed"
FAILED (remote: 02 data length is too large)
maybe the RUU is not right for my phone?
Don't know whether is it i downloaded wrong rom file for my device
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a RUU if it's a Lollipop version (version starting with 7.xx.xxx.x). Others fastboot versions won't work.
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
fungrian said:
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
Click to expand...
Click to collapse
Does not apply to the M7, the boot partition isn't write protected like previous htc devices.