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
Related
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
moose&beer said:
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
Click to expand...
Click to collapse
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
sfobrien said:
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
Click to expand...
Click to collapse
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
sfobrien said:
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
Click to expand...
Click to collapse
No worries. And yeah, I did the OTA, but held off until Google pushed a notification to my N10 for the update. I'll give goomanager a try. Appreciate the replies. Thanks.
This is normal behaviour in a OTA update. Installs a couple of files that, if a custom recovery is installed, reflash stock recovery on reboot. This doesn't happen if you flash a factory image.
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
three west said:
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
Click to expand...
Click to collapse
Thanks - I'll give goomanager a try.
beekay201 said:
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I assumed the same, but I got the same situation as OP, I'll try reinstalling TWRP using Nexus Root Toolkit, or does goomanager have a special functionality for those conditions?
Update: Used NRT to install TWRP in the advanced settings, worked beautifully.
The latest Google OTA's are not successfully installing unless you restore stock recovery fist and some are failing if you are rooted as well.
Best bet if you are running as rooted or custom recovery is to backup first, un-root, restore stock then sideload the OTA. This will save you lots of frustration and heartburn.
It's easy enough to restore stock and to re-root so just make it part of your ota routine.
currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Use goomanager. It's by far the easiest since it's mostly automated.
mjb152 said:
currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Click to expand...
Click to collapse
I just downloaded the latest version of TWRP, booted into the bootloader and loaded the image by
Code:
fastboot flash recovery {insert name of image file here}
. Easy peasy,,,
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
mjb152 said:
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
Click to expand...
Click to collapse
Just use ADB to Fastboot flash recovery. Either Fastboot flash your root file or copy it to your device. If you copy it to your device, then boot to recovery and flash your Superuser or SuperSU .zip. You don't want to restore your backup though if your on the latest OTA now and your backup is the previous OTA.
SwiftKey'ed from my White Note 2 via XDA Premium HD
Wug works well.. Simple too.
Sent from my Nexus 7 using xda app-developers app
theres TWRP flashable zips in the TWRP thread, this is the easiest if you alrady got TWRP
you can use wug to install it for the first time then use goomanager to update it later or TWRP manager to dl manually.
my phone is bootloader unlock, does it mean I can flash the third part recovery like TWRP, and use it?
MY guess yes..
Sent from my LT30p using Tapatalk
allen_ho said:
my phone is bootloader unlock, does it mean I can flash the third part recovery like TWRP, and use it?
Click to expand...
Click to collapse
TWRP will not work on the OTA, yet. However, there is a working CWM in the HD forum. I flashed it to my M and have zero issues with it.
RikRong said:
TWRP will not work on the OTA, yet. However, there is a working CWM in the HD forum. I flashed it to my M and have zero issues with it.
Click to expand...
Click to collapse
I flashed the CWM recovery too...it does boot to recovery
but it seems to be some problem with CM11 package, the assert check shows my device ID is empty so the recovery just abort the installation.
I want to flash CM11-m6 snapshot....any ideas?
falleny said:
I flashed the CWM recovery too...it does boot to recovery
but it seems to be some problem with CM11 package, the assert check shows my device ID is empty so the recovery just abort the installation.
I want to flash CM11-m6 snapshot....any ideas?
Click to expand...
Click to collapse
CM11 won't work if you've updated. Apparently, the boot loader is updated and the ROMs haven't been updated for it.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
CM11 won't work if you've updated. Apparently, the boot loader is updated and the ROMs haven't been updated for it.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Bad news...Looks like i will be stucked in full bloated stock rom for sometime...thank u
falleny said:
Bad news...Looks like i will be stucked in full bloated stock rom for sometime...thank u
Click to expand...
Click to collapse
You have an unlocked BL, just flash SU to get root, and delete/freeze apps. That's pretty much what I did and used Xposed on top of that.
I haven't tried it yet, buy couldn't you just rsd back to an earlier build then flash your custom ROM?
Sent from my XT907 using Tapatalk
I fastboot flash the lastest CWM recovery, but it didn't work for the CM 4.4.2 ROM, and twrp, it didn't work again. why? does the VFW rom change something?
allen_ho said:
I fastboot flash the lastest CWM recovery, but it didn't work for the CM 4.4.2 ROM, and twrp, it didn't work again. why? does the VFW rom change something?
Click to expand...
Click to collapse
None of the ROMs have been updated to work with the new recovery. Just give it time.
RikRong said:
None of the ROMs have been updated to work with the new recovery. Just give it time.
Click to expand...
Click to collapse
what's that mean?
do you mean the third part recovery didn't work cause the VFW rom?
allen_ho said:
what's that mean?
do you mean the third part recovery didn't work cause the VFW rom?
Click to expand...
Click to collapse
It means that none of the ROMs out right now will work with the new CWM. Also, quit trying flash TWRP. TWRP is not compatible with the new KK, yet.
Got it, many thanks
Root
My xt907 Has the OTA 4.4 update and an unlocked BL. I don't have a custom recovery installed anymore. Is it possible to flash SU or superuser and get root with fastboot. If so. Please help! Thanks. I'm ok with flashing CWN if need be. I just want root to install a Xposed and remove bloatware.
Ahoalton said:
My xt907 Has the OTA 4.4 update and an unlocked BL. I don't have a custom recovery installed anymore. Is it possible to flash SU or superuser and get root with fastboot. If so. Please help! Thanks. I'm ok with flashing CWN if need be. I just want root to install a Xposed and remove bloatware.
Click to expand...
Click to collapse
I'm pretty sure you can use fastboot/ADB to sideload zips, though I'm not super familiar with the commands so I wouldn't know how to explain it to you.
I am familiar enough with the commands, but I am unable to find the zips to flash. any help would be great.
Thanks,
Egg all over the face
I was one of the people who thought it would be cool to update to the OTA immediately without waiting and reading... I got the CWM recovery going and rooted stock 4.2.2 , but I really cant wait for TWRP to get updated so I can get back to my Rom, or really any supported Rom would be better then stock. I have only myself to blame.
Eclipse00 said:
I was one of the people who thought it would be cool to update to the OTA immediately without waiting and reading... I got the CWM recovery going and rooted stock 4.2.2 , but I really cant wait for TWRP to get updated so I can get back to my Rom, or really any supported Rom would be better then stock. I have only myself to blame.
Click to expand...
Click to collapse
Looks like the new TWRP is here, but still needs one tweak. Please follow this thread for updates.
http://forum.xda-developers.com/showthread.php?p=53189684
TWRP for KitKat Bootloader
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
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
This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium
mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium
No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that