Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
promsos said:
Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
Click to expand...
Click to collapse
Did your firmware.zip have a boot*.img in it? You probably need the old version of the boot.img to match the old software. You might want to find on of the old Verizon RUUs and extract the boot.img from there and try flashing that in fastboot. Message me if the Verizon boot doesn't work for you, I might have some other ideas. I'd say be careful, but you're already in trouble.
Edit: You could also do a nandroid backup and try a custom ROM to get it functional in the short term.
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
promsos said:
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
Click to expand...
Click to collapse
The boot.img from an older Verizon RUU would probably work, but you might have to try a couple to get the right one. The boot.img is directly tied to the ROM version that is installed, and is often called the kernel and tells the system how to boot the ROM.
Make sure you do a backup of your working Viper before restoring the stock one and trying to flash a boot.img.
I don't understand why you re locked the boot loader and flashed a firmware zip just to revert to stock recovery? All you had to do was pull the stock recovery from the firmware.zip in the OTA then flash it via fast boot. Then go ahead and flash the OTA.
You need to now find and flash a compatible boot.img. Just keep trying different ones until it boots.
I'm making a little progress here, thanks for the help. I downloaded a 4.4.3 Verizon kernel, loaded that (after restoring the old nandroid backup) and I'm able to boot, whew... I'm having two issues now, 1) my wireless won't turn on for some reason and 2) I tried installing the 4.4.4 OTA update my carrier released (downloaded via 4G) and it won't apply - I was hoping successfully applying this OTA would fix the wireless issue. Looking at my software version it looks like I'm actually running 4.4.2, could that cause both of these issues? I'm trying to locate a 4.4.2 kernel to load but figured I'd toss out the question in the meantime.
Ashyx - I wish I had a better answer to why I temporarily relocked the boot loader and flashed firmware.zip other than desperation (trying to get that darn OTA). It was a while ago I flashed the firmware.zip file but I thought that when I initially extracted the recovery from the zip file and flashed it I could no longer boot into a recovery, maybe I'm making that up though - I can hardly remember last week lol. I'm an IT guy, so I'm not completely clueless, but I'm far from proficient with mobile technologies, as I'm sure you gathered already.
Anyways, I'd appreciate any insight, in the mean time I'm going to keep hunting for a 4.4.2 kernel to try on this thing. Thanks again to all.
http://forum.xda-developers.com/showthread.php?t=2723159
Try the zips from here, they should have a boot.img for 4.4.2.
Sent from my One M8 using XDA Free mobile app
Ok, I think I'm back up and running. I was able to find a 4.4.2 boot.img that allowed me to once again use my wireless. After getting the wireless working I had to find valid versions of flashlight.apk and calculator.apk to put in data/preload and the OTA finally took....success at last. I really appreciate the help durgis, I'll be grabbing a nandroid of my now working phone right away so I don't run into issues in the future. Again, thank you for the help, very much appreciated.
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
rook79 said:
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
Click to expand...
Click to collapse
Hey rook, I do have the same CID, are you on Cellcom out of Wisconsin? I didn't grab a bare bones nandroid, but i can do a backup, uninstall my apps and do one, or rebuild mine from my unbootable one now that I have everything i need. If you want to try a different ROM you could try Viper, it worked decent for me, just a few quirks when i bounced from wireless to 3G for some reason.
I am with Cellcom. My problems started with the recent OTA update. The update wouldn't take, because of the flashlight.apk. I decided it was time to root this phone anyway and try some custom roms. I've done it with my other HTC phones in the past with no problems. Unlocked the bootloader, loaded TWRP and did a backup. Didn't check where the backup was being put and ended up saving it to internal. Put on a new ROM and wiped my backup. Cyanogenmod 11 is the only ROM that I've had success with. Every other rom that I have tried so far will not complete the initial boot. I suspect that I'm missing something stupid, or it has something to do with the OTA update not completing. Are you running Viper, or did you get the Cellcom OTA update to work?
I was running Viper for a while but now have my phone reverted to stock with the 4.4.4 OTA applied. If you want a nandroid of stock Cellcom 4.4.4 I can work on one for you, it may take a couple days to get it but I should be able to get one.
That would be awesome. I've been looking for a stock Rom for a while now. As you know those are nearly impossible to find. Not having a stock nandroid backup or the OTA update zip kind of put me in a SOL position. Thanks for your help.
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
That worked awesome. Thanks!!!
Hi Guys, (@rook79 , @promsos)
i have the same model and running into similar problem, i was also not able to flash any other rom than SkyDragon, wanted to be able to flash other roms but no luck, i thought its the firmware that wont let me install so i went for S-Off and flashed one of the firmware from verizon, since there was not much help for this specific model and everyone was referring it as a variant from verizon, i did flash one and my problem started, my phone had no signals after flashing the firmware and was still not able to flash any other ROM, i flashed couple of more firmwares and radios to get my network working but no luck, and i got a new problem that the phone keeps rebooting after a couple of minutes it loads into system.
then somebody helped me with the stock firmware 4.4.4 from here and nandroid from this thread, firmware was still verizon, i managed to restore it but still the same reboot issue and no signals, but i was able to download OTA which wont install, everytime i try to install it, it goes to stock recovery with a progress bar 1% filled and then stuck into boot loop and after n number of attempts it boots into system, where again it reboots after a couple of minutes.
extracted the firmware from OTA and manually flashed it and tried to install OTA but still same, i tried to reboot into stock recovery but every time i do that, it goes to black screen and then keep rebooting, i am not able to get to that red triangle screen.
help less clueless trying to find complete RUU for it (not sure if thats going to help)
my partition table has 2 vzw partitions as well because i flashed dottat's RUU for verizon.
can you guys help me with that?
my phone is m8_wlv CID: LRA_001 MID: 0P6B20000
s-off, and i am on a GSM network (not US).
promsos said:
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
Click to expand...
Click to collapse
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
is this what you are looking for? https://www.dropbox.com/s/2oozc291kwe5l9r/OTA_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4-3.31.512.2_release_426215.zip?dl=0
hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
Hi
Do you still have that LRA version?? I need some help
I am sorry if this has happened to 40 other people and mentioned every day but I am at the end of my patience trying to figure this out and have too many tabs open with redundant info!!!
I attempted to unlock my bone-stock up-to-date (v6.0.1) one m9 developer edition using this link http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133 but after following all the directions when it was time to restart it just gave me the screen with the red development only warning for about 2 or 3 seconds then reset and repeated.. it says it may do this a few times but it did it like 10+ times so I figured there was a problem. Since then I have tried many different files from many different places.
I do not have a working backup copy of my phone (my bad) but I did make a backup of the system image onto my sd card.
As of now, if I reboot it sends me to the white bootloader screen after trying to follow another similar page with directions to root (specifically mentions android v6.0 in the title).
The phone is now S-on.
LK-1.0.0.00000
Radio 01.01-U11440892_97.00.51203G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.35.617.12
The recovery mode loads to TWRP 2.8.7.1_CPTB-B1
Eventually my main goal was to get this phone to work "correctly" with Tmobile US (wifi calling and fastest available internet connection) but for now I just want it to load back up to my system (hopefully without losing the data that is currently in it!!!)
Can anybody recommend which files I need to put on and which way you recommend?
Thanks in Advance!!!!
-AshayinFLA
You can't root Android M with a different SuperSU version than 2.64 or 2.65. (Keyword: system-less root)
There's backup for your version in my thread. Instructions how to correctly restore it can be found in my google sheet (linked in the 5th post or my signature).
I'm not 100 % sure but I guess you need to flash the T-Mobile firmware if you want to use their WIFI-calling. For that you need S-OFF. Otherwise you can't change the firmware. (Wouldn't it have been easier to buy a T-Mobile branded phone than buying a dev edition, paying for either Sunshine or someone who has a java card and convert the phone to the T-Mobile version? )
I've rooted and flashed custom roms many times during the years on many devices, but this is the first time I've needed to go back to stock and it didn't really go as planned.
The reason is I planned to use my old retired One X as work phone and use my work phone for other purposes and our company is using MobileIron which requires an unrooted phone and also adds several other limitations to the phone (requires a five digit pin, doesn't allow stuff on the lock screen etc.).
I was previously running a Resurrection Remix (Android 5.1) on it with the new layout, but I installed an old Philz recovery, reformatted the sd card, flashed this rom http://forum.xda-developers.com/showthread.php?t=1546970, that was supposed to be completely stock, not rooted, no busybox etc. and then also installed the stock recovery after the rom. After that I was able to take an official OTA update to fix the heartbleed bug (4.18.401.4) and I thought everything was fine.
I then registered and installed MobileIron and also that looked fine and I got a nice green checkbox that all was ok, but when I did the final step to try to connect to the corporate Exchange ActiveSync that failed and I got a mail telling me something like "Critical. Your mobile device has been detected as compromized (jailbreaked or rooted). All access to corporate information has been blocked/removed from the device.".
Does anybody know what MobileIron is looking for and if there is any way to be more stock than I currently am? I don't suppose it will check for an unlocked bootloader? I do have an old RUU lying around "RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed". But it feels wrong to use a RUU to downgrade the phone (if that's even possible on a S-ON phone?), and even if I did would I be able to upgrade to the current version using OTA's in that case? If it matters my CID is HTC__Y13.
Decided to go back to my S-oFF Sprint htc one m8 from over a year ago.
First thing I did was update my firmware only, no recovery no boot, firmware only. I upgraded firmware to 6.20.651.3 using this link: http://forum.xda-developers.com/showthread.php?t=2729173
I then updated my twrp from 2.8.50 to 3.0.2-0.
after I try any rom, even sprint roms, I can't get passed the hands free activation and prl update screen. It will reboot before the phone boots up. I have tried a few gpe roms and it wont get past the boot screen.
I tried loading up a nandroid i made over a year ago and its a lollipop rom that works, but still wants to go through handsfree activation. I am able to turn it off there, but want to get back to marshmallow and newer roms. I called sprint support and they said it shows as fully activated on their end.
What else should I try? Should i upgrade firmware, recovery and boot?
I hate bumping, but im out of options here. Any advice?
memekmek said:
I hate bumping, but im out of options here. Any advice?
Click to expand...
Click to collapse
I've gone through countless threads like these: http://forum.xda-developers.com/showthread.php?t=2716834
my situation seams to be unique, where my phone will actually reboot right after hands free activation, thus rendering it useless. I've been able to mount the system in twrp and delete the htc service apk, but on the marshmallow roms, i can't get LTE to work.
Im stumped. :crying:
So I've managed to read through threads and turn off hands free activation by:
1. Using wifi at initial setup (this helps get passed the initial hands free activation)
2. Mounting system in twrp, then deleting htcservice apk in twrp (this helps getting past the initial setup if its a problem)
3. freezing vdm client in titanium backup to avoid having the hands free activation keep popping up.
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Any help on the LTE and firmware issues would be very much appreciated!
memekmek said:
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Click to expand...
Click to collapse
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).
redpoint73 said:
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).
Click to expand...
Click to collapse
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.
memekmek said:
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.
Click to expand...
Click to collapse
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.
redpoint73 said:
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.
Click to expand...
Click to collapse
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?
memekmek said:
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?
Click to expand...
Click to collapse
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).
redpoint73 said:
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).
Click to expand...
Click to collapse
Welp, did the RUU last night. It changed nothing, and did nothing for me other than making it a pain to reinstall twrp and get my nandroid back up. booo
lte and data is still spotty on 6.0 roms. The only other possible reason i think this could be happening is because i tried to carrier unlock this phone a few months ago, but i downloaded sim card info app, and it all appears to be ok.
Good morning,
I've recently moved to Japan and purchased an HTC 10 from AU / KDDI. The version information is as follows: CID KDDI_801, MID 2PS670000 / htc_pmeuhljapan. This is my first time dealing with a non-US phone. I've unlocked, s-offed, etc and installed CyanogenMod on my US HTC phones. I've managed to S-OFF / Unlock the AU phone. However, I was unable to root without TWRP or backup the stock recovery. So I flashed TWRP onto it, rooted and that whole deal without issue. I've also backed up my System Image / Boot.
This broke my OTA updates (surprise surprise) but I found an update here: http://forum.xda-developers.com/htc-10/help/htc-10-au-japan-ota-zip-file-t3490829/page2 and attempted to flash. I cannot flash the entire zip file, however, my phone will take the firmware file within. This seems to update the firmware from 1.28 to 1.95. However, this breaks the phone's WiFi (WiFi won't see any networks), but seems to re-install stock recovery.
Still, the OTA updates failed. So I reflashed TWRP recovery and restored my backup. WiFi works just fine again. After I restore the backup it says OS-1.95.970.4 in download mode, however, in the OS itself it shows the old build number 1.28.xxxx. Does anyone have an applicable copy of the stock recovery I can throw on there and attempt to get an OTA update? If not, would international ROM's work with this phone or do I need to find Japan specific? I know they have some of their own bands so I'm not sure of compatibility issues. If you need any additional information please let me know. Sorry if any of the questions / circumstances seem ridiculous, again, I've never had to deal with a non-US phone so there's a bit less information available.
i also use htc 10 of Au japan, can you upload an stock or backup of stock of it. my phone cant boot now
is this phone water proof?
minori_aoi said:
is this phone water proof?
Click to expand...
Click to collapse
No
Hi..which twrp did you flash?
Sir how you unlocked this phone. ?
I dont know i try sunshine and the htcdev there is no way to unlocked bootloader it's furstasing.... :crying:
And another way is buy xtc2clip the price is like so so expensive :crying: