yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] vit0oo:
No I just installed prime 1.5, but before install prime 1.5 i had this error ...
[Eee Pad Transformer Android Development] Jhinta:
mkbootimg --cmdline 'nvmem=128M@384M mem=1024M@0M vmalloc=256M init=/init root=/dev/mmcblk1p1 video=tegrafb console=tty0 usbcore.old_scheme_first=1 tegraboot=sdmmc' --kernel zImage --ramdisk ubuntu.gz -o boot-new.img

normaly this would load my ramdisk even if i remove root= and init=, but now it lissens to that so ramdisk gets ignored but why .. i had this problem after i updated to the new android now i cant get it back .
[Eee Pad Transformer Android Development] vit0oo:
I have try :

mkbootimg --cmdline 'nvmem=128M@384M mem=1024M@0M vmalloc=256M init=/init root=/dev/mmcblk1p1 video=tegrafb console=tty0 usbcore.old_scheme_first=1 tegraboot=sdmmc' --kernel boot-new.img-kernel.gz --ramdisk boot-new.img-ramdisk.cpio.gz -o boot-vito.img

./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
./nvflash -r --download 6 boot-vito.img

Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c11c840ff5517
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0

sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Nvflash started
[resume mode]
sending file: boot-vito.img
/ 6240256/6240256 bytes sent
boot-vito.img sent successfully

And allways the same error the ramedisk not load :D

Edit : i have other error when i remove init=/init and root=/dev/mmcblk1p1
[Eee Pad Transformer Android Development] rdnetto:
When you figure it out, please post the answer. I went and installed Prime 1.6 like an idiot, now I've got the same problem. :(

Flashing the official firmware (v8.2.3.9) also fails in CMW, with:

Installing update...
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-8.2.3.9.zip
(Status 7)
Installation aborted.

It seems to be tied to the NVidia logo on the boot screen, which remains even when other images are flashed. It may be necessary to get a Nandroid from one of the others...
[Eee Pad Transformer Android Development] Jhinta:
darn well this confirms it , some how the loaders gets locked out.

i will add native loaders in OP after i get out of work .

so till this is fix rootfs is gone.
[Eee Pad Transformer Android Development] rdnetto:
I've figured out a fix (I think this is a new record for me :)).

-restore to good state with with this nvflash script

-downgrade to 8.2.3.9

-root

-use v2 of the Ubuntu bootloader/kernel - the current one (v3) crashes (also the Linux version is corrupt, as I noted above). As far as I can tell, apart from the different kernel you've also changed the init script and bootimg.cfg (the bootsize option) slightly - any of them could be the cause.

You may want to take a look at that script btw, if you haven't already - could have some useful info on how to reverse this without wiping absolutely everything.
[Eee Pad Transformer Android Development] Jhinta:
I didn't change any config file . Only boot.img . So flashing the new Rom repartitions nand little diff ?
[Eee Pad Transformer Android Development] lilstevie:
bootimg.cfg is all the information about a given boot.img, this is generated out of the header information in the boot.img and is used by abootimg
[Eee Pad Transformer Android Development] rdnetto:
I guess the bootsize value was changed automatically because the size of the boot image was different. Whatever the reason, it got stuck in a reboot loop when I tried to use it.

I don't think the partitioning is different (though I haven't checked*) - it looks like the update modifies whatever loads the bootloaders we've been using, and adds the NVidia logo in the progress. Since it's fixed by the unroot script, it should be one of those partitions, though I'm not familiar enough with Android partitions and nvflash to reverse engineer it. There's also the possibility there's another partition we don't know about that's modified by the installation of the new kernel, but that's unlikely.

* Off the top of my head, Android does have fdisk installed (or it might just be Prime). We can use that to check if the partition table has changed, and dd/md5sum to check which partitions are changed.

Or we could do the update and then flash one partition at a time until it gets fixed, which would probably be faster.

At any rate, it's rather late here, so I'm off to bed.
[Eee Pad Transformer Android Development] Jhinta:
sorry guys i want to check it out but i'm realy going for my weekend :o

i will not be home so i cant do anything .. till monday
[Eee Pad Transformer Android Development] vit0oo:
you think if i put a nandroid backup from other asustf101, it could downgrade the bootloader ?!

Edit :

Ok guys i found the solution,

download this archive and execute download.bat

reboot

download that and execute flash.bat ( this boot.img remove nvidia boot logo )

reboot

the pad boot on the new boot.img and load ramdisk :D
[Eee Pad Transformer Android Development] Jhinta:
Dont know ,what about prime 1.4 nvflash that should be a full reinstall .
[Eee Pad Transformer Android Development] vit0oo:
I upload the nvflash archive with boot.img system.img and recovery.img for downgrad the bootloader and remove the nvidia boot logo
[Eee Pad Transformer Android Development] aligatro2010:
Jhinta,

Can you create a binary patch from old img to new one? Many of us already downloaded the old img and re-downloading would waste a lot of traffic. However, a patch should weight a lot less, because it will only have changes.

There are tools called bsdiff and bspatch. I only tried to create a patch and it seems to work. Make sure to use it on unzipped image.

bsdiff: usage: bsdiff oldfile newfile patchfile

bspatch: usage: bspatch oldfile newfile patchfile
[Eee Pad Transformer Android Development] rdnetto:
Alternatively, he could just upload a tar of files and a script to overwrite the old ones. I don't think he could have changed that much, beyond replacing/adding modules and editing some conf files...
[Eee Pad Transformer Android Development] vit0oo:
Link added for downgrad the bootloader
[Eee Pad Transformer Android Development] aligatro2010:
True, but it`s a bit trickier to apply.
[Eee Pad Transformer Android Development] mgalyan:
Coming from Prime 1.6, linux system hangs on boot near beginning of boot script. Says that it cannot mount the SDCARD, and then it simply displays readings of the "lux" from the light sensor for the screen. Have not figured out a way to boot into the GUI yet.
[Eee Pad Transformer Android Development] lilstevie:
SDCARD not being mounted means the rootfs does not get mounted, this means no GUI to boot into
[Eee Pad Transformer Android Development] Jhinta:
Will the kernel source off 8.4.4.11 working when its out?

if it does we better can do that. in the mean time we can do native .

native also boots faster
[Eee Pad Transformer Android Development] mrevankyle:
not to be a bother but i would like to try this out and the link has been out for 4 days. so could someone kindly reupload or direct me to where i could download the rootfs. thanks in advance
[Eee Pad Transformer Android Development] Jhinta:
For the moment i cant upload , jtaging my modem once thats done, i will have my own server backup and running

You can easly download a rootfs try hd2 file and upgrade it to natty , you can use any rootfs for arm so just look for it read OP !!!
[Eee Pad Transformer Android Development] aligatro2010:
The new init script requires two partitions now ? One is for storing image itself, but why need the other one? Is it going to be used for opt or something in new image?

Also, I have a weird problem with framebuffer and Xorg. When it tries to start, it gives me error that device or resource is busy. I am using your older kernel from July 2nd and old rootfs image. It's weird, because it worked before and I didn't change anything.
[Eee Pad Transformer Android Development] mrevankyle:
isn't the rootfs from the hd2 just for choroot?
[Eee Pad Transformer Android Development] Jhinta:
Then i ask you what is chroot

And when you know that i will ask you, what is a root file system

And when you know that you go , ahhhhhh

Read OP mega source link
[Eee Pad Transformer Android Development] Jhinta:
Jtaging is thaking sooolong somthing like 1kbs orso
[Eee Pad Transformer Android Development] Jhinta:
The boot.img that i made need 1 of them your choice . But with the new bootloader they dont work , did you update your android ?

I need to build new one also there is a fix , read threat for that.
[Eee Pad Transformer Android Development] kalel90:
Jhinta i was wondering if you might consider porting meego to the asus transformer after Ubuntu? Nvidia recently released drivers meego that support the transformer.

Thread is here - http://xdaforums.com/showthread.php?t=1189072
[Eee Pad Transformer Android Development] rdnetto:
Meego is a lot closer to regular Linux than Android is. Those drivers could be really useful for getting graphics acceleration (and maybe some other stuff like Bluetooth or audio) working.
[Eee Pad Transformer Android Development] rdnetto:
There are 2 ways you can use the init script:

-1 FAT partition containing ubuntu/rootfs.ext2

-2 partitions: 1 FAT (unused, but has to be FAT), and 1 ext which is the root file system (i.e. no loop mount)

The unused FAT partition is just so the SD card remains usable in Windows.

Later down the track I expect it'll be used for /boot (probably as ext2) when we get dual boot working, since the initrd's size is limited.
[Eee Pad Transformer Android Development] rdnetto:
Has anyone been able to get the current bootloader to work? Mine gets stuck in a reboot loop even if the init script is blank (although the init script does run), so I'm thinking there's something wrong with the kernel.

On a related note, could anyone fill me in on how to turn the vmlinuz file produced by compiling the source into the zImage file used by abootimg?

EDIT: Never mind, I just realised it's generated by the Makefile...
[Eee Pad Transformer Android Development] Jhinta:
:D i will.
[Eee Pad Transformer Android Development] Jhinta:
tnk its the kernel source for 8.4.4.11 , i'm waiting for it.
[Eee Pad Transformer Android Development] SalsaForte:
Just a quick: go go go!

Some more encouragement is never too much! :D
[Eee Pad Transformer Android Development] rdnetto:
To be clear, I was referring to the boot image you uploaded, the one with the kernel that's supposed to match the source code in the OP.

Here's the error I get:

Bad newroot /rfs
Kernel panic - not syncing: Attempted to kill init!
...
Rebooting in 1 sec...

Manually running 'switch_root /rfs /init' in a shell gives "switch_root: not rootfs". Anything with exec causes a kernel panic like the one above.

EDIT:

Fixed it, though this was only supposed to facilitate debugging.

Added the following lines to the end of the init script:

echo "Failed to load rootfs."

#necessary to keep process running, otherwise kernel panic results
exec /bin/sh
[Eee Pad Transformer Android Development] Jhinta:
oke now that the kernel is out , i can build again .

Also see lilstevy dev ubuntu threat for emmc install .

congrats to lilstevy for dual boot .

I will still build the final boot.img , with rootfs or native second partition.

also i will be adding cwm zip for restoring android or ubuntu.
[Eee Pad Transformer Android Development] crash6:
I dont have anytime to work on this myself right now but I can donate some server time to speed things up if needed. Pm me. I have access to some pretty hardcore equipment. Ive done the same thing with DJSteve for the original development for the streak.
[Eee Pad Transformer Android Development] jerdog:
https://twitter.com/#!/littlesteve/status/87219690576941056

lilstevie showing that it booted - some things still don't work - but it's a great start!!!!
[Eee Pad Transformer Android Development] lugiber:
Amazing!

I never would have thought that anyone would have come this far so quickly!

Can/will you be able to use it without the "dock"? I have found that i'm only using the dock about half the time i'm using my transformer.

Good work.Great work! Keep it up!

(And don't forget to make this availble soon,can't wait to try it out!)
[Eee Pad Transformer Android Development] lilstevie:
you can use it without the dock by using an onscreen keyboard, but I find it easier to use the dock :) I updated the video with a link to the bootimg
[Eee Pad Transformer Android Development] lugiber:
Wow that's great! And, yeah, the docks easier to use. i suppose. But sometimes when you're just "couch surfing" the screen is all you need. So its nice to know you have that option as well!

I'll try your release when you have posted instructions on how to flash. I really don't want to spend hours unbricking my device.

Can't wait to try it out though! This is the reason i bought the transformer in the first place. I really love to beta test and to see my hardware improve with every new release. Its also nice to see the community surpass what the "big companes" can come up with.

Thanks for all your efforts!
[Eee Pad Transformer Android Development] lilstevie:
I would recommend the dock for at least the first boot (oem-config doesn't have a virtual keyboard). past that though it should be possible
[Eee Pad Transformer Android Development] lugiber:
Cool, linux is always best with a keyboard. The same goes for android.

Now get busy on that howto! ;)
[Eee Pad Transformer Android Development] brando56894:
I'm sure someone could write a shell script that would backup and restore the required partitions. That actually sounds like something I could do, ill take a stab at writing one when I get home later.
[Eee Pad Transformer Android Development] lilstevie:
it should be fairly easy, just download all the partitions with nvflash, reset the device upload a new partition layout and reflash with a smaller sdcard partition that has the ubuntu rootfs, at the moment though it is just easier (with constant changes) to use the uSD, if you would like to write an installer script though that would be a welcomed addition
[Eee Pad Transformer Android Development] lilstevie:
[YOUTUBE]3cFcjB3_RsI[/YOUTUBE]

New video shows some undocked action :) and usage
[Eee Pad Transformer Android Development] Jhinta:
[Q] are you using a rootfs or partition?

btw xorg fix is up in OP
[Eee Pad Transformer Android Development] lilstevie:
I am booting from a partition
[Eee Pad Transformer Android Development] stark0:
how do you make dual boot ? Android boots from recovery ? So .. you lose recovery ?
[Eee Pad Transformer Android Development] Jhinta:
do you have wifi working?
[Eee Pad Transformer Android Development] lilstevie:
Presently no, it is one of the issues that I am currently working on (the second being dock related). it appears to be a driver issue
[Eee Pad Transformer Android Development] brando56894:
Idk if this came across in my post but i was talking about a linux based cwm replacement. Ill look into writong that script.
[Eee Pad Transformer Android Development] aligatro2010:
lilstevie ,

Will I be able to restore old recovery partition if I messup system partition ? Does bootloader have a recovery mode of it's own?

Nevermind, APX loads bin from pc. So, as long as I don't erase bootloader i'll be able to restore right ?

Also, I was thinking about a dualboot. Can't we put a small kernel that supports kexec and then from a menu select which kernel to boot into?
[Eee Pad Transformer Android Development] 0lddirtypaki:
this is unbelievable! to be able to boot into ubuntu and for it be that responsive so early in dev is crazy! i know we are a long away from complete but any word on how the tegra 2 will work? will we be able to utilize compiz or unity?
[Eee Pad Transformer Android Development] paow:
Before someone even starts to think about those stuff nvidia needs to release the drivers I guess
[Eee Pad Transformer Android Development] jerdog:
Lilstevie- is there a possibility you could put together the steps in text form, or the OP could update with the exact steps from start to finish so others can join in? Building an nvflash with this would be helpful to.

Great work!
[Eee Pad Transformer Android Development] Jhinta:
are you willing to send min max event1 , Also dit you had to patch kernel for touchscreen?
[Eee Pad Transformer Android Development] brando56894:
Would it be relatively easy to switch distributions on the tf if the user is well versed in Linux and the general process is laid out? I'd rather have Arch Linux on mine since that's what I use on my desktop, I feel Ubuntu would be too bulky for an embedded system.
[Eee Pad Transformer Android Development] Tenny:
I agree, another lighter distro of ubuntu would work well too. I'm a fan of kubuntu & lubuntu. I have lubuntu running on a nettop, and it runs pretty smoothly compared to ubuntu.
[Eee Pad Transformer Android Development] TheDeadCPU:
LXDE should be best for the TF. (IMO)
[Eee Pad Transformer Android Development] brando56894:
I never really liked the light window managers, I think I'd go with a stripped down version of KDE 4. My netbook with a single core atom at 1.6 GHz and integrated video could run it, so it should run fine on here with a dual core CPU and a hexacore (?) GPU.
[Eee Pad Transformer Android Development] lilstevie:
APX mode is implemented in bootrom so even with a bad bootloader you can still recover, APX is like godmode for the device :)

as for using kexec, fixing kexec on the arm platform is a total whore, the best thing would be to do something similar to samsung, and implement a recovery switch in the initrd for android

Natty supports MT events otb and ignores singletouch events, I haven't yet worked the kernel to support evdev/xorg versions that are not from canonicals natty/oneiric repos. The only drivers I have touched so far are the ones that have not been working properly, the elantech touchpad, and the bcm wireless
[Eee Pad Transformer Android Development] lithiasalesjs:
So basically ... No Dock .... You can't install ?
[Eee Pad Transformer Android Development] Jhinta:
i got dock working a trying to get multitouch pad working
[Eee Pad Transformer Android Development] lilstevie:
the dock mainly works OTB, the touchpad, and the keymapping is the only thing that needs to be worked on
[Eee Pad Transformer Android Development] lilstevie:
no, it is just harder to run oem-config
[Eee Pad Transformer Android Development] xTRICKYxx:
I cannot wait for a fully functioning Ubuntu 11 with Hardware acceleration on my TF101.
[Eee Pad Transformer Android Development] nicandris:
guys since this is a DEV thread why don't you just throw the instructions for us to install the Ubuntu and try to actually help you with the issues?
[Eee Pad Transformer Android Development] Jhinta:
QUOTE ->This is a Dev thread <-QUOTE -> Then you sould already know how to boot it.

m'n files are not needed !!! :cool:
[Eee Pad Transformer Android Development] lilstevie:
agreed here,

To be honest if you know enough to help the boot.imgs posted by both Jhinta and myself are enough
[Eee Pad Transformer Android Development] dark alex:
Will we be able to dual-boot Android and Ubuntu then?
[Eee Pad Transformer Android Development] Jhinta:
people, please !!!!:mad:

Do not PM me Unless you got some code,info,howto's,patches,or damn good ID.

READ !! and i'm not gonne tell you how ubuntu works, google will do that for you !!!
[Eee Pad Transformer Android Development] dark alex:
I'll rephrase my question.

I want to know if there's or will be a possibility to choose between Android 3.1 and Ubuntu (or whatever) like in Grub or something similar...
[Eee Pad Transformer Android Development] aligatro2010:
Yes, you can dual-boot, but there is no nice menu and you would have to overwrite your recovery partition. So, basically you can make it boot into ubuntu when you press power - volume- and android just by booting normally.

About recovery partition, lilstevie, did you extend partition 6 into 7 to get more space on partition 5? (my old post was deleted for some reason)

Everyone, I was successful at booting ubuntu into tty console, but I don't have a dock atm, so I can't do anything.(can't enter text) I used rootfs from nvidia website + binary provided by lilstevie. Process of installing is super easy, if you have some experience with linux and know how to use nvflash. I am not sure if I should post instructions, since this is still highly experimental and lilstevie said he will post instructions himself in the next release.
[Eee Pad Transformer Android Development] Viish:
Please do :D
[Eee Pad Transformer Android Development] Tenny:
I disagree. It would just clog up the thread with people that can't help the progress only slow the devs down by giving support. At this point wifi doesn't work so its not like there is much fun / cool / etc stuff to really do. Once wifi is working the then I think it'd be good for it to be released.
[Eee Pad Transformer Android Development] cowballz69:
Agreed smooth it out as much as u can before making it main stream.
[Eee Pad Transformer Android Development] Jhinta:
lilstevie , does you ubuntu even boot when building wifi as M.

Some info 4 others .

touch screen working by default in natty. with correct settings

also setting cpu speed min ad 300+ fix some lag higer is beter ( or a better scaler is needed )
[Eee Pad Transformer Android Development] TheDeadCPU:
Just a tip, if you're going to make instructions etc. Make a feedback thread for it. Add the instructions etc there, and just keep this for dev only. (feedback thread in general ofc)
[Eee Pad Transformer Android Development] nfusion77:
You could always make a different thread so it does not clutter up this one and it would help some of us to get a few trial runs in before we get everything up and running.;)
[Eee Pad Transformer Android Development] lilstevie:
I did not resize partition 5, partition 5 is about 5MB which is enough for the root kernel I use on 3.1
[Eee Pad Transformer Android Development] lilstevie:
wifi is one of the key ingredients to my next release, no wifi no deal
[Eee Pad Transformer Android Development] lilstevie:
By default wifi is built as a module so yes :)
[Eee Pad Transformer Android Development] Jhinta:
sorry i mean build in :p , mine doesnt when i do that .
[Eee Pad Transformer Android Development] Jhinta:
wifi is finaly up , needs some fixing.

only thing to do is touchpad and sound
[Eee Pad Transformer Android Development] stark0:
Good news :)

I think you and lilstevie should work together!
[Eee Pad Transformer Android Development] cowballz69:
how is the performance of flash on it?
[Eee Pad Transformer Android Development] jcarrz1:
Is x working or is it still command-line only?

this is really exciting, good work!
[Eee Pad Transformer Android Development] stark0:
x is working, see the first post, screen and text.
[Eee Pad Transformer Android Development] TheDeadCPU:
Awesome! Working wifi! I'ma tell the Portal admin. (He has a Transformer)
[Eee Pad Transformer Android Development] icow:
how do you actually install this really wanna try it out
[Eee Pad Transformer Android Development] TheDeadCPU:
There will be instructions later. Read the thread damnit.
[Eee Pad Transformer Android Development] lilstevie:
what was the trick to getting wifi up, having networking would be advantageous to testing
[Eee Pad Transformer Android Development] test1943:
is it just me or many people

Somehow I prefer VNC or the chroot(honestly I don't know what it means) way, we'll use honeycomb as the main OS and whenever we need to do things that can't be done in Android, instead of reboot and startup a new one, we OPEN Ubuntu;-)

Isn't that a dream come true:rolleyes: