Related
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.
Entropy512 said:
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.
Click to expand...
Click to collapse
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?
khunkami said:
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?
Click to expand...
Click to collapse
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
If you install a TWRP image using heimdall or odin it should persist - the dd method listed in http://teamw.in/project/twrp2/124 should work too. (i337 is the AT&T/Rogers Note2, right?)
Omni shouldn't be flashing recovery on this device (Omni only changes recovery on devices that can't change kernel without changing recovery - like the I9100/I777/N7000 and many Sonys), but even if it is, it should be flashing a TWRP build...
Entropy512 said:
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
Click to expand...
Click to collapse
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,
Gertlily said:
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,
Click to expand...
Click to collapse
I am just curious. Why does Omni Rom unroot the device after system-update?
khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It is not only the issue on OmniROM but on (almost) every ROM, I've had the same on cyanogen and Samsung Stock.. So flashing it yourself is better.. Hope this bug will get fixed somewhere in the future.
Bye,
Sent from my Nexus 7 using Tapatalk
khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It's because Omni doesn't have root yet. It's on the to do list. The easiest way is to install SuperSU to system, then install the back up script. That way you'll keep root through updates.
khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.
AKdballs said:
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.
Click to expand...
Click to collapse
You shouldn't be using CF-Auto-Root if you have a custom recovery (which you need in order to install Omni). Just flash SuperSU in recovery.
I knew something wasn't quite right but I did it that way because it works. I have downloaded su onto the SD card, as well as the latest nightly build of Omni. Can I install the new nightly with TWRP, and add su as a second zip to install at the same time? Or should I flash them separately?
Sent from my SGH-I337M using xda app-developers app
So I have converted my Note for to developer and have an unlocked bootloader and installed TWRP through Odin. I have tried a few times to gain root by installing SuperSU through TWRP, but it just manages to keep looping my phone after it installs. Is there a way to install SuperSU without doing it through TWRP as I think that's the problem?
Also I wouldn't be able to install a ROM until I gain root correct?
Thank you for all of your help
adriel161 said:
So I have converted my Note for to developer and have an unlocked bootloader and installed TWRP through Odin. I have tried a few times to gain root by installing SuperSU through TWRP, but it just manages to keep looping my phone after it installs. Is there a way to install SuperSU without doing it through TWRP as I think that's the problem?
Also I wouldn't be able to install a ROM until I gain root correct?
Thank you for all of your help
Click to expand...
Click to collapse
install a prerooted rom of your choice through twrp recocery.. they will come pre rooted..
if not i have a feeling youre not using the correct supersu zip to root the device..
have you flashed cf auto root?
Sent from my SM-G925V using XDA-Developers mobile app
Flash a prerooted rom or flash the Emotion-TW-5.1.1-nightly-r21 kernal + BETA-SuperSU-v2.71-20160331103524
elliwigy said:
install a prerooted rom of your choice through twrp recocery.. they will come pre rooted..
if not i have a feeling youre not using the correct supersu zip to root the device..
have you flashed cf auto root?
Sent from my SM-G925V using XDA-Developers mobile app
Click to expand...
Click to collapse
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
refusedchaos said:
Flash a prerooted rom or flash the Emotion-TW-5.1.1-nightly-r21 kernal + BETA-SuperSU-v2.71-20160331103524
Click to expand...
Click to collapse
Cool, thanks got it to work!
Now my only issue is that once I was rooted and everything I wanted to flash CM13.
I shut down my phone and went into TWRP, I restored and the tried to install CM13+Gapps and it just went into a black screen and started over. I rebooted, but now I'm in a boot loop.
So I am going to start over and regain root, but do you know if I did something incorrectly? How would I go about it? Thank you.
shusuke028 said:
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
Click to expand...
Click to collapse
Settings-/developer options/ enable root
Sent from my SM-N920F using XDA-Developers mobile app
adriel161 said:
Cool, thanks got it to work!
Now my only issue is that once I was rooted and everything I wanted to flash CM13.
I shut down my phone and went into TWRP, I restored and the tried to install CM13+Gapps and it just went into a black screen and started over. I rebooted, but now I'm in a boot loop.
So I am going to start over and regain root, but do you know if I did something incorrectly? How would I go about it? Thank you.
Click to expand...
Click to collapse
Hmm im not sure (i'm running stock + Emotion kernel). But if you want to go CM13, you dont need to flash the Emotion kernel.
EDIT: you did a full factory reset (via recovery) before you flashed CM13 right?
refusedchaos said:
Hmm im not sure (i'm running stock + Emotion kernel). But if you want to go CM13, you dont need to flash the Emotion kernel.
EDIT: you did a full factory reset (via recovery) before you flashed CM13 right?
Click to expand...
Click to collapse
Yes I did, but I had the Emotion Kernal installed. That's probably why, I'm going to attempt right now to flash SuperSu then CM13.
[/COLOR]
shusuke028 said:
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
Click to expand...
Click to collapse
Cm13 is pre-rooted, root is embedded in the rom, superSu isn't needed, you can turn it on in developer settings.
adriel161 said:
Yes I did, but I had the Emotion Kernal installed. That's probably why, I'm going to attempt right now to flash SuperSu then CM13.
Click to expand...
Click to collapse
Yea, try with stock kernal. I don't think you need to flash SS when flashing CM13 though
For me, when I try to flash CM13 through TWRP it'll get to saying "MTP Enabled" in the terminal window, then black screens for a few seconds, and reboots to TWRP. It also doesn't flash CM13, and I'm at a loss for what to do
Orange Offizier said:
For me, when I try to flash CM13 through TWRP it'll get to saying "MTP" in the terminal window, then black screens for a few seconds, and reboots to TWRP. It also doesn't flash CM13, and I'm at a loss for what to do
Click to expand...
Click to collapse
Which version of TWRP do you have? And did you make sure it was a vzw build?
Reminon said:
Which version of TWRP do you have? And did you make sure it was a vzw build?
Click to expand...
Click to collapse
I have TWRP 3.0.2, and it is a vzw build
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Xdevillived666 said:
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Click to expand...
Click to collapse
Screenshots guys
I can confirm CF-Autoroot works without flaws!
I used the Nexus Root Toolkit and that worked a charm, got recovery and root installed easily.
What recovery are you guys using? latest 3.0.2-3?
Krenol said:
What recovery are you guys using? latest 3.0.2-3?
Click to expand...
Click to collapse
I'm using 3.0.2-1 but I have heard people say 3.0.2-2 works as well. Hope that helps
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
RonnellTapawan said:
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
Click to expand...
Click to collapse
It would seem so. Until I decrypted, I wasn't able to keep it permanently installed.
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Razeer123 said:
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Click to expand...
Click to collapse
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
I rooted at first with PHH suhide and the only thing I couldn't do was change system files, as expected. Flashed back to stock, updated to dev preview again (clean slate) and installed magisk v8 and root. Everything is working fine and dandy.
Xdevillived666 said:
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
Click to expand...
Click to collapse
Yeah, I think everyone have this number. I suppose the x.x.1 means Security Patch number, but I'm not sure.
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
ToothTooth said:
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
Click to expand...
Click to collapse
You can. Just before installing , reinstall stock recovery and then install ota or use flash fire
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Morning all
Just checking in to say I've been running this 7.1.1 preview for over 24 hours, without so much as a slight hiccup. It's very smooth and fluid. I haven't bothered rooting or anything yet as the phone runs beautifully as is, but no doubt I will tinker when I get back from a short break. Only disappointing thing is android pay not working due to unlocked bootloader
Anyone has no-force decrypt boot img, coz seems like device is encrypted, as Im stuck with TWRP(3.0.2-1) logo
odunke01 said:
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Click to expand...
Click to collapse
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
odunke01 said:
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
Click to expand...
Click to collapse
What are you using su hide for?
It was for pokemon go.
Although I have reverted to PN on 7.0 as I was having other issues. Root (edit:and recovery) wasn't holding after reboot and my hosts file kept disappearing.
I also missed the night light.
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)
dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread
Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt
Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip
i am very frustrated, I get into TWRP again and again no matter what i do. Bootloader unlocked, I can finish the dirtycow rooting, flash SU, and a ROM. And then.
I am greeted by TWRP.
There is this one time I booted up the WETA rom, i didn't like something so I reflashed the room, thus beginning my TWRP bootloop nightmare...
Are you saying that after flashing rom your device is rebooting constantly into twrp?
Team DevDigitel said:
Are you saying that after flashing rom your device is rebooting constantly into twrp?
Click to expand...
Click to collapse
yes
dangercl0se said:
yes
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3
Its a common issue on the ls997
Related to having been on older softwear and
Your phone dl the update.zip and is causing this
Need to delete fota and misc directories
I have walkthrough in above link.
thanks so much. i really appreciate that
i did dive into the directories and can't find most of them, i will try again with the fastboot method. when do i do that? after i completed root and flashed super su?