Can't revert HTC One M8 to stock - One (M8) Q&A, Help & Troubleshooting

I received an unlocked HTC One M8 (US, works on AT&T, not Harmon Kardon), factory reset, never been modded. Because it ran Android 6.x, I was concerned that it wasn't as secure as it could be, so I researched how to install the newest Android possible. I found many articles on these forums, guides from 2014 all the way to 2016. I didn't (and still don't) know enough to tell the difference between a good tutorial and a bad/outdated one. I saw that some tutorials were edited to reflect new mods, but now that I have read even more, I suspect that even those updated ones are now obsolete.
My problem is that I installed Resurrection Remix with v7.1.2, along with pico Open Gapps, and it won't let me install several apps like Chrome or even YouTube. I have decided that I don't want a newer ROM and I would rather just revert to stock. I have been attempting to revert to stock for the last three or four days, and I have spent many hours researching and reading (mostly this site...go figure), but so far I have not accomplished anything.
Current information about the phone: I did not make a backup (I've had little success doing this over the years on Android phones), I unlocked the bootloader with the HTC unlock code.bin file, the phone has S-ON and has not been rooted. In fact, I've tried SuperSU and Sunshine and neither worked. I have TWRP 2.7.1.0 installed. I have drivers from HTC Sync, but I also installed the Android Studio, along with some utilities that come with it. I have attempted the RUU from HTC (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4) and it always says that there was an error.
I have attempted several times to change the CID, but only because a tutorial told me to. I assume that it was changed when I installed the Remix mod. I have no idea what it should be. I have attempted to install firmware as well, both with the adb method and by copying it to the SD card and renaming it for bootloader, but both options fail. The adb method fails with...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
...and the SD card method thinks for a bit, then says "press power to reboot" in the same type of text as the bootloader text.
I am only a little familiar with adb and fastboot, so please, be gentle. If you list commands, I will use them without even thinking, like how Ron Burgandy reads everything on the teleprompter.
Please help.
Here's the getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Did I post in the wrong forum? Any help would be greatly appreciated. Thanks!

speedee39 said:
Did I post in the wrong forum? Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Hi,
no you did not post in the wrong forum. This section is not that active but there are still a handful of people visiting and trying to help.
You've posted plenty of info - which is good. First of all, you can't change the cid if you're s-on. You need to be s-off. Changing the cid is not really necessary unless you want to convert your carrier device into the dev edition or the Google Play edition M8. What cid were you trying? Was changing the cid successful? In that current state it shouldn't.
Speaking of the Google Play edition. You tried to revert to sense stock, according to the ruu you mentioned. The thing is your getvar result shows that your mid and cid directs towards a Google Play edition device. If you want to go on sense there are a few steps you have to do before you can (repartitioning system for example as the storage size is bigger on sense than on GPe).
Another thing is, the TWRP recovery you used is way too old for the firmware. The latest one can be found on twrp.me
Can you tell us how big your system partition is? If it's only over 1GB you certainly have a GPe device - in fact getvar says that as well.

maultasche said:
You've posted plenty of info - which is good. First of all, you can't change the cid if you're s-on. You need to be s-off. Changing the cid is not really necessary unless you want to convert your carrier device into the dev edition or the Google Play edition M8. What cid were you trying? Was changing the cid successful? In that current state it shouldn't.
Click to expand...
Click to collapse
The guide I found for reverting to stock said to change to the super CID (fastboot oem writecid 11111111). I only did that because I thought that it was the "right way" to do this. But if the CID can't be changed unless the phone is s-off, then it must still be stock, because I doubt that I've ever achieved s-off while flashing a different ROM.
maultasche said:
Speaking of the Google Play edition. You tried to revert to sense stock, according to the ruu you mentioned. The thing is your getvar result shows that your mid and cid directs towards a Google Play edition device. If you want to go on sense there are a few steps you have to do before you can (repartitioning system for example as the storage size is bigger on sense than on GPe).
Click to expand...
Click to collapse
Yes, I attempted the Sense stock because the tutorial told me to and also because that's what is listed on HTC's website. I don't want to go to Sense, just thought that I was supposed to. So you're saying that the phone is a Google Play Edition? I'll need to look that up.
maultasche said:
Another thing is, the TWRP recovery you used is way too old for the firmware. The latest one can be found on twrp.me
Click to expand...
Click to collapse
Thank you for that, I didn't know. I'll get it. One question that I've never found the answer to is, if I installed TWRP to change the ROM, what is the stock recovery image? Or, is it bad to simply leave TWRP installed? I have no plans to sell the phone.
maultasche said:
Can you tell us how big your system partition is? If it's only over 1GB you certainly have a GPe device - in fact getvar says that as well.
Click to expand...
Click to collapse
I think I did this correctly. Here's what I found through the shell:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p45 1032088 853196 178892 83% /system
Once I started looking this up, I found a post on XDA about GPe and different partition sizes. I'll check for GPe ROMs now. Do I need any other files besides that and the updated TWRP? Is the order to install a newer TWRP, then flash the GPe ROM, and then relock the bootloader?
I noticed that the bootloader has a persistent message about it being relocked and **WARNING**. Is there a way to clear the warning flag? One of the tutorials that I was following listed several shell commands to do this. I'm going to list them, so let me know if that is the way to clear the flag.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot-bootloader
Thanks for your help.

You indeed have a GPe device. If you want to go back to GPe this thread has all your answers, links and ruu's
https://forum.xda-developers.com/showthread.php?t=2708589
Since your device is a GPe device there is no need to change cid, mid etc. - with s-on you can't change them anyways. Just grab the latest GPe ruu and follow flashing instructions.
Stock recovery is only needed for ota-updates. On sense the updates would fail as this particular recovery is missing. I assume on GPe that would happen as well. It's up to you if you use twrp or stock recovery. GPe won't get updates anymore, same as sense.
I recommend not to mess with this stuff in bootloader. Once you go back to stock (ruu etc), it should fix itself. Besides that to temper with it you need to be s-off anyway.

maultasche said:
You indeed have a GPe device. If you want to go back to GPe this thread has all your answers, links and ruu's
https://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
Yes, I had found that exact thread earlier today, thanks to you, and I was just replying to tell you that I have successfully reverted my phone back to stock.
In the spirit of contribution to the site that has helped a novice such as me, I want to share the steps I took so that others might be helped.
The phone, as mentioned earlier, is an HTC One M8 Google Play Edition (Gpe), was s-on, not rooted, bootloader unlocked. I had an old version of TWRP and Resurrection Remix ROM using Android 7.1.2.
Prerequisites
1. Stock GPe ROM: https://androidfilehost.com/?fid=817550096634750828
2. TWRP 3.1.1-0-m8: https://dl.twrp.me/m8/twrp-3.1.1-0-m8.img.html
3. Backup account fix (linked in aforementioned thread): https://www.androidfilehost.com/?fid=24686680535467942
4. ADB and fastboot
5. Unlocked bootloader
**This assumes that you have a Windows computer. I used Windows 10 v1709**
Steps
1. Copy the ROM and TWRP files to the same folder in which fastboot and ADB are located. This makes it easier to run commands.
2. (There might be another way to do this one, but I don't know it) Copy the backup account fix file "MRA58K.H15_backup-account-fix.zip" to a micro SD card and put it in the phone.
3. Open a command prompt or PowerShell window in the folder that contains ADB and fastboot by right-clicking + Shift in an open area and selecting "Open PowerShell/Command Prompt window here."
4. In the PowerShell/Command Prompt window, type "fastboot flash recovery twrp-3.1.1-0-m8.img" and press Enter to install TWRP
5. Reboot into the bootloader and choose "fastboot," then choose "recovery"
6. In TWRP, browse to ADB sideload and then "swipe to start sideload."
7. In your PowerShell/Command Prompt window, type "adb sideload HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H15_AROMA-Installer-v6-020817.zip" and press Enter to start the installation
8. On the phone's screen, choose the top option, which should be the unrooted, completely stock installation.
9. On my machine, the PowerShell/Command Prompt window showed progress up to 41% and then it finished successfully.
10. After that, do not reboot, but go back into the main TWRP menu and go to Install. Browse to the MRA58K.H15_backup-account-fix.zip file that you previously saved on your SD card and install it.
11. Once that is installed, reboot the phone. My phone took between 5 and 10 minutes to boot the first time.
12. (Optional) I wanted to have a completely reverted phone, so I locked the bootloader again by rebooting the phone into the bootlader and typing "fastboot oem lock" in the PowerShell/Command Prompt window. It then said "relocked" but no warnings or errors.
I hope this helps somebody. All credit goes to maultasche for pointing me in the right direction and to graffixnyc for the other thread.

Related

Can't Flash TWRP Recovery

Self-admitted newb here. Been reading up on FAQs and instructions on how to Root my new device and am eager to learn more to eventually fully optimize. I was able to unlock, but when attempting to flash TWRP recovery, it'll just hang forever with this message:
"sending 'recovery' (11976 KB)...".
I confirmed checksums of files downloaded, USB Debugging is flagged, Fastboot is deselected, updated the HTC drivers on my PC, and my S/N is acknowledged with the 'fastboot devices' command. I even did a Factory Reset from bootload screen, as this is a new device with no data on it yet.
Any helpful suggestions on determining next steps would be greatly appreciated!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(bootloader) version-misc: PVT SHIP S-OFF
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You need 2.7 series..
flyera343 said:
You need 2.7 series..
Click to expand...
Click to collapse
Agreed, and I was mistakenly attempting to flash twrp-2.8.6.1-m8.img initially . I'm sorry I failed to mention that in the original post and yes, I also did erase cache several times. Re-attempting to flash twrp-2.7.0.1-m8.img is when the 'sending recovery' hang issue comes up.
bump
pill_popper said:
(bootloader) version-main: 1.54.401.109
(bootloader) modelid: 0P6B12000
(bootloader) security: off
Click to expand...
Click to collapse
You have a very old software version. Since your device is S-Off, I suggest :
1. change the MID 0P6B12000 to 0P6B10000
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2708581
2. run 4.16.401.10 RUU.exe - https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/edit?pli=1
RUU will flash your entire phone back to stock including recovery
(as your device is S-Off, no need to lock/relock bootloader)
3. Now you can install the latest TWRP recovery and do whatever you want to do
Thank you for your kind words. I appreciate it. Will follow up on the points covered in your post and report back.
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery. This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
ckpv5 said:
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery.
Click to expand...
Click to collapse
Correct, sorry if I wasn't being clear about that. I've Unlocked, but not yet rooted hence, the attempt to send TWRP. I haven't yet taken next steps though.
ckpv5 said:
This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
Click to expand...
Click to collapse
More reading! :cyclops:
**Updated**
So I've tried using Minimal ADB tool as well. Now instead of hanging, I'm eliciting errors.
target reported max download size of 1830711296 bytes
sending 'recovery' (11976 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.023s
I'm running as Administrator in Windows 7, I can hear the PC recognize the phone when I plug it in the USB and I've also confirmed multiple times the 'fastboot devices' command recognizes my phone.
If this might be a USB related issue, how would I go about investigating in that direction? Not sure what is preventing me from simply flashing a TWRP recovery. Any thoughts on this are welcome, thank you.
*bumpity bump*
So I can see 'FASTBOOT USB' in bootloader mode, and the fastboot devices command returns my S/N, but still the adb devices command just returns the message 'list of devices' and nothing else. Attempting to flash TWRP recovery still fails. I've uninstalled all HTC stuff and manually updated the driver to 'MTP USB Device' via Device Manager per redpoint73's advice. Before I give up on this PC, are there any additional steps I can take? Any guidance from you guys would be appreciated, thanks!
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
ckpv5 said:
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
Click to expand...
Click to collapse
I guess what most on here would consider to be trivial are to me revelations. Thank you for your response and now I see my device S/N is recognized after running the adb devices command when the phone is running in 'normal' mode! Yes, it is properly working but sadly, all four USB ports on the PC are USB 3.0 I'll read up on your suggestions and reply with questions at that point before taking action. Again with the reading! :cyclops: My concerns here are if stock recovery would continue to work if I go down either of those paths and how the phone is supposed to respond if it's not responding when attempting to flash TWRP. Thanks again for your inputs, I appreciate it!
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
ckpv5 said:
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
Click to expand...
Click to collapse
If I wanted to attempt #3, please point me to the correct version as it wasn't clear to me what file to choose here:
http://forum.xda-developers.com/showthread.php?t=2701376
Thanks!
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
ckpv5 said:
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
Click to expand...
Click to collapse
The whole point of this exercise is to gain root so that yes, I can have the option of flashing a custom ROM. I noticed in the executable's file name you referenced model M8_UL_L50, but mine is M8_UL_CA. I also noticed its radio version differs from the one listed in my getvar all file. *edit* I've now realized this file is straight from HTC.
Since my current version is so old, is it still OK to run this to update to the latest version rather than updating to an intermediate version before updating to the latest version? Just wanted to confirm before taking any unnecessary action. Thank you again for your patience and the helpful information!
M8_UL - M8 with LTE
L50 - Android L 5.0
CA - US region
Radio version different because yours is old/lower version and this is newer/latest version and you're going to update hboot, radio and many more with this RUU. You need the update in order to install custom ROM as I mentioned before most custom ROMs work only on hboot 3.19.0000
You have S-Off device, you don't need intermediate version ... and most important RUU doesn't need intermediate version because RUU will wipe clean your device and replace all images with those come with it. (So make a backup of your important files to PC)

Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?

Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?
Hi
As the title says I completely erased my phone. The file structure seems to be there still from a fairly old ARHD 4.4.4 install. I did a Nandroid before doing this and it is backed up on my computer. Because it is an older (KK) ROM I'm on TWRP 2.8.1.0. I've tried to do
1 ADB pushed a version of that over to the device and tried to install with TWRP but it wouldn't install.
2 an ADB sideload of the latest GPE ("blues") by lyapota, but it didn't install. Does this take a super long time, as I'm trying it a second time. First time I cancelled after about 10 mins of no activity.
So, I'm in a bit deep here. At this point I'm even afraid to unplug the phone from the computer as I fear I'll never get it to boot again. Can I still access the phone by turning it on via booting into download mode/recovery?
If generous, can you walk me through step by step? Otherwise, is there a good guide that will step by step me through the process? A 2014 version of this thread referred the poor guy to the FAQ, but it doesn't cover this case.
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
ckpv5 said:
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B11000
(bootloader) cidnum: HTC__621
(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!
finished. total time: 0.050s
Should I start looking for a stock kitkat ROM or RUU?
Is there a thread you know of, or a good google search term I can start my learning on?
And most importantly, will anything I do ever eliminate my s-off?
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
ckpv5 said:
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Sounds OK, will that install a less effective radio, or are radios not affected? I have S-off for exactly this kind of this instance, but i guess it could be construed as the cause too.... The main reason is getting bloat off the ROM though.
Should be fine. As far as I can remember, both TWN and EU have same radio.
The different is slightly on rcdata... but that another story, won't affect anything at where you are now.
Being a S-Off device you can change the OS version at any time that like.
Weird, I downloaded minimal adb fastboot, and I can fastboot devices and get my serial, but adb devices returns device null. Am I missing something? The phone is in bootloader mode. Should I be in TWRP?
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how? Every time I reboot TWRP it asks me if I want SU, but the process hangs.
Can the HTC utility restore a phone in this state, and not lose s-off? I put the external SD in the phone, with the nandroid I did today, and am trying to transfer it into the bare file system, where should I put it. Why can't TWRP just see the nandroid on the external? WIll the nandroid be of any value to me at this point?
When I try to do this:
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
it tells me "cannot copy system.ext4.win000" "it's file size is larger than the device limit"
So do I need to re partition somehow? How would I do that? How can I find, and post, what the filesystem layout is now if more info is needed?
I have the TWRP backup on the external SD, but restore won't see it either.
Or what about the Hasson2000 toolkit to push an RUU to it?
Sorry guys, I still need help. I try to do adb shell, but can't seem to get root (su) . Because of this I am afraid of moving forward. I have changed my CID to GOOGL001 using HASOON2000's toolkit as I've decided I might as well go full goog since I'm at this point. I think my MID 0P6B11000 is OK, as it's mentioned in graffixnyc/Enewman17's GPE thread, correct? I've downloaded the MM H11 and it's waiting, but I'm afraid to move forward with the root problem better explained in the post above. Am I overly worried?
downwiththebanksters said:
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how?
Click to expand...
Click to collapse
No .. while in TWRP you just run adb shell, no need SU because while in TWRP it's already rooted ..
so
adb shell
~ # <[6n
then paste in the code to change MID then type exit, exit
If you want to run the EU WWE RUU that I linked above, you also need to change the CID .. I suggest a SuperCID 11111111 then later you can run anything that you like as long has you have the correct MID for the RUU that you're going to install.
Now .. since you changed the CID to Google CID and intended to install a GPE RUU .. read through the thread that you linked .. can't help much .. maybe someone else will help you for the GPE conversion.
Still I suggest, instead of running a Google CID ... change it to SuperCID so you don't have to every time change the CID when you decide to run other RUU.
EDIT :
I just remember something .. there is a RUU zip for Taiwan HTC__621 that you can use (but you need to put back the CID to HTC__621 (the original CID) or make it SuperCID 11111111
The steps are the same as I posted before. You need to use htc_fastboot.exe and follow those fastboot commands to install a RUU zip.
Or if you have a microSD card, you can rename the RUU zip to 0P6BIMG.zip and put it on your microsd. On fastboot, select hboot .. it will scan the 0P6BIMG.zip and ask whether you want to update, volume up to update. Once completed, remove this 0P6BIMG.zip from your microsd.
Later you can do all the OTA to the latest.
Download 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 here : http://androidruu.com/?developer=M8
Well as I said above I decided to try the full GPE RUU, so I followed these instructions. I used hasoon2000's toolkit to change the CID, my MID was compatible with the GPE. I then fastboot bootloader and:
Method 1
*ADB / Fastboot*
First, make sure you have the path to adb and fastboot setup in your system environment variables
When you open a command prompt, open it in the folder the zip is in. Hold shift, Left Mouse click, open command prompt here.
1. Rename the RUU.zip to something short and easy like RUU.zip
2. adb reboot bootloader "press enter" Wait till phone reboots into fastboot
3. fastboot oem rebootRUU "press enter" Wait till the phone is in RUU mode (black screen with HTC logo)
4. fastboot flash zip RUU.zip "press enter"
*You will get the following message: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
*RUU mode will reboot,
*Now run the same command again,
5. fastboot flash zip RUU.zip "press enter"
6. fastboot reboot-bootloader "press enter"
7. Select hboot, Do a factory reset in recovery. To enter the recovery menu when greeted by the Android with an exclamation, Hold Power button and click Volume UP.
8. Done, reboot system.
It took a long time for the ROM to install, but I was happy to see the Google splash screen rolling along.
Overall a bit scary as I worried about potential partition issues, but I could see the naked filesystem poking around in TWRP, and knew it wasn't a brick because I got the HTC splash screen and TWRP. I'm not totally in love with the GPE right now, as I miss the Nova launcher layout (fixable, installing now), and I can't toggle data with a homescreen widget (unfixable, now 3 clicks with dropdown...first world problems!!). Bottom line, be careful with what you wipe in TWRP! Thanks to you ckpv too!

Htc one m8 unable to find correct firmware and rom

THANKS IN ADVANCE
hi being long period user of android phone still facing many problems to get OTA update on my phone. I was excited about my phone HTC one M8 and wanted to install OTA update there was not any software update option in my phone and than i ran for internet search spent regular three days to find correct firmware get back to stock which totally different from samsung phones. I gone through all the the threads and option provided on internet tried to get back to stock. I need help of professional
who can sort out this problem. HTC PHONE IS NOW BOOTLOADER LOCKED S-OFF KITKAT INSTALLED SUPERCID software number 1.54.651.8
PLEASE GIVE LINK TO GET STOCK RECOVERY AND HOW TO INSTALL OR FLASH IT.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.05.20.0321_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ***********
(bootloader) imei: ***********
(bootloader) imei2: Not Support
(bootloader) meid: **************
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
http://forum.xda-developers.com/showthread.php?t=2729173
http://forum.xda-developers.com/show....php?t=2729173
Click to expand...
Click to collapse
THANKS ckpv5 I WILL GIVE YOU WHOLE INFO. ABOUT MY PROBLEM
As i changed my MID and flashed wrong zip of HTC europe rom on HTC SPRINT which drained everything including my custom TWRP. I was totally new to HTC totally messed up everything. its been more than five days my phone had stuck at hboot screen i know you guy are genius can save my hundard of BUCKs as its new phone bought 15 days ago it was rooted.
I WAS TRYING TO INSTALL SPRINT FIRMWARE TOO BECAUSE I HAD ALREADY FLASHED THAT FIRMWARE ACCORDING TO EUROPE ROM. NOW THE PROBLEM IS THAT I AM UNABLE TO FLASH FIRMWARE DUE TO CHANGED MID (talked earlier) CANNOT UNDERSTAND WHAT TO DO.
Do you still have TWRP installed ?
If no, install one
If yes,
Boot to TWRP recovery, select mount - system
open command prompt from your adb/fastboot folder then run command
adb shell
then this code
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Make sure you copy the code, not write it yourself
then exit
then select reboot - bootloader
then run
fastboot getvar mid
you should see your mid now read 0P6B70000
(you don't need "su" command)
Now you can install Sprint RUU - http://www.htc.com/us/support/htc-one-m8-sprint/news/
or check those in Sprint section that I linked above
Note : You will get your device running again but you maybe lost the 3G/4G and only can get 2G. Reason is you flashed wrong radio meant for GSM on your CDMA, this usually brick the radio. If you're lucky enough, this is not happening.
ckpv5 said:
Do you still have TWRP installed ?
If no, install one
If yes,
Boot to TWRP recovery, select mount - system
open command prompt from your adb/fastboot folder then run command
adb shell
then this code
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Make sure you copy the code, not write it yourself
then exit
then select reboot - bootloader
then run
fastboot getvar mid
you should see your mid now read 0P6B70000
(you don't need "su" command)
Now you can install Sprint RUU - http://www.htc.com/us/support/htc-one-m8-sprint/news/
or check those in Sprint section that I linked above
Note : You will get your device running again but you maybe lost the 3G/4G and only can get 2G. Reason is you flashed wrong radio meant for GSM on your CDMA, this usually brick the radio. If you're lucky enough, this is not happening.
Click to expand...
Click to collapse
this is what now comes up when i try to flash TWRP
C:\Users\USER\Desktop\fastboot_adb\fastboot_adb>fastboot flash recovery "twrp-2.8.5.0-m8_whl.img."
target reported max download size of 1826418688 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.501s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.516s
i'm brain dead nothing works SUGGEST SOMETHING
EVEN UNABLE TO UNLOCK BOOTLOADER NOW
You can't fastboot flash recovery while the bootloader is locked/relocked.
You need a microSD.
Download the 0P6BIMG.zip that I posted here : http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
No need to worry what OS it is written for now, it will get fixed when you install RUU.
Place the 0P6BIMG.zip on root of microSD (means not in any folder)
Then put your phone on hboot, it will scan the file. Volume up to update (install). Once done, it will ask you to reboot but you know that your device is bootlooping, just put the device on bootloader (remove the microSD to delete the 0P6BIMG.zip)
Now you can boot to TWRP recovery and do the rest as described above.
ckpv5 said:
You can't fastboot flash recovery while the bootloader is locked/relocked.
You need a microSD.
Download the 0P6BIMG.zip that I posted here : http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
No need to worry what OS it is written for now, it will get fixed when you install RUU.
Place the 0P6BIMG.zip on root of microSD (means not in any folder)
Then put your phone on hboot, it will scan the file. Volume up to update (install). Once done, it will ask you to reboot but you know that your device is bootlooping, just put the device on bootloader (remove the microSD to delete the 0P6BIMG.zip)
Now you can boot to TWRP recovery and do the rest as described above.
Click to expand...
Click to collapse
:fingers-crossed: Thanks man you are really great now these are the outcomes
C:\Users\USER\Desktop\fastboot_adb\fastboot_adb>fastboot getvar mid
mid: 0P6B70000
finished. total time: -0.000s
Now it want follow your command give me further steps. Thanks Again
Moreover, i made mistake that i also had flashed firmware file according to htc europe rom. Now which one should choose.
Doesn't matter about the firmware now .. just install RUU.
That was the guide written above.
1. Change MID
2. Install RUU exe that is linked above.
Make sure you have windows PC with usb2.0 and the latest htc usb drivers are installed.
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.
Or you can use RUU zip
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip that you can get in Sprint thread.
Rename it to 0P6BIMG.zip and install the same way as you installed TWRP above (microSD method)
ckpv5 said:
Doesn't matter about the firmware now .. just install RUU.
That was the guide written above.
1. Change MID
2. Install RUU
Make sure you have windows PC with usb2.0 and the latest htc usb drivers are installed.
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.
Click to expand...
Click to collapse
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU
sorry it could be silly but which one is right one in both of it or give the link to particular one because i am afraid don't mess anything again. Thanks man
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
What's this RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4 got do with your device ?
All my links are referred to RUU 6.20.651.3 on post #2, #4 & #8
ckpv5 said:
What's this RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4 got do with your device ?
All my links are referred to 6.20.651.3 on post #2, #4 & #8
Click to expand...
Click to collapse
Sorry bro i sent you by mistake i got it i will flash 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU file through HBOOT and i will post the outcome whatever there will be but you are great. You saved me. Thanks a lot bro
It says that Device halted due large image update file
What do you suggest now.
Then install 6.20.651.3 Signed Full Firmware first, see whether it can be installed.
Rename it to 0P6BIMG.zip and install it microSD method. If successful then install RUU.
(This is the problem .. I don't have Sprint device, unable to test)
ckpv5 said:
Then install 6.20.651.3 Signed Full Firmware first, see whether it can be installed.
Rename it to 0P6BIMG.zip and install it microSD method. If successful then install RUU.
(This is the problem .. I don't have Sprint device, unable to test)
Click to expand...
Click to collapse
There is another problem occured i flashed signed firmware now phone only shows the HTC logo and unable to restart what should do now???
Was the firmware installation successful ? This is important.
When you reboot, there is no OS, you need to put back to bootloader then install RUU.
(Same way after you installed TWRP before)
I think this is easier.. instead of going to Marsmallow, install the lollipop first just to get your phone up & running.
Install this 0P6BIMG_Sprint_HTC_One_M8_4.25.651.18_RUU.zip, for this you don't need to install firmware.
Once successful, then you can try again to install Marshmallow 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip but
you need to install 6.20.651.3 Firmware first.
ckpv5 said:
Was the firmware installation successful ? This is important.
When you reboot, there is no OS, you need to put back to bootloader then install RUU.
(Same way after you installed TWRP before)
I think this is easier.. instead of going to Marsmallow, install the lollipop first just to get your phone up & running.
Install this 0P6BIMG_Sprint_HTC_One_M8_4.25.651.18_RUU.zip, for this you don't need to install firmware.
Once successful, then you can try again to install Marshmallow 0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip but
you need to install 6.20.651.3 Firmware first.
Click to expand...
Click to collapse
Thanks man we made it IT IS FINALLY WORKING you are really great Man this info will HELP SOMEONE AS WELL..
Great ..
Now I can sleep well.. it's 1.00 am here... good night
ckpv5 said:
Great ..
Now I can sleep well.. it's 1.00 am here... good night
Click to expand...
Click to collapse
Thanks you spent much time to solve my problem rest of the phone is working fine and it shows one error of something that attached a screenshot also attached screenshot of networks please tell there is 3g and 4g Thank you great man
There is also portable wifi hotspot is missed. Need help where to find it.
karamghumaan said:
There is also portable wifi hotspot is missed. Need help where to find it.
Click to expand...
Click to collapse
Did you find it? And how did you changed WiFi and signal status bar icon? Which htc theme did you use?
Sent from my HTC One_M8 using Tapatalk
Zile995 said:
Did you find it? And how did you changed WiFi and signal status bar icon? Which htc theme did you use?
Click to expand...
Click to collapse
Hello mate No it is till missing and official theme and i also want change that icon but i couldn't find that option too. Are you able to give me that solution how i can do it. More there is activating device window at start up how can i remove that?
karamghumaan said:
Thanks you spent much time to solve my problem rest of the phone is working fine and it shows one error of something that attached a screenshot also attached screenshot of networks please tell there is 3g and 4g Thank you great man
Click to expand...
Click to collapse
SO you have no cell data access?
What bands does your carrier uses for 3G and LTE (what band for each of those - they are 2 different things).
karamghumaan said:
There is also portable wifi hotspot is missed. Need help where to find it.
Click to expand...
Click to collapse
Hotspot is locked out on most US carrier versions. If you don't see Hotspot as an available "tile" in the notification quick settings, and no Hotspot widget, than the feature has been disabled on your stock ROM.
Easiest way to enable Hotspot is with the proper custom ROM (supports Sprint version M8).

Which RUU can i flash?

So, I had a marshmallow update on my phone, and later i converted into GPE, but didn't like it. Went back to Sense, but it just doesn't feel as good as before. One day, the battery died, and when i tried turning it on, it would give me all sorts of errors. This never happened while i was on marshmallow before conversion to GPE. Had to reset it from the recovery. I think it hasn't returned to Sense properly.
As i am S-Off, i was thinking of flashing it with a RUU which is compatible with my device. Please suggest me which is compatible.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21450002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.708.1
(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: 0P6B63000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
Based on your MID, looks like you're on a GSM M8? I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
I have read here that flashing carrier RUU can brick the device radio for good. So, this is why I wanted to confirm.
cytherian said:
I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
Click to expand...
Click to collapse
HTC does not post the RUU for his version on HTC Dev.com (many versions are not posted there)
OP's version doesn't have a carrier forum sub-section.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
xexux said:
(bootloader) version-main: 6.16.708.1
Click to expand...
Click to collapse
I don't know if there is an RUU for this version number.
One alternative, is to restore the TWRP backup 6.16.708.1 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 09:42 AM ---------- Previous post was at 09:38 AM ----------
xexux said:
Went back to Sense, but it just doesn't feel as good as before.
I think it hasn't returned to Sense properly.
Click to expand...
Click to collapse
How exactly did you go back to Sense?
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
xexux said:
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Good to hear that it worked out and thanks for posting. :good:
cytherian said:
Good to hear that it worked out and thanks for posting. :good:
Click to expand...
Click to collapse
This is how I got Sense back, and after that, I started experiencing bugs with M8 as explained in my first post.
xexux said:
So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
redpoint73 said:
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
Click to expand...
Click to collapse
I restored it with the latest TWRP backup for my model. About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
xexux said:
I restored it with the latest TWRP backup for my model.
Click to expand...
Click to collapse
What version number exactly? Perhaps you still have the files on your computer, and can look?
I've seen a number of times, folks say and think they restored the right version for their model, and once we ask for version numbers, we see they actually got it wrong.
xexux said:
About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Click to expand...
Click to collapse
I can see it too. But doyou actually remember manually download and flash the firmware in RUU mode?
Did you convert to GPE using the RUU?
xexux said:
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
Click to expand...
Click to collapse
It's possible. But flashing another region's RUU will also change the radio baseband, and therefore changes the specific bands supported. It may have undesirable results (not support the 3G or LTE band or bands used by your local carrier).
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Bukss said:
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Click to expand...
Click to collapse
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
c:\miniadb_m7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 99000499834418
(bootloader) product: m8_wlv
(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: RUU
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
Abnova said:
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B12000
Click to expand...
Click to collapse
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
redpoint73 said:
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
Click to expand...
Click to collapse
Yeah I realised how big of a mess I was in when I got it back. Anyway
1.)On further investigation it seems like the the phone is in a wierd RUU mode. So it still can interface with the laptop through fastboot. Like I said earlier, trying to reboot to bootloader brings you to the same black screen with the silver Logo (see attached). When the phone is plugged in to the laptop or switches to the HTC silver Logo screen however when it's unplugged, it goes to a wierd bootloader like screen but black and only has the option for RUU. ( See attached)
2.) I took it to them to replace the battery because . The phone would switch off even at 100% battery. It only worked when it stayed plugged in , like a PC. I'm guessing the repair guys saw I had modified the software (I was running Dirty Unicorns, Android 7.1.2, Latest TWRP with a relocked Bootloader, S-Off) and had thought the problem actually had to do with the software. I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Anyway I hope this information helps. Thanks for your help.
Abnova said:
I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Click to expand...
Click to collapse
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Abnova said:
1.)On further investigation it seems like the the phone is in a wierd RUU mode.
Click to expand...
Click to collapse
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Thanks for your contribution, will definitely try tomorrow
redpoint73 said:
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Click to expand...
Click to collapse
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Abnova said:
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Click to expand...
Click to collapse
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
redpoint73 said:
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
Click to expand...
Click to collapse
I tried that, it would flash then refuse to reboot to the recovery. I've tried so many things but none of them worked. My only hope is if someone edited the Android.txt file inside the Rom Zip so that the model ID is the same as that of my corrupt phone. That way it'll flash and hopefully fix it. I've tried myself but everytime I tried to edit it says the zip/archive is corrupt on WinRAR. I don't know whether it's a problem with my laptop or if it's a complication related to the rom.zip. I've downloaded it again but it still does the same thing. So basically I'm stuck because there is no way I can change the MID. This probably means the phone is bricked.

Unable to install/enter twrp recovery

I purchased a HTC M8 dual sim phone. I unlocked the bootloader and flashed the latest twrp on it, all seemed fine. However when rebooting to recovery it's stuck at "entering recovery...". There's tons of threads about that suggesting various version of twrp, so far I have tried (erasing cache in between):
twrp-2.7.1.0-m8.img
twrp-2.8.0.0-m8.img
twrp-2.8.1.0-m8.img
twrp-2.8.3.0-m8.img
twrp-2.8.7.0-m8.img
twrp-3.0.0-1-m8.img
twrp-3.1.1-0-m8.img
twrp-3.2.3-1-m8.img
twrp-3.3.0-0-m8.img
twrp-3.3.1-0-m8.img
However I always get either stuck at entering recovery or go directly back to bootloader.
So I wanted to do OTA updates first, but HTC doesn't allow me to anymore. So I installed stock recovery from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 Still couldn't install the OTA. So i (probably stupidly followed these instructions to get S-ON: https://forum.xda-developers.com/ve...w-to-to-stock-unroot-lock-bootloader-t3505783
The getvar all reports:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.22.30306251.27G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) version-misc: PVT SHIP S-ON
[...]
(bootloader) meid: A1000037D21505
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B41000
(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: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
In some old threads about dual sim "special" twrp imgs like TWRP_Recovery_2.8.0.5_M8_CPTB.img are recommended, but the download links are broken.
So in the end I'd just like to get twrp installed, from there I know my way around (I'd have tried lineage first). Any pointers/ideas what to try next to achieve that?
imsodin said:
Still couldn't install the OTA. So i (probably stupidly followed these instructions to get S-ON: https://forum.xda-developers.com/ve...w-to-to-stock-unroot-lock-bootloader-t3505783
Click to expand...
Click to collapse
S-off does not limit OTA. So maybe not the best idea to make it s-on again. On the other hand, s-on will not limit installation of TWRP, custom ROMs, etc.
Also, if the device was made s-off by sunshine, you should be able to install the sunshine app, and just s-off it again with no fee. The sunshine license is forever associated with the device, and if it was purchased once, you can s-off that device again and again.
imsodin said:
In some old threads about dual sim "special" twrp imgs like TWRP_Recovery_2.8.0.5_M8_CPTB.img are recommended, but the download links are broken.
Click to expand...
Click to collapse
Far as I can recall, the dual SIM M8 did require it's own version of TWRP. Keep trying to find a working link, is all you can do.
redpoint73 said:
S-off does not limit OTA. So maybe not the best idea to make it s-on again. On the other hand, s-on will not limit installation of TWRP, custom ROMs, etc.
Also, if the device was made s-off by sunshine, you should be able to install the sunshine app, and just s-off it again with no fee. The sunshine license is forever associated with the device, and if it was purchased once, you can s-off that device again and again.
Far as I can recall, the dual SIM M8 did require it's own version of TWRP. Keep trying to find a working link, is all you can do.
Click to expand...
Click to collapse
Good to know about s-on, then it won't bother me.
As to a working link: They all go to yandex/mega/..., i.e. no luck with any archives. I scoured xda and google, and all broken links or pointers to the "normal" m8 twrp (often explicitly stating that it's the same for dual sim, e.g. https://forum.xda-developers.com/htc-one-m8/help/twrp-recovert-htc-one-m8-dual-sim-t3384609). I really don't want to write this phone off, well mostly I don't want to look for an alternative, but I am at my wits end and wasting too much time
imsodin said:
I scoured xda and google, and all broken links or pointers to the "normal" m8 twrp (often explicitly stating that it's the same for dual sim, e.g. https://forum.xda-developers.com/htc-one-m8/help/twrp-recovert-htc-one-m8-dual-sim-t3384609).
Click to expand...
Click to collapse
It is confusing to determine whether the dual SIM requires its own recovery or not, as I looked at some threads myself. But the thread you linked in particular, the guy that says it is the same recovery (as the single SIM M8) ckpv5, I don't think I've ever seen him wrong about anything. So I would take his word for it.
Based on his thread here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
the proper TWRP version for OS version 3.xx should be TWRP 2.8.3.0, so you should focus there. I know you tried it already, but it doesn't hurt to try it again.
TLDR:
This device isn't unproblematic to handle - don't just assume anything from previous experience as I did. I manages to create a paperweight (technically maybe recoverable, but I don't have the patience anymore to try).
Thanks for keeping me on the right track, I managed to get twrp 2.8.1.0 (sic!) to work. I doubt the following will be helpful to anyone, but who knows:
fastboot getvar all showed the above output, i.e. version 3.33.401.6. However when I tried to get the downloaded OTA (for the firmware) I noticed it says it will upgrade to 3.33.401.6. So checking the settings in Android I find that my actual version is 1.45.401.12. Which according to https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 means you should use twrp 2.8.1.0.
I was pretty sure I already tried that, but I probably didn't. I did find a dubious claim that you need to flash the recovery twice immediately and then erase cache and did that for good measure (I know I am not supposed to, but when it comes to all things android/phone I do believe in "weird s**t").
Now after that I installed LOS 16 - well I tried. TWRP fails to report the model which aborts the installation. So I removed the asserts from LOS' install script. Stupid move: It doesn't only check the model but also the bootlocker - and that was actually incompatible. Obviously as I have no reason to go back to some ancient HTC OS I didn't do a backup. So now I can't boot a system to get to s-off and can't install an RUU - which for all I read is the only way to get back on track to update the firmware. Just for funsies I also tried to flash a newer boot.img in hopes to get to bootloader 0.19, but that didn't have any effect.
The only way out would be to install some ROM that runs on bootloader 0.18 - I didn't find any. Then get to s-off using sunshine, then go through the entire back-to-stock dance and finally use OTAs to update firmware and once done go back to custom. Well, actually that would have been the intuitive and logical thing to do in the first place: Exhaust all official upgrades, backup, go custom. But inpatient me wanted to take the shortcut to custom and now I spent hours for nothing.
Sorry for the lengthy rant
See my comments below in red font:
imsodin said:
TLDR:
fastboot getvar all showed the above output, i.e. version 3.33.401.6. However when I tried to get the downloaded OTA (for the firmware) I noticed it says it will upgrade to 3.33.401.6. So checking the settings in Android I find that my actual version is 1.45.401.12. Which according to https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 means you should use twrp 2.8.1.0.
The OS number reported by getvar is the correct (current) firmware. The OS number shown in settings is not to be trusted. At some point, it looks like somebody flashed a 1.45.xxx based ROM, but the phone still has 3.33.xx firmware. You want the ROM to correspond with the firmware.
Now after that I installed LOS 16 - well I tried. TWRP fails to report the model which aborts the installation. So I removed the asserts from LOS' install script. Stupid move: It doesn't only check the model but also the bootlocker - and that was actually incompatible. Obviously as I have no reason to go back to some ancient HTC OS I didn't do a backup. So now I can't boot a system to get to s-off and can't install an RUU - which for all I read is the only way to get back on track to update the firmware.
You don't need s-off to flash an RUU intended for your version M8 (dual SIM). If the RUU is not for the dual SIM, it will probably brick your phone if you flashed it. So those safeguards exist for a reason.
If you can find RUUs for your dual SIM M8, that would be an easy way out. But I don't think I've seen such an animal.
Other options might be:
- (if you can find them) flash 3.33.401.6 stock backup and stock recovery. Then OTA update.
- (if you can find it) flash 4.30.401.16 signed firmware, and restore stock TWRP backup 4.30.401.16 that ckpv5 posted in his collection.
- (if you can find it) flash 4.30.401.16 signed firmware and flash LOS16, as that firmware might put you on the right bootloader and firmware to work with that ROM.
I know these unfortunately are all high bars to meet, as the dual SIM doesn't have a lot of resources posted.
Just for funsies I also tried to flash a newer boot.img in hopes to get to bootloader 0.19, but that didn't have any effect.
boot.img is a completely separate partition from bootloader. They sound the same, but not the same. boot.img is essentially the kernel. You can't flash bootloader by itself with s-on. But you can flash bootloader with the correct RUU or signed firmware for your version M8 (CID, MID).
Click to expand...
Click to collapse
The problem is my CID has been changed to 111111 (which I read is some kind of magical super-power CID, don't know why though ), thus I can't flash any RUUs. I tried flashing a few x.x.401.x firmwares without success.
Anyway thanks again for helping me - in the meantime I lost the phone I wanted to replace, which was the final trigger to abandon this project and just get a cheap new phone that I'll hopefully not butcher (for now (still gets security updates) it'll get Magisk Root only - after upgrading and backing up).

Categories

Resources