Howto root tf300 jelly bean - Transformer TF300T General

I think I've found a way to root tf300. I'm sorry but it does require unlook. It works for me.
Short story: update asus blob with su.
Warning: Do not update to jelly bean from official asus updates unless you want to lost the option to restore. Set up nvflash first!
Warning #2: Do not unlock! I have to find a knew way.
For those who have made the same mistake as I (installing jelly bean) here is a guide to root.
Requirements: Windows with fastboot / Linux if you can run fastboot and a lot of time
Tools (I haven't found an official qemu.exe and it's tricky to compile that):
-blobunpack and blobupdate
-qemu emulator with a minimalistic linux (bzimage initramfs) where android su is on /root
-fastboot
-official asus firmware blob (asus website)
For windows users:
Unzip all to a directory. Unzip blob twice.
Get blob.APP:
Code:
blobunpack blob APP
Now start Linux:
Code:
qemu -kernel bzImage -initrd initramfs -hda blob.APP
After booting you are in a Linux shell. Run:
Code:
mkdir /mnt
mount -t ext4 /dev/sda /mnt
cp su /mnt/xbin/su
umount /mnt
Close it and run:
Code:
blobupdate blob APP blob.APP
You can transfer the file in fastboot mode:
Code:
fastboot flash system blob
For Linux these steps are much simplier and you don't need qemu:
Code:
$ make
$ chmod 6755 su
$ ./blobunpack blob APP
$ mkdir mnt
$ su
# mount -t ext4 blob.APP mnt
# cp su mnt/xbin/su
# umount mnt
# exit
$ rmdir mnt
$ ./blobupdate blob APP blob.APP
You can download su binary from http://forum.xda-developers.com/showthread.php?t=1704209 and http://db.tt/FBUNeVmo . I don't know if you can run fastboot.

Does the tf300 require a unlocked bootloader?

xSvenHD said:
Does the tf300 require a unlocked bootloader?
Click to expand...
Click to collapse
please read the 1st line of the thread.

Sorry i was reading it fast.
Is this brick free?
Sorry for my bad English Sent From My TF300

Can anyone confirm this?
And does it stay root or do you need an app for su?

grlks said:
Code:
qemu -kernel bzImage -initrd initrd -hda blob.APP
Click to expand...
Click to collapse
This command is not working.Qemu doesn`t start.Maybe wrong linux kernel or some parameters.
UPD:initrd is missing.Only initramfs.
UPD2:Seems like included Linux is corrupted.Can`t get it to work.
UPD3:The whole instruction is a trolling.I can`t mount blob.APP.And string "-hda blob.APP" doesn`t have any sense,because u need a bootable linux image to run qemu,otherwise it will show only bios.And when i `ve booted,i can`t mount blob.app.
OP is a ******.Need another instructions.I have lost 4 hours.

grlks said:
Code:
blobunpack blob APP
Know start Linux:
Code:
qemu -kernel bzImage -initrd initrd -hda blob.APP
After booting you are in a Linux shell. Run:
Code:
mount -t ext4 /dev/sda /mnt
cp su /mnt/xbin/su
poweroff
If it has shuted down update blob:
Code:
blobupdate blob APP blob.APP
You can transfer the file in fastboot mode:
Code:
fastboot flash system blob
Click to expand...
Click to collapse
What I have to do to get updated blob file (I don't have with me the Asus' wire to test the fastoot (last command)) :
Code:
qemu -kernel bzImage -initrd [COLOR="Red"]initramfs[/COLOR] -hda blob.APP
After booting you are in a Linux shell. Run:
Code:
[COLOR="Red"]mkdir /mnt
[/COLOR]mount -t ext4 /dev/sda /mnt
cp [COLOR="Red"]/[/COLOR]su /mnt/xbin/su
[COLOR="Red"]umount /mnt[/COLOR]
poweroff
The poweroff command above didn't work, I kill the quemu proccess after umount /mnt .
If it has shuted down update blob:
Code:
blobupdate blob APP blob.APP
I will try fastboot this afternoon or tomorow.

xSvenHD said:
Sorry i was reading it fast.
Is this brick free?
Click to expand...
Click to collapse
If you downloaded the correct blob file from asus.
It does not require extra tools on android (it will replace any custom recovery with the original SOS / recovery partition).

MantusRus said:
This command is not working.Qemu doesn`t start.Maybe wrong linux kernel or some parameters.
UPD:initrd is missing.Only initramfs.
UPD2:Seems like included Linux is corrupted.Can`t get it to work.
UPD3:The whole instruction is a trolling.I can`t mount blob.APP.And string "-hda blob.APP" doesn`t have any sense,because u need a bootable linux image to run qemu,otherwise it will show only bios.And when i `ve booted,i can`t mount blob.app.
OP is a ******.Need another instructions.I have lost 4 hours.
Click to expand...
Click to collapse
The bootable Linux image is bzImage and initramfs. Sorry for wasting your time.

grlks said:
I think I've found a way to root tf300. There is no unlook required. It works for me.
Short story: update asus blob with su.
Warning: Do not update to jelly bean from official asus updates unless you want to lost the option to restore. Set up nvflash first!
For those who have made the same mistake as I (installing jelly bean) here is a guide to root.
Requirements: Windows with fastboot / Linux if you can run fastboot and a lot of time
Tools (I haven't found an official qemu.exe and it's tricky to compile that):
-blobunpack and blobupdate
-qemu emulator with a minimalistic linux (bzimage initramfs) where android su is on /root
-fastboot
-official asus firmware blob (asus website)
Unzip all to a directory. Unzip blob twice.
Get blob.APP:
Code:
blobunpack blob APP
Now start Linux:
Code:
qemu -kernel bzImage -initrd initramfs -hda blob.APP
After booting you are in a Linux shell. Run:
Code:
mkdir /mnt
mount -t ext4 /dev/sda /mnt
cp su /mnt/xbin/su
umount /mnt
Close it and run:
Code:
blobupdate blob APP blob.APP
You can transfer the file in fastboot mode:
Code:
fastboot flash system blob
For Linux these steps are much simplier:
Code:
$ chmod 6755 su
$ ./blobunpack blob APP
$ mkdir mnt
$ su
# mount -t ext4 blob.APP mnt
# cp su mnt/xbin/su
# umount mnt
$ rmdir mnt
$ ./blobupdate blob APP blob.APP
You can download su binary from http://forum.xda-developers.com/showthread.php?t=1704209 and http://db.tt/FBUNeVmo . I don't know if you can run fastboot.
Click to expand...
Click to collapse
Hello!
Which qemu are you using?
I installed the package from the official fedora repos, I don't have "qemu" alone and "qemu-arm" was not exactly working with the arguments you gave us..
Thanks for the help
edit:
Here an exception thrown when trying to run qemu-system-arm,
I don't know if the problem comes from a wrong usage of the command or if something went wron in the blob unpack...
qemu-system-arm -kernel bzImage -initrd initramfs -hda blob.APP
qemu: fatal: Trying to execute code outside RAM or ROM at 0xff91c756
R00=00000000 R01=00000113 R02=00000100 R03=00000000
R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=00000000 R14=00010010 R15=ff91c756
PSR=400001f3 -Z-- T svc32
Click to expand...
Click to collapse

aachour said:
Hello!
Which qemu are you using?
I installed the package from the official fedora repos, I don't have "qemu" alone and "qemu-arm" was not exactly working with the arguments you gave us..
Thanks for the help
Click to expand...
Click to collapse
qemu-system-i386 but for linux see the buttom. Linux can mount blob.APP if it has loopback support. You just need qemu for windows.

grlks said:
qemu-system-i386 but for linux see the buttom. Linux can mount blob.APP if it has loopback support. You just need qemu for windows.
Click to expand...
Click to collapse
Hej!
Thanks a lot
I thought you had to emulate an arm cpu to run the image.
Thanks again!

Any idea how to mount the tablet in linux while in fastboot mode?
I set the rule :
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0b05", MODE="0666", OWNER="aachour"
in /etc/udev/rules.d/51-android.rules
but this doesn't seem to change anyhing, fastboot wait for the device
I've been searching but didn't find any different rule...
thanks!

The most interesting question-how to fastboot it wit the locked bootloader?It`s "waiting for device" for me.

MantusRus said:
The most interesting question-how to fastboot it wit the locked bootloader?It`s "waiting for device" for me.
Click to expand...
Click to collapse
You have to install the drivers for tf300.

grlks said:
Code:
fastboot flash system blob
Click to expand...
Click to collapse
Fastboot returns :
Code:
writing 'system'.... failed (remote: (InvalidState))
Apparently due to the locked bootloader.
If someone got an idea ?

RaS_KoR said:
Fastboot returns :
Code:
writing 'system'.... failed (remote: (InvalidState))
Apparently due to the locked bootloader.
If someone got an idea ?
Click to expand...
Click to collapse
Same here.I think it`s a dead end.

Problems with locked bootloader
I was wrong. You can't flash with fastboot on locked bootloaders. I am sorry for all those testing it. I will fix it!

grlks said:
I was wrong. You can't flash with fastboot on locked bootloaders. I am sorry for all those testing it. I will fix it!
Click to expand...
Click to collapse
Yeah, that would be awesome
Thanks for all your efforts!

Does it is possible to re-zip the modified blob into the original Asus's zip and install it with a Sd card ?

Related

Install Debian or Ubuntu on ERIS! [Froyolinux]

NEW DEBIAN.img
http://www.multiupload.com/FEO9PZLOCP
This image has internet working and very nice and neat.
To use image copy to ext2 partition and mount
You will need an ext2 partition, you can use my rom and follow its install instructoins and these images and my rom work together perfectly!
http://forum.xda-developers.com/showthread.php?p=16969687#post16969687
download the mount.zip it contains linux a terminal command and linuxboot.sh using adb
http://www.multiupload.com/SDOPA3GVSP
This requires either an ext2 partition or, The img file on your sdcard/debain.img. Using ext2 partition is what is recomended.
adb push linux /system/bin/
adb push linuxboot.sh /system/bin/
Click to expand...
Click to collapse
busybox mount -o rw,remount /
mkdir /mnt/linux
mkdir /sdcard/debain
mount -o rw,loop -t ext2 /sdcard/debain.img /sdcard/debain
mount -o rw -t ext2 /dev/block/mmcblk0p2 /mnt/linux
dd if=/sdcard/debain of=/mnt/linux
Click to expand...
Click to collapse
Now just type :
linux
Click to expand...
Click to collapse
in the terminal and you will be connected
On first boot
linux
Click to expand...
Click to collapse
this should put you into a localhost:#
once in local host type:
nano /etc/init.android/rc_enter.sh​now add this to the file
There should already be this inside:
if [ 1 -eq 1 ]; then echo nameserver 192.168.1.1 > /etc/resolv.conf; fi
/etc/init.d/hostname.sh start
Click to expand...
Click to collapse
ADD :
vncserver -kill :1
rm -r tmp
mkdir tmp
cd tmp
mkdir .X11-unix
cd ..
vncserver
Click to expand...
Click to collapse
To connect to vncserver use any vncserver app and use the following info:
username: localhost
password: android
host: localhost
port: 5901​
Click to expand...
Click to collapse
the new debian.img is roughly 2.5 gigs so I would make enough room on your ext2 partition for 2.5 gigs at least, if you have any problems let me know
OLD
_________________________________________________________________________________________________________________________________________________
OK everyone here it is. Debian and Ubuntu works on ERIS. I have an image that you can download and extract to /sdcard/Ubuntu/ or /sdcard/debian Download One of the .rars below. To use correctly you must have a 2.2 foryo rom, and flash conaps defauctcfs7 loop enabled kernal
Also need a few other files that I have either told you how to or were to download. Follow the instructions and you will be fine.
I am sorry this is not A SELF INSTALLER or an APK BY any means, You must start from scratch and compile your debian, but I have shown the way with Conaps help you can easily install debian from this tutorial.
Debian with vncserver download and extract and push to /sdcard/debian
Ubuntu with vncserver, icewb-UI, and synaptic packagemanager, and firefox, download and extract and push to /sdcard/ubuntu
For Debian
in terminal type:
su
insmod /system/lib/modules/loop.ko
sh /sdcard/debian/installer.sh
chroot debian /bin/bash
For Ubuntu Version
in terminal type:
su
insmod /system/lib/modules/loop.ko
sh /sdcard/ubuntu/mount.sh
chroot ubuntu /bin/bash
to start tightvncserver and connect threw pocket cloud type:
vncserver -geometry 480x320 {-geometry 480x320 is optional}
password:android
repeat:android
open pocket cloud
server: localhost
password:android
port:5901
Special thanks to Conap for creating his new DecafuctCFSv7.zip
Thanks to workshed for a nice keyboard fix
1. download Conap's loop kernal obviously.
2. Recomend downloading and installing conaps CELB (NOT CELEB LOL) ROM, But any 2.2 rom will work
Or Dualrom with loop kernal DualRomLoop
There is a tutorial on how to partitoin your sdcard there, although if you want to run dual rom with debian on second rom I would make my partition sizes as follows:
mkpartfs primary fat32 512B 300MB
mkpartfs primary ext2 300MB 550MB
mkpartfs primary ext2 550MB 900MB
mkpartfs extended 900MB 7948MB
mkpartfs logical ext2 900MB 975MB
mkpartfs logical fat32 975MB 7948
3. Install or flash conaps loop kernal, and conaps celb rom
4. Download this Linux.rar and extract to
/sdcard/debian/*files*here
or
/sdcard/ubuntu/*files*here
Then wait for your phone to boot, and follow the rest of the instructions; I would let the phone idle for a few minutes just to let it settle down
5. Download Swapper from the market, Not Swapper 2. install and create a swap.swp file of 256 megs the most you can, and make sure its running when you continue with the steps so dont exit it, press home instead of the back arrow
DEBIAN
In the terminal type:
su
insmod /system/lib/modules/loop.ko
sh /sdcard/debian/installer.sh
Then an easy chroot:
chroot /debian /bin/bash/
For UBUNTU
In the terminal type:
su
insmod /system/lib/modules/loop.ko
sh /sdcard/ubuntu/mount.sh
Then an easy chroot:
chroot ubuntu /bin/bash/
Or you can Install via gscript by running installer.sh in gscript then an easy chroot by typing in the terminal:
chroot /debian /bin/bash/
MAKE SURE TO SET YOUR PATH IN THE TERMINAL @ localhost:/ export PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
first if that doesnt work try export USER=/root
One time install type:
/scripts/onetime.sh
A little clean up:
cd tmp
rm -r .X*
cd ..
gpg --recv-keys 9AA38DCD55BE302B
gpg --export 9AA38DCD55BE302B | apt-key add -
apt-get update
apt-get install tightvncserver
apt-get install lxde
to start tightvncserver and connect threw pocket cloud type:
vncserver -geometry 480x320
password:android
repeat:android
open pocket cloud
server: localhost
password:android
port:5901
Originally Posted by Conap
6. Open up Terminal Emulator and type:
su
insmod system/lib/modules/loop.ko
busybox mount -o remount,rw /
mkdir debian
busybox mknod /dev/loop0 b 7 0
mount -o loop,noatime sdcard/debian/debian.img debian
mount --bind /dev/pts /debian/dev/pts
mount --bind /proc /debian/proc
mount --bind /sys /debian/sys
sysctl -w net.ipv4.ip_forward=1
chroot /debian /bin/bash
export PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
cd tmp
rm -r .X*
cd ..
If you have problems make sure that you have succesfully installed Conaps Loop
by puting the loop.ko in your sdcard and by typing:
su
cd /sdcard
insmod loop.ko
If your phone reboots you probably need to make sure swapper is running correctly and you have task killer to kill most tasks
GOOD LUCK!
Sounds cool
This is the same spot I am at although I did it a little different. What I am stuck on is getting a ui running. Any luck with that? also anything i apt-get seems to fail...
screenies?
list of wat is and isn't working?
great job though
My sd card is partitoned for Darktremor with a linux swap. Would I still need Swapper?
Sent from my ERIS using XDA App
Well i did the steps this way instead of using scripts.
1. insmod system/lib/modules/loop.ko
2. busybox mount -o remount,rw /
Forgot to write a step: mkdir image
3. busybox mknod /dev/loop0 b 7 0
4. mount -o loop,noatime sdcard/debian.img image
5 .cp -r image/* sd-ext/
6. mkdir data/local/debian/
7. mount -t ext2 /dev/block/mmcblk0p2 /data/local/debian
8. mount --bind /dev/pts /data/local/debian/dev/pts
9. mount --bind /proc /data/local/debian/proc
10. mount --bind /sys /data/local/debian/sys
11. sysctl -w net.ipv4.ip_forward=1
12. chroot /data/local/debian /bin/bash
Now if you don't want to partition your sd card I beleive you can just chroot into the img itself instead of copying the files so you would skip steps 5-7 and change the paths in the other steps from data/local/debian/ to image/ This image was only 1.4 GB which could be made bigger i believe if you wanted more room. The debian.img just goes on the fat32 portion of your sd card. This was done using celbfroyo but all cm roms mount an ext partition as sd-ext i beleive. If your not using a cm rom you would probably need to mount the ext partition yourself.
Tuckface1 said:
screenies?
list of wat is and isn't working?
great job though
Click to expand...
Click to collapse
no screenies cause at this point we are just at a command prompt of debian with no ui...when we get a ui I will get some screenies for you. I am getting an internet connection.
Conap said:
no screenies cause at this point we are just at a command prompt of debian with no ui...when we get a ui I will get some screenies for you. I am getting an internet connection.
Click to expand...
Click to collapse
ok I am getting ui with xwindows server but for some reason cant see login. I get a grey screen when connected to vnc
but under terminal I have web, and debian shell so its close
mjgdroid said:
ok I am getting ui with xwindows server but for some reason cant see login. I get internet with wget but doesnt let me download kde idk what ui are you going to get?
Click to expand...
Click to collapse
i was attempting to get icewm but would take anything at this point. How do you get the ui with xwindows? i was trying through the androidvnc app. Is there a different app?
Conap said:
i was attempting to get icewm but would take anything at this point. How do you get the ui with xwindows? i was trying through the androidvnc app. Is there a different app?
Click to expand...
Click to collapse
apt-get install tightvncserver (return)
apt-get install lxde (return)
i am using pocket cloud light
OK my phone just rebooted due to low memory I will be right back, but I posted what I did after I installed /ontime/sript.sh
then
apt-get install tightvncserver (return)
apt-get install lxde (return)
at wich point I can connect threw pockect cloud light , now I justneed a xwindows file or something
Any idea on how to get terminal not to shut out of localhost after we close it?
mjgdroid said:
Any idea on how to get terminal not to shut out of localhost after we close it?
Click to expand...
Click to collapse
are you running it on the phone or through adb?....i still get could not connect to server in vnc and cloud ...
phone.... adb seems messy to me, and I want to know it works while I'm doing it : ok stupid stupid me, just realized why u are yousing adb lol omg
eventually i would assume we would want a script to run on phone to start it which should be simple...i did get lxde ui to load
mjgdroid said:
apt-get install tightvncserver (return)
apt-get install lxde (return)
i am using pocket cloud light
Click to expand...
Click to collapse
Conap said:
eventually i would assume we would want a script to run on phone to start it which should be simple...i did get lxde ui to load
Click to expand...
Click to collapse
can you log into debian I get a grey screen on pocket cloud maybe a different vnc?
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb devicess
'adb' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\System32>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\System32>cd c:\
c:\>cd c:\sdk\tools
c:\sdk\tools>adb devices
List of devices attached
HT9C2HG16524 device
c:\sdk\tools>adb shell
# su
su
su
su
# su
# insmod /sdcard/loop.ko
insmod /sdcard/loop.ko
# su
su
s#su
su
# insmod /sdcard/loop.ko
insmod /sdcard/loop.ko
insmod: init_module '/sdcard/loop.ko' failed (File exists)
# sh /sdcard/debian/bootdeb.sh
sh /sdcard/debian/bootdeb.sh
modprobe: chdir(2.6.29-DecaFuctCFS-dirty-512f5dee): No such file or directory
←[H←[JAndroid Filesytem remounted as read/write
←[H←[Jmount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or direct
ory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
Custom Linux Pseudo Bootstrapper V1 - by Charan Singh
WEB: http://www.maharajafarms.com
EML: [email protected]
Starting init process
INIT: Debian booting.....
Running Linux Kernel
net.ipv4.ip_forward = 1
AutoMounter started
Type EXIT to end session
Make sure you type EXIT for a clean kill of Debian, Phone will reboot after shut
down!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Debian
Processes killed......
Loopback device shutdown - success
Debian down
by Charan Singh
http://www.maharajafarms.com
[email protected]
Rebooting device to ensure clean shutdown so debian doesnt eat memory ........
.
c:\sdk\tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.
c:\sdk\tools>cd c:\sdk\tools
c:\sdk\tools>adb shell
# insmod /sdcard/loop.ko
insmod /sdcard/loop.ko
# busybox mount -o remount,rw /
busybox mount -o remount,rw /
# busybox mkno /dev/loop0 b 7 0
busybox mkno /dev/loop0 b 7 0
mkno: applet not found
# busybox mknod /dev/loop0 b 7 0
busybox mknod /dev/loop0 b 7 0
# sh /sdcard/debian/bootdeb.sh
sh /sdcard/debian/bootdeb.sh
modprobe: chdir(2.6.29-DecaFuctCFS-dirty-512f5dee): No such file or directory
←[H←[JAndroid Filesytem remounted as read/write
mknod: /dev/loop2: File exists
←[H←[JCustom Linux Pseudo Bootstrapper V1 - by Charan Singh
WEB: http://www.maharajafarms.com
EML: [email protected]
Starting init process
INIT: Debian booting.....
Running Linux Kernel
net.ipv4.ip_forward = 1
AutoMounter started
Type EXIT to end session
Make sure you type EXIT for a clean kill of Debian, Phone will reboot after shut
down!
xauth: (argv):1: bad display name "localhost:1" in "add" command
New 'X' desktop is localhost:1
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/localhost:1.log
localhost:/# apt-get update
apt-get update
Hit http://ftp.de.debian.org lenny Release.gpg
Hit http://ftp.de.debian.org lenny Release
Ign http://ftp.de.debian.org lenny/main Packages/DiffIndex
Hit http://ftp.de.debian.org lenny/main Packages
Reading package lists... Done
W: There is no public key available for the following key IDs:
9AA38DCD55BE302B
W: You may want to run apt-get update to correct these problems
localhost:/#
How do I get rid of the error no public key available for the folowing id's says to run apt-get update, but if i do that i get this error again to run apt-get update endless looop
pocket cloud and tightvncserver working
This sounds promising, but what ui do you hope to run in the end?
Sent from my FroyoEris using XDA App
Nevermind. I read the original thread. Good luck to you all.
Sent from my FroyoEris using XDA App
to get rid of the key error i ran
gpg --recv-keys 9AA38DCD55BE302B
gpg --export 9AA38DCD55BE302B | apt-key add -
(Thanks to workshed for figuring that part out)
i still was having trouble running apt-get install whatever though...
i am able to log in through vnc and cloud now....
Not sure why but each time I chroot in I have to go in and remove all the .X files and directories from the tmp/ folder. Also have to run the command:
export HOME=/root
that can be added to bash.rc once i manage to edit it
I then run vncserver and it asks for a password.
then through cloud or androidvnc i use localhost and port 5901 and put in the password i entered above. I can't seem to get a keyboard on androidvnc so i think i'm gonna try cloud again.

Not sure if this has been done yet (or is even possible...); Flashing via ADB

Hi everyone ^^
I recently had a little... "Incident"... With my phone, resulting in a soft-brick and a whole lot of the Android system being removed (/System/Bin had to be replaced with ADB). What used to happen (Before replacing some of the Android system) was the phone would boot and get stuck at the bootloader. What happens now (after replacing some of the system files) is it'll boot and then reboot after about 30 seconds.
Common fixes would normally include (And are unavailable because...);
Download Mode via 3 button combo (Unavalable due to homekey not working)
Download Mode via ADB (Reboot/Crash)
Recovery Mode via 3 button combo (Again ,home key)
Recovery Mode via ADB (Reboot/Crash)
JIG (Parts unavailable/Stupidly expensive)
Flash via Odin/Heimdall(ADB recognizes the phone, but the system Odin/Heimdall uses does not)
So, what can I do? Well I just tried "ADB shell sbin/recovery" and... Woah, it worked! Sort of... The phone still crashed after about 30 seconds or when I tried to use the CWM recovery to flash a zip. No biggie. It just means some system stuff is missing (I think...).
This is more or less development, and I do not claim to have any major understanding of Android's inner workings besides some UNIX commands. I can't post in Development because of the 10-post requirement, but meh.
What I'm looking for (It's not exactly a question ) is the absolutely critical files that my system is missing (Which I believe to be causing the crash). I ran logcat only to have;
Code:
link_image[1962]: 98 could not load needed library 'liblog.so' for 'logcat' (load_library[1104]: Library 'liblog.so' not found)CANNOT LINK EXECUTABLE
This would eventually go towards an open-source tool for software-based soft-brick recovery.
Here's the ls from /sbin;
Code:
[ expr mkyaffs2image split
[[ false mmcwait.sh stat
adbd fbsetup.sh modprobe strings
ash fdisk more stty
awk fgrep mount swapoff
basename find mountpoint swapon
bbconfig fix_permissions mv sync
bml_over_mtd flash_image nandroid sysctl
bunzip2 fold nandroid-md5.sh tac
busybox free nice tail
bzcat freeramdisk nohup tar
bzip2 fuser od tee
cal getopt parted test
cat grep patch time
catv gunzip pgrep top
chgrp gzip pidof touch
chmod head pkill tr
chown hexdump printenv true
chroot id printf tty
cksum insmod ps tune2fs
clear install pwd ueventd
cmp kill rdev umount
cp killall readlink uname
cpio killall5 realpath uniq
cut killrecovery.sh reboot unix2dos
date length recovery unlzop
dc less renice unyaffs
dd ln reset unzip
depmod losetup rm uptime
devmem ls rmdir usleep
df lsmod rmmod uudecode
diff lspci run-parts uuencode
dirname lsusb sdparted volume
dmesg lzop sed watch
dos2unix lzopcat seq wc
du md5sum setsid which
dump_image mkdir setupenv.sh whoami
e2fsck mke2fs sh xargs
echo mkfifo sha1sum yes
edify mkfs.ext2 sha256sum zcat
egrep mknod sha512sum
env mkswap sleep
erase_image mktemp sort
And ls /system;
Code:
app fonts lost+found tts xbin
bin framework media usr
etc lib modules vendor
Any help with this would be great ^^
So far, it looks like pushing the system directory from a romkitchen rom I built is working... The only problem is that it can't seem to access /sdcard or /sd-ext Can anybody help with this?
The Download mode jigs are cheap? eBay has them for not much at all, especially if you consider the cost of the handset. It's also possible to make them from more common parts. Read the thread, might save you a lot of messing about.

[HowTo] homebrew your custom Ubuntu image for Iconia A500

I'm posting this in a new thread as requested...
There is a simple way to preapare a custom Ubuntu image file compiled for ARMEL with only the packages and functionalities you need.
For this procedure you will need
- a linux machine with working ADB (I tried it on a x64 ubuntu machine)
- a rooted Iconia A500 with busybox installed
- a little knowledge about what you're doing, but just a little.
1. Install Rootstock
on your linux machine, open up the terminal and type
Code:
sudo apt-get install rootstock
If you use at least Ubuntu Karmic, it should automatically pull all the dependencies, otherwise you'll have to manually install Qemu and a newer debootstrap.
2. Create the tarball
you're ready to download the packages and prepare the tarball.
Remember: rootstock doesn't automatically include a kernel, so you'll have to manually include it in the package list
Here's the syntax for a basic run (run "man rootstock" for all the parameters):
Code:
sudo rootstock \
--fqdn [COLOR="Red"]<YOUR_CHOSEN_HOSTNAME>[/COLOR] \
--login [COLOR="Red"]<YOUR_CHOSEN_USERNAME>[/COLOR] \
--password [COLOR="Red"]<YOUR_CHOSEN_PASSWORD>[/COLOR] \
--imagesize [COLOR="Red"]<IMAGE_SIZE_IN_GB>[/COLOR]G \
--seed [COLOR="Red"]<LIST_OF_PACKAGES_SEPARATED_BY_COMMAS>[/COLOR]
Here's an example for a 2GB image with OMAP kernel and a complete Kubuntu-desktop distribution:
Code:
sudo rootstock \
--fqdn ubuntu \
--login ubuntu \
--password ubuntu \
--imagesize 2G \
--seed linux-image-omap,kubuntu-desktop
In --seed you can specify whatever package you want. You could start with just the kernel and build-essential, then add whatever you need. A good start could be like this:
Code:
--seed linux-image-omap,build-essential,lxde,tightvncserver,openssh-server
This will give you a running ubuntu with a very light, performance-oriented desktop environment (lxde) with ssh and vnc.
Remember: It's still possible to add new packages with apt-get from chroot whenever you want.
Once you have chosen the packages you want, you just have to press enter and rootstock will automatic download the packages and prepare the tarball.
You'll end up with a file named "armel-rootfs-<TIMESTAMP>.tgz"
3. Prepare the img file
This is very easy and quick:
Code:
dd if=/dev/zero of=arm_ubuntu.img bs=1MB count=0 seek=[COLOR="Red"]<SIZE_IN_MB>[/COLOR]
The seek parameter defines the size in MB of your image. make it as large as you want, it should at least be as big as the size you selected for the tarball (2G in my example).
Remember: 1 GB = 1024 MB
Now we format the image. Since the Iconia supports ext4 file system, we can use it!
Code:
mkfs.ext4 -F arm_ubuntu.img
You may want to pass other flags to define advanced options, labels and reserved blocks, but this is the least you need to make it work.
4. Decompress
Now we have to mount the img file in a loop:
Code:
sudo mount -o loop arm_ubuntu.img /mnt
and decompress the tarball into it.
Code:
sudo tar -C /mnt -zxf armel-rootfs-<TIMESTAMP>.tgz
It's done!
[OPTIONAL]
This is the right time to put custom scripts in /mnt/usr/bin like this one to start the vnc server with the correct geometry for the A500:
Code:
#!/bin/bash
rm -fr /tmp/.X1*
vncserver -geometry 1280x752
NB: the A500 screen is 1280x800, but the honeycomb statusbar (1280x48px) is always on top. To avoid panning to show the ubuntu menu bar, we just subtract those 48 pixels from the ubuntu vertical resolution.
Now we just umount it.
Code:
sudo umount /mnt
5. Load on the tablet and get it running
The script to mount and boot is derived from the one in the Backtrack 5 Thread.
Load the img file on the tablet with
Code:
adb push arm_ubuntu.img /sdcard/ubuntu/arm_ubuntu.img
It will take a loooong time and there's no progress bar, so just have faith.
Next, we prepare the boot script. The only thing you need to do is to put your username in (the one you chose in rootstock).
Code:
perm=$(id|cut -b 5)
if [ "$perm" != "0" ];then echo "This Script Needs Root! Type : su";exit;fi
mount -o remount,rw /dev/block/mmcblk0p5 /system
export kit=/sdcard/ubuntu
export bin=/system/bin
export mnt=/data/local/mnt
mkdir -p $mnt
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export USER=[B][COLOR="Red"]<THE_USERNAME_YOU_CHOSE_BEFORE>[/COLOR][/B]
export HOME=/home/$USER
export stor=$mnt/home/$USER/storage
export sdcard=$stor/sdcard
export extsd=$stor/external_sd
export usb=$stor/USB_storage
if [ -b /dev/loop2 ]; then
echo "Loop device exists"
else
busybox mknod /dev/loop2 b 7 0
fi
mount -o loop,rw,noatime -t ext4 $kit/arm_ubuntu.img $mnt
echo "mounting storage devices in $stor..."
mkdir -p $sdcard
mkdir -p $extsd
mkdir -p $usb
busybox mount --bind /mnt/sdcard $sdcard
busybox mount --bind /mnt/external_sd $extsd
busybox mount --bind /mnt/usb_storage $usb
mount -t devpts devpts $mnt/dev/pts
mount -t proc proc $mnt/proc
mount -t sysfs sysfs $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "127.0.0.1 localhost ubuntu" > $mnt/etc/hosts
busybox chroot $mnt /bin/bash
echo "Shutting down Ubuntu ARM for Iconia A500"
umount $sdcard
umount $extsd
umount $usb
umount $mnt/dev/pts
umount $mnt/proc
umount $mnt/sys
umount $mnt
Once done, we can save the file as startubuntu and adb push it to the tab. (the same folder as the img is fine)
Done! We run it by invoking the startubuntu script from the android terminal emulator (must be in superuser mode)
I hope you found this how-to useful.
And we use this distro via our tablets ssh client?
EDIT: sorry my bad Never read code while tired
Hi,
i am running ubuntu natty.
and i got this error:
...
Setting up wireless-crda (1.13) ...
Setting up linux-image-2.6.38-8-omap (2.6.38-8.42) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.38-8-omap
/bin/df: Warning: cannot read table of mounted file systems: No such file or directory
Not sure if it is fatal. rootstock has created successful the rootfs
reida010 said:
Hi,
i am running ubuntu natty.
and i got this error:
...
Setting up wireless-crda (1.13) ...
Setting up linux-image-2.6.38-8-omap (2.6.38-8.42) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.38-8-omap
/bin/df: Warning: cannot read table of mounted file systems: No such file or directory
Not sure if it is fatal. rootstock has created successful the rootfs
Click to expand...
Click to collapse
Same happened to me. Totally not fatal. the tarball is good.
For everyone out there:
I would like your help with testing. I have a crash on start problem with firefox in all the images I tried. Does any of you have the same issue?
Hi,
i get
Code:
Loop device exists
then i did
Code:
echo "$kit/arm_ubuntu.img"
and i get
Code:
/sdcard/ubuntu/arm_ubuntu.img
but then i get
Code:
mount: cannot setup loop device: No such file or directory
any ideas?
Because of firefox.
i read a while ago a tweet about a bug in meego and ubuntu in firefox for arm.
when it is this bug then you should try firefox trunk because it is fixed.
but i cannot refind it :-(
edit:
bugzilla.mozilla.org/show_bug.cgi?id=634594
I was searching for that today, thanks mate. Nice Tutorial =D
reida010 said:
Hi,
but then i get
Code:
mount: cannot setup loop device: No such file or directory
any ideas?
edit:
bugzilla.mozilla.org/show_bug.cgi?id=634594
Click to expand...
Click to collapse
i have the same problem. You should make loop file not in /mnt/sdcard, but in /mnt/external_sd.
Kh_Shad said:
i have the same problem. You should make loop file not in /mnt/sdcard, but in /mnt/external_sd.
Click to expand...
Click to collapse
That would apply only if you put the image file in the external MicroSD, if you have put it in the internal memory (as described in the tutorial) the path is /mnt/sdcard. Also, the speed of the internal memory is better.
Hi,
i found out how i can make it work
but it's strange.
i don't works when i do
Code:
sh ./startubuntu
but with this it works fine:
Code:
/system/bin/sh ./startubuntu
Is this maybe because i didn't use adb.
Someone told me that copy paste might change the permissions (what the ****! really?)
on my tablet startubuntu is not executable.
And it doesn't change anything when i do chmod 755 startubuntu
but after moving it to /system/bin chmod works fine.
After then i can always just run
Code:
su
startubuntu
and ubuntu is up and running.
(many thanks by the way :-D)
Sorry guys, will this method produce a native Ubuntu install similair to how Wubi works? Or is this like the chroot methods were we have to VNC into the distro from within Android?
It is native!!!
but you need vnc to access the xserver
On my n900 i used xephyr but i don't think this is working for android because afaik they don't use X. (n900 is so cool for linux geeks ;-D)
edit:
if you mean with 'native' that it will replace android -> no -> it is a chroot
Yeah that answered my question. Thank you
I'm not going to bother until there is a native distro running with full system resources. I guess with the current bootloader situation that day may never come :-(
It failed in creating the image for me... and it seems like a error in the package linux-image-2.6.38-8-omap
[TRIM]
Need to get 37.4 MB of archives.
After this operation, 98.3 MB of additional disk space will be used.
Get:1 //ports.ubuntu.com/ubuntu-ports/ natty/main wireless-crda armel 1.13 [15.0 kB]
Get:2 //ports.ubuntu.com/ubuntu-ports/ natty/main linux-image-2.6.38-8-omap armel 2.6.38-8.42 [19.8 MB]
Get:3 //ports.ubuntu.com/ubuntu-ports/ natty/main devio armel 1.2-1build1 [16.9 kB]
Get:4 //ports.ubuntu.com/ubuntu-ports/ natty/main flash-kernel armel 2.28ubuntu19 [13.1 kB]
Get:5 //ports.ubuntu.com/ubuntu-ports/ natty/universe kubuntu-mobile armel 1.218 [2720 B]
Get:6 //ports.ubuntu.com/ubuntu-ports/ natty/main linux-firmware all 1.52 [17.5 MB]
Get:7 //ports.ubuntu.com/ubuntu-ports/ natty/main linux-image-omap armel 2.6.38.8.22 [2394 B]
Fetched 37.4 MB in 5min 29s (113 kB/s)
Selecting previously deselected package wireless-crda.
(Reading database ... 9309 files and directories currently installed.)
Unpacking wireless-crda (from .../wireless-crda_1.13_armel.deb) ...
Selecting previously deselected package linux-image-2.6.38-8-omap.
Unpacking linux-image-2.6.38-8-omap (from .../linux-image-2.6.38-8-omap_2.6.38-8.42_armel.deb) ...
Done.
Selecting previously deselected package devio.
Unpacking devio (from .../devio_1.2-1build1_armel.deb) ...
Selecting previously deselected package flash-kernel.
Unpacking flash-kernel (from .../flash-kernel_2.28ubuntu19_armel.deb) ...
Selecting previously deselected package kubuntu-mobile.
Unpacking kubuntu-mobile (from .../kubuntu-mobile_1.218_armel.deb) ...
Selecting previously deselected package linux-firmware.
Unpacking linux-firmware (from .../linux-firmware_1.52_all.deb) ...
Selecting previously deselected package linux-image-omap.
Unpacking linux-image-omap (from .../linux-image-omap_2.6.38.8.22_armel.deb) ...
Setting up wireless-crda (1.13) ...
Setting up linux-image-2.6.38-8-omap (2.6.38-8.42) ...
Running depmod.
Failed to run depmod
dpkg: error processing linux-image-2.6.38-8-omap (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up devio (1.2-1build1) ...
No apport report written because MaxReports is reached already
Setting up flash-kernel (2.28ubuntu19) ...
Setting up kubuntu-mobile (1.218) ...
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
Setting up linux-firmware (1.52) ...
I: Cleaning up...
dpkg: dependency problems prevent configuration of linux-image-omap:
linux-image-omap depends on linux-image-2.6.38-8-omap; however:
Package linux-image-2.6.38-8-omap is not configured yet.
dpkg: error processing linux-image-omap (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
Errors were encountered while processing:
linux-image-2.6.38-8-omap
linux-image-omap
E: Sub-process /usr/bin/dpkg returned an error code (1)
I: Umounting temporary Image
I keep getting a failure also!
Ceck out both of my log files below.
tholmewood said:
Sorry guys, will this method produce a native Ubuntu install similair to how Wubi works? Or is this like the chroot methods were we have to VNC into the distro from within Android?
Click to expand...
Click to collapse
It is a chroot/vnc method, currently the only method available to run linux on this device, because of the locked bootloader... I seriously hope for a chance to dual boot in the future.
i was wondering what packages are needed in order to create an ubuntu netbook Edition? Is the A500 powerful enough for that kind of interface?
Thought you guys might be interested in this post.
http://forum.xda-developers.com/showpost.php?p=15156543&postcount=64
Have fun!
@p-ille
Have you tried firefox daily?
Did it work?
reida010 said:
@p-ille
Have you tried firefox daily?
Did it work?
Click to expand...
Click to collapse
Not really, my job is killing me these days... I'll try it asap!
sent from my Iconia A500
p-ille said:
Not really, my job is killing me these days... I'll try it asap!
sent from my Iconia A500
Click to expand...
Click to collapse
You realize what a pain that tutorial is to follow? Could you please provide a pre built image at least if asking for scripts is probably way too much?

[Q] Compile from sources

OS Ubuntu 10.04 LTS x64
I downloaded photonic sources from schlund github place, ARM EABI Toolchain, get config from device(with schlund FW) and try to make, but have a error in makefile in "expr $(VERSION) \* 65536 + $(PATCHLEVEL) \* 256 + $(SUBLEVEL)); \". If i calculate version and write number to expr make done. I have zImage. Now i try to write new kernel to device. Get file boot.img from clockworkmod backup, "unpackbootimg -i boot.img", "mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline "no_console_suspend=1 console=null" --base 00200000 --pagesize 2048 -o ./tmp/boot.img" => have new boot.img. Through ADB push boot.img to sdcard then:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/boot.img
Reboot device, but it write error in console(then i restore recovery and restore)
How to correctly build kernel and put it to the device?
Sorry for my bad english...
You not need bloksize argument for mkbootimg. And you have wrong argument for base (00200000 instead of 0x00200000)! Try:
- mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline 'no_console_suspend=1 console=null' --base 0x00200000 -o ./tmp/boot.img"
First, mount your sd card in recovery, then:
- adb push boot.img /sdcard/
than:
- adb shell erase_image boot
than:
- adb shell flash_image boot /sdcard/boot.img
It working also without mounting sdcard becouse boot.img is small and you are able to put it in memory, for example push it to /
- adb push boot.img /
- adb shell erase_image boot
- adb shell flash_image boot /boot.img
Can i "flash_image" In the booted android or just recovery?
will try to evening....
Just want to play with kernel...
YES!!!!!!!!!!!
It's work!!!!!!!!!!!!!!!!!!!!!!!!!
Thanx munjeni!!!!!!!!!!

Root permission on CM9 RC2

Hi guys! I want to know how to have root permission on my Htc Hd Mini with NAND ROM CM9 RC2...
Thanks!
Repack boot.img, repack initrd and edit default.prop (change ro.secure=1 to ro.secure=0), pack initrd than pack boot.img again...done
munjeni said:
Repack boot.img, repack initrd and edit default.prop (change ro.secure=1 to ro.secure=0), pack initrd than pack boot.img again...done
Click to expand...
Click to collapse
Ok...so after I must to reinstall the rom?
fra18061988 said:
Ok...so after I must to reinstall the rom?
Click to expand...
Click to collapse
No! Just install only boot.img
Can you edit boot.img for me? I haven't software to unpack .img...is impossible for me...
My boot.img is attached in this post...
Thank you so much!!!!
You can do it using your recovery!
Procedure:
reboot to recovery
installing tools:
adb push unpackbootimg /
adb push mkbootimg /
adb push mkbootfs /
adb shell chmod 6755 /unpackbootimg
adb shell chmod 6755 /mkbootimg
adb shell chmod 6755 /mkbootfs
unpacking boot.img:
adb push boot.img /tmp/
adb shell
cd /tmp
/unpackbootimg -i boot.img
mkdir initr
cd initr
ls ../
gunzip < ../boot.img-ramdisk.gz | cpio -i --make-directories
cd ..
edit default.prop that is located in /tmp/initr (you can do it by adb push and adb pull... just for idea)!
/mkbootfs ./initr | gzip > initrd.gz
/mkbootimg --kernel boot.img-zImage --ramdisk initrd.gz --cmdline 'no_console_suspend=1 console=null' --base 0x12c00000 -o new_boot.img
and you are done, press ctrl+c to exit from adb, than:
adb pull /tmp/new_boot.img
Or if you want to install new boot.img:
adb push new_boot.img /
adb shell
erase_image boot
flash_image boot /new_boot.img
To repack boot.img I used Cygwin...but in default.prop, "ro.secure" is already set to ro.secure=0 ...see below
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
So...root permission are on CM9 RC2
My big problem was to move applications like Facebook, Google Play etc...on SD Card. I solved the problem with Titanium Backup and Link2SD...

Categories

Resources