Database Develop

[Q] Help With Updates !!!!

I have HTC Incredible S, which i update it to the last version 3.08 with HBOOT 2.00.000, I tried to change its CID after downgrading the Main version and i got my phone bricked... So i took it to a store to fix it and they run it alive again... I have the handset now S-OFF with HBOOT 1.13.0000 and android version 2.3.3 and when i try to check for updates it gives me that no updates are available although the update is available to android version 3.08....
What Can I do please help to get my device takes updates again???

At h-boot 1.13 your phone is incredibly easy to root and install custom ROM's on, I suggest you root your phone and install one of the custom ROM's on the dev page opposed to updating to stock.
Sent from my Incredible S

Sir I can't update my phone and when I flash RUU Rom I have this message :
sending 'zip' (252201 KB)...
OKAY [ 42.530s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 51.866s
Any Ideas

talal_zaki said:
I have HTC Incredible S, which i update it to the last version 3.08 with HBOOT 2.00.000, I tried to change its CID after downgrading the Main version and i got my phone bricked... So i took it to a store to fix it and they run it alive again... I have the handset now S-OFF with HBOOT 1.13.0000 and android version 2.3.3 and when i try to check for updates it gives me that no updates are available although the update is available to android version 3.08....
What Can I do please help to get my device takes updates again???
Click to expand...
Click to collapse
Did you see what the store did to you phone to "run it alive again"?

talal_zaki said:
Sir I can't update my phone and when I flash RUU Rom I have this message :
sending 'zip' (252201 KB)...
OKAY [ 42.530s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 51.866s
Any Ideas
Click to expand...
Click to collapse
Model ID check indicates that you are attempting to flash a RUU that is not meant for your device. Which RUU/ROM.zip are you trying to flash?
Can you get into FASTBOOT USB mode and enter the following command and post your results:
fastboot getvar all

They RIFF BOX it again coz it was dead...

INFOversion: 0.5
INFOversion-bootloader: 6.13.9999
INFOversion-baseband: 3805.06.03.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.30.415.1
INFOserialno: HT131TD07312
INFOimei: 355301043098113
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3212***
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4024mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: -0.000s

talal_zaki said:
INFOversion: 0.5
INFOversion-bootloader: 6.13.9999
INFOversion-baseband: 3805.06.03.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.30.415.1
INFOserialno: HT131TD07312
INFOimei: 355301043098113
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3212***
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4024mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: -0.000s
Click to expand...
Click to collapse
There's something VERY wrong with your modelid. I would recommend flashing a custom rom if you need your phone in a hurry.
Go back to the guy who riffed your phone, he's put the wrong model ID on it. That's for the Canadian Bell mobile if i'm not mistaken

is there something i can do to get back my phone again without going to the guy who riffed my phone???

talal_zaki said:
is there something i can do to get back my phone again without going to the guy who riffed my phone???
Click to expand...
Click to collapse
I'm quite certain there is not a way to change the modelid through adb or fastboot. If you really want to flash RUU rom, which is the impression I get as you have disregarded on more than one occasion to flash a custom rom, then you will have to copy the rom.zip from the temp directory when you start up the ruu program, extract the android-info.txt, edit the modelid: PG3213000 to modelid: PG3212000, add back to the rom.zip, rename the rom.zip to PG32IMG.zip, copy it to your sdcard, restart your phone in hboot mode and install it that way.
Keeping in mind that you will have to do these steps every time you wish to flash a new stock rom, going back to the vendor or flashing a custom rom seems easier IMO

will try in a few hours, after work hope it will work.

talal_zaki said:
is there something i can do to get back my phone again without going to the guy who riffed my phone???
Click to expand...
Click to collapse
Nonverbose said:
I'm quite certain there is not a way to change the modelid through adb or fastboot. If you really want to flash RUU rom, which is the impression I get as you have disregarded on more than one occasion to flash a custom rom, then you will have to copy the rom.zip from the temp directory when you start up the ruu program, extract the android-info.txt, edit the modelid: PG3213000 to modelid: PG3212000, add back to the rom.zip, rename the rom.zip to PG32IMG.zip, copy it to your sdcard, restart your phone in hboot mode and install it that way.
Keeping in mind that you will have to do these steps every time you wish to flash a new stock rom, going back to the vendor or flashing a custom rom seems easier IMO
Click to expand...
Click to collapse
From the looks of your getvar values, you currently have S-OFF at this point, too, so modifying the android-info.txt file inside a PG32IMG.zip file will definitely allow you to flash a RUU even though your modelid is PG3212***

Dear Sir I ca not flash RUU, I have the same problem always (modelid)...

tpbklake said:
From the looks of your getvar values, you currently have S-OFF at this point, too, so modifying the android-info.txt file inside a PG32IMG.zip file will definitely allow you to flash a RUU even though your modelid is PG3212***
Click to expand...
Click to collapse
talal_zaki said:
Dear Sir I ca not flash RUU, I have the same problem always (modelid)...
Click to expand...
Click to collapse
You need to extract the ROM.zip from the RUU and then you can edit the android-info.txt file in the ROM.zip and add modelid = PG3212*** to the this file.
Then copy the ROM.zip file to your sd card and name it PG32IMG.zip. That will allow you to flash the via the bootloader.

Can I Format the Phone to change its model ID??
The Model ID still the same, 3212*** i want to change it to 3213*** Please help coz all of these steps wont work, I asked the shop who repaired my Incredible S and he said that he made a permanant S-OFF with XTC Clip....

talal_zaki said:
The Model ID still the same, 3212*** i want to change it to 3213*** Please help coz all of these steps wont work, I asked the shop who repaired my Incredible S and he said that he made a permanant S-OFF with XTC Clip....
Click to expand...
Click to collapse
It is good that you are S-OFF with XTC Clip, however, you cannot change the modelid on the phone.
You need to modify the android-info.txt file in the PG32IMG.zip file on the SD card to allow it to flash on your PG3212000. That is how you are going to get the rom reflashed.

I changed the model ID from PG3212*** to PG3213*** and installed a RUU rom but it stills not taking updates (any ideas)

talal_zaki said:
I changed the model ID from PG3212*** to PG3213*** and installed a RUU rom but it stills not taking updates (any ideas)
Click to expand...
Click to collapse
Can we see a new getvar output. State what ruu you installed,if it succeeded,and what you want it to do next. Try to be as clear and complete as possible to help us understand how to advise you.

INFOversion: 0.5
INFOversion-bootloader: 2.00.0000
INFOversion-baseband: 3822.10.08.28_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.08.405.3
INFOserialno: HT131TD07312
INFOimei: 355301043098113
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213***
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3867mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-af9874be
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: -0.000s
I tried RUU roms RUU_VIVO_ARA_2.3.3>>> (no updates)
I tried RUU_VIVO_ARA_1.42 (NO Updates)
I tried RUU_VIVO_ARA_2.12 (NO updates)...
Finally I Installed RUU_VIVO_SENSE3.0... (NO Updates)
even I put some OTA files on the memory card but the phone wont install or see them

You're on gb 2.3.5 with sense3.0 what exactly do you believe you can update to?

[Q] modelid is PN071*****?

Is that supposed to happen? Is it safe to assume that my mid is PN0710000 then? if not, how should I fix this?

Wait, where is written this MID?

in adb when trying to fastboot getvar all. It probably didn't help that it says getvar all failed, but I'm stuck here

Wait, if you will you the command:
Code:
fastboot getvar all
you musb be in fastboot usb.
If you're in android, you can boot in fastboot with the command:
Code:
adb reboot bootloader[/url] and now you can use the getvar.
p.s. Post it here deleting imei and serial number :)

I did it just like that, did it a couple more times just to make sure, and still got the same result. Anyways:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 5.29.401.13
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: xxxxxxxxxx
INFOimei: xxxxxxxxx
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN071****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4310mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.067s
Click to expand...
Click to collapse
please tell me this can be fixed...

Habel said:
I did it just like that, did it a couple more times just to make sure, and still got the same result.
Click to expand...
Click to collapse
Your version main start with 5, when the latest base starts with 3, and this is strange.
However, have you flashed some firmware in this period?
Probably there is a solution, but i don't know atm.

well, I just bought this phone yesterday (yay me), realized something was off when I couldn't OTA update (which is because of S-off), and now afraid to just flash the new 3.62 firmware because of the stars (asterisks?). could it be i did something wrong with the commands?

Try to flash a ruu for your phone

ok, I'll take a look at that. thanks for your help Guich
edit: what kind of RUU should I get? do i need to match it with the bootloader or something else, or any one of them works?

Habel said:
ok, I'll take a look at that. thanks for your help Guich
edit: what kind of RUU should I get? do i need to match it with the bootloader or something else, or any one of them works?
Click to expand...
Click to collapse
A ruu compatible with your cid
Because you're s-off and all ruu can be flashed fine!

hey Guich, I took your advice and tried to flash the RUU, but now i'm getting very confused. the flashing went fine, but I see no changes on my phone. In Settings>About>Software Information the software version is still 1.29.401.13, while getvar all shows me that the version is 3.62.401.1. Is there anything I'm misunderstanding here?
edit: do i need to unlock the bootloader for any of this?

I have same PN071**** I dont remember what was there before I have it from Ebay probly some Chinesse version but the cover say that it is PN714000, I accidently changed S-OFF to S On and flashed another rom.I cant do S-OFF anymore tried many things. Riffbox doesnt work with 714000 unfortunately.

[SOLVED] Google'd and Google'd but still need help

Hi guys
I have looked and looked but need some help
I have a HTC One which I successfully converted to a "stock" GPE with no problems, but I have found that I miss some little bit HTC Zoe for example.I can detect the device with ADB and can use oem writecid to change to HTC__001 which I need to flash the RUU.zip
I have tried tool kits and adb but I am having no luck with the following.
Changing the MID so I can flash a stock RUU
Unlocking the RELOCKED bootloader
I have S-Off
Below is where I am at the moment.
******RELOCKED*******
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT- 1.54. 0000
RADIO-4T. 21. 3218. 21
OpenDSP-v32. 120. 274. 0909
OS- 3.62. 1700. 1
eMMC-boot 2048MB
Dec 9 2013, 00:38:19. 0
Any help or guidance would be great

lspec230 said:
Hi guys
I have looked and looked but need some help
I have a HTC One which I successfully converted to a "stock" GPE with no problems, but I have found that I miss some little bit HTC Zoe for example.I can detect the device with ADB and can use oem writecid to change to HTC__001 which I need to flash the RUU.zip
I have tried tool kits and adb but I am having no luck with the following.
Changing the MID so I can flash a stock RUU
Unlocking the RELOCKED bootloader
I have S-Off
Below is where I am at the moment.
******RELOCKED*******
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT- 1.54. 0000
RADIO-4T. 21. 3218. 21
OpenDSP-v32. 120. 274. 0909
OS- 3.62. 1700. 1
eMMC-boot 2048MB
Dec 9 2013, 00:38:19. 0
Any help or guidance would be great
Click to expand...
Click to collapse
With S-OFF you don't need an unlocked bootloader tu flash in ruu mode.
so change your CID to HTC__001:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
then use this tool to change MID back to PN0710000
you must use this tool from custom recovery so if you are on stock recovery, yes you will have to unlock bootloader again and flash latest twrp recovery.Unlock Via htcdev or with s-off method, as you wish.
then follow nkk71's guide to return to stock (linked in my signature below). Follow post #1 and #3 (use ruu.zip method) with 1.28.401.7 ruu.zip from htc1guru.com

Thanks for your help
alray said:
With S-OFF you don't need an unlocked bootloader tu flash in ruu mode.
so change your CID to HTC__001:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
then use this tool to change MID back to PN0710000
you must use this tool from custom recovery so if you are on stock recovery, yes you will have to unlock bootloader again and flash latest twrp recovery.Unlock Via htcdev or with s-off method, as you wish.
then follow nkk71's guide to return to stock (linked in my signature below). Follow post #1 and #3 (use ruu.zip method) with 1.28.401.7 ruu.zip from htc1guru.com
Click to expand...
Click to collapse
I used HTCDev to get unlock, I have kept the unlock.bin but it doesn't seem to work now.....is that because I have changed CID and MID? Do i need to go back to HTCDev and get another unlock
Thanks for the quick reply...exactly what i needed a clear concise way ahead rather than me stumbling around with frustration

@lspec230 just to be sure you see that I have edited my above post with additional info
if you have more questions, just ask here. I'll be back in a few hours but im sure others members will assist you here.
---------- Post added at 06:14 PM ---------- Previous post was at 06:14 PM ----------
lspec230 said:
I used HTCDev to get unlock, I have kept the unlock.bin but it doesn't seem to work now.....is that because I have changed CID and MID? Do i need to go back to HTCDev and get another unlock
Thanks for the quick reply...exactly what i needed a clear concise way ahead rather than me stumbling around with frustration
Click to expand...
Click to collapse
You need a new unlock code each time

ARGH...Unlock not working
alray said:
@lspec230 just to be sure you see that I have edited my above post with additional info
if you have more questions, just ask here. I'll be back in a few hours but im sure others members will assist you here.
---------- Post added at 06:14 PM ---------- Previous post was at 06:14 PM ----------
You need a new unlock code each time
Click to expand...
Click to collapse
I went to HTCDev and got a new Unlock_code.bin with no trouble at all.
Used the following and all appears to push to the device but then nothing, I dont get the HTC Bootloader splash screen asking if i want to proceed.
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x8
6_64-20131030\sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s

Forget about the bootloader unlocking. Change MID/CID and flash a full RUU!
Luckily you are soff
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
Also, are you rooted?

Still no luck
Not sure what's going on....I cant install TWRP on there to change the MID or Flash a stock RUU
I tried from ADB and for past experience from Samsung also copied it to the phone hoping I could flash from recovery, but there isn't an option for that.
Cant help but think the RELOCKED flag is causing the problems.
I will try a factory reset and cache/partition wipe and start again.
I suppose one option is to flash a RUU that will work with my current MID. Then start the process from there.....

lspec230 said:
Not sure what's going on....I cant install TWRP on there to change the MID or Flash a stock RUU
I tried from ADB and for past experience from Samsung also copied it to the phone hoping I could flash from recovery, but there isn't an option for that.
Cant help but think the RELOCKED flag is causing the problems.
I will try a factory reset and cache/partition wipe and start again.
I suppose one option is to flash a RUU that will work with my current MID. Then start the process from there.....
Click to expand...
Click to collapse
can you post the current "fastboot getvar all" (excluding IMEI and s/n) and I'll post a package for you.

getvar
nkk71 said:
can you post the current "fastboot getvar all" (excluding IMEI and s/n) and I'll post a package for you.
Click to expand...
Click to collapse
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-20
6_64-20131030\sdk\platform-tools>fastboot getvar all
(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.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3822mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
There you go...This has now got personal, I could stay with GPE but I amnow determined to get this to work!!
Many thanks for the help so far...really appreciate it

lspec230 said:
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-20
6_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
all: Done!
finished. total time: 0.066s
There you go...This has now got personal, I could stay with GPE but I amnow determined to get this to work!!
Many thanks for the help so far...really appreciate it
Click to expand...
Click to collapse
Here you go, download that, then
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3.zip
fastboot reboot-bootloader
-> enter TWRP, use Guru Bootloader Reset tool, or scotty's adb command to unlock

Thanks for your help
nkk71 said:
Here you go, download that, then
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3.zip
fastboot reboot-bootloader
-> enter TWRP, use Guru Bootloader Reset tool, or scotty's adb command to unlock
Click to expand...
Click to collapse
All sorted thanks so much for the help
Not sure if I will even understand but what was going wrong?
:good:

lspec230 said:
All sorted thanks so much for the help
Not sure if I will even understand but what was going wrong?
:good:
Click to expand...
Click to collapse
now follow @alray's instructions to change MID and CID, and flash stock Sense ruu.zip
remember to stay S-Off, and in my guide check "Not so FAQ #2" to see what was wrong.

ALL DONE!
nkk71 said:
now follow @alray's instructions to change MID and CID, and flash stock Sense ruu.zip
remember to stay S-Off, and in my guide check "Not so FAQ #2" to see what was wrong.
Click to expand...
Click to collapse
To all who helped many thanks.....now back on sense!! that was a mission!!

lspec230 said:
To all who helped many thanks.....now back on sense!! that was a mission!!
Click to expand...
Click to collapse
Congrats,
if you could also edit main thread title to include [SOLVED], thanks

One last question...OTA updates
nkk71 said:
Congrats,
if you could also edit main thread title to include [SOLVED], thanks
Click to expand...
Click to collapse
Followed your guide, and went S-On thinking i would get OTA's is this right?
I have included my getvar all
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-201310
6_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-baseband: 4A.13.3227.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.20.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.054s
Also attached is my software info

lspec230 said:
Followed your guide, and went S-On thinking i would get OTA's is this right?
I have included my getvar all
C:\Users\Neil\Downloads\adt-bundle-windows-x86_64-201310
6_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.43.0000
(bootloader) version-main: 1.20.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
Also attached is my software info
Click to expand...
Click to collapse
1- Why oh why did you go S-On?? You don't need S-On for OTAs
2- Why dint you read this: "---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead"
Okay so now you're S-On, bootloader locked or unlocked?
bootloader has to be locked or relocked, then go ahead and flash the 1.28.401.7 ruu.zip, then get S-Off!
then stay UNLOCKED and S-Off and take all the OTAs you like then report back
any reason you need S-On??

nkk71 said:
1- Why oh why did you go S-On?? You don't need S-On for OTAs
2- Why dint you read this: "---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead"
Okay so now you're S-On, bootloader locked or unlocked?
bootloader has to be locked or relocked, then go ahead and flash the 1.28.401.7 ruu.zip, then get S-Off!
then stay UNLOCKED and S-Off and take all the OTAs you like
any reason you need S-On??
Click to expand...
Click to collapse
Because I am a FOOL!!! I missed that by not reading properly....

lspec230 said:
Because I am a FOOL!!! I missed that by not reading properly....
Click to expand...
Click to collapse
okay, so slow it down a little, take a deep breath and no panicking or rushing things!!! okay?
Here's what you're going to do:
1- lock/relock bootloader
2- flash ruu.zip 1.28.401.7
3- DO NOT TAKE ANY OTAs
4- use revone, to get S-Off, and unlock your phone
Once that is done report back, if you have questions, please go ahead ask before doing things
---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------
lspec230 said:
Because I am a FOOL!!! I missed that by not reading properly....
Click to expand...
Click to collapse
PS: if ruu.zip fails, giving "signature fail" it's cause it's not signed and you are now S-ON.
in that case use RUU.EXE: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
no need to "downgrade hboot", just run the RUU.EXE, NOTHING ELSE and report back with a "fastboot getvar all"

lspec230 said:
Because I am a FOOL!!! I missed that by not reading properly....
Click to expand...
Click to collapse
alray said:
Follow post #1 and #3 (use ruu.zip method) with 1.28.401.7 ruu.zip from htc1guru.com
Click to expand...
Click to collapse
2) RUU.ZIP (Windows7, Mac, Linux): http://www.htc1guru.com/downloads/ruu-zip-downloads/ <- this is now the preferred method instead of RUU.EXE
------> if you’ve found a RUU.ZIP proceed to post 3
---------> Note: M7_UL .401. users don't use 1.20.401.1, use 1.28.401.7 instead
Click to expand...
Click to collapse
hopefully you did not bricked your phone here,just take your time to read carefully next time

alray said:
hopefully you did not bricked your phone here,just take your time to read carefully next time
Click to expand...
Click to collapse
i don't think a brick is involved, but i guess i need to do some revisions about the S-On part (when it's needed and when not ), but as someone mentioned, the guide is "cluttered" already :crying:
@lspec230 any progress mate?

Unable to flash latest firmware (s-off)

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/

[Q] Cyanogen to clean sense 6 kitkat

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?