I just got /system mounted as writable, and was able to install busybox to /system/xbin. It's a workaround for now but it works. Updating the OP with detalis.
Sorry if I'm asking a dumb question, I'm just learning adb and still don't fully understand it all...but are you saying root was successful? Or are you still trying to get system r/w? I'm going to use this method to at least make sure I get the same result and try to contribute whatever I can. If anyone needs a tester or anything, please let me know how I can help. Thanks for all of your hard work, guys.
Jeromel - how did you install ICS? Did you upgrade from HC, and if so, were you rooted?
Please excuse my ignorance on this, but where exactly to you add the three lines to install-recovery.sh? I've got root and r/w on system, but I'm a little shaky on editing a system file I'm unfamiliar with.
Thanks for all your work on this!!
It's safe to delete everything in the file. I usually like to make a copy of any files I edit ot let Root Explorer do it for you.
yes, i tried fastboot in hc 3.2.1 with no luck. the new adb number is the serial number on your sd cover on your device. i am going to start working on fastboot again tonight when i get home from work. good luck guys!Did anyone else notice that the ADB devices number has changed now? Instead of a series of numbers & characters, it has 11 numbers instead?
This boot/flash_image/fastboot stuff is driving me nuts...
Did anyone try to fastboot oem unlock with 3.2/3.2.1?
Seems like some other folks got something going on this: http://translate.googleusercontent....615135&usg=ALkJrhjALDNSSlGHDd26CctrAwxkKFebiA.
Seems like some other folks got something going on this: http://translate.googleusercontent....615135&usg=ALkJrhjALDNSSlGHDd26CctrAwxkKFebiA.
Edit: The downloaded file is stored in /cache/fota_dn/309CEA5E573E2F0ACC60EF7F0537F2D9.zip - I pulled it to my pc via adb command, but the file is not valid and won't open - likewise on the acer, I can't view the contents using anything. Could it be secured/encrypted?
Edit: The downloaded file is stored in /cache/fota_dn/309CEA5E573E2F0ACC60EF7F0537F2D9.zip - I pulled it to my pc via adb command, but the file is not valid and won't open - likewise on the acer, I can't view the contents using anything. Could it be secured/encrypted?
$ adb shell mkdir /data/local/tools
$ adb push tools /data/local/tools ; adb shell
$ cd /data/local ; chmod 755 tools/*
$ cd tools ; ./mempodroid 0xd9f0 0xaf47 sh
# PATH=$PWD:$PATH
# sh mount.txt -o remount,rw /system
# ./busybox cp busybox /system/xbin; ./busybox cp su /system/xbin/
# chmod 6755 /system/xbin/su
# cd /system/xbin
# for i in $(busybox --list); do ln -s busybox $i; done; sync
# cp /data/local/tools/mount.txt /system/bin/mount
# cp /data/local/tools/mount.txt /system/xbin/mount
[b]This is no longer needed[/b]
# ./busybox losetup -o $((512 * 51200)) /dev/block/loop7 /dev/block/mmcblk0
# ./busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
# mkdir loop ; mount -t ext4 /dev/block/loop7 loop
# ./busybox cp su loop/xbin/ ; ./busybox cp busybox loop/xbin/
# chmod 6755 loop/xbin/su ; sync
# cd loop/xbin
# for i in $(busybox --list); do ln -s busybox $i; done; sync
# busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
# mount -t ext4 /dev/block/loop7 /data/local/tools/loop
$ adb shell
$ su
# stop
[b]your screen will go black[/b]
# mkdir /data/loop
[b]skip this if the loop is already set up
# busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3[/b]
# mount -t ext4 /dev/block/loop7 /data/loop
# mount -o bind /data/loop /system
# start
busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
mount /dev/block/loop7 /data/loop
mount -o bind /data/loop /system
Not sure why the files aren't showing up. Maybe try busybox sync after copying them.
[edit] I asssume you can get root manually and it's just a problem with your script?
Let me know, hopefully the instructions are all correct now. I updated them several times yesterday.
Also, there might be an easier way than what I posted, if you find one post it here or shoot me a PM.
Thought that might happen, have to get some more ideas.
[edit] So maybe using 'stop' will help, from adb
# stop
# mount -o bind /data/local/tools/loop /system
# start
There probably won't be a bootanimation, but if it gets to the lockscreen it should be ok without FCs. If it bootloops just hold in the power button or use the pinhole reset.
I should just suck it up and upgrade just don't think I'm ready.