Database Users

OTA with TWRP?

this may have been asked, but i'm new to the nexus 7. i rooted it right away, and put TWRP on. probably shouldn't have but i like doing nandroids. i was excited for the OTA and want to just install it since my tab got it, but it won't obviously since i've got a custom recovery (duh i should've thought of that..) and i don't want to go flashing roms yet (i like keeping everything stock right away, it's so smooth)
so my question is, is there a way to go back and flash the stock recovery somehow so i can OTA, then put TWRP back on? i can't find the stock file to fastboot flash or anything

You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox

kangy said:
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
Click to expand...
Click to collapse
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?

Alright try this.
Go to SuperSU settings and and click on Reinstall under Cleanup, it will give you a prompt and tell you it will self close and to re-install from the market. (Mine never fully uninstalled which I assume is due to it being flashed to ROM, I checked under the App manager and it only had a downgrade option so) Anywho. If it did uninstall go ahead and redownload it from the market, if it didn't check the market anyway, the Dev published and update for it to help with 4.2 multi users.
Once you get it reinstalled and/or updated from the market go back to the settings and Toggle off Enable Superuser, close the app, re-open and then re-enable superuser. You probably will want to give it a reboot at this point. (Ive restarted my device a hundred times since going to 4.2 from trying to work through the bugs. Once you restart test a root app. I used Adaway for the test. Important, if the app fails or gives an error about not having root, try again. After I went through all of those motions SuperSU was pretty slow for a while with giving root access, usually the second request from the app wakes it up. Since then though it is back to being snappy with zero lag.
Yes, the reason you can't flash TWRP through ROM Toolbox is that requires root. Once you get your SuperSU working try flashing the latest TWRP again, it should only take a few seconds to flash. Let me know how it goes, I'm subscribed to the thread. I may not be the smartest guy on XDA but you are in the same exact boat I was last night!

jayochs said:
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Click to expand...
Click to collapse
First, determine if you have root or not. Open TiBackup, if it opens correctly and you can see all your apps listed, you have root. Otherwise it will say "Failed to obtain root," and quit.
If you have root, then great. If not, you can flash the SuperSU zip in TWRP/CWM: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
I haven't tried flashing superSU, I've always flashed Superuser zip [google "superuser zip"], and then installed superSU from Play store.
Once you have root..
Go to Settings > Security and check allow installation from non-market apps, and uncheck the security feature that checks all apps for being malicious.
Then try it. If you still cannot restore apps, you might have to install them with adb.
I just updated someone's N7 to 4.2, and as usual I backed up everything in TiBackup.
Then I backed up the TitaniumBackup directory [because I had to do a full factory reset].
I then extracted all the .apk.gz files with gunzip. [in linux OR adb: $ gunzip *.apk.gz -- for windows, I suppose you would have to use 7-Zip].
Then I tried to install with pm:
Code:
for i in *.apk; do pm install $i; done
But every one was giving me an error, INSTALL_FAILED_INVALID_URI, I couldn't figure it out. Found a thread said to chmod 755 /data/local, but that did not fix it.
So what I had to do, was on my linux PC:
Code:
for i in *.apk;
do adb install "$i"
done
So I finally was able to batch install my apk files.
after that I restored all apps data.

Nandroid back ups not possible after 4.2 update
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.

Yordan5 said:
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Click to expand...
Click to collapse
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.

mvmacd said:
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
Click to expand...
Click to collapse
NRTK 1.5.5 would not flash the 4.2 custom rom I fed it either. Just kept stalling out with errors that it could not find the zip file.
So I booted into TWRP and flashed it with no problem at all.
I also did backup in TWRP and checked everything but saw no mention that is was a Nandroid backup. How can I be sure?

i'm trying to nandroid back to a 4.1.2 nandroid i have, problem is, twrp has different directories for nandroids in 4.2 than 4.1.2...so it can't find the old nandroids and i can't find the 4.2 dir where twrp stores them now. ugh. such a damn headache for an update that it turns out i didn't want lol

Read my post below, I was having the same problem but got back on 4.1.2. You have to use the twrp explorer and relocate the twrp files since 4.2 moved them.
http://forum.xda-developers.com/showthread.php?t=1992552
Nandroid Downgrade from 4.2 to 4.1.2
Sent from my Nexus 7 using Tapatalk 2

Root may have failed, need help please

This is my first time rooting. I have a Samsung Galaxy Note 3, model SM-N900P. It's running Lollipop 5.0.
I downloaded Odin 3.09, Samsung KIES Captivate, and CWM Recovery. I followed instructions from an article on android.gs, called "How to Root Galaxy Note 3 N900 on Android 5.0 Lollipop using Odin".
I'm pretty sure it went wrong when I had to put the CWM recovery file into Odin. Beforehand, when I tried unzipping the CWM recovery file, I found the contents to be corrupted, so I assumed I wasn't supposed to unzip it. So i left the CWM file unzipped. It was called "n9005-cwm-recovery-6.0.4.7-kk(0125).tar".
So when I ran Odin i just selected that file, and Odin said it worked. My phone asked me if I wanted to root and I said yes. Everything seemed to have been working like the instructions said. And when my phone booted up, and I opened clean master, I found that I could now disable apps from auto-starting, a feature that requires root access. (I didn't actually use this newfound feature, so I'm not sure it actually works.)
But SuperSU wasn't installed, so I found it in the Google Play Store, and upon opening it, I was left with the message: "There is no SU binary installed and SuperSU cannot install it. This is a problem!" and the app closes if I dismisses the message. Also, I downloaded Root Checker, which told me I had not properly rooted. I uninstalled both these apps.
Am I just one missed step away from a complete root? Maybe I unplugged my phone from my computer too quickly? Or have I messed something up? How do I fix it? Do I just proceed to root again normally, or do I have to un-root somehow, or do I do a factory reset, etc? I don't know what I'm doing. If I've given too much information or too little, sorry haha.

pacificpacifist said:
This is my first time rooting. I have a Samsung Galaxy Note 3, model SM-N900P. It's running Lollipop 5.0.
I downloaded Odin 3.09, Samsung KIES Captivate, and CWM Recovery. I followed instructions from an article on android.gs, called "How to Root Galaxy Note 3 N900 on Android 5.0 Lollipop using Odin".
I'm pretty sure it went wrong when I had to put the CWM recovery file into Odin. Beforehand, when I tried unzipping the CWM recovery file, I found the contents to be corrupted, so I assumed I wasn't supposed to unzip it. So i left the CWM file unzipped. It was called "n9005-cwm-recovery-6.0.4.7-kk(0125).tar".
So when I ran Odin i just selected that file, and Odin said it worked. My phone asked me if I wanted to root and I said yes. Everything seemed to have been working like the instructions said. And when my phone booted up, and I opened clean master, I found that I could now disable apps from auto-starting, a feature that requires root access. (I didn't actually use this newfound feature, so I'm not sure it actually works.)
But SuperSU wasn't installed, so I found it in the Google Play Store, and upon opening it, I was left with the message: "There is no SU binary installed and SuperSU cannot install it. This is a problem!" and the app closes if I dismisses the message. Also, I downloaded Root Checker, which told me I had not properly rooted. I uninstalled both these apps.
Am I just one missed step away from a complete root? Maybe I unplugged my phone from my computer too quickly? Or have I messed something up? How do I fix it? Do I just proceed to root again normally, or do I have to un-root somehow, or do I do a factory reset, etc? I don't know what I'm doing. If I've given too much information or too little, sorry haha.
Click to expand...
Click to collapse
1. The custom recovery you installed isn't for your device. Use this ONE.
2. You should downgrade your device coz Cf-Auto-root only is working till android 4.4.4 (KTU84P.N900PVPUDNH7). And root it with this FILE via ODIN.

Joku1981 said:
1. The custom recovery you installed isn't for your device. Use this ONE.
2. You should downgrade your device coz Cf-Auto-root only is working till android 4.4.4 (KTU84P.N900PVPUDNH7). And root it with this FILE via ODIN.
Click to expand...
Click to collapse
So I can't do this on lollipop?

I Don't Know What I'm Doing Anymore!

Hello everyone,
this is my first time posting on the XDA forums after doing a lot of research, so please bear with me if I've missed something painfully obvious. My issue I'm looking to get help with is my AT&T GS4 i337.
Here goes the problem, initially I had the FNJ4 (4.4.4) baseband and build number. I was really excited to try custom ROM's like CM11 or 12. I ended up reflashing the phone via odin with baseband and build number FNB1 with a rootable kernel (titled I337UCUFNB1_TWRootable_Full_Odin.tar 4.4.2). This successfully worked as did using TowelRoot (v3) to root. Since the reflash, I cannot seem to load CWM or TWRP much less access even the factory recovery mode on startup (it goes to the "unable to boot into normal mode" screen). And today, I was messing around with the "Disable Service" app and accidentally unchecked the box to turn off the service for SuperSu (even though I re-checked the box, I still lost root). And now I cant even run the tr.apk file to successfully root again - what I mean is the tr.apk installs and says I have root, but then when I check the root with root checker basic it says the phone has not been successfully rooted.
On a side note, I did find a flashable recovery .zip version of SuperSu (2.46) app to get the app back except now, shortly after startup, the app service turns itself off and I loose SuperSu again. I really don't know what to do.
I have tried messing with Terminal Emulator, Flashify, TWRP manager, ROM manager, ODIN and Titanium Backup to try and get SuperSU (to get root) and the factory recovery mode back (I also tried using Safetrap to install CWM and TWRP without success). The only program I haven't messed with is flashing with Heimdall. Oh yeah, I also tried using SELinux Mode Changer (changed mode to permissive) without any success.
I know this is getting super long, but my initial intent was just to be able to run CM11 or CM12 and customize the phone the way I want it. Any help would be greatly appreciated as I'm not sure how to prioritize these problems.

The bootloader of the AT&T S4 SGH-I337 is locked. This means you can not install a custom kernel or a custom recovery, and thus you are limited to touchwiz based firmware. You can have custom firmware based on touchwiz, however, you will not be able to have CyanogenMod or any other aosp based firmware.
I would suggest that you repeat the process: flash stock NB1, the rootable kernel, root with towelroot, and install SuperSU as you did before, and then depending on where you want to end up, install safestrap or upgrade to Lollipop with the keeproot method. Look in the general forum for threads by guut13 and muniz_ri.

creepyncrawly said:
The bootloader of the AT&T S4 SGH-I337 is locked. This means you can not install a custom kernel or a custom recovery, and thus you are limited to touchwiz based firmware. You can have custom firmware based on touchwiz, however, you will not be able to have CyanogenMod or any other aosp based firmware.
I would suggest that you repeat the process: flash stock NB1, the rootable kernel, root with towelroot, and install SuperSU as you did before, and then depending on where you want to end up, install safestrap or upgrade to Lollipop with the keeproot method. Look in the general forum for threads by guut13 and muniz_ri.
Click to expand...
Click to collapse
Got it. Thank you very much for responding so quickly! I'm new to this whole thing (the world of installing custom ROM's and the like) and I'm finding that so many details (Root/firmware/baseband/kernel/ROM compatibility) are so much more dependent on carrier and model number than I ever imagined. Thank you for pointing me in the right direction by helping me understand my limitations. Now its time to do a little more research.....

Can't root anymore

Hi All,
I had obtained root via CF-Autoroot and was using it with xposed for the last few weeks without issues. I took the lunge and tried to install phh super su, magisk systemless root. so the nightmare begins for me and i'm hoping it's an easy fix!
My system is still encrypted (I believe because TWRP can't see the system) SD card is fine. I've wiped my device a few times already and am hoping I don't need to wipe it again(prior to this setup).... So currently it's running fine without root access (How I hate android without root!!!)
- I've tried flashing Supersu zip in TWRP and it's failed - I believe it's not supported yet for encrypted devices.
-I've tried using the original CF-Autoroot method I used initially.
Both methods, it boots up straight away (no optimising apps) and after installing supersu app from playstore, it says no binaries found.
What are some ways I can inject root without wiping my device?
Please help me! Thankyou!

Maybe go back to the start and flash original FW through Odin and start from scratch, so you have a fresh phone to work with.

dwarfer66 said:
Maybe go back to the start and flash original FW through Odin and start from scratch, so you have a fresh phone to work with.
Click to expand...
Click to collapse
That's my plan when I get home tonight. I want to flash the original firmware file my phone started with (I'm assuming it won't delete anything?) and then run through the root steps again.. if it doesn't work, I'll wipe my phone and make sure I get rid of encryption this time..

kevinwu128 said:
That's my plan when I get home tonight. I want to flash the original firmware file my phone started with (I'm assuming it won't delete anything?) and then run through the root steps again.. if it doesn't work, I'll wipe my phone and make sure I get rid of encryption this time..
Click to expand...
Click to collapse
I think you will only lose stuff if you do a system reset after installing the original FW.
I only have had to do that on my tab S not my Edge after coming from a custom rom as I got slow down.

Resolved: flashed original rom and obtained root with cf-autoroot.
If someone has detailed instructions for magisk systemless root and xposed, it'd be much appreciated.. i want to have the option to use android pay or play pokemon go if i wanted. Thankyou

Root problem (full root not systemless)

Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish

zishhaider said:
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
Click to expand...
Click to collapse
I don't understand your goal?
Systemless root IS full root. Your terminology is incorrect.
SuperSU doesn't really support system root on Android 7.
I also dont see the point of making SuperSU a system app. Even though its rather pointless if that is all you require for whatever strange reason then you can just move the Supersu app to the system partition.
There is a better way to stay rooted after a hard reset and it's called FRP.

First there is nothing strange in stay rooted after hard reset, trust me. My friend use this mobile. He needs root for lucky patcher. When first he came to me I rooted it via twrp and after couple of days he came back with custom binary block option and plus he doesn't remember newly created gmail id pass. For me it was hell of a job. So i decided to root it permanently. I am not an expert though but my point was to take full root instead of systemless root. Thanks for clearing that 7.0 isn't supported for full system root. I saw here a rom stock dexoded and pre rooted. Is it better option to install it rather than stock rom?

See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root

zishhaider said:
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Click to expand...
Click to collapse
Like I already stated Factory Reset Protection (FRP) is already built in to SuperSU.
Just do the following in a terminal then re-install SuperSU:
echo "FRP=true">>/data/. supersu
.