Retaining Root on 4.4 - Nexus 7 Q&A, Help & Troubleshooting

Well I flashed 4.4 successfully using TWRP. But some how or another I've unrooted myself. I've tried everything that I can (aside from messing with ADB and the SDK directly) and I can't figure out how to re-root the device.
Help!

Install TWRP again if it's gone and then flash SuperSU

tom1807 said:
Install TWRP again if it's gone and then flash SuperSU
Click to expand...
Click to collapse
No dice. Says I'm unrooted.
Managed to get it working. Koush's Superuser app doesn't work for some reason. SuperSU does. I just hope they fixed the glitches with it causing unnecessary battery drain.

What were your steps?
You can obtain the last flashable zip file from here
Ok, you edited your post, so my one is obsolete

Related

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

Keep Root or Re-Root 4.3 - SOLVED

UPDATE - I discovered a Nexus 4 thread, followed the direction (changing as needed for the N7) and voila it worked
I created a step-by-step tutorial to keep ALL data going from 4.2.2 root > 4.3 root
http://forum.xda-developers.com/showthread.php?t=2390286
Unlocked Bootloader and Rooted. From what I've read I can't keep root (as of now). So what is the easiest way to keep all my data and move over to Rooted 4.3? Step-by-step would be helpful....
Thanks.
The easiest way if you have stock recovery is to revert any system changes you've made (in my case remove the AOSP browser from system apps), accept the OTA update, and once it's up and running, boot into twrp without permanently flashing (which you can do with mskips toolkit) and flash the updated 1.51 supersu zip. Then go to the play store and activate the supersu app.
Sent from my Galaxy Nexus using xda premium
Worked like a charm!! Thank you very much!! Super quick/easy! Already did the OTA update and thought it would be a pain in the ass to fix, but no problem.
Mskip's toolkit: http://goo.im/devs/mskip/toolkit/google_nexus7/Google_Nexus_7_ToolKit_v5.0.0.exe
SuperSU:
http://download.chainfire.eu/343/SuperSU/UPDATE-SuperSU-v1.45.zip
95Z28 said:
The easiest way if you have stock recovery is to revert any system changes you've made (in my case remove the AOSP browser from system apps), accept the OTA update, and once it's up and running, boot into twrp without permanently flashing (which you can do with mskips toolkit) and flash the updated 1.51 supersu zip. Then go to the play store and activate the supersu app.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have the same situation here, but I'm not familiar with the procedure.
"boot into twrp without permanently flashing (which you can do with mskips toolkit) and flash the updated 1.51 supersu zip."
could you explain that step by step please?
I install the toolkit - which point to I have to use? and wat is twrp?
What do I have to do, to flash the 1.51 supesu.zip?
Big thanks in advance
Harry
Dirty-Harry said:
I have the same situation here, but I'm not familiar with the procedure.
"boot into twrp without permanently flashing (which you can do with mskips toolkit) and flash the updated 1.51 supersu zip."
could you explain that step by step please?
I install the toolkit - which point to I have to use? and wat is twrp?
What do I have to do, to flash the 1.51 supesu.zip?
Big thanks in advance
Harry
Click to expand...
Click to collapse
Is it not easier to simply use Chainfires CF Auto-Root? A couple of clicks in windows and it's done.
Does Chainfires CF Auto-Root only root not make any changes? I don't want to have to reset the rom back to factory or reinstall all of the apps. If Chainfires CF Auto-Root does just root, cool.
With Mskip's toolkit how do you root? There is no choice for 4.3, just 4.2.2.
Unless I've missed something when installing the OTA using clockwork recovery it asked if I wanted to stop a stock recovery from being reinstalled and if I wanted to keep root. This just seemed to work and gave me 4.3 with custom recovery and root - nothing else needed.
Dirty-Harry said:
I have the same situation here, but I'm not familiar with the procedure.
"boot into twrp without permanently flashing (which you can do with mskips toolkit) and flash the updated 1.51 supersu zip."
could you explain that step by step please?
I install the toolkit - which point to I have to use? and wat is twrp?
What do I have to do, to flash the 1.51 supesu.zip?
Big thanks in advance
Harry
Click to expand...
Click to collapse
I'd like my hand held too, please. Or at least link to instructions. Thanks.
If anyone wants to actually make a 1,2,3,etc direction list, many people would be grateful.
95Z28 said:
The easiest way if you have stock recovery is to revert any system changes you've made (in my case remove the AOSP browser from system apps), accept the OTA update, and once it's up and running, boot into twrp without permanently flashing (which you can do with mskips toolkit) and flash the updated 1.51 supersu zip. Then go to the play store and activate the supersu app.
Click to expand...
Click to collapse
1. I'm not sure if I have any system changes? Is there an easy way to tell?
2. Running OTA update will only remove Root, not unlocked Bootloader or Custom Recovery (CWM/TWRP)?
Am I following this right? Supposing I have removed any system changes i do the following:
1. Accept OTA
2. After update boot into recovery (Vol Down + Power) --- CWM in my case
3. Flash the 1.51 SuperSU Zip
4. DONE? I'm rooted?

PHH's Root Disappeared

Hi Guys.
As the title suggests root access suddenly disappeared from my nexus 6p yesterday.
DigitalHigh rom 7.0 was flashed through the latest twrp (3.0.2-2) and everything was running fine. I got the notification that the SU binary is out of date from PHH's SuperUser. Opened it but nothing really happened. So I downloaded superSU and suddenly it prompted me that the device isn't rooted. Being unfamiliar with PHH's SU I decided to flash the latest SuperSu through TWRP but the phone wouldn't boot.
Right now it has been restored to a backup taken just before flashing SuperSU which means everything is running fine and even android pay works however there's no root access. Is there something specific that might have caused this?
Are there any ways to re-gain root?
Haven't gone through the process of a clean flash yet as the phone is needed for work however even if all of that is done the SU binary will still need to be updated. Is there a different method for updating PHH's root?
So far I have tried clearing cache etc. but noting worked.
apostol96t said:
Are there any ways to re-gain root?
Click to expand...
Click to collapse
Phhusson's superuser and SuperSU don't mix. If you're back to booted, but not rooted with Phh, you'll need to either flash one of the Nougat boot images from the nexus/angler folder or the latest superuser.zip (I think the latest is r229) from http://superuser.phh.me

Lost root after flashing 4.1.6, Please help.

Hi, Can someone please help, I must have done something wrong. Flashed official 4.1.6 update through twrp successfully, but lost root, tried to flash super su again (ver 2.86), but got stuck in boot, logo froze.
Flashed 4.1.6 again, phone works but no root still.
Is that a wrong super su version or did I do something else wrong?
Help will be really appreciated.
Regards
After flashing a full update you'll always have to reflash your root solution. I guess you mean SuperSU v2.82...
Use the official 2.82, found here (there's a link to the flashable zip). There's also a link to a version to try if you're experiencing bootloops.
You could also try the release candidate, found here.
Magisk all the way
1. Wipe data
2. Flash ROM
3. Flash root package, either SuperSU or Magisk
4. Reboot
I see no reason why wouldn't this work for you
Didgeridoohan said:
After flashing a full update you'll always have to reflash your root solution. I guess you mean SuperSU v2.82...
Use the official 2.82, found here (there's a link to the flashable zip). There's also a link to a version to try if you're experiencing bootloops.
You could also try the release candidate, found here.
Click to expand...
Click to collapse
Hi,
Many thanks.
Before proceeding, should the super su app also be removed from phone?
Regards
dua999 said:
Hi,
Many thanks.
Before proceeding, should the super su app also be removed from phone?
Regards
Click to expand...
Click to collapse
When you flash the rom it will already be uninstalled
sakumaxp said:
When you flash the rom it will already be uninstalled
Click to expand...
Click to collapse
I think, I was not able to explain, Rom is already there, but I just flashed 4.1.6 update, and root was gone.
Just wanna avoid all those data backup, restore, register all new banking apps etc, it time consuming and painful.
I am pretty sure, root can be restored, when I have an unlocked bootloader, twrp recovery working properly.
SuperSU is still there in apps but can't open as says, root not available. However, can uninstall this if that is required.
Cheers
dua999 said:
I think, I was not able to explain, Rom is already there, but I just flashed 4.1.6 update, and root was gone.
Just wanna avoid all those data backup, restore, register all new banking apps etc, it time consuming and painful.
I am pretty sure, root can be restored, when I have an unlocked bootloader, twrp recovery working properly.
SuperSU is still there in apps but can't open as says, root not available. However, can uninstall this if that is required.
Cheers
Click to expand...
Click to collapse
You can try to uninstall it through supersu app but make sure to keep you boot img. Then your phone will be fully unrooted, go into twrp and reflash supersu/magisk
sakumaxp said:
You can try to uninstall it through supersu app but make sure to keep you boot img. Then your phone will be fully unrooted, go into twrp and reflash supersu/magisk
Click to expand...
Click to collapse
Thanks all for help, all sorted

[Q] Successful rooted, but /system is read only?

Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2

Categories

Resources