Phone HTC One M9
Bootloader Unlocked
Recovery: TWRP 2.8.7.0
Android: version 7.0
Carrier: AT&T
I unlocked my bootloader by following instructions on htc dev. then i put twrp 2.8.7.0 then i installed supersu 2.48 which ended in my phone stuck in start up at the htc logo screen. then i installed stock then made a backup. then i installed in this order until one worked supersu 2.67, 2.68, then 2.74 it worked it loaded up i installed root check and it was rooted. after rooting i did not have mobile data and if i tried to make phone calls it would crash and i would not be able to hang up forcing my phone to restart by holding down all 3 buttons until it reset. I then went back into twrp and restored my backup and it worked again.
I then installed supersu 2.78 with the same problem.
For those too lazy to read it all \/ \/ \/
QUICK READ
Unlocked bootloader, installed twrp, installed supersu, versions before 2.74 did not work
Phone no sim detected only when rooted.
Works fine when unrooted.
I am a mechanical person. I've rooted phones since 2011 but like 1 every 2 years. Even after all that I still know nothing. So don't flood me with hacker talk I wont understand. Im not so up to date.
(The only root i know fluently is clock work mod 2011 for droid charge.)
Thank you so much.
nobody?
Not a single reply. I swear someone else has rooted the htc one m9. If they could just tell me what recovery and supersu they used for android 7 that would be enough.
I am having the same issue. Surely someone else has stumbled upon this issue before us...
Related
Hi guys
I just got my wife a Samsung Galaxy S3 I747 for ATT using Straight Talk. I purchased one for my self about 3 months ago, same model. Both were purchased used, mine had 4.1.2 and my wife's has 4.1.1. I rooted and installed CWM Recovery on mine. I wanted to update my wife's to at least 4.1.2 like mine or even 4.1.3.
From my understanding, once you root and install a recovery mod, such as TWRP or the ClockWorkMod Recovery, that your phone will not be able to update via your service provider.
The problem is, I got her phone yesterday, and I tried to update it, but it kept saying it was at the latest update/firmware. I even installed Kies, but it reported the same thing. After a few hours, I decided I would root it and install TWRP and maybe install a new ROM with the FW on it later. Well, this morning, the phone reported that an important update was available. Somewhat confused, b/c I thought it couldn't be the FW b/c yesterday it said the phone was at the latest FW, and plus the fact the update is, as I thought, refused by the service provider or phone, when it is rooted or a recovery mod is installed. When it finished, of course it asked to reboot. I was curious how this was going to play out.
When it rebooted, it loaded the TWRP Recovery. Being still new to all this, I wasn't sure how to proceed, so I clicked the reboot button, but nothing happen, so I tried the shutdown button. The phone powered off with no issues. I turned it back on and it loaded successfully to the home screen. I checked the status of the update, and it said it failed. No surprise there, I'm just happy it didn't brick her phone during the process.
Is this normal? Should I just disable updates from my provider? Is it possible to install the update and then just reapply the root and recovery mod?
Thanks
Mike
Modify_inc said:
Hi guys
I just got my wife a Samsung Galaxy S3 I747 for ATT using Straight Talk. I purchased one for my self about 3 months ago, same model. Both were purchased used, mine had 4.1.2 and my wife's has 4.1.1. I rooted and installed CWM Recovery on mine. I wanted to update my wife's to at least 4.1.2 like mine or even 4.1.3.
From my understanding, once you root and install a recovery mod, such as TWRP or the ClockWorkMod Recovery, that your phone will not be able to update via your service provider.
The problem is, I got her phone yesterday, and I tried to update it, but it kept saying it was at the latest update/firmware. I even installed Kies, but it reported the same thing. After a few hours, I decided I would root it and install TWRP and maybe install a new ROM with the FW on it later. Well, this morning, the phone reported that an important update was available. Somewhat confused, b/c I thought it couldn't be the FW b/c yesterday it said the phone was at the latest FW, and plus the fact the update is, as I thought, refused by the service provider or phone, when it is rooted or a recovery mod is installed. When it finished, of course it asked to reboot. I was curious how this was going to play out.
When it rebooted, it loaded the TWRP Recovery. Being still new to all this, I wasn't sure how to proceed, so I clicked the reboot button, but nothing happen, so I tried the shutdown button. The phone powered off with no issues. I turned it back on and it loaded successfully to the home screen. I checked the status of the update, and it said it failed. No surprise there, I'm just happy it didn't brick her phone during the process.
Is this normal? Should I just disable updates from my provider? Is it possible to install the update and then just reapply the root and recovery mod?
Thanks
Mike
Click to expand...
Click to collapse
It is perfectly normal. You described the expected sequence for a phone with any custom recovery. OTA updates download then reboot into stock recovery. Absent that ..what you said.
For your update path, I. urge you to visit xda's i747 forum & read up on the controversy & pitfalls of AT&T's OTA 4.3
Look out for:
locked bootloader
Knox Warranty bit
one way upgrade
(on pain of brick)
It's different this time around.
Hello!
A few weeks ago, HTC sends me an update to fix the Heartbleed Bug from Android 4.1. On my device I have root and Xposed. If I install the update, would it remove my root and Xposed? It's my first Android Update after rooting
Thanks,
Weely_XD
I think you have to go back to full stock (Rom,recovery,bootloader locked) to update, so yes update remove root.
Could someone that installed this confirm if root was lost or not?
Thanks!
I will not be changed
romy25 said:
I will not be changed
Click to expand...
Click to collapse
of course not, but what about your phone, LOL
Well, I went ahead and installed the stock recovery and this OTA-update.
Everything seemed fine so I re-installed a new copy of TWRP (same version number as I had before)... Confused me totally. It was asking me to root again as soon as I quit recovery, which I did a few times... But I could never finish the installation of SuperSU. It always failed...
I was messing around with this for 2 days, until I for some reason tried to install TWRP from another "old" file I found on my computer (the exact same file I used when i rooted my phone the first time).
Now everything worked fine...
I guess the other recovery image was corrupt, incorrect, or something else...
Well, the mess was sorted out at least, and I still have root, did not have to reset my phone, and everything else seems to be OK.
Thanks! :good:
Hi guys. It's been a pretty long time since i have rooted and installed a custom recovery on an android (however i do have a good amount of past experiences with other devices) but i just recently got the LG G3 from verizon(VS985) and have rooted it on Lollipop 5.0.1 successfully. I then did a lot of research on getting TWRP 2.8.6.1 so that i can get a custom ROM installed, however i have followed every step required to install it and i cannot get it to work. everything goes just fine while using ADB but after it is all said and done and the phone tries booting into TWRP it goes to the LG start up screen and then goes black and flashes red and blue on the notification light. It continues to do this until i hold down the volume down and power button together and then it just reboots like normal.
Has anyone seen this before and know where I may have done something wrong?
I have tried doing the process again thinking that maybe i just did something incorrectly but I came out with the same results
If there is anymore information that you need from me feel free to ask
Thank you for your help!
Ok so i figured out what was wrong. I did not realize that TWRP wouldn't work on 5.0 and that i had to downgrade to 10b to get it working. However now that i have a new rom installed and running I can't get the IR sensor to work. Are there some sort of drivers that i need to download? Thank you guys for your help in advance
Can't you just replace the a boot partition with an earlier one, v10b maybe, then you can install bumped TWRP latest version and that will work in rooted Lollipop ?
Sent from my VS985 4G using Tapatalk
Just search in the Play Store for VS985 TWRP autorec, that app is supposed to install TWRP properly under any version.
Hey there fellow XDA forum members, I am currently running stock 6.0 Marshmallow on my Moto E XT1527 Surnia (Telus) and have that squid build of TWRP and it runs fine. Now here's where I run into issues... I've tried twice now to flash the SuperSU Update zip but when I boot into recovery TWRP doesn't ask me if I want to install SuperSU, and not sure but I didn't check the box for "keep read only" and just swiped right; does that matter? Anyhow; back to my OP, is there a way to get SuperSU Update to stick? Cause after flashing the zip as aforementioned, and reboot system, it just hangs at the white warning bootloader unlocked screen...why?? And I heard about systemless root for 6.0 but honestly don't know where to begin, and thought there would've been a tutuorial or a guide but have yet to find one, any help is greatly appreciated, thanks!
I posted this recently.. [XT1527] Install Systemless Root on Marshmallow
It was on page 2
I used that method and i have the same phone as you.
It's still working good for me but you may want to toggle namespace separation on or off
if some app's give you issues.
If you have Busybox installed then make sure it's using a recent newer version that is fixed for this issue too.
Trying to root my surnia for the first time. I was following these to get my phone rooted using twrp (already unlocked the bootloader).
https://forum.xda-developers.com/moto-e-2015/development#root (the yt video)
https://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726
TWRP successfully boots. When rebooting it asks if I want to install SuperSU, I swipe yes. Reboots. Gets stuck at bootloader warning with the phone at about 35-40 degrees Celsius. I've left it for 30 minutes even which most forums say it should only take 5-10 minutes for the first startup so I assume I'm softblocked. I was able to restore to stock and retry but same result. I would really appreciate any advice you have for me.
Model is a Moto E (2nd gen) 4G LTE with Marshmallow (6.0) installed.
EDIT: Fixed by downgrading stock rom to 5.1.1, and redoing the whole procedure. Don't know how to close thread.
necrokamios said:
Trying to root my surnia for the first time. I was following these to get my phone rooted using twrp (already unlocked the bootloader).
https://forum.xda-developers.com/moto-e-2015/development#root (the yt video)
https://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726
TWRP successfully boots. When rebooting it asks if I want to install SuperSU, I swipe yes. Reboots. Gets stuck at bootloader warning with the phone at about 35-40 degrees Celsius. I've left it for 30 minutes even which most forums say it should only take 5-10 minutes for the first startup so I assume I'm softblocked. I was able to restore to stock and retry but same result. I would really appreciate any advice you have for me.
Model is a Moto E (2nd gen) 4G LTE with Marshmallow (6.0) installed.
EDIT: Fixed by downgrading stock rom to 5.1.1, and redoing the whole procedure. Don't know how to close thread.
Click to expand...
Click to collapse
Don't let two install SuperSU. Use an up to date flashable zip.
amarc78 said:
Don't let two install SuperSU. Use an up to date flashable zip.
Click to expand...
Click to collapse
The root process went well when I used a 5.1.1 stock ROM. I figured that the reason that in future versions of TWRP they remove the install SuperSU option if system is 6.0 is because it doesn't work with the TWRP installer. Also, this may sound stupid, but I have no idea how to load it onto a memory partition so it can flash xD. I'm a noob after all.