cannot return to stock on M7 - One (M7) Q&A, Help & Troubleshooting

I have been having trouble with data connectivity and I wanted trying returning to stock but have had issues.
First off I was on a 6.* firmware and S-ON so I decided to S-OFF, update the firstware to 6.09.401.5 and got super CID
So then I tried the RUU update (or backdate in my case) to 1.26.502.12 via htc1guru.com (EXE) method and the process failed. Keep in my I change the CID back CWS__001 before
Is this because the firmware is so different or something else?
Is there a RUU available for the 6.09.401.5 firmware / android 4.4.3 I was not able to find one.
I am stuck now, the data is worse that it was before and I just want to get back to stock at this point.

maxpower2078 said:
I have been having trouble with data connectivity and I wanted trying returning to stock but have had issues.
First off I was on a 6.* firmware and S-ON so I decided to S-OFF, update the firstware to 6.09.401.5 and got super CID
So then I tried the RUU update (or backdate in my case) to 1.26.502.12 via htc1guru.com (EXE) method and the process failed. Keep in my I change the CID back CWS__001 before
Is this because the firmware is so different or something else?
Is there a RUU available for the 6.09.401.5 firmware / android 4.4.3 I was not able to find one.
I am stuck now, the data is worse that it was before and I just want to get back to stock at this point.
Click to expand...
Click to collapse
Is your phone AT&T = CWS__001 ? or is it international = 6.9.401.5 ?
If you on 6.x why in the world would you go all the back to 1.x ? that's 2 years old ?

clsA said:
Is your phone AT&T = CWS__001 ? or is it international = 6.9.401.5 ?
If you on 6.x why in the world would you go all the back to 1.x ? that's 2 years old ?
Click to expand...
Click to collapse
I'm just trying to find the combo that works at this point.
I flashed 4.18.502.7 in hopes to flash that RUU as I am getting the following right now
D:\android\dev\platform-tools>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 38723880 is not a multiple of the block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
OKAY [ 65.799s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 66.006s
this came from trying to install RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip linked to from your post actually
I would like the latest 4.4.3 RUU but can't find it.
I have set the CID to 11111111 for now but it was CWS__001 so yes, US AT&T
Is there a better way?

for good measure
Code:
D:\android\dev\platform-tools>fastboot getvar al
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3937mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.166s

maxpower2078 said:
I'm just trying to find the combo that works at this point.
I flashed 4.18.502.7 in hopes to flash that RUU as I am getting the following right now
D:\android\dev\platform-tools>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 38723880 is not a multiple of the block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 38723880 is not a multiple of the block size 4096
OKAY [ 65.799s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 66.006s
this came from trying to install RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_decrypted.ROM.zip linked to from your post actually
I would like the latest 4.4.3 RUU but can't find it.
I have set the CID to 11111111 for now but it was CWS__001 so yes, US AT&T
Is there a better way?
Click to expand...
Click to collapse
Your s-off so use the firmware and RUU combination and leave your CID at CWS__001
flash this first then the 4.x.502 RUU
https://www.androidfilehost.com/?fid=23329332407580581
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
after this you can take the OTA to 5.x.502
after it's done you can flash back to custom recovery if you want.

clsA said:
Your s-off so use the firmware and RUU combination and leave your CID at CWS__001
flash this first then the 4.x.502 RUU
https://www.androidfilehost.com/?fid=23329332407580581
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
after this you can take the OTA to 5.x.502
after it's done you can flash back to custom recovery if you want.
Click to expand...
Click to collapse
I do have firmware 4.18.502.7 on right now but am getting the message above. i found a thread that attributed it to the fastboot version and to use mfastboot but that appears to be for motorolas.
I am using the ruu linked here http://forum.xda-developers.com/showthread.php?t=2695749

do i need to have the same firmware one as the ruu has when flashing it?

maxpower2078 said:
do i need to have the same firmware one as the ruu has when flashing it?
Click to expand...
Click to collapse
yes flash the firmware then the RUU , regardless if your on it now or not
update your fastboot here > http://forum.xda-developers.com/showthread.php?t=2588979

clsA said:
yes flash the firmware then the RUU , regardless if your on it now or not
update your fastboot here > http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
thanks, got the EXE version of 4.18.502.7 to work. Now I'll see if there is an OTA from here, but I'm on Straightalk so I am not sure if I can receive AT&T OTAs

maxpower2078 said:
thanks, got the EXE version of 4.18.502.7 to work. Now I'll see if there is an OTA from here, but I'm on Straightalk so I am not sure if I can receive AT&T OTAs
Click to expand...
Click to collapse
Well if your back to stock with a working phone i guess your ok
If you want to continue on go here >> http://forum.xda-developers.com/showthread.php?t=2775650

clsA said:
Well if your back to stock with a working phone i guess your ok
If you want to continue on go here >> http://forum.xda-developers.com/showthread.php?t=2775650
Click to expand...
Click to collapse
Thanks, this has been a huge struggle and all brought on by sporadic non functioning data. Tested on this and it works great. I am doing the OTA update right now. I will put another recovery on it to backup the current image at minimum.

maxpower2078 said:
Thanks, this has been a huge struggle and all brought on by sporadic non functioning data. Tested on this and it works great. I am doing the OTA update right now. I will put another recovery on it to backup the current image at minimum.
Click to expand...
Click to collapse
and this is all my wifes phone, mine has the same problem and have to do it all over again, haha

maxpower2078 said:
Thanks, this has been a huge struggle and all brought on by sporadic non functioning data. Tested on this and it works great. I am doing the OTA update right now. I will put another recovery on it to backup the current image at minimum.
Click to expand...
Click to collapse
Good deal, TWRP 2.8.4.0 has been working well for me

Related

Converted TMobile USA to GPE. can't flash other RUU's

Hey guys,
I have a tmobile usa htc one that I converted to GPE. I did so through a GPE RUU zip file. I used the command fastboot flash zip "RUU zip file here".zip. My phone successfully converted and a dark bootloader replaced my white bootloader with the red warning sign.
Now the problem is when I try to flash another RUU zip... lets say Stock Tmobile HTC one, or Developers ROM RUU, I always got an error message. I know I can flash a sense based rom onto my phone, but I want the option to revert back to stock, Developers edtion.
How do I go on about this? someone help :crying:
I'd greatly appreciate it.
itsmarkiemark said:
Hey guys,
I have a tmobile usa htc one that I converted to GPE. I did so through a GPE RUU zip file. I used the command fastboot flash zip "RUU zip file here".zip. My phone successfully converted and a dark bootloader replaced my white bootloader with the red warning sign.
Now the problem is when I try to flash another RUU zip... lets say Stock Tmobile HTC one, or Developers ROM RUU, I always got an error message. I know I can flash a sense based rom onto my phone, but I want the option to revert back to stock, Developers edtion.
How do I go on about this? someone help :crying:
I'd greatly appreciate it.
Click to expand...
Click to collapse
maybe you should start by posting your ''fastboot getvar all'' minus imei/sn and give us a link to the ruu that failed to install. Also:
I always got an error message
Click to expand...
Click to collapse
doesnt say much. you should write down that exact error code you get.
alray said:
maybe you should start by posting your ''fastboot getvar all'' minus imei/sn and give us a link to the ruu that failed to install. Also:
doesnt say much. you should write down that exact error code you get.
Click to expand...
Click to collapse
I tried to flash this:
http://www.htc1guru.com/dld/ruu-zip...157-04_release_336982_signed_2_decrypted-zip/
& this
http://www.htc1guru.com/dld/ruu-zip...r_brightstarus_wwe_3-22-1540-1-decrypted-zip/
my get varinfo is
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Private dont mind this, I added this to block my serialno
(bootloader) imei: Private dont mind this, i added this to block my imei
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4206mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
and the error message when trying to flash RUUs is this:
C:\Users\mm\Desktop\Android\HTC ONE>fastboot flash zip RUU Zip M7_UL_JB_50_Brigh
tstarUS_WWE_1.29.1540.3.zip
target reported max download size of 1526722560 bytes
error: cannot load 'RUU': No error
itsmarkiemark said:
fastboot flash zip RUU Zip M7_UL_JB_50_Brigh
tstarUS_WWE_1.29.1540.3.zip
target reported max download size of 1526722560 bytes
error: cannot load 'RUU': No error
Click to expand...
Click to collapse
''fastboot flash zip RUU name_of_file.zip'' is not a valid command...
you need to flash this way:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip -----> yes again
fastboot reboot-bootloader
alray said:
''fastboot flash zip RUU name_of_file.zip'' is not a valid command...
you need to flash this way:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip -----> yes again
fastboot reboot-bootloader
Click to expand...
Click to collapse
Even if RUU is apart of the zip name? Because I just copy and pasted the name of the file onto the commandline.
And yes the command you gave me is how I converted to GPE. I also just copy and pasted the zip file name into the command. I just don't remember if the GPE zip had Ruu in the start of the name
Anyways;
I'll just rename the zip file to see what happens
Thanks
itsmarkiemark said:
Even if RUU is apart of the zip name? Because I just copy and pasted the name of the file onto the commandline.
And yes the command you gave me is how I converted to GPE. I also just copy and pasted the zip file name into the command. I just don't remember if the GPE zip had Ruu in the start of the name
Anyways;
I'll just rename the zip file to see what happens
Thanks
Click to expand...
Click to collapse
yes try renaming it to something simpler without space
alray said:
yes try renaming it to something simpler without space
Click to expand...
Click to collapse
tried flashing wwith a simple name and I got this
C:\Users\mm\Desktop\Android\HTC ONE>fastboot flash zip DeveloperEdition.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1004448 KB)...
OKAY [ 33.872s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 37.590s
I guess it doesnt like my model ID?
itsmarkiemark said:
tried flashing wwith a simple name and I got this
C:\Users\mm\Desktop\Android\HTC ONE>fastboot flash zip DeveloperEdition.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1004448 KB)...
OKAY [ 33.872s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 37.590s
I guess it doesnt like my model ID?
Click to expand...
Click to collapse
If you want to flash the dev edition ruu, you'll need to change mid to dev edition (PN0712000)
---------- Post added at 04:14 AM ---------- Previous post was at 04:11 AM ----------
itsmarkiemark said:
tried flashing wwith a simple name and I got this
C:\Users\mm\Desktop\Android\HTC ONE>fastboot flash zip DeveloperEdition.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1004448 KB)...
OKAY [ 33.872s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 37.590s
I guess it doesnt like my model ID?
Click to expand...
Click to collapse
its easy to do with s-off, just use this tool
alray said:
If you want to flash the dev edition ruu, you'll need to change mid to dev edition (PN0712000)
---------- Post added at 04:14 AM ---------- Previous post was at 04:11 AM ----------
its easy to do with s-off, just use this tool
Click to expand...
Click to collapse
right now im using the htc one toolkit. I think i can change the model id.
just to be clear is the meid from getvar info the model ID?
btw is there a list thread with a full list of MID and CID? because ive tried looking all around XDA and google.
just in case I want to go back to Tmobile stock.
itsmarkiemark said:
right now im using the htc one toolkit. I think i can change the model id.
just to be clear is the meid from getvar info the model ID?
btw is there a list thread with a full list of MID and CID? because ive tried looking all around XDA and google.
just in case I want to go back to Tmobile stock.
Click to expand...
Click to collapse
not meid, modelid.
you always need to match mid and cid to the ruu you want to use. when you download the ruu from htc1guru.com the required mid and cid are listed in the download page.
htc cid list here
htc one mid almost all listed here here
so for dev edition you need cid: BS_US001 and MID PN0712000
I'll recommand you use that tool I linked to you to change mid.
for cid just do this
Code:
fastboot oem writecid BS_US001
fastboot reboot
from htc1guru.com:
File Size 1.1 GiB
Downloads 3759
Comments Developer Edition
modelid: PN0712000
cid: BS_US001
MD5 ed60a68fe040ea4437cdd7e56c9fae0c
Support Ask Questions and find General Support info for this file here: http://forum.xda-developers.com/showthread.php?t=2428276
Click to expand...
Click to collapse
alray said:
not meid, modelid.
you always need to match mid and cid to the ruu you want to use. when you download the ruu from htc1guru.com the required mid and cid are listed in the download page.
htc cid list here
htc one mid almost all listed here here
so for dev edition you need cid: BS_US001 and MID PN0712000
I'll recommand you use that tool I linked to you to change mid.
for cid just do this
Code:
fastboot oem writecid BS_US001
fastboot rebot
Click to expand...
Click to collapse
Thanks... will try this right now
but one last question. will 4GLTE work if i change the CID? I never payed attention what were my MID and CID were before I flashed the GPE RUU. but its obvious that the CID didnt change since its still tmo-010. I was under the impression that flashing a RUU will change everything. I guessing it doesnt since I need to change the CID and MID to flash the Developer RUU
thanks! I did your steps and RUU is flashing as we speak.
appreciate the help. You have my many thanks!
itsmarkiemark said:
thanks! I did your steps and RUU is flashing as we speak.
appreciate the help. You have my many thanks!
Click to expand...
Click to collapse
np, if you appreciated the help please click the ''thanks'' button bellow my posts
alray said:
np, if you appreciated the help please click the ''thanks'' button bellow my posts
Click to expand...
Click to collapse
already did mate:highfive:

[Q] RUU is stuck at "Checking Header", can't go back to stock

Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
F:\fastboot>fastboot getvar all
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.09.401.1
version-misc: PVT SHIP S-OFF
serialno: SH35JWxxxxx
imei: 354436056xxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4279mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-f361905d64
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.064s
Click to expand...
Click to collapse
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
OKAY [ 67.418s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 67.608s
Click to expand...
Click to collapse
Can anyone point me in the right direction here? I don't really know what else to try.
fBx said:
Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
Can anyone point me in the right direction here? I don't really know what else to try.
Click to expand...
Click to collapse
you already have a thread here: http://forum.xda-developers.com/showthread.php?t=2796167 for the same issue. why a 2nd one?
btw you don't need to relock bootloader to flash ruu when the phone is s-off.
Would it work to flash a nandroid backup of an original german unbranded phone via CWM?
fBx said:
Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
Can anyone point me in the right direction here? I don't really know what else to try.
Click to expand...
Click to collapse
I have the same problem, How did you fix?
maxwilliam100 said:
I have the same problem, How did you fix?
Click to expand...
Click to collapse
try to flash the firmware first
alray said:
try to flash the firmware first
Click to expand...
Click to collapse
Thanks for the tip @alray
I'm downloading the firmware and will defenately follow directions form this link
trjlive (dot) com/guide-install-firmware-htc-one-m7/
In the meantime here is the info from my phone
HTML:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxx
imei: xxxxxxxxxxxxxxxx
meid: 99000146508682
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: 11111111
battery-status: good
battery-voltage: 3947mV
partition-layout: Generic
ecurity: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-371c4f408e
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.072s
maxwilliam100 said:
Thanks for the tip @alray
I'm downloading the firmware and will defenately follow directions form this link
trjlive (dot) com/guide-install-firmware-htc-one-m7/
In the meantime here is the info from my phone
HTML:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: 11111111
battery-status: good
battery-voltage: 3947mV
partition-layout: Generic
ecurity: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-371c4f408e
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Wait, you have a sprint phone? Hope you ar enot trying to flash this 4.19.401.9 ruu for GSM phones?
Btw you have s-off, you can use every ruu intended for sprint variant m7wls (x.xx.651.x RUU). Do not attempt to flash ruu for GSM variants. You should also set back your cid to its original value (SPCS_001).
And remove your S/N, IMEI and MEID numbers from your above post, these are sensitive data you want to keep for yourself.
alray said:
Wait, you have a sprint phone? Hope you ar enot trying to flash this 4.19.401.9 ruu for GSM phones?
Btw you have s-off, you can use every ruu intended for sprint variant m7wls (x.xx.651.x RUU). Do not attempt to flash ruu for GSM variants. You should also set back your cid to its original value (SPCS_001).
And remove your S/N, IMEI and MEID numbers from your above post, these are sensitive data you want to keep for yourself.
Click to expand...
Click to collapse
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg
maxwilliam100 said:
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg
Click to expand...
Click to collapse
your fastboot getvar and bootloader revels you have a Sprint phone .. Use Only Sprint Files
http://forum.xda-developers.com/sprint-htc-one
maxwilliam100 said:
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg
Click to expand...
Click to collapse
M7_WLS = Sprint = CDMA phone = different partition table = flash a ruu not for sprint and you'll end with a bricked phone.
use a x.xx.651.x ruu for cid SPCS_001 and mid PN0720000 only
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
and do not use windows 8 to flash it or you'll be stuck
use windows 7, MacOs or linux.
alray said:
M7_WLS = Sprint = CDMA phone = different partition table = flash a ruu not for sprint and you'll end with a bricked phone.
use a x.xx.651.x ruu for cid SPCS_001 and mid PN0720000 only
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
and do not use windows 8 to flash it or you'll be stuck
use windows 7, MacOs or linux.
Click to expand...
Click to collapse
@maxwilliam100
theirs also
Sprint 4.xx RUU
https://www.androidfilehost.com/?fid=23329332407573774
Sprint 5.xx RUU
http://forum.xda-developers.com/showthread.php?t=2795856
Thank you very much @alray and @clsA
I'm now downloading this ruu and since its at zip then i think i will have to rename the zip file to ruu.zip and flash from
fastboot oem rebootRUU
fastboot flash zip ruu.zip
Click to expand...
Click to collapse
Is there anything else that i should be aware of?
maxwilliam100 said:
Thank you very much @alray and @clsA
I'm now downloading this ruu and since its at zip then i think i will have to rename the zip file to ruu.zip and flash from
Is there anything else that i should be aware of?
Click to expand...
Click to collapse
you may have to do the fastboot flash zip ruu.zip 2 times
clsA said:
you may have to do the fastboot flash zip ruu.zip 2 times
Click to expand...
Click to collapse
Thanks Guys,
After three weeks of googling every available thing and failure, i came here as my last hope... PM random people on the internet and youtube..... without any success
Many thanks to @alray and @clsA
:highfive:

[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

Bootloop/ errors with GPE still on jellybean

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!!

HTC One M7 - Unfortunately Setup Wizard Has Stopped Working

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

Categories

Resources