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

[Q] Root after unroot

Hello
I have a little problem with my note 3
I was rooted it by Kingo and i was using the Xposed
after i was want to update the system and I've make unroot
From the SU and i forgot to delete the Xposed, when I press
the Update i reserve " Your system has been modified "
I've tried to install the Su again bot isn't work
Is there any way to root it again without using computer?

Me no understand

kenny1991 said:
Me no understand
Click to expand...
Click to collapse
My note 3, was rooted, and I've deleted the root, and i forgot to delete the Xposed app who make changes in the system, now after the deleted i want to update the system to lollipop bot i can't update it because when i press the Update button it says " your device has been modified software update not available".
So is there anyway to root it again without pc, just to delete the Xposed app and update it
I hope you understand me, and am sorry my English not very well

Did you uninstall xposed properly?
It would of edited files before....now that you are not rooted the files are modified and you cant fix unless you re-root , uninstall xposed then unroot again.
Also did you delete any system apps that came with the phone?
You may need a computer to do this, i dont think you can properly uninstall xposed without root.

plazaman91 said:
Did you uninstall xposed properly?
It would of edited files before....now that you are not rooted the files are modified and you cant fix unless you re-root , uninstall xposed then unroot again.
Also did you delete any system apps that came with the phone?
You may need a computer to do this, i dont think you can properly uninstall xposed without root.
Click to expand...
Click to collapse
No I've make mistake i didn't uninstall it properly this is the problem, i forgot to delete the add block inside the Xposed,
The second question, no i didn't delete any of the system app

Just flash your rom with odin

Danny Syr said:
No I've make mistake i didn't uninstall it properly this is the problem, i forgot to delete the add block inside the Xposed,
The second question, no i didn't delete any of the system app
Click to expand...
Click to collapse
Well you can try what @kenny1991 said and flash through odin.
Factory reset may fix your problem as well.

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

Can't Unroot S4?

So, i tried to Root my GF's I9506 with CF-Autoroot.
Safteynet fails and PokemonGo doesn't work, login problems.
I Unrooted trough SuperSU, restarted the phone a couple of times but PoGo still wont login.
She's on Stock Samsung Rom with Stock Recovery.
What can i do?
I was able to Re-Root with SuperSU for some reason. Had to update the binary tho. That's strange...
Shouldnt work if SuperSU unrooted in the first place?

Maybe it leaves files behind. If you're interested, there are ways to hide root from the game.
Anyway, the only sure way to remove root would probably be the flashing of a stock ROM.

Pwnycorn said:
Maybe it leaves files behind. If you're interested, there are ways to hide root from the game.
Anyway, the only sure way to remove root would probably be the flashing of a stock ROM.
Click to expand...
Click to collapse
Hmm. She really dosen't want to do a factory reset. so i guess i have to hide it then..
I think there are a few options i think all of them needs another recovery though:
Magisk + Magiskhide + phh
SuperSu, Suhide
Something called iSu.
Might it help to root again, remove anu "Su" files and folders trough ES Filexplorer? Then unroot from SuperSu?

If the phone is running a stock ROM, flashing a stock ROM usually leaves all of the data intact.

Dallebull85 said:
Hmm. She really dosen't want to do a factory reset. so i guess i have to hide it then..
I think there are a few options i think all of them needs another recovery though:
Magisk + Magiskhide + phh
SuperSu, Suhide
Something called iSu.
Might it help to root again, remove anu "Su" files and folders trough ES Filexplorer? Then unroot from SuperSu?
Click to expand...
Click to collapse
Removing any root file live might break root, which in turn won't let you remove any of the other files left.
Besides, you don't even know what files to look for.
Having a custom recovery won't affect her usage of the phone, nor the game. Besides, it gives you the benefit of making a Nandroid backup.

Ty for all the answers. So a custom Recovery doesn't trigger Saftynet?
Might as well install TWRP, backup and try to reflash stock rom from there.
Samsung Galaxy S4 International Qualcomm (jfltexx)
Samsung Galaxy S4 LTE Advanced i9506 (ks01lte)
Which one? i suppose its the 9506, flashhing my old CF-autoroot for my 9505(jfltexx) didn't work.

To flash a stock ROM, you need Odin, Samsung phone drivers, and the stock ROM from sammobile.com.

OK. But i'll do a backup on twrp first. Ty ty
Fixed it! Reflashed stock Rom with Odin and now Pogo works again!
Ty a lot for all the help. you guys are the best!

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
.