Related
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
[Edit]: resolved by going S-OFF and changing the CID. Still odd this evne happened.
After trying to get XPosed Alpha working on stock Lollipop (apparently it doesn't - crashes com.android.phone, persistnetly) I tried a couple of ROMS / Backups offered here. Amongst them the Beatmod ROM (http://forum.xda-developers.com/desire-eye/development/rom-beatmod-desire-eye-android-5-0-2-t3094559) that comes with (working) XPosed (but breaks ADB and USB PassThru), and the offered flashable Lolloipop ROM offered here: http://forum.xda-developers.com/des...m-htc-desire-eye-europe-2-19-401-1-5-t3089472
Of course I made a nandroid backup of my Stock Lollipop before doing anything (I made the backup rioght after the OTA) - and it worked fine going back from Beatmod to my backup.
Howerver now (I think it started after flashign the Stock ROm I linked above - but I didn't notice it right away) after booting the system UI crashes, so does Dot View - no matter what ROM or Backup I apply. Beatmod is stuck at "Unlocking SIM card", and my recovery shows no active SIM. I THINK I accidentally screwed up the radio in the process - but I'm S-ON so I'm not qutie sure how that can even happen.
I have the unlocked international version of the eye, S-ON. Carrier is T-Moibel Germany.
Any help getting at least back to stock would be appreciated, as it seems there is no RUU available anywhere yet for this version of the phone.
Note: I'm new to debugging these things (by now I always managed to repair things myself), so please tell me what additional info is needed! I'm tech-savyy so no need to break it down in tiny pieces, no worries.
Applying my Backup from before any OTAs (Means KitKat) worked. However now, while the first OTA went through just fine, the one that updates to Lollipop stops with
Code:
Package expects build fingerprint of htc/tmo_de/htc_eyeul:4.4.4/TKU48P/402884.9:user/release-keys or htc/tmo_de/htc_eyeul:5.0.2/LRX22G/504177.2:user/release-keys; this device has htc/htc_europe/htc_eyeul:4.4.4/KTU48P/402884.9:user/release-keys
.
I guess that means it downloaded a branded OTA version, while I'm currently running an unbranded firmware - the question is, why - and why did it work the first time rigfht after I got the phone?
-> Which part did I change while flashing around that doesn't get reset when I apply the backup, and how do I get it back? As I said, I'm S-ON.
It's even worse. I tried manually flashing the firmware from the OTA ZIP and it worked. Then I tried unlokcing the bootloader again - didn't work at first, needed more than one try, but worked.
So, I guess I successfully branded my before unbranded device? How do I go back?
Last update. Issue still not solved. OTAs that I can download won't install anymore (looking for branded device but don't find it, see second post). Backup I made and ROMs downloaded end up with no Signal and crashing SystemUI, and not recognizing the SIM card anymore (My Stock KitKat backup still works fine though. Just Lollipop doesn't). I'm pretty sure the crashes are because of the SIM card issue (broken Radio? But I flasehd the firmware from the OTA that DOES include radio) though.
Why is there no RUU yet!
CID shows T-MOB101 - which would indicate a branded device (that I did not buy - I have to admit though, I didn't check the CID before all this). It downloads a branded OTA. BUt the stock system is HTC_Europe (as it should be) so the OTA doesn't install anymore. The backup form the HTC_Euope Lollipop however doens't recognize the SIM.
Apparently my CID changed. On an S-ON phone. What the ****?
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.
Hi everyone,
I've been researching for a couple days and I'm pretty much ready to root my phone. I have the Bell Canada version. All I want to do is unlock the bootloader, root it, and install Xposed. From what I can tell, I shouldn't have any problems. But I've been seeing a lot about the radio not working, and I'm concerned I might be screwing myself since there is no RUU for the international version of the HTC 10. Which means, as far as I can tell, that if I screw up my phone there's no going back. I haven't seen many threads addressing specifically the Bell/international version, so I want to be clear before I try anything. I have much experience rooting phones, but I'm new to HTC and it seems much more complicated and risky.
So I have a few questions:
- Has anyone successfully rooted the Bell/international variant of the HTC 10 without issues or radio loss?
- Further, has anyone gotten Xposed framework working?
- Is there a way to revert the phone back to stock/fully functioning in the case that the radio stops working or some other problems arise?
Thanks in advance.
I plan on getting one soon and root it. Would be fun to know if someone did it already.
Sent from my Nexus 5 using XDA-Developers mobile app
Found some information on reddit
https://www.reddit.com/r/htc/comments/4tap0f/bell_stock_rom_htc10/d5lszn8
Were you guys able to root and/or flash a ROM on the Bell model?
I am running Leeroid ROM on my Bell HTC 10. Very easy. Unlock bootloader, install twrp with fastboot and you're gold
Xposed works great too. Never had an issue with radio since rooting. I do have a minor problem which only started happening since i removed the rom encryption and my lte wont work until i go into mobile networks and reset apn to default. Once i do that my lte works like normal until i reboot and have to repeat the 10 second process.
And you can always save a twrp backup of your stock ROM if you want to go back.
sweet, thanks for confirming! Did you manage to get a Sharp display by chance? I have a feeling that literally all of the Bell ones are of Tianma.
Bell user here. I'm on stock rom with latest update with some mods. Phone runs pretty good now,
1.90.666.4 OS
Sunshine > $25 dollar paypal (S-OFF)
TWRP for recovery
AcoustiX_Audio_ZeroInfinity_v30 (make speaker louder)
ElementalX-HTC10-0.25-Sense (Plus $3.00 EX Kernal Manager Paypal)
Tweaked_pnp_thermal_ivicask_v19
I've rooted my HTC 10 using sunshine. I'm currently on Leedroid's ROM.
As anyone successfully restored to stock? I need to do so to unlock. I want to use a different SIM.
There was a bell ruu somewhere around. Just run that and you'll be back to full stock.
Do you have a link?
No but @xunholyx might be able to help
I have the 2.41.666.3 RUU. You can download it here.
Thanks a lot. I also need a stock recovery. Is it included?
Yes. RUUs always contain the stock recovery. They restore everything to stock. Also, it will wipe your phone, so backup anything you don't want to lose.
So I have an unlocked HTC 10. a while back I managed to do all the good stuff to make it work with Verizon. I don't remember all of the things I did, but safe to say the needed things for it work on Verizon through the #*#*4636*#*# menu. Fast forward a year later, I'm still on 6.0.1 and I would like to know how I can go to the latest and greatest update from Android while being able to connect to the Verizon signal. I haven't kept up with anything from here so pardon my lack of knowledge.
Xeazlouro said:
So I have an unlocked HTC 10. a while back I managed to do all the good stuff to make it work with Verizon. I don't remember all of the things I did, but safe to say the needed things for it work on Verizon through the #*#*4636*#*# menu. Fast forward a year later, I'm still on 6.0.1 and I would like to know how I can go to the latest and greatest update from Android while being able to connect to the Verizon signal. I haven't kept up with anything from here so pardon my lack of knowledge.
Click to expand...
Click to collapse
So you must be s-off in that case and you simply flashed the Verizon radios, right?
You can probably update your unlocked 10 to the latest software, and then redo the steps you originally did to get it to work on verizon.
To update:
If you were never rooted and didn't ever modify your system partition, make sure you have stock recovery and take the OTA update.
If you are rooted, but have an untouched system backup on hand, restore it as well as stock recovery and then take the OTA.
If you are rooted with no backup, or if the above options fail, the easiest and cleanest way is to backup your phone contents and run the latest Nougat ruu which will bring you to fully stock and updated.
Other option, since you're s-off, is to flash the OTA "manually" with twrp and through fastboot. Look for instructions in the twrp thread faq.
Tarima said:
So you must be s-off in that case and you simply flashed the Verizon radios, right?
If you are rooted with no backup, or if the above options fail, the easiest and cleanest way is to backup your phone contents and run the latest Nougat ruu which will bring you to fully stock and updated.
Other option, since you're s-off, is to flash the OTA "manually" with twrp and through fastboot. Look for instructions in the twrp thread faq.
Click to expand...
Click to collapse
No. To convert US Unlocked to VZW we had to manually set the CID and then run the Verizon RUU. If we flash the latest N RUU, I don't think that'll work on VZW. Last I checked (which was last fall TBH) VZW was on a different and older branch than the Unlocked latest head codeline. We should be able to run the latest VZQ RUU assuming someone has made one. I'm also looking for this. I'll update this post if I find it.
drumz0rz said:
No. To convert US Unlocked to VZW we had to manually set the CID and then run the Verizon RUU. If we flash the latest N RUU, I don't think that'll work on VZW. Last I checked (which was last fall TBH) VZW was on a different and older branch than the Unlocked latest head codeline. We should be able to run the latest VZQ RUU assuming someone has made one. I'm also looking for this. I'll update this post if I find it.
Click to expand...
Click to collapse
Where does the OP say he converted to VZW variant?
There are two ways to get unlocked to work on VZW, one is to flash just the modem and the other is a full Vzw conversion. Based on the fact he states he had to go into the secret menu, my guess is that it was the former which is why I asked....
FYI latest vzw ruu can be found on the Verizon HTC 10 forums.
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
Interesting, didn't know you could get VZW to work without the full conversion. That was the route I went, and despite it, my phone still shows up on Verzion as a 'Non Verizon Device' (Everything works though). Thanks for the link to the RUU though!