Related
Right now I'm facing problem to update to stock using RUU.
My version is 2.17.707.3 so I dowload from HTCRUU the file named RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed.exe, but after some operations (reboot to bootloader, etc) gives me an 132 error saying: "Signature error". Why is that?
Also I found other RUU file named RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed.exe, Can i use just this to update to JB?
Before you proceed, check the actual version no. Go to bootloader in fastboot mode, do command fastboot getvar version-main then you will know which RUU is correct for you.
Example, mine is 3.14.707.24, then RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Ra dio_5.1204.162.29_release_296434_signed.exe is the correct RUU for my device.
Code:
D:\HTC\fastboot>fastboot getvar version-main
version-main: 3.14.707.24
finished. total time: -0.000s
D:\HTC\fastboot>
I already do that. That's why I know how version to use.
Then follow this procedure to flash the RUU
1) Boot to bootloader in fastboot mode, relock your bootloader - fastboot oem lock
2) Still in fastboot mode, run the RUU follow the updater instruction until it finish.
Important points relock bootloader & run ruu in fastboot
I already do that too. The problem is that after 1 minute, it says ERROR 132, "Signature Problem"
ERROR 132, "Signature Problem" usually refer to unlocked bootloader. As you said you did relock the bootloader, I have no idea. Maybe someone else can assist you on this.
Quick question. After flash the stock recovery is mandatory to erase the cache using fastboot erase cache?
After relock the bootloader, can I flash the stock recovery?
Not mandatory but recommended.
You can't flash stock recovery or stock boot.img after you relock the bootloader.
If you need to flash those to you device, do it before you relock the bootloader.
ckpv5 said:
Not mandatory but recommended.
You can't flash stock recovery or stock boot.img after you relock the bootloader.
If you need to flash those to you device, do it before you relock the bootloader.
Click to expand...
Click to collapse
Im also stuck with this issue! Error 132!!! I cant flash my HOX+ back to stock and I need toO!!! hhheelp!!
i have htc one x 4.0.3
fastboot getvar version-main
device >
1.29.401.12
total time: 0.010s
The bootloader is relocked and the Hboot is 0.95
tried to upgrade to JB 4.1 with RUU_ENDEAVOR_U_JB_45_S_hTC_EUROPE_WWE_3.14.707.24_Ra dio_5.1204.162.29_release_296434_signed.exe but wont finish due to a 132 signature problem error...
What are the steps i have to do ?
best regards
leddra2k said:
Im also stuck with this issue! Error 132!!! I cant flash my HOX+ back to stock and I need toO!!! hhheelp!!
Click to expand...
Click to collapse
Ok, just to ask, this is HTC One X section, and in quote i can see that you have HTC One X +? Did you download RUU for HTC one X or HTC One X +?
Because guide for back to stock with RUU is just like previous members wrote... go into fastboot, relock bootloader, run RUU (with administrators rights in vista or win7)..
And for the others: http://forum.xda-developers.com/showthread.php?t=1859714
Stock OTA and RUU: http://androidfiles.org/ruu/?dir=Endeavor
IMPORTANT from the link:
Get the RUU file required for your device:
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
Code: fastboot getvar version-main
If for example this command returns the value 1.29.401.x then you need to use that file or you can use a higher numbered file from the same region eg 2.17.401.x. NOTE: You can't use a lower numbered file eg 1.26.401.x and you also can't use a file from a different region eg 2.17.707.x.:
PROCESS :
1. Boot your phone to fastboot mode by holding power+vol down button for 10 secs..(if your phone keeps restarting in normal phone mode, go to Setting>Power and untick Fast boot)
2. Plug your phone into your PC and open a Command Prompt.
(windows XP - Click Start > Run > type CMD in box then press OK
(Windows 7 - Click Start > type CMD in search box then press Enter)
3. cd to the location of your fastboot files folder
4. Relock bootloader - type command:
Code: fastboot oem lock
The phone will then restart into fastboot again showing "RELOCKED"
6. On your pc run the RUU (vista and win7 run as administrator) that you downloaded earlier, follow the steps as prompted and patiently wait for it to finish.
REMEMBER your phone should be charged ABOVE 50% (Full battery is advice) AND if the RUU or restore is INTERRUPTED 4 any reason during restore your
phone will be PERMANENTLY BRICKED..
I have successfuly installed the rom 4.1 from insertcoin i have update the hboot and the right firmware. Thebproblem im facing is the phone keeps rebooting, the installation of the rom ended with no errors... i have full wiped the phone formated the cache... amy idea how to fix the auto reboot? Thanks
armandino said:
I have successfuly installed the rom 4.1 from insertcoin i have update the hboot and the right firmware. Thebproblem im facing is the phone keeps rebooting, the installation of the rom ended with no errors... i have full wiped the phone formated the cache... amy idea how to fix the auto reboot? Thanks
Click to expand...
Click to collapse
It's because you didn't flash the correct boot.img or you didn't full wipe your device.. start over and follow these steps:
1. flash boot.img from rom.zip and then fastboot erase cache
2. Go to recovery and flash this script : http://d-h.st/B2K
3. Flash rom.zip
4. Reboot
PS: From next time, please don't highjack other people's thread by asking questions not related to the topic! If you need further help, open a new topic!
Please help. I am getting
fastboot getvar version-main
version-main:
finished. total time: 0.230s
ladylane100 said:
Please help. I am getting
fastboot getvar version-main
version-main:
finished. total time: 0.230s
Click to expand...
Click to collapse
try with fastboot getvar all
F:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-baseband: 1.46.40.0721
(bootloader) version-cpld: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) product: a11_chl
(bootloader) platform: hTCBmsm8226
(bootloader) cidnum: SPCS_002
(bootloader) battery-status: good
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6a60e19e
(bootloader) gencheckpt: 0
ladylane100 said:
F:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-baseband: 1.46.40.0721
(bootloader) version-cpld: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) product: a11_chl
(bootloader) platform: hTCBmsm8226
(bootloader) cidnum: SPCS_002
(bootloader) battery-status: good
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6a60e19e
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Strange I think you are not with ONE X international we never have this this radio 1.46.40.0721 and for first time I see this CID SPCS_002
Boas pro htc m9 3.35.401.32 qual é o ruu de nougat correto pra instalar pode me ajudar ?
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: removed by me
(bootloader) version-main: 3.36.709.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
!!!!!!!!!!!!!!!!!!I AM ALSO GETTING ERROR 132 WITH HTC M9 RUU DOWNLOADED FROM HTC OFFICIAL SITE...!!!!!!!!!!!!!!!!!!
RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12.exe
Hi All,
I attempted to restore to the stock rom when I ran into this problem where my phone would only boot into recovery mode.
Currently I have S-on and the OS wiped out after a fail attempt at installing the zip file One_5.11.401.10_deodexed.zip
I thought that I might be able to recover it by running one of the RUU exe files but so far I have not been successful. I always got the error 155 returned. Also I am really unsure if this method would work and what RUU file is right for my device? Here is the information I got on my device, may be someone can point out what RUU I might need:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW54321
(bootloader) imei: 1234567890
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
I know that my phone is GSM, unlocked, and work with tmobile. However I am uncertain as to weather it was originally a tmobile phone or an ATT phone, or else.
Thank you for your help.
redmapleleaf said:
Hi All,
I attempted to restore to the stock rom when I ran into this problem where my phone would only boot into recovery mode.
Currently I have S-on and the OS wiped out after a fail attempt at installing the zip file One_5.11.401.10_deodexed.zip
I thought that I might be able to recover it by running one of the RUU exe files but so far I have not been successful. I always got the error 155 returned. Also I am really unsure if this method would work and what RUU file is right for my device? Here is the information I got on my device, may be someone can point out what RUU I might need:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW54321
(bootloader) imei: 1234567890
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
I know that my phone is GSM, unlocked, and work with tmobile. However I am uncertain as to weather it was originally a tmobile phone or an ATT phone, or else.
Thank you for your help.
Click to expand...
Click to collapse
Update: I had an all nighter hellish time trying to recover the seeming bricked phone. At last the following procedure worked for me. I like to post it here just in case someone else got into the same problem. Note that I was using TWPR recovery.
1. I sideloaded superuser.zip
2. I side loaded revone to /sdcard/ directory
3. from the pc:
adb shell
cd /sdcard/
chmod 755 revone
./revone -s 0 -u
exit
4. reboot into fastboot and I got S-OFF
Next I was still having problem installing RUU zip file. The only thing that worked for me was this:
1. I changed the CID to 11111111, (not sure if this is necessary)
2. download Guru Reset M7 3.62.401.1.zip file from htc1guru.com
3. adb sideloaded Guru Reset M7 3.62.401.1.zip to /sdcard/ directory
4. using TWPR install zip to install Guru Reset M7 3.62.401.1.zip
5. the phone reboot and came back working.
At this point I still have S-OFF. The new ROM is of an older version so software update tried to download and install a newer version. However it wasn't able to install. There was a message telling me that it has detected an "variant version of the firmware was installed so update cannot continue". So I still have the following tasks to do before the phone is truly unrooted:
1. change CID from 11111111 back to what it was before
2. update to the latest stock firmware
3. change S-OFF to S-ON
the HTC boot is already in "locked" state so I don't need to lock it again. Still not sure how I can update to the latest stock firmware though. I would appreciate any information in this regard. Thanks.
Update: ok, I finally able to get the software update working without getting the ‘Variant System Version’ message. It worked after I change the CID back to Googl001 from 11111111. I did it with the fastboot command "fastboot oem writecid googl001" .
It seems that the only thing that I need to do now to return it to the original stock product is to change S-OFF to S-ON. Or may be not.
I am still not sure if I got the stock firmware or not though. This is because I saw that the phone has a "SuperSU Installer" app running. This app allow me to root the device. It would be odd if HTC would ship the phone with this app included.
So if you know for sure how I could return this phone to completely stock image, please let me know.
Thank you.
redmapleleaf said:
Update: I had an all nighter hellish time trying to recover the seeming bricked phone. At last the following procedure worked for me. I like to post it here just in case someone else got into the same problem. Note that I was using TWPR recovery.
1. I sideloaded superuser.zip
2. I side loaded revone to /sdcard/ directory
3. from the pc:
adb shell
cd /sdcard/
chmod 755 revone
./revone -s 0 -u
exit
4. reboot into fastboot and I got S-OFF
Next I was still having problem installing RUU zip file. The only thing that worked for me was this:
1. I changed the CID to 11111111, (not sure if this is necessary)
2. download Guru Reset M7 3.62.401.1.zip file from htc1guru.com
3. adb sideloaded Guru Reset M7 3.62.401.1.zip to /sdcard/ directory
4. using TWPR install zip to install Guru Reset M7 3.62.401.1.zip
5. the phone reboot and came back working.
At this point I still have S-OFF. The new ROM is of an older version so software update tried to download and install a newer version. However it wasn't able to install. There was a message telling me that it has detected an "variant version of the firmware was installed so update cannot continue". So I still have the following tasks to do before the phone is truly unrooted:
1. change CID from 11111111 back to what it was before
2. update to the latest stock firmware
3. change S-OFF to S-ON
the HTC boot is already in "locked" state so I don't need to lock it again. Still not sure how I can update to the latest stock firmware though. I would appreciate any information in this regard. Thanks.
Click to expand...
Click to collapse
Update: all problems are fixed, the phone is returned to its stock state completely. Here is what I did.
1. Change the CID to T-MOB010 by using "fastboot oem writecid T-MOB010
2. with CID=T-MOB010 and model number MID=PN0713000 I look up the RUU exe that support those two parameters and download it from htc1guru.com
3. down grade my hboot from 1.54 to 1.44 by flashing a hboot.zip file
4. put the phone in fastboot mode and run the RUU exe . After it is done the phone is back to stock rom.
That's it. Hope these steps could help some sorry soul out there. This HTC root/unroot is NOT FUN at all! If you happen to read this HTC, please make your bootloader idiot proof. Otherwise we will just go with your competitor whoever has a better bootloader.
redmapleleaf said:
Update: ok, I finally able to get the software update working without getting the ‘Variant System Version’ message. It worked after I change the CID back to Googl001 from 11111111. I did it with the fastboot command "fastboot oem writecid googl001" .
It seems that the only thing that I need to do now to return it to the original stock product is to change S-OFF to S-ON. Or may be not.
I am still not sure if I got the stock firmware or not though. This is because I saw that the phone has a "SuperSU Installer" app running. This app allow me to root the device. It would be odd if HTC would ship the phone with this app included.
So if you know for sure how I could return this phone to completely stock image, please let me know.
Thank you.
Click to expand...
Click to collapse
Hello everyone! glad to be a new member of this amazing community! I am a new member with a tough problem, would love if I get ideas on how to solve it.
So After flashing stock unrooted GPe rom as per the most common methods circulating around (changing CID, MID, S-Off, etc), I was thrilled to see the boot splash screen change into google's except that it keeps booting into the bootloader; for some reason I could not get into recovery either (but I flashed TWRP again and it works now)
So as it stands now I have the following:
S-Off
Unlocked
Software status: Official
Working TWRP (which keeps saying NO OS IS INSTALLED)
Unable to mount /data (whatever that means) + "error: closed" when attempting to sideload the RUU roms via ADB
I did not install any firmware or kernels
and whenever I try to boot the OS I get put back in bootloader over and over.
As far as im concerned this phone seems bricked for me, but im also new so I wouldn't know, having said that, I am open for the most radical of options and procedures to get this working.
Thank you all in advance!
Flash it again via adb, the flashing command must be executed twice.
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Megaliths said:
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Click to expand...
Click to collapse
That unrooted GPE was for dual sim? I see you have a dual sim.
Make a screenshot.
Details about the ROM would help.
Do a fastboot getvar all command also.
Actually I don't know if the Rom is for dual sim or not, I figured as long as I get CID and MID right it should fit? pardon my ignorance on the matter. ill post a screenshot as soon as possible!
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Megaliths said:
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Click to expand...
Click to collapse
Delete the IMEI.
OP - Do you want it back to Sense?
EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
Come to think about it now, I'd rather go to stock now if it all possible.
Megaliths said:
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
Click to expand...
Click to collapse
Megaliths said:
Come to think about it now, I'd rather go to stock now if it all possible.
Click to expand...
Click to collapse
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
EddyOS said:
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
Click to expand...
Click to collapse
It never booted up correctly no. I'd love if you can help me go to stock with such a messed up state my phone had gotten into.
We should be able to sort things out, but I'll need to get to a proper PC and get links together
EddyOS said:
We should be able to sort things out, but I'll need to get to a proper PC and get links together
Click to expand...
Click to collapse
Thank you so much!
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
EddyOS said:
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
Click to expand...
Click to collapse
That is amazing thank you, ill try it and get back to you asap.
I have two questions:
Will I still get OTAs even if I don't have the original CID and MID? (I remember the original CID which is J15 but I can't remember the mid).
Also, I am currently on custom recovery and in your guide above I do not see anything about flashing stock recovery, should I do that first?
Thank you again!
The RUU flashes everything stock, so it'll overwrite it all
I'd change the CID back to stock once it's all working again but the MID I'm not sure on so I'll see if I can find out for you
At step 8 I get an error "DNS server not authoritative for zone", how to resolve that?
Nvm I resolved the DNS thin, but now I get error 41 model id check fail. It is probably because of bad MID isn't it?
Thank you again for helping me, I hope it is not much trouble.
Hi All,
I've been a member here for a long time, but now with a new account.
I have a real problem, and I do not know what to do.
Firstly, I am pretty computer literate, but I am lost with phone technology a little. I have a bit of experience flashing ROMS, but I really do not know where to begin.
I bought a HTC ONE M8 for my daughter from eBay (I know... ) and today it seems to have tried an update. This has resulted in bricking my phone. The M8 was (I thought) new, but whatever has happened has screwed things up.
Can someone help me recover from this update failure? I can provide all information from the BOOT screens for you, but as yet, I don't even know what to supply.
Thanks chaps - I know this is the only place that will be able to help as you are all expert.
Simon
Edit: I have installed Android Studio as I have read that this is what I need initially.
Edit: Bootloader Information
*** Software status: Official ***
*** Locked ***
M8_UL PVT SHIP S-OFF
OS-6.12.401.4
So, here are my thoughts. I think that this is a Chinese HTC and it has tried up update to a Europe Marshmellow ROM. Can anyone confirm this might be causing the problem?
Can I "roll-back"?
Ratzz2 said:
Edit: Bootloader Information
*** Software status: Official ***
*** Locked ***
M8_UL PVT SHIP S-OFF
OS-6.12.401.4
So, here are my thoughts. I think that this is a Chinese HTC and it has tried up update to a Europe Marshmellow ROM. Can anyone confirm this might be causing the problem?
Can I "roll-back"?
Click to expand...
Click to collapse
M8_UL is not a Chinese HTC. I guess your problem is root or previously a rooted device and that is the reason the update failed.
To get to know better about your device, post here fastboot getvar all result minus serial & imei no.
Then we'll see what you need to do ... either roll-back or moving forward with a new Marshmallow stock ROM
Hi, thanks for replying.
I see, I didn't know that M8_UL is not a Chinese HTC - shows how much I know about this kind of stuff!
I will look up how to post the fastboot getvar all information, but if I don't get back to this first, I am assuming (from what I have already read) that I can do this via a CMD window? I am not 100% what I need to download to access my HTC, but will look into it now.
Many thanks again - you have given me a glimmer of hope!
Assuming you have a Windows PC ...
What you need is fastboot/adb, install this : http://forum.xda-developers.com/showthread.php?t=2588979
-when install the adb installer, select Y for system-wide and N for drivers
-you can open Command Prompt from any where that you like when it is system-wide.
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
Open a command prompt then type fastboot getvar all
copy the output but delete serial & imei no.
Here we go ...
(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-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.102s
First - you need this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
Since the bootloader is LOCKED, what you can do :
1. Download the RUU zip here : https://www.androidfilehost.com/?fid=24369303960687057
2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
Then follow these :
Rename the RUU zip to RUU.zip (make sure you don't hide the windows extension so you won't make mistake and rename it to RUU.zip.zip)
put your device on bootloader/fastboot mode (as you get the getvar) and connect to PC
Open a command prompt from RUU folder then run below commands:
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
Once complete - fastboot reboot
It should boot, then you run setup .. done.
(Only thing is you will lose all data in internal storage as RUU will give you out of the box state - at least better than a non-working phone)
NOTE : other methods to install RUU zip - http://forum.xda-developers.com/showpost.php?p=67314040&postcount=1749
Thank-you my friend, am downloading now.
Not worried about the data loss - I'd pretty much written the phone off anyway, so loss of data is a very small price to pay.
Will update you once all done.
If possible use PC with USB2.0
I'm on mobile for 6 hours.
If the above fails, I'll give you another method later.
I don't see a reason it would fail.
Thank you buddy - you are indeed, a GOD! :good::good::good::good::good::good:
It has re-booted and is just updating the apps. I will make sure I turn off the 'auto update' option so this won't happen again.
Just out of interest, if I wanted ever to upgrade the OS are there any good resources I could read?
I really appreciate your time in this - I know it's not easy to see a bit of a newbie type "Bricked" in the title!
Thanks again...
Simon
Great :good:
If you don't plan to root the device, there is no need to turn off auto update. It will success for future update when there is one.
Don't think there will be another OS update for M8, this Marshmallow is the last major OS update. If there is any further update, it will be some patches/small update.
Thanks again, you have been a massive help ...
Hi, I am new to this forum and have the same problem. Everything has been working until the step 'htc_fastboot flash zip RUU.zip (to install RUU)'. It tells me that 'htc_fastboot is not recognized as an internal or external command, operable program or batch file. Any assistance on this? I am not stuck with a black screen just written htc But thanks for your help so far...I have a little hope this will be sorted
PavM3 said:
Hi, I am new to this forum and have the same problem. Everything has been working until the step 'htc_fastboot flash zip RUU.zip (to install RUU)'. It tells me that 'htc_fastboot is not recognized as an internal or external command, operable program or batch file. Any assistance on this? I am not stuck with a black screen just written htc But thanks for your help so far...I have a little hope this will be sorted
Click to expand...
Click to collapse
You probably failed to perform one of these steps:
ckpv5 said:
2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
Open a command prompt from RUU folder then run below commands:
Click to expand...
Click to collapse
Note that the part I've highlighted in red is really important. If your command prompt is not opened in the right folder (where htc_fastboot.exe is located) it won't work; even if you did all the other steps correctly.
A shortcut to open CMD prompt in the correct directory, is to open the RUU folder, then with your cursor inside the RUU folder window: Shift-right mouse button click, then select "Open command window here".
I did open the command prompt from within the RUU folder (which I saved on the desktop) so the path is c:\user\user\desktop\RUU hence the command looked like this c:\user\user\desktop\RUU\htc_fastboot flash zip RUU.zip and that is what gave me the error.
I had typed the first two commands ' Fastboot reboot-bootloader' and 'fastboot oem rebootRUU' not from within the RUU folder but from c:\program files\Minimal ADB and Fastboot>. These commands worked, but not now when I try the two from within RUU where I keep getting an error.
What I see is lack of interaction between Minimal ADB and Fastboot (Which I saved under C:\program files) and RUU saved on the desktop. Should I have saved them in the same folder? I have tried moving RUU to the same path as Minimal ADB and Fastboot but that doesn't work either.
Yes, I had I downloaded the files from the links provided and opened that command prompt from within RUU (holding down shift button and right clicking to get 'open command window here'. I have never done this sort of thing before so pardon my lack of knowledge on the basics....I am just determined to have my HTC m8 working again since there is no care centre in Kenya, where I come from. Thanks for the prompt response - wish I noticed it earlier.
redpoint73 said:
You probably failed to perform one of these steps:
Note that the part I've highlighted in red is really important. If your command prompt is not opened in the right folder (where htc_fastboot.exe is located) it won't work; even if you did all the other steps correctly.
A shortcut to open CMD prompt in the correct directory, is to open the RUU folder, then with your cursor inside the RUU folder window: Shift-right mouse button click, then select "Open command window here".
Click to expand...
Click to collapse
PavM3 said:
I did open the command prompt from within the RUU folder (which I saved on the desktop) so the path is c:\user\user\desktop\RUU hence the command looked like this c:\user\user\desktop\RUU\htc_fastboot flash zip RUU.zip and that is what gave me the error.
I had typed the first two commands ' Fastboot reboot-bootloader' and 'fastboot oem rebootRUU' not from within the RUU folder but from c:\program files\Minimal ADB and Fastboot>. These commands worked, but not now when I try the two from within RUU where I keep getting an error.
What I see is lack of interaction between Minimal ADB and Fastboot (Which I saved under C:\program files) and RUU saved on the desktop. Should I have saved them in the same folder? I have tried moving RUU to the same path as Minimal ADB and Fastboot but that doesn't work either.
Click to expand...
Click to collapse
Can you confirm the RUU folder contains a file htc_fastboot.exe? You didn't rename this at all, did you?
Try to copy the RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder, and see if that helps.
Yes. The RUU folder contains the file htc_fastboot.exe as well as RUU.zip (which was renamed to this from the initial long name it had when I downloaded). I had already tried copying both RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder and have just retried and I get the error message 'preprocess_file: Cannot read header len bytes. Also I had tried and just retried copying the RUU folder (as opposed to the two separately)in the Minimal ADB and Fastboot folder and now it says 'Fastload is not recognized as an internal or external command, operable program or batch file.'
redpoint73 said:
Can you confirm the RUU folder contains a file htc_fastboot.exe? You didn't rename this at all, did you?
Try to copy the RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder, and see if that helps.
Click to expand...
Click to collapse
Can you do a screen capture of the RUU folder contents?
And also of the CMD window, when you try the command to flash the RUU zip (from RUU folder - let's concentrate there).
Is this solution applicable to this problem ? -> http://forum.xda-developers.com/htc-one-m8/help/htc-m8-boots-recovery-mode-t3303826
PandaDNB said:
Is this solution applicable to this problem ? -> http://forum.xda-developers.com/htc-one-m8/help/htc-m8-boots-recovery-mode-t3303826
Click to expand...
Click to collapse
If the RUU matches your phone's CID, yes.
Well i can currently see on the phone screen CID-11111111 and the 1.6 gig file(which is the RUU ?) is still downloading.
When i ran the fastboot 1.3.1 i got the same output as the OP.
(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-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Preface
- I don't know what half of the dang rooting terms mean (My own fault before getting into all of this :crying
- Verizon HTC One M8
- Had Unlocked, Root, and S-OFF for 2 years
- Had some version of TWRP recovery
- Trying to get it back to stock recovery and "ROM" (correct term?)
- Connecting phone to OSX for adb/fastboot and could successfully run commands for both.
- fastboot getvar all output (with values I believe to be sensitive starred-out)
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: ***********
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(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: f2489bd1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
What I've tried
- I downloaded an RUU 0P6BIMG.zip from a link on some M8 thread in XDA; couldn't even tell you which one (but I make sure the posts I view are related to Verizon M8). My understanding is that an RUU is an all-in-one tool for stock: stock bootloader, recovery, and ROM. My understanding may or may not be correct.
- I connected my phone to the computer (again, OSX), and I could see my device listed with fastboot devices.
- Following Method 1 on this page, I rebooted into "RUU mode" (term?) with fastboot oem rebootRUU. This showed an all-black screen with a white "htc" in the center.
- Then I flashed the RUU I'd downloaded with fastboot flash zip 0P6BIMG.zip
- This started copying files / doing whatever. Took about 5 minutes and seemed to be working, but ultimately it ended with a "FAILURE: something something" (unfortunately, I didn't capture the exact output).
Where I'm at now
- I believe I'm still in "RUU mode" with failure indicators. It's still an all-black screen with the white "htc" in the center, but now each of the 4 corners of the screen also has a white "warning" symbol (triangle with exclamation mark).
- I can still see my device listed on my computer with fastboot devices, but cannot get any adb commands to work. fastboot getvar all gives the same result as it did prior.
- I attempted to re-flash the RUU file, but it again failed, only within a matter of seconds, not minutes.
- I downloaded an hboot.img (again, from a link on some XDA M8 post), and can successfully run fastboot boot hboot.img. Not sure what it actually does.
- I downloaded a new TWRP image file, twrp-3.0.2-0-m8.img from their site. I am able to successfully flash it with fastboot flash recovery twrp-3.0.2-0-m8.img. I assume this means it's "permanently" on the phone, not just some temporary measure.
- I'm also able to boot into it TWRP fastboot boot twrp-3.0.2-0-m8.img.
Now what?
- I cannot boot into the bootloader (white screen with options; I assume -- possibly incorrectly -- that this is hboot) using fastboot reboot-bootloader.
- Where do I go from here? I feel somewhat relieved that I can boot into TWRP, but not sure what to try now. From what I gather, the "RUU mode" with failure indicators stemmed from the failed RUU flash. So I thought to try to find another RUU file from a different source in case the original that I'd used was corrupted. Other than that, I'm pretty lost.
Please help!
Well, I fixed it somehow. I actually found another RUU file and tried flashing it. It initially failed with an error of "failed (remote 90 hboot pre-update please flush image again immediately)". I'm not sure if it actually meant to say "flash" instead of "flush", but I ran the same fastboot command again to see what would happen, and it worked. Perhaps that's what I needed to do the first time.
Anyway, the phone boots up to stock Android 4.4.2. I can boot into the bootloader if necessary, and I'm pretty sure it has custom recovery (if I boot into recovery, I don't get TWRP. It just has a completely black screen with an image of the phone that has a red warning icon on it).
So I don't know if I was actually on the right track in the first place, or if I just happened upon some dumb luck. But anyway it's working.