Bootloop/ errors with GPE still on jellybean - One (M7) Q&A, Help & Troubleshooting

Back in the day, my HTC One M7 GPE was one of the ones that became a soft brick with the initial update. So after Google replaced my phone, I turned off updates, and thereby wound up remaining on jellybean (4.2.2).
All was well and good until last week, when my phone wound up on a bootloop. Originally I could stop it from bootlooping by clearing the cache of certain apps like Gmail. But it would go back into a bootloop after some use like checking email or a webpage. I tried to download/ update the system, but my system was saying it didn't have enough memory. I started mass uninstalling things I don't use, in hopes that this wound work, but no luck.
So, I contacted Google who had me go into the bootloader and recovery. That gave me an android lying on his back with the red triangle/ exclamation point. From there he had me clear the cache.
After that, my phone would go into a bootloop no matter what!!
Out of desperation, I saved whatever I could on my computer, and then factory reset.
However, still with the factory reset I am getting bootloops!!
I was able to re-turn on usb debugging, and I have the file (now) to unlock my bootloader.
However, before I go ahead and do so, I am hoping there is a way to re-load on the OEM ROM and replace whatever has gone bad.... and hope the phone can then do its natural updates??
I've downloaded the 2.14.1700.15 files from the HTCdev website, and I tried to flash the zip files, but I get the "12 signature verify fail" error.
I have confirmed that my cid is still GOOGL001 . I thought that as long as it was a matching ROM that it would flash without unlocking the bootloader?
There are also Framework support files on the HTCdev website - I may need to replace/ flash those also??
If anyone has ideas before I go ahead and unlock the bootloader, that would be great!!
And if i do unlock the bootloader, given that I have never performed an update on the system, what version of the software (file) would you recommend that I flash the system with? I have no need for a custom ROM. The GPE ROMs are fine for me.
Thank you so much for your help!!

elisaw99 said:
Back in the day, my HTC One M7 GPE was one of the ones that became a soft brick with the initial update. So after Google replaced my phone, I turned off updates, and thereby wound up remaining on jellybean (4.2.2).
All was well and good until last week, when my phone wound up on a bootloop. Originally I could stop it from bootlooping by clearing the cache of certain apps like Gmail. But it would go back into a bootloop after some use like checking email or a webpage. I tried to download/ update the system, but my system was saying it didn't have enough memory. I started mass uninstalling things I don't use, in hopes that this wound work, but no luck.
So, I contacted Google who had me go into the bootloader and recovery. That gave me an android lying on his back with the red triangle/ exclamation point. From there he had me clear the cache.
After that, my phone would go into a bootloop no matter what!!
Out of desperation, I saved whatever I could on my computer, and then factory reset.
However, still with the factory reset I am getting bootloops!!
I was able to re-turn on usb debugging, and I have the file (now) to unlock my bootloader.
However, before I go ahead and do so, I am hoping there is a way to re-load on the OEM ROM and replace whatever has gone bad.... and hope the phone can then do its natural updates??
I've downloaded the 2.14.1700.15 files from the HTCdev website, and I tried to flash the zip files, but I get the "12 signature verify fail" error.
I have confirmed that my cid is still GOOGL001 . I thought that as long as it was a matching ROM that it would flash without unlocking the bootloader?
There are also Framework support files on the HTCdev website - I may need to replace/ flash those also??
If anyone has ideas before I go ahead and unlock the bootloader, that would be great!!
And if i do unlock the bootloader, given that I have never performed an update on the system, what version of the software (file) would you recommend that I flash the system with? I have no need for a custom ROM. The GPE ROMs are fine for me.
Thank you so much for your help!!
Click to expand...
Click to collapse
Wrong section thread, should be here http://forum.xda-developers.com/htc-one/help

Droid_Core said:
Wrong section thread, should be here http://forum.xda-developers.com/htc-one/help
Click to expand...
Click to collapse
Oooops, sorry.
Now that the thread has been moved - can anyone assist me with this??

elisaw99 said:
Oooops, sorry.
Now that the thread has been moved - can anyone assist me with this??
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei/sn)

alray said:
Post the output of "fastboot getvar all" (remove your imei/sn)
Click to expand...
Click to collapse
ok, here it is!
C:\Users\Owner\sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.521s

elisaw99 said:
ok, here it is!
C:\Users\Owner\sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.521s
Click to expand...
Click to collapse
You could flash the 5.11.1700.3 GPE RUU and update to the latest version from there using ota
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
File and instructions at post 1 of this thread. Don't forget that flashing a RUU will wipe the phone so backup your important files before.

Thanks for the reply!
Do I have to unlock the bootloader to flash this RUU?
Also it looks like on the webpage that it is a Lollipop Sense RUU? Is that right? I was hoping to stay with the GPE ROMs. And i was guessing that I needed to load on the jellybean original first prior to updating to Lollipop.... but maybe that isn't necessary??
Thanks for all of your assistance!!

elisaw99 said:
Thanks for the reply!
Do I have to unlock the bootloader to flash this RUU?
Also it looks like on the webpage that it is a Lollipop Sense RUU? Is that right? I was hoping to stay with the GPE ROMs. And i was guessing that I needed to load on the jellybean original first prior to updating to Lollipop.... but maybe that isn't necessary??
Thanks for all of your assistance!!
Click to expand...
Click to collapse
The bootloader must be locked to flash the ruu since your phone is S-ON.
.1700 is the GPE version not Sense

alray said:
The bootloader must be locked to flash the ruu since your phone is S-ON.
.1700 is the GPE version not Sense
Click to expand...
Click to collapse
Ok, sounds good! And this is Lollipop I presume?
Unfortunately, it looks like the link to download is broken? Says file does not exist. Is there another download link I can use?
Thanks a lot!

elisaw99 said:
Ok, sounds good! And this is Lollipop I presume?
Unfortunately, it looks like the link to download is broken? Says file does not exist. Is there another download link I can use?
Thanks a lot!
Click to expand...
Click to collapse
5.0.1 GPE RUU:
http://www.graffixnyc.com/download.php
4.4 GPE RUU:
http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/

alray said:
5.0.1 GPE RUU:
http://www.graffixnyc.com/download.php
4.4 GPE RUU:
http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
Click to expand...
Click to collapse
Thanks for the new links!
Do I need to flash the 4.4 first? And then will my phone automatically OTA update?
Or do I need to flash the original 4.2.2 first?
Or does none of it matter, and I can flash the latest version right away??

elisaw99 said:
Thanks for the new links!
Do I need to flash the 4.4 first? And then will my phone automatically OTA update?
Or do I need to flash the original 4.2.2 first?
Or does none of it matter, and I can flash the latest version right away??
Click to expand...
Click to collapse
Actually neither of those links are working either.
If someone could let me know the best options, it would be appreciated!

I'm wondering if the files you are sending are the same as that on the HTCdev website:
http://www.htcdev.com/devcenter/downloads ?
By going into the One Google Play Edition, a bunch of ROMs and Frameworks come up. I'm currently on 2.14.1700.15 . I originally tried to flash that UI, but that's when i got the signature errors.
Do I need to flash the Frameworks first? And, if so, what is the line code to do that?
Or is the reason it failed is because I used the android fastboot, instead of HTC fastboot??

elisaw99 said:
Actually neither of those links are working either.
If someone could let me know the best options, it would be appreciated!
Click to expand...
Click to collapse
The link for 4.4 is still good. Flash this one then install ota updates.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
elisaw99 said:
I'm wondering if the files you are sending are the same as that on the HTCdev website:
http://www.htcdev.com/devcenter/downloads ?
Click to expand...
Click to collapse
No these are kernel source files, not useful for you, flash the ruu and you should be fine.

Ok, unfortunately it did not work.
Can any one detect what I may be doing wrong?
I tried 3 times to get the flash of the file to work, but no luck. The RUU file I tried to flash was "RUU Zip M7_Google Edition_4.4_3.58.1700.5.zip"
C:\Users\Owner\sdk>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 53(ms)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.749 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 72(s)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.767 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 71(s)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.576 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 72(s)
C:\Users\Owner\sdk>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 42(ms)

elisaw99 said:
Ok, unfortunately it did not work.
Can any one detect what I may be doing wrong?
I tried 3 times to get the flash of the file to work, but no luck. The RUU file I tried to flash was "RUU Zip M7_Google Edition_4.4_3.58.1700.5.zip"
C:\Users\Owner\sdk>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 53(ms)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.749 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 72(s)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.767 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 71(s)
C:\Users\Owner\sdk>htc_fastboot flash zip RUU.zip
sending 'zip'... (506183 KB) OKAY
sending time = 21.576 secs
writing 'zip'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 72(s)
C:\Users\Owner\sdk>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 42(ms)
Click to expand...
Click to collapse
12 signature verify fail = Your bootloader is unlocked. It must be locked or re-locked (fastboot oem lock) to flash a RUU.

no, my bootloader is locked. i never unlocked it.
i also tried both the htc fastboot, and regular fastboot. both have the signature fail error.

elisaw99 said:
no, my bootloader is locked. i never unlocked it.
i also tried both the htc fastboot, and regular fastboot. both have the signature fail error.
Click to expand...
Click to collapse
Ok then it might be caused by the RUU not being signed with HTC's signature. Unsigned RUU can only be flashed on S-OFF phone. So you'll need either to find a signed RUU or S-OFF your phone and use that one.

Before I unlock my bootloader and attempt to install something else, could someone let me know if they have an RUU.zip that would work with my phone?!? I have tried just about anything that looked like an RUU.zip that I could find for GPE, and all give me the signature fail. I'm getting horribly frustrated and want a phone again!!
PLEASE HELP!!

Related

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

[Q] Stuck at RUU Bootloader

I believe I have bricked my device. I'm s-off on the latest firmware and radios and was running the latest insertcoin sense 7 rom when I tried to run the LP RUU to get it back to stock and it failed. Keeps giving me error code 152, which means it thinks something is wrong with the image. It has left me stuck on the RUU bootloader screen with no means of getting back to the main bootloader. I still have fastboot commands, but cannot manually flash the newest firmware or rom.zip from this thread. The RUU I have is also from this thread. I have tried it several times, tried relocking the bootloader even though I am s-off, still didnt work, and I am completely stuck on the bootloader. Now it seems that I can't flash anything because I've relocked the bootloader? I've tried fresh downloads of everything, and also have the HTC drivers installed with HTC sync uninstalled. Does anyone have any suggestions or ideas? I have been working on phones for years and never had a problem running an RUU until today. Any help is greatly appreciated, and I'll buy you a beer if you can fix it
Please ask questions if I'm not clear enough, I can clarify if needed.
Here are a few of the outputs I'm getting:
C:\adb>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 116912852 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 116912852 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 116912852 is not a multiple of t
he block size 4096
OKAY [ 64.235s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 64.450s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4215mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
Have you tried running it as .exe?
BD619 said:
Have you tried running it as .exe?
Click to expand...
Click to collapse
Yes, that's what caused all of this to begin with. The .exe RUU failed with Error 152. I've tried the previous KK RUU as well, to no avail.
Edit: The failure is with the partition update. everything passes, and then the partition fails and it hangs after it tries to update system.
goliath714 said:
Yes, that's what caused all of this to begin with. The .exe RUU failed with Error 152. I've tried the previous KK RUU as well, to no avail.
Click to expand...
Click to collapse
When you run the exe from you PC when it fails does it give you a Recover option in the RUU screen?
BD619 said:
When you run the exe from you PC when it fails does it give you a Recover option in the RUU screen?
Click to expand...
Click to collapse
Yes, and I've followed all those steps as well. It does the same thing each time; says it has recovered successfully, I go to continue the RUU process, and it fails again and gives me the chance to recover, and this repeats no matter how many times I try.
goliath714 said:
Yes, and I've followed all those steps as well. It does the same thing each time; says it has recovered successfully, I go to continue the RUU process, and it fails again and gives me the chance to recover, and this repeats no matter how many times I try.
Click to expand...
Click to collapse
After you recover don't restart the RUU.
Try from the beginning from a different USB port USB2 work best.
BD619 said:
After you recover don't restart the RUU.
Try from the beginning from a different USB port USB2 work best.
Click to expand...
Click to collapse
Tried that as well. Tried both USB 2 and 3, running as administrator and normally, same Error 152 each time. Tried recovering and not recovering as well. My PC is running Windows 7 Pro.
Could the fact that I relocked it have anything to do with it?
goliath714 said:
Tried that as well. Tried both USB 2 and 3, running as administrator and normally, same Error 152 each time. Tried recovering and not recovering as well. My PC is running Windows 7 Pro.
Could the fact that I relocked it have anything to do with it?
Click to expand...
Click to collapse
Being re-locked shouldn't matter since you are s-off.
My only other suggestions are...
Different cable
Different PC.
BD619 said:
Being re-locked shouldn't matter since you are s-off.
My only other suggestions are...
Different cable
Different PC.
Click to expand...
Click to collapse
BD could it be because he's relocked and doesn't have a eng . bootloader be the problem, just throwing this out there.
Aldo101t said:
BD could it be because he's relocked and doesn't have a eng . bootloader be the problem, just throwing this out there.
Click to expand...
Click to collapse
I don't think so...I had him try everything I can think of and he's still having problems.
BD619 said:
I don't think so...I had him try everything I can think of and he's still having problems.
Click to expand...
Click to collapse
yeah, it's weird that's for sure. well thought maybe I could help, thanks
BD619 said:
I don't think so...I had him try everything I can think of and he's still having problems.
Click to expand...
Click to collapse
I took it to the Sprint store and they couldn't even flash the image. Not that it's any different than the one I was using, but they replaced it for free since I've had it less than a year. Chalk one up for the home team!
Sent from my One M7 using XDA Free mobile app

[Q] (Q) Lollipop soft brick help please

Hi all,
My friend handed me his HTC One M7 the other day and it was looping at the beginning Android / HTC screen from boot, he took the lollipop update but it failed somewhere along the way and this is how it's ended up.
The device is not rooted and is not bootloader unlocked, i've tried to flash a few RUU files to bring it back to life but the vast majority of them only get as far as 1/5 checking header.
I'm more than happy to root the device and install a custom rom but I wasn't sure if it needed to be bootable to do so, afaik the bootloader unlocking doesn't require to have the device on, infact I don't think you need to have the OS to get a custom recovery either? Anyway, i'd like for him to retain his warranty so if there's a way for him to get it back to stock HTC then i'd prefer to do that.
If that's not possible and unlocking the bootloader, installing a custom rom is then I'll do that.
Any help would be greatly appreciated.
Many thanks.
PS: I have had the m7 before but I didn't have it when android 5 was available so i'm a little out of touch with what may go wrong.
dladz said:
Hi all,
My friend handed me his HTC One M7 the other day and it was looping at the beginning Android / HTC screen from boot, he took the lollipop update but it failed somewhere along the way and this is how it's ended up.
The device is not rooted and is not bootloader unlocked, i've tried to flash a few RUU files to bring it back to life but the vast majority of them only get as far as 1/5 checking header.
I'm more than happy to root the device and install a custom rom but I wasn't sure if it needed to be bootable to do so, afaik the bootloader unlocking doesn't require to have the device on, infact I don't think you need to have the OS to get a custom recovery either? Anyway, i'd like for him to retain his warranty so if there's a way for him to get it back to stock HTC then i'd prefer to do that.
If that's not possible and unlocking the bootloader, installing a custom rom is then I'll do that.
Any help would be greatly appreciated.
Many thanks.
PS: I have had the m7 before but I didn't have it when android 5 was available so i'm a little out of touch with what may go wrong.
Click to expand...
Click to collapse
Connect the phone to your computer, Boot it in bootloader mode select "fastboot" mode and make sure "fastboot usb" is shown in red. Open a fastboot command prompt:
Code:
fastboot getvar all
post the output here but make sure to hide the imei and serialno before posting.
Thanks mate I'm in bed at the moment but will do after work tomorrow,, Appreciate your help, im guessing this is to see what firmware is installed? Or hboot? I'll come back tomorrow, Many thanks.
dladz said:
Thanks mate I'm in bed at the moment but will do after work tomorrow,, Appreciate your help, im guessing this is to see what firmware is installed? Or hboot? I'll come back tomorrow, Many thanks.
Click to expand...
Click to collapse
Firmware, hboot, CID, MID, S-ON/S-OFF, M7_UL/M7_U
Checking header 1/5..ill give you a clue...your ruu that you going to flash,it has to match firmware that is on it now...as you are s-on,you cant change firmware.so,try with other ruu's,some that maches firmware number..not older,not newer.
And like others said,give them "getvar all" info.
Sent from my HTC One using XDA Free mobile app
Chaps you are both legends, I'm just running round getting ready for work. I'll jump on this when I get home. Appreciate your help. Thanks.
alray said:
Connect the phone to your computer, Boot it in bootloader mode select "fastboot" mode and make sure "fastboot usb" is shown in red. Open a fastboot command prompt:
Code:
fastboot getvar all
post the output here but make sure to hide the imei and serialno before posting.
Click to expand...
Click to collapse
C:\ANDROID SDK\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W909506
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3596mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Here you go mate.
currently downloading this https://www.androidfilehost.com/?fid=95832962473396760 it's for version 6.09.401.11 which was listed.
Unless there's something i'm supposed to do.
dladz said:
C:\ANDROID SDK\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W909506
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3596mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Here you go mate.
currently downloading this https://www.androidfilehost.com/?fid=95832962473396760 it's for version 6.09.401.11 which was listed.
Unless there's something i'm supposed to do.
Click to expand...
Click to collapse
Would recommend to simply flash the latest ruu (7.19.401.2) which will fix and update the phone to the latest version.
Instructions and file here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
alray said:
Would recommend to simply flash the latest ruu (7.19.401.2) which will fix and update the phone to the latest version.
Instructions and file here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
I did actually try that one mate, that's how i got the 1/5 checking headers problem, and it simply doesn't go any further, i'll give it another whirl but as far as i can remember it was that version.
brb after checking.
Actually I didn't flash one of these but the version does ring a bell. Downloading now mate.
The previous one i mentioned i flash via fastboot flash zip but it still loops, 20 mins until that one downloads. Will let you know and thank you by the way.
dladz said:
I did actually try that one mate, that's how i got the 1/5 checking headers problem, and it simply doesn't go any further, i'll give it another whirl but as far as i can remember it was that version.
brb after checking.
Actually I didn't flash one of these but the version does ring a bell. Downloading now mate.
Click to expand...
Click to collapse
Im almost sure you were trying to flash the 4.xx.401.x version not the one I have linked above.
alray said:
Im almost sure you were trying to flash the 4.xx.401.x version not the one I have linked above.
Click to expand...
Click to collapse
I flashed this one https://www.androidfilehost.com/?fid=95832962473396760 which is 6.09.401.11 but it didn't work, not to worry anyway, i'll give the one you linked to a whirl too, just waiting for it to download, 10 mins left.
dladz said:
i'll give the one you linked to a whirl too, just waiting for it to download, 10 mins left.
Click to expand...
Click to collapse
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
alray said:
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
Oh really? Why didn't i know this !? See I've been gone from HTC for far too long, should be getting the M9 soon though. One of my contracts expires soon, i've got a few, need to check on them. You thinking of getting the M9 ? Think Samsung has made a mistake going with the Exynos.
Ok it's downloaded, i'll grab that fastboot and give it a whirl. Fingers crossed.
alray said:
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
Ok i got this
C:\HTC Fastboot>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 44(ms)
C:\HTC Fastboot>fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.4
01.102_Radio_4T.35.3218.16_10.33Q.1718.01D_release_421804_signed.zip
sending 'zip'... (43287 KB) OKAY
sending time = 2.844 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 9(s)
C:\HTC Fastboot>
Rebooting.
EDIT: Bootloop mate.
dladz said:
Oh really? Why didn't i know this !? See I've been gone from HTC for far too long, should be getting the M9 soon though. One of my contracts expires soon, i've got a few, need to check on them. You thinking of getting the M9 ? Think Samsung has made a mistake going with the Exynos.
Click to expand...
Click to collapse
I'll might grab the M9 later this year when the price will drop a bit. I'm still satisfied with my M7 and doesn't feel like I need something more.
Ok it's downloaded, i'll grab that fastboot and give it a whirl. Fingers crossed
Click to expand...
Click to collapse
Dont forget you'll need the dll files in the same folder where you have htc's fastboot and the ruu. You can simply replace fastboot.exe with htc's fastboot in your sdk folder were the required dll files are
---------- Post added at 12:16 PM ---------- Previous post was at 12:14 PM ----------
dladz said:
Ok i got this
C:\HTC Fastboot>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 44(ms)
C:\HTC Fastboot>fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.4
01.102_Radio_4T.35.3218.16_10.33Q.1718.01D_release_421804_signed.zip
sending 'zip'... (43287 KB) OKAY
sending time = 2.844 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 9(s)
C:\HTC Fastboot>
Click to expand...
Click to collapse
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
alray said:
Would recommend to simply flash the latest ruu (7.19.401.2)
Click to expand...
Click to collapse
alray said:
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
Click to expand...
Click to collapse
Just copied the HTC fastboot into the SDK platforms and tools folder, reflashing now.
dladz said:
Just copied the HTC fastboot into the SDK platforms and tools folder, reflashing now.
Click to expand...
Click to collapse
read my post above you are flashing the wrong ruu. You need 4.19.401.2 not 4.19.401.102
alray said:
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
Click to expand...
Click to collapse
Ah, idiot. Sorry
Couldn't see a european one though? This device is unlocked, wouldn't it have the providers software on otherwise?
Ok downloading, sorry mate, my eyes are failing me, getting old.
Ok so I think it's all done mate, looks like it's going to load up, I mean the script has finished running but the green bar is still onscreen.

HTC One M7 e801 bootup blankscreen

First of all, I got my m7 unlocked and stuffs. Then my supersu keep on appearing error for stop responding
Therefore I realize maybe my supersu was too old or something based on the tutorial, the zip was older version. I flashed with update-supersu.zip , thats where my nightmare begin.
I reboot after flashing it, HTC logo bootup appear then went on blankscreen. I tried to wiped data and factory reset still the same
Next I was trying to flash full firmware thought it should bring back my m7 to life, not successful, and tried different rom(Google stock rom), it all shows
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: not allowed)
Click to expand...
Click to collapse
I don't know what to do anymore, what did i miss to flash any rom or simply have my m7 works again, please help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader)
(bootloader)
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4102mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bf7e9305
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
first of all, i figure out a few things here, maybe someone could help with my informations
If was planning to make it S-OFF but with Hboot 1.61 i will need to pay $25 for sunshine, X.
So the only way is that I flash stock M7_U 7.18.709.102 (HTC_Asia_TW), im not sure whats the correct way to do that. Or flash something ruu? I have no idea about that
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
what am I suppose to do? while the meantime im downloading the zip and its freaking slow, take very long (if someone got a better download website) due to the mirror
my recovery mode, fastboot and bootloader are functioning which is something im still happy for.
Please if someone could help me out
fungrian said:
first of all, i figure out a few things here, maybe someone could help with my informations
If was planning to make it S-OFF but with Hboot 1.61 i will need to pay $25 for sunshine, X.
So the only way is that I flash stock M7_U 7.18.709.102 (HTC_Asia_TW), im not sure whats the correct way to do that. Or flash something ruu? I have no idea about that
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
what am I suppose to do? while the meantime im downloading the zip and its freaking slow, take very long (if someone got a better download website) due to the mirror
my recovery mode, fastboot and bootloader are functioning which is something im still happy for.
Please if someone could help me out
Click to expand...
Click to collapse
Sometimes downloading things requires patience.
Im not sure exactly how S-ON flashing works but i did hear somewhere that something to do with boot image gets involved
I found out the best way to bring back my m7 is to use RUU method, but when i try to flash zip it shows "failed"
./fastboot-mac flash zip PN07IMG.zip
sending 'zip' (1975775 KB)...
FAILED (remote: 02 data length is too large)
Click to expand...
Click to collapse
FAILED (remote: 02 data length is too large)
maybe the RUU is not right for my phone?
Don't know whether is it i downloaded wrong rom file for my device
fungrian said:
I found out the best way to bring back my m7 is to use RUU method, but when i try to flash zip it shows "failed"
FAILED (remote: 02 data length is too large)
maybe the RUU is not right for my phone?
Don't know whether is it i downloaded wrong rom file for my device
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a RUU if it's a Lollipop version (version starting with 7.xx.xxx.x). Others fastboot versions won't work.
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
fungrian said:
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
Click to expand...
Click to collapse
Does not apply to the M7, the boot partition isn't write protected like previous htc devices.

Categories

Resources