Hello XDA,
I've made absolutely no changes to my phone settings, ROMS, Kernal ETC..
Recently, I've decided to upgrade to a new ROM which was CRDroid Android 7.0 (Name may be wrong)
I use Philz CWM recovery, while installing I noticed once it finished it said cannot mount /data.
Though the phone rebooted on it's own and started to boot, but once it reached the boot logo the phone froze.
Directly in the middle of the animation, it stopped and stayed that way for at least 15 minutes before I had to hard reset it.
I noticed I cannot install any type of Android N (7.0) ROM without freezing, I can only install Marshmellow or lower.
Can anyone explain why, is this a firmware issue perhaps?
Use the latest TWRP recovery
Philz is outdated now and most probably won't work
Sent from my HTC M8 using XDA Labs
Regardless of the recovery used, problem still persists. I believe it may be a firmware issue.
Trytohaxme said:
Regardless of the recovery used, problem still persists.
Click to expand...
Click to collapse
Does that mean you tried TWRP or not? And what version(s)?
In TWRP do you still get issue not mounting data? If so, try going to Wipe section of TWRP, and tap "Format data" which will often fix the mount data problem. Obviously, your data will be lost.
Please try to give as much detail and specific as possible when posting. Posting a 2 sentence response is rarely enough for us to work with.
Trytohaxme said:
I believe it may be a firmware issue.
Click to expand...
Click to collapse
We would need to know more about the firmware to say anything about that. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting0
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: REMOVED
(bootloader) imei: REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 99000499864898
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(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: f2489bd1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.098s
I've tried about 3 versions of TWRP, including the latest version.
I'm no longer able to format or install using TWRP which is the reason I have to use Philz.
I have major screen burn issues on the top portion of my phone, so touch is unresponsive so being able to use the volume rocker with Philz recovery is a life saver.
I've heard something about connecting the phone to a windows laptop, and formatting the partitions VIA > Device Manager helps with mounting the /Data partition though because I believe mine may be corrupt as I can only install ROMS that do not touch the data partition.
Trytohaxme said:
(bootloader) version-main: 4.17.605.5
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B20000
Click to expand...
Click to collapse
Your firmware is Lollipop. I'm not a user of the AOSP ROMs (as all Nougat ROMs are), but from what ahmed posted, LP ROMs can indeed cause problems with Hougat: https://forum.xda-developers.com/htc-one-m8/help/upgrade-5-1-1-to-7-x-x-to-firmware-t3580047
Also, your getvar output shows you have the Verizon M8. Did you verify the ROMs support the Verizon version?
redpoint73 said:
Your firmware is Lollipop. I'm not a user of the AOSP ROMs (as all Nougat ROMs are), but from what ahmed posted, LP ROMs can indeed cause problems with Hougat: https://forum.xda-developers.com/htc-one-m8/help/upgrade-5-1-1-to-7-x-x-to-firmware-t3580047
Also, your getvar output shows you have the Verizon M8. Did you verify the ROMs support the Verizon version?
Click to expand...
Click to collapse
I'm currently downloading MM firmware for my device, and yes I verify there is Verizon support.
Though my phones model is Verizon branded, the phone is unlocked and I use it with T-Mobile.
Trytohaxme said:
Though my phones model is Verizon branded, the phone is unlocked and I use it with T-Mobile.
Click to expand...
Click to collapse
What M8 version is important in this case (Verizon) for a variety of reasons, and I'm not talking about what carrier you are using it on. The Verizon version M8 is very unique in that it uses different kernel, partitioning, and antenna hardware due to CDMA support. Plus, you can only flash Verizon firmware or RUU (others won't work, and may even cause a permanent radio brick). The Sprint version has similar aspects (although the firmware is not even interchangeable between Sprint and Verizon M8 versions).
redpoint73 said:
What M8 version is important in this case (Verizon) for a variety of reasons, and I'm not talking about what carrier you are using it on. The Verizon version M8 is very unique in that it uses different kernel, partitioning, and antenna hardware due to CDMA support. Plus, you can only flash Verizon firmware or RUU (others won't work, and may even cause a permanent radio brick). The Sprint version has similar aspects (although the firmware is not even interchangeable between Sprint and Verizon M8 versions).
Click to expand...
Click to collapse
Well, I did a little more research and seem to have come to the conclusion that in order to flash the roms I'm trying to flash I need to use TWRP.
The problem is since my phone top portion of the screen is not touch responsive, I have no choice but to use Philz.
Is there a TWRP that would happen to work in landscape mode, otherwise I'm SOL.
Trytohaxme said:
Well, I did a little more research and seem to have come to the conclusion that in order to flash the roms I'm trying to flash I need to use TWRP.
The problem is since my phone top portion of the screen is not touch responsive, I have no choice but to use Philz.
Is there a TWRP that would happen to work in landscape mode, otherwise I'm SOL.
Click to expand...
Click to collapse
I understand you have some peculiar things going on causing you to use Philz. I don't think there is a harm in trying Philz (to flash an N ROM), after you have the firmware updated. But I just wouldn't expect Philz (which hasn't been updated for 2 years) to work well with the latest ROMs.
No landscape TWRP that I know of.
redpoint73 said:
I understand you have some peculiar things going on causing you to use Philz. I don't think there is a harm in trying Philz (to flash an N ROM), after you have the firmware updated. But I just wouldn't expect Philz (which hasn't been updated for 2 years) to work well with the latest ROMs.
No landscape TWRP that I know of.
Click to expand...
Click to collapse
Each ROM I tried installed give me basically the same output, maybe you can help figure them out.
Code:
detected filesystem ext4 for /dev/block/flatform/msm_sdcc. 1/by-name/system
unmount of /system failed
failed to mount /dev/block/flatform/msm_sdcc. 1/by-name/userdata at /data: device or resource busy
These are the 3 differents errors I receive during installation of a new ROM.
After those errors show the ROM continues with the installation, but as soon as the phone boots it freezes than reboots back to recovery.
Trytohaxme said:
Each ROM I tried installed give me basically the same output, maybe you can help figure them out.
Click to expand...
Click to collapse
Is this with Philz?
Is this on the LP firmware or MM firmware?
---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------
Maybe adb sideload feature can help you to use TWRP in your condition?
https://twrp.me/faq/ADBSideload.html
redpoint73 said:
Is this with Philz?
Is this on the LP firmware or MM firmware?
---------- Post added at 01:18 PM ---------- Previous post was at 01:17 PM ----------
Maybe adb sideload feature can help you to use TWRP in your condition?
https://twrp.me/faq/ADBSideload.html
Click to expand...
Click to collapse
This is on LP and MM firmware, and the same output occurs even while using sideload sadly
Here is a photo I just took using my laptops webcam, as you see the boot animation starts than completely freezes.
http://imgur.com/BSZ2ZzD
Related
I hope someone can help.
My M8 messed up a while back and got stuck on the boot screen - Android would load and I could hear notifications coming through but the screen only displayed the white HTC loading image. I left it for hours and nothing changed. I could swipe down to see volume controls and holding the power button allowed me to turn off and restart. Factory reset did not fix the problem so I headed for recovery. I've rooted HTC and Samsung devices in the past without issues and thought that flashing a stock image would fix things but here I got a bit lost.
I couldn't reach stock recovery so I unlocked the bootloader and flash TWRP. From here I rather foolishly deleted far too much from the phone - cache/system/data - and so I now had no OS on the phone rather than a faulty OS. From here I downloaded and flashed a GPE ROM and got the phone back running but it would not detect my SIM card. At this point I could use Wifi but having tracked down the right stock recovery for the phone (I think) and flashed it, I now have working Android but no Wifi or SIM detected.
Getvar data:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
I've decided to accept that I'm in over my head and need expert help. I can't send the phone back to EE in this state so you guys are my only hope!
You need to have more info. What is the exact model phone, is your phone European, international, etc. What was the version of android you were running before you flashed a ROM (lollipop, etc.). Double check the APN settings for your carrier.
If you were running lollipop originally but flashed a marshmallow ROM then you may need to update your firmware. Did you flash a 'ported' gpe ROM that is supposed to work with the stock partitions or an actual gpe system image (big difference).
You may just be able to flash the current firmware, but double check everything to make sure that you have the correct firmware and ROM for your phone before you try again. And the process is different for s-on versus s-off for flashing firmware and an ruu flash.
themakeshiftmonkey said:
At this point I could use Wifi but having tracked down the right stock recovery for the phone (I think) and flashed it, I now have working Android but no Wifi or SIM detected.
Click to expand...
Click to collapse
If you tell us the version number you flashed, we can tell you whether it was right or not.
But flashing stock recovery would not have changed anything (WiFi, etc.). DO you mean you flashed a stock TWRP "nandroid" backup (stock ROM)?
---------- Post added at 09:29 AM ---------- Previous post was at 09:25 AM ----------
morr22066 said:
You need to have more info. What is the exact model phone, is your phone European, international, etc. What was the version of android you were running before you flashed a ROM (lollipop, etc.).
Click to expand...
Click to collapse
The info is all given in the OP, and doesn't look like it was edited after your post (so was apparently there to begin with).
CID and MID tell the version. Only thing missing is main version, but from the radio baseband (1.29xxx) it looks like the phone was on MM firmware. So its a bit puzzling why WiFi and SIM is broken.
I'd suggest to the OP to make sure they are on the correct stock nandroid, and see if the problems persist.
Sorry guys, I'll try and explain better.
The phone is European and on EE (UK). It had fairly recently upgraded to Marshmallow OTA.
After having GPE running on it, I got hold of a stock backup (not recovery - I was pretty tired and confused when I posted that) from http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
I downloaded and installed 6.12.61.4 from that list. This gave me back the right OS but now I have no wifi and the phone won't recognise the SIM.
I've since wiped cache/data/system and reflashed with the same result.
Edit to provide additional info:
I've just discovered that as well as wifi, bluetooth can't be turned on either. Also, when switched on and left idle, the phone crashes and reboots every hour or so.
I've ruled out issues with the SIM itself in regards to the mobile data/cell reception problem. The SIM works fine in another phone. Also tried another SIM in the M8 and it was not recognised either. This has been persistent since I flashed GPE onto the phone. The wifi problem is fairly new though. It was working while running this backup, but I left the phone for a couple of weeks while I had other things taking up my time. I've come back to it and reflashed to see if this resolved but now wifi has gone too.
I have no idea what to do from here guys, I really hope you can guide me to a solution.
Jonny
themakeshiftmonkey said:
Sorry guys, I'll try and explain better.
The phone is European and on EE (UK). It had fairly recently upgraded to Marshmallow OTA.
After having GPE running on it, I got hold of a stock backup (not recovery - I was pretty tired and confused when I posted that) from http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
I downloaded and installed 6.12.61.4 from that list. This gave me back the right OS but now I have no wifi and the phone won't recognise the SIM.
I've since wiped cache/data/system and reflashed with the same result.
Edit to provide additional info:
I've just discovered that as well as wifi, bluetooth can't be turned on either. Also, when switched on and left idle, the phone crashes and reboots every hour or so.
I've ruled out issues with the SIM itself in regards to the mobile data/cell reception problem. The SIM works fine in another phone. Also tried another SIM in the M8 and it was not recognised either. This has been persistent since I flashed GPE onto the phone. The wifi problem is fairly new though. It was working while running this backup, but I left the phone for a couple of weeks while I had other things taking up my time. I've come back to it and reflashed to see if this resolved but now wifi has gone too.
I have no idea what to do from here guys, I really hope you can guide me to a solution.
Jonny
Click to expand...
Click to collapse
hi,
i´ve got similar issuses some nightlies / stockroms
like redpoint73 says - the recovery seems not to be the problem.
is your bootloader unlocked?
i´ve just installed latest TWRP Recovery ( https://dl.twrp.me/m8/ )- FullBackup 2 SD - Fullwipe - install cm13 nightly ( https://download.cyanogenmod.org/?device=m8 )
in some nightlys the SIM won´t reconnet after flightmode - but no wifi problems
themakeshiftmonkey said:
After having GPE running on it, I got hold of a stock backup (not recovery - I was pretty tired and confused when I posted that) from http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
Click to expand...
Click to collapse
You're still linking the wrong thing (linked post is stock recovery files when you want a stock backup). Did you restore recovery or a backup? The proper file would be the 6.12.61.4 backup from Post #3 of the collectionhttp://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
redpoint73 said:
You're still linking the wrong thing (linked post is stock recovery files when you want a stock backup). Did you restore recovery or a backup? The proper file would be the 6.12.61.4 backup from Post #3 of the collectionhttp://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Click to expand...
Click to collapse
Yes, sorry. I must be trying your patience a little.
I flashed that backup file from post #3 of that thread using TWRP, following the instructions in post #1 up to and including step 9.
I'm currently running CM12.1 on my HTC One M8, and have been successfully doing so for the past 6 months.
I decided to try and install CM13 today after all this time, and the CM13 and Gapps install were clean (i.e. TWRP reported it as successful) Then when I clicked reboot system, it loads into fastboot for some reason, not into the normal reboot screen.
Even after rebooting 5 or 6 times, it still repeatedly goes back into fastboot. Anyone had a similar problem who could help me out ?
I backed up, therefore am back to 12.1 for now.
Make sure you firmware is compatible, and you're using a compatible version TWRP.
If so, try another nightly, and try a different gapps. I don't use CM13 on my M8, but us it on my Samsung Tab Pro 8.4. On that, I've found CM13 to be finicky about gapps version. I've had most luck with Open Gapps, and the smaller gapps packages (pico, nano).
Also, make sure you wipe data, cache, and Dalvik. Trying to migrate data from CM12>Cm13 probably won't work, and cause no boot (as often the case with moving between major build changes).
redpoint73 said:
Make sure you firmware is compatible, and you're using a compatible version TWRP.
If so, try another nightly, and try a different gapps. I don't use CM13 on my M8, but us it on my Samsung Tab Pro 8.4. On that, I've found CM13 to be finicky about gapps version. I've had most luck with Open Gapps, and the smaller gapps packages (pico, nano).
Also, make sure you wipe data, cache, and Dalvik. Trying to migrate data from CM12>Cm13 probably won't work, and cause no boot (as often the case with moving between major build changes).
Click to expand...
Click to collapse
Apologies for the noobish response, but how can I check the compatibility of the firmware and TWRP? TWRP version is 2.7, I assumed that would be fine to install CM13 with?
Sugz said:
Apologies for the noobish response, but how can I check the compatibility of the firmware and TWRP? TWRP version is 2.7, I assumed that would be fine to install CM13 with?
Click to expand...
Click to collapse
TWRP 2.7 is over 2 years old. That is probably your problem right there, or at least part of it.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) and we'll take a look to see if the firmware needs to be updated, as well (will also tell us which updated version TWRP to install).
redpoint73 said:
TWRP 2.7 is over 2 years old. That is probably your problem right there, or at least part of it.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) and we'll take a look to see if the firmware needs to be updated, as well (will also tell us which updated version TWRP to install).
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Heres what i got with that command..
I just don't understand how CM12 was so easy to install, and this has caused so many problems.
Sugz said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
Click to expand...
Click to collapse
Looks like from the above info you are on Lollipop firmware (hboot, radio, etc.) which should be okay with CM13, I believe (read the CM13 thread to confirm).
I recommend (with LP firmware) to flash TWRP 2.8.7 from here (includes the required TWRP img file, and instructions to flash with fastboot - if you don't already know how): https://twrp.me/devices/htconem8gsm.html
Sugz said:
I just don't understand how CM12 was so easy to install, and this has caused so many problems.
Click to expand...
Click to collapse
I'm guessing you haven't updated CM12 either in 6 months. Or if so, it wasn't updated for current firmware or recovery versions (not personally aware)?
But its very normal for newer CM versions to fail if you haven't updated hboot and/or TWRP versions. This is for your protection, to ensure proper compatibility. All the software/firmware components need to be updated, not just the ROM.
On that same note, whenever flashing a new ROM (and a major update of CM applies) its often a good idea to read through the specific ROM thread (not the whole thing, but at least skim through the more recent several pages) to see what firmware, TWRP versions are required, installation or other bugs, etc.
Thank you for your help. Turns out that I was completely stupid in installing the HTC One M8 ROM, instead of the M8 dual sim ROM which is what caused all these problems in the first place.
Successfully installed CM13 now with Gapps, functioning greatly.
Sugz said:
Thank you for your help. Turns out that I was completely stupid in installing the HTC One M8 ROM, instead of the M8 dual sim ROM which is what caused all these problems in the first place.
Successfully installed CM13 now with Gapps, functioning greatly.
Click to expand...
Click to collapse
You should still update your TWRP version. Using version from over 2 years ago, is asking for trouble. If not now, then at some point down the road.
Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!
A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.
Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.
Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).
Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.
Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.
Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.
My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
Two days of trying to find a solution here on xda and always banging my head in dead links and a load of information to try to understand I now have ended up with a hopefully not bricked device, I'm just stuck and need help.
This is the output of "fastboot getvar all" now.
Code:
(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: FA4A8SF00188
(bootloader) imei: 990004997721794
(bootloader) imei2: Not Support
(bootloader) meid: 99000499772179
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(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
This is the different lines in the output of the "fastboot getvar all" before
Code:
version-baseband: 1.12.20.1211
version-main 4.21.512.4
commitno-bootloader: 205bdca3
What I did was flashing "unsigned_firmware_6.12.401.4" and to make that work I had to change one line inside the android-info.txt from modelid: 0P6B10000 to modelid: 0P6B20000.
I'm not shure when the trouble started, and after two days of testing I don't remember all I did or not. exactly but I started to try a couple of different roms and the trying to go back to backup made by twrp "twrp-3.1.1-0-m8" there was sudden restarts and twrp got errors with carrier partition, I changed to an older twrp and got that working for a while but ten suddenly I got other errors from /cash and /data partitions when trying to whipe with twrp, tried different twrp:s trying to flash other firmwares and other roms and kernels, I'm stuck.
Now If I install lineage os, 14. .... the installation finish but with errors, I can start the phone but it will restart then and then, and if i shut it down it will not be shut down after some minutes it starts again by it self.
IF i go back to the backed up stock that I got the phone with it will do exactly the same with reboots and not being able to shut down properly.
Android version 4.4.4
HTC Sense-version 6.0
Program version 3.31.512.2
HTC SDK API level 6.25
PRI-version not available
PRL--version not available
Kernel version 3.4.g3e2305b [email protected]#1 SMP PREeMPT
Basebandvesion not available
Versionnumber 3.31.512.2 CL39569 release-keyes.
he phone is only stable in bootloader and in twrp, the twrp for the moment is 2.8.0.
Excuse me for messing up, but what shall I do now?
My goal is a working LineageOS on the phone
Edited: Oh, I forgot to tell that I prefer to use Linux when working on the phone. Somewhere I have a rarely used win10 machine also if needed.
You have a peculiar version of the M8, which is know as LRA (a Verizon variant). This is one of the "CDMA" M8 variants, which supports the Verizon LRA CDMA network (in addition to GSM, HSPA, LTE) and it differs from most other M8 versions. Therefore you can NOT flash firmware from any other version M8, such as the Euro firmware currently installed. The radio is not compatible, results in a radio brick, and that is probably why you have carrier partition errors.
Try flashing the proper RUU for LRA, and only this one: https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
I can't personally vouch for the above RUU. But I think others have verified it works on their LRA device. Hopefully, your phone boots after that, and the cell network functions. If so, you can install TWRP 3.1 (or at least 2.8.7) and a Verizon-compatible ROM. I don't know if Lineage qualifies, so I'll leave that up to you to research.
redpoint73 said:
You have a peculiar version of the M8, which is know as LRA (a Verizon variant). This is one of the "CDMA" M8 variants, which supports the Verizon LRA CDMA network (in addition to GSM, HSPA, LTE) and it differs from most other M8 versions. Therefore you can NOT flash firmware from any other version M8, such as the Euro firmware currently installed. The radio is not compatible, results in a radio brick, and that is probably why you have carrier partition errors.
Try flashing the proper RUU for LRA, and only this one: https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
I can't personally vouch for the above RUU. But I think others have verified it works on their LRA device. Hopefully, your phone boots after that, and the cell network functions. If so, you can install TWRP 3.1 (or at least 2.8.7) and a Verizon-compatible ROM. I don't know if Lineage qualifies, so I'll leave that up to you to research.
Click to expand...
Click to collapse
YEEEES thank you very much redpoint73, your answer led me to the solution. I got the phone back working
It didn't really work with the direct solution you pointed at (I don't know why), but after I red the whole thread RUU for bluegrass cellular variant I found a solution. There is a link to OTA
, I downloaded that, extracted the firmware from the zip and flashed it to my phone. Now it feel like new again. I'm not sure everything is back to normal but the version-baseband is back to where it started, the same with the version-main, but the bootloader? ie the commitno-bootloader is not changed back, will probably not only flashing firmware but so far i'ts working good. I just restored my lineageOS from previous backup.
I have wifi, radio and gps working and the lineageOS seams to work very well, maybe their version of M8 includes all versions?
Thank you again and again redpoint73
vildevilde said:
It didn't really work with the direct solution you pointed at (I don't know why), but after I red the whole thread, I downloaded that, extracted the firmware from the zip and flashed it to my phone. Now it feel like new again.
Click to expand...
Click to collapse
Not sure why the RUU didn't work, either. If the firmware from the OTA worked, the RUU should have worked. But RUU can be more finicky to things on the PC side, such as Windows version, if Visual C++ is installed, USB ports (2.0 vs. 3.0), etc. So nice job, working out a solution that worked.
vildevilde said:
I'm not sure everything is back to normal but the version-baseband is back to where it started, the same with the version-main, but the bootloader? ie the commitno-bootloader is not changed back,
Click to expand...
Click to collapse
The bootloader (3.19.0.0000) isn't different between LRA and Euro, or for that matter Lollipop versus Marshmallow. And since the firmware installed successfully, the bootloader would most likely match everything else installed by the firmware.zip (such as radio).
In other words, the bootloader number looks fine.
vildevilde said:
I just restored my lineageOS from previous backup.
I have wifi, radio and gps working and the lineageOS seams to work very well, maybe their version of M8 includes all versions?
Click to expand...
Click to collapse
I'm not a Lineage user on this device, so like I said before, I don't know either way whether it supports your LRA version M8.
If everything works on Lineage, I'd say it must support your LRA version device.
redpoint73 said:
Not sure why the RUU didn't work, either. If the firmware from the OTA worked, the RUU should have worked. But RUU can be more finicky to things on the PC side, such as Windows version, if Visual C++ is installed, USB ports (2.0 vs. 3.0), etc. So nice job, working out a solution that worked.
The bootloader (3.19.0.0000) isn't different between LRA and Euro, or for that matter Lollipop versus Marshmallow. And since the firmware installed successfully, the bootloader would most likely match everything else installed by the firmware.zip (such as radio).
In other words, the bootloader number looks fine.
I'm not a Lineage user on this device, so like I said before, I don't know either way whether it supports your LRA version M8.
If everything works on Lineage, I'd say it must support your LRA version device.
Click to expand...
Click to collapse
Yes, I'm using this as my daily phone now. Running LOS with microG support and everything works very good, easy updates every second day and no problems,
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.