Maybe it is interesting also for others, how to get back ROOT access after flashing JB OTA. I did it with YAKJU.
The steps:
1.) adb reboot bootloader
2.) download recovery-clockwork-5.5.0.2-maguro.img
2.) fastboot boot recovery-clockwork-5.5.0.2-maguro.img
3.) adb kill-server
4.) adb start-server
5.) adb devices
6.) mount the system in CWM
7.) adb shell ls -al /system/bin/su
8.) adb shell chmod 4755 /system/bin/su
9.) adb shell ls -al /system/bin/su
10.) reboot
Dont forget to use fastboot with su or sudo -i in Linux.
Steps 3, 4 and 5 are only to ensure that your ADB works correctly with your device.
Steps 7 and 9 is also only for paranoid users like me
That's it.
Voodoo OTA Rootkeeper?
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!
gibosi said:
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!
Click to expand...
Click to collapse
I was able to make it work...I hit restore su... then it took like a minute little pop up saying su restore successful ..opened superuser app...went back to ota root keeper...hit restore su again...that's when superuser prompted me to allow superuser access.
Sent from my Galaxy Nexus using xda premium
Based on your experience, I flashed Jellybean this afternoon and Voodoo OTA Rootkeeper restored root. Thanks!
i think i've become lazy these days, i just selected - "root phone" in the nexus tool kit 7.4 after flashing the update to get root back.
i dont even bother typing the fastboot commands to boot CWM recovery in CMD anymore, i just select the option in the toolkit.
gibosi said:
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!
Click to expand...
Click to collapse
Placing this here in case it can help anyone else:
I downloaded the Jelly Bean .zip file, placed it in /cache, and used the stock recovery to update. After installation, I had lost root. su was gone from /system/xbin and OTA Rootkeeper was unable to restore root. Neither CWM Touch 5.8.0.2 nor CWM 5.5.0.2 were able to mount /sdcard in order to apply su.zip. However, /system/usr/we-need-root/su-backup was still there with the proper permissions so I was able to restore root manually by using it.
the OP's instructions worked for me. I flashed the OTA with CWM by the way (the stock failed on the package checking because I was rooted) ?
Anyway, I ran Titanium Backup to check the root worked per OP's instructions and it did but it complained that permissions weren't optimal so I let it change them to 6755 instead (which gives super to both the owner and the group).
Works like a charm now so far.... only 5 minutes with it though
I forgot to run root keeper before the 4.1.2 OTA. I presume this is still valid?
Can someone confirm that this wont wipe the device?
Ta
aidanbree said:
I forgot to run root keeper before the 4.1.2 OTA. I presume this is still valid?
Can someone confirm that this wont wipe the device?
Ta
Click to expand...
Click to collapse
Let me make this a little easier, do the first couple of steps then once you are in recovery flash this: http://androidsu.com/superuser/
You are rooted.
Why are you trying to make this so hard?
Boot in to CWM Recovery and flash the zip. Takes about 5 seconds.
Couldn't we just adb push a su apk to system/app and maybe a adb install su?
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
Couldn't we just adb push a su apk to system/app and maybe a adb install su?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You could but I still think my way would be easier, just my opinion though.
Sent from my Galaxy Nexus using Tapatalk 2
miketoasty said:
You could but I still think my way would be easier, just my opinion though.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I see but if you took the 4.1.2ota you were on stock recovery and someone wanting to get ota'the same way would have to revert back to stock recovery once this was done.
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
I see but if you took the 4.1.2ota you were on stock recovery and someone wanting to get ota'the same way would have to revert back to stock recovery once this was done.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Good point, I don't regularly use the stock recovery so I wasn't thinking about it.
Sent from my Galaxy Nexus using Tapatalk 2
miketoasty said:
Good point, I don't regularly use the stock recovery so I wasn't thinking about it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am going to do this today, my girlfriend needs roots for silly things like changing the on screen button. I'll document it and leave it in here.
This way she can have her root and I dont have to be like "I needs to update your phone/tablet" when google pushes something new, and maybe other people might find it useful
Related
Has anyone successfully installed clockwork recovery on the continuum? I was tempted to try the fascinate instructions
Sent from my SCH-I400 using XDA App
I have used Titanium Back up with success
Okay, I can officially say that the Fascinate Clockwork Recovery does not work... Fails on "updating from Verizon" or something similar.... Then reboots... Is that Clockwork or the standard recovery?
Okay, I did not backup my stock recovery (stupid stupid stupid stupid), so can anyone get me that file and tell me which directory I need to shove it in?
Sent from my SCH-I400 using XDA App
I cannot remember the process to backup the recovery. What do you need me to do?
ThePravus said:
I cannot remember the process to backup the recovery. What do you need me to do?
Click to expand...
Click to collapse
Use root explorer or something similar, find the recovery file and copy it... Attach it here and let me injure what directory it was in... Please... I appreciate any help...
Sent from my SCH-I400 using XDA App
Or let me know... Somehow Swype changed that to injure...
Sent from my SCH-I400 using XDA App
I believe its more than just a file, you have to flash it.
Weudel said:
Use root explorer or something similar, find the recovery file and copy it... Attach it here and let me injure what directory it was in... Please... I appreciate any help...
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
If you know why the directory is I can post the files. Man, we really need some devs...
Also, you can might not need to flash it, but you would probably need to use ABD then.
Sent from my SCH-I400 using XDA App
Was informed that we could use dump_image to pull it and then flash_image to reflash. Trying to get ADB working at the moment. Typing on the phone is terrible.
ThePravus said:
Was informed that we could use dump_image to pull it and then flash_image to reflash. Trying to get ADB working at the moment. Typing on the phone is terrible.
Click to expand...
Click to collapse
The typing isn't that bad if you use swype or SwiftKey. Is there anything I can do to help?
Sent from my space time Continuum using the XDA App.
OK this is the best I can do I think.
I dumped the recovery block with the awesome help from Da_G]NARF[ on the XDA IRC chan.
AFAIK this should fix it.
Extract boot.rar
Copy boot.bin to your sdcard
Unmount the SDcard if you copied from your computer.
Open a terminal either with ADB shell or im assuming a term emulator would work.
SU for root privs. then use this command:
Code:
dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096
This will backup your current one.
Code:
dd if=/sdcard/boot.bin of=/dev/block/bml1 bs=4096
This will rewrite with the new one.
Reboot.
dfgged said:
The typing isn't that bad if you use swype or SwiftKey. Is there anything I can do to help?
Sent from my space time Continuum using the XDA App.
Click to expand...
Click to collapse
If you can pull the stock recovery and post it, that would be great...
Otherwise, could one of you try booting into the stock recovery and see what it does... I tried to load the Fascinate Clockwork using ROM Manager and I'm not sure if it actually did anything or not... I don't think Clockwork would check with Verizon for updates.... All I have experience with is Amon Ra on my Eris..... Would be great if it just failed to change it.....
ThePravus said:
OK this is the best I can do I think.
I dumped the recovery block with the awesome help from Da_G]NARF[ on the XDA IRC chan.
AFAIK this should fix it.
Extract boot.rar
Copy boot.bin to your sdcard
Unmount the SDcard if you copied from your computer.
Open a terminal either with ADB shell or im assuming a term emulator would work.
SU for root privs. then use this command:
Code:
dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096
This will backup your current one.
Code:
dd if=/sdcard/boot.bin of=/dev/block/bml1 bs=4096
This will rewrite with the new one.
Reboot.
Click to expand...
Click to collapse
Awesome, thanks...
Looks like it worked... I guess I might not know for sure until the 2.2 OTA comes out.... Fingers crossed...
I've been working on porting clockwork. After running
Code:
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
with the path substitution, I get
Code:
unpackbootimg not found. Is your android build environment set up and have the host tools been built?
Does anyone have any suggestions?
I am new to these forums Well, i have been looking around here for a while for my Continuum phone, i just haven't said anything
I may be completely wrong... But do these steps (The ones in the beginning) install Clockwork? Or is that for something completely different?
and this is probably the wrong place to ask... But in order to install the Voodoo lagfix, you need Clockwork, right?
Thank you for your help everyone
trailblazer101 said:
I am new to these forums Well, i have been looking around here for a while for my Continuum phone, i just haven't said anything
I may be completely wrong... But do these steps (The ones in the beginning) install Clockwork? Or is that for something completely different?
and this is probably the wrong place to ask... But in order to install the Voodoo lagfix, you need Clockwork, right?
Thank you for your help everyone
Click to expand...
Click to collapse
Well this the right place to ask, and the steps you see are steps to flash the stock recovery back. Also, yes, we do need clockwork for voodoo.
Sent from my space time Continuum using the XDA App.
dfgged said:
Well this the right place to ask, and the steps you see are steps to flash the stock recovery back. Also, yes, we do need clockwork for voodoo.
Sent from my space time Continuum using the XDA App.
Click to expand...
Click to collapse
There currently is not a Clockwork Recovery for the Continuum, but it is in the works...
Has anyone other than Weudel tried using this supposed stock recovery?
Sent from my SCH-I400 using XDA App
I'm using a Terminal Emulator on my phone trying to run the command to backup my current boot image. I'm typing "su" first for root privileges then typing "dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096" but I'm getting an error saying uknown operand if. Help?
Nevermind, I've discovered the problem. The code to backup your current boot image is "dd if=/dev/block/bml1 of=/sdcard/boot.bak bs=4096". There was an equal sign missing in the post above.
So I've completed the steps listed above and was under the impression this would restore my phone to stock. However, I still don't have the Verizon bloatware I deleted. Did I not understand what this process was meant to accomplish?
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
wang1404 said:
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
Click to expand...
Click to collapse
I am not %100 if this is your problem but i think you need ENGINEERING HBOOT
to run adb commands ,you can do it by reading the wiki http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
But if you want to do it be very very carefull becasue if you do it wrong you will brick your phone and there is no way back
S-OFF is different from having your phone rooted, so it sounds like your rooting hasn't worked. If you have S-OFF and the eng hboot, you could use fastboot to flash Clockwork recovery and then install a custom pre-rooted ROM.
Or you will need to go through the rooting procedure again to see what has gone wrong.
Sent from my HTC Desire Z
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
steviewevie said:
Or you will need to go through the rooting procedure again to see what has gone wrong.
Click to expand...
Click to collapse
I did notice that while I was rooting. A command said no such file or directory. So I wonder if that was it? I thought it was supposed yo happen tho lol
Sent from my Nexus One using XDA App
wang1404 said:
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
joemm said:
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
Click to expand...
Click to collapse
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
wang1404 said:
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
joemm said:
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
The ADB remount command requires the ro.secure property to be set to 0 (even if you are rooted). If you want to remain on the stock ROM, flashing the linked ROM will do it for you (and is way easier than doing it yourself manually). Most (if not all) of the custom ROMs will set this property for you if you wanted to try others as well.
Thank you guys very much. I never faced this problem before since my n1 was rooted and flashed rom using the phone not adb our anything related to computer.so thanks guys. Case closed. Happy me lol
Sent from my Nexus One using XDA App
Is there a method of flashing CWM3 via update.zip in samsung recovery? I don't have a functional USB cable to use with the One Click method :/. Sorry if this has already been answered, I couldn't find an answer through searching. Thanks in advance!
No, but luckily USB cables are dirt cheap these days, I'm sure you can find one for < $5, or if worst comes to worst go to Sprint and beg a rep to replace your cable.
Lost the one that came with the phone, only have one which I stole from another charger and the device isn't recognized at all (tried it on multiple pcs). I really don't want to buy one as I never use it except for the CWM flash. I have a SD card reader to eliminate the need for cables.
Well, you need one if you're going to flash CWM, if anything just think of it as making your life easier in the long run, no more taking the SD card out just to put files on it.
Frankly I wouldn't mind if there were a way to do it manually in terminal.
*bump* Anyone have any ideas for a method of using terminal to do this?
it can be done in terminal, just open the batch file and read what it does via adb and do that in terminal
I started to do that but cant get past the exploit (rageagainstthecage). I get permission errors and can't even copy the file to /data/local/tmp. Any ideas?
EDIT: It's because the data partition cannot be modified without root access. Somehow adb bypasses this.
Adb runs with root access i suppose... let me look at something..
I basically need a method of obtaining temporary root on the device without using a computer. If i can do that, I can flash cwm using redbend_ua and then flash a rom/kernel for perm root. If it helps, i'm on OTA EC05
EDIT: Does redbend_ua require root access?
EDIT2: Nevermind. I tried running redbend_ua to flash the recovery image and got an error about /data/local/fota missing.
does z4root work on froyo?
http://forum.xda-developers.com/showthread.php?t=833953
if it does.. then
Code:
su
cp /sdcard/redbend_ua /data/local
chmod 755 /data/local/redbend_ua
cp /sdcard/zImage /data/local/tmp/zImage
/data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
chris41g said:
does z4root work on froyo?
http://forum.xda-developers.com/showthread.php?t=833953
if it does.. then
Code:
su
cp /sdcard/redbend_ua /data/local
chmod 755 /data/local/redbend_ua
cp /sdcard/zImage /data/local/tmp/zImage
/data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
Click to expand...
Click to collapse
I thought of z4root, and no it doesnt work on froyo, not since eb13 it appears :/. I then thought "if ONLY i hadn't updated to ec05 (my phone came with di18)". Is there a way to get back to di18 without odin or custom recovery? Thanks for all your efforts thus far by the way.
trobertson said:
Is there a way to get back to di18 without odin or custom recovery?
Click to expand...
Click to collapse
No. invisible text
063_XOBX said:
No. invisible text
Click to expand...
Click to collapse
Is there another method of rooting I can do manually? That's the real problem here. I need root to run redbend_ua and from there i can do everything using clockwork. OR some other way to flash clockwork that doesnt require root but it seems that doesn't exist.
Well previously koush had an update.zip that would run in stock recovry and install cwm.. but it stopped working as of froyo, I'm assuming the recovery signature changed. Maybe contact him via twitter or something and see if he ever made a new one..
Sent from my SPH-D700 using XDA App
chris41g said:
Well previously koush had an update.zip that would run in stock recovry and install cwm.. but it stopped working as of froyo, I'm assuming the recovery signature changed. Maybe contact him via twitter or something and see if he ever made a new one..
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks for the heads up, I PM'd koush. Crossing my fingers on this one >.<!
trobertson said:
Thanks for the heads up, I PM'd koush. Crossing my fingers on this one >.<!
Click to expand...
Click to collapse
Doesn't look like he's going to answer me. I tried getting him on IRC as well and was simply ignored :/.
I don't think he checks these forums often
Sent from my SPH-D700 using XDA App
What do i do? Fastboot no dice. Want my root back
Spawn The Dark Ages
What do you do? Follow XDA rules and use search before posting.
i did search and got nothing. found out problem myselfhttp://forum.xda-developers.com/showthread.php?t=1856164
but thanks so much for the constructive response
dont use rootkits, everything would have been easier without. you have a nexus.. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or su binaries, and reboot. that is all. anyways, install supersu, open it, update your su binaries. there is a flashable version on xda, or the free supersu app in the play market.
@ JediNinjafication yes, why are you using a tool kit? You are way above that!!
Sent from my Galaxy Nexus using Xparent Red Tapatalk 2
JediNinjafication said:
What do i do? Fastboot no dice. Want my root back
Spawn The Dark Ages
Click to expand...
Click to collapse
flashable in your custom recovery http://download.chainfire.eu/212/SuperSU/CWM-SuperSU-v0.96.zip
the point is that you dont need fastboot or a root toolkit to get your su back. flash it, open the app after you boot. if it says that you need to update it, do it. if not, then you are good.
had no recovery at the time. when restored it took that too.
and i do not use kits. ever.
Hi,
I just joined the forums this evening. This is my first post.
Basically I want to figure out how to re-root my (2013) Nexus 7 which I just updated to 4.4.2.
I installed 4.4 and had to re-root, of course losing all my settings and apps, having to reinstall and reset everything to my liking.
I have never made a backup.
I just now upgraded to 4.4.2 update, and all my settings and apps are in tact, however, I lost root.
I do not want to re-root and reinstall everything again, so I need help on recovery and steps involved.
I am still unlocked, and I have the TWRP installed as well as SuperSU and RecoveryTools.
Please advise how to make a backup and re-root in the least painful way.
(PS I did use the Wug'sFresh kit to do my rooting the first time around, and am not very comfortable using the SDK etc)
Thanks!
-Mike
Same issue. Rooted it a few days ago, reinstalled many things and now it told me to root again... omg...
Sent from Nexus 7 v2013 using Tapatalk HD
jonidontcry said:
Same issue. Rooted it a few days ago, reinstalled many things and now it told me to root again... omg...
Sent from Nexus 7 v2013 using Tapatalk HD
Click to expand...
Click to collapse
Hi,
It is very frustrating I want to be able to keep all my apps/settings and configurations after root, but I don't know how.
I think there is an app that allows you to keep your root after upgrades, but I haven't really figured out which way to do things.
Any pros out there who can help?
Everything is fine on my tablet right now, just the way I like it BESIDES being unrooted.
skeletal77 said:
Hi,
I just joined the forums this evening. This is my first post.
Basically I want to figure out how to re-root my (2013) Nexus 7 which I just updated to 4.4.2.
I installed 4.4 and had to re-root, of course losing all my settings and apps, having to reinstall and reset everything to my liking.
I have never made a backup.
I just now upgraded to 4.4.2 update, and all my settings and apps are in tact, however, I lost root.
I do not want to re-root and reinstall everything again, so I need help on recovery and steps involved.
I am still unlocked, and I have the TWRP installed as well as SuperSU and RecoveryTools.
Please advise how to make a backup and re-root in the least painful way.
(PS I did use the Wug'sFresh kit to do my rooting the first time around, and am not very comfortable using the SDK etc)
Thanks!
-Mike
Click to expand...
Click to collapse
have you tried flashing the SuperSU zip in recovery? should be all you need to do to get root back. dont need to lose any data. just re-enable root apps aka grant root permissions when they pop up.
efan3719 said:
have you tried flashing the SuperSU zip in recovery? should be all you need to do to get root back. dont need to lose any data. just re-enable root apps aka grant root permissions when they pop up.
Click to expand...
Click to collapse
Hi efan3719:
I don't have the zip in my SDcard but SuperSU is installed, but when I tap on it it says I need root access, and when I tap on Recover Tools > flash TWRP it says "need root" as well..
Should I download SuperSU zip latest file version and copy it over to my device and then run it using my file explorer?
Sorry, I may be confusing I'm still learning this stuff.
skeletal77 said:
Hi efan3719:
I don't have the zip in my SDcard but SuperSU is installed, but when I tap on it it says I need root access, and when I tap on Recover Tools > flash TWRP it says "need root" as well..
Should I download SuperSU zip latest file version and copy it over to my device and then run it using my file explorer?
Sorry, I may be confusing I'm still learning this stuff.
Click to expand...
Click to collapse
download SuperSU from here http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip, put it on your device. reboot to recovery, flash the supersu zip. reboot. you should now be rooted.
:/
I have the zip file now on my device.
However, when I reboot into recovery TeamWin no longer comes up it goes to dead android character with exclamation point. :/
Try the nexus root toolkit. It makes rooting very easy with great step by step instructions.
mulperi said:
Try the nexus root toolkit. It makes rooting very easy with great step by step instructions.
Click to expand...
Click to collapse
I have that program. I used it to do my original unlock and root.
Can I re-root using that without losing my latest update/and settings?
I cannot boot into Recovery Mode to reinstall SuperSU (which I currently have installed on my system but it won't work when I tap on it because it says I require root).
So I cannot install the SuperSu zip I just placed onto my device.
This is confusing.
Okay I used Wugs again and looks like I am re-rooted.
Wugfresh is the answer to all these questions.-->> http://forum.xda-developers.com/showthread.php?t=1766475
skeletal77 said:
Okay I used Wugs again and looks like I am re-rooted.
Click to expand...
Click to collapse
Pls tell me what you did. Kept all your data?
Sent from my GT-N7100 using Tapatalk 2
jonidontcry said:
Pls tell me what you did. Kept all your data?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Hi,
basically I had my Nexus 7 (2013) upgraded to KitKat 4.4.2 using the automatic (wi-fi) over the air update.
it installed fine but caused me to lose root. no other information was lost, all my apps and settings were the same, i simply lost root.
when you lose root, you are no longer able to access TWRP during the bootloader startup by going into recover mode. it will show a dead Android character.
so I simply connected my Nexus to my pc and (having Wug's Root Tookit and Nexus 7 drivers already installed from my first time rooting) I selected (from Wug's drop down menu - when Wug's program starts up) my build and version.. then it did it's magic and downloaded the pertinent files. (of course you need to have USB DeBugging checked in settings > developer options or whatever..
then i selected Root option and 'install custom recover' check box as well.. and let it do its thing.
TWRP started up automatically during reboot, and did the root.. then my Nexus was all good again, all apps and data in tact, with root. all good.
Hope that helps.
Excellent sharing. I have the same issue after upgrading to 4.4.2 via OTA
Sent from Nexus 7 v2013 using Tapatalk HD
I hope I was able to help.
Basically after a system update, just do the re-root feature of Wugs and you should be good
skeletal77 said:
Hi,
basically I had my Nexus 7 (2013) upgraded to KitKat 4.4.2 using the automatic (wi-fi) over the air update.
it installed fine but caused me to lose root. no other information was lost, all my apps and settings were the same, i simply lost root.
when you lose root, you are no longer able to access TWRP during the bootloader startup by going into recover mode. it will show a dead Android character.
so I simply connected my Nexus to my pc and (having Wug's Root Tookit and Nexus 7 drivers already installed from my first time rooting) I selected (from Wug's drop down menu - when Wug's program starts up) my build and version.. then it did it's magic and downloaded the pertinent files. (of course you need to have USB DeBugging checked in settings > developer options or whatever..
then i selected Root option and 'install custom recover' check box as well.. and let it do its thing.
TWRP started up automatically during reboot, and did the root.. then my Nexus was all good again, all apps and data in tact, with root. all good.
Hope that helps.
Click to expand...
Click to collapse
Fantastic post. I hadn't heard of Wug and did the old school adb push business. This was very very helpful. Many Thanks. :good:
Finally rooted again using Wug.
However it is asking me to make a full backup (nandroid).
Could someone help to show me how to make a backup correctly?
Sent from my GT-N7100 using Tapatalk 2
Just before upgrading from by Google server pushed OTA 4.4 to 4.4.2 I bought Pro version of SuperSU and enabled 'Ota Survival Mode'. Worked great, after OTA still root.
Saved the trouble (with my stock recovery) to temperary 'boot' TWRP via Adb fastboot and Usb-cable to reflash SuperSu.
Yes you should just be able to use WuGFresh's nexus root toolkit to update n7 4.4.2 update
The app won't have a 4.4.2 option but you can just select root any version and it will still be able to root your n7 running 4.4.2
Such a great program...
Hope it helps others...
-droidshadow
Sent from my SCH-I535 using XDA Premium 4 mobile app
droidshadow said:
Yes you should just be able to use WuGFresh's nexus root toolkit to update n7 4.4.2 update
The app won't have a 4.4.2 option but you can just select root any version and it will still be able to root your n7 running 4.4.2
Such a great program...
Hope it helps others...
-droidshadow
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just press Ctrl+U to update and you will see your new version 4.4.2 in the list.
Sent from Nexus 7 v2013 using Tapatalk HD