I got Wubs toolkit, would that help with reinstallation of SuperSU? or better not risk it? lol. Sorry for all the questions. :/

Originally Posted by jesus359

I got Wubs toolkit, would that help with reinstallation of SuperSU? or better not risk it? lol. Sorry for all the questions. :/

Just reinstall from the Play Store?

I tried that, but part is on the /system folder and I dont have access to it without root. :/ Should I try Full Unroot the try installing it again?

If you have a custom recovery (CWM or TWRP) installed...

...flash Chainfires SU .zip package available here...

http://download.chainfire.eu/310/Sup...erSU-v1.04.zip

Reboot... and you're Rooted.

Rgrds,
Ged.

Yeah, if you can't install, just reflash from recovery.

Re: 4.2.2 update

---

Originally Posted by uberNoobZA

I was on JOP40D (4.2.1) Stock, rooted, with CWM 6.0.2.3. I downloaded this OTA file http://android.clients.google.com/pa...D.6ece895e.zip from the link in the other 4.2.2 thread (http://forum.xda-developers.com/show....php?t=2144330)

I booted into CWM, and flashed the downloaded ZIP file as normal
When I told CWM to reboot, CWM warned me the update would flash stock Recovery and do I want to STOP this from happening and I said YES.
It then said I had lost root, and do I want to restore root, and I said YES.
It then booted into Android and continued with the upgrade.

I now have 4.2.2 stock installed (JDQ39), and still have root and custom recovery, and an unlocked bootloader.

From what I have read, if you 'sideload' the update using ADB, or do a normal OTA update, you will lose root and custom recovery. However, using the steps above will keep root and recovery for you

Exactly what I did and is working perfect. Can't be easier than that.

Sent from my Nexus 7 using xda app-developers app

Originally Posted by iElvis

Yeah, if you can't install, just reflash from recovery.

I dont have recovery. I lost everything. :/

Re: 4.2.2 update

---

Originally Posted by jesus359

I dont have recovery. I lost everything. :/

Question 1: did you make a backup?

Question 2: if you didn't, why not?

Sent from my Nexus 7/Nexus 4

Re: 4.2.2 update

---

Originally Posted by Slender Troll

Question 1: did you make a backup?

Question 2: if you didn't, why not?

Sent from my Nexus 7/Nexus 4

Yes, I made a back up. I got several backup with different Roms and one back up with everything stock (rooted of course). When I went to flash I didn't erase anything. I just selected install and it flashed, before I did that I downloaded the voodoo ota root keeper, and made a backup of that as well. Flashe, booted, and now the voodoo app freezes and force closes, and when I went to put the recovery menu only the android with a red triangle on top appears, no letters or anything. I'm gonna try to do factory reset. Adb as of right now, I'm searching for the drivers. I got the SDK downloaded. Any other recommendations and/or tips would be great. I'm running out of options.

Sent from my Nexus 7 using Tapatalk HD

---------- Post added at 02:20 AM ---------- Previous post was at 02:16 AM ----------

Update: in wubs root tool kit. I tried to install the drivers, when I did a drivers test, it was that adb was listed as offline, and I'm guessing its because I have not yet put it in the whitelist, (one of the things in the 4.2.2 updates, from what I have read) anybody know how to put it in the white list?

Sent from my Nexus 7 using Tapatalk HD

---------- Post added at 03:07 AM ---------- Previous post was at 02:20 AM ----------

edit: Whoo! I figured it out, I went into fastboot mode and flashed TWRP. For those who encounter this issue: Make sure yu can use adb (even if it says that device is offline), Power down, press vol down and power, open command promot(on windows), choose a recovery and put it in the platform-tools folder in the sdk folder, in command prompt go to where the recovery is at and type fastboot flash recover "name of recovery".img. Yu should be set!

Originally Posted by dalanik

getting assert failed on /system/app/CalendarGoogle.apk.

Do you have your CalenderGoogle.apk system app installed?

I'm getting the same error "assert failed ......./system/app/Books.apk" .... After root I uninstalled Books.apk and a couple other GApps using TitaniumBackup. I have a backup of the apks & data.

I re-installed Books from TiBkp and I get the same error for Currents.apk (also uninstalled).....SO if you've uninstalled your SYSTEM GApps, try adding them ALL back (hopefully you have a backup) then proceed.

UPDATE -- I have restored all but Google Play Magazines....Having a TiBkp restore issue...