[SOLVED] Acer A200 ROOTED - Acer Iconia A500

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

Related

Is there a way to install a recovery image or root from sd card & android terminal?

Is there a way to install a recovery image or root from sd card & android terminal?
Is there a way to install a recovery image or root from sd card & android terminal?
I can't get adb on mac to recognize my phone.
yes if you are on 2.1 do the
Ok ,I figured this out when I was at work and could not use my company computer.
So we need the download.
DroidXRoot_v2.zip
After you download, use a file manager and extract on the sdcard (not in any folder on the root)
Now put the wifi widget on your home screen
Download terminal emulator from the market
Open the terminal . Now comes the fun part.!
code
type these in and hit enter after each one.
cd /sqlite_stmt_journals
cp /sdcard/exploid ./exploid
chmod 755 exploid
./exploid
Now after typing that last command hurry up and hit the home screen button and turn on wifi. After go back in the terminal and type.
rootshell
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
cp /sdcard/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
rm /system/bin/rootshell
all credit goes to brian from MyDroidWorld for that
2.2 do this ( credit goes to Eousphoros from droidforums)
open up your favorite terminal emulator program
- cd /tmp
- cp /sdcard/rage*.bin /tmp/
- chmod 777 rage*.bin
- ./rage*.bin
- ignore it's output, we are thinking outside of the box here, just wait for it to finish and return a $
- now go to settings -> applications -> manage applications -> running -> terminal and force close that girlie
- relaunch the terminal app and you should be greeted with the friendly # symbol. Toda you now have a root shell
- the rest is pretty much the same.
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
* cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
* chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
b-dub25 said:
2.2 do this ( credit goes to eousphoros from droidforums)
open up your favorite terminal emulator program
- cd /tmp
- cp /sdcard/rage*.bin /tmp/
- chmod 777 rage*.bin
- ./rage*.bin
- ignore it's output, we are thinking outside of the box here, just wait for it to finish and return a $
- now go to settings -> applications -> manage applications -> running -> terminal and force close that girlie
- relaunch the terminal app and you should be greeted with the friendly # symbol. Toda you now have a root shell
- the rest is pretty much the same.
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/superuser.apk /system/app/superuser.apk
- cp /sdcard/su /system/bin/su
* cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
* chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
Click to expand...
Click to collapse
nice. Thank you.
What can i do to root a 2.3.4 with a Mac?

msgingerRC1 French keyboard fix !

Hi,
i post here, because i dont have access to the dev part (10 posts limit maybe).
For the french guys, i have the working files for the hw keyboard.
I'll post them when i get up !
Edit : This is a simple zip file , dont use it with recovery mode !!!!!
Instructions :
unzip file, connect to the phone in adb shell , make /system rw , put the file in /system/usr/keychars (.bin) and /system/usr/keylayout (.kl) . Make the symbolic links to the scholes file. reboot !
I'll test with a more simple(generic) solution.
It's not possible to have an apk?
Nice pat972 I test it now !!
can you explain " Make the symbolic links to the scholes file" please ? (In french toooo )
Ok , let me know if you have a problem with the menu key ! i'll correct it !
For the symbolic links : when you are in the directory , you can do a "ls -l" , you'll see a file pointing to another one, originally pointing to something with "jordan".
you have to do "ln -s /system/usr/keylayout/file.kl sholes-keypad.kl".
No , i don't know how to do apk files !
Thanks for your answer but this don't work.. I have run the folowing command :
>adb remount
remount succeeded
>adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# cp /mnt/sdcard/a/umts_milestone2-keypad.kcm.bin /system/usr/keychars
# cp /mnt/sdcard/a/umts_milestone2-keypad.kl /system/usr/keylayout
# cd /system/usr/keychars/
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kl sholes-keypad.kl
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
exit
>adb reboot
It's good? or I do a mistake ?
Ok it 's good , but you mix all the symbolic and directories !
so here it is :
# cd /system/usr/keychars/
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
# cd ../keylayout/
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kl sholes-keypad.kl
pat972 said:
Ok it 's good , but you mix all the symbolic and directories !
so here it is :
# cd /system/usr/keychars/
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
# cd ../keylayout/
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kl sholes-keypad.kl
Click to expand...
Click to collapse
Sorry for this BIG mistake ... but this don't work too....... I think because I do this mistake ! So I come back tomorrow to do new test
Thanks for help!
Sorry for this BIG mistake ... but this don't work too....... I think because I do this mistake ! So I come back tomorrow to do new test
Thanks for help!
Oups it's me, bad bad , sorry i copy paste your line, but there is a mistake in it again !
For the bin file, it is , keychars directory :
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
then you do a "ls -l" to verify the symlink in each directory :
# ls -l
-rw-r--r-- root root 896 2011-08-24 06:26 umts_milestone2-keypad.kcm.bin
-rw-r--r-- root root 896 2011-07-12 22:00 qwerty2.kcm.bin
-rw-r--r-- root root 896 2011-07-12 22:00 qwerty.kcm.bin
lrwxrwxrwx root root 2011-08-24 05:13 sholes-keypad.kcm.bin -> /system/usr/keychars/umts_milestone2-keypad.kcm.bin
You see that the sholes file point the umts one in the keychars directory not the keylayout !
In fact, this is the problem but when I do this commande line, the result is :
"Link failed file exist"
What I must delete ?
You must delete:
/system/usr/keychars/umts_milestone2-keypad.kcm.bin
so do a
Code:
rm /system/usr/keychars/umts_milestone2-keypad.kcm.bin
Thanks for your answer, but always the same message ...
I have delete "sholes-keypad.kcm.bin" after and can finish all code line but don't work............. I test to restore ROM and restart this
Edit : Now it's work, so the commande line are (if you have put the 2 files on the "a" folder in the SDcard ) :
Code:
>adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# cp /mnt/sdcard/a/umts_milestone2-keypad.kcm.bin /system/usr/keychars
# cp /mnt/sdcard/a/umts_milestone2-keypad.kl /system/usr/keylayout
# cd /system/usr/keychars/
# rm sholes-keypad.kcm.bin
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
# cd /system/usr/keylayout/
# rm sholes-keypad.kl
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kl sholes-keypad.kl
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
>adb reboot
Hi, did someone test this. If you select different country (like german) did the hardware keyboard also switch?
Hi, no i did not, but i would say no ! I have an idea , but i need to test it ! I'll change the bin file and let you know! While im here, it just test your new bluremail.apk and it doesnt seems to work with classic mail ! Said no connection.
Sent from my MotoA953 using XDA App
@walter79 : Yes I have test to change country, but nothing change !
@pat972 : all the "alt" are not good ! (numbers, etc...)
@alex could you do a "ls -l" in each directory and post it here !
@walter : I do some quick test, what appears to me is that my keyboard is always in azerty no matter what locale i put in build.prop or when i change the language setting in the menu.
I also replace my modified keychars by the froyo one, and the keyboard is again in azerty. They are minor differences , more particularly the froyo keychars mix azerty and qwerty layout !
what i think is that the language menu don't change the hw.keyboard layout
I can't see in "cd /system/usr/keychars/" the "Shole.....bin" ....
Code:
# cd /system/usr/keylayout
cd /system/usr/keylayout
# ls -l
ls -l
-rw-r--r-- root root 3295 2011-08-25 11:34 umts_milestone2-k
eypad.kl
-rw-r--r-- root root 4132 2011-08-25 11:16 qwerty.kl
-rw-r--r-- root root 245 2011-08-25 11:16 AVRCP.kl
-rw-r--r-- root root 75 2011-08-25 11:16 cpcap-key.kl
lrwxrwxrwx root root 2011-08-25 11:37 sholes-keypad.k
l -> /system/usr/keylayout/umts_milestone2-keypad.kl
# cd /system/usr/keychars/
cd /system/usr/keychars/
# ls -l
ls -l
----rwxr-x root root 896 2011-08-25 11:36 umts_milestone2-k
eypad.kcm.bin
-rw-r--r-- root root 896 2011-08-25 11:16 qwerty2.kcm.bin
-rw-r--r-- root root 896 2011-08-25 11:16 qwerty.kcm.bin
#
pat972 said:
Oups it's me, bad bad , sorry i copy paste your line, but there is a mistake in it again !
For the bin file, it is , keychars directory :
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
then you do a "ls -l" to verify the symlink in each directory :
# ls -l
-rw-r--r-- root root 896 2011-08-24 06:26 umts_milestone2-keypad.kcm.bin
-rw-r--r-- root root 896 2011-07-12 22:00 qwerty2.kcm.bin
-rw-r--r-- root root 896 2011-07-12 22:00 qwerty.kcm.bin
lrwxrwxrwx root root 2011-08-24 05:13 sholes-keypad.kcm.bin -> /system/usr/keychars/umts_milestone2-keypad.kcm.bin
You see that the sholes file point the umts one in the keychars directory not the keylayout !
Click to expand...
Click to collapse
So , your problem is you don't have the link in the keychars ! so do it , it must look like my previous post (quote) .
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
and do a ls -l to verify it !
All works now ! Sorry ...but I don't understand why the 1rst time this command line don't work....pearhap's can't do the 2 files in the same time (reboot between) ???
Thanks for your help !

Re-root failed

I´m trying to root my phone. It has been rooted before but something messed up and i dant have root anymoore.
I use this method
Code:
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
When i write
Code:
/bin/mount -o remount,rw /system
i get
Code:
/bin/mount: not found
if i check with Astro the file seems to be there.
Anyone know how to solve this?
Just root with : http://forum.xda-developers.com/showthread.php?t=1255548 ?
Its for 2.3.4 or earlier android system.
PakaPakaxz said:
Just root with : http://forum.xda-developers.com/showthread.php?t=1255548 ?
Its for 2.3.4 or earlier android system.
Click to expand...
Click to collapse
It doesnt work.
having the same issue...
jiggytom said:
having the same issue...
Click to expand...
Click to collapse
Did you solved this problem yet?
You might try:
/system/bin/mount -o remount,rw /system
The /bin partition is osh, perhaps you remade this in some way that adb can not read/execute it?

[GUIDE] Root Nexus-S 4.0.3 stock firmware without BL unlock

Thanks to nice Kernel exploid found by zx2c4 http://blog.zx2c4.com/749 and sauriks mempodroid https://github.com/saurik/mempodroid its now very easy to root the nexus-s 4.0.3 firmware without unlooking the BL.
You can just follow this howto http://forum.xda-developers.com/showthread.php?t=1461736 but with this offsets kindly provided by saurik: 0xd7cc 0xad27
If you need a clockworkmod just download rom manager from the market and klick install clock work mod.
have fun
Thanks derpeter, I am looking for the related topic for several days!!!
Will try it later, thanks!!!
thank u dear <3
Worked great! Thanks!
Tested and works. Now running stock OTA rooted ICS.
Checked out the link. Though it stated that it is in the transformer prime thread, the adb commands are still the exact same for nexus s?
Yes the same process works you just have to replace the offsets as it says in the first post.
So the process for the Nexus S would be as follows...
Downloads:
mempodroid
su binary
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 sh
** You should now be in a remote shell session with root (indicated by #)
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
** IF you have previously rooted your Android, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
Click to expand...
Click to collapse
Doesn't work for me. And it's annoying. These are the comands. I had done something bad?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Sergiu>cd C:/
C:\>adb push mempodroid /data/local
adb server is out of date. killing...
* daemon started successfully *
627 KB/s (37273 bytes in 0.058s)
C:\>adb push su /data/local
2426 KB/s (22364 bytes in 0.009s)
C:\>adb shell
[email protected]:/ $ chmod 777 /data/local/mempodroid /data/local/mempodroid 0xd7cc
0xad27 sh
id /data/local/mempodroid 0xd7cc 0xad27 sh <
Unable to chmod 0xd7cc: No such file or directory
10|[email protected]:/ $ chmod 777 /data/local/mempodroid/data/local/mempodroid 0xd7
cc 0xad27 sh
oid/data/local/mempodroid 0xd7cc 0xad27 sh <
Unable to chmod /data/local/mempodroid/data/local/mempodroid: Not a directory
10|[email protected]:/ $ chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 sh
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd7cc 0xad27 sh
[email protected]:/ $ /data/local/mempodroid 0xd7cc 0xad27 sh
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
[email protected]:/ # cat /data/local/su > /system/xbin/su
cat /data/local/su > /system/xbin/su
[email protected]:/ # chown 0.0 /system/xbin/su
chown 0.0 /system/xbin/su
[email protected]:/ # chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
[email protected]:/ # rm /data/local/mempodroid
rm /data/local/mempodroid
[email protected]:/ # rm /data/local/su
rm /data/local/su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\>adb reboot
C:\>
Please help me, I find this metod so f...ing good. I have an i9023, never rooted.
sergiu_s said:
Please help me, I find this metod so f...ing good. I have an i9023, never rooted.
Click to expand...
Click to collapse
I also had trouble following the guide, but then discovered this script, which made the whole process completely automatic.
I'm running stock ICS on i9023.
The script doesn't work for me. I tried it even in Linux. I have stock ics 4.0.3
Sent from my Nexus S using xda premium
Mate u just gain a root. # u log in as root
Sent from my Nexus S using Tapatalk
I saw that, (#), but I don't have root privileges in any application. That's my problem.
Sent from my Nexus S using xda premium
I am not an expert in Android but I think to gain access to app as root would have to go via su app did u try superuser app? I would try it myself but my phone is already rooted via clock mod
Sent from my Nexus S using Tapatalk
I was right mate I just read how to . U haven't got superuser installed obviously. Download from the market and should work.
Sent from my Nexus S using Tapatalk
It worked great guys, thanks to the dev's
I installed superuser and it's works. Thanks guys.
Sent from my Nexus S using xda premium
FYI, this no longer works in 4.0.4. Found out the hard way when I forgot to re-enable the save root option in SuperSU after a nandroid.
The guide works perfectly. I have upgraded my I9020T to 4.0.4 from a AWS 4.0.3 WITHOUT wiping data! Thanks so much!
lethalp1mp said:
FYI, this no longer works in 4.0.4. Found out the hard way when I forgot to re-enable the save root option in SuperSU after a nandroid.
Click to expand...
Click to collapse
ya i did the same thing (didnt run voodoo ota before the 4.0.4 OTA)....looks like google patched this exploit...hope another one comes up so i can root 4.0.4 (without wiping)
nolook said:
ya i did the same thing (didnt run voodoo ota before the 4.0.4 OTA)....looks like google patched this exploit...hope another one comes up so i can root 4.0.4 (without wiping)
Click to expand...
Click to collapse
Yeah i'm also waiting for that!
Sent from my GT-P7300 using XDA

[Q] Mount system in adb to read and write on Nexus 7?

Hi guys,
For the Nexus 7, is there a command I can execute in adb shell root to mount the /system/ to enable reading and writing?
For example for the Galaxy Nexus it was...
mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by- name/system /system
What is it for the Nexus 7?
Thanks!
mdrdroid said:
Hi guys,
For the Nexus 7, is there a command I can execute in adb shell root to mount the /system/ to enable reading and writing?
For example for the Galaxy Nexus it was...
mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by- name/system /system
What is it for the Nexus 7?
Thanks!
Click to expand...
Click to collapse
Shot in the dark:
Code:
adb shell
su
mount -o remount rw /system
then, for example, you should be able to do:
Code:
cp /system/build.prop [destination]
cp [source] /system/
cwoggon said:
Shot in the dark:
Code:
adb shell
su
mount -o remount rw /system
then, for example, you should be able to do:
Code:
cp /system/build.prop [destination]
cp [source] /system/
Click to expand...
Click to collapse
Thank you for replying!
I did try your shot in the dark, however when I tried to do a mkdir test for example I still got:
[email protected]:/ # mkdir test
mkdir failed for test, Read-only file system
I believe the format is like:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
But I don't know the specifics. Any thoughts is appreciated!
What I posted above works on my GNex, was /system your active directory when you tried to mkdir?
I would try on my N7, but its ready to be RMA'd...
Code:
[email protected]:/system # mount -o remount rw /system
mount -o remount rw /system
[email protected]:/system # mkdir test
mkdir test
[email protected]:/system # ls
ls
app
bin
build.prop
etc
fonts
framework
lib
media
test
usr
vendor
xbin
[email protected]:/system # rmdir test
rmdir test
[email protected]:/system # ls
ls
app
bin
build.prop
etc
fonts
framework
lib
media
usr
vendor
xbin
[email protected]:/system #
cwoggon said:
What I posted above works on my GNex, was /system your active directory when you tried to mkdir?
I would try on my N7, but its ready to be RMA'd...
Code:
[email protected]:/system # mount -o remount rw /system
mount -o remount rw /system
[email protected]:/system # mkdir test
mkdir test
[email protected]:/system # ls
ls
app
bin
build.prop
etc
fonts
framework
lib
media
test
usr
vendor
xbin
[email protected]:/system # rmdir test
rmdir test
[email protected]:/system # ls
ls
app
bin
build.prop
etc
fonts
framework
lib
media
usr
vendor
xbin
[email protected]:/system #
Click to expand...
Click to collapse
Your advice worked, I over complicated it. I just did this again on my N7 and worked perfectly. Thank you very much!!!

Categories

Resources