adb devices
adb push asroot2 /data/local
adb shell chmood 0755 /data/local/asroot2
adb shell
$ /data/local/asroot /system/bin/sh
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system (or is it -zero)
$ cd /system/bin
$cat sh > su
$ chmod 4775 su (or 4755?)
$exit
adb push recovery-RA-heroc-v1.2.3.img
adb shell
$ su
# flash_image recovery recovery-RA-heroc-v1.2.3.img
then boot to recovery by typing: reboot recovery while pressing volume down and the when it boots to screen press home?
is this how to do it? help please
Code:
adb devices
adb push asroot2 /data/local
adb push recovery-RA-heroc-v1.2.3.img /data/local
adb shell
Code:
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system
cd /system/bin
cat sh > su
chmod 4755 su
flash_image recovery /data/local/recovery-RA-heroc-v1.2.3.img
reboot recovery
corrected some stuff for ya make sure asroot2 and recovery-RA-heroc-v1.2.3.img is in same directory as adb.exe
and that's good to go
UPDATE: no longer requires a sd card to root + recovery image + made copy/pasteable
fullgrown said:
adb devices
adb push asroot2 /data/local
adb shell chmood 0755 /data/local/asroot2
adb shell
$ /data/local/asroot /system/bin/sh
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock /system (or is it -zero)
$ cd /system/bin
$cat sh > su
$ chmod 4775 su (or 4755?)
$exit
adb push recovery-RA-heroc-v1.2.3.img
adb shell
$ su
# flash_image recovery recovery-RA-heroc-v1.2.3.img
then boot to recovery by typing: reboot recovery while pressing volume down and the when it boots to screen press home?
is this how to do it? help please
Click to expand...
Click to collapse
Up to the exit is the rooting part, yes. After that you can shell in and type "su" and have root access.
The rest of it is installing a custom recovery image.
thank you!!! now i'm rooted!!!
I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now, and now I'm here. What am I doing wrong? Thanks
there
Code:
mount -o remount,rw /dev/mmcblk0p12 /system
back
Code:
mount -o remount,ro /dev/mmcblk0p12 /system
Hmm, well at least I didn't get any errors this time.
I didn't get a confirmation or that it did anything at all. Is that normal?
Run mount with no parameters and look for the line with that device name, should see rw in that line instead of ro.
Sent from my MB860 using XDA App
Thanks guys, but I resorted to busybox chmod command instead lol
I tried this and got no errors, and using cat /proc/mounts/ I see the path as rw. But when I try to copy I still get the read only file system error.
**Lol, I had the phone in usb storage mode and had to switch it to Windows Media Sync**
Hi there!
I upgraded my wife's tattoo's recovery to 3.0.0.6 using ROM Manager, unaware that I will not be able to flash ROMs anymore (amend / edify scripting differences)
Now I cannot find a way to revert to original/older recovery, did try a lot of stuff around here and still no luck
Cannot flash using RUU as i receive a "Wrong bootloader error"
Any help would be appreciated.
Thanx in advance.
Adrian
________________________________________________
LE: After trying for some weeks now, I decided to post this message - few minutes after, I solved the problem - like this:
Code:
C:\>adb push c:\flash_image /sdcard/
365 KB/s (26172 bytes in 0.070s)
C:\>adb push c:\rtattoo\recovery.img /sdcard/
905 KB/s (3731456 bytes in 4.025s)
C:\>adb shell
# su
su
# mount -o remount, rw /system
mount -o remount, rw /system
# cp /sdcard/flash_image /system/bin
cp /sdcard/flash_image /system/bin
# cd /system/bin
cd /system/bin
# chmod 777 flash_image
chmod 777 flash_image
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
Thanx - OP please close.
why so much on typing CMD adb
use android commmander It is Great
You can try to use this script http://forum.xda-developers.com/showthread.php?t=644279 but replace the recovery file with the original recovery file . don't forget to rename it to the same name.
So I have root on the Tattoo following the guide here: http://forum.xda-developers.com/showthread.php?t=716282
Code:
C:\Tattoo>adb shell
# id
id
uid=0(root) gid=0(root)
and I have flashed the boot.img ok I think.
but when I flash the recovery.img I get the following:
Code:
# insmod ./tattoo-hack.ko
insmod ./tattoo-hack.ko
# mount -o rw,remount /dev/block/mtdblock5 /data
mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
mount -o rw,remount /dev/block/mtdblock3 /system
# ./flash_image recovery /sdcard/recovery.Tattoo.alpha2b.Mvx.img
./flash_image recovery /sdcard/recovery.Tattoo.alpha2b.Mvx.img
flashing recovery from /sdcard/recovery.Tattoo.alpha2b.Mvx.img
mtd: erase failure at 0x00040000 (Input/output error)
mtd: erase failure at 0x00040000 (Input/output error)
mtd: skipping write block at 0x00040000
#
I have tried about 3 diffrent recovery.img files and after this output reboot and try recovery and I just get the "TATTOO" boot screen forever untill I pull the battery then I can boot back to the OS but I never get recovery. I also tried using adb to boot to recovery and get the same results.
Any idea what I can try?
this is driving me nuts.
Thanks!
And from ROM manager?
lemmymet said:
And from ROM manager?
Click to expand...
Click to collapse
The phone has the stock rom on it, trying to do the initial root/flash so I don't have rom manager yet. I also havent been able to find the .apk of rom manager that will work from the stock rom.
Thats right Folks, I am sitting here holding a ROOTED Acer A200 In my hands...
This was done on ICS 4.0.3 Leaked.
However This SHOULD work for the OTA update.
I hate to have to say this. but........
YOU ARE TAKING RESPONSIBILITY FOR DOING THIS, AND YOU ALONE ASSUME ALL RISKS. THIS HAS WORKED FOR ME BUT I ASSUME NO RESPONSIBILITY IF YOU BRICK YOUR TABLET!
Credit goes to saurik (hxxps://github.com/saurik/mempodroid) for the root method, Jason A. Donenfeld (zx2c4) (Linux Local Privilege Escalation via SUID /proc/pid/mem Write | Nerdling Sapple) for finding the exploit
and to Rkeene (Rooting the Toshiba Thrive) for Getting around the /system mount as RW issue.
First,
( You are going to need to have the android sdk installed, so you have ADB, There are plenty of docs on doing this )
then go here
hxxps://github.com/saurik/mempodroid...ster/README.md
get the precompiled binary, (mempodroid )
then
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
Once you have this completed.
goto Rkeenes Site.
hxxp://rkeene.org/projects/info/wiki/210
skip down to step 16.
Follow the instructions there.. Mind you there is a specific offset that you must use for your acer. ( It is listed on his page now )
but this WILL work.
I have done it..
Please please please. Give MASSIVE Credit where Credit is due on this, Saurik, Jason A. Donenfeld (zx2c4), and RKeene.
In Our case here, RKeene took the time to work with me to get the offsets for the Acer, so we can get the /system folder mounted RW. ( I would say an hour or two )
-Hex
Have anyone confirmed this working?
Quick Question
Does the root process being taken require access to a linux machine or can it be done from windows. Most of the commands look like they take place in adb shell but some of the adb push commands look like they are run from a linux command line. I know sounds stupid but not sure and dont want to brick device. The reson I ask is because I run mempodroid and run mkdir command. gets
"[email protected]:/ $ /data/local/mempodroid 0xd9f0 0xad4b -o remount,re "/system
/data/local/mempodroid 0xd9f0 0xad4b -o remount,re "/system
> /data/local/mempodroid 0xd9f0 0xaf47 sh
/data/local/mempodroid 0xd9f0 0xaf47 sh
> mkdir /data/x-root
mkdir /data/x-root
> mkdir /data/x-root/bin
mkdir /data/x-root/bin
> ^C
C:\Program Files\Android\android-sdk\platform-tools>adb push busybox /data/x-root/bin/busybox
failed to copy 'busybox' to '/data/x-root/bin/busybox': No such file or directory"
What am i missing?
Update
Now it shows this
"[email protected]:/ $ chmod 777 data/local/mempodroid
chmod 777 data/local/mempodroid
[email protected]:/ $ /data/local/mempodroid 0xd9f0 0xaf47 mount -o remount,rw /system
0xaf47 mount -o remount,rw /system <
mount: Operation not permitted"
This is killing me!?
I get to here
mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
and it tells me
mount: invalid argument
what the?
---------- Post added at 12:47 PM ---------- Previous post was at 11:55 AM ----------
Ok, this was a pain in the arse!
I hope I can remember the steps I took in order to get this done.
By the way, I'm using windows
adb push mempodroid /data/local
adb push su /data/local
adb shell
$ chmod 777 /data/local/mempodroid
Click to expand...
Click to collapse
Then I went to here as directed,
http://rkeene.org/projects/info/wiki/210
but didn't follow the steps as they were shown because I got stuck many times and had to start over.
So here are my steps.
1.
$ /data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
which then should turn the $ into a #
2.
# mkdir /data/x-root /data/x-root/bin
Click to expand...
Click to collapse
3. Download this,
http://www.rkeene.org/projects/info/resources/diatribes/root-toshiba-thrive/busybox
and then move the file to where you have mempodroid and su so you can adb push them easier
4.
adb push busybox /data/x-root/bin/busybox
adb push su /data/x-root/bin/su
adb shell
Click to expand...
Click to collapse
5. This is where it got tricky. If you don't pay close attention, you will most likely do what I did and put files where they aren't supposed to go. So please, PAY ATTENTION!
If you still have the # in the shell, move forward. Otherwise,
/data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
and then move forward once # is confirmed.
# cd /data/x-root/bin
# chmod 755 busybox
# ./busybox bash
Click to expand...
Click to collapse
Now, there is no doubting it, you will get the "bash: precmd: not found" error.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
# PATH="${PATH}:/data/x-root/bin"; export PATH
Click to expand...
Click to collapse
6. AGAIN, PAY CLOSE ATTENTION HERE!!
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
Click to expand...
Click to collapse
7. This is where I ran into another problem, so pay attention.
# cd /
# mkdir /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
You will see nothing as the steps describe. This is because we skipped a step. Why? Because mount -o ro -t ext4 /dev/loop0 /dev/tmpdir for some strange reason wouldn't unmount so I could mount the next step. So instead, we move on and then check again.
Here is the removed step
# mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
# umount /dev/tmpdir
Click to expand...
Click to collapse
You can try this but I advise not to or you could very well run into the same issue I had where you can't unmount in order to move on with the root process
# mount -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
And now you will see /system mounted.
8.
# cp /data/x-root/bin/su /dev/tmpdir/bin/
# chmod 4555 /dev/tmpdir/bin/su
# umount /dev/tmpdir
# losetup -d /dev/loop0
# sync
# reboot
Click to expand...
Click to collapse
9. Now once your A200 reboot and displays the home screen, we will confirm.
adb shell
[email protected]:/ $ su
Click to expand...
Click to collapse
If the $ doesn't turn into a #, you did something wrong...
Thank you hexmare, for opening this thread and giving the guidance.
Thank you d10369319, for "/data/local/mempodroid 0xd9f0 0xaf47 sh", I would have never figured this out.
Thank you RKeene, for writing out the guide to Root the Toshiba Thrive
And Thank you Saurik along with zx2c4, for mempodroid
By the way, I'm posting this in the Dev section...
been away
Thanks for clearing up the questions. I have been gone the past couple hours. Also thanks for reposting this in the dev section as well, I would have but I don't have enough posts on here to post under that section yet.
-Hex
So i'm stucks again
where did i go wrong?
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found
Anytime, buddy. I figured if I was having problems rooting, others would have problems as well so I wanted to make it as simple as possible...
---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------
d10369319 said:
where did i go wrong?
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found
Click to expand...
Click to collapse
I think you might have missed these steps.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
Click to expand...
Click to collapse
Something that I want to point out as well. Especially those that are trying this root on a200's that have the OTA update.
Please for the love of all that is holy, MOUNT AS READ ONLY FIRST. You need to make sure that you have the correct offset for the system area that you mount.
If you have the wrong offset, mount as RW, and write to it, you can REALLY hose up your tablet and possibly brick it.
mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
ls -l /dev/tmpdir
ls -l /system
** COMPARE THEM if they pass then continue.**
umount /dev/tmpdir
mount -t ext4 /dev/loop0 /dev/tmpdir
sorry for the several caps spots. But this is really important. I don't want Shiny bricks being formed.
-Hex
Tryed agin get this
philosophics said:
Anytime, buddy. I figured if I was having problems rooting, others would have problems as well so I wanted to make it as simple as possible...
---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------
I think you might have missed these steps.
Click to expand...
Click to collapse
I tried it again and still got same error. When i run it i get
[email protected]:/data/x-root/bin # unset PS1 PROMPT_COMMAND
unset PS1 PROMPT_COMMAND
[email protected]/busybox bash
./busybox bash
/data/x-root/bin # for tool in $(./busybox --list); do ln -s busybox $tool; done
for tool in $(./busybox --list); do ln -s busybox $tool; done
link failed File exists
link failed File exists<====This shows up a bunch
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found
---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------
Are you running the OTA update or the dev leak ICS?
d10369319 said:
for tool in $(./busybox --list); do ln -s busybox $tool; done
link failed File exists
link failed File exists<====This shows up a bunch
Click to expand...
Click to collapse
This is because you've already completed this step so it's already there.
---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------
Are you running the OTA update or the dev leak ICS?
Click to expand...
Click to collapse
I am running the OTA
And by the way, I think I know what's wrong. I put one step in the wrong place.
Before you cd / try this
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
then try cd / and continue.
If that's what went wrong, I will revise the guide
---------- Post added at 04:25 PM ---------- Previous post was at 04:22 PM ----------
hexmare said:
Something that I want to point out as well. Especially those that are trying this root on a200's that have the OTA update.
Please for the love of all that is holy, MOUNT AS READ ONLY FIRST. You need to make sure that you have the correct offset for the system area that you mount.
If you have the wrong offset, mount as RW, and write to it, you can REALLY hose up your tablet and possibly brick it.
mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
ls -l /dev/tmpdir
ls -l /system
** COMPARE THEM if they pass then continue.**
umount /dev/tmpdir
mount -t ext4 /dev/loop0 /dev/tmpdir
sorry for the several caps spots. But this is really important. I don't want Shiny bricks being formed.
-Hex
Click to expand...
Click to collapse
Yes, but this is where I got stuck. When I tried to run the umount command for this, it basically told me no. This is why I intentionally left that particular step out...
Well since you are running OTA, ( Which was my main concern ) and you didn't brick it I guess we are in good shape for the offsets. Since mine is the leaked version, I didn't want people on OTA to try and arf up.
so Thumbs up to you.
now since you have the OTA and root. Would you mind pulling a System Dump, including Boot and recovery images so those of us on leak can move back to official??
-Hex
I ran it from the point were i got
"link failed File exists
link failed File exists
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found"
Still same problem
---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
Started completely over from sctratch 4 times and still get stuck in the same exact spot. Completely insane.
hexmare said:
now since you have the OTA and root. Would you mind pulling a System Dump, including Boot and recovery images so those of us on leak can move back to official??
-Hex
Click to expand...
Click to collapse
I would be glad to do so, but have never done it before. Mind throwin me the steps for that?
---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------
d10369319 said:
I ran it from the point were i got
"link failed File exists
link failed File exists
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found"
Still same problem
---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
Started completely over from sctratch 4 times and still get stuck in the same exact spot. Completely insane.
Click to expand...
Click to collapse
I just updated the guide. Misplaced some steps. Try it again with the revised steps.
Are there any specific device settings that your running other than usb debuging on your device, and what version of windows are you using cause im thinking maybe device drivers may be an issue.
I'm running windows 7
If you are able to use adb with the A200, then drivers would not be an issue.
GOT ROOT!!!!!!!!!!!!
Found the error
"/data/x-root/bin # PATH="${PATH}:/data/x-root/bin"; export PATH
PATH="${PATH}:/data/x-root/bin"; export PATH
/data/x-root/bin # mknod
mknod
BusyBox v1.19.3-Stericson (2011-11-01 20:22:18 CDT) multi-call binary.
Usage: mknod [-m MODE] NAME TYPE MAJOR MINOR
Create a special file (block, character, or pipe)
-m MODE Creation mode (default a=rw)
TYPE:
b Block device
c or u Character device
p Named pipe (MAJOR and MINOR are ignored)
/data/x-root/bin # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
/data/x-root/bin # losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
/data/x-root/bin # cd /
cd /
/ # mkdir /dev/tmpdir
mkdir /dev/tmpdir
/ # ls -l /dev/tmpdir
ls -l /dev/tmpdir
/ # mount -t ext4 /dev/loop0 /dev/tmpdir
mount -t ext4 /dev/loop0 /dev/tmpdir
/ # ls -l /dev/tmpdir
ls -l /dev/tmpdir
drwxr-xr-x root root 2012-02-16 16:27 app
drwxr-xr-x root shell 2012-02-16 16:27 bin
-rw-r--r-- root root 1939 2008-08-01 08:00 build.prop
drwxr-xr-x root root 2012-02-16 16:27 etc
drwxr-xr-x root root 2012-02-16 16:27 fonts
drwxr-xr-x root root 2012-02-16 16:27 framework
drwxr-xr-x root root 2012-02-16 16:27 lib
drwxr-xr-x root root 1969-12-31 19:00 lost+found
drwxr-xr-x root root 2012-02-16 16:27 media
-rw-r--r-- root root 595088 2008-08-01 08:00 recovery-from-boot.p
drwxr-xr-x root root 2012-02-16 16:27 tts
drwxr-xr-x root root 2012-02-16 16:27 usr
drwxr-xr-x root shell 2012-02-16 16:27 vendor
drwxr-xr-x root shell 2012-02-16 16:27 xbin
/ # cp /data/x-root/bin/su /dev/tmpdir/bin/
cp /data/x-root/bin/su /dev/tmpdir/bin/
/ # chmod 4555 /dev/tmpdir/bin/su
chmod 4555 /dev/tmpdir/bin/su
/ # unmount /dev/tmpdir
unmount /dev/tmpdir
bash: unmount: not found
/ # umount /dev/tmpdir
umount /dev/tmpdir
/ # losetup -d /dev/loop0
losetup -d /dev/loop0
losetup: /dev/loop0: No such device or address
/ # losetup -d /devo/loop0
losetup -d /devo/loop0
losetup: /devo/loop0: No such file or directory
/ # sync
sync
/ # reboot
reboot
reboot returned
/ #
C:\Program Files\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ #"
run #PATH="${PATH}:/data/x-root/bin"; export PATH
Thats were the error occured and was causing a problem.
Thanx to saurik (hxxps://github.com/saurik/mempodroid) for the root method, Jason A. Donenfeld (zx2c4) (Linux Local Privilege Escalation via SUID /proc/pid/mem Write | Nerdling Sapple) for finding the exploit
And a big thanks to philosophics for helping me out.
---------- Post added at 01:17 AM ---------- Previous post was at 01:15 AM ----------
philosophics said:
I'm running windows 7
If you are able to use adb with the A200, then drivers would not be an issue.
Click to expand...
Click to collapse
Turns out it was a typo in the direction's, only needs one # for the path command and thats whats was causing the error. Ty so much for your help philosophics.
You are most welcome. I remember what the original android days were like. Kind of a pain to get anything done...
Grats on the root!!!
Before I dive in head first, will my iconia be wiped while performing this root?? Just want to back up if need be.
And it's confirmed working on the OTA??
No, your device will not be wiped...
Yes, I performed this on the OTA