Hello!
I am use this Tutorial to rooting my Hero: http://forum.xda-developers.com/showthread.php?t=543571
How i can unrooting my Hero? I think, its possible, because the boot.img dont replaced with a other rom...
I found this Command *thanks!*:
* adb shell mount /system
* adb shell rm /system/app/Superuser.apk (if you have it)
* adb push su /system/bin/
* reboot
Click to expand...
Click to collapse
.. the problem is, i havent the original su
Can someone upload the original su?
Do I need to change the rights?
*from Tutorial*
adb shell chmod 4755 /system/bin/su
Click to expand...
Click to collapse
Big Thanks! Nice Community!
*sorry, my english is very bad >.< xD*
My advice would be, keep reading. Page 5 or 6 IIRR has Dayzee's guide which is what I used to root mine, but IIRR she tells you how to unroot again
If you did a Nandroid backup first you could just restore from that?
@ak1ra1nblack: I dont found..
@badgaz: I haven't a backup...
I need the original su file and the original rights for
adb shell chmod 4755 /system/bin/su
Thanks!
Ok, Close please ~~
tur0kx said:
Ok, Close please ~~
Click to expand...
Click to collapse
did you manage to unroot it! IF so share with us the complete steps and link to original su file!
If someone can provide us with an original SU file or a changed back one (Maybe enlightener can help?) then I'll add it in the guide - I don't have it in there yet, though there is code to remove superuser.apk and repush it if it goes wrong which might be what the other poster was thinking about. I do think rooting state can be reversed if you did this method, so lets see if we can get an unrooted SU (or do we just have to remove su file altogether to be virgin again?)
Hugs to all - Dayzee
I just checked.
I restored my nandroid backup.
I booted the cm-recovery mounted /system.
and now in /system/bin there is no su.
I expected this already.
To unroot removing su and SuperUser.apk should be enough.
BR
phlo
Ok is there somebody that could please clarify on the specific steps to unroot the phone?
I don't like to guess at all with these kind of things for obvious reasons
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
tur0kx said:
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
Click to expand...
Click to collapse
That is nice, should be in the wiki.
How about unrooting by flashing back backed up .img files? Witch file to restore? How?
my search button stopped working, i tried reinstalling google search and flashing caulkin's search button fix (to reverse the disable) even though i never applied the disabling zip. anyone have any more fixes besides reflashing?
I'll quote myself from another thread:
drmacinyasha said:
Here's how to fix (from your Terminal/Command Prompt, where ADB is):
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell rm /system/app/GoogleQuickSearchBox.apk
adb shell rm /system/app/VoiceSearch.apk
adb shell rm -r /data/data/com.google.android.voicesearch
adb shell pm uninstall com.google.android.voicesearch
adb reboot
Now go install the Google Search and Voice Search from the Android Market. Problem solved.
NOTE: You have to have full root. That means # in your shell, and NAND unlock. If you don't, you are SOL.
Click to expand...
Click to collapse
If you're still having problems, use this:
adb shell cp /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/GoogleQuickSearchBox.apk
Works fine here
from the apple store loling
drmacinyasha said:
I'll quote myself from another thread:
If you're still having problems, use this:
adb shell cp /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/GoogleQuickSearchBox.apk
Click to expand...
Click to collapse
Can you type the code to use in terminal emulator please?! i know its slightly different...im having this same problem with the search button
Edit: fixed
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?
Hello!
The title says it all! Is it possible to make a Nandroid backup directly to PC connected via USB? If yes, how?
Thanks!
amagalma said:
Hello!
The title says it all! Is it possible to make a Nandroid backup directly to PC connected via USB? If yes, how?
Thanks!
Click to expand...
Click to collapse
ADB pull can do almost anything. Step one of this OP http://forum.xda-developers.com/showthread.php?t=2128848 will show you how to backup everything.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
ADB pull can do almost anything. Step one of this OP http://forum.xda-developers.com/showthread.php?t=2128848 will show you how to backup everything.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for your answer!
The code in step 1 is:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
What should I change in order to specify the exact path where to backup in my PC? And another question: will this create images that are exact copies in size? Which is to say, will I need 16GB of free space in my PC's hard drive? (I have the Nexus 2 16GB Wi-Fi)
Thanks!
What should I change in order to specify the exact path where to backup in my PC?
Click to expand...
Click to collapse
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\name-of-the-file-you-made-on-your-pc-here
adb pull /sdcard/stock-boot.img/ [C:\name-of-your-file-make-on-on-your-PC-first)]
adb pull /sdcard/stock-recovery.img/ [C:\name-of-your-file]
adb pull /sdcard/stock-system.img/ [C:\name-of-your-file]
And another question: will this create images that are exact copies in size?
Click to expand...
Click to collapse
Yes
Which is to say, will I need 16GB of free space in my PC's hard drive?
Click to expand...
Click to collapse
What ever memory is in use is what you will need space wise for your nandroid. Look at the storage available and minus it from 16GB. That's the space you will need.
Find the name of the image to pull it. It may be labeled just plain recover.img, boot.img and (usually is.) What ever they are, just plug that info into the code. It all works the same you just have to tell (command) the computer what to pull. Sorry about the KFHD reference. I was on my tablet and that's where most of my help is focused at.
LinearEquation said:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\name-of-the-file-you-made-on-your-pc-here
adb pull /sdcard/stock-boot.img/ [C:\name-of-your-file-make-on-on-your-PC-first)]
adb pull /sdcard/stock-recovery.img/ [C:\name-of-your-file]
adb pull /sdcard/stock-system.img/ [C:\name-of-your-file]
Yes
What ever memory is in use is what you will need space wise for your nandroid. Look at the storage available and minus it from 16GB. That's the space you will need.
Find the name of the image to pull it. It may be labeled just plain recover.img, boot.img and (usually is.) What ever they are, just plug that info into the code. It all works the same you just have to tell (command) the computer what to pull. Sorry about the KFHD reference. I was on my tablet and that's where most of my help is focused at.
Click to expand...
Click to collapse
Thank you very much for your help!
Hi my freinds
my sim1 and 2 not work
i understand this problem come by delete the nvram Partition
if anyone have rooted xperia m5 (e5633) can help me to solve this proablem run the following commands from ADB and then upload the file that will be pulled from the phone here:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/nvram of=/data/local/tmp/nvram.img"
adb shell su -c "chmod 777 /data/local/tmp/nvram.img"
adb pull /data/local/tmp/nvram.img"
Hi my freinds
my sim1 and 2 not work
i understand this problem come by delete the nvram Partition
if anyone have rooted xperia m5 (e5633) can help me to solve this proablem run the following commands from ADB and then upload the file that will be pulled from the phone here:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/nvram of=/data/local/tmp/nvram.img"
adb shell su -c "chmod 777 /data/local/tmp/nvram.img"
adb pull /data/local/tmp/nvram.img"
i couldn't find that folder
Just reflash your fw i u want the imei show up
but no prob when your imei null stats
Bennybtc said:
i couldn't find that folder
Click to expand...
Click to collapse
Hi
your device will be rooted
and copy this folder from root/data/nvram
please help me aim not find any solution for this one
farshad9500gy said:
Hi
your device will be rooted
and copy this folder from root/data/nvram
please help me aim not find any solution for this one
Click to expand...
Click to collapse
It tooks me quite a while to understand what are you saying:silly:
Anyway i'm not rooted, still in MM. Just reflash your fw or repair it via pc companion
meliacentrum said:
Just reflash your fw i u want the imei show up
but no prob when your imei null stats
Click to expand...
Click to collapse
i reflashed my phone and still imei is null
if you have rooted Xperia M5 running stock firmare (the firmware version/device variant doesn't matter, it can be from doul SIM devices too) could run the following commands from ADB and then upload the file that will be pulled from the phone here:
adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/nvram of=/data/local/tmp/nvram.img"
adb shell su -c "chmod 777 /data/local/tmp/nvram.img"
adb pull /data/local/tmp/nvram.img"
Follow this step:
http://www.androidrooting.org/how-to-recover-your-phone-when-you-have-lost-your-imei/
Or
http://www.wtfandroid.com/how-to-change-imei-number-easily-on-android-100-working/
Hope get it back