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
Related
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
Trying to do the 4.3 OTA update. It fails with the message indicating that /system/bin/debuggerd does not have the expected entries.
Looks like Stickmount probably corrupted the file.
Could someone please post an original /system/bin/debuggerd file from Nexus 10 for version 4.2.2 / JDQ39?
It would be greatly appreciated.
Thanks a lot in advance.
I searched all over for this damn file and only ever found one for the N7 which didn't work. Extracted this one from the N10 4.2.2 factory image and successfully updated.
https://mega.co.nz/#!8MkiBAYR!JLj5Wso5EFM6Apn3zspM7hoDtlwl-2_17qW1JDwadn0
Hopefully this link works, otherwise PM me.
Sent from my Nexus 10 using XDA Premium HD app
Thank you so much!!!
It worked perfectly!
I dropped the file in place with Root Explorer in ES File Manager.
Then used TWRP adb sideload to apply the OTA update file.
Then I used Goo Manager to reinstall TWRP recovery.
Then used TWRP adb sideload to apply the SuperSU 1.51 zip file to restore root.
All is good.....Thanks again
djd216 said:
Thank you so much!!!
It worked perfectly!
I dropped the file in place with Root Explorer in ES File Manager.
Then used TWRP adb sideload to apply the OTA update file.
Then I used Goo Manager to reinstall TWRP recovery.
Then used TWRP adb sideload to apply the SuperSU 1.51 zip file to restore root.
All is good.....Thanks again
Click to expand...
Click to collapse
I just ran the normal OTA update, then used CF-Autoroot, which also worked fine for anyone wondering (It has been updated for 1.51).
Greetings Folks!!!
I am on CM12.1 Lollipop 5.1.1 Nightly, and ROOT access was working fine on my phone so far. When I launched Thunderzap today, I noticed that the app was waiting on "Requesting ROOT Privileges" for over 2 mins, and also the SuperSU app was missing from the app drawer. Thunderzap had been recently updated, and I suspect that might have triggered the root access to be requested again, but it wasn't given root access for some reason, and I never got a prompt to grant it root access. However, my other apps like ROOT Explorer, Shell Terminal Emulator etc, which weren't updated off lately, worked fine with root access. Not sure why now, but I thought reinstalling SuperSU-v2.46 might be a good idea at that time, and I flashed that file. And ever since I have completely lost my root access. When I launch the SuperSU app now, i get an error saying:- "There is no SU binary installed, and SuperSU cannot install it"
Some help would be appreciated. Screenshots attached.
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
acemccloud1 said:
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
Click to expand...
Click to collapse
can you please share the method u used to flash back CM?
i am unable to re root
Hello,
After upgrade my nexus 7 from 4.4.4 to 5.1.1 with nexus toolkit all application needs root works perfect, but no root app (e.g. SuperSU or Superuser) appears in menu. I installed SuperSu from TWRP recovery but Application list in SuperSu is empty and all apps needs root works without showing message to allow or deny root access.
How can fix it?
After re-flashing system.img an new installation of SuperSU from TWRP, the problem solved!
Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.
RautMike said:
Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.
Click to expand...
Click to collapse
Flash magisk 13
RautMike said:
Hey I just updated my phone through twrp and I lost root access & custom recovery. Could someone tell me how I can root my phone now again? Info of my phone is below in the pic
P.S: I used KingRoot before and it worked. But not anymore.
Click to expand...
Click to collapse
Of course you lost root and TWRP because a update.zip contains also recovery and other things(vendor, custom, etc.) and by flashing it the stock recovery will overwrite your TWRP and the new system will delete your root access.
And NEVER install KingRoot on this device! It will mess a lot of things(SuperSU and Magisk work)
You will need to flash TWRP again in order to have root because both supersu and magisk need to be flashed through TWRP(because they are .zip files, at least a part of the root, you will need to install the magisk app to have full root)
SuperSU root just needs to be flashed, just magisk needs an app to be installed after .zip flash.
XTutorials said:
Of course you lost root and TWRP because a update.zip contains also recovery and other things(vendor, custom, etc.) and by flashing it the stock recovery will overwrite your TWRP and the new system will delete your root access.
And NEVER install KingRoot on this device! It will mess a lot of things(SuperSU and Magisk work)
You will need to flash TWRP again in order to have root because both supersu and magisk need to be flashed through TWRP(because they are .zip files, at least a part of the root, you will need to install the magisk app to have full root)
SuperSU root just needs to be flashed, just magisk needs an app to be installed after .zip flash.
Click to expand...
Click to collapse
Ok, thank you very much. Ill just wait to come back home from my Vacation and then flash twrp