Not that I would know, I only used your root-method, wich installs superroot?
Everything else was still the stock-rom
And the link was a google-search for a download... first hit... if it's only a driverpackage I obviosly haven't found it
Wasn't there a way to install the update while keeping the root?
Well, that's weird...simply having the root (/system/bin/su and /system/app/Superuser.apk) file present should not cause an OTA to fail to install.
What exactly did you see when it tried to install and when it failed? (if you can remember)
Can you do another check for system update?
The update.zip file (although its likely not named that way) is likely still / already present in your /cache directory, so it wouldn't need to be re-downloaded by the device.
Well, that's weird...simply having the root (/system/bin/su and /system/app/Superuser.apk) file present should not cause an OTA to fail to install.
What exactly did you see when it tried to install and when it failed? (if you can remember)
Can you do another check for system update?
The update.zip file (although its likely not named that way) is likely still / already present in your /cache directory, so it wouldn't need to be re-downloaded by the device.
it showed the green android lying with an open hatch an red x inside... waited 45minutes but nothing happend, then I pulled the battery out... did boot the normal way after that luckily.
Oh and manual check for updates under "settings - phone-info - systemupdates" doesn't show an update... it says the system is uptodate... still running 4.0.2
And /cache seems to be empty, if the "/cache" is the right directory that the ES File Explorer shows...
Last edited by PhinPhin; April 29th, 2012 at 10:31 PM.
it showed the green android lying with an open hatch an red x inside... waited 45minutes but nothing happend, then I pulled the battery out... did boot the normal way after that luckily.
Oh and manual check for updates under "settings - phone-info - systemupdates" doesn't show an update... it says the system is uptodate... still running 4.0.2
And /cache seems to be empty, if the "/cache" is the right directory that the ES File Explorer shows...
Thanks!
Yeah, /cache is the right place, but not having the same model of phone or having it in-hand, I don't know for sure what the file would be called.
Here's a link that looks similar to your issue (no magic answers, though):
Also, this thread: OTA to a newer build of 4.0.4 failed re-iterates that you need a stock recovery installed in order for the OTA to successfully apply.
Can you install my Android Root Toolkit app (free in the Market) and use the "Identify Current Recovery" function and let me know what it says?
Thanks!
Last edited by scary alien; April 29th, 2012 at 11:39 PM.
Also, this thread: OTA to a newer build of 4.0.4 failed re-iterates that you need a stock recovery installed in order for the OTA to successfully apply.
Can you install my Android Root Toolkit app (free in the Market) and use the "Identify Current Recovery" function and let me know what it says?
Thanks!
I can't I only get an error wich says I should try it later again if I try to download any app from the Store.... I hope the update killed not something important. Tried already the obvious stuff, uninstalled the Storeupdates, stopped it, cleared its cache... nothing. Phonerestart doesn't help, too... both on wifi and 3G/EDGE. Man, and I thought staying on the stockrom would keep me away from this crap...
Btw. sorry: its the android with the red triangle with an "!" in it. dunno why I thought it was a cross :P The Update begins normal (standing android with that moving thing) but then after 40% or so I get to see the fail-android. VolUp+VolDown+power also doesn't bring me to the recovery at this point
Last edited by PhinPhin; April 30th, 2012 at 12:05 AM.
Okay, just to double-check, have you used the "Identify Current Recovery" feature to display which recovery you have installed (I'm expecting it to say its the stock 4.0.2 recovery, but it would be good to confirm)?
Okay, just to double-check, have you used the "Identify Current Recovery" feature to display which recovery you have installed (I'm expecting it to say its the stock 4.0.2 recovery, but it would be good to confirm)?
Lemme know .
Sorry, forgot that Here:
Btw. looks like I can now install apps again, maybe it was a temp failure of the Google-servers... Update still fails, though.
I don't know of any way to monitor the stock recovery while it tries to apply the OTA (there's no adb access from the stock recovery to hook into).
LOL--I knew / remember you from the other thread [its no big deal ].
Rooting via that method is very unintrusive--you're only inserting the su binary and the Superuser.apk file--nothing else. So, that should not interfere with you receiving or being able to successfully install an impending OTA.
If you do get another message about an update--tell it to install later, and then examine the file that was hopefully downloaded in your /cache partition. It should be a relatively small file (37MB or so) and we'd be able to examine the installation script inside it to see what its looking for.
Other than that, I'm not sure how to have you proceed (I'd suggest manually installing the OTA yourself, but I'm guessing you'd run into the very same issues that you already are...).
Other than that, I'm not sure how to have you proceed (I'd suggest manually installing the OTA yourself, but I'm guessing you'd run into the very same issues that you already are...).
Okay, how I install it myself? The recovery is stock, so no choice for starting the update manually... or does the stock-recovery only shows the update-option if an *update*.zip is in /cache?
Last edited by PhinPhin; May 1st, 2012 at 02:50 PM.
Okay, how I install it myself? The recovery is stock, so no choice for starting the update manually... or does the stock-recovery only shows the update-option if an *update*.zip is in /cache?
Its the stock recovery that does the update.
The update.zip file (won't actually be called that on download) contains a whole series of assert checks that verifies that your device is the right model, O/S version, and that the various key files on the system that it wants to patch are present and match what's expected.
Can you post a screenshot of your Settings -> About phone screen (i.e., not the phone number subscreen, but the one with the Android version, Baseband version, Kernel version, Build Number, etc.).
I just wonder why, even die manual downloaded file gave that error... can't be a broken file on their server, else everyone would had encountered that.... weird.
I only found it out when trying to update su, I didn't notice a failure when rooting. Was this issue resolved? Any ideas would be great. Thanks I'm using stock 4.0.4.
I only found it out when trying to update su, I didn't notice a failure when rooting. Was this issue resolved? Any ideas would be great. Thanks I'm using stock 4.0.4.
Yep, the solution there was to use the new su.zip file that seems to work better on 4.0.4:
Try flashing that version--it should work much better for you.
Cheers!
Yes. that is the su version that i download. CWM flash looks to be fine.
However, as soon as i reboot from CWM, i go to /system/xbin and there is NO SU there!
i tried adb push of the su , but i cannot do any chmods in order to get 755 so its executable.
env below looks odd to me???
the zip file has /system/xbin/su
but the symlink on my system is as follows:
Code:
ls -l /system/xbin
-rwxr-xr-x root shell 59456 2012-02-06 21:26 dexdump
lrwxrwxrwx root root 2012-05-14 09:51 su -> /system/bin/su
above does not look correct?
the flash will put su in /system/xbin
the symbolic in /system/xbin points to /system/bin
there is no su in /system/bin on my system
AND
after the flash/reboot, i go to /system/xbin expecting to see 'su' and it is NOT THERE???
Yes. that is the su version that i download. CWM flash looks to be fine.
However, as soon as i reboot from CWM, i go to /system/xbin and there is NO SU there!
i tried adb push of the su , but i cannot do any chmods in order to get 755 so its executable.
env below looks odd to me???
the zip file has /system/xbin/su
but the symlink on my system is as follows:
Code:
ls -l /system/xbin
-rwxr-xr-x root shell 59456 2012-02-06 21:26 dexdump
lrwxrwxrwx root root 2012-05-14 09:51 su -> /system/bin/su
above does not look correct?
the flash will put su in /system/xbin
the symbolic in /system/xbin points to /system/bin
there is no su in /system/bin on my system
AND
after the flash/reboot, i go to /system/xbin expecting to see 'su' and it is NOT THERE???
Apologies for the delay...am at work and can't really research this at the moment...
Yeah, its definitely strange because the su.zip should be installing the su binary in /system/xbin and then symlink /system/bin to it.
I see that you've listed your /system/xbin/su file above and it looks like its actually pointing to /system/bin/su (i.e., the reverse of what's supposed to happen?).
I'm thinking that you should be able to manually push things via adb like you mentioned (you'd need to use a 06755 value for its permission bits).
Can you flash or soft-boot CWM, mount /system, manually remove any /system/bin/su and /system/xbin/su before you push it, then resecure it (and optionally symlink the other su)?
If you give me a little time to get home, I can detail the exact commands for you then...
the description you gave should be enough for me to go on for now.
i think the problem may be permissions for chmod the su binary to make it executable.
adb push will put the file out there with rw-rw-r-- permissions and if i dont have authority to chmod in any directory , im stuck.
C:\i\android-sdk-windows\platform-tools>adb shell
shell@android:/ $ su
su
/system/bin/sh: su: not found
127|shell@android:/ $ chmod 06755 /mnt/sdcard/su
chmod 06755 /mnt/sdcard/su
Unable to chmod /mnt/sdcard/su: Operation not permitted
as you can see in the above, im not able to exec su . I can push it fine .
also not able to mount rw ... no permissions ... i dont make sense of this.
Last edited by rowntreerob; May 14th, 2012 at 07:08 PM.
yes.. using "G" softboot and "H", i flashed su.zip then i tried to chmod and had no permissions on the chmod..
while still in CWM after the flash , i chose 'reboot' and used and existing open shell .. maybe i need to open a new cmd shell in windows after the CWM reboot ??
opened new windows CMD immediately after 'reboot' from within CWM and heres what i get:
Code:
cd /mnt/sdcard
shell@android:/mnt/sdcard $ chmod 06755 su
chmod 06755 su
Unable to chmod su: Operation not permitted
I'm in need of help, I rooted, and unlocked my bootloader earlier, but my phone doesn't have root access! I can't used any root apps, but the Superuser app is installed, I tried to flash the recovery that was mentioned to work when the other doesn't work, but whenever I can't boot into recovery, I get the triangle with the "!" inside it. There's an option in Wug's Toolkit, that says flash recovery, I'm not sure if I should/can use it, any help or insight would be great, thank you!
__________________
I find that a duck's opinion of me is largely influenced by whether or not I have bread.
-FrenchToast
I'm in need of help, I rooted, and unlocked my bootloader earlier, but my phone doesn't have root access! I can't used any root apps, but the Superuser app is installed, I tried to flash the recovery that was mentioned to work when the other doesn't work, but whenever I can't boot into recovery, I get the triangle with the "!" inside it. There's an option in Wug's Toolkit, that says flash recovery, I'm not sure if I should/can use it, any help or insight would be great, thank you!
FrenchToast,
Apologies for the belated reply...been crazy busy these last few days.
I don't know if you are on 4.0.4 already or not, but it you are, then you'll need to use the su.zip package that works best for 4.0.4:
(I would bet that it would work fine on 4.0.2, also).
If your install custom recovery is going away, its because at shutdown time there's a file called /system/recovery-from-boot.p whose presence indicates to Android that the stock recovery should be re-flashed.
for manually fixing this after you've successfully attained root.
You can also install my (free) app, Android Root Toolkit, which has an option for renaming the recovery-from-boot.p file. Its link is in my signature (which I'm hoping will show up in this post ).
(I would bet that it would work fine on 4.0.2, also).
If your install custom recovery is going away, its because at shutdown time there's a file called /system/recovery-from-boot.p whose presence indicates to Android that the stock recovery should be re-flashed.
for manually fixing this after you've successfully attained root.
You can also install my (free) app, Android Root Toolkit, which has an option for renaming the recovery-from-boot.p file. Its link is in my signature (which I'm hoping will show up in this post ).
i looked into this and i guess that symlinks to "toolbox" in /system/bin are different than symlinks to "busybox" in /system/xbin.
i dont think i had busybox.. i had root , but no busybox.
i thought u got BB with root.
i used this method to root and thought that tar / grep would be included with the toolbox? They are not there in the symlinks in /system/bin
What am i supposed to do with root if i want to mount /data and then install a package or an RPM there so that i can do some shell scripting and c work?
I want to move a tar to /data/local and then unpack it. Not able to because tar is not found ??
what i dont have that i need: (tar / which / grep )
Code:
127|shell@android:/ # which
which
sh: which: not found
127|shell@android:/ # grep
grep
sh: grep: not found
127|shell@android:/ # tar
tar
sh: tar: not found
127|shell@android:/ #
Last edited by rowntreerob; June 1st, 2012 at 05:16 PM.
Reason: new data
Here's the dump of supported commands for the version that I have installed:
Quote:
C:\Users\Scary Alien>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
root@android:/ # busybox
busybox
BusyBox v1.19.4-cm9 bionic (2012-02-05 18:40 +0100) multi-call binary.
Copyright (C) 1998-2011 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2. Merged for bionic by tpruvot@github
See source distribution for full notice.
Usage: busybox [function] [arguments]...
or: busybox --list[-full]
or: function [arguments]...
BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as.
.
There is no "root exploit" required to root the Samsung Galaxy Nexus since it comes with an unlockable bootloader. So, this means that there is not soon likely to be a 1-click or easy rooting app to run that exploits something in Ice Cream Sandwich in order to root the phone.
This seems like a 1-click method in the thread below. Anything wrong with this?
I've read about Adam Outler's CASUAL adb utility/tool. I'm guessing this tool might use the same mempodroid exploit used in the thread I wrote about up-top. The reason I say this is that it won't work on ICS higher than 4.0.2. As far as I know, unless you save/protect root in 4.0.2, the only way to root past 4.0.2 is to boot an insecure boot image file and/or softboot/flash a custom recovery and flash the su.zip file.
Quote:
And if you want your mind to be blown, go read this:
Yeah, I've read about mskip's GNex toolkit before. Its very nice and very comprehensive. But again, these are just variations of tools like Wugfresh's toolkit (although I do believe mskip's tool existed before Wug's ).
Unfortunately, this only works on ICS 4.0.1 or 4.0.2 devices since the kernel exploit was patched for 4.0.4.
This appears to be a tool on-par with Wug's Gnex root toolkit. Very nice, but not really new.
I've read about Adam Outler's CASUAL adb utility/tool. I'm guessing this tool might use the same mempodroid exploit used in the thread I wrote about up-top. The reason I say this is that it won't work on ICS higher than 4.0.2. As far as I know, unless you save/protect root in 4.0.2, the only way to root past 4.0.2 is to boot an insecure boot image file and/or softboot/flash a custom recovery and flash the su.zip file.
Yeah, I've read about mskip's GNex toolkit before. Its very nice and very comprehensive. But again, these are just variations of tools like Wugfresh's toolkit (although I do believe mskip's tool existed before Wug's ).
Cheers!
I believe the two bottom ones say they've been updated to work with jelly bean.
I'm at the airport right now and can't look it up well on this esteem. Can't wait to get the bigger screen of nexus.
________________
EDIT: yep, at least 3 of the 4 support Jelly Bean for rooting 1 click.
I believe the two bottom ones say they've been updated to work with jelly bean.
I'm at the airport right now and can't look it up well on this esteem. Can't wait to get the bigger screen of nexus.
Yeah, you're gonna love the GNex .
In addition to the above (or maybe they've already reference it?) but you can do many of the same flashing operations using Odin (or Heimdall) vs. using fastboot.
I unfortunately, haven't yet worked with Odin...
So may ways to do things with an unlocked bootloader [its great to have so many options].
Just make sure after you install the Win7 Samsung USB drivers to reboot the PC, then go from there. In the first step you use the Nexus volume button to arrow up and down on the screen to make a choice, then use the power button to "start" the process. During that time there is a graphic on the screen with the instructions, but I was in a hurry, trying to PRESS the screen to make the choices.
Okay, it won't work without a wipe because of the locked bootloader... gah
But how I can make a backup of the apps (won't lose all game-saves again) and homescreen-settings of widgets and icons? The Toolkit saves a 700MB file, that can't be all apps (>6GB)
Device(s): GNex GT-i9250 with AndroidME v.1.4,
(formerly) LTE LG Esteem with ROM #2,
LG Optimus M
Carrier: Straight Talk SIM
Thanks: 36
Thanked 124 Times in 90 Posts
Quote:
Originally Posted by PhinPhin
Okay, it won't work without a wipe because of the locked bootloader... gah
But how I can make a backup of the apps (won't lose all game-saves again) and homescreen-settings of widgets and icons? The Toolkit saves a 700MB file, that can't be all apps (>6GB)
This thread is useful for your purposes. Go to the link, there's more info I didn't copy and paste including a mention of homescreen icons.
Before anything make a android if anything should go wrong you can restore.
For messages I suggest SMS Backup and Restore found in the play store.
For apps and all that use titanium backup and restore app+data on jellybean which will import all settings and data the application had on the original backup.
Contacts should have been backed up to the Google servers so you don't really have to worry about that, once you sign in to jellybean for the first time your contacts will be completely restores automatically.
Home screens not possible , to my knowing, unless you use a third party launcher such as Nova which let's you backup home screens
Last edited by ChazzMatt; July 18th, 2012 at 09:25 AM.
-- simplest and fastest from what I've found
-- works for both GSM and LTE versions of the device
-- does not require a special (insecured) boot.img file
Cons: requires both adb and fastboot USB connectivity
Brief description:
- download su.zip flashable root package and proper version of ClockworkMod
- put phone in fastboot mode
- soft-boot or flash ClockworkMod custom recovery
- push the su.zip file to your phone via adb
- flash the su.zip root package in ClockworkMod to install root
- reboot phone
I wanted to use this method to root my JB phone.
Recently I used the ClockworkMod to flash my phone to 4.1.1 and everything seemed to work perfectly. Later I wanted to use the above method to root it and I've encountered a problem - the recovery mode of ClockworkMod won't start. It ends up with android error and I have to take out my battery.
What is the easiest way to root a phone right now? I am a linux user so no windows programs will do it for me (it's quite a lot of struggle to find a friend willing to borrow a computer and then mess around with it...).
Also, wiping data from my cell phone is not an option (bootloader is unlocked though).
Any ideas?
I wanted to use this method to root my JB phone.
Recently I used the ClockworkMod to flash my phone to 4.1.1 and everything seemed to work perfectly. Later I wanted to use the above method to root it and I've encountered a problem - the recovery mode of ClockworkMod won't start. It ends up with android error and I have to take out my battery.
What is the easiest way to root a phone right now? I am a linux user so no windows programs will do it for me (it's quite a lot of struggle to find a friend willing to borrow a computer and then mess around with it...).
Also, wiping data from my cell phone is not an option (bootloader is unlocked though).
Any ideas?
Welcome to the AndroidForums, Bungi!
So, are you in fact rooted? (did you previously successfully flash CWM and flash the su.zip file)
It kind of sounds like you just need to make the recovery "stick" (Android will re-write the stock recovery every time you shut down unless you disable a file that tells/allows him to do so).
If this sounds right, then take a peek at the Flashed custom recovery won't "stick"? section in this post:
Also, I created a (free, in the Market) app called Android Root Toolkit that has an option to "make recovery stick".
Please note that after you've taken steps to make the recovery stick, you'll have to re-flash your custom recovery so it's present again (my app also has some custom recovery flashing options for the Galaxy Nexus, so you can re-flash it with it).
Let me know .
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
So, are you in fact rooted? (did you previously successfully flash CWM and flash the su.zip file)
Not quite. I was rooted before updating to JB. I didn't delete any files and according to Superuser.apk I have the /system/bin/su file but no root shell.
I wanted to root it the way I used to (fastboot - recovery mode - flash with su.zip) but the phone crashes the moment it boots in recovery mode. It works fine in fastboot but when I switch to recovery and tell it to boot that mode it crashes. I downloaded your app but I reckon I'd need to be rooted first to use it...
Thanks for a quick answer!
EDIT:
I just checked with a terminal emulator - I have no permission to use "su" command.
Last edited by Bungi; July 19th, 2012 at 04:07 PM.
Not quite. I was rooted before updating to JB. I didn't delete any files and according to Superuser.apk I have the /system/bin/su file but no root shell.
I wanted to root it the way I used to (fastboot - recovery mode - flash with su.zip) but the phone crashes the moment it boots in recovery mode. It works fine in fastboot but when I switch to recovery and tell it to boot that mode it crashes. I downloaded your app but I reckon I'd need to be rooted first to use it...
Thanks for a quick answer!
EDIT:
I just checked with a terminal emulator - I have no permission to use "su" command.
So, you obtained JellyBean as a result of an over-thead-air (OTA) update, right (vs. installing a JB custom ROM)?
If you did install/take an OTA, then yeah, you're going to have to re-root by re-flashing ClockworkMod custom recovery via fastboot and then flash the su.zip (be sure to use the newer, up-to-date su.zip that I mention at the top of the first post in this thread).
OTAs clobber root because the su binary gets re-secured during the installation process. You could have saved root with OTA RootKeeper (or even with my app that I mentioned earlier) since they'll allow you to restore root after having previously saved it.
The good news is that your bootloader is unlocked, so all you really have to do is:
- download / copy the new su.zip file to the top-level of your /sdcard folder
- put phone in fastboot / bootloader mode
- fastboot flash recovery recovery.img (using the proper recovery.img name, of course)
- flash the new su.zip (that you've already copied to your /sdcard)
- reboot
After you reboot, you'll be rooted and you can make your recovery stick as I described in the previous post.
Let me know how it goes!
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
So, you obtained JellyBean as a result of an over-thead-air (OTA) update, right (vs. installing a JB custom ROM)?
Here's what I did:
The system let me know there is an update and it downloaded an upgrade. Then I turned on the phone on recovery mode (up/down button + power) and picked "install .zip from sdcard" and pointed to the upgrade that was downloaded by system itself (I had to cp it to sdcard from cache). And it went fine
Quote:
The good news is that your bootloader is unlocked, so all you really have to do is:
- download / copy the new su.zip file to the top-level of your /sdcard folder
- put phone in fastboot / bootloader mode
- fastboot flash recovery recovery.img (using the proper recovery.img name, of course)
- flash the new su.zip (that you've already copied to your /sdcard)
- reboot
Last (hopefully) quick question. Do I flash the recovery with the ROM that I used for upgrade? Or maybe can i flash it somehow with ClockworkModRecovery (I liked the options it offered in recovery mode).
I would like to mess it up when I'm so close to a happyend
EDIT:
Nevermind I just flashed the recovery mode from Clockwork and then installed the su.zip and it works perfectly! Thank you so much
Device(s): GNex GT-i9250 with AndroidME v.1.4,
(formerly) LTE LG Esteem with ROM #2,
LG Optimus M
Carrier: Straight Talk SIM
Thanks: 36
Thanked 124 Times in 90 Posts
Just want to say I've used this 1-click solution now on both my Galaxy Nexus phone and now my wife's Galaxy Nexus phone. Worked very well. Mine had ICS 4.01, but hers had received the 4.1.1 Jelly Bean OTA -- it rooted them both just fine.
Even lets you back up and restore the APN.
This package has now been updated to Nexus Root Toolkit v1.5.2.
1Likes
I only get an error wich says I should try it later again if I try to download any app from the Store.... I hope the update killed not something important. Tried already the obvious stuff, uninstalled the Storeupdates, stopped it, cleared its cache... nothing. Phonerestart doesn't help, too... both on wifi and 3G/EDGE. Man, and I thought staying on the stockrom would keep me away from this crap... 
