I recently rooted my HTC One M9. After flashing a few different ROMs (Onyx and SkyDragon) I've noticed that every time I lock my phone it reboots. Ive tried reflashing the ROMs and wiping the caches aswell as all the data. Does anyone have any suggestions on how to fix this?
Apart.abyss said:
I recently rooted my HTC One M9. After flashing a few different ROMs (Onyx and SkyDragon) I've noticed that every time I lock my phone it reboots. Ive tried reflashing the ROMs and wiping the caches aswell as all the data. Does anyone have any suggestions on how to fix this?
Click to expand...
Click to collapse
Those ROMs (IIRC) haven't been updated in awhile, and I believe are still on LP base.
Not sure if this will help.
But are you on the new MM firmware using the LP ROM? Could be the cause.
I'd suggest if you want to stick with one of those ROMs to get on the LP firmware (if not already on it).
Or find a ROM that's been updated to MM and also be on the MM firmware.
andybones said:
Those ROMs (IIRC) haven't been updated in awhile, and I believe are still on LP base.
Not sure if this will help.
But are you on the new MM firmware using the LP ROM? Could be the cause.
I'd suggest if you want to stick with one of those ROMs to get on the LP firmware (if not already on it).
Or find a ROM that's been updated to MM and also be on the MM firmware.
Click to expand...
Click to collapse
Would you happen to have any suggestions?
Apart.abyss said:
Would you happen to have any suggestions?
Click to expand...
Click to collapse
Well, there's AndyBones own Fluent (which I have run for close to two years) and Viper, both of which have been updated to MM bases. You can also run CM if you are wiling to go AOSP.
My M9 (currently on Viper) never has the issue you have described.
hgoldner said:
Well, there's AndyBones own Fluent (which I have run for close to two years) and Viper, both of which have been updated to MM bases. You can also run CM if you are wiling to go AOSP.
My M9 (currently on Viper) never has the issue you have described.
Click to expand...
Click to collapse
Doesn't Viper require something special to flash it? I haven't flashed to much with newer devices.
Apart.abyss said:
Doesn't Viper require something special to flash it? I haven't flashed to much with newer devices.
Click to expand...
Click to collapse
Nothing special vs. any other ROM, just need to be on the latest firmware to flash the latest version.
Related
I got my htc one back in January and immediately rooted it with s-off and installed twrp, since then I have been using this rom and it has worked just fine. But recently I got quite sick of sense and when I tried in stall this rom the phone would not work, I tried cm11 after but it would not flash at all giving me an error every time. I read that I need to update my firmware but Im not really sure what that means, or how to tell what firmware I am on(I thought firmware was the same thing as a rom?)
sorry if this is a stupid question, Im not really that good with technology :L
thewaffleninja said:
I got my htc one back in January and immediately rooted it with s-off and installed twrp, since then I have been using this rom and it has worked just fine. But recently I got quite sick of sense and when I tried in stall this rom the phone would not work, I tried cm11 after but it would not flash at all giving me an error every time. I read that I need to update my firmware but Im not really sure what that means, or how to tell what firmware I am on(I thought firmware was the same thing as a rom?)
sorry if this is a stupid question, Im not really that good with technology :L
Click to expand...
Click to collapse
There were some recent changes to CM11 that require a new recovery. Have you tried the latest version of TWRP?
Where you using the CM11 nightlies or M releases?
durgis said:
There were some recent changes to CM11 that require a new recovery. Have you tried the latest version of TWRP?
Where you using the CM11 nightlies or M releases?
Click to expand...
Click to collapse
I used the most recent nightly at the time, this was on Wednesday. Im on twrp 2.6.3.3, could you or someone link me how to update twrp? goomanager does not work for some reason and those are the only tutorials i can find.
thewaffleninja said:
I used the most recent nightly at the time, this was on Wednesday. Im on twrp 2.6.3.3, could you or someone link me how to update twrp? goomanager does not work for some reason and those are the only tutorials i can find.
Click to expand...
Click to collapse
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
durgis said:
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
Click to expand...
Click to collapse
thank you
durgis said:
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
Click to expand...
Click to collapse
I just updated and it still didn't work :C
thewaffleninja said:
I just updated and it still didn't work :C
Click to expand...
Click to collapse
Where there any errors while installing the rom in TWRP? You might try one of the CyanogenMod snapshots instead of a nightly, they're a bit more stable and well tested. Also, make sure that you backup and wipe when switching between different roms.
http://download.cyanogenmod.com/?device=m7vzw&type=snapshot
I recently decided to get back in the trying customized software after taking almost a year and half break from regularly doing it back on my Nexus S. Everything was going smoothly at first and I choose the latest version of liquidsmooth as first at bat and it worked like a charm until the cellular radio would not turn on. I tried everything I could find and even tried flashing the latest radio while on the rom, but no dice. I had to flash the stock image and it worked again, but when I tried flashing again same problem. I even tried slim rom after my second attempt with liquid and the radio just would not work. Wifi worked like a charm but no cellular at all. Can anyone help me with this. I really liked what I got to play around with on liquidsmooth, but I need my phone to actually function as phone. For now I am back to stock until I can find a solution.
Which stock image did you flash? I recommend
http://forum.xda-developers.com/showthread.php?p=53353625
Lemme guess...you were using twrp to flash 4.4 ROMs
jrebo said:
Which stock image did you flash? I recommend
http://forum.xda-developers.com/showthread.php?p=53353625
Click to expand...
Click to collapse
I did flash that one. It's what I'm running now until I can figure out how to get my custom flashes working.
Skripka said:
Lemme guess...you were using twrp to flash 4.4 ROMs
Click to expand...
Click to collapse
Yes. I read that as long as I used version 2.6.3.3 or higher, it would be fine.
Protoroll said:
Yes. I read that as long as I used version 2.6.3.3 or higher, it would be fine.
Click to expand...
Click to collapse
"would be fine" in the sense that it has been common knowledge since 4.4 CyanogenMod builds started in November 2013...that TWRP does not work on L900 for AOSP-base 4.4, and it never has. And by the looks of things never will, as there's been no progress on L900 TWRP working in months,
Use PhilZ to flash and odds are your radios will magically work.
Skripka said:
"would be fine" in the sense that it has been common knowledge since 4.4 CyanogenMod builds started in November 2013...that TWRP does not work on L900 for AOSP-base 4.4, and it never has. And by the looks of things never will, as there's been no progress on L900 TWRP working in months,
Use PhilZ to flash and odds are your radios will magically work.
Click to expand...
Click to collapse
Alright, thank you for the help. I will try PhilZ and see how it goes.
Has anyone tried this yet? I know there was talk of testing for it?
Wondering the same. I know there's an experimental 64 bit version but I hear there are bugs with it.
Sent From My HTC One (M9)
I've been running it for a couple days now with a few modules installed. No problems to report.
Latest version bootlooped me.
w0rdie said:
Latest version bootlooped me.
Click to expand...
Click to collapse
On a custom Rom or stock?
I've heard about some users having problems with xposed and s-off.
Sent from my HTC One M9
Here on Viper rom for like 2 weeks now, no issues.
Get the 21 version from here: http://forum.xda-developers.com/xposed/xposed-android-5-1-successfully-t3074586
flash it in recovery, install the alpha 2 apk from here: http://forum.xda-developers.com/showthread.php?t=3034811
and done. But be careful, some modules causes bootloops.
(i'm not s-off, so idk if that could indeed be an issue)
(oh i see they updated couple of days ago, don't know if those cause issues too)
(edit: updated my list due to some not needed anymore on venom as they have it in tweaks)
I'm S off and I don't have any issues. I just followed the same instructions that are above.
Be sure to read the Xposed compatibility spreadsheet so you don't install something that isn't compatible.
I'm S-off with ARHD5. Framework installed fine, but I haven't bothered with any mod other than Xprivacy which doesn't yet work. Your priorities may differ.
it works fine on tmobile stock rom with s-on. i had boot loop with s-off though, but have not tried the latest release with s-off yet, but that one works with s-on.
does anyone have a list of modules that will work for the M9.. I know there aren't any sense modules.. but would be nice to know ahead of time what works. Instead of constant bootloop of trial and error"ing" each one.. lol.. hope that makes sense.
nvm found a lollipop list. at these that is a start..
minotauri said:
it works fine on tmobile stock rom with s-on. i had boot loop with s-off though, but have not tried the latest release with s-off yet, but that one works with s-on.
Click to expand...
Click to collapse
S off created a dump file that caused issues or something. There is a flash zip that removes that file posted in one of these threads
@sausje85 do you know of an xposed APM that will work for our m9?
[Cruzer] said:
@sausje85 do you know of an xposed APM that will work for our m9?
Click to expand...
Click to collapse
No sorry, I'm on Viper rom, which has it already.
sausje85 said:
No sorry, I'm on Viper rom, which has it already.
Click to expand...
Click to collapse
yah i'll go straight to that rom as soon as it has wifi calling for tmobile... until then stuck with stock..
I've tried on multiple occasions to install the latest nightly CM13 on my m9 without success.
About a couple months after the phone came out I UNLOCKED BOOTLOADER and ROOTED. I also flashed TWRP v2.8.7.0. Phone Software version: 1.32.710.16
After I did this I could no longer install the latest HTC updates due to my custom recovery. Now I'm done with the lag and bloatware and want to install CM13.
I tried to flash the latest CM13 through ADB and was getting error: assert failed: hima.verify_sbl1... / Error executing updater binary in zip...I also tried installing through TWRP...no luck.
I have come to the understanding that I need to install the lastest firmware from HTC since CM13 is Android 6.0 before I try to flash CM13 again.
I am download the latest firmware update from HTC: RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe
Will this be ok to install as is and will i then be able to flash CM13?
I've been reading that a few people have bricked their phones following this HTC guide and Im scared to do the same.
Any advice? Thank you
you need a firmware for x.xx.710.xx ... you can't install another firmware as long as your phone is not s-offed
DeeZZ_NuuZZ said:
you need a firmware for x.xx.710.xx ... you can't install another firmware as long as your phone is not s-offed
Click to expand...
Click to collapse
Ive just downloaded SunShine and it did not work...any other methods to s-off?
Ant-onov said:
Ive just downloaded SunShine and it did not work...any other methods to s-off?
Click to expand...
Click to collapse
sunshine only works with near stock rom, or stock. for example ARHD or MaximusHD will work fine, not possible on cm13 or any other "hardcoded" custom rom
DeeZZ_NuuZZ said:
sunshine only works with near stock rom, or stock. for example ARHD or MaximusHD will work fine, not possible on cm13 or any other "hardcoded" custom rom
Click to expand...
Click to collapse
I have stock ROM but TWRP recovery. Ill try do SunShine again, otherwise ill try the other methods. Thank you
Ant-onov said:
I have stock ROM but TWRP recovery. Ill try do SunShine again, otherwise ill try the other methods. Thank you
Click to expand...
Click to collapse
Yea either a stock backup or a ROM, doesn't matter. And there are no other ways for s-off
Sent from my HTC One M9 using XDA-Developers mobile app
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
MM MaD said:
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
Click to expand...
Click to collapse
You can do either but ensure two things for avoiding a possible bootloop. One is the TWRP and the other is wiping all except internal storage before flashing the ROM.
You should have the modified TWRP 3.0.2-23.
Wipe, flash ROM and flash TWRP before booting as the existing TWRP is likely to be overwritten by the stock recovery. Speaking from experience!
Though I was going from 3.2.7 to 3.2.8, TWRP was overwritten which I found only after booting and when I tried to get back into recovery.
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
jfodra said:
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
Click to expand...
Click to collapse
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
lekronop said:
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
Click to expand...
Click to collapse
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
jfodra said:
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
Click to expand...
Click to collapse
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
lekronop said:
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
Click to expand...
Click to collapse
Oh okay. Thanks a lot for the clarifications.
jfodra said:
Oh okay. Thanks a lot for the clarifications.
Click to expand...
Click to collapse
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
lekronop said:
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
Click to expand...
Click to collapse
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
jfodra said:
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
Click to expand...
Click to collapse
Yes it does.. That's the reason I unlock the bootloader as soon as I get a new device
i was on freedom os . i am back on stock oxygen os but i have 2 issues.
1) when i got an update to 3.2.7 it showed in german that there is an update even though the language i chose was english
2) The boot animation shows the freedom os splash screen and then the boots into stock. Ihave got the boot animation of stock os but need instructions on how to flash the zip.
Can someone throw light on the above 2 issues?