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
Related
Hey all,
I'm looking to get my phone up to date. I bought my AT&T M7 a month or two after it came out and I've never upgraded the firmware or anything besides the ROM since I bought it (2yr contract is up next week, if that helps with a timeframe). I'm looking to find the latest firmware.
Should I look for the absolute latest one, or does it depend on my ROM? I'm looking to try the Android Revolution HD ROMs and didn't see anything about a specific firmware, just that it's not a bad idea to update it.
Would there be repercussions of updating? I'm currently on an unlocked bootloader and S-ON, and I might as well leave it S-ON while I'm flashing firmware to prevent bricking (from what I read, it should work as long as everything matches, and I don't see how it could be a good idea to go S-OFF to "get around" that and risk bricking).
I could use help finding the latest firmware version, since I don't really know what to look for.
Output of "fastboot getvar all":
Code:
# fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: [omitted]
(bootloader) imei: [omitted]
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) security: on
(bootloader) build-mode: SHIP
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 170.344s
No, I'm not sure what keeps failing. The output changes everytime I run the command (different fields are shown each time, the numbers are consistent for the repeated ones). Sometimes it outputs nothing and says completed, and others it outputs some stuff like above and fails. If you know what this is indicative of, that'd be nice to know as well. Note that I'm on Debian Linux and not Windows, so I suspect my version of fastboot from the repos might not be the latest one or something like that. (I do have Win 7 and 8.1 64-bit VMs at my disposal though, so Windows only solutions should work fine too, no worries)
Thanks for any and all of your time!
jtaylor991
jtaylor991 said:
Hey all,
I'm looking to get my phone up to date. I bought my AT&T M7 a month or two after it came out and I've never upgraded the firmware or anything besides the ROM since I bought it (2yr contract is up next week, if that helps with a timeframe). I'm looking to find the latest firmware.
Should I look for the absolute latest one, or does it depend on my ROM? I'm looking to try the Android Revolution HD ROMs and didn't see anything about a specific firmware, just that it's not a bad idea to update it.
Would there be repercussions of updating? I'm currently on an unlocked bootloader and S-ON, and I might as well leave it S-ON while I'm flashing firmware to prevent bricking (from what I read, it should work as long as everything matches, and I don't see how it could be a good idea to go S-OFF to "get around" that and risk bricking).
I could use help finding the latest firmware version, since I don't really know what to look for.
Output of "fastboot getvar all":
Code:
# fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: [omitted]
(bootloader) imei: [omitted]
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) security: on
(bootloader) build-mode: SHIP
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 170.344s
No, I'm not sure what keeps failing. The output changes everytime I run the command (different fields are shown each time, the numbers are consistent for the repeated ones). Sometimes it outputs nothing and says completed, and others it outputs some stuff like above and fails. If you know what this is indicative of, that'd be nice to know as well. Note that I'm on Debian Linux and not Windows, so I suspect my version of fastboot from the repos might not be the latest one or something like that. (I do have Win 7 and 8.1 64-bit VMs at my disposal though, so Windows only solutions should work fine too, no worries)
Thanks for any and all of your time!
jtaylor991
Click to expand...
Click to collapse
If your s-on and unlocked bootloader your first step should be to achieve s-off, on hboot 1.44 you can use Revone or Rummruner. all you need is custom recovery TWRP 2.6.3.3 / Root / and a rom with insecure kernel. ARHD 31.6 should work.
After your s-off you can flash this RUU.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot flash zip RUU.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
followed by this 4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
and then this RUU.zip>> http://www.androidfilehost.com/?fid=23329332407580500
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot flash zip RUU.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
after that 1 OTA update and your on the most current version
5.12.502.2
clsA said:
and then this RUU.zip>> http://www.androidfilehost.com/?fid=23329332407580500
5.12.502.2
Click to expand...
Click to collapse
I got S-OFF and everything else has been fine up to this second RUU zip. Here's what happens:
Code:
# fastboot flash zip RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
fastboot: /tmp/buildd/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Aborted
I tried redownloading to no avail. Help?
Can I just OTA update from here since it boots (i.e. was the second RUU just to save time)? I'll wait until you say it's safe, since I'm worried that it'd mess up something somehow (as in accidentally re-lock or S-ON, etc).
I went ahead and just did the OTA update and skipped the last RUU zip and it all worked out fine. Thanks a million!
Sent from my HTC One using XDA Free mobile app
jtaylor991 said:
I went ahead and just did the OTA update and skipped the last RUU zip and it all worked out fine. Thanks a million!
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Great glad you got it all sorted out
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.
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!!
Hi,
I have a One M7 which has Vodafone branding, but is not network locked and has HBOOT 1.61 and S-ON. I wanted to convert it to Google Play Edition, so I did the following:
Unlocked the bootloader using instructions at HTCdev
Installed recovery using Hasoon2000's HTC One All-In-One Toolkit
When restarting recovery, it asked me if I wanted to root, I chose to root
Tested root with app on Play Store, found that it hadn't been rooted successfully
Installed SunShine to achieve S-off, temproot was unsuccessful; couldn't S-off
Booted into recovery, and for whatever reason, chose to "fix permissions"
On next reboot, I found that Play Store was missing
Performed a factory reset from recovery, rebooted
Android proceeded to do it's "updating apps" thing, but stopped halfway through and gave me the error "Unfortunately Setup Wizard Has Stopped Working". Now the error continuously pops up and I can't access anything in the OS. I also can't seem to get ADB to recognise my device any more. It either says "error: device not found", or "List of devices attached" and follows up with two blank lines.
I'm stuck as to what to do with this now. The only thing that works is fastboot:
fastboot getvar all
(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: 7.18.161.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
Click to expand...
Click to collapse
cds80 said:
Hi,
I have a One M7 which has Vodafone branding, but is not network locked and has HBOOT 1.61 and S-ON. I wanted to convert it to Google Play Edition, so I did the following:
Unlocked the bootloader using instructions at HTCdev
Installed recovery using Hasoon2000's HTC One All-In-One Toolkit
When restarting recovery, it asked me if I wanted to root, I chose to root
Tested root with app on Play Store, found that it hadn't been rooted successfully
Installed SunShine to achieve S-off, temproot was unsuccessful; couldn't S-off
Booted into recovery, and for whatever reason, chose to "fix permissions"
On next reboot, I found that Play Store was missing
Performed a factory reset from recovery, rebooted
Android proceeded to do it's "updating apps" thing, but stopped halfway through and gave me the error "Unfortunately Setup Wizard Has Stopped Working". Now the error continuously pops up and I can't access anything in the OS. I also can't seem to get ADB to recognise my device any more. It either says "error: device not found", or "List of devices attached" and follows up with two blank lines.
I'm stuck as to what to do with this now. The only thing that works is fastboot:
Click to expand...
Click to collapse
Your post is the perfect example why I say to everyone:, don't use any toolkit, learn the basic adb/fastboot commands!
Toolkits can be nice for some time but when they are not supported anymore, they will flash an outdated version of TWRP and so outdated supersu binaries which will cause issues.
Now you can flash a custom rom using twrp, or flash your stock RUU using fastboot, root your phone using the latest supersu version and s-off with sunshine.
alray said:
Your post is the perfect example why I say to everyone:, don't use any toolkit, learn the basic adb/fastboot commands!
Toolkits can be nice for some time but when they are not supported anymore, they will flash an outdated version of TWRP and so outdated supersu binaries which will cause issues.
Now you can flash a custom rom using twrp, or flash your stock RUU using fastboot, root your phone using the latest supersu version and s-off with sunshine.
Click to expand...
Click to collapse
Thanks for the reply. So I can use fastboot to flash roms without having to copy them to the phone first? For some reason I thought it was only for flashing recoveries.
cds80 said:
Thanks for the reply. So I can use fastboot to flash roms without having to copy them to the phone first? For some reason I thought it was only for flashing recoveries.
Click to expand...
Click to collapse
You can use fastboot to flash RUU (stock rom). Other roms are flashed from recovery.
Sent from my HTC One using XDA Labs
Thanks for your help. I've downloaded the second-gen 7.18.161.21 RUU for vodafone from the collection in your sig. The MD5 is reported as da17b2877fbe45da5598d2d02d89d4eb which matches my download, but I am concerned that I cannot read the .zip properly with 7zip or WinRAR to inspect the .txt file. 7zip won't open it at all, and WinRAR displays the contents but reports corruption when I try to extract.
Should I proceed to flash it?
cds80 said:
Thanks for your help. I've downloaded the second-gen 7.18.161.21 RUU for vodafone from the collection in your sig. The MD5 is reported as da17b2877fbe45da5598d2d02d89d4eb which matches my download, but I am concerned that I cannot read the .zip properly with 7zip or WinRAR to inspect the .txt file. 7zip won't open it at all, and WinRAR displays the contents but reports corruption when I try to extract.
Should I proceed to flash it?
Click to expand...
Click to collapse
Okay, having just seen your comment on "corrupted" archives actually being encrypted, I feel a little foolish. I was following another one of posts that mentioned checking the version numbers from a text file inside the archive to ensure they match.
Well, I tried flashing the RUU mentioned earlier, here's what I got:
C:\adb>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.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 340906976 is not a multiple of the block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 340906976 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 340906976 is not a multiple of the block size 4096
OKAY [ 61.452s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 61.630s
Click to expand...
Click to collapse
cds80 said:
Well, I tried flashing the RUU mentioned earlier, here's what I got:
Click to expand...
Click to collapse
If you want to flash the .21 ruu on your .51 version, you'll need too downgrade you version-main first. You'll also need to use htc_fastboot.exe not the regular fastboot.exe to flash the RUU.
Sent from my HTC One using XDA Labs
alray said:
If you want to flash the .21 ruu on your .51 version, you'll need too downgrade you version-main first. You'll also need to use htc_fastboot.exe not the regular fastboot.exe to flash the RUU.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Thanks. So, it seems that I have two options: follow the instructions for flashing an older RUU, or change my CID to flash a current RUU that belongs to a different carrier (I cannot find a Vodafone RUU that matches my version). Is that correct?
Never mind, I managed to flash an older RUU following the instructions in your collection link. It's now booting properly again, and everything seems fine! Thanks for the help
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.