Related
Thousand bows and kiss to anyone who can help me. I seem to have tried everything I can think of.
Need a miracle!
The story is I wanted to reload stock ATT Sense 5.0 firmware from GPE. During this process things got bad to worst. I went from S-Off > S-ON to Unlock to re-lock. Now I can't even unlock the set. The command takes but disclaimer doesn't appear. Reboot-bootloader still has *** RELOCKED ***
The Phone is on a bootloop to GPE. Boots to start up page then reboots a second later.
All RUU release return with ERROR 155.
RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe
D:\sdk-tools>fastboot getvar all
< waiting for device >
(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:
(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: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.053s
D:\sdk-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.157s
Same problem!!
domohan said:
Thousand bows and kiss to anyone who can help me. I seem to have tried everything I can think of.
The story is I wanted to reload stock ATT Sense 5.0 firmware from GPE. During this process things got bad to worst. I went from S-Off > S-ON to Unlock to re-lock. Now I can't even unlock the set. The command takes but disclaimer works. Reboot-bootloader still has *** RELOCKED ***
Same thing happened to me I was able to flash custom firmware but now still stuck at same problem except went from dark bootloader to white....
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Please let there be a way!!!
Click to expand...
Click to collapse
domohan said:
Thousand bows and kiss to anyone who can help me. I seem to have tried everything I can think of.
Need a miracle!
The story is I wanted to reload stock ATT Sense 5.0 firmware from GPE. During this process things got bad to worst. I went from S-Off > S-ON to Unlock to re-lock. Now I can't even unlock the set. The command takes but disclaimer doesn't appear. Reboot-bootloader still has *** RELOCKED ***
The Phone is on a bootloop to GPE. Boots to start up page then reboots a second later.
All RUU release return with ERROR 155.
RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe
D:\sdk-tools>fastboot getvar all
< waiting for device >
(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:
(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: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.053s
D:\sdk-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.157s
Click to expand...
Click to collapse
I feel like the problem is the downgrading issue from KITKAT 4.4.x ... ARGH!
domohan said:
Thousand bows and kiss to anyone who can help me. I seem to have tried everything I can think of.
Need a miracle!
The story is I wanted to reload stock ATT Sense 5.0 firmware from GPE. During this process things got bad to worst. I went from S-Off > S-ON to Unlock to re-lock. Now I can't even unlock the set. The command takes but disclaimer doesn't appear. Reboot-bootloader still has *** RELOCKED ***
The Phone is on a bootloop to GPE. Boots to start up page then reboots a second later.
All RUU release return with ERROR 155.
RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe
D:\sdk-tools>fastboot getvar all
< waiting for device >
(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:
(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: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.053s
D:\sdk-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.157s
Click to expand...
Click to collapse
You can see here for error 155
http://forum.xda-developers.com/showthread.php?t=2316726
why did you S-on??:/
also try this http://www.htc1guru.com/downloads/stock-rom-downloads/
here you can get the STOCK ATT ROM .
khandelwalsiddharth said:
You can see here for error 155
http://forum.xda-developers.com/showthread.php?t=2316726
why did you S-on??:/
also try this http://www.htc1guru.com/downloads/stock-rom-downloads/
here you can get the STOCK ATT ROM .
Click to expand...
Click to collapse
I questioned myself before I s-on..argh! should have stopped! obviously i'm beating myself up.....
link above has great information but needs s-off...
domohan said:
I questioned myself before I s-on..argh! should have stopped! obviously i'm beating myself up.....
link above has great information but needs s-off...
Click to expand...
Click to collapse
No now you are s-on go to HTC1guru.com and find a RUU for your carrier . I have seen there for att.
Sent from my HTC One using xda app-developers app
khandelwalsiddharth said:
No now you are s-on go to HTC1guru.com and find a RUU for your carrier . I have seen there for att.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I've tried the three RUU files for ATT as well as other RUU.exe files and they all error out with "ERROR[155]: UNKOWN ERROR"
I've also tried RUU from a laptop with the same "ERROR[155]: UNKOWN ERROR
I also got AV off
As of now it's impossible to use the signed RUU to get to factory default.
Similar issue discussed here. It's a one way trial. See how you fare http://forum.xda-developers.com/showthread.php?t=2608878
SaHiLzZ said:
Similar issue discussed here. It's a one way trial. See how you fare http://forum.xda-developers.com/showthread.php?t=2608878
Click to expand...
Click to collapse
Ya for SaHiLzZ! :good: :highfive:
You got me to the right path and did it!
Using the instructions and different trail and error I was able to get a firmware to stop the bootloop!
http://forum.xda-developers.com/showthread.php?t=2182823
Since I was already s-on and re-locked i did the following steps with different firmware.
x.xx.1700.x - HTC One Google Edition - did not work
x.xx.1540.x - HTC One U.S. Developer Edition :good::highfive:
This worked: 4.06.1540.3.zip . i renamed to firmware.zip and did the steps below
How to flash?
(bootloader needs to be relocked)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Click to expand...
Click to collapse
Unlocking still doesn't work. It will say successful but i never get the disclaimer and RUU still errors155.
domohan said:
Ya for SaHiLzZ! :good: :highfive:
You got me to the right path and did it!
Using the instructions and different trail and error I was able to get a firmware to stop the bootloop!
http://forum.xda-developers.com/showthread.php?t=2182823
Since I was already s-on and re-locked i did the following steps with different firmware.
x.xx.1700.x - HTC One Google Edition - did not work
x.xx.1540.x - HTC One U.S. Developer Edition :good::highfive:
This worked: 4.06.1540.3.zip . i renamed to firmware.zip and did the steps below
Unlocking still doesn't work. It will say successful but i never get the disclaimer and RUU still errors155.
Click to expand...
Click to collapse
So what's the current status now?? What os/firmware?
Sent from my HTC One using Tapatalk
n1234d said:
So what's the current status now?? What os/firmware?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
issues:
-kitkat 4.4 won't hold a charge.. always at 1%
-signed RUU.exe doesn't work. ERROR155
-unlock_code.bin doesn't work
D:\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(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: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
domohan said:
issues:
-kitkat 4.4 won't hold a charge.. always at 1%
-signed RUU.exe doesn't work. ERROR155
-unlock_code.bin doesn't work
D:\sdk-tools>fastboot getvar all
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
all: Done!
finished. total time: 0.052s
Click to expand...
Click to collapse
you need to unlock bootloader (using HTCdev), however, you have a US Dev Edition firmware (4.06.1540.2) with ATT CID: CWS__001 so I don't know if HTCdev will allow that.
try getting a new unlock tocken, and see... otherwise you'll have to wait for 4.06 ATT version to be rolled out and someone shares the OTA file, so you can return to ATT firmware.
nkk71 said:
you need to unlock bootloader (using HTCdev), however, you have a US Dev Edition firmware (4.06.1540.2) with ATT CID: CWS__001 so I don't know if HTCdev will allow that.
try getting a new unlock tocken, and see... otherwise you'll have to wait for 4.06 ATT version to be rolled out and someone shares the OTA file, so you can return to ATT firmware.
Click to expand...
Click to collapse
Last I saw, I think the android-info has CWS__001 listed in the Dev edition signed RUU
Sent from my HTC One using Tapatalk
n1234d said:
Last I saw, I think the android-info has CWS__001 listed in the Dev edition signed RUU
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yes that's fine, but i don't know if HTCdev's unlock token will work for that combo
@domohan try flashing the 4.06.1540.2 RUU again, and then OTA to 4.06.1540.3 and try unlocking.. Don't have any ideas now.. @nkk71 any ideas except waiting for the ATT ota? I'm not even sure it'll take the ota because its already Dev edition, and s-on..
Sent from my HTC One using Tapatalk
n1234d said:
@domohan try flashing the 4.06.1540.2 RUU again, and then OTA to 4.06.1540.3 and try unlocking.. Don't have any ideas now.. @nkk71 any ideas except waiting for the ATT ota? I'm not even sure it'll take the ota because its already Dev edition, and s-on..
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i don't think there's a 4.06 RUU, only the firmware package. if unlock token doesn't work, only idea i have is to get his hand on ATT OTA (once it's out), extract the signed firmware.zip, flash that, and hope HTCdev gives a good unlock token.
nkk71 said:
i don't think there's a 4.06 RUU, only the firmware package. if unlock token doesn't work, only idea i have is to get his hand on ATT OTA (once it's out), extract the signed firmware.zip, flash that, and hope HTCdev gives a good unlock token.
Click to expand...
Click to collapse
Oh yeah, sorry my bad.. Obviously he can't flash 3.22.. What if he extracts the firmware from the 4.06 ota and flashes that? Btw, aren't signed zips always encrypted? Won't decrypting the zip mess the signature?
Sent from my HTC One using Tapatalk
OTA.zip - Not encrypted
firmware.zip inside OTA.zip - encrypted
So interesting result though. Bootloops stopped with 4.06.1540.2 firmware.zip however unlock still doesn't work.
n1234d said:
@domohan try flashing the 4.06.1540.2 RUU again, and then OTA to 4.06.1540.3 and try unlocking.. Don't have any ideas now.. @nkk71 any ideas except waiting for the ATT ota? I'm not even sure it'll take the ota because its already Dev edition, and s-on..
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Generating a new unlock didn't work. Looks to be the same MD5/CRC32 value. I tried it anyways and it didn't work.
I've tried unlocking with flash 4.06.1540.2 and 4.06.1540.3 with same result.
On 4.06.1540.2 currently but OTA didn't come in.
nkk71 said:
i don't think there's a 4.06 RUU, only the firmware package. if unlock token doesn't work, only idea i have is to get his hand on ATT OTA (once it's out), extract the signed firmware.zip, flash that, and hope HTCdev gives a good unlock token.
Click to expand...
Click to collapse
will any fastboot erase xxxx or fastboot format xxxx commands do anything?
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.
Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.
Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!
Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(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: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.070s
ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process
After upgrade to 4.4 my phone started to reboot randomly and display "Process com.htc.dialer isn't responding", so i flashed hboot 1.44 and installed new ruu now phone after boot is stuck on black screen and i can see only top bar with icons.
Phone is S-OFF
UNLOCKED
not rooted
below getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:--------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4238mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.344s
Any help would be great.
Okay so i flashed it again with same ruu now it load lock screen and aftter unlock it only shows white htc logo and after couple minutes reboot, after one reboot it goes back to being stuck on black screen.
ol3k1990 said:
After upgrade to 4.4 my phone started to reboot randomly and display "Process com.htc.dialer isn't responding", so i flashed hboot 1.44 and installed new ruu now phone after boot is stuck on black screen and i can see only top bar with icons.
Phone is S-OFF
UNLOCKED
not rooted
below getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:--------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4238mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.344s
Any help would be great.
Okay so i flashed it again with same ruu now it load lock screen and aftter unlock it only shows white htc logo and after couple minutes reboot, after one reboot it goes back to being stuck on black screen.
Click to expand...
Click to collapse
download 4.19.401.9 no wipe firmware from here and flash it in fastboot RUU mode: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml
Code:
fastboot oem rebootRUU
fastboot flash zip (name of firmware).zip
fastboot flash zip (name of firmware).zip - [B]yes twice[/B]
[B][I]if successful at the end then[/I][/B]
fastboot reboot-bootloader
[B][I]if failed, report back here before doing anything else.[/I][/B]
now with your phone in fastboot USB mode still, download and run this RUU
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Seanie280672 said:
download 4.19.401.9 no wipe firmware from here and flash it in fastboot RUU mode:
Code:
fastboot oem rebootRUU
fastboot flash zip (name of firmware).zip
fastboot flash zip (name of firmware).zip - [B]yes twice[/B]
[B][I]if successful at the end then[/I][/B]
fastboot reboot-bootloader
[B][I]if failed, report back here before doing anything else.[/I][/B]
now with your phone in fastboot USB mode still, download and run this RUU
Click to expand...
Click to collapse
Hi, thanks for replaying
I did everyting above and after installing new ruu now is still rebooting the only difference it isstuck on white htc screen after lock screen and the Process com.htc.htcdialer error is showing again.
ol3k1990 said:
I did everyting above and after installing new ruu now is still rebooting the only difference it isstuck on white htc screen after lock screen and the Process com.htc.htcdialer error is showing again.
Click to expand...
Click to collapse
can you post a new fastboot getvar all please ?
Seanie280672 said:
can you post a new fastboot getvar all please ?
Click to expand...
Click to collapse
My new getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ----------------
(bootloader) imei: ------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4264mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.284s
ol3k1990 said:
My new getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVE THIS
(bootloader) imei: REMOVE THIS
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4264mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.284s
Click to expand...
Click to collapse
remove your imei and serial number please like ive done in the quote.
well the firmware flash went fine, if you notice you are now on HBOOT 1.56 and also have a version main, did the RUU flash ok ?
Seanie280672 said:
remove your imei and serial number please like ive done in the quote.
well the firmware flash went fine, if you notice you are now on HBOOT 1.56 and also have a version main, did the RUU flash ok ?
Click to expand...
Click to collapse
It went perfectly fine
ol3k1990 said:
It went perfectly fine
Click to expand...
Click to collapse
I would have to say it sounds like you have some sort of hardware problem going on there, maybe a bad nand.
you could try flashing twrp recovery and then doing a full format (format data) then try all of the above again, see if that works, if it still fails then id say it was down to hardware.
Seanie280672 said:
I would have to say it sounds like you have some sort of hardware problem going on there, maybe a bad nand.
you could try flashing twrp recovery and then doing a full format (format data) then try all of the above again, see if that works, if it still fails then id say it was down to hardware.
Click to expand...
Click to collapse
Thanks for replaying again ,
The phone is still under guarantee so if that wont help i will try to get it back to locked and s-off and then send it for service.
ol3k1990 said:
Thanks for replaying again ,
The phone is still under guarantee so if that wont help i will try to get it back to locked and s-off and then send it for service.
Click to expand...
Click to collapse
yes you can do that, but you will have to flash an earlier firmware and ruu before going s-on, with the later ones, like the one you have on there now, going s-on brings back the tampered flag.
Seanie280672 said:
yes you can do that, but you will have to flash an earlier firmware and ruu before going s-on, with the later ones, like the one you have on there now, going s-on brings back the tampered flag.
Click to expand...
Click to collapse
So it should be alright if i flash hboot 1.44 and install the ruu i used earlier.
ol3k1990 said:
So it should be alright if i flash hboot 1.44 and install the ruu i used earlier.
Click to expand...
Click to collapse
which ruu did you use earlier ?
Seanie280672 said:
which ruu did you use earlier ?
Click to expand...
Click to collapse
Cant post links yet but full name is
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
ol3k1990 said:
Cant post links yet but full name is
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Click to expand...
Click to collapse
yup that will be perfect, downgrade your hboot to 1.44, run the ruu.zip, make sure your firmware is downgraded to, it should be and then remove tampered flag from the bootloader if its still there, then lock the bootloader and s-on.
Seanie280672 said:
yup that will be perfect, downgrade your hboot to 1.44, run the ruu.zip, make sure your firmware is downgraded to, it should be and then remove tampered flag from the bootloader if its still there, then lock the bootloader and s-on.
Click to expand...
Click to collapse
Thanks for help
HTC supports Rooting so warranty may still be ok. Depending on your provider honoring it is another thing but I'm sure you can go directly to HTC if your provider has a problem with it.
bornthor said:
HTC supports Rooting so warranty may still be ok. Depending on your provider honoring it is another thing but I'm sure you can go directly to HTC if your provider has a problem with it.
Click to expand...
Click to collapse
HTC will refuse to repair, and make you pay for repairs if you have TAMPERED or UNLOCKED or RELOCKED flags on your bootloader, they will shift all fault and blame onto you.
Seanie280672 said:
HTC will refuse to repair, and make you pay for repairs if you have TAMPERED or UNLOCKED or RELOCKED flags on your bootloader, they will shift all fault and blame onto you.
Click to expand...
Click to collapse
I guess if you have experienced this and or have been told this personally then you know. I'm looking at the htcdev site that says "not all claims... May be covered under warranty." it's worth a try if you can't resurrect it.
Hi, Hope this post is in the right place, apologies if not.
I recently got a HTC One (M7) which was already unlocked, S-OFF and rooted and had 4.4 on it but i wanted to upgrade that OS so installed GPE and then it updated a few times to 5.01 which was all good but now i want to go back to 4.4 and this is the problem i'm having.
I'm in the UK using a O2 UK RUU file which i know does work but now when i go to use it i get as far as 'Checking Header' (5%) and thats it ..it wont go any further? I have tried in compatibility mode but that just returns errors.. I am using Fastboot & ADB tools and tried pushing the firmware but i'm really quite a novice when it comes t stuff like this ..
I tried fastboot getvar and all i get it a list of commands now which i dont understand
I do know my CID is 111111
Here's the Bootloader Info:
*** UNLOCKED***
M7 UL PVT SHIP S-OFF RH
CID 11111111
HBOOT 1.54.0000
RADIO 4T.30.3218.21
OPEN DSP v34.120.274.0429
OS 5.11. 1700 .3
All i want to do it flash the phone back to original Stock with OS 4.4 ..
also, when i try to go into recovery it wont let me, i get the green android laying on his back with a red exclamation on him and pressing up with power dont take me into recovery.
Any idea's please?
I would like to thank xda and it's members for all the help previously.. thanks guys
Craig_CFC said:
Hi, Hope this post is in the right place, apologies if not.
I recently got a HTC One (M7) which was already unlocked, S-OFF and rooted and had 4.4 on it but i wanted to upgrade that OS so installed GPE and then it updated a few times to 5.01 which was all good but now i want to go back to 4.4 and this is the problem i'm having.
I'm in the UK using a O2 UK RUU file which i know does work but now when i go to use it i get as far as 'Checking Header' (5%) and thats it ..it wont go any further? I have tried in compatibility mode but that just returns errors.. I am using Fastboot & ADB tools and tried pushing the firmware but i'm really quite a novice when it comes t stuff like this ..
I tried fastboot getvar and all i get it a list of commands now which i dont understand
I do know my CID is 111111
Here's the Bootloader Info:
*** UNLOCKED***
M7 UL PVT SHIP S-OFF RH
CID 11111111
HBOOT 1.54.0000
RADIO 4T.30.3218.21
OPEN DSP v34.120.274.0429
OS 5.11. 1700 .3
All i want to do it flash the phone back to original Stock with OS 4.4 ..
also, when i try to go into recovery it wont let me, i get the green android laying on his back with a red exclamation on him and pressing up with power dont take me into recovery.
Any idea's please?
I would like to thank xda and it's members for all the help previously.. thanks guys
Click to expand...
Click to collapse
Flash the firmware that matches your RUU first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then flash the RUU ... RUU gets stuck on the Hboot update step, flashing firmware first eliminates this problem
clsA said:
Flash the firmware that matches your RUU first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then flash the RUU ... RUU gets stuck on the Hboot update step, flashing firmware first eliminates this problem
Click to expand...
Click to collapse
Hi and thank you for your help.. i tried looking for the correct firmware.zip but after trying to flash it i get errors and 'fails' i'm not exactly sure which firmware i should be using - i did go to HTC site and selected what i thought were O2 UK FW files (1 was MR 3, 1 MR2 and 2 x zip files) so i assumed the .zip files were the FW files but its with these i got the errors. When i flashed them it did read them but aftr a few seconds returned a fail.
The RUU i am trying to put back on is RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2 which i know works on my device as i used it before i installed the GPE.
Any ideas please? I'm sorry i cant provide any more information.
Getvar Info:
C:\Users\Craig\Desktop\platform-tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: o2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4097mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.152s
C:\Users\Craig\Desktop\platform-tools>
Thanks again!
Craig_CFC said:
Hi and thank you for your help.. i tried looking for the correct firmware.zip but after trying to flash it i get errors and 'fails' i'm not exactly sure which firmware i should be using - i did go to HTC site and selected what i thought were O2 UK FW files (1 was MR 3, 1 MR2 and 2 x zip files) so i assumed the .zip files were the FW files but its with these i got the errors. When i flashed them it did read them but aftr a few seconds returned a fail.
The RUU i am trying to put back on is RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2 which i know works on my device as i used it before i installed the GPE.
Any ideas please? I'm sorry i cant provide any more information.
Getvar Info:
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: o2___001
(bootloader) security: off
all: Done!
finished. total time: 0.152s
C:\Users\Craig\Desktop\platform-tools>
Thanks again!
Click to expand...
Click to collapse
Well you phone is having a bit of an identity crises
you have hboot 1.54 ( assume it's the Dark bootloader for GPE)
your Firmware version is 6.x.401.x which is for the International version
and your CID is O2
I'm going to recommend you convert to International by changing you CID
fastboot oem writecid HTC__001
then flash this firmware
https://www.androidfilehost.com/?fid=23329332407574077
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
followed by this RUU
http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
or
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe - 1.50 GB
Maybe a little late but you could also try this:
http://forum.xda-developers.com/showthread.php?t=2358781
Go to post #2 and follow those instructions. Then flash whatever RUU you want.
I converted to GPE one time, didn't like it and also had trouble getting back to KK.
ANGRY_robert said:
Maybe a little late but you could also try this:
http://forum.xda-developers.com/showthread.php?t=2358781
Go to post #2 and follow those instructions. Then flash whatever RUU you want.
I converted to GPE one time, didn't like it and also had trouble getting back to KK.
Click to expand...
Click to collapse
Thanks again for the help.. much appreciated - im using TWRP v2.7 and wiped the whole phone by accident - i'm trying to push (adb sideload fw_4.19.401.9_custom.zip) but keeps coming back as no device - i have a yellow exclamation in device manager under 'other devices' 'one' and cant seem to find a windows 7 driver for this? once i can push or sideload the firmware i can flash it correct?
Thanks again
So to refresh my memory, you were on stock GPE and want to go back to stock sense correct? Now you have wiped the phone using twrp and twrp is all that is left?
Sent from my HTC One using XDA Free mobile app
ANGRY_robert said:
So to refresh my memory, you were on stock GPE and want to go back to stock sense correct? Now you have wiped the phone using twrp and twrp is all that is left?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Yes thats correct - i'm new to all this flashing stuff but have been reading lots of various posts on xda ...
This is whats returned from fastboot flash:
C:\Users\Craig\Desktop\platform-tools>fastboot flash zip fw_4.19.401.9_custom.zi
p
target reported max download size of 1526722560 bytes
sending 'zip' (27605 KB)...
OKAY [ 2.357s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.408s
C:\Users\Craig\Desktop\platform-tools>
and...
C:\Users\Craig\Desktop\platform-tools>adb push zip fw_4.19.401.9_custom.zip
adb server is out of date. killing...
* daemon started successfully *
error: device not found
i really dont know what to do now - i have all the correct files in the platform tools folder where i run the fastboot & adb commands (firmware & ruu) and have changed the CID to HTC___001
When i'm in recovery mode (TWRP) i get the yellow exclamation (screenshot hopefully attached)
First you need to get the driver working. Click on "one" and see if you can select from a list of devices on the pc. Now if the last working firmware on the phone was gpe then you need to push/sideload a gpe based Rom. This is because the partition structure is different than sense. You need to get a working Rom onto the phone first.
Sent from my HTC One using XDA Free mobile app
Craig_CFC said:
Yes thats correct - i'm new to all this flashing stuff but have been reading lots of various posts on xda ...
This is whats returned from fastboot flash:
C:\Users\Craig\Desktop\platform-tools>fastboot flash zip fw_4.19.401.9_custom.zi
p
target reported max download size of 1526722560 bytes
sending 'zip' (27605 KB)...
OKAY [ 2.357s]
writing 'zip'...
FAILED (remote: not allowed) You get this when the bootloader is locked did you relock the bootloader ?
finished. total time: 2.408s
C:\Users\Craig\Desktop\platform-tools>
and...
C:\Users\Craig\Desktop\platform-tools>adb push zip fw_4.19.401.9_custom.zip This is useless the firmware has to be flashed in fastboot RUU mode
adb server is out of date. killing...
* daemon started successfully *
error: device not found
i really dont know what to do now - i have all the correct files in the platform tools folder where i run the fastboot & adb commands (firmware & ruu) and have changed the CID to HTC___001
When i'm in recovery mode (TWRP) i get the yellow exclamation (screenshot hopefully attached)
Click to expand...
Click to collapse
Read my instructions again in post 4 and follow them
Your drivers are easy to fix see post 2 faq 2 here >> http://forum.xda-developers.com/showthread.php?t=2541082
clsA said:
Read my instructions again in post 4 and follow them
Your drivers are easy to fix see post 2 faq 2 here >> http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Thank you clsA, i'm doing this now - flashed firmware success.. just adding the RUU now - will let you know how it goes
Craig_CFC said:
Thank you clsA, i'm doing this now - flashed firmware success.. just adding the RUU now - will let you know how it goes
Click to expand...
Click to collapse
All fixed thank you so much - back to good old KitKat thanks for all your help !! very very much appreciated
Craig_CFC said:
All fixed thank you so much - back to good old KitKat thanks for all your help !! very very much appreciated
Click to expand...
Click to collapse
your welcome // Please use the Thanks button below my name
clsA said:
your welcome // Please use the Thanks button below my name
Click to expand...
Click to collapse
Getvar Info:
C:\Users\Craig\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(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: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.076s
Thanks again, ive clicked the like button
Craig_CFC said:
Getvar Info:
C:\Users\Craig\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(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: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.076s
Thanks again, ive clicked the like button
Click to expand...
Click to collapse
Looks good .. you should get some OTA updates almost immediately
clsA said:
Looks good .. you should get some OTA updates almost immediately
Click to expand...
Click to collapse
Had 2 OTA's immediately - phone is running sweet again :good: :good:
I'm having some issues with getting the firmware updated on my m7 and hoping someone can help.
I had posted some info in another thread of mine, but the thread is now over a year old so I figured I would start a new one.
First, here is my get-var output
C:\DroidTools>fastboot getvar all
(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: 99000146505640
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.094s
Not sure why the get-var didn't finish out (Too many links) ?
Anyways I tried updating the firmware with the latest I could find for the sprint variant, but I received this error.
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware as well and still no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues though.
I was also able to flash a newer twrp recovery without any hiccups.. so not sure what is up.
I am currently running AICP 12.1 but I am getting allot of crashes on random thing, and I suspect my mega-old firmware may be contributing. I also tried the last CyanogenMod that was available (13...?) but I couldn't get data and calls to work.
I also attempted to re-lock the boot-loader and tried flashing the firmware that way, but I received a different error.
"remote 12 signature verify fail"
After that I had to scramble and remember how to unlock the boot-loader again just to get my phone to boot back up lol. I haven't had my unlock file in years so that was fun.
So I'm stuck at 1.44.0000 for now. I'm starting to wonder if i have to find an older firmware first before I can jump to a newer one?
Also slightly confused on the RUU. I am already running custom recovery and custom ROM. Is updating the RUU still necessary?
All feedback and help is welcomed.
Thanks
cloud66 said:
I'm having some issues with getting the firmware updated on my m7 and hoping someone can help.
I had posted some info in another thread of mine, but the thread is now over a year old so I figured I would start a new one.
First, here is my get-var output
C:\DroidTools>fastboot getvar all
(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: 99000146505640
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.094s
Not sure why the get-var didn't finish out (Too many links) ?
Anyways I tried updating the firmware with the latest I could find for the sprint variant, but I received this error.
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware as well and still no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues though.
I was also able to flash a newer twrp recovery without any hiccups.. so not sure what is up.
I am currently running AICP 12.1 but I am getting allot of crashes on random thing, and I suspect my mega-old firmware may be contributing. I also tried the last CyanogenMod that was available (13...?) but I couldn't get data and calls to work.
I also attempted to re-lock the boot-loader and tried flashing the firmware that way, but I received a different error.
"remote 12 signature verify fail"
After that I had to scramble and remember how to unlock the boot-loader again just to get my phone to boot back up lol. I haven't had my unlock file in years so that was fun.
So I'm stuck at 1.44.0000 for now. I'm starting to wonder if i have to find an older firmware first before I can jump to a newer one?
Also slightly confused on the RUU. I am already running custom recovery and custom ROM. Is updating the RUU still necessary?
All feedback and help is welcomed.
Thanks
Click to expand...
Click to collapse
The firmware.zip you are trying to flash (the one linked in the other thread) isn't signed so your phone must be s-off. Sorry I should have mentioned that earlier but didn't noticed yours was s-on.
Its actually s-off now, showing "shipped s-on"?
Not sure what that means but the bootloader is definitely unlocked.
cloud66 said:
Its actually s-off now, showing "shipped s-on"?
Not sure what that means but the bootloader is definitely unlocked.
Click to expand...
Click to collapse
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
alray said:
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
Click to expand...
Click to collapse
Can you help me with an M7 that has these details:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone won't boot and the version-main is blank. First time I'm handling an M7 since this is a friends and the guides all involve toolkits so kinda lost at the moment. Bootloader is locked
Unlocked the bootloader only to find it has TWRP and no OS
Renosh said:
Can you help me with an M7 that has these details:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone won't boot and the version-main is blank. First time I'm handling an M7 since this is a friends and the guides all involve toolkits so kinda lost at the moment. Bootloader is locked
Unlocked the bootloader only to find it has TWRP and no OS
Click to expand...
Click to collapse
You can flash it back to stock rom using a RUU.
The latest version is here: http://dl3.htc.com/application/RUU_...691.655435036.1511537283-936972463.1506975706
Launch the .exe file with the phone in bootloader mode and showing "fastboot usb" in red
If you are not using a Windows PC you can find the .zip version of the same RUU here: https://androidfilehost.com/?fid=24588232905725176
You can flash it using fastboot in ruu mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
htc_fastboot reboot
If you prefer to flash a custom rom instead of stock, just make sure to choose one compatible with the Sprint variant (M7WLS). Push it to your phone memory and flash it using the "install" menu from twrp.
If the phone was sim-unlocked (working on other network than Sprint) you might have to sim-unlock again after flashing a RUU.
alray said:
You can flash it back to stock rom using a RUU.
The latest version is here: http://dl3.htc.com/application/RUU_...691.655435036.1511537283-936972463.1506975706
Launch the .exe file with the phone in bootloader mode and showing "fastboot usb" in red
If you are not using a Windows PC you can find the .zip version of the same RUU here: https://androidfilehost.com/?fid=24588232905725176
You can flash it using fastboot in ruu mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
htc_fastboot reboot
If you prefer to flash a custom rom instead of stock, just make sure to choose one compatible with the Sprint variant (M7WLS). Push it to your phone memory and flash it using the "install" menu from twrp.
If the phone was sim-unlocked (working on other network than Sprint) you might have to sim-unlock again after flashing a RUU.
Click to expand...
Click to collapse
Thanks I actually already managed to fix it using this thread:
https://forum.xda-developers.com/showthread.php?t=2795856
I used the full firmware but had to install this redistributable file for RUU to work (Windows 10) after locking bootloader:
https://npackd.appspot.com/p/com.microsoft.VisualCPPRedistributable/9.0.21022.8
I'll have to search for sim unlock, crap
alray said:
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
Click to expand...
Click to collapse
Thanks for the info. I'm going to try this sometime this week hopefully.
I've been running AICP 7.1.1 for nearly 3 weeks so far with minor hiccups now and then so i'm slightly hesitant to screw something up again :-/
I will update this as soon as I try a signed RUU from HTC.
Will a signed RUU destroy my recovery as well?
Also do I need to unlock after I flash the RUU?
Steps would be
1. relock bootloader
2. Install signed RUU
3. Relock Bootloader
4. Install TWRP
5. Install Rom
6. ?
Assuming I have these correct and everything works that is.
cloud66 said:
Thanks for the info. I'm going to try this sometime this week hopefully.
I've been running AICP 7.1.1 for nearly 3 weeks so far with minor hiccups now and then so i'm slightly hesitant to screw something up again :-/
I will update this as soon as I try a signed RUU from HTC.
Will a signed RUU destroy my recovery as well?
Also do I need to unlock after I flash the RUU?
Steps would be
1. relock bootloader
2. Install signed RUU
3. Re-unlock Bootloader (use www.htcdev.com/bootloader)
4. Install TWRP
5. Install Rom
6. ?
Assuming I have these correct and everything works that is.
Click to expand...
Click to collapse
Stock recovery will overwrite twrp when flashing a RUU, not really a concern since it will take only a few minutes to reflash twrp. And yes you'll need to re-unlock the bootloader after flashing the ruu, before you can install twrp back to your recovery partition. Steps 1 to 5 above are correct.