yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] jrohwer:
N.B. the partition /dev/block/mmcblk0p4 is not the boot partition it is the staging partition!!! The boot partition (as well as the recovery partition) is not directly accessible for dd on the TF. This means any images that are flashed need to be packed into a special binary format (a.k.a. blobs) with tags to indicate which partition the image needs to be flashed to (LNX for the boot partition, SOS for the recovery partition). When the TF reboots after you have flashed a blob to staging, this blob gets "processed" (this is the blue line you are seeing on reboot) and the image gets flashed to the correct partition.

Incidentally the kernel used in the latest TWRP recoveries has a hack that the boot and recovery partitions are directly accessible by dd. Not so the stock ASUS rom. Not sure about KatKiss or other custom ROMS, haven't investigated.

Note you can still flash the correct blobs to staging using dd from Android or Linux and then reboot (I have actually written scripts for my own use case) and don't go via recovery. The blobs will still get processed upon reboot. Only thing is you can't backup the boot and recovery partitions from within Linux or Android, you need TWRP for that.
[Eee Pad Transformer Android Development] steveeJ:
thank you for your detailed and very helpful answer.

it makes sense now that the paranoid android kernel blob i tried to flash to that staging partition didn't flash a valid kernel onto the target partition p9, which it's own update-script flashes it to... it's missing the staging information :) now with that information i can investigate and experiment further. the best thing to have would be some kind of graphical boot menu, which is my long term goal. but first I gotta get all features working on the gentoo i installed today.

btw, i had to replace the

run-init

with

exec switch_root

at the end of your provided init-script to make gentoo boot.

greets

steveeJ
[Eee Pad Transformer Android Development] jrohwer:
Well you can still use the paranoid android kernel. Most probably the image provided is a plain Android boot image (you can easily test if it unpacks with abootimg). The fact that it's flashed to p9 only works in TWRP (as explained in my previous post). However, you can blobpack it with the blob tools.

https://github.com/AndroidRoot/BlobTools

It's a very straightforward compile. Then, assuming your PA image is called boot.img, you just do:

blobpack boot.blob LNX boot.img

This will create boot.blob with the partition information (LNX), so that you can then flash it to p4 (either using dd or in recovery). You can also unpack blobs with blobunpack. But the fact that you changed my initrd tells me that you must already have blobunpacked the blob I provided to get to it? :D Or did you take a backup from TWRP?

Useful to know for gentoo users :)
[Eee Pad Transformer Android Development] jrohwer:
Replying to self here. It wasn't the nvram.txt after all. Both nvram_murata.txt and nvram.txt work with the bcmdhd driver. The issue is that the bcmdhd driver crashes and locks up your system when trying to connect to an ad-hoc network (which is what I was trying to do when first getting it to work). It crashes irrespective of the nvram.txt used. It only works with a proper AP. Is this a known issue? The bcm4329 driver works with ad-hoc networks and normal access points.
[Eee Pad Transformer Android Development] shanegru:
how do i unistall this? couldnt get lubuntu to work.. just delete the linuxroot folder? or is there more to it?
[Eee Pad Transformer Android Development] steveeJ:
flash your ROMs kernel to have access to android again, and delete the folder you created under /data.

yes, that should be it!
[Eee Pad Transformer Android Development] shanegru:
ok i tryed.. tubuntu and lubuntu... not sure why this is not working.. i know im on sk1....could it be the rom i use? i use raymans cm 10 version 8... with his cooked in OC'd kernal.. its android 4.2. it seems to install ok.. but when i flash the kernal.. it just keep saying the same old thing...i use raymans rom. almost no force closes.. everything works... and i get 3-7 days battery life.. my tablet never goes off... and wifi is on 24/7... but would like to check out linux on this tablet...without formatting my drives...:))
[Eee Pad Transformer Android Development] jrohwer:
What's the "same old thing" it keeps on saying when you flash the kernel? This mod should work for any rom since you're not actually booting up that rom but booting a Linux specific kernel.
[Eee Pad Transformer Android Development] shanegru:
ok i use twrp 2.3.2.3 i do notice when i flash stuff..it says e:Unable to mount '/staging.. its always said this.. ive flashed many roms and they do work...i notice if i have my dock in use.. or attached the errors.. seem to be endless.. i dont know how to make a logcat or a text file.. with all the errors :(...anyways heres the screen i get..... plymouthd: ply-terminal.c:611: ply_terminal_open: ASSERTION 'terminal != ((void *)0)' failed then minutes later it said... {245.022721} INFO task kinteract:59 blocked for more then 120 seconds.. echo 0. /proc/sys/kernal/hung_task_timeout_secs disable this message

i did run the commands as the op said... and i had my dock attached.. ill delete and start over..without the dock..

btw with the dock attached.. tons of endless errors.... without the dock.. not so many errors.. ok gonna do the delete.. and retry now without the dock.... tell me how to make a file of errors.. ill test for ya.. have the dock etc

ok

also is there an easy way to remove that folder?.. when im in terminal emulatori type this

cd /data

rmdir linuxroot

and it says the not empty...lmao.. new to termnal
[Eee Pad Transformer Android Development] prog19:
just "rm -rf /data/linuxroot" should do the trick
[Eee Pad Transformer Android Development] shanegru:
ok tryed this again.. without my dock.. didnt work for me.. and it did copy a bunch of stuff... so i know it worked..

i checked /data/linuxroot.... that folder was made.. i checked mnt/unbuntu also was made...

maybe rayman has a different file structure...is there a command..to make a text file. of my file structure...

so we can see whats wrong? or a text file with my errors...

any help would be greatly appreciated...

i now i am on sk 1.. cuz nvflash works on my tablet...i use twrp 2.3.2.3 and raymans custom rom 4.2 the one he perfected by christmas.. awesome rom.. everything works...

and i mean every darn thing works...and i like this concept.. running both OS on the same partition..
[Eee Pad Transformer Android Development] jrohwer:
The /staging error is perfectly normal and occurs everytime you flash a blob to the staging partition. See here for an explanation:

http://xdaforums.com/showpost.php?p=43912072&postcount=68

Which image are you using to copy over to /data/linuxroot as in the OP? Maybe try a different image?

This has been answered above.
[Eee Pad Transformer Android Development] vietchinh:
The problem is...

NOTHING WORKS! For me then.

I have testes some of the image ( Netintallt Tubuntu, Archlinux( couldnt make dekstop because im to noob).

Its either wifi doesn't work or it wourlndt boot with the same error he had.

So i took a break and wait for new kernel that come up and adress some of problems.
[Eee Pad Transformer Android Development] shanegru:
from the transformation.. like the op said.. i itryed lubuntu.. archlinuz... but i did notice.. that lubutu did have the home folder.. that the op said would create problems.. so did i use the wrong image... or should i just delete the home folder?... wish i know how to make my errors a text file.. i cant stop the screen of errors.... sure would make support more easier...
[Eee Pad Transformer Android Development] jrohwer:
After a failed boot, reboot back into Android. Use a file manager to navigate to the directory /data/linuxroot/var/log

Post the following files, if they are there:

dmesg
kern.log
syslog

PM me the files or post them here, then I can try and have a look. If the files are not there, it means the boot process doesn't even find the root fs, and then I can't really help unfortunately.
[Eee Pad Transformer Android Development] jrohwer:
So you did manage to boot (but then wifi didn't work)? If so that should be relatively easy to fix. Did you copy the modules as described in the first post? Did you manually try running "modprobe bcm4329 iface_name=wlan0" in a terminal as root? Then if you do "ifconfig" it should list the wlan0 interface and you should be able to connect.

Which image did you use to boot successfully?
[Eee Pad Transformer Android Development] vietchinh:
Archlinux the prebuild one. Where you have to make a desktop etc.

I will try the outdated archlinux one.

And other images again.
[Eee Pad Transformer Android Development] shanegru:
ok i only had the dmesg file.. heres the link

http://db.tt/ZwQlo5YX

let me know.. whats up...

if anyone got any linux img to work.. plz post the link...

its got to be the img or busybox hmmm
[Eee Pad Transformer Android Development] rickatnight11:
I tried this with Tubuntu v1.1(lubuntu 12.10) from the Transformazing thread, and while the kernel boots up, it eventually hangs on...

plymouthd: ply-terminal.c:611: ply_terminal_open: Assertion `terminal != ((void*)0)' failed.

Attaching dmesg, kern.log, and syslog.
[Eee Pad Transformer Android Development] shanegru:
ok guys i might of been told a fix... this comes from user miniblu .. hope i spelled it correctly he cant post here...but heres how he fixed it

I to am using SBK1 running CM10,1 4.2.2 and was having exactly the same problem as you. It seems that when you try to create the rootfile system in cm10.1 into the /data partition something goes wrong. I eventually got it working using Lbuntu 12.04 image from transformazing loopmount thread, First use transformazings instuctions to get this img working as loopmount with his linux1android4.2 kernel. While running this copy the rootbind lib/modules into the image and install cpufrequtils (apt-get install cpufrequtils) and create a file /etc/default/cpufrequtils containing

ENABLE="true"

GOVERNOR="performance"

MAX_SPEED="1410000"

MIN_SPEED="312000"

this will set max frequency to 1.41GHz as for me anything above that is not very stable which meant for me installing this later to fix it took many reboots. Also following transformazings instructions to get trackpad working at this stage will make things much easier later.

Now boot back to android and follow the instructions from rootbind OP to create the linixroot folder from img file but wherever it says /data/linuxroot change to /data/data/lintuxroot. Once this is done boot back into the loopmount linux and open a root file manager (sudo pcmanfm) goto "places" then "mmcblk0p7" then "data" here you will find the "linuxroot" folder. Cut this and go up one level and paist(into "mmcblk0p7"). Close the file manager and in the terminal you opened it from type "sync". You can now sutdown and flash the rootbind kernel and all should work. I'm not fully sure why this works but it has worked for me with 3 different images now. ps I would post a more detailed explanation but I'm new to xda and can't post to development threads yet. Hope this helps. MiniBlu

ill test this soon.. and let yas know.. if it helped me.. this is for cm 10.1 roms...

ok nothing works.. guess ill give up
[Eee Pad Transformer Android Development] prog19:
I've managed to boot a ubuntu 13.04 core and install lxde, but i wasn't able to add my user, so I went all the way back, trying lubuntu-desktop. As soon as it gets done I will try this method, or post how I get my thing done.
[Eee Pad Transformer Android Development] jrohwer:
These three files are definitely not created during boot with my kernel since they say "Linux version 2.6.36.4" while mine is 3.1.10. So I suppose that they are just the old log files that came with the image that you used.
[Eee Pad Transformer Android Development] jrohwer:
OK this is interesting, I have never used multiuser mode and am not exactly sure how the mounts work there, but it seems to be the problem, i.e. that /data is not the root directory of mmcblk0p7. Anyone running multiuser mode (either CM10.1 or EOS/KatKiss), could you do me a favour and run the following commands in a terminal:

su
busybox mount > /sdcard/mounts.txt

And then grab the file mounts.txt from the /sdcard folder and post it here?
[Eee Pad Transformer Android Development] maq0007:
Here you go, I'm using KatKiss
[Eee Pad Transformer Android Development] shanegru:
raymans v.8 cm10.1.. with his cooked rom.. completed before xmas :)

it rules...

rootfs on / type rootfs (ro,relatime)

tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

none on /dev/cpuctl type cgroup (rw,relatime,cpu)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

debugfs on /sys/kernel/debug type debugfs (rw,relatime)

none on /acct type cgroup (rw,relatime,cpuacct)

tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)

tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)

/dev/block/dm-0 on /mnt/asec/roman10.media.converter.v7vfp3-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=writeback)

tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)

/dev/block/mmcblk0p1 on /system type ext4 (ro,relatime,user_xattr,acl,barrier=1,data=ordered)

/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,journal_async_commit,nodelalloc,data=writeback)

/dev/block/mmcblk0p7 on /data type ext4 (rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,journal_async_commit,nodelalloc,data=writeback)

/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)

tmpfs on /storage/emulated type tmpfs (rw,nosuid,nodev,relatime,mode=050,gid=1028)

/dev/block/vold/179:9 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
[Eee Pad Transformer Android Development] jrohwer:
OK it seems as from Android 4.2 onwards Linux namespaces and bind mounts are used to bind to the correct "emulated" external storage. This would be all the "fuse" mounts in the above post. I need to install a 4.2 ROM with multiuser setup in order to come up with a workaround. I have an idea but need to test it first. I will report back here.

See http://source.android.com/devices/tech/storage/index.html for further info (bottom of the page).
[Eee Pad Transformer Android Development] shanegru:
thanks man..appreciate any help..i dont want to change roms..when you find the best rom.. it hard to give it up..and this way of mounting both linux and android without formatting.. or loosing the much needed twrp.. is very desireable to me... can anyone tell me what tablet rayman is working on?.. also.. can someone post any links.. to teach me. how to take open source android and port it to this device? might as well learn to do this.. i have plenty of time on my hands..nothing i cant learn..also interested in learning how to pack and unpack my own blobs any help would be nice..who knows i might end up being a new developer
[Eee Pad Transformer Android Development] TravellingGuy:
i2c transfer timed out

I'm experimenting with options to install Linux on my tf101. I've succesfully got some of the Ubuntu images running via OLife (and Tubuntu). I have also successfully created a Debian image (using http://xdaforums.com/showthread.php?t=1476835) and successfully got it running with OLife.

I'd love to use rootbind, but my problem is when I try to run any image (whether my own or one of the various Ubuntu flavours floating around xda), I get this over and over and over and over:

tegra-i2c tegra-i2c.1: i2c transfer timed out, addr (0x000b, data 0x00)
tegra-i2c tegra-i2c.1: i2c transfer timed out, addr (0x000b, data 0xc2)
arbitration lost recovered by re-try-count 0x00000001
arbitration lost recovered by re-try-count 0x00000008

Any help/suggestions? There doesn't seem to be that much info around on fixing it.
[Eee Pad Transformer Android Development] jrohwer:
I'm sorry I have never seen this and have no idea!!! :confused:

Does the kernel actually boot the root filesystem?

Can you try and take logs according to this post:

http://xdaforums.com/showpost.php?p=44211217&postcount=82

If the date/time on those files is the time when you tried to boot up Linux, then it means the file system is read. Then please post the contents of those files. OTOH if the date is in the past, it means the boot does not even get to the point where the root fs is mounted, and it is a problem with the rootbind setup.
[Eee Pad Transformer Android Development] Kingzak34:
Undock your tab until you get to session manager screen ( boot with your tab undocked and you won't have these errors )

Tapatalké depuis mon Nexus 4 MIUI !
[Eee Pad Transformer Android Development] shanegru:
thats the jb error.. i get when i have my dock attached.. without the dock.. im still stuck at my error.. in post above here some where..

still waiting for the fix.. i sent my mount.txt file :)) patiently waiting..
[Eee Pad Transformer Android Development] TravellingGuy:
You, good sir, are a God. :)

Thank you very much, booting without the dock works, a great workaround!
[Eee Pad Transformer Android Development] JoinTheRealms:
[MENTION=3753391]jrohwer[/MENTION]

This might help with the mount thing, my brains not working enough to look into it :silly: http://xdaforums.com/showthread.php?p=36889027
[Eee Pad Transformer Android Development] Kingzak34:
But I really don't know why there are these errors

Tapatalké depuis mon Nexus 4 MIUI !
[Eee Pad Transformer Android Development] jrohwer:
Yes I'm sure it is the issue. However, it is only for dalvik apps and busybox is not a dalvik apps. The issue however, is where /data is mounted and when you start the android terminal emulator, that is also a dalvik app, and then /data won't point to the root of mmcblk0p7. Not sure what happens in adb. I first need to install a 4.2 ROM on my TF101 to actually see how this works (haven't done so yet).
[Eee Pad Transformer Android Development] JoinTheRealms:
Ah ok, i remember having this issue on the tf101, but my tf300 and tf700 dont seem to have this issue with custom kernels. Oh the other thing im still trying to understand the whole kernel process/ dualbooting etc etc. Over on the tf700 forum we have just got a kexec capable kernel compiled and i immediately thought of the tf101, since majority of tf101 devices are nvflash capable you could safely re partition mmcblk0p7 and give a dedicated linux partition and have a kexec based dualboot without any of the short-comings of mounting an image.

Im still very much in the learning stages so im not sure what this would take to get running, ull know much better than i do;).
[Eee Pad Transformer Android Development] jrohwer:
Yes but I own a TF101G which does not have nvflash/wheelie, so I can't repartition. That's what got me into developing this in the first place! I also don't have C programming skills so can't edit kernel source code, so I'm using other guys' sources (Jhinta). Quite comfortable to compile kernels though :)

I remember reading somewhere on the TF700 forums that you have a kernel that can actually boot both Android and Ubuntu, and I saw a mod where the initrd was modded to give a boot menu upon boot where the user could choose Ubuntu or Android. For this to work though you need a single kernel that can boot both OSes....
[Eee Pad Transformer Android Development] JoinTheRealms:
Yeah it's kinda confusing the hybrid kernel, the benefit of the initrd is you can choose between 9 different rootfs files:) heres the kernel patch for the kexec http://xdaforums.com/attachment.php?attachmentid=2171875&d=1375883275, not even sure how the patching process works,or how the kexec works but its proberly worth a try? :)

On the tf700 the kexec apparently looks for a linux partition on external sd card (mmcblk0p8?) if not it falls back to booting the normal kernel. Once ive learned more about how it all works im gonna try compile a hybrid kernel for the tf101, since it apparently doesn't require much modification to stock android sources.
[Eee Pad Transformer Android Development] tounano:
an error I'm getting

Hey,

I'm getting this error as well:

plymouthd: ply-terminal.c:611: ply_terminal_open: Assertion 'terminal != ((void *)0)' failed.

Tried to find a solution, but without success.

I tried Tubunto from Transformazing thread.

Did anyone come up with a solution?

Thanks.
[Eee Pad Transformer Android Development] jrohwer:
Possible fix for running with JB4.2

To all those who have been struggling to get rootbind installed from a system running JB4.2, try the following in a terminal:

busybox chmod 755 /data/linuxroot

Bottom line: I have installed KatKiss4.2 on my TF and the ubuntu rootbind runs just fine. However, I realized that the default umask on this ROM (and I suppose other JB ROMS as well) is 0077 whereas on ICS it was 0000. This means that when you create the folder /data/linuxroot as root user in a terminal, only root will be able to write to that folder and any subfolders, and of course the Linux system won't be able to boot. That's why we have to chmod it to 755 so that other UIDs can enter and read that directory as well.

Instructions on OP have been updated, but if you already have your rootfs under /data/linuxroot, the chmod command above should suffice. Let me know if it works...
[Eee Pad Transformer Android Development] vietchinh:
Does this applies to 4.3?

I wil ltest it on there
[Eee Pad Transformer Android Development] prog19:
Worked like a charm using Tubuntu 1.2 IMG, and Katkiss 4.3 rom.

You, sir, are a certified beast. Thank you very much !

edit: After doing sudo depmod -a everything got screwed-up again. I'll redo the process and report back
[Eee Pad Transformer Android Development] shanegru:
im not sure if its a JB issue or not.. i just went back to stock rooted i..c.s. pretty much same problem...i did notice kind of a new error..

something about ext 2...

ill try this command before i give up..

busybox chmod 755 /data/linuxroot

let ya know in a few minutes'

oh wait..i didnt try that command yet.. but after running them errors.. then i hit i for ignore.... and im at guest account.. hmm let me see if it still boots up lmao

ok it does boot up..im using stock i.c.s. rooted..and lubuntu from the thread the op said to use one of them :))

trying to su in terminal.. anyone know the lubuntu password.. or was there another account.. i should of logged in lmao

ok ive tryed this a few times.. my problem might of been using my dock.. but i know i removed the dock after install .. then hit i for ignnore.. when screen says to hit.. s or i or m.. i did that a few times.. and it eventually let me in...

trying to guess the password until i get a reply..

stuck at lubuntu password lmao...

just hit i :)) when you see the errors :)) it will bootup

still need password for the lubuntu

not sure if the modules installed.. gonna try n get internet
[Eee Pad Transformer Android Development] jrohwer:
Haven't tested myself but see below, prog19 seems to have gotten it working.

:)
[Eee Pad Transformer Android Development] vietchinh:
So far i can confirm to everyone that wifi works normal.

Though after installing with net installer v0.7 it doesnt boot. It seems i dont need to install those extra"s or it went somwhere wrong.

Well Tubuntu is next.