Related
Anyone knows how to install busybox?
I've tried to follow some guides but ends up with:
Code:
215:Desktop ricardo$ adb push busybox /data/local
580 KB/s (1083568 bytes in 1.823s)
215:Desktop ricardo$ adb shell
$ su
# cd /system/xbin
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cat /data/local/busybox > busybox
cannot create busybox: not enough memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# dd if=/data/local/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Out of memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# ./busybox cp /data/local/busybox /system/xbin
cp: can't create '/system/xbin/busybox': Cannot allocate memory
same here. cannot write to rw-mounted /system.
sucks
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
I have the same problem
ricardoft said:
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
Click to expand...
Click to collapse
What should I do with your files?
Nobody has a solution to this?
I don't think this is a memory issue though, .. added 512mb swap and still it claimed to be out of memory, ..
also I figured maybe hd space .. however when i ln /data/local/tmp/busybox to /system/xbin it had the same error.
I both tried ln from the system and ln from busybox both had same result.
It's not a memory problem! In order to install it you have to be in recovery mode.
Try:
While in recovery mode use adb to connect to our phone. Now transfer the zip file (busybox.zip) to your phone and install it via clockwork recovery -> install zip file -> select my zip file.
can anyone post the proper busybox file cause for some reason the file signature verification failed.
adb push busybox-signed.zip /sdcard/busybox-signed.zip
rebooted phone held down volume button while booting ..
choose recovery, ..
choose install zip from sdcard..
then i see a lot of no and one yes .. so i choose yes but the installation is aborted.
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
it has error during installation at line 4 with your busybox.zip
somethinf like can not chmod
(rooted buzz with stock rom)
Elibongo said:
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
Click to expand...
Click to collapse
Do what this guy said.
titanium install in /sdcard busybox, not in /system/bin (xbin) , so it is not usuable by other apps
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
kevin2516 said:
Do what this guy said.
Click to expand...
Click to collapse
you have read my mind especially since that isn't free software.
hellysmile said:
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
Click to expand...
Click to collapse
i think you need to create aliases however why install it in xbin anyways then, .. if you need to create aliases or links in bin.. ?
example
$ ln -s /data/local/tmp/busybox ls
$ ./ls
if it is in a path that is included in PATH executing a command will auto look for it in all directories defined in PATH env so basicly you could just create all the directories under /data/local/tmp/bin
and just then append that to PATH env echo $PATH then append :/data/local/tmp/bin to it and busybox should work as well.
Ofloo said:
you have read my mind especially since that isn't free software.
Click to expand...
Click to collapse
titanium backup is free software... look on the market, there's a free version and a donate version.
i have aliases in /system/xbin
they was created after busybox --instal -s
but in system allready exists some commands like ls => i want to use ls from busbox, not from system
and terminal emulator dont anderstand ^[ likes bindings
is there a definitive way to do this. There seems to be no clear way of doing it.
matpol said:
is there a definitive way to do this. There seems to be no clear way of doing it.
Click to expand...
Click to collapse
Maybe this helps:
fang0654 said:
To install:
1) extract and push busybox to your sdcard, reboot into recovery
2) mount /system
3) if you don't have /system/xbin (you should), create it
adb shell:
# mkdir /system/xbin (if necessary)
dd if=/sdcard/busybox of=/system/xbin/busybox
cd /system/xbin
chmod 755 busybox
./busybox --install .
4) reboot and done
OPTIONAL - before rebooting replace the busybox installed by the root process in /system/bin
1) mv /system/bin/busybox /system/bin/busybox.bak
2) cp /system/xbin/busybox /system/bin/busybox
Click to expand...
Click to collapse
from this site: http://forum.xda-developers.com/showthread.php?t=702634
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
matpol said:
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
Click to expand...
Click to collapse
You dont have to extract the binary into a folder, just extract the busybox file direct on your sdcard. Than the dd command should work, on my phone it works fine.
But if not, does the command cat in the adb shell work?
If so, try istead of the dd comand:
Code:
mount /sdcard
cat /sdcard/busybox > /system/xbin/busybox
And remember to start your wildfire in the recovery mode, that was the mistake I had done...
This howto is for those people who are unable to root their Galaxy Tab using any of the automated procedures and do not suffer from CLPS (command-line-phobia-syndrome).
My story: After upgrading my EURO (GSM) Galaxy Tab to JM6 my persistent efforts to root the device using either the z4root or SuperOnClick methods have all been unsuccessful. z4root (v1.3.0) kept crashing at different stages, apparently depending on which and how many background apps were running. With SuperOneClick I never managed to get beyond the "changing permissions" stage.
Since both methods are basically wrappers of the rageagainstthecage application, I tried to perform the rooting procedure manually. Guess what, that worked without any problem and it is pretty easy to do.
The basic steps of the rooting process are:
1) use rageagainstthecage to get a temporary root shell
2) use the temporary root shell to copy three files to the read-only system partition the device
While I find the outlined procedure straightforward, you may not. Anyhow, try this at your own risk.
==== Prerequisites ====
I used Ubuntu 10.10 for this, but it should work on any other distro and on Windows just as well. Whatever OS you use, you need a working adb connection to your Galaxy Tab. Odin or Kies are of no use here.
You need the following binaries
* su
* busybox
* Superuser.apk
* rageagainstthecage
To get the all required files, simply download "SuperOneClickv1.5.5-ShortFuse.zip". That's what I used.
Get it here: http://forum.xda-developers.com/showthread.php?t=803682
Extract the contents of the ZIP, open a command-prompt on your computer and change to the directory where the extracted files are located.
Some advice if shell commands are not your regular cup of tea.
The following instructions show the shell commands. Some are executed on the host computer. Others are executed on the Galaxy Tab. You can differentiate between the two easily: All commands which start with "> " need to be executed in a shell on the host computer. Commands which are prefixed with "$ " are executed on the Galaxy Tab. In both case the ">" and the "$" must not be typed. If you copy+paste from this howto, make sure only to copy the commands and leave out the prompt.
==== Step 1: getting a temporary root shell ====
Copy the rageagainstthecage exploit to a temporary directory.
Code:
> adb push rageagainstthecage /data/local/tmp
263 KB/s (5392 bytes in 0.020s)
Change the file permissions and execute the exploit.
Code:
> adb shell
$ cd /data/local/tmp
$ chmod 777 rageagainstthecage
$ ./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
(other output truncated)
Your shell session will be terminated which will throw you back to the regular command prompt of your host computer.
==== Step 2: restart adb server ====
Now stop and restart the adb server process.
Code:
> adb kill-server
> adb start-server
* daemon not running. starting it now *
* daemon started successfully *
Now reconnect to the Galaxy Tab again. Notice the '#' prompt. This means you have a temporary root shell now. We use this to execute some privileged commands which make the rooting permanent.
==== Step 3: making it permanent ====
First, make the system partition writeable. We need this to be able to copy su, busybox and Superuser.apk to the required locations. Then exit the android shell again.
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
The final steps are to change the file permissions for su and busybox and then remount the system partition as read-only again.
Code:
> adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
# exit
That should be all. Try a reboot and some apps which require root, like Titanium Backup. The Superuser.apk should popup a dialog requesting permission.
Hope this helps. Happy rooting.
[update]
This process worked for JMA and JMD as well.
"adb install" Superuser.apk instead of "adb push"
[/update]
It will help me !
Merci ;-)
Fantastic! This is just what I was looking for, thank you! I feel dumb now, because I started a thread of my own right as you posted this. You must just type faster than me
I ran a quick test, and it all looks good. One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Anyway, thanks again, this did exactly what I needed it to. Well done, I appreciate it.
DavidThompson256 said:
One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Click to expand...
Click to collapse
Thanks for pointing that out! Actually both the filesystem type and blockdevice name were totally wrong. Apparently the mount command ignores both parameters - at least when they are wrong.
I just verified this as self-punishment for not paying attention:
Code:
# mount
(...)
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
/system is mounted read-only to /dev/block/stl9. This is the normal state of things.
Now I remount this without the fstype parameter and using a wrong blockdevice name:
Code:
# mount -o remount,rw /dev/block/xyz /system
# mount
(...)
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
Surprise, this actually remounts /system in read-write mode. This is why my original howto worked despite using the wrong parameters.
Thanks again. I corrected the HOWTO.
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
leonreijnders said:
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
Click to expand...
Click to collapse
That is strange. The result of the rooting process is just adding three files to the system partition. I find it hard to believe that this could lead to the problem you describe. However, while experimenting with z4root I had the the effect that there were many rageagainstthecage processes running in the background and the Galaxy Tab slowed down considerably. Perhaps there is something similar going on.
Have you tried rebooting after completing the rooting process?
Try shutting down the Tab completely.After rebooting get a shell on the Tab with "adb shell" and execute "ps". That shows the process list. If that looks normal, I would try a factory reset of the device. Which ROM version are you running?
BlackLevel: Thank you soooooooooo much... I don't get how to hit the Thanks Meter thing, but here is the old fashioned way. I used a MacBook to accomplish your perfect, step by step rooting of an AT&T Galaxy Tab i987. It helps that I'm more comfortable at the command line than with most GUI systems.
I could put this into a bash script, but that could be dangerous. People really need to look at whats happening with 'adb' and have some idea of what adb is for. I did renamed your 'adbmac' to 'adb', then I could cut and paste from your instructions except for adding ./ before the adb... ie. ./adb shell
Again, wonderful work at pulling this all together in one place.
Jeff
This guide worked perfectly! I love a nice quiet clean root and it doesn't get any better than this. You my friend deserve a cookie!
Hi Guys,
I flashed to JMA, rooted it with One Click Root, and everxthing seemdet to be okay, but activating OCLF failed....is there anybody with the same problem?
Jan
Thanks a lot !. It's clean and doesn't need a kies ...
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
And thanks again ...
Mike
mbaroukh said:
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
Click to expand...
Click to collapse
The reason is that "/sbin/adbd" (the adb daemon) is running as the shell user. It would need to run as root user instead. This requires changes to the initial ram disk where adbd the relevant settings are stored.
Dealing with "insufficient permissions for device"
Thanks, this worked for me.
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
gklyne said:
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
Click to expand...
Click to collapse
Thanks for the feedback. On my Ubuntu 10.10 adb runs under my regular user-id (1000) and I do not have to use sudo or run the local adb server as root. That might be due to the way the udev rules are set up. Mine are rather unrestrictive and look like this:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
How do yours look like?
Which is the more simple method for root of galaxy tab euro ?are there ?
the incredible said:
Which is the more simple method for root of galaxy tab euro ?are there ?
Click to expand...
Click to collapse
Try z4root or SuperOneClick. Both methods are wrappers of the rageagainstthecage exploit and try to automate the manual process outlined here.
This thread should be a sticky. Worked like a charm.
z4root is very simple method..thanks.
thanks to Germany...
I agree, this thread should be sticky. Finaly some sense in android devel section...
Thank you very much for your guide!
I followed all the instructions in your guide, everything seems fine until I try to push the busybox and su to my Galaxy Tab.
blacklevel said:
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
[/update]
Click to expand...
Click to collapse
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too
(No space left on device) is impossible, my tab is brand new sealed when i got it.
I have been trying the z4root and SuperOneClick procedure to root this tab but are all unsuccessful.
I am not sure if it is because of my tab needed a "NAND unlock" (I cannot find any guide about the NAND unlock) because I received this message when I tried to install busybox from the market.
Please help! My tab is carrier locked to Bell Canada, I really wanna to unlock it and root it~
Thanks!
gummo6869 said:
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too,
Click to expand...
Click to collapse
The `no space left on device` message indicates that the /system partition is still read-only. That means the mount command in step 3 was unsuccessful. Did you get any error message when you executed it?
I have rooted HTC Desire and i tried to remove system app in many ways but nothing worked. Pls give any advice how can i done this.
First i tried with Root Explorer, i mounted R/W mode i deleted the app, the app is deleted from /system/app but present in menu and when i restart the phone it comes back in /system/app
Second i tried with Terminal Emulator: "#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" "#rm /system/app/appname.apk and i got the same result again :\
Third i tried with Titanium Backup Pro, when i Uninstall the app i got the same result but when i try to freeze it that's the only way i can remove from the menu :\
Thanks
Root Explorer only works if you're S-OFF
Easiest way, download the Android SDK and use adb in Recovery to remove them
Remove the apps from the ROM before flashing it?
Be carefull as removing certain apps can make the ROM unstable.
Sounds like the OP has only rooted and isn't using a custom ROM, hence my suggestion
Otherwise, yes, download a custom ROM and remove what you don't want prior to flashing
EddyOS said:
Sounds like the OP has only rooted and isn't using a custom ROM, hence my suggestion
Otherwise, yes, download a custom ROM and remove what you don't want prior to flashing
Click to expand...
Click to collapse
I've recently come across two very interesting Windows apps which make the process easy.. Android Commander and QtADB...Both are GUI frontends for ADB, so once rooted, removing it should be easy in these. However, I believe that some may be removable only in Recovery mode, unless you have S-OFF
My devise is rooted and i use custom rom, Oxygen 2 atm but its not S-OFF, how can i S-OFF? I used unrEVOked to root my phone.
Thanks
v.pakard said:
My devise is rooted and i use custom rom, Oxygen 2 atm but its not S-OFF, how can i S-OFF? I used unrEVOked to root my phone.
Thanks
Click to expand...
Click to collapse
With Alpharev
Second i tried with Terminal Emulator: "#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" "#rm /system/app/appname.apk and i got the same result again :\
Click to expand...
Click to collapse
Did you boot to clockwork recovery first? You must and then run
adb shell
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
rm anythingyouwant.apk
rm anythingyouwant.odex
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
reboot with trackball
This is how I do it in linux. You can boot with live distro linux, connect your desire and start console. I think it should work. I do it from virtualbox.
Thanks alot, S-OFF was the problem, my phone was rooted but not S-OFF. Now everything is fine.
Thanks,
pakard
I just upgraded my GNex GSM yesterday.
It's now smoother than ever before...
But one thing is I wanna get root access on my GNex
GSM 4.0.4 IMM76D.
Is there any CF-Root or something available now...?
here it comes in 3...2....1........
.4 is unrootable. Would've known if you searched.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
zeyarwynntun said:
I just upgraded my GNex GSM yesterday.
It's now smoother than ever before...
But one thing is I wanna get root access on my GNex
GSM 4.0.4 IMM76D.
Is there any CF-Root or something available now...?
Click to expand...
Click to collapse
This question sounds more like: I just lost my glassess and I don't know how to read!
http://forum.xda-developers.com/showthread.php?t=1382163
Try a search, You might find one of the 20ish threads that have an answer in it on how to root your Gnex.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
@rbiter said:
.4 is unrootable. Would've known if you searched.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
10/char
Galaxy Nexus Toolkit v5.6
Oh, yes, I've lost my glasses...
I just have my GNex rooted with Galaxy Nexus Toolkit v5.6
zeyarwynntun said:
Oh, yes, I've lost my glasses...
I just have my GNex rooted with Galaxy Nexus Toolkit v5.6
Click to expand...
Click to collapse
Is it possible to root without using cwm?
I'm not interested in flashing non stock images.
sblantipodi said:
Is it possible to root without using cwm?
I'm not interested in flashing non stock images.
Click to expand...
Click to collapse
No, it is not possible to root IMM76D without using CWM.
That said, you DO NOT have to flash CWM to be able to use it...
EDIT: j.go (who posted below me) is right. You can root by booting an insecure kernel (which by the way is what CWM is), and copying the two files over using ADB (which is essentially what CWM does, but much easier).
efrant said:
No, it is not possible to root IMM76D without using CWM.
That said, you DO NOT have to flash CWM to be able to use it...
Click to expand...
Click to collapse
You can root without CWM. Fastboot boot with unsecure boot image. Adb push su and superuser.apk. Reboot. Congratulations, you are rooted.
j.go said:
You can root without CWM. Fastboot boot with unsecure boot image. Adb push su and superuser.apk. Reboot. Congratulations, you are rooted.
Click to expand...
Click to collapse
I don't understood, can you make a step by step guide please?
I want to root my phone leaving as much as stock items as possible.
How to root ANY build, on a GN with an unlocked bootloader
Note: There is currently no way to root IMM76D (i.e., 4.0.4) without an unlocked bootloader. The following method is for devices with unlocked bootloaders.
Method 1
1) Download CWM from here to your computer: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img.
2) Download the attachments from here to your computer: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Download this to your /sdcard on your device: http://www.box.com/s/jvcf196j7x8f8vrc9cyt
4) Extract all the files into one directory, and put cwm.img in there
5) Restart your device in fastboot mode and plug into computer
6) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
7) Wait for it to boot
8) Navigate the menus. There is an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
9) Reboot. Done.
Method 2 (more manual)
1) Download CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img If you are having problems, download the attachment from here and use it instead of CWM.
2) Download the attachments from here: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Extract all the files into one directory, and put cwm.img in there
4) Restart your device in fastboot mode and plug into computer
5) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
6) Wait for it to boot
7) In the command prompt, type the following:
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
8) Done.
Note: if you are having problems mounting /system in CWM, try doing it in CWM itself (on device via the menu), instead of typing in the command.
EDIT: Added title and note.
efrant said:
1) Download CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img
2) Download the attachments from here: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Extract all the files into one directory, and put cwm.img in there
4) Restart your device in fastboot mode and plug into computer
5) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
6) Wait for it to boot
7) In the command prompt, type the following:
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
8) Done.
Click to expand...
Click to collapse
this will give me the root access on a stock 4.0.4 phone?
in the thread at point 2) is wrote that this does not work on 4.0.4.
sblantipodi said:
this will give me the root access on a stock 4.0.4 phone?
Click to expand...
Click to collapse
Yes.
sblantipodi said:
in the thread at point 2) is wrote that this does not work on 4.0.4.
Click to expand...
Click to collapse
That is why you are not following the directions in that thread. You are following the directions in this thread, right?
efrant said:
Yes.
That is why you are not following the directions in that thread. You are following the directions in this thread, right?
Click to expand...
Click to collapse
lol... great
do you think that this way of rooting will create problem in future OTA notifications?
sblantipodi said:
lol... great
do you think that this way of rooting will create problem in future OTA notifications?
Click to expand...
Click to collapse
No, it will not. Rooting by ANY method does not affect OTAs...
P.S. There is a slightly easier method that I will add to the previous post soon. (I wanted to put in the fully manual method so you can see what is happening.)
Another question, I am an app developer so adb and fastboot are in my default path from the original SDK.
Can I use my ADB and FastBoot from my SDK?
sblantipodi said:
Another question, I am an app developer so adb and fastboot are in my default path from the original SDK.
Can I use my ADB and FastBoot from my SDK?
Click to expand...
Click to collapse
Yes.
10 char
Hey efrant, if I wanted to remove the Superuser.apk and su files already on the device, could I follow Method 2 and fastboot boot cwm.img then do the following in step 7:
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
rm /system/bin/su
rm /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
Then once done, disconnect usb cable and reboot the device?
This would essentially leave me with stock recovery, locked bootloader and no root - correct?
ruffneckc said:
Hey efrant, if I wanted to remove the Superuser.apk and su files already on the device, could I follow Method 2 and fastboot boot cwm.img then do the following in step 7:
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
rm /system/bin/su
rm /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
Then once done, disconnect usb cable and reboot the device?
This would essentially leave me with stock recovery, locked bootloader and no root - correct?
Click to expand...
Click to collapse
Is your bootloader locked or unlocked currently? You cannot use fastboot commands if your bootloader is locked.
Assuming that your bootloader is unlocked, your procedure is correct, although you would have to relock you bootloader afterwards by booting into fastboot mode, and typing: fastboot oem lock
However, re-locking is something that I never recommend to anyone.
efrant said:
Is your bootloader locked or unlocked currently? You cannot use fastboot commands if your bootloader is locked.
Assuming that your bootloader is unlocked, your procedure is correct, although you would have to relock you bootloader afterwards by booting into fastboot mode, and typing: fastboot oem lock
However, re-locking is something that I never recommend to anyone.
Click to expand...
Click to collapse
My bootloader is currently locked. Regarding re-locking it, I'm just curious as to why you don't recommend it? Essentially, I want keep the option of getting OTAs and get rid of the "Unsupported Device" message in Google Wallet. I read that the app checks for root by looking for the two files and whether the device release keys are modified.
I really appreciate your help.
i have made a CWM flashable su.
if anyone wants. instead of going through all the mount, and copy process,
you will just need to flash the su from the zip file,
go to play store and install the Superuser.apk and then from that update su to the latest version.
if interested, let me know.
Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.
You can root using this toolkit http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Mojochief said:
Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.
Click to expand...
Click to collapse
Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
EDIT: All that file does, is copy su and Superuser.apk to your device and set the appropriate permissions.
You can root using this toolkit http://forum.xda-developers.com/show....php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Thanks I'll try it, but I'm actually not a big fan of one click thingies where you don't know what you're doing.
Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
Click to expand...
Click to collapse
Thank you I really prefer that over toolkits!
Mojochief said:
Thank you I really prefer that over toolkits!
Click to expand...
Click to collapse
This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.
This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.
Click to expand...
Click to collapse
Just tried it and it worked just fine
And thank you for the explanation!
So actually you could do it w/out booting cwm just with fastboot+adb right?
Mojochief said:
[snip]
So actually you could do it w/out booting cwm just with fastboot+adb right?
Click to expand...
Click to collapse
No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.
No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.
Click to expand...
Click to collapse
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.
Mojochief said:
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.
Click to expand...
Click to collapse
Yes, you can use another insecure boot image, but it needs to be a 4.0.4 compatible kernel. Older ones won't work.
Sent from my Galaxy Nexus using Tapatalk