So I had my m7 running fine, rooted and running a custom ROM. I got the M8 and so I wanted to return it to stock so I could sell it. Im now regretting that because I can't get it to do anything now. I've reflashed various ROMs (stock and custom Sense ROMs) without any success. For awhile I could get the stock rom (or what i believe was stock) to boot but the touch screen wouldn't work so it was worthless. Now I only get it to set on the HTC logo with the white background. I've left it for over 30 minutes and nothing happens. I'm a semi-noob but this one has be stumped. Any help is greatly appreciated.
Here is what my bootloader looks like:
Tampered
Relocked
M7_WLS PVT SHIP S-On RH
HBOOT-1.55.0000
RADIO-1.00.20.0913_3
OpenDSP-v31.120.274.0617
eMMC-boot 2048MB
Oct 1 2013
biged87 said:
So I had my m7 running fine, rooted and running a custom ROM. I got the M8 and so I wanted to return it to stock so I could sell it. Im now regretting that because I can't get it to do anything now. I've reflashed various ROMs (stock and custom Sense ROMs) without any success. For awhile I could get the stock rom (or what i believe was stock) to boot but the touch screen wouldn't work so it was worthless. Now I only get it to set on the HTC logo with the white background. I've left it for over 30 minutes and nothing happens. I'm a semi-noob but this one has be stumped. Any help is greatly appreciated.
Here is what my bootloader looks like:
Tampered
Relocked
M7_WLS PVT SHIP S-On RH
HBOOT-1.55.0000
RADIO-1.00.20.0913_3
OpenDSP-v31.120.274.0617
eMMC-boot 2048MB
Oct 1 2013
Click to expand...
Click to collapse
Your phone is the (M7_WLS CDMA) Sprint variant. You are not posting in the right forum, so I guess you are flashing roms/recoveries for the wrong variant (M7_UL GSM)
alray said:
Your phone is the (M7_WLS CDMA) Sprint variant. You are not posting in the right forum, so I guess you are flashing roms/recoveries for the wrong variant (M7_UL GSM)
Click to expand...
Click to collapse
i am using the Sprint variant recovery and the roms have been for Sprint. i posted in this forum because i thought it was the right place to ask for help. what forum do you recommend?
Thanks!
biged87 said:
i am using the Sprint variant recovery and the roms have been for Sprint. i posted in this forum because i thought it was the right place to ask for help. what forum do you recommend?
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/sprint-htc-one/help
What rom version and what is your recovery version?
can you post a complete "fastboot getvar all" except the imei, meid and serialno
alray said:
http://forum.xda-developers.com/sprint-htc-one/help
What rom version and what is your recovery version?
can you post a complete "fastboot getvar all" except the imei, meid and serialno
Click to expand...
Click to collapse
Here is what I have from Get Var. I am thinking i need to update my hboot to 1.56 so I use OMJ's RUU ( http://forum.xda-developers.com/showthread.php?t=2658910 ). I try it now and it crashes at 4%.
C:\adbtools\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.0913_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
C:\adbtools\sdk\platform-tools>
biged87 said:
Here is what I have from Get Var. I am thinking i need to update my hboot to 1.56 so I use OMJ's RUU ( http://forum.xda-developers.com/showthread.php?t=2658910 ). I try it now and it crashes at 4%.
C:\adbtools\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.0913_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
C:\adbtools\sdk\platform-tools>
Click to expand...
Click to collapse
if your phone is s-on make sure to use the encrypted/signed version , not the decrypted one. bootloader must be locked or re-locked.
alray said:
if your phone is s-on make sure to use the encrypted/signed version , not the decrypted one. bootloader must be locked or re-locked.
Click to expand...
Click to collapse
Yeah i'm using the encrypted one as far as i can tell (Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip)
I am also relocked as you can see in the GET VAR screen. Maybe it has something to do with recovery or hboot. I don't know.
biged87 said:
I am also relocked as you can see in the GET VAR screen.
Click to expand...
Click to collapse
no, locked/unlocked/relocked status is not included in a getvar, its only displayed on the bootloader screen
alray said:
no, locked/unlocked/relocked status is not included in a getvar, its only displayed on the bootloader screen
Click to expand...
Click to collapse
You're right, my bad. It is in the OP though and is relocked. Thanks!
Might have made it worse.
I figured i should update my hboot from 1.55 to 1.56. So here is my current booloader screen.
Tampered
Relocked
M7_WLS PVT SHIP S-ON RH
HBOOT-1.56.0000
Radio-1.00.20.0913_3
OpenDSP-v31.120.274.0617
OS- 4.06.651.4
The OS line is new... I tried to then flash the Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip ROM using OMJ's instructions and it just crashes at 4% and says Error 155: UNKNOWN ERROR, like before. I appreciate any help.
biged87 said:
Might have made it worse.
I figured i should update my hboot from 1.55 to 1.56. So here is my current booloader screen.
Tampered
Relocked
M7_WLS PVT SHIP S-ON RH
HBOOT-1.56.0000
Radio-1.00.20.0913_3
OpenDSP-v31.120.274.0617
OS- (4.06.51.40)
That OS line is in Red and wan't there before. I tried to then flash the Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip ROM using OMJ's instructions and it just crashes at 4% like before. I appreciate any help.
Click to expand...
Click to collapse
did you download the firmware file and flash it twice ?
Seanie280672 said:
did you download the firmware file and flash it twice ?
Click to expand...
Click to collapse
Yes. typed the flash command twice.
Technically the very first time i only did it once and then i watched the video and saw him do it twice. so yeah i did it twice.
biged87 said:
Yes. typed the flash command twice.
Technically the very first time i only did it once and then i watched the video and saw him do it twice. so yeah i did it twice.
Click to expand...
Click to collapse
so you got the successful message at the end, then reboot your phone to fastboot USB mode and run the ruu
Seanie280672 said:
so you got the successful message at the end, then reboot your phone to fastboot mode and run the ruu, does it give you an error code when it fails ?
Click to expand...
Click to collapse
Yes i ran the reboot command and it went to the htc screen and i powered it down and went back into fastboot-usb and ran the RUU. It stops at 4% and says Error 155 (unknown). Im using Windows 7. Thanks for your continued help.
biged87 said:
Yes i ran the reboot command and it went to the htc screen and i powered it down and went back into fastboot-usb and ran the RUU. It stops at 4% and says Error 155 (unknown). Im using Windows 7. Thanks for your continued help.
Click to expand...
Click to collapse
well this is what the error means:
--------------------------------------------------------------------------------
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
PLEASE READ PAGE 5 AND 6 FROM THE THREAD YOU LINKED WHERE YOU ARE GETTING THE FILES FROM.
Related
Total noob here, please bear with me.
I rooted my HTC One M7 with TWRP following the guide from htconeroot.com (can't post links yet. yep, still a noob)
But instead of using openrecovery-twrp-2.5.0.0-m7 (touchscreen issues) I used openrecovery-twrp-2.6.0.1-m7 as was suggested in the comments. After that, I have a rooted HTC One with SuperSU. No special apps installed requiring root access, except for Greenify and PowerToggles.
This were the details in fastboot mode:
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.707.1
eMMC-boot 2048MB
Jun 23 2013,04:07:35.14299
Click to expand...
Click to collapse
Weeks later my phone's battery got drained, after I charged it, turned it on, gets past splash screen, and it just couldn't get to finish booting (black screen with visible notification bar, no carrier signal). Then it restarts again up to the black screen. This happens over and over.
Frustrated, I tried to install different ROMs just to get my phone working again. I tried Android Revolution HD 22 first, then the Odex-ed Stock Sense 5, Google Edition 4.0, all from Android Revolutions blog.
All of them sadly did not fix my problem, my phone still just keeps restarting and restarting. With Google edition though I was able to use it for like a minute or two, but then it restarts again. With the others, they were not usable.
Then I noticed that something changed in the values during fastboot:
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-1.29.651.10
eMMC-boot 2048MB
Click to expand...
Click to collapse
I don't know how this changed, but this is the RUU version isn't it? Does this explain why even with Google Edition ROM I couldn't get a signal?
How do I fix this problem? I'm really at a loss here. Someone please help
EDIT:
These are my current fastboot vars:
(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: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
No it is only the firmware version
Use Vomers great guide, ensure you read it and understand it will resolve your issue
Remember to thank vomer
http://forum.xda-developers.com/showthread.php?t=2365506
L0rdNels0n said:
No it is only the firmware version
Use Vomers great guide, ensure you read it and understand it will resolve your issue
Remember to thank vomer
http://forum.xda-developers.com/showthread.php?t=2365506
Click to expand...
Click to collapse
Thank you very much for the link! I've seen this thread before, but got turned off initially when I saw that S-OFF is not possible with HBOOT 1.54. Reading through it and following instructions, I was able to restore my firmware back to 2.24.707.1.
So now I'm back to where I started - $500 boot loop device.
I've read in several threads here that flashing RUU with S-ON is not possible, and that S-OFF cannot be achieved with HBOOT 1.54, and that it's not possible to downgrade HBOOT to 1.44.
I've also been looking for nandroid backups which I am hoping would solve my problem, but so far no luck.
Do I have any other options?
Thanks!
My terminology will probably be off or just plain wrong. Sorry but I am doing my best to give as much info as possible and appreciate the help.
I have a Sprint HTC One (US). I recently tried to put a new rom on my phone and messed up somewhere along the way. I think I wiped where I was loading the rom from :silly:. I now have no rom installed and my computer is not able to connect to or see the phone. When I try and use adb and run the "detect devices" command it comes back with nothing. So then I tried running the RUU for my phone and in versions 1.29.651.10, 1.29.615.7, and 1.29.615.6 I have received error code 155 in all of them. I read that means I need the boot loader to be locked but cannot find a way to do that if the adb is not detecting my phone.
I am able to get into TWRP v2.6.1.0. If I do not hold down the volume down key while trying to boot it will sit on the HTC logo screen.
At the top of the boot loader I have:
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0626
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:15705
I just want to be able to put the stock rom back on the phone. Any help?
Checkered Spheres said:
My terminology will probably be off or just plain wrong. Sorry but I am doing my best to give as much info as possible and appreciate the help.
I have a Sprint HTC One (US). I recently tried to put a new rom on my phone and messed up somewhere along the way. I think I wiped where I was loading the rom from :silly:. I now have no rom installed and my computer is not able to connect to or see the phone. When I try and use adb and run the "detect devices" command it comes back with nothing. So then I tried running the RUU for my phone and in versions 1.29.651.10, 1.29.615.7, and 1.29.615.6 I have received error code 155 in all of them. I read that means I need the boot loader to be locked but cannot find a way to do that if the adb is not detecting my phone.
I am able to get into TWRP v2.6.1.0. If I do not hold down the volume down key while trying to boot it will sit on the HTC logo screen.
At the top of the boot loader I have:
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0626
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:15705
I just want to be able to put the stock rom back on the phone. Any help?
Click to expand...
Click to collapse
Make sure the rom you tried to flash was sprint compatible. Might be your issue. Boot your phone in bootloader mode, select fastboot then connect usb cable to computer. Open a cmd prompt from your adb/fastboot folder and type this command:
Code:
fastboot getvar all
copy/paste output here but remove IMEI and SN
also ADB only works when phone is booted to OS or RECOVERY
FASTBOOT works when phone is in bootloader mode.
so the command to relock the bootloader is
Code:
fastboot oem lock
don't lock the bootloader yet, want to be sure if the ruu match your getvar info.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4030mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.564s
Checkered Spheres said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4030mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.564s
Click to expand...
Click to collapse
You need s-off to use these ruu because its a version downgrade (from 1.31.651.2 ----> 1.29.651.7)
So you need to s-off with revone tool before using ruu. don't forget you have a sprint version and you can't use some stuff here. You must make sure you always download srpint compatible rom and recovery (M7_WLS)
alray said:
You need s-off to use these ruu because its a version downgrade (from 1.31.651.2 ----> 1.29.651.7)
So you need to s-off with revone tool before using ruu. don't forget you have a sprint version and you can't use some stuff here. You must make sure you always download srpint compatible rom and recovery (M7_WLS)
Click to expand...
Click to collapse
So what would the order of operations be? Relock boot loader, s-off, then ruu?
Is there any problem that when I type "adb devices" it returns with nothing? I know it was able to pull the info for the getvar but am unsure how that is possible.
Checkered Spheres said:
So what would the order of operations be? Relock boot loader, s-off, then ruu?
Is there any problem that when I type "adb devices" it returns with nothing? I know it was able to pull the info for the getvar but am unsure how that is possible.
Click to expand...
Click to collapse
don't relock bootloader! Flash a sprint compatible rom, then s-off with revone. when you have s-off, remove tempered flag from bootloader and set it to ''locked'' not ''relocked'' and then flash the ruu.
btw adb commands like ''adb devices'' will only work when OS is booted or in custom recovery, not in bootloader.
Hi All, Firstly let me say thankyou for the years of help i've received from all on this site...
Ok so without thinking i went ahead and tried rooting my HTC one (M7)
It didnt work but now i have TAMPERED and UNLOCKED,
I would like to know if there is a way I can Remove both the above and revert back to how it was? if so can i also remove the Clockwork Recovery as well?
I just want it to go back to how it was before i started messing.
phone details
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
HTC one UK, o2, KITKAT 4.4.2 sense 5.5
i tried S-OFF with firewater, revone and toolkit but still cant S-OFF, so any help to revert back to how it was (noob style) thankyou all
dazzco said:
Hi All, Firstly let me say thankyou for the years of help i've received from all on this site...
Ok so without thinking i went ahead and tried rooting my HTC one (M7)
It didnt work but now i have TAMPERED and UNLOCKED,
I would like to know if there is a way I can Remove both the above and revert back to how it was? if so can i also remove the Clockwork Recovery as well?
I just want it to go back to how it was before i started messing.
phone details
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
HTC one UK, o2, KITKAT 4.4.2 sense 5.5
i tried S-OFF with firewater, revone and toolkit but still cant S-OFF, so any help to revert back to how it was (noob style) thankyou all
Click to expand...
Click to collapse
Should be pretty simple
just relock your bootloader with fastboot
fastboot oem lock
then flash this
RUU >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353143_signed_2.exe
clsA said:
Should be pretty simple
just relock your bootloader with fastboot
fastboot oem lock
then flash this
Click to expand...
Click to collapse
thankyou very much for the VERY quick response...
I will try this now!
could you.... please.... in case i get stuck tell me how to relock bootloader with fastboot because apparently i need S-OFF to do this!
thankyou again
dazzco said:
thankyou very much for the VERY quick response...
I will try this now!
could you.... please.... in case i get stuck tell me how to relock bootloader with fastboot because apparently i need S-OFF to do this!
thankyou again
Click to expand...
Click to collapse
I just did ?
fastboot oem lock
clsA said:
I just did ?
fastboot oem lock
Click to expand...
Click to collapse
Sorry! I tried it But it says it cant do it because i need the correct Rom Update Utility
Error 131 customer id error
dazzco said:
Sorry! I tried it But it says it cant do it because i need the correct Rom Update Utility
Click to expand...
Click to collapse
then your not _O2_UK_4.20.206.16
what does it say your OS is ?
clsA said:
then your not _O2_UK_4.20.206.16
what does it say your OS is ?
Click to expand...
Click to collapse
it doesnt but my misses said its unlocked.
it says OS- (nothing after)
thanx
dazzco said:
it doesnt but my misses said its unlocked.
it says OS- (nothing after)
thanx
Click to expand...
Click to collapse
relock the bootloader
then run the ruu
clsA said:
relock the bootloader
then run the ruu
Click to expand...
Click to collapse
Still same, Sorry this is the file i got from getvar
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************* (i removed)
(bootloader) imei: *************** (i removed)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3914mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
My htc one m7 AT&T is bricked i think. I got it from a friend and it had the htc sign with four exclamation marks. and the boot loader says the following:
***Tampered***
***Relocked***
M7_UL PUT SHIP S-ON RH
RADIO-1.44.000
OPENDSP-v26.120.274.0202
eMMC-boot
Jul 5 2013, 16:04:18:109
RUU
Zraww said:
My htc one m7 AT&T is bricked i think. I got it from a friend and it had the htc sign with four exclamation marks. and the boot loader says the following:
***Tampered***
***Relocked***
M7_UL PUT SHIP S-ON RH
RADIO-1.44.000
OPENDSP-v26.120.274.0202
eMMC-boot
Jul 5 2013, 16:04:18:109
RUU
Click to expand...
Click to collapse
You are stuck in ruu mode, the bootloader is waiting for the flash.
What is the output of "fastboot getvar all" ? Remove emei and serial before posting it.
alray said:
You are stuck in ruu mode, the bootloader is waiting for the flash.
What is the output of "fastboot getvar all" ? Remove emei and serial before posting it.
Click to expand...
Click to collapse
@alray What should i do to fix it and the getvar is
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
getvar:all FAILED (status read failed (Too many links))
Zraww said:
@alray What should i do to fix it and the getvar is
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Your pretty lucky, you have an AT&T phone on the original firmware.
If you plan on keeping it and using it you should get S-off with rumrunner before you update it past 3.x.502.x
You can find the RUU you need in the AT&T general forums posted by me.
If you just want a working phone use the 3.x.502.x ruu. Then use rumrunner to a-off
clsA said:
Your pretty lucky, you have an AT&T phone on the original firmware.
If you plan on keeping it and using it you should get S-off with rumrunner before you update it past 3.x.502.x
You can find the RUU you need in the AT&T general forums posted by me.
If you just want a working phone use the 3.x.502.x ruu. Then use rumrunner to a-off
Click to expand...
Click to collapse
can you post the link for the ruu and rumrunner plz that will help me alot
Zraww said:
can you post the link for the ruu and rumrunner plz that will help me alot
Click to expand...
Click to collapse
RUU >> http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
http://rumrunner.us/
Rom to use with Rumrunner > https://www.androidfilehost.com/?fid=23622183712458309
@clsA the version of my phone is 1.26.502.12 so the ruu wont work ive tried other ruus but they stop at sending and takes long to complete
Zraww said:
@clsA the version of my phone is 1.26.502.12 so the ruu wont work ive tried other ruus but they stop at sending and takes long to complete
Click to expand...
Click to collapse
use this RUU instead http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
if you still have problems with sending, check your drivers, sounds like you don't have your HTC fastboot drivers set up correctly.
then continue with what clsA said above.
@Seanie280672 every time i run ruus it stops at like 5% or 20% then takes very long so i will try the one you gave me and post the results
Zraww said:
@Seanie280672 every time i run ruus it stops at like 5% or 20% then takes very long so i will try the one you gave me and post the results
Click to expand...
Click to collapse
if it appears to stop at about 20%, don't be too concerned, just leave it running for 10 mins and doing its things, ive flashed RUU's before which go up to 5% approx. and 10 mins later jump to 99% with nothing inbetween.
@Seanie280672 they took longer than a hour
Zraww said:
@Seanie280672 they took longer than a hour
Click to expand...
Click to collapse
No if your having problems with RUU / Flash the firmware first then the RUU, this works 98% of the time.
@clsA what do you mean by to flash the firmware how do i do that
Zraww said:
@clsA what do you mean by to flash the firmware how do i do that
Click to expand...
Click to collapse
let me find all the files and instructions for you
fastboot flash zip firmware.zip / this file >> https://www.dropbox.com/s/o1o487pmdfi9dyo/firmware_3.17.502.3.zip?dl=0
and then flash this RUU >> http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
@clsA the firmware didnt flash i did it twice and it failed
Zraww said:
@clsA the firmware didnt flash i did it twice and it failed
Click to expand...
Click to collapse
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
@clsA it still fails
Zraww said:
@clsA it still fails
Click to expand...
Click to collapse
You can try to flash a custom recovery and then flash a custom rom like InsertCoin
@Insecret can u please post up a link of the files
Zraww said:
@Insecret can u please post up a link of the files
Click to expand...
Click to collapse
maybe @alray can help you
I have a HTC One M7 on EE that is no longer used at work and thought I would snaffle it to use at home, I got the network unlock code from EE and tried to apply it and found it didn't work, on digging about I assume it doesn't work as the phone has been updated to Android 5.1 Google Play Edition Kernel Version 3.4.10-ge0627be so it now has the wrong modelid and cidnum. I didn't update it originally and don't know its history I have just picked it up as it was going spare.
So I thought no problem I will just put it back to a stock rom and run the network unlock again, I don't really like the 5.1 GPE anyway and would prefer it on Lollipop 5.02.
This was some 8 hours ago and I have tried everything and I cannot unlock the bootloader (Its relocked), whatever I try just does nothing, the Recovery doesn't work I just get the red triangle, I have tried a stock Guru RUU but this wont work as I assume it now has the incorrect modelid and cidnum, I am just going round and round in circles. I cannot change the modelid as I cannot unlock it
This is the getvar all for the phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
Am I on a hiding to nothing or should I be able to reverse it back to stock to network unlock it ?
Info on the recovery screen as follows
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.36.3218.06
Open DSP-v34.120.274.0429
OS-6.04.1700.6
eMMC-boot 2048MB
Apr 28 2015,09:16:24:0
Can anyone point me in the right direction of show me the error of my ways before it drives me crazy.
Thanks Sean
Sean1971 said:
I have a HTC One M7 on EE that is no longer used at work and thought I would snaffle it to use at home, I got the network unlock code from EE and tried to apply it and found it didn't work, on digging about I assume it doesn't work as the phone has been updated to Android 5.1 Google Play Edition Kernel Version 3.4.10-ge0627be so it now has the wrong modelid and cidnum. I didn't update it originally and don't know its history I have just picked it up as it was going spare.
So I thought no problem I will just put it back to a stock rom and run the network unlock again, I don't really like the 5.1 GPE anyway and would prefer it on Lollipop 5.02.
This was some 8 hours ago and I have tried everything and I cannot unlock the bootloader (Its relocked), whatever I try just does nothing, the Recovery doesn't work I just get the red triangle, I have tried a stock Guru RUU but this wont work as I assume it now has the incorrect modelid and cidnum, I am just going round and round in circles. I cannot change the modelid as I cannot unlock it
This is the getvar all for the phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
Am I on a hiding to nothing or should I be able to reverse it back to stock to network unlock it ?
Info on the recovery screen as follows
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.36.3218.06
Open DSP-v34.120.274.0429
OS-6.04.1700.6
eMMC-boot 2048MB
Apr 28 2015,09:16:24:0
Can anyone point me in the right direction of show me the error of my ways before it drives me crazy.
Thanks Sean
Click to expand...
Click to collapse
You'll need s-off to unlock the bootloader since there is an issue with bootloader unlock on GPE (both htcdev.com and fastboot oem unlock method doesn't work).
Use Sunshine s-off to s-off and unlock the bootloader
alray said:
You'll need s-off to unlock the bootloader since there is an issue with bootloader unlock on GPE (both htcdev.com and fastboot oem unlock method doesn't work).
Use Sunshine s-off to s-off and unlock the bootloader
Click to expand...
Click to collapse
Great thanks for your help, I will give that a try today.
Sorry me again, Sunshine passes the pre checks apart from it reports my phone is not rooted. I cannot run SuperSU Installer to root the device because, recovery doesn't work and whatever I try to get TWRP on the phone fails. I just seem to be going round in circles. When I Fastboot Flash Recovery the TWRP img file it says its copied the correct file size but I don't get the finished okay message just a fail.
I didn't put the 5.1 GPE on the phone, is it normal for the phone to be relocked and S-On after putting on the 3.4.10-ge0627be 5.1 GPE rom on the phone ?
Any advice welcomed as I am well out of my depth with this.
Sean1971 said:
Sorry me again, Sunshine passes the pre checks apart from it reports my phone is not rooted. I cannot run SuperSU Installer to root the device because, recovery doesn't work and whatever I try to get TWRP on the phone fails. I just seem to be going round in circles. When I Fastboot Flash Recovery the TWRP img file it says its copied the correct file size but I don't get the finished okay message just a fail.
I didn't put the 5.1 GPE on the phone, is it normal for the phone to be relocked and S-On after putting on the 3.4.10-ge0627be 5.1 GPE rom on the phone ?
Any advice welcomed as I am well out of my depth with this.
Click to expand...
Click to collapse
You can't flash a custom recovery, your bootloader is locked...!
Try to achieve temp root so you can use sunshine like they do in the verizon htc one forum.
alray said:
You can't flash a custom recovery, your bootloader is locked...!
Try to achieve temp root so you can use sunshine like they do in the verizon htc one forum.
Click to expand...
Click to collapse
Thanks for your help, really appreciate it. See I said I was out of my depth ....
I tried Toweroot and that wouldn't work for my device, so then tried Kingroot and that sorted it so I was able to run Sunshine and I now have it S-OFF and Unlocked, I can now try to get it back to stock and get it network unlocked.