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] Can't S-ON?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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?

[SOLVED]Hard bricked HTC one m7 any help?

Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly (before, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone went into bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
EDIT1: 8. rewritten version-main from 4.19.xxxxxx to 1.00.000.0 (via HTC One All-In-One Toolkit by Hasoon2000) in an desperate attempt to fix ruu flashing, no luck as well (i think that even broke more things )
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 3544************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi

uuzi said:
Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly my phone (before brick, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone was in a bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 354436054678733
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi
Click to expand...
Click to collapse
First of all and as I'm sure you've discovered going back to S-on is never a good fix for anything except warranty
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before. Don't know if this is a hardware issue. Flashing firmware may solve it but with s-on and super cid I'm not even sure thats possible or which firmware you can use with your version main that way. Going back to s-on may well have been the nail in the coffin here I'm afraid.
If your able to boot recovery you can push a rom to flash but you need to fix the firmware first as I fear that's the cause of your bootloop. Hopefully @nkk71 @clsA or @majmoz have somthing to add here :good:

oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.

uuzi said:
oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.
Click to expand...
Click to collapse
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP

uuzi said:
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
Click to expand...
Click to collapse
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
i'm not really sure right now, i'm trying again now

Danny201281 said:
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before.
Click to expand...
Click to collapse
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
uuzi said:
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP
Click to expand...
Click to collapse
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?

Result:
Code:
C:\unbrick>fastboot oem rebootRUU
(bootloader) Start Verify: 3
OKAY [ 0.030s]
finished. total time: 0.031s
C:\unbrick>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 32.802s]
writing 'zip'...
(bootloader) signature checking...
FAILED (status read failed (Unknown error))
finished. total time: 801.973s

nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?
Click to expand...
Click to collapse
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery

nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
Click to expand...
Click to collapse
Yeah I got that after he had said he'd changed it manually. Just caught me off guard thought it was something bigger. :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 05:01 PM ---------- Previous post was at 04:57 PM ----------
uuzi said:
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery
Click to expand...
Click to collapse
What about TWRP 2.6.3.3 If it's still working maybe you can flash ARHD to get it booting maybe.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!

uuzi said:
OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!
Click to expand...
Click to collapse
Glad to here your back up good job :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

I can not return to official rom

hi guys
first excuse me for bad English and second, for being so dumb
I will summarize to save time
I decided to use a rom cyanogen on my device
only I did not have proper care and did not do the backup security official rom
Now I want to go back to stock version
tried several guides the internet and none helped me, always returns me errors
I have written official recovery, and locked the bootloader
I can not find RUU.exe for my version
Here is what I did and the mistakes returns?
C: \ Fastboot> fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microprocessor: None
INFOversion-main: 6.15.599.101
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
Infoproduct: m7_u
INFOplatform: HBOOT-8064
INFOmodelid: PN0711000
INFOcidnum: HTC__332
INFObattery-status: good
INFObattery-voltage: 3858mV
INFOpartition-layout: Generic
Infosecurity: on
INFObuild-mode: SHIP
INFOboot-mode: fastboot
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. Total time: 0.050s
I used this same version as of this writing al 6.15.599.101, and was not, the bootloader this relocked and the recovery this the 4.4.3_stock-recovery works ... and enter the official recovery the it was before, and even Then relocked the error I have not found the RUU.exe to this version, most believe TBM would not work because the fastboot already given Beheerder error ..... I tried to write que way, Then I downloaded the official rom here http: // www .htcdev.co ... r / downloads / P75 notice, is the seventh rom from top to bottom, exactly q is described on my device,
One M7
HTC LA SPA (ES) MR 1424 3.4.10 v4.4.3
6.15.599.101
after downloading, the renamed file to rom and put in fo fastboot folder, casette The Following command:
C: \ Fastboot> fastboot oem rebootRUU
... INFOStart Verify: 3
OKAY [0.031s]
finished. Total time: 0.033s
C: \ Fastboot> fastboot flash zip rom.zip
sending 'zip' (433842 KB) ... OKAY [38.841s]
writing 'zip' ... INFOsignature checking ...
FAILED (remote: 12 signature verify fail)
finished. Total time: 84.695s
with the unlock bootloader of this msg When trying to flash:
C: \ Fastboot> fastboot flash zip rom.zip
sending 'zip' (433842 KB) ... OKAY [39.89
writing 'zip' ... InfoZip head
InfoZip info parsing ...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. Total time: 40.131s
sorry to bother
If anyone knows help me I will be very grateful :good:

Steel-Cleiton said:
hi guys
first excuse me for bad English and second, for being so dumb
I will summarize to save time
I decided to use a rom cyanogen on my device
only I did not have proper care and did not do the backup security official rom
Now I want to go back to stock version
tried several guides the internet and none helped me, always returns me errors
I have written official recovery, and locked the bootloader
I can not find RUU.exe for my version
Here is what I did and the mistakes returns?
C: \ Fastboot> fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microprocessor: None
INFOversion-main: 6.15.599.101
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
Infoproduct: m7_u
INFOplatform: HBOOT-8064
INFOmodelid: PN0711000
INFOcidnum: HTC__332
INFObattery-status: good
INFObattery-voltage: 3858mV
INFOpartition-layout: Generic
Infosecurity: on
INFObuild-mode: SHIP
INFOboot-mode: fastboot
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. Total time: 0.050s
I used this same version as of this writing al 6.15.599.101, and was not, the bootloader this relocked and the recovery this the 4.4.3_stock-recovery works ... and enter the official recovery the it was before, and even Then relocked the error I have not found the RUU.exe to this version, most believe TBM would not work because the fastboot already given Beheerder error ..... I tried to write que way, Then I downloaded the official rom here http: // www .htcdev.co ... r / downloads / P75 notice, is the seventh rom from top to bottom, exactly q is described on my device,
One M7
HTC LA SPA (ES) MR 1424 3.4.10 v4.4.3
6.15.599.101
after downloading, the renamed file to rom and put in fo fastboot folder, casette The Following command:
C: \ Fastboot> fastboot oem rebootRUU
... INFOStart Verify: 3
OKAY [0.031s]
finished. Total time: 0.033s
C: \ Fastboot> fastboot flash zip rom.zip
sending 'zip' (433842 KB) ... OKAY [38.841s]
writing 'zip' ... INFOsignature checking ...
FAILED (remote: 12 signature verify fail)
finished. Total time: 84.695s
with the unlock bootloader of this msg When trying to flash:
C: \ Fastboot> fastboot flash zip rom.zip
sending 'zip' (433842 KB) ... OKAY [39.89
writing 'zip' ... InfoZip head
InfoZip info parsing ...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. Total time: 40.131s
sorry to bother
If anyone knows help me I will be very grateful :good:
Click to expand...
Click to collapse
Sorry, I can't understand everything you said but first edit your first post and remove your IMEI and SERIALNO. Dont post these number ever, you want to keep these numbers for yourself.
There is no ruu for .599 version neither any stock rom. The file you are trying to flash is not a ruu/rom, its a kernel source and its not useful for your situation.
You can use custom roms, or you will need to achieve s-off to change your CID/MID and use another ruu version like the .401 version or the .1540 version.

alray said:
Sorry, I can't understand everything you said but first edit your first post and remove your IMEI and SERIALNO. Dont post these number ever, you want to keep these numbers for yourself.
There is no ruu for .599 version neither any stock rom. The file you are trying to flash is not a ruu/rom, its a kernel source and its not useful for your situation.
You can use custom roms, or you will need to achieve s-off to change your CID/MID and use another ruu version like the .401 version or the .1540 version.
Click to expand...
Click to collapse
thanks for your response man
I edited and the first post as requested
I now understand that I can not go back to version 599 stock
if I use another CID / MID will be able to receive OTA updates in the future?
anyway I can not go back to version 599, I will have to use another stock like you said
you could teach me how to make changes, to use another version rom stock?
sorry for bad English

Steel-Cleiton said:
if I use another CID / MID will be able to receive OTA updates in the future?
Click to expand...
Click to collapse
Yes
you could teach me how to make changes, to use another version rom stock?
Click to expand...
Click to collapse
Flash a close to stock rom (needed to achieve s-off)
achieve s-off using sunshine (will cost you 25$)
change your CID to BS_US001
Code:
fastboot oem writecid BS_US001
change your MID to PN0712000 using the MID change tool in custom recovery
flash the 6.07.1540.2 RUU.

alray said:
Yes
Flash a close to stock rom (needed to achieve s-off)
achieve s-off using sunshine (will cost you 25$)
change your CID to BS_US001
Code:
fastboot oem writecid BS_US001
change your MID to PN0712000 using the MID change tool in custom recovery
flash the 6.07.1540.2 RUU.
Click to expand...
Click to collapse
let's see if I understand
sunshine is a paid program ?
is this site I'll download it http://theroot.ninja/download.html
he is a .apk?
I will install on HTC and runs it?
I understand the rest of what you said
only on the sunshine did not quite understand how to make
Thx and sorry my bad english

Steel-Cleiton said:
let's see if I understand
sunshine is a paid program ?
is this site I'll download it http://theroot.ninja/download.html
he is a .apk?
I will install on HTC and runs it?
I understand the rest of what you said
only on the sunshine did not quite understand how to make
Thx and sorry my bad english
Click to expand...
Click to collapse
Yes sunshine is a paid app to achieve s-off. Sunshine is the only method to s-off HTC One on Hboot 1.57. This app must be used on a close to stock rom to work correctly. Before charging you the 25$ (via paypal) the app will run some tests to make sure s-off is possible so you will not pay anything if s-off is not achieved.

alray said:
Yes sunshine is a paid app to achieve s-off. Sunshine is the only method to s-off HTC One on Hboot 1.57. This app must be used on a close to stock rom to work correctly. Before charging you the 25$ (via paypal) the app will run some tests to make sure s-off is possible so you will not pay anything if s-off is not achieved.
Click to expand...
Click to collapse
ok I've downloaded the sunshine .apk
I can install it without problems
only that I get the following msg when I run the software:
your device has debuggable rmdisk (ro debuggable=1). you need to flash a non-debuggable boo.img stock would be best
another question noob
I live in Brazil
this CID will work all operators?
4g will work as before?
there is some CID running all operators?
If the answer is yes, I will continue to receive OTA update?
I mean if I install a CID for all operators

Steel-Cleiton said:
ok I've downloaded the sunshine .apk
I can install it without problems
only that I get the following msg when I run the software:
your device has debuggable rmdisk (ro debuggable=1). you need to flash a non-debuggable boo.img stock would be best
Click to expand...
Click to collapse
Flash a stock rom!
this one should work fine
another question noob
I live in Brazil
this CID will work all operators?
4g will work as before?
there is some CID running all operators?
If the answer is yes, I will continue to receive OTA update?
I mean if I install a CID for all operators
Click to expand...
Click to collapse
4G will work fine as before (no LTE).
BS_US001 is the dev edition cid so you'll get ota updates everywhere.

alray said:
Flash a stock rom!
4G will work fine as before (no LTE).
BS_US001 is the dev edition cid so you'll get ota updates everywhere.
Click to expand...
Click to collapse
Now I was confused, sorry my ignorance
I ask a little patience I'm understanding gradually
every time I tried to flash a rom received errors
how do I write this rom you posted?
I use fastboot or TWRP for this?
need to write the official recovery and lock the bootloader?
I'm already very grateful to you man
I tried a lot of help throughout internet
and only you so far helped me
thank you for the patience that is having me

Steel-Cleiton said:
Now I was confused, sorry my ignorance
I ask a little patience I'm understanding gradually
every time I tried to flash a rom received errors
how do I write this rom you posted?
I use fastboot or TWRP for this?
need to write the official recovery and lock the bootloader?
I'm already very grateful to you man
I tried a lot of help throughout internet
and only you so far helped me
thank you for the patience that is having me
Click to expand...
Click to collapse
no don't lock the bootloader and don't flash the stock recovery. Just copy the rom to your phone storage and flash in using twrp recovery.

alray said:
no don't lock the bootloader and don't flash the stock recovery. Just copy the rom to your phone storage and flash in using twrp recovery.
Click to expand...
Click to collapse
I'll try when I get home
I'm at work now, get out of here one hour
thanks a lot:good:

alray said:
no don't lock the bootloader and don't flash the stock recovery. Just copy the rom to your phone storage and flash in using twrp recovery.
Click to expand...
Click to collapse
uhuuuuuuuuuuuuuu
worked my friend
now a question
this is a rom stock?
or is a developer rom?
the CID needs to be changed to match the version of the rom, just so I can receive OTA?
if I do not change CID and continue using this rom version, I can receive OTA update?
there is some rom stock lollipop version?
thank you my friend
I warmly thank for your patience

Steel-Cleiton said:
uhuuuuuuuuuuuuuu
worked my friend
now a question
this is a rom stock?
or is a developer rom?
the CID needs to be changed to match the version of the rom, just so I can receive OTA?
if I do not change CID and continue using this rom version, I can receive OTA update?
there is some rom stock lollipop version?
thank you my friend
I warmly thank for your patience
Click to expand...
Click to collapse
If you have achieved S-OFF then follow the steps alray posted here starting with Step 3. When you complete the steps successfully your phone will be a DevEd on the last version waiting for the Lollipop OTA.

majmoz said:
If you have achieved S-OFF then follow the steps alray posted here starting with Step 3. When you complete the steps successfully your phone will be a DevEd on the last version waiting for the Lollipop OTA.
Click to expand...
Click to collapse
yes I did all the steps
not only posted yesterday because it was late
Alray was my master
I owe much to him

alray said:
no don't lock the bootloader and don't flash the stock recovery. Just copy the rom to your phone storage and flash in using twrp recovery.
Click to expand...
Click to collapse
hello my good friend
I learned what you taught me
was complicated by I do not have a good English
more I got it, thanks for your patience
look:
before:
C: \ Fastboot> fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microprocessor: None
INFOversion-main: 6.15.599.101
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
Infoproduct: m7_u
INFOplatform: HBOOT-8064
INFOmodelid: PN0711000
INFOcidnum: HTC__332
INFObattery-status: good
INFObattery-voltage: 3858mV
INFOpartition-layout: Generic
Infosecurity: on
INFObuild-mode: SHIP
INFOboot-mode: fastboot
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. Total time: 0.050s
now:
C:\Fastboot>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.07.1540.2
INFOversion-misc: PVT SHIP S-OFF
INFOserialno
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_u
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: BS_US001
INFObattery-status: good
INFObattery-voltage: 4271mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.074s
this all right?
now can receive future OTA updates?

Steel-Cleiton said:
hello my good friend
I learned what you taught me
was complicated by I do not have a good English
more I got it, thanks for your patience
look:
before:
C: \ Fastboot> fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microprocessor: None
INFOversion-main: 6.15.599.101
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
Infoproduct: m7_u
INFOplatform: HBOOT-8064
INFOmodelid: PN0711000
INFOcidnum: HTC__332
INFObattery-status: good
INFObattery-voltage: 3858mV
INFOpartition-layout: Generic
Infosecurity: on
INFObuild-mode: SHIP
INFOboot-mode: fastboot
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. Total time: 0.050s
now:
C:\Fastboot>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.07.1540.2
INFOversion-misc: PVT SHIP S-OFF
INFOserialno
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_u
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: BS_US001
INFObattery-status: good
INFObattery-voltage: 4271mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.074s
this all right?
now can receive future OTA updates?
Click to expand...
Click to collapse
Yes its all good, glad it worked :good:

alray said:
Yes its all good, glad it worked :good:
Click to expand...
Click to collapse
I know not how to thank you
I admire your dedication and patience
I will continue to follow this forum
I have a lot to learn here
thanks again Alray

alray said:
Yes its all good, glad it worked :good:
Click to expand...
Click to collapse
I have just received OTA lollipop
thank you again
so I pay my credit card, I will make a donation to you friend

I need some help, my phone has the same software number.
I tried to change the MID using this post as reference: http://forum.xda-developers.com/showthread.php?t=2322820
I get the gray screen, but when I try to run the RUU software I'm having error 170, phone is not connected.
The software just ask me to press finish to close the program, and don't install the rom.
How to solve this error 170?