Related
Hey so I had converted my M8 to GPe but am now selling it so I'm putting it back to Sense. Everything's working except for the wifi which I had issues with in the past from not flashing the Telus firmware.zip again from a 4.4.4 OTA file. At this link http://d-h.st/BfV the OTA file is there but there's only two fake looking download buttons that Chrome says both are malicious. One downloads an .exe and the other gets outright blocked. Can anyone help me out with finding the OTA file for Telus?
Thanks, I'm selling the phone in a few hours and am freaking as the wifi doesn't currently work! :/
Bump I just need the firmware.zip for Telus, the official OTA Collection on this forum's links are busted for me at least.
Hendrycks said:
Bump I just need the firmware.zip for Telus, the official OTA Collection on this forum's links are busted for me at least.
Click to expand...
Click to collapse
the blue download now button is the one you need, its not fake, the ota will have the firmware you need.
Are you s-off ?
Seanie280672 said:
the blue download now button is the one you need, its not fake, the ota will have the firmware you need.
Are you s-off ?
Click to expand...
Click to collapse
Oh ok, and ya I am but I used a different firmware and now my phone's got the HTC silver logo with 4 triangles with exclamation points in each other. I can only see that screen or what looks like the bootloader but it says the following:
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.1540 (3.28.1540.5) < ------this is all in red text
eMMC-boot 2048MB
Oct 2 2014,14:55:52.0
RUU <----- this is white text with an orange box around it
I'd love some help with recovering the phone to being usable again, I feel like a total dumbass :/ thanks in advance!
Hendrycks said:
Oh ok, and ya I am but I used a different firmware and now my phone's got the HTC silver logo with 4 triangles with exclamation points in each other. I can only see that screen or what looks like the bootloader but it says the following:
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.1540 (3.28.1540.5) < ------this is all in red text
eMMC-boot 2048MB
Oct 2 2014,14:55:52.0
RUU <----- this is white text with an orange box around it
I'd love some help with recovering the phone to being usable again, I feel like a total dumbass :/ thanks in advance!
Click to expand...
Click to collapse
The orange RUU means your phone is stuck in RUU mode, meaning you've not completed the firmware flash, you cant use that OTA file for the firmware, first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts, and 2nd, your phone has developer edition 1540 firmware, you need the full firmware of 3.28.1540.5 full wipe package or the RUU.
RUU zip: https://www.androidfilehost.com/?fid=95897840722643418 flash it like firmware.
Seanie280672 said:
first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts.
Click to expand...
Click to collapse
Sometimes is a full package, sometimes its not. You're right, that sometimes if not all modules were updated (from the preceding OTA) typically its not a full package (only includes the parts that were updated).
Flashing firmware zips without knowing exactly what you are doing is really dangerous. I've seen folks flash a "partial" firmware, that didn't contain all the bootloader modules; only 2 of the 3, and the one that wasn't updated didn't correspond to the 2 that were. BRICK
Seanie280672 said:
The orange RUU means your phone is stuck in RUU mode, meaning you've not completed the firmware flash, you cant use that OTA file for the firmware, first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts, and 2nd, your phone has developer edition 1540 firmware, you need the full firmware of 3.28.1540.5 full wipe package or the RUU.
RUU zip: https://www.androidfilehost.com/?fid=95897840722643418 flash it like firmware.
Click to expand...
Click to collapse
I ran a stupid developer edition .exe and it failed but I just want it back to being Telus and leave it at that, can I flash the Telus firmware.zip in the OTA and be good to go?
EDIT: I can't get to any menus once the phone is plugged in to my comp so how can I flash the RUU like firmware?
Hendrycks said:
I ran a stupid developer edition .exe and it failed but I just want it back to being Telus and leave it at that, can I flash the Telus firmware.zip in the OTA and be good to go?
EDIT: I can't get to any menus once the phone is plugged in to my comp so how can I flash the RUU like firmware?
Click to expand...
Click to collapse
Did you change your CID and MID on your phone before flashing the dev edition firmware ?
Seanie280672 said:
Did you change your CID and MID on your phone before flashing the dev edition firmware ?
Click to expand...
Click to collapse
My MID is whatever it had to be to be a GPe and my CID is set to SuperCID. I didn't want it to be dev I just needed a firmware that I thought would work and messed up.
EDIT: What steps do I have to take to get it out of being stuck in RUU? I tried using ADB to flash the RUU like a firmware and it doesn't work. It says it's the max download size and that it can't load firmware.zip
Hendrycks said:
My MID is whatever it had to be to be a GPe and my CID is set to SuperCID. I didn't want it to be dev I just needed a firmware that I thought would work and messed up.
EDIT: What steps do I have to take to get it out of being stuck in RUU? I tried using ADB to flash the RUU like a firmware and it doesn't work. It says it's the max download size and that it can't load firmware.zip
Click to expand...
Click to collapse
if you are s-off, you needed to change your MID and CID to match the firmware you are flashing, if you are still s-off, then you can edit the dev ed firmware you have downloaded, edit the android-info.txt file, change the MID in that file to whatever yours is and add your CID to the text file to whatever yours is too, then save it.
As your phone is already in RUU mode, with it highlighted on the screen, unplug the USB lead, and then plug it back in, should go back to the black screen with silver HTC logo.
DO NOT GO S-ON EVER AT THIS POINT, you'll be flashing a modified firmware, modified with your CID and MID and s-on will lead to an instant brick
Thats if this even works at all :fingers-crossed: only thing I can think of to try as its too late to change your phones MID and CID.
Seanie280672 said:
if you are s-off, you needed to change your MID and CID to match the firmware you are flashing, if you are still s-off, then you can edit the dev ed firmware you have downloaded, edit the android-info.txt file, change the MID in that file to whatever yours is and add your CID to the text file to whatever yours is too, then save it.
As your phone is already in RUU mode, with it highlighted on the screen, unplug the USB lead, and then plug it back in, should go back to the black screen with silver HTC logo.
DO NOT GO S-ON EVER AT THIS POINT, you'll be flashing a modified firmware, modified with your CID and MID and s-on will lead to an instant brick
Thats if this even works at all :fingers-crossed: only thing I can think of to try as its too late to change your phones MID and CID.
Click to expand...
Click to collapse
If the RUU was an .exe how can I edit it?
Okay so progress!! I just reflashed a firmware from before and followed this video: https://www.youtube.com/watch?v=oGWNtRAkRqs
And now I'm back into fastboot USB and so I can do everything again! So what do I do to get this all fixed up and back to being Telus? Flash the Firmware.zip from the Telus OTA?
Hendrycks said:
Okay so progress!! I just reflashed a firmware from before and followed this video: https://www.youtube.com/watch?v=oGWNtRAkRqs
And now I'm back into fastboot USB and so I can do everything again! So what do I do to get this all fixed up and back to being Telus? Flash the Firmware.zip from the Telus OTA?
Click to expand...
Click to collapse
noooo, forget the OTA all together, you cant take the chance that its not a full firmware, if its not you'll have a brick.
which firmware "from before" did you flash ?
Change your cid and mid to match the dev edition RUU and then run the RUU.
Seanie280672 said:
noooo, forget the OTA all together, you cant take the chance that its not a full firmware, if its not you'll have a brick.
which firmware "from before" did you flash ?
Change your cid and mid to match the dev edition RUU and then run the RUU.
Click to expand...
Click to collapse
I used the "1.54.401.5-W_Splash.zip" linked on that video I linked. It's what I used trying to get my phone back to Sense from GPe before this Developer Edition crap all went down aha.
With that firmware my getvar all is now:
C:\Users\Andrew\Desktop\HTC Tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
does that tell you anything about what to do next?
EDIT: Thanks so much for the help so far btw, I'm definitely not going to try and just jump head first doing this anymore, I have an S6 Edge pre-ordered and I am not going through this again with it.
Hendrycks said:
I used the "1.54.401.5-W_Splash.zip" linked on that video I linked. It's what I used trying to get my phone back to Sense from GPe before this Developer Edition crap all went down aha.
With that firmware my getvar all is now:
C:\Users\Andrew\Desktop\HTC Tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
does that tell you anything about what to do next?
EDIT: Thanks so much for the help so far btw, I'm definitely not going to try and just jump head first doing this anymore, I have an S6 Edge pre-ordered and I am not going through this again with it.
Click to expand...
Click to collapse
ok well first of all, you need to change that modelID, I suggest as you flashed the 401 firmware, you may as well stay on that, its world wide english international firmware, however your modelID is for google play edition, you need to change that to WWE, so see here, and make sure you copy and paste the commands, because one slip up with this and you'll have a brick: http://forum.xda-developers.com/showthread.php?t=2708581 choose the one for HTC Europe MID, ignore the fastboot reboot command at the very end of that instruction set.
then change you cid to HTC__001 (thats 2 underscores, cid is always 8 characters)
post your fastboot getvar all again once done and we'll take it from there.
Seanie280672 said:
ok well first of all, you need to change that modelID, I suggest as you flashed the 401 firmware, you may as well stay on that, its world wide english international firmware, however your modelID is for google play edition, you need to change that to WWE, so see here, and make sure you copy and paste the commands, because one slip up with this and you'll have a brick: http://forum.xda-developers.com/showthread.php?t=2708581 choose the one for HTC Europe MID, ignore the fastboot reboot command at the very end of that instruction set.
then change you cid to HTC__001 (thats 2 underscores, cid is always 8 characters)
post your fastboot getvar all again once done and we'll take it from there.
Click to expand...
Click to collapse
Ok I can definitely do what that link says except that now my phone isn't shown when I do adb devices, I have to be in fastboot USB right?
Hendrycks said:
Ok I can definitely do what that link says except that now my phone isn't shown when I do adb devices, I have to be in fastboot USB right?
Click to expand...
Click to collapse
yes fastboot usb is correct, but you cant use adb commands in fastboot mode, you use fastboot commands, so type fastboot devices instead.
oh damn, hang on 1 sec.
Seanie280672 said:
yes fastboot usb is correct, but you cant use adb commands in fastboot mode, you use fastboot commands, so type fastboot devices instead.
oh damn, hang on 1 sec.
Click to expand...
Click to collapse
I got it but that link says to do adb at the top but then switches to saying to do fastboot? When I do fastboot devices it does show up though. Do I still follow those instructions?
Hendrycks said:
I got it but that link says to do adb at the top but then switches to saying to do fastboot? When I do fastboot devices it does show up though. Do I still follow those instructions?
Click to expand...
Click to collapse
no, bear with me 1 min, on my M7 there was an app to run in recovery to change the MID, much easier, however, im just wondering if you run those commands in recovery, or within a booted rom.
Seanie280672 said:
no, bear with me 1 min, on my M7 there was an app to run in recovery to change the MID, much easier, however, im just wondering if you run those commands in recovery, or within a booted rom.
Click to expand...
Click to collapse
Sounds good thanks
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
AeroPeg said:
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
Click to expand...
Click to collapse
Are you S-Off? Is your device Developer Edition?
Sent from my HTC One_M8 using Tapatalk
AeroPeg said:
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
Click to expand...
Click to collapse
about error 155, try the following
1. Lock your bootloader through by booting into hboot and then going into fastboot and issuing the command "fasboot oem lock".
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Should work. Best of luck
How do I flash a new recovery?
SergioRmz, My device is S-ON, not developer edition, just factory unlocked from htc
Rawfire, I can't flash a RUU. The RUU just gives me an error after a few seconds from starting it - it says try again with a different RUU / wrong RUU (error 155).
Also, could you help me flash a new recovery? Could I flash a new recovery, then flash someone's stock nandroid backup & recovery to get my device to stock? Can I do all of this with a RELOCKED & S-ON device?
I have no idea how to flash a new recovery so instructions would be very very helpful
One final question - Can you tell me the best way in my current sitatution to get my device to stock without S-OFF? I'm willing to try anything (except S-off) to get my device to stock so I can sell it / trade it in.
AeroPeg said:
SergioRmz, My device is S-ON, not developer edition, just factory unlocked from htc
Rawfire, I can't flash a RUU. The RUU just gives me an error after a few seconds from starting it - it says try again with a different RUU / wrong RUU (error 155).
Also, could you help me flash a new recovery? Could I flash a new recovery, then flash someone's stock nandroid backup & recovery to get my device to stock? Can I do all of this with a RELOCKED & S-ON device?
I have no idea how to flash a new recovery so instructions would be very very helpful
One final question - Can you tell me the best way in my current sitatution to get my device to stock without S-OFF? I'm willing to try anything (except S-off) to get my device to stock so I can sell it / trade it in.
Click to expand...
Click to collapse
I can suggest couple of things, unlock the bootloader to install custom recovery and then you can flash any compatible rom,
Or to suggest some exact RUU, what's your device's exact model?
rawfire said:
about error 155, try the following
1. Lock your bootloader through by booting into hboot and then going into fastboot and issuing the command "fasboot oem lock".
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Should work. Best of luck
Click to expand...
Click to collapse
Just tried this, said "Device was already locked!"
Then tried RUU again, still said Error 155 "please get the correct RUU and try again"
When I unplug the phone it says error zip file with RUU written under it, and I had to press power + volume down to get it to the bootloader again.
Thanks for your continued help rawfire.
AeroPeg said:
Just tried this, said "Device was already locked!"
Then tried RUU again, still said Error 155 "please get the correct RUU and try again"
When I unplug the phone it says error zip file with RUU written under it, and I had to press power + volume down to get it to the bootloader again.
Thanks for your continued help rawfire.
Click to expand...
Click to collapse
Considering your firmware, I would suggest you to try THIS RUU & flash...
Device info
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
AeroPeg said:
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
Click to expand...
Click to collapse
try this one out, I'm sure it'll work.
Can't open
rawfire said:
try this one out, I'm sure it'll work.
Click to expand...
Click to collapse
Windows says invalid file, can't open.
7 zip can't extract either. I've tried both mirrors
Any other RUU suggestions?
AeroPeg said:
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
Click to expand...
Click to collapse
Is that os-4.16.1540.8 written on the bootloader ? If yes, you have a Dev Ed device, the other RUU meant for EU won't work for you.
Post fastboot getvar all (without serial & imei no.) then we know the actual device version
If it is indeed a Dev Ed device, what you need to do :
1. flash the 6.12.1540.4 firmware
See this : http://forum.xda-developers.com/showpost.php?p=64407841&postcount=2862
How-to, see this : http://forum.xda-developers.com/showpost.php?p=64416322&postcount=2864
2. Run RUU 6.12.1540.4 after the firmware is installed
Or the easy way is :
find 4.16.1540.8 RUU and install this then after, do OTA to 4.17.1540.9 then 6.12.1540.4
Edit : here is the direct HTC link for 4.16.1540.8 RUU - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Fastboot getvar all
ckpv5 said:
Is that os-4.16.1540.8 written on the bootloader ? If yes, you have a Dev Ed device, the other RUU meant for EU won't work for you.
Post fastboot getvar all (without serial & imei no.) then we know the actual device version
If it is indeed a Dev Ed device, what you need to do :
1. flash the 6.12.1540.4 firmware
See this : http://forum.xda-developers.com/showpost.php?p=64407841&postcount=2862
How-to, see this : http://forum.xda-developers.com/showpost.php?p=64416322&postcount=2864
2. Run RUU 6.12.1540.4 after the firmware is installed
Or the easy way is :
find 4.16.1540.8 RUU and install this then after, do OTA to 4.17.1540.9 then 6.12.1540.4
Edit : here is the direct HTC link for 4.16.1540.8 RUU - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
Here's what I got when I typed fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
Update: just googled 0P6B12000 is Dev edition, my bad. Going to try easy method of installing the 4.16.1540.8 RUU. Thanks ckpv5. Will post with results.
AeroPeg said:
Here's what I got when I typed fastboot getvar all:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
Click to expand...
Click to collapse
Then it is confirmed that you have a Dev Ed device.
Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.
Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
4.16.1540.8 RUU stuck
ckpv5 said:
Then it is confirmed that you have a Dev Ed device.
Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.
Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
Click to expand...
Click to collapse
4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now. Phone is showing just the silver htc logo, no progress bar or anything else.
Should I try flashing the 6.12.1540.4 firmware now? Thanks for the help so far ckpv5
Also, is the phone charging while connected to the computer & updating? Just asking since I can't see the battery percent (no OS) and don't want the phone to die while flashing.
AeroPeg said:
4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now.
Click to expand...
Click to collapse
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.
See the How-To linked above for the HTC Sync Manager download page, install it as it will install the USB Driver, then uninstall the Sync Manager but leave the driver
While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
ckpv5 said:
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.
See the How-To link above.
While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
Click to expand...
Click to collapse
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?
Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
AeroPeg said:
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?
Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
Click to expand...
Click to collapse
You must use USB2.0
When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.
If you don't have a USB2.0 - other options :
Option 1:
Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.
Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.
Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.
boot to bootloader then select hboot or boot to hboot - it's your choice
hboot will scan the file and ask to volume up to update
volume up
finish, press power to reboot and do all the setup stuff
remove 0P6BIMG.zip from your microSD
now you have ROM installed then can proceed with OTA and the rest.
Option 2:
Re unlock your bootloader again with your unlock_code.bin that you got from HTC.
Install TWRP 2.8.7.0
Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery
Reboot.. setup.. OTA..OTA.. done.
You can get all the needed files in the link shown in my signature
So now .. you have 3 options to choose.
1. RUU method
2. 0P6BIMG.zip method
3. Nandroid method
I got to go now ... good luck
SOLUTION - see ckpv5's 3 solutions
ckpv5 said:
You must use USB2.0
When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.
If you don't have a USB2.0 - other options :
Option 1:
Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.
Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.
Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.
boot to bootloader then select hboot or boot to hboot - it's your choice
hboot will scan the file and ask to volume up to update
volume up
finish, press power to reboot and do all the setup stuff
remove 0P6BIMG.zip from your microSD
now you have ROM installed then can proceed with OTA and the rest.
Option 2:
Re unlock your bootloader again with your unlock_code.bin that you got from HTC.
Install TWRP 2.8.7.0
Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery
Reboot.. setup.. OTA..OTA.. done.
You can get all the needed files in the link shown in my signature
So now .. you have 3 options to choose.
1. RUU method
2. 0P6BIMG.zip method
3. Nandroid method
I got to go now ... good luck
Click to expand...
Click to collapse
Thanks a TON ckpv5. I followed your instructions & reinstalled HTC Sync Manager, then connected the cable to a USB 2.0 port instead of 3.0. The RUU method you originally suggested worked like a charm. I now have stock HTC software, stock recovery just like I wanted. I then did an OTA to the latest software. When I sell my device in a few days, I'll be sure to follow your tip and run the latest 6.12.1540.4 RUU to clear off all the old OTA files.
Many thanks again for your help - hopefully others will see the 3 solutions you posted.
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated
Thanks..
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT44LWM05174
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
ceylin45 said:
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated
Click to expand...
Click to collapse
Yes ... just follow what is written on top post above.
I just received HTC one m8 and i want to install the right RUU for my device from HTC support site
can you please help, my fastboot vars :
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
4.16.1540.8 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
then you can do OTA to Marshmallow 6.12.1540.4
Thanks,
even if I have cid = 11111111 ?
Yes - 11111111 or SuperCID is a universal CID, RUU/OTA will accept that.
You need to relock bootloader before you run RUU because your device now is S-On
and you need a Windows PC with USB2.0 and latest HTC USB driver installed.
If you're not sure about HTC USB driver - download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install then after uninstall HTC Sync Manager but leave the HTC USB driver
ckpv5 said:
Yes - 11111111 or SuperCID is a universal CID, RUU/OTA will accept that.
Click to expand...
Click to collapse
Thanks
and another questions to be sure:
1) I get the device with 4.16.1540.8 installed , why i need to install it again ?
2) my device is s-on , does it affects on updates with supercid ?
1. I don't know why - you asked for the RUU so I gave you the link. You should know better whether you need it or not.
2. No .. as long as the ROM in your system now is non-rooted (never rooted) and stock recovery is installed .. should be fine.
If you're not sure then run the RUU then do OTA. Before that you can try to update and see whether it will success or fail.
Settings - about - software update.
ckpv5 said:
1. I don't know why - you asked for the RUU so I gave you the link. You should know better whether you need it or not.
2. No .. as long as the ROM in your system now is non-rooted (never rooted) and stock recovery is installed .. should be fine.
If you're not sure then run the RUU then do OTA. Before that you can try to update and see whether it will success or fail.
Settings - about - software update.
Click to expand...
Click to collapse
when I try to update from Settings the device found new version 4.17.1540.9 but get the following message :
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at wwwhtccom"
Your getvar doesn't show any irregularity.
I updated my M8 also on same CID 11111111 and MID 0P6B12000
So I have no idea .. I first helped because you asked for RUU.
Lets wait if anyone else will come to help for other problem
@redpoint73 - if you are around .. maybe you can help to confirm whether this device is AT&T or Developer Edition.
I have a feeling this is an AT&T converted to DEV ED and re S-On
@tapuz12ewq
Another possibility is your device is a AT&T originally .. you also can install RUU for AT&T, only thing is there is no Marshmallow update yet for AT&T - you can get the RUU 4.28.502.2 here : http://forum.xda-developers.com/showthread.php?t=2751432
ckpv5 said:
Your getvar doesn't show any irregularity.
I updated my M8 also on same CID 11111111 and MID 0P6B12000
So I have no idea .. I first helped because you asked for RUU.
Lets wait if anyone else will come to help for other problem
@redpoint73 - if you are around .. maybe you can help to confirm whether this device is AT&T or Developer Edition.
I have a feeling this is an AT&T converted to DEV ED and re S-On
@tapuz12ewq
Another possibility is your device is a AT&T originally .. you also can install RUU for AT&T, only thing is there is no Marshmallow update yet for AT&T - you can get the RUU 4.28.502.2 here : http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Thanks,
so I little bit confused , to fix it , which RUU are safe to install , 4.28.502.2 or 6.12.1540.4 ?
6.12.1540.4 definitely won't work, you'll get error 155 unless HTC already fix the RUU.
You can only try either 4.16.1540.8 or 4.28.502.2 and I'm not so sure whether installing 4.28.502.2 will success or not because your current version is 4.16.1540.8
another RUU that you can try is 4.17.1540.9 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_446501_signed_2.exe
Or ... S-Off the device with SunShine app (USD25) then you can fix it with any RUU.
I got to rest now ... it's 3 AM here ... good luck
ckpv5 said:
6.12.1540.4 definitely won't work, you'll get error 155 unless HTC already fix the RUU.
You can only try either 4.16.1540.8 or 4.28.502.2 and I'm not so sure whether installing 4.28.502.2 will success or not because your current version is 4.16.1540.8
another RUU that you can try is 4.17.1540.9 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_446501_signed_2.exe
Or ... S-Off the device with SunShine app (USD25) then you can fix it with any RUU.
I got to rest now ... it's 3 AM here ... good luck
Click to expand...
Click to collapse
I try to enter to stock recovery menu and find on the top screen "android stock recovery LRX22C"
do you familiar with this id LRX22C ? can it cause to not get the OTA ?
Thanks
tapuz12ewq said:
I try to enter to stock recovery menu and find on the top screen "android stock recovery LRX22C"
do you familiar with this id LRX22C ? can it cause to not get the OTA ?
Thanks
Click to expand...
Click to collapse
That's stock recovery for lollipop.
LRX22C - Android 5.0.1
LRX22G - Android 5.0.2
So which of the RUU that your tried ? I have a feeling that both will fail unless the device is S-Off again. The previous owner shouldn't change the S-Off status unless he put all the correct CID/MID to the device.
Maybe it needs the actual CID BS_US001 instead of 11111111 to get the OTA, personally I never have any problem with 11111111
ckpv5 said:
That's stock recovery for lollipop.
LRX22C - Android 5.0.1
LRX22G - Android 5.0.2
So which of the RUU that your tried ? I have a feeling that both will fail unless the device is S-Off again. The previous owner shouldn't change the S-Off status unless he put all the correct CID/MID to the device.
Maybe it needs the actual CID BS_US001 instead of 11111111 to get the OTA, personally I never have any problem with 11111111
Click to expand...
Click to collapse
yes, installed successfully 4.17.1540.9
thank you very much
i will try to OTA later to marshmallow
tapuz12ewq said:
yes, installed successfully 4.17.1540.9
thank you very much
i will try to OTA later to marshmallow
Click to expand...
Click to collapse
after I successfully installed 4.17.1540.9 from RUU
I tried to install the marshmallow update from by OTA but it failed with the same error :
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at www.htc.com"
how can I install the next update ?
It's weird that the RUU can be successfully installed but not OTA.
So .. you can try this to install next RUU 6.12.1540.4
1. Download the 6.12.1540.4 firmware - https://drive.google.com/file/d/0B4jGj3SfskzMbzBtd1R1VHlmbVU/view?usp=sharing
2. Download the 6.12.1540.4 RUU if you still don't have it - http://www.htc.com/us/support/htc-one-m8/news/
3. place the firmware.zip that you downloaded in your fastboot folder then open command prompt from your fastboot folder
4.Put your device to bootloader/fastboot mode
Run below commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
You'll see -
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip
fastboot reboot-bootloader
5. Run 6.14.1540.4 RUU
6. Done
ckpv5 said:
It's weird that the RUU can be successfully installed but not OTA.
So .. you can try this to install next RUU 6.12.1540.4
1. Download the 6.12.1540.4 firmware - https://drive.google.com/file/d/0B4jGj3SfskzMbzBtd1R1VHlmbVU/view?usp=sharing
2. Download the 6.12.1540.4 RUU if you still don't have it - http://www.htc.com/us/support/htc-one-m8/news/
3. place the firmware.zip that you downloaded in your fastboot folder then open command prompt from your fastboot folder
4.Put your device to bootloader/fastboot mode
Run below commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
You'll see -
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip
fastboot reboot-bootloader
5. Run 6.14.1540.4 RUU
6. Done
Click to expand...
Click to collapse
can I instead move from s-on to s - off with the sunshine app, maybe after that i will get the OTA ?
Yes .. that's a wise move to S-Off then you can change the CID to BS_US001 then you should be able to install OTA whenever it is available.
Also note, this 6.12.1540.4 maybe the last major update as the HTC support for major update end by March or April 2016.
ckpv5 said:
Yes .. that's a wise move to S-Off then you can change the CID to BS_US001 then you should be able to install OTA whenever it is available.
Also note, this 6.12.1540.4 maybe the last major update as the HTC support for major update end by March or April 2016.
Click to expand...
Click to collapse
BS_US001 also will keep my phone sim free ?
what about MID ?
Your phone is already SIM unlocked.
Change of CID has no effect on it.
No need to change MID as that's the Developer Ed MID
ckpv5 said:
Your phone is already SIM unlocked.
Change of CID has no effect on it.
No need to change MID as that's the Developer Ed MID
Click to expand...
Click to collapse
I not sure that it seem unlock originally , why the seller change to super cid ?
and you suspect it was at&t ?
While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
pauluthupm said:
I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Click to expand...
Click to collapse
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Solved : Unbrick HTC M* - Revert to Stock
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
Thank you for the help. fortunately i did find the solution. just the way u said only. I was in office and dint have access to xda in office. Let me also put what i have done.
pauluthupm said:
While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
Click to expand...
Click to collapse
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Make sure u download the htc fastboot files: Google is ur friend.
Place the image in the same folder as the htc fastboot files are.
rename the file to 0P6BIMG.zip( remember not to add two zips at the end.,windows generally hides the extension
Now open ur command prompt.
naviagate to the htc fastboot folder , i my case, i put in c drive
so it would like c:\htc_fastboot_files
Now Voulme Down Button and then press the power button.
In my case i had to use Power+Volume up to reboot the phone . And the moment it rebooted i pressed just the vol down button.
So we would be in Bootloader. Now switch phone to fastboot mode.
Navigate using volume buttons and power button to enter.
in fast boot mode
bring up ur command prompt:
We are already in the fastboot file folder. like i mentioned before: c:\htc_fastboot_files
type fastboot get var all
look for this info: (bootloader) version-main: 6.12.401.4 ( This might be different case to case, according to this you can search for relevant ruu, just google with the version number firmware)
Now htc_fastboot oem lock ( To relock the bootloader)
htc_fastboot oem rebootRUU
htc_fastboot flash zip Firmware_xx.zip ( in my case its 0P6BIMG.zip)
Once the flash completes, you will have a window which says Flash complete. OKAY. Mind you it takes some time.
After this,
htc_fastboot reboot . Thats it. Phone will take quite some time to reboot and complete the process.
My phone was up and running from here. But in case of errors. You might want look down.
IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (don’t use hubs! Always direct-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot...
The least dangerous FAILED messages are listed below and are safe to reboot (below this section you find CRITICAL errors, please observe):
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 24 android-info fail (means something wrong with android-info.txt in the zip)
- 32 header error (means the zip couldn't be read and unzipped properly)
- 41 Wrong Model ID (means it's not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap CID first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot in-between).
- 99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues.
- 130 wrong model ID (seems it's the same like 41, just that it shows in the FUU as 130.
- 155 seems to indicate different things. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match.
- 170 Check USB - FUU won’t run because of not working ADB.
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 24 "android-info fail" do:
- check that your ZIP isn’t some HTC OTA or anything thats got no android-info.txt - those cannot be flashed with fastboot flash zip nameof.zip command.
- check that your zip has a good MD5 and is not broken, check android-info.txt etc...
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn't help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
htc_fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
htc_fastboot oem writecid 11111111
You can change back to any desired CID after a successful firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn't brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definitely this means the ZIP is not signed - get an unmodified zip!
For “Error 130 wrong model ID" do:
- Please refer to Error Code 41/42.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers. One way to solve is to run the ARUWizard with the phone already in Fastboot mode. Else you will have to re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn't work well currently.
NOT safe to reboot / Flash (partly) happened Errors (if you encounter one of them, DON’T reboot:
- 152 Image Error - Phone Screen shows a little triangle beside a full green bar
For “Error 152 Image Error" do:
- Error 152 is quite rare, have seen it only once with a friend’s phone and it aborted the flash nearly at the end. The flash was started by the FUU. We could resolve the matter by NOT rebooting the phone and flashing the zip again through a manual fastboot flash as outlined further up.
pauluthupm said:
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
redpoint73 said:
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
Click to expand...
Click to collapse
Yep. That's straight up stolen (copy/pasted) from @Sneakyghost's threads.
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
xunholyx said:
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
Click to expand...
Click to collapse
Yeah, hard to tell what OP is talking about, if they don't even get the name right.
Also completely unnecessary of him to clutter up the board by copy and pasting huge amounts of text when a link can be provided (or refer to a thread, if he can't link).
NEW HTC m8 on custom recovery
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
--------------------------------------------------------------
Hi redpoint, need your help.
i want to revert my htc m8 to stock marshmallow. i am currently running ,mi ui with twrp recovery.
i am posting getvar results below. i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? can u help me with which firm ware i should download and which stock recovery should i install ?
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
pauluthupm said:
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
Click to expand...
Click to collapse
What's going on here, is this a different phone than what you listed in the first post?
pauluthupm said:
i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Click to expand...
Click to collapse
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
pauluthupm said:
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? 0
Click to expand...
Click to collapse
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
m8 revert to stock
redpoint73 said:
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
Click to expand...
Click to collapse
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
My device id belongs to India when i googled hence i m searching for these ruu. I wanted to try sunshine s off so that change the mid and cid to eu version and then try different ruu. Sunshine keeps giving me an error while running the initial tests it requires an non debuggable boot.img. So that doesnt help either.
do you require anymore info ? i can give u remote access if it requires.
PS: MIUI Rom is still working if i want to use my phone
pauluthupm said:
do you require anymore info ? i can give u remote access if it requires.
Click to expand...
Click to collapse
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
I had answered to your questions right below it. Did u mean i dint answer with details?
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
i have No clue how i found it. I googled lot of pages and somehow i found this this link. butyes i downloaded it from http://forum.gsmhosting.com/vbb/f48...-ruu-4-x-x-6-x-x-updated-19-3-2016-a-1940130/
I am not sure its signed or not. to be honest i have no clue.
answers to what you had asked?
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
Originally Posted by redpoint73
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
pauluthupm said:
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery.
Click to expand...
Click to collapse
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
pauluthupm said:
Now i tried flashing that ruu downloaded from gsm developers. but i failed with it.
Click to expand...
Click to collapse
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
How big is the file (MB)?
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
pauluthupm said:
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
Click to expand...
Click to collapse
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.720.xx specifically refer to your version M8 (CID and MID).
EDIT: fixed a typo, the number in red in the last line should read 720.
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
redpoint73 said:
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
HTML:
[QUOTE]Yes i renamed it to 0P6BIMG.zip
[/QUOTE]
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
remote: 12 signature verify fail)
Execution time is 115(s)
Click to expand...
Click to collapse
How big is the file (MB)?
1.66 GB
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.709.xx specifically refer to your version M8 (CID and MID).
Click to expand...
Click to collapse
Can you help me with the link i should download ? the correct ruu for my m8 ?
i can post the getvar values here if its of any help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
pauluthupm said:
Yes i renamed it to 0P6BIMG.zip
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
Click to expand...
Click to collapse
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
redpoint73 said:
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Bootloader is currently unlocked. Since you said i can run ruu in custom recovery also. I went and reinstalled custom recovery twrp 2.7 from Hasoons All in one Kit.
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
Click to expand...
Click to collapse
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
Click to expand...
Click to collapse
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
htc_fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
Execution time is 1(s)
Click to expand...
Click to collapse
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
Click to expand...
Click to collapse
pauluthupm said:
Being very honest, i have very little knowledge, its a new learning for me.
Click to expand...
Click to collapse
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
---------- Post added at 12:17 PM ---------- Previous post was at 12:10 PM ----------
pauluthupm said:
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Click to expand...
Click to collapse
It won't work. You need version numbers with 720, not 709.
I see in my last post, I said you needed 720 (which is correct) then a typo which implies you need 709 (not correct). So there may have been some confusion or conflicting info there.
Also, that version is too old (software number 1.54). You can only run RUU with equal or greater version than the firmware on the phone, which in your case is 4.xx.
pauluthupm said:
]
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
Click to expand...
Click to collapse
RELOCKED is the important part. Not sure why you got in error , but it looks to be properly relocked to run RUU.
Was it RELOCKED or UNLOCKED when you tried the RUU 6.20.709.2 and got Error 12: Signature Error?
redpoint73 said:
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
I should have. Now i regret for messing up the phone
Click to expand...
Click to collapse
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Absolutely learned it. I wouldnt want mod any phones anymore. Too much of headache, since am i am noob.
Click to expand...
Click to collapse
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
Click to expand...
Click to collapse
In fact i did have twrp back up. bt i had kept this sd card in my wallet. I broke the sd card by mistake. thats how i lost it.
OP cannot install RUU 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2 on his current firmware version.
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038He needs to install the signed 6.15.720.2 firmware first before install the RUU zip
Easier method is - install RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signed.exe
Download from : http://androidruu.com/?developer=M8
then OTA to 4.18.720.10 then later to 6.15.720.2
Or restore 4.18.720.10 backup & install 4.18.720.10 stock recovery (yeah .. skip a version) then OTA to 6.15.720.2
Download from : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck
Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.
ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.
Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.
You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.
hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip
ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1
ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same
alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan
alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14