Related
Okay, this is extremely irritating. I'm getting an "installation aborted. Status (0)" when trying to install the SU zip from recovery. If I use superboot it just gets stuck at Google's logo. Below are some more info:
running IMM76I 4.0.4 (GSM)
I tried using CWM, CWM Touch, TWRP 2.1 (all "booted" only), superboot. All recoveries were for GSM Galaxy Nexus (maguro)
I tried using su binaries only, full su, downloading again both. MD5 is correct.
I tried fixing permissions, wiping dalvik cache, mount/unmount system, toggle signature verification, toggle script asserts, fastboot oem lock/unlock
At the end of everything, SU is installed but I have no root..
Update: I think I *might* have pinpointed the problem: it appears that the recoveries are trying to read the su.zip from /sd-ext, which if I'm correct does not exist on the GNex (only sd-int).. now why the heck would that happen? Might it be because I only fastboot boot'ed them and not fastboot flash'ed? I'd rather keep my stock recovery if possible..
Any help would be greatly appreciated, I've been going crazy for the past 3h trying to gain root, which should be a matter of minutes with a "dev phone" like the Gnex...
Unless you're specifically trying it the manual way for the experience why not just use the GNex toolkit to unlock/root/etc?
Why not just flash the recoveries then return flash the stock recovery back..?
Why do you want to keep the stock recovery?
Copy the file from here to the root of your /sdcard, reboot into CWM and flash the zip... Or better yet, just follow the instructions in that link.
Ok, I tried WugFresh's Gnex toolkit. Everything goes fine till the phone reboots, than it gets stuck at "rooting your Galaxy Nexus".
I'm starting to think it might be the ROM, despite it being 100% stock. I will try re-flashing the whole stock image (downloading atm) and see what happens.
p.s.: I'm not a noob (I thought it would be obvious from the first post but apparently some people missed it :laugh: ), so I know how to root under "normal" circumstances. No need to point me at "how-to-root" threads unless they contain particular information about this specific situation (su.zip installation aborted).
Thanks to everyone who has replied so far!!
Lazer Bear said:
Ok, I tried WugFresh's Gnex toolkit. Everything goes fine till the phone reboots, than it gets stuck at "rooting your Galaxy Nexus".
I'm starting to think it might be the ROM, despite it being 100% stock. I will try re-flashing the whole stock image (downloading atm) and see what happens.
p.s.: I'm not a noob (I thought it would be obvious from the first post but apparently some people missed it :laugh: ), so I know how to root under "normal" circumstances. No need to point me at "how-to-root" threads unless they contain particular information about this specific situation (su.zip installation aborted).
Thanks to everyone who has replied so far!!
Click to expand...
Click to collapse
I pointed you to that link because you may have downloaded an incompatible superuser zip. I packaged that one up, so I know it works.
P.s. Not sure about other recoveries, by the non-touch version of CWM looks for files in /sdcard (i.e., /data/media) and sub-folders, not anywhere else...
Sent from my Galaxy Nexus using Tapatalk 2
HOORAY! I did it!!!
This is what I did:
1-downloaded latest WugFresh's Toolkit (tired of doing everything manually and getting 0 results..)
2-tried flashing stock rom, got stuck after it flashed the bootloader
3-Downloaded another toolkit from xda (Gnex toolkit 7.0)
4-successfully flashed stock with that.
5-tried rooting using that one, got stuck after booting insecure image
6-went back to Wugfresh's, successfully rooted using it!!
So, basically I have no idea how or why this problem happened nor how I solved it, but after 2 days and 5h I did it! Lol..
So I used odin to flash the official stock jelllybean rom then I used the Samsung toolkit to flash clockwork mod recovery and root. To root it said to flash a superuser zip in recovery. I did.after I reboot everything is working fine. Apps gain root access the promp pops up but after a few minutes it didn't anymore and I cant open busybox or setcpu because it cant gain access but the apps I already granted can. I updated su binary and it fails on gaining root access.
This happens with both super su and superuser. I also tried starting again by oding rom and rooting again. No luck. Please help
Sent from my SGH-T999 using xda premium
Sent from my SGH-T999 using xda premium
Ok, you can try a few things.
First since you have Root Explorer already granted, go into /system/xbin and make sure that there is a file named su. If not, then go into /system/bin and see if it is there. Follow this: If it is in /system/bin, copy it and put it in /system/xbin, check permissions and reboot. Then try an un-granted app and see if that works. Pay attention to the bin and xbin parts here ok.!?
^^^Edit: While you are in /system/xbin make sure that busybox is there also. Just to be sure it installed properly.
Second. If the above didn't work, the go to the market and ChainsDD used to have an app called SuperUser Updated Fixer or something like that. I remember a long time ago, I was having some trouble updating the binaries (as were tons of other people) and he came out with that handy little app. I have been using it since (whenever I have a ROM that uses SuperUser.apk).
Third: I literally just read over in mrRobinson's thread that ICS likes SuperUser, while JB likes SuperSU. Might be something to look into. Maybe swapping out the two apps, might alleviate the issue.
I tried swapping out to super su but was having the same problem. Instead of trying the root explorer method you posted I thought I would go ahead and clean install yet another time. I just wanted the update and root access to work no errors. So here's what I did to fix it and it worked however there's another problem now.
I factory reset, wiped caches
flashed jb stock firmware (instead of the stock fw i now flashed mr.robinsons prerooted firmware)
rebooted checked and saw super su was working fine with my apps.
flashed clockwork mod recovery
made a nandroid backup
flashed wildchilds stock deodexed jb rom (i needed a deodexed rom thats why i flashed this otherwise i would of just kept stock)
booted up and in the play store theres an update for Super Su however i cant update it, it gives me an error.
error retrieving information from server. cant download.tried wifi on off, mobile data on off, clearing google play data and cache. no luck. restored nandroid and there was no update so i clicked reinstall from playstore in su and when i went to go download it, it gave the same error.
So my previous problem is fixed and i dont seem to be losing root anymore but now I cant update SU anymore.
Never mind I seemed to have linked the two issues just because 1 happened before the other, but that might not be the case.
The Google play error is now happening with other apps that i try to update as well.
Is this happening to you guys too?
sometimes when i power off my phone it doesnt boot anymore it gets stuck on boot loop. for example all i did was fix permissions in cwm and it got stuck on boot loop.
Did you Odin root66?
Yeah I odined the root 66 fw by Robinson. That has fixed losing root. Super user is working fine. The only remaining problem is that I get into a boot loop sometimes when I restart for some reason like when I fix permissions.
Sent from my SGH-T999 using xda premium
okay so this may have been addressed but im going to tell my way of fixing the lag (it worked for me it might not for you)
So this is a complete shot in the dark but here we go:
So i have a Sprint Galaxy Nexus and I used to have the lag that everyone else is having
so i started to wonder what my phone was getting it from...
well i noticed if i used Odin to flash stock 4.2.2 the lag was gone but then instantaneously after I rooted the device again and installed busybox and a permarecovery mod (WugFresh toolkit's AIO setup) it started too lag again D:
So I was very confused and I remembered that my first Sprint Galaxy Nexus did not have this proplem but then I remembered it started off on 4.0.4 ICS and was updated through OTA to 4.2.2 before I rooted it using a linux based toolkit ( not wugfresh's kit)
so i proceeded to dig around and see what i could do
And i came up with this...
1. back up your stuff ( EVERYTHING!)
2. use the wugfresh toolkit to downgrade your nexus to the earliest or any ICS based firmware
3. do not use the wugfresh toolkit to root/busybox/permrecovery
4. Update through OTA to 4.2.x
5. if you locked your BootLoader Unlock it now!
6. while device is unrooted use MTP to bring over your ROM of choice to your internal storage
6. use a different toolkit to install a custom recovery....DO NOT ROOT/BUSYBOX/PERMRECOVERY THE STOCK ROM (if you want to run a stock based rom with root find a flashable zip after these steps
7. dont boot into a stock firmware as it will reset your recovery so from the bootloader after installing the custom recovery, Reboot into it then perform a NANDROID backup just in case
8. Install rom of choice! and there you go thats what i did and i have no more lag issues besides the normal stuff
Thank you hope this is helpful!
AaronEmoBoi said:
okay so this may have been addressed but im going to tell my way of fixing the lag (it worked for me it might not for you)
So this is a complete shot in the dark but here we go:
So i have a Sprint Galaxy Nexus and I used to have the lag that everyone else is having
Click to expand...
Click to collapse
Never had lag here, i think this lag is caused from apps installed instead android...
AaronEmoBoi said:
so i started to wonder what my phone was getting it from...
well i noticed if i used Odin to flash stock 4.2.2 the lag was gone but then instantaneously after I rooted the device again and installed busybox and a permarecovery mod (WugFresh toolkit's AIO setup) it started too lag again D:
Click to expand...
Click to collapse
Done this phases 2 hours ago ( i update PA ), don't lag, how do you root your device? busybox installed from market ? recovery installed how?
i suggest use natural method
Flash factory image
Flash recovery ( use: fastboot flash recovery openrecovery-twrp... , instead using toolkit )
download SuperSu Universal installer zip from Chainfire's thread
Flash this zip
Install busybox installer from market and do normal install
AaronEmoBoi said:
So I was very confused and I remembered that my first Sprint Galaxy Nexus did not have this proplem but then I remembered it started off on 4.0.4 ICS and was updated through OTA to 4.2.2 before I rooted it using a linux based toolkit ( not wugfresh's kit)
so i proceeded to dig around and see what i could do
And i came up with this...
1. back up your stuff ( EVERYTHING!)
2. use the wugfresh toolkit to downgrade your nexus to the earliest or any ICS based firmware
3. do not use the wugfresh toolkit to root/busybox/permrecovery
4. Update through OTA to 4.2.x
5. if you locked your BootLoader Unlock it now!
6. while device is unrooted use MTP to bring over your ROM of choice to your internal storage
6. use a different toolkit to install a custom recovery....DO NOT ROOT/BUSYBOX/PERMRECOVERY THE STOCK ROM (if you want to run a stock based rom with root find a flashable zip after these steps
7. dont boot into a stock firmware as it will reset your recovery so from the bootloader after installing the custom recovery, Reboot into it then perform a NANDROID backup just in case
8. Install rom of choice! and there you go thats what i did and i have no more lag issues besides the normal stuff
Thank you hope this is helpful!
Click to expand...
Click to collapse
Useless and stupid IMHO, no reason for "lag gone",
when you flash ROM or kernel, anything will wiped and formated, reflash again over and over is useless
I had my Nexus 7 (currently on stock 4.4) rooted originally. It was working fine. I then went to XDA, downloaded a rooted version of the stock 4.4 ROM. It seemed to work fine. Then, somewhere between a reboot, root decided to stop working entirely. Yes, I have tried repeatedly to flash the superuser.zip file. Literally nothing happens. It says it worked in recovery, but when I reboot the tablet, the Superuser app is nowhere to be found, and none of my rooted apps work. I also tried reflashing an entire rooted ROM, but any time I flash any ROM, it gives me an error in recovery and I can't do it (using TWRP, btw). I am tempted to just wipe the thing clean but I have some apps that I can't really back up the data with (you guessed it) without root.
PLEASE, I need help.
darnocs1 said:
I had my Nexus 7 (currently on stock 4.4) rooted originally. It was working fine. I then went to XDA, downloaded a rooted version of the stock 4.4 ROM. It seemed to work fine. Then, somewhere between a reboot, root decided to stop working entirely. Yes, I have tried repeatedly to flash the superuser.zip file. Literally nothing happens. It says it worked in recovery, but when I reboot the tablet, the Superuser app is nowhere to be found, and none of my rooted apps work. I also tried reflashing an entire rooted ROM, but any time I flash any ROM, it gives me an error in recovery and I can't do it (using TWRP, btw). I am tempted to just wipe the thing clean but I have some apps that I can't really back up the data with (you guessed it) without root.
PLEASE, I need help.
Click to expand...
Click to collapse
Do you have super user in your settings? If not try downloading it from the play store. Also on some roms root needs to be enabled under developer options.
chrisg553 said:
Do you have super user in your settings? If not try downloading it from the play store. Also on some roms root needs to be enabled under developer options.
Click to expand...
Click to collapse
It's not in settings or dev settings; this is a stock ROM that was (supposedly) just pre-rooted. I've tried downloading from the Play Store, but it doesn't work. The device still acts like it hasn't been rooted.
Maybe you should give SuperSU a try...
Dexxon said:
Maybe you should give SuperSU a try...
Click to expand...
Click to collapse
Yes, but not from the app store. You have to flash the zip-file from the SuperSU-website.
I think you need to start over...
Well there are a few things you can do....
I think first thing you should try is the WuGFresh Nexus Root Toolkit.
You can download that program which needs to be run on a Windows computer here -> http://www.wugfresh.com/nrt/
That program is such an amazing piece of software it does everything for you!
First start off with getting the proper drivers installed onto your Windows computer so that you can communicate with your Nexus 7 tablet. The Nexus Root Toolkit will show you how to install the drivers correctly, just follow the steps.
After you have the drivers installed you should unlock the bootloader, which can be done again from the toolkit.
After you unlock your bootloader you can now root your toolkit. When you are going to root your tablet you should install an advanced custom recovery manager. Hands down the best is TWRP recovery which can be installed via the rootkit. Under the root button is a box that says install custom recovery, just tick that box and hit the root button and the Nexus Root Toolkit will do everything for you.
If that works then you can install Titanium Backup and do a backup of your apps that you don't want to loose.
Second option:
I saw in your post that you said that you tried to boot into recovery and flash the super.zip. Are you using the SuperSu.zip? If you are able to boot into recovery and flash zips that means you already have a custom recovery manager so what you can do is do a back up of your data partition. This will save all of your apps and your progress/data on the apps so if you reformat your tablet you can always restore that data partition to bring back your apps + data.
If you can make a backup your data partition then I would personally recommend that you reformat your tablet. I would delete everything and reinstall the stock Nexus 7 ROM and then I would root the tablet with the Nexus Root Toolkit and go from there.
Here is a good link to show you how to reformat and install the stock Nexus ROM from scratch...
Link -> http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
I personally have used that link and its step by step guide to reset my Nexus 7 so i can say that it will work for you 100% just as long as you follow the steps correctly.
Next time don't be afraid to root your tablet yourself. I know that it can be intimidating...but there are so many documentations and videos on Youtube.com to help you root your Nexus 7 tablet, and you can always ask questions here on XDA.
I hope this has been helpful for you....
If you have anymore questions please let me know....
-droidshadowd
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.
So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?
Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.
Thanks in advance...
skallal said:
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.
So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?
Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.
Thanks in advance...
Click to expand...
Click to collapse
In order to run the stock OTA you need to put your system back to stock. That means stock recovery, remove ALL modifications to the system partition (root, ad blocks, etc...) then you can run it. If that sounds like too much work - just back up and flash the factory image then restore.
I was rooted with the Wugfresh toolkit. I downloaded the 5.0 (and later 5.0.1) factory image from Motorola and unpacked it. I edited the flash-all.bat batch file (right click, Edit -or- right click, Open With, select notepad/wordpad) and removed the -w flag from the end of the file. It's not the very end, but very close. Just delete the -w and any excess spaces and save the file. The -w flag is what tells it to do a wipe of all data, removing it will prevent that. Put your Nexus into bootloader mode and double click the batch file.
Once it finishes flashing, it will boot up and say "optimizing apps" or "Android is updating" or something like that. Mine took about 15 minutes. After that, run the Chainfire Auto Root (CFAR) script to get root access back, and you're back in business.
Note: flashing Factory Images and running CFAR require an unlocked bootloader. CFAR will unlock the bootloader AUTOMATICALLY as part of the script. This WILL RESULT IN A LOSS OF DATA. If you are already unlocked, you're fine, as long as you remove the -w flag from the batch file.
Also, you do not need to go from 4.4.4 to 5.0 to 5.0.1, you can jump straight from 4.4.4 to 5.0.1.
There is also this:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
At least a few of us have used that with no issues. I was running stock rooted 4.4.4 with TWRP, so I updated my bootloader, rebooted into recovery, wiped cache and Dalvik (probably not necessary before flashing), flashed the ROM, wiped cache and Dalvik again, and rebooted, and it's working great with no loss of data.
Telyx said:
There is also this:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
At least a few of us have used that with no issues. I was running stock rooted 4.4.4 with TWRP, so I updated my bootloader, rebooted into recovery, wiped cache and Dalvik (probably not necessary before flashing), flashed the ROM, wiped cache and Dalvik again, and rebooted, and it's working great with no loss of data.
Click to expand...
Click to collapse
^I am going to do this, after reading similar reports of success.
However, to OP I want to stress that it is important that you update your bootloader before flashing the ROM. The patch is attached to the linked post.
While I am definitely tech savvy, I am not that comfortable with the WugFresh toolkit. For example, I just updated it to v1.9.9 and connected my device. While I know I previously unlocked the boot loader and rooted my device, the toolkit itself does NOT tell me if my device is unlocked or rooted.
Is there a tutorial somewhere describing how to update to Lollipop with the WugFresh toolkit? Thanks to @fury683 for the comment about editing the batch file. But I don't know what that means with respect to the toolkit user interface, that is what buttons are clicked in what order. I need a step by step list of instructions before starting.
@OrBy, by flash the stock image, do you mean the 4.4.4 image or the new 5.0.1 image? And how do I flash the image? WugFresh toolkit?
I used the WugFresh toolkit a few months ago, but have forgotten the steps I took. Should have written it down. I'll try to stick with the WugFresh toolkit.
Thanks for all the comments
Factory images and Wugfresh are not used together. Wugfresh is a collection of things while factory images return the device to 100% factory stock out of the box. If you modify the batch file as detailed above, no user data/apps are removed, just the system, recovery, etc partitions.
Factory images are a one click method that has a very similar end result as Wugfresh does to return to stock. I would go with factory images as it is the easiest and most straight forward method. Run batch, confirm, wait about 1-2 minutes, done.
skallal said:
@OrBy, by flash the stock image, do you mean the 4.4.4 image or the new 5.0.1 image? And how do I flash the image? WugFresh toolkit?
Click to expand...
Click to collapse
Well if your hung up on running the OTA then the 4.4.4 but if I were you I would just flash the 5.0.1 and skip the who OTA.
I managed to update to 5.0.1 without wiping the device using WugFresh. I went to the WugFresh site, read the FAQ, and found how to update without wiping clean. Turns out there is an option to disable wipe without editing the batch file. I was able to do the while procedure leaving the device unlocked.
I did have an unexpected issue. I had to reinstall in the USB drivers on my PC before I could re-root it. WugFresh made this part easy too, though I'm surprised a reinstall was even required. Once that was done, USB connection was restored and I could complete the rooting process.
I always stress out whenever updating Android in any way. The rules are different with each device and OS version.
One change I've noticed I'd that my Nexus 7 brightness I'd dimmer and I have to turn to setting higher. Hope the update is worth the trouble.
Follow up: after all the work upgrading to 5.0.1, I decided I didn't like the new version. I did the upgrade without a clean wipe. But I did the downgrade with a clean wipe.
The WugFresh toolkit is quite capable utility. I couldn't imagine doing it the hard way with the adb command line interface. At least know how to recover and rebuild my system should the need ever occur in the future. And Titanium Backup is indispensable too.
I found Lollipop to be a battery hog. Perhaps I'll try it again when some of the issues are worked out. There is no compelling reason change from Kit Kat at this time, IMHO.
OrBy said:
In order to run the stock OTA you need to put your system back to stock. That means stock recovery, remove ALL modifications to the system partition (root, ad blocks, etc...) then you can run it. If that sounds like too much work - just back up and flash the factory image then restore.
Click to expand...
Click to collapse
This is NOT true. I upgraded while rooted and it went fine. Just beware of xposed and other tools that mess up with /system and thus the upgrade scripts.
While I was able to update from KK (4.4.4) to LP (5.0.1) without wiping the data, it didn't work out for me. The battery life was terrible. It drained at least twice as fast compared to before the update. I was trying to avoid the pain of a clean install. But in the end, it wasn't worth with it.
I ended up going back to KK, and then to LP again but with a clean install. When installing LP the second time, I wiped the data and let Google reinstall all of the apps. There were a small number of apps, that I later restored the data from Titanium Backup, for example games with previous scores.
This made a huge difference in battery life. Plus the look and feel of many apps changed to the new Material design.
I'm not entirely sure I like the look of LP. I'd prefer LP under the hood, but the look of KK. Oh well!
Bottom line: don't do OTA updates with a major new release.