Help for updating - Nexus 7 Q&A, Help & Troubleshooting

Hi i have a n7 3g on 4.2.1 rooted..i installed also ota rootkeeper
Now i nave the 422 update downloaded but i ve read the rootkeeper is not functioning on 422 so now if i install the update will my root be safe opening rootkeeper band rerooting with it?
I ve a stock ROM and kernel..just unlock bootloader and root..
sent from rootilapia

I'm also stock rom/kernel, rooted and have cwm recovery, supersu, and voodoo ota rootkeeper. I told ota rootkeeper to backup root. I copied the update file to the N7 and ran the update through cwm recovery. After the update I kept root and kept cwm recovery by answering Yes to a prompt about disabling flashing stock recovery (thus keeping cwm recovery) and Yes to a prompt about recovering root. Very easy overall.

R: Help for updating
Hi to copy the update.zip you used adb or just wired to PC and copied it in the -root of sd?
If i install the update downloaded by the nexus and then run rootkeeper would be good or better install it through recovery?
Really thanks
sent from rootilapia

I downloaded the update (6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip) to my computer and from there to the N7 via usb cable. That way I could easily check the md5 checksum and I don't always trust d/l straight to the N7 although it should work fine. You can even install the zip from the download folder.
Do you have root via Superuser or Supersu? With Supersu and ota rootkeeper (told it to backup root) I kept both root and my cwm recovery. Without them, the update will flash the stock recovery overwriting a custom recovery like cwm or twrp and you will loose root. Even so, you can re-root after getting 4.2.2 and you can install a custom recovery.
I'm not sure if Superuser or twrp recovery gives the same results as I had, but the setup I posted above works beautifully. You do need to backup root with rootkeeper before flashing the update.

i lost root after updating even with rootkeeper. i simply flashed the supersu file i already had on my sd and all is fine

R: Help for updating
I have supersu and i ve configured rootkeeper when just installed means i checked everything
So now if i download the update for nakasig and install it through cwm and then put super su.apk in root of SD and then open rootkeeper and restore root will work?
sent from rootilapia

Related

rooted System image from ota 621

For anyone interested I have made a system image of my rooted droid x after updating over the air to 621. It is clockwork recovery image zipped up. I know that you need root in order to install recovery but I see some have managed to overcome the limitation of returning to the 605 update so this may be of use to them.
For those interested I managed to get root by rooting a fresh install and running everything which required root access then running root keeper. After the ota update I ran the rootkeeper again regained root and rebooted.
I have removed a few pieces of bloat ware and installed a few other apps to the system.
This is the dropbox link 158meg
http://db.tt/qR61pYCr
md5 11d7ac8b21639b178ffed7e90f949af6 system.img
I hope this is of use to someone.

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] Lil help please, Root issues after update

I updated to 4.2.1 with the OTA zip file using TWRP and voodoo root keeper installed. It flashed just fine. Rebooted with update. My root access is funky though. SuperSU is still there and I can access root file threw root explorer but I can't mount it as writable and when I install a new app that needs root access it never asks for it. Does superSU need to be updated? There is no update available??? Thanks
just flash the supersu zip again in TWRP
http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip

[Q] Ziddys OTG Kernel - Lost Root

I have just installed Ziddys OTG kernel R184 on a Stock rooted JWR66Y. However after rebooting I have lost root with superuser complaining that th SU binaries are out of date. I have tried installing the superuser.zip again from recovery but still get the same error and no root. I am using clockworkmod superuser and all was working ok till I flashed the new kernel. At a loss on what to try next to regain my root.
Andy.
g1dtf said:
I have just installed Ziddys OTG kernel R184 on a Stock rooted JWR66Y. However after rebooting I have lost root with superuser complaining that th SU binaries are out of date. I have tried installing the superuser.zip again from recovery but still get the same error and no root. I am using clockworkmod superuser and all was working ok till I flashed the new kernel. At a loss on what to try next to regain my root.
Andy.
Click to expand...
Click to collapse
I have now installed the latest supersu via CWM and all is working ok and I have root back.

Rerooted, but....

So I updated my tab because there was an incremental update. I lost root and twrp after that, so I used wugs toolkit flash twrp and root my device. My question is, the process installed busybox and whenever I install it (coz wug said so during the process) the binaries do not seem to be found as it continuously nags me to update when I already did so. Also, it doesn't seem to be installed on system/xbin. Need help

Categories

Resources