Develop Bugs

HTC M8 Hong Kong Help (No version_main)

Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!

panchizzles said:
Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
Click to expand...
Click to collapse
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.

xunholyx said:
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
Click to expand...
Click to collapse
Thanks for the reply!
Do I have to flash the latest TWRP version before proceeding?

Recoveryproblems after Android 6.0 Update

Hello,
some days ago I've installed Android M.
If i try to boot recovery now i just get the dead droid.
~5 Mins later it just reboots to normal mode.
Flashing TWRP didn't help
Any suggestions - never had something like this before?

J3n50m4t said:
Hello,
some days ago I've installed Android M.
If i try to boot recovery now i just get the dead droid.
~5 Mins later it just reboots to normal mode.
Flashing TWRP didn't help
Any suggestions - never had something like this before?
Click to expand...
Click to collapse
did you installed Android M on Verizon device?

ajeevlal said:
did you installed Android M on Verizon device?
Click to expand...
Click to collapse
No. updated with LG Bridge (h815)

J3n50m4t said:
Hello,
some days ago I've installed Android M.
If i try to boot recovery now i just get the dead droid.
~5 Mins later it just reboots to normal mode.
Flashing TWRP didn't help
Any suggestions - never had something like this before?
Click to expand...
Click to collapse
TWRP requires an unlocked bootloader which the VS986 (Verizon G4) has not been able to do. I saw a thread somewhere about installing MM on any G4, but figured I could wait a while and be happy with 13B. What software version were you BEFORE installing 6.0 MM? Can you not go back to 13B by placing a system image on your phone and flashing that in recover/command mode? I have not read much about what MM does with your kernel/bootloader, so DEFINITELY check that before you think about going back to 5..1 LG has anti-rollback stuff backed in that can brick your phone if you try going to a previous version, but not sure how the 6.0 MM flash handles that.
Edit: Well, that answers that question, not a Verizon phone. lol.
Which H815 version do you have? VERY IMPORTANT because not all H815 are made the same. Depending on the region is what determines if you can actually unlock your bootloader.

woozzy101 said:
TWRP requires an unlocked bootloader.
Click to expand...
Click to collapse
Bootloader is unlocked. Had 5.1 before with TWRP & Co. working.
The CM Wiki is exactly what I did. Installing Android 6 and then flashing recovery with adb.
Can't link due newbie but cyanogen wiki /w/Install_CM_for_h815

Now tried to boot directly into recovery after flashing.
I'm just getting the Stock recovery after a sucessful flash of twrp?

Root new Android 7 stock ROM

Hi everyone!
New Android 7 Developer RUU is out. I remember that there were several problems with the last Android 6 security updates in September and October. So it wasn't possible to root with the latest SuperSU.zip
Instead you had to use an older version and update to the latest version with Play Store later.
Before I flash the Android 7 RUU, I would like to know if anyone already has experience with rooting latest Stock ROM?
Any problems which occurred? And if the root process was successful, which SuperSU Version have you used? Thanks in advance!

Njoatun said:
Hi everyone!
New Android 7 Developer RUU is out. I remember that there were several problems with the last Android 6 security updates in September and October. So it wasn't possible to root with the latest SuperSU.zip
Instead you had to use an older version and update to the latest version with Play Store later.
Before I flash the Android 7 RUU, I would like to know if anyone already has experience with rooting latest Stock ROM?
Any problems which occurred? And if the root process was successful, which SuperSU Version have you used? Thanks in advance!
Click to expand...
Click to collapse
I've used this to root stock Nougat ROM and it worked fine https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Anyway make a backup.. just in case it doesn't work
EDIT: It will reboot the phone at least 2 times before booting into system

Mat08.cc said:
I've used this to root stock Nougat ROM and it worked fine https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Anyway make a backup.. just in case it doesn't work
EDIT: It will reboot the phone at least 2 times before booting into system
Click to expand...
Click to collapse
Do we need to modify system in twrp? before installing this?

shaygia said:
Do we need to modify system in twrp? before installing this?
Click to expand...
Click to collapse
No there's no need, at least I didn't change anything and it worked well

I just wanted to add this as a note as I did not see anyone else having these issues in nougat (7.0). Do not install SuperSU 2.78-201609011115. If you do your mobile data option in the notification bar will be grayed out. Your cell signal will have a slash through it and cell signal will no longer work. I do not know if other versions of SuperSU will also cause this symptom.
If this happens to you restore from a backup in recovery or if need be run the RUU again.
Mat08.cc's linked version of SuperSU does work!!!! Thanks!

My m9 doesn't want to upgrade. After it download the Nougat ,it says that I'm running modified system. My phone is att but converted to developer edition. The way I was updating my phone each time so far was with RUU file and I didn't gave any issues until now. Please help . Thanks in advance.

dohcvtec said:
My m9 doesn't want to upgrade. After it download the Nougat ,it says that I'm running modified system. My phone is att but converted to developer edition. The way I was updating my phone each time so far was with RUU file and I didn't gave any issues until now. Please help . Thanks in advance.
Click to expand...
Click to collapse
Excuse me, I did not understand.. The phone has received the upgrade but can not install it?

Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!

dohcvtec said:
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
Click to expand...
Click to collapse
Have you installed this one << https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip >> ? (2.78-SR5)

dohcvtec said:
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
Click to expand...
Click to collapse
Definitely an incorrect SuperSU apk. Use the one in OP of http://forum.xda-developers.com/one-m9/general/nougat-coming-t3513698

Okay. Will try and get back to you. Thanks
P. S. Am I the only ine who is experiencing Messages failing and sending reports to HTC? Ever since I switched to Nougat, every time when I receive/send a text the app fails and when I try to access notifications it fails automatically as well. Ideas? Thank you

idontkn1 said:
Definitely an incorrect SuperSU apk. Use the one in OP of http://forum.xda-developers.com/one-m9/general/nougat-coming-t3513698
Click to expand...
Click to collapse
Reporting back:
After installing the SuperSU that you gave, everything works normally. Thank you very much.
There is an update which my phone didn't want to install. It said that the update is for himaulatt and my phone is himaul. Is it because phone is rooted and with twrp recovery? When I install the update manually via RUU from laptop, works fine. It just pisses me off cause I have tk start from scratch with my phone but update is successful. Had this issue for a while now amd was trying to figure it out. I really don't want to keep wiping the phone every single time there is an update. Thank you in advance.
Best Regards

dohcvtec said:
Reporting back:
After installing the SuperSU that you gave, everything works normally. Thank you very much.
There is an update which my phone didn't want to install. It said that the update is for himaulatt and my phone is himaul. Is it because phone is rooted and with twrp recovery? When I install the update manually via RUU from laptop, works fine. It just pisses me off cause I have tk start from scratch with my phone but update is successful. Had this issue for a while now amd was trying to figure it out. I really don't want to keep wiping the phone every single time there is an update. Thank you in advance.
Best Regards
Click to expand...
Click to collapse
You might want to read the latest posts in the TWRP thread. The important part starts here.

Flippy498 said:
You might want to read the latest posts in the TWRP thread. The important part starts here.
Click to expand...
Click to collapse
I just read the threads you gave me. I understood the process. I will search for the zip file cause this seems to stop me right now. Everything else makes sense from top to bottom. Thank you very much once again.

Doesnt rooting void official oxygen updates?

Hello, so i 've been on oxygen 4.0 on my OnePlus 3 for about a week now, and flashed that version via new TWRP. I am rooted with custom recovery. But just now browsing website, and I got a notification that update is available to 4.0.2 lol. OFFICIAL UPDATE. I thought that it is not possible to get official updates when rooted/with custom recovery. Is there something wrong going on? Should I Update? When I was on Oxygen 3.2.8 I wanted to get update using VPN, but had no luck, notification never appeared. Should I officially update this official oxygen 4.0.2 version? is it safe? I don't want to brick my OP3 :/

Don't, I was on the same position and I did and now I have soft bricked my phone and I am here looking for a solution.

LonerIM said:
Don't, I was on the same position and I did and now I have soft bricked my phone and I am here looking for a solution.
Click to expand...
Click to collapse
Thanks. I knew something sketchy is going around lol. I will have to update using twrl method then. This Update is probably only for stock recovery.

LonerIM said:
Don't, I was on the same position and I did and now I have soft bricked my phone and I am here looking for a solution.
Click to expand...
Click to collapse
just found out that flashing anything under 1gb officially, while you are on TWRP will lead on soft brick. So you will have to flash full OTA zip on your TWRP recovery to fix. BTW, what is your TWRP version? thanks

IAmLucky said:
Thanks. I knew something sketchy is going around lol. I will have to update using twrl method then. This Update is probably only for stock recovery.
Click to expand...
Click to collapse
Actually, I just fixed it and came here to let you know , all I needed to do (I am not an expert on these stuff so it took me a while), is to install an updated unofficial TWRP to avoid the pattern bug, because it kept TWRP from reading my internal storage, once I fixed that the phone turned on with the newer 4.0.2 version.

LonerIM said:
Actually, I just fixed it and came here to let you know , all I needed to do (I am not an expert on these stuff so it took me a while), is to install an updated unofficial TWRP to avoid the pattern bug, because it kept TWRP from reading my internal storage, once I fixed that the phone turned on with the newer 4.0.2 version.
Click to expand...
Click to collapse
which twrp version?

Updating to nougat

Hello All!
I'm sorry if this has been asked before but I'm trying to install nougat on my phone and having some great difficulty.
So far my phone is flashed and I was running TWRP 3.0.2 however every time i try to flash a lineage 14.1 based rom it would never work. (tried straight lineage 14.1, nutOS, DOT) none of them worked (wiped the phone clean, then received error 7, removed the assert lines that let in install but just perpetually boot looped) . My many a google searches makes me believe that that particular version of TWRP does not work with nougat. but that's the only version I am able to get working. any newer version of TWRP gets stuck in a perpetual boot loop.
So with that said, if my suspicious are correct and i need a newer version is there anything I'm missing to install a newer version of TWRP? if 3.0.2 is a good enough version to install nougat based rom's what am I missing on that end?
Any help at all would be greatly appreciated! and Thanks in advance!
Ninja edit: I'm runnnig the Z00A (Z551ML) and i've been using using roms/images meant for Z00A

I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/

Slent said:
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Click to expand...
Click to collapse
Yup that was it. My google-fu is off as i found my answer from a reddit post (5 seconds after asking this question in reddit...) My issue was that i was still on lolipop, the last OTA update and had no idea asus put out a manual update. worst part is, after unlocking the bootloader installing twrp, THEN installing that oem update, that might have cause my phone to crash mid update so it ended up bricking the phone...
I was able to Frankenstein it back together with old parts that I thought were no good, right now I'm on that last manual update and I gotta fight through a few issues preventing the boot loader from being unlocked.
Anyway you were correct, using the last OTA update updates the bootloader so I was stuck cause of that.