Develop Bugs

[android] NAND flashale android !!USER!! Questions UPDATED MANY HOW TO'S

Hi there, as many of you may know dzo or simple god makes a flashable version of android for our KAISERs.
But vefore here are some rules:
THIS THREAD IS MADE TO KEEP THE FLASHING ANDROID ON KAISER DEV THREAD CLEAN FROM USERQUESTIONS!!!
DON'T ASK USER QUESTIONS IN THE DEV THREAD!!!
This Thread is for experienced Kaiser users who aren't in development but wan't to see android running native from NAND.
THIS IS AT THE CURRENT STATE VERY VERY VERY BETA, THERE MAY BE A HIGH RISC TO BRICK YOUR DEVICE. THIS WILL COMPLETLY WIPE WINDOWS MOBILE. JUST USE IT IF YOU CAN ANSWER YOURSELF THE FOLLOWING QUESTIONS: (without search function)
-What is an .nbh file
-how to flash a kaiser
-What is HardSPL /Security unlock
-How to recover a bad rom flash?
-What to do if your device won't start anymore?
-Do you have basic android skills?
Ok Guys, little cleanup and updates:
INDEX:
-Post one:
Different flashing methods
Things to take care off
-Post two:
How to creat your own nbh files
How to make custom splash screens
-Post three:
Working Systems/rootfs
Bugs
Usefull Links
Thanks
HOW TO START ANDROID FROM NAND
Method one:
1-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
2-Download http://www.mediafire.com/?zldjhfnkzk2
3-Copy the androidinstall.tar from the androidinstall.zip file to the root of your sdcard
4-delete/rename any old android files on your sdcard
5-Unzip the androidinstall.zip and replace the ruu_signed.nbh in it with the one you downloaded in the first link. (must be named ruu_signed.nbh)
-6Run the custom ruu.exe - thats all after reboot you'll have a flashed Cupcake android.
Method two:
1-delete/rename any old android files on your sdcard
2-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
3-Create three empty files on your sdcard wihout any extension:
-datafstonand
-systemfstonand
-rootfstonand
4-Copy your prefered rootfs.img, system(img,ext2,sqsh) and an empty data.img to sdcard root
5-Copy the nbh file you downloaded to the root of your sdcard and rename to kaisimg.nbh
6-Reboot your device using restart button and cam button, then when it tells you, press power key to flash the new nbh.
-Reboot by pulling the battery - Thats it ( First start may take a while and may reboot randomly, just give it some time)
Different Tricks and hints (collected in the forums):
-Change Panel Type:
Run: "echo 1 > /sys/module/board_htckaiser/parameters/panel_type" through adb or init
-Experimental GPS:
For working, gps you need to replace libgps.so with the one from the vogue gps thread.
Experimental openGL Drivers ( Eclair Only)
-Download this one and flash your prefered nbh: http://rapidshare.com/files/345432577/kasiandroid_nbh_with_opengl.zip
-Install the included script sheduler, and replace the afterboot.txt with the one included in the zip file
This will install an app that will run the afterboot.txt after every boot and fix file permissions.
-Or you can open the afterboot.txt and run it in terminal after every boot.
To see if it works install the included gallery3d.apk, iff you see thumbnails, it worked

Not tested by me, yet through no time.. (Thanks to quitlahok and rzk333 for this manual)
THIS IS JUST FOR THOOSE WHO ARE MORE IN DEVELOPMENT AND LINUX
HOW TO CREATE YOUR OWN NBH FILES:
1- Set up your prefered Linux Setup, i use Debian.
2-Build kaiser kernel with wiki manual
3-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/tinboot
4-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/bootenv
5-cd bootenv
6-cp buildInitrd buildInitrd-mini
7-nano (or whatever your favorite editor is) buildInitrd-mini
8-change all instances (2 of them) of initrd to initrd-mini
9-sh buildInitrd-mini
10-cd tinboot
11-nano tinboot.S
12-the paths to fix are at the bottom of the file, it's pretty self-explanatory. higher up in the file you'll see the kernel cmdline under an .ifdef kaiser line
13-after that you'll need to download and extract any windows kitchen, and install wine however your linux distro requires and make a note of the path you extract nbhmerge.exe to as you'll need it in your tinboot.S file, along with the path to your kernel zImage and initrd-mini.gz
after that if you've got everything else in place, go ahead and run the compilekaiser script in the tinboot dir and you should have an nbh
if the nbh won't flash (i had this issue) copy the output.nb file, boot into windows, and use nbhutil.exe to convert it to an nbh and flash that one. for some reason yang doesn't work right for me personally
HOW TO CREATE CUSTOM SPLASH SCREENS: (this is a manual by POV)
1. Install HardSPL.
2. Create a BMP file in paint, size must be 240x320, save it as BMP 24bit.
3. Download SplashTool
4. Load your BMP on nb_image_converter (included in SplashTool's zip) and save it as splash.nb
5. Open SplashTool.exe and convert splash.nb to new format.
6. Pack the resulting splash.nb into a NBH file using htc rom tool.
7. Flash your cusotm NBH using CustomRUU.
This will not harm your installed android

WORKING SYSTEMS / ROOTFS'S: ( Collected in the forums)
- http://forum.xda-developers.com/showthread.php?t=587116 ION Donut, reuploaded by 160bpm
- http://forum.xda-developers.com/showthread.php?t=619980 MYNs warm Donut
- http://forum.xda-developers.com/showthread.php?t=619718 Jamezelles Sense Tattoo
- http://forum.xda-developers.com/showthread.php?t=591104 Plemens Donut AOSP
- http://forum.xda-developers.com/showthread.php?t=603028 Jamezelles Sense Hero
- http://forum.xda-developers.com/showthread.php?t=619285 Shidells Android 2.1
rootfs 2010-01-06 works best for me get it here: http://sourceforge.net/projects/androidhtc/files/
Bugs:
NOT WORKING: WiFi, GPS, Voice Call, Bluetooth
(GPS experimental with the files from first post)
Usefull Links:
Android on Sourceforge:
http://sourceforge.net/projects/androidhtc/files/
Android on htc Website:
http://www.androidonhtc.com
dzo's page:
http://it029000.massey.ac.nz/vogue/
Android SDK:
http://developer.android.com/sdk/
Tinboot dev thread:
http://forum.xda-developers.com/showthread.php?t=614275
Thanks:
dzo, plemen, jamezelle, zenulator, enatefox, mssmision, vilord, rzk333, diagdave
SORRY IF I'LL FORGET ANYONE

Here's a couple boot screens I made.

Thanks i'll add this to the first post

Thanks JeckyllHavok, good idea I keep posting over here am not into kernel things anyway

Ok after a few attempts I finally got Android flashed, and running, using my backup kaiser, which has no network connection, so the lack of wifi is a bit of a problem, but seems to be working fine so far, and fast
Just wondering if it would be possible to flash other versions, like eclair or even flan, since polyrhythmic's eclair version seems to be nice and stable, or is this going to fast to soon?

Just tested this with sshidels nexus rom, but itjust ends in bootscreen loops. Maybe other roms work

Looks like in need to learn to read. I found these instructions in the Vouge forum:
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
Click to expand...
Click to collapse

Buried for stupidity. Works great so far.

Flashing now.
1st edit: We have Android .
2nd edit:26 min it just turned itself off ... creepy ... soft reset ....I'll post back results.
3rd:39 min later Actual Phone screen came up No SIM ..Opps rebooted waiting agian.

What is working/not working with this flash.

From what I've read everything except.
Blutooth
wifi
GPS
Still waiting back at ANDROID screen

I have successfully flashed THIS BUILD using the following method:
dzo said:
...create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Click to expand...
Click to collapse
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.

loserskater said:
I have successfully flashed THIS BUILD using the following method:
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.
Click to expand...
Click to collapse
Hi
Can you please send me the files on the sdcard. I am having an issue with every build.
Thanks

Did wifi work with any builds?

I think no, not now

Tilt
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.

Jaguarius said:
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.
Click to expand...
Click to collapse
Are the keys on the slide keyboard working correctly

OK now got two nand flashed kasiers, (both kais130), first using the 'original' flash method, ( dzo nbh, androidinstall.tar), and the other method from the vogue threads, with polyrhythmics Eclair build, which is much slower, ( uses SD card rather than Nand?).
Both seem to be working as well as can be expected at this early stage of Nand flashing.
What I would like to know is how to 'upgrade' our zImage, since some builds have a different zImage version than the one we are currently flashing with, ( I am assuming our zImage is in the NBH flash), since this may help enable wifi/gps which we are presently lacking.

update 18-may dualizer major update: full toolkit(beta)!

major update here, the dualizer has become a feature rich toolkit for dualbooting. this includes a modified version of amon ra's recovery image. you need it to use the dualizer toolkit, it is included and can be flashed with one command.
it is a beta version for now. i have tested each option, but i cannot foresee all conditions you might have on your phone... have a backup at all time! and don't forget to backup the stuff from your sdcard before installing dualboot, during the creation of this toolkit i accidently deleted everything on mine...
there is no logging at the moment, if you get any error messages please paste them here in full.
i haven't tried a nandroid backup at all yet, and wouldn't advice you to do it either. please use apps like titanium backup to backup your stuff. i will be looking into getting some kind of nandroid capability, but that is not a trivial topic. i can however imagine to have full pc-based backup capabilites, sometime in the future...
before you use any of the romX options make sure you have installed the dualboot environment, i have no idea what happens otherwise...
i have tried to include a full description, please let me know if something is unclear (i hope it is obvious that romX needs to be replaced with either rom1 or rom2):
Code:
kendon's dualboot toolkit for the HTC Hero
usage: ./dualizer <option>
place the two roms you want to use for dualbooting in the
rom1 and rom2 subdirectories. make sure directories do
contain other files. you can use the temp/ subdir of the
two rom folders to store your roms while you want to flash
another update.zip
you need a modified version of Amon_Ra's custom recovery image.
it can be installed with this tool, see the options.
options are:
help show this information
vmsetup prepare ubuntu vm for usage
check-dev check if your device is properly attached and connected via adb
boot-rec reboot hero to currently flashed recovery
check-rec check if RA-hero-v1.6.2-DBmod is currently flashed
boot-dbmod put hero in fastboot mode (back+power) first!
fastboot hero with RA-hero-v1.6.2-DBmod
no permanent changes are done, works with unlocked spl only
NOTE: the trackball doesn't select, use green key instead
unlocked-spl copies update.zip for unlocked spl to sdcard, so you can flash it.
if this goes wrong it can brick your phone, make sure you do it right!
flash-dbmod flash RA-hero-v1.6.2-DBmod to recovery partition (permanently)
NOTE: the trackball doesn't select, use green key instead
install-db ALL your data will be lost, so you better have a backup!
install dualboot environment on htc hero
this includes partitioning of the sdcard
place roms in folders rom1 and rom2 first!
romX wipedata wipe data/factory reset romX
romX wipedalvik wipe dalvik-cache for romX
for the following options place update.zip file in folder romX first!
romX flash flashes update.zip from folder romX
romX makeboot create boot.img-update.zip files for romX
romX makeboot push create boot.img-update.zip files for romX and push it to /sdcard
i don't see any potential to brick your phone, even if it fails, as the critical parts (spl, radio) are not touched at all. worst that could happen is that you have to do a full wipe and flash a rom... be careful while flashing recovery and/or bootloader though!
as always: use at own risk!
note: first (and maybe second) boot maybe painfully slow. after that it gets better, see for yourself if it is too slow for you. i have been using villainrom and slidevillain in a dualboot for a few days now, i haven't noticed too much slowdown. then again i don't care too much about this.
credits: huge thx to the ppl in this thread: http://forum.xda-developers.com/showthread.php?t=594077 the information in there helped a lot.
changelog:
v0.2: major update, toolkit for flashing, wiping etc.
v0.1: initial release

installation & usage instructions
please read the first post before you install dualboot!
instructions for windows:
instructions for windows said:
the dualboot install can now set up all necessary stuff in a fresh installed ubuntu virtual machine in virtualbox. you must have adb access to your hero from the windows command line, if you need help check theunlockr.com for their awesome video tutorials.
here is a great howto install virtual box in windows: http://www.psychocats.net/ubuntu/virtualbox
and this is the second part, howto install ubuntu in a virtual machine: http://www.psychocats.net/ubuntu/installing
once you are done installing ubuntu download the archive from the first post and follow these steps (the default download directory is "Downloads", so i'm gonna use that in this example):
- go to "Downloads", you find it in "Places" in the upper menu bar
- rightclick the zipfile you just downloaded and select "Extract Here"
- open a terminal window: goto Applications, Accessoires, Terminal
- execute these commands:
Code:
cd ~/Downloads/dualizer/
chmod +x dualizer
./dualizer setup
it will ask for your password once, then do some stuff and finally reboot the virtual machine.
once rebooted, connect your hero to your pc, rightclick on the usb sign in the lower right corner of the virtual machine window and select the "HTC Android Phone". some hardware installations from windows might pop up (happened to me), just click on next and let them do their stuff. if it doesn't work at first shut down ubuntu, then restart your pc and continue. "reboot tut gut", as the german likes to say
back to ubuntu, with your hero connected to pc and virtualbox, open a terminal and check if your hero is detected by adb with the following commands:
Code:
cd ~/Downloads/dualizer/
./dualizer check-dev
this will tell you if your device is properly connected. you can now continue with the options you can get from
Code:
./dualizer help
Click to expand...
Click to collapse
instructions for linux:
instructions for linux said:
you need java, perl and zip setup, make sure that these are available. then follow these steps:
- extract the attached zipfile from the first post on your pc (for this example i'll assume you extracted it on your desktop).
- get the two roms you want to dualboot, do not extract them.
- put one rom in the rom1 folder, the other rom in the rom2 folder inside the dualizer folder on your desktop.
- open a terminal, cd to the folder and make the main file executable by typing:
Code:
cd ~/Desktop/dualizer
chmod +x dualizer
- turn on your hero (recovery or normal, doesn't matter)
- connect your hero to your pc and check if your hero is detected by adb with the following commands:
Code:
./dualizer check-dev
this will tell you if your device is properly connected. you can now continue with the options you can get from
Code:
./dualizer help
Click to expand...
Click to collapse

reserved...

Holy... this is incredible. Great job on getting this out.

I use a virtual box and ubuntu 10.04 lts.The method seems to work but in step 3 on partition card my hero restarts and boots in recovery and i don't have time to mount the usb/htc device into virtual box so i get in step 5 an no device found error.The time is very short.I have to press USB-MS toggle on my hero and after that i have to mount it in virtual box.I've tried it over 20 times but i don't have time and in terminal get me the error.Is there a way to pause the process or a solution to my problem?
Sorry for my bad english
EDIT:SOLVED.Set the sleep from dualizer in step3 from 15 to 30.Wainting for setup to finish.Cross my fingers
EDIT2: Ok now this is getting awkward.Waiting on step 4 (push to sd) for 25 minutes now.I have checked the log.Last line says mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory.Should I wait for it any longer?Or what should I do now?

As I have said on the VillainROM forum; this is really outstanding work.
Well done, Kendon.

Zero00SM said:
EDIT2: Ok now this is getting awkward.Waiting on step 4 (push to sd) for 25 minutes now.I have checked the log.Last line says mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory.Should I wait for it any longer?Or what should I do now?
Click to expand...
Click to collapse
that shouldn't happen, and the pushing shouldn't take longer than a few minutes. you should cancel it by pressing ctrl-c, if you fancy debugging then check why it wouldn't mount. otherwise you can partition your sdcard, do a full wipe and should be able to flash a regular rom.
i guess i underestimated the complexity of the virtual machine solution, gotta look deeper into this... *sigh*

Hi, regarding the Apps2SD issue... Would it ever be possible for the two ROMs that are dual booting to have the same apps sourced from one place... if that makes any sense...
Like in windows... you can "install for all users" so if you log off and someone else logs in with there account the very same apps are there...
Ok bad analogy since we are talking about dual booting different versions like (Vista & Windows 7) ... but the same data on hdd is accessible...
is this possible with the dual booting scenario?
If I had Slide Villain and Villain 5.5 .. both being 2.1 ROMs which would make app compatibility a non-issue...
If I booted up Villain 5.5 and made changes to an app / save data .. could this not be accessible with the slide rom.. I would hate having to install the very same apps on another partition..worst of all if you have save data (such as a game) and wanted to play it on one of the ROMs your game progress would be different?
you could just use Titanium to transfer over the data but agaqin it is a long procedure.
It would be fantastic if we could mirror image exactly what we have on our main Roms to our "secondary roms" ...

Amazing !
Ciao
Fred

Yeah this is really amazing. I have read this on villainRom forum, and i was stupified .
But, if i want to flash another Rom as primary and need to wipe cache, i need to do this process again! Am i right?

for the shared apps:
a shared apps2sd directoy/partition is possible, although you'd have the problem that apps are installed to one market only, and idk what would happen when you update an app in one rom, would the update get market-linked in the other? you can solve this with titanium backup, but it isn't really comfortable at all. i'll think about this.
for shared data: in theory possible as well, but i don't think it would work out well. you cannot distinguish between system data and apps data that easily, and i don't think it would work to share system data (sense settings etc) between two different roms...
@masterxiter: easiest way to do this is to use the installer script again. you can wipe the cache manually, installing another rom would be really complicated (about as complicated as the installer script )...

Sweet. But is there any way i can run this in cygwin? every version of linux ive tried so far doesnt support my crap compaq wifi card or most things, or even wired for that matter, and running ubuntu in a virtual machine gives a reboot every time after step 1 (maybe cos i suck at terminal)

i'll try some time, but i have never used cygwin... so don't expect anything too soon.

joshman99 said:
Sweet. But is there any way i can run this in cygwin? every version of linux ive tried so far doesnt support my crap compaq wifi card or most things, or even wired for that matter, and running ubuntu in a virtual machine gives a reboot every time after step 1 (maybe cos i suck at terminal)
Click to expand...
Click to collapse
if you install ubuntu in an virtual machine like VMware(paid) or virtualbox(free) you can just use linux, it will automatically grab all your internet settings and stuff from the windows installation(main computer) so your windows will be like some kind of router for your virtual machine with everyhing working.
Very nice tutorial, i'm not going to try it.. because my phone has to be resend to HTC for fixing some dead pixels, there just messers with screens
BTW. you can also try another linux version sounds crazy, maybe try backtrack?? the only thing you need is linux, backtrack is..

I have backtrack 4 (I could never get wifi on that either, but tbh i couldnt work out how to try (that distro is soo confusing imo). I got backtrack 3 to work a while back, so if i can find the disk im gnna try that.
Also virtualbox didnt put my internet settings at all (maybe co im on win7 ultimate?)
Thanks for the suggestions, cos i know cygwin aint the most elegant solution

changing rom 1 and rom 2
i test lotz of roms.... everyday they are being updated...
say if i dualize with ahero0.8 and Kimera 1.7....
wud i be able to update aHero to 0.9 and leave kimera as it is???
simply can i update JUST ONE rom???

manual setup??
i tried it got error in step 3 and then 'Device not found errors...'
can u make a tutorial for doing it manually.....

kendong2 said:
please read the first post before you install dualboot!
instructions for linux:
you need java, perl and zip setup, make sure that these are available. then
Click to expand...
Click to collapse
hihi.. i am trying to do a dual boot, so im wondering what u mean by.. need java , perl and zip setup... can advice me?

He means that you need to have Java, perl and zip installed and configured on your Linux system. If you dont have that installed and configured correctly than the install script wont be able to run.

lolnl said:
He means that you need to have Java, perl and zip installed and configured on your Linux system. If you dont have that installed and configured correctly than the install script wont be able to run.
Click to expand...
Click to collapse
oh noes.. .i do not have those in my ubuntu, does that mean i cant do a dual boot? btw, i saw post 2 and post 3 ... are they the same instruction ? or different? (one for windows user and one for linux?)

[WIP] Ubuntu netbook 10.10 porting

Hi !
I'm actually porting/playing with ubuntu on my Galaxy S. The goal would be to boot ubuntu "natively" from the ubuntu initramfs, but since i was unable to get a working framebuffer output on kernel boot (if someone have a solution for this, it would really help me), i'm using a chrooted environment for now. Some guys already had ubuntu to run on the Galaxy S in a chrooted environment, but the android UI was still running (using a lot of memory) and we had to use VNC to experience the ubuntu desktop. With this version, X is using the s3cfb framebuffer and fbdev driver to draw to the screen. I have also modified a Xorg input driver (plpevtch) to have a preliminary touch screen support. Since we still run it after the android services initializations, ubuntu will use the current connection (wifi, 3G).
If someone want's to play/help/try this stuff, here is the procedure i'v done for now :
Requirements :
- A Linux computer ( tested on ubuntu 10.10 )
- Galaxy S i9000 running an android kernel with ext2 support ( tested with Universal lagfix kernel )
- root (provided with the previous kernel i think)
- busybox (market)
- sdcard 2GB at least, primary partition formated to ext2 (play with the scripts to change to fat or ext4 etc)
- I think that's all
Download :
Download the attached package and extract it, this one contains the required scripts to download/patch ubuntu, prepare the sdcard, and stat/stop ubuntu.
Usage :
create.sh :
usage : create.sh /path/to/my/ext2/sdcard
This script will download the ubuntu netbook 10.10 compressed image for arm, decompress it, mount it then copy the filesystem to a specified path (should be an ext2 formated partition on the sdcard, and be the first partition on the sdcard ( /dev/mmcblkXp1 ).
Should be run first, one time ...
start.sh :
usage : start.sh
This script run "droid_ubuntu_init.sh" on the phone, which stop the android interface, mount the sdcard, prepare the chrooted environment and start a chrooted session (chroot_init.sh, which simulate a "daemon" to allow services to run in the background and start the ubuntu desktop.
Should be run everytime you wants to start ubuntu.
update.sh :
usage : update.sh
At the first "boot", ubuntu desktop (X) will not work, we have to update the distribution. To do so, run "start.sh" (if not already done) to start ubuntu, then run this script. It will update ubuntu (you should really use a wifi connection to do so), and X should then work. It will also install an ssh server. This will take a long time
Should be run one time.
====== Notes =====
If you want to run some "services", you should edit the file "scripts/chroot_init.sh" and add your service here (after the ssh service for example).
The package contains the "patch" applied to the ubuntu rootfs, and the sources of the modified touchscreen xorg input driver.
I did not work on a "stop" script yet, you'll have to reboot the phone if you want the android UI back.
It's really a work in progress, nothing really usable for now.

This is realy cool thumbs up
Il defently start looking at this at first possible time slice.

Download the attached package
Click to expand...
Click to collapse
Hi, where is the script ?
I would love to see Ubuntu running in native mode like it did on my former HD2 (witch, btw, i still think it's the best smartphone ever, Galaxy S - no were near).

mdalacu said:
Hi, where is the script ?
I would love to see Ubuntu running in native mode like it did on my former HD2 (witch, btw, i still think it's the best smartphone ever, Galaxy S - no were near).
Click to expand...
Click to collapse
Won't that be primarily because of the HUGE amount of development for it?

What about trying with a lightweight disto like puppy linux? last one uses lucid lynx package and it can run in ram (so very light).
Also maybe you can make some kind of "boot menu" using recovery mode:
in recovery mode, android is not started so if we add an entry to to recovery to run the start script on the sd from there it should be what you are looking for.

The only big problem i see for me to port ubuntu or anything else natively is a way to debug the boot process. Unfortunately, i was unable to get the kernel framebuffer to work, i would really need some help on this. For now it work great enough in a chrooted env to port some drivers etc. Anyone ? Else yes i'm using a custom rootfs to debug the kernel/drivers/rootfs.

Let's hope i find the time to try this tonight, while booting from a Ubuntu livecd

Oups, i did forget to attach the files. .. Will do so tomorow.
Has anyone worked on "really" porting another distro, done some work on kernel drivers? Actually it seems the s3cfb framebuffer isnt hardware accelerated using fbdev, preventing screen rotation and such. Any hint?

Hi,
I'm a french poweruser of Ubuntu (Server/Desktop).
May I have your script please?
Thanks,
RolluS

Hi,
I'm a french poweruser of linux
Mais ou sont donc les scripts ?
How is the script ?
Julien_050

Cpasjuste said:
Oups, i did forget to attach the files. .. Will do so tomorow
Click to expand...
Click to collapse
Posting the script might generate more interest.

When the files are up, i will try it thx.
koe1974 said:
Posting the script might generate more interest.
Click to expand...
Click to collapse
+1

hi, i was almost at goal, but when starting X-session, it unmounts my sd card... any ideas?

Right when it starts?
Maybe some x app is taking over the sdcard.. just an idea

NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

THIS IS FOR TESTING ONLY. DO NOT ATTEMPT TO INSTALL THIS IF YOU DON'T KNOW HOW TO GET INTO BOOTLOADER MODE AND FLASH A ROM FROM THE SD CARD.
Announcements​
We are currently replacing Tinboot with LK for boot. This will give us fastboot and many other enhancements and fixes to make our device more like a native Android device. This has already fixed some issues with GSM phones, sleep modes, and a few other things. The current issue being worked on is the power button not working (possible GPIO issue).
Introduction​
This thread tracks the most recent NAND development. A huge thanks to [ACL] and WoZZeR999 for dedicating time to NAND development for us, and again, thanks to Jonpry, PHH, stinebd, and the rest of #htc-linux for their contributions. It's truly amazing what these guys have done for us, so be sure to show them your appreciation :wink:
The original NAND boot testing thread can be found here:
http://forum.ppcgeeks.com/tp2-andro...und-test-7-single-nbh-serialno-tilt2-fix.html
File Repository​
Autobuild files can be found here: Index of /files/
The LK directory will contain the latest LK Bootloader and boot image code.
The rhodium_nand directory contains the latest kernels
The XDAndroid directory contains the latest OS files and updates (including the root update)
Note: We often disable autobuild when extremely experimental code is submitted, so this may not always be up to date but should be more stable than content we post in the threads.
Latest Files
LK Bootloader: http://htcdevs.wirelesstcp.net/files/LK/RHODIMG_NORECOVERY.NBH
Recovery Image: http://htcdevs.wirelesstcp.net/files/LK/recovery.img
05-22 Kernel: http://htcdevs.wirelesstcp.net/files/rhodium_nand/20110522_175721-kernel-update.zip
FRX06 OS Files: http://htcdevs.wirelesstcp.net/files/xdandroid/FRX6/update.zip
Optional - FRX06 Root: http://htcdevs.wirelesstcp.net/files/xdandroid/opt_updates/Root-Update.zip
Installation Procedure​
Obtain Install Files
You need 4 files to get NAND up and running:
LK Bootloader NBH
Recovery.img
Kernel
OS Files
Install Directions
1) Set up your computer to use fastboot: http://forum.xda-developers.com/showthread.php?t=532719
2) Flash your phone with the LK Bootloader NBH
3) Copy recovery.img to your fastboot/adb folder
4) Open bash/command prompt and run fastboot flash recovery recovery.img
5) If successful, type fastboot reboot, and hold the Power Button as your phone boots
6) Your phone should boot into recovery, and there you can apply the various update.zip files in this order:
- FRX06 Update.zip
- Kernel-Update.zip
- Root-Update.zip
To navigate in recovery, use volume up/down (or up/down on keyboard) to change selection, then use End Call key (or Enter on keyboard) to make a selection.
Here's a video from ACL
http://www.youtube.com/watch?v=4r4o2CCKwvU
Work in Progress
Panel init/power down
No data on first boot
Youtube app has issues
GSM can boot with no rild arguments (no data)
Not Working at all
Camera
No bluetooth
No 3.5mm headphone jack​

Frequently Asked Questions
What is NAND booting?
NAND booting uses code on the NAND to boot directly into Android without having Windows Mobile on the device. Currently, zImage and initrd.gz are stored on the internal NAND while the modules, rootfs, ext2, and data are stored on the SD card.
How do I setup NAND boot?
First, you need to download the Update Utility (CustomRUU) and the latest package. Extract the NBH to the same folder as the Update Utility and flash like you would a custom ROM. Put the included modules on the SD card (modules must be from the same package as the NBH) along with the modified rootfs.img (see first post) and system.ext2 from http://xdandroid.com/wiki/Main_Page (you can use system.ext2 from BLAZN, but XDAndroid will be better for testing)
Why don't my changes to Startup.txt work/How do I change boot options?
Because we are booting without Haret, Startup.txt is not used. Any changes to Startup.txt will have no effect. If there is a boot option you need enabled, you can either compile a new tinboot with those changes or let me know and I can compile one for you.
Where are the Android files stored and how do I update them?
Modules, rootfs.img, and system.ext2 must be stored under /andboot on the SD card. Every update will require flashing a new NBH (contains zImage) and replace the old modules file with the new one. Sometimes deleting the data.img file is necessary between builds if you experience major problems.
Wifi or other devices aren't working after an update...
The modules and zImage are a pair and must always be updated together. If you only flash the NBH but don't replace the modules file on the SD card, you will get a mismatch on the modules preventing the drivers from loading.
My battery drained and now my phone is stuck in a boot cycle! AHHHHHH!
Don't worry about it. You have two quick and easy options. First, unplug the USB cable, then remove the battery, then put the battery back in, and plug the USB cable back in. Now let it charge for 5 minutes, then turn it on, and you should be good to go. If it still does not work, unplug the USB cable, then remove the battery, then put the battery back in, attempt to enter bootloader mode and plug the USB cable back in as soon as the bootloader screen comes up. Now you can charge it for 5 minutes and restart back into Android (where you should continue charging).
Project Status
What is currently being worked on?
Battery life (up to about 9 hours now)
Backlight control (Dimming works and backlight can be turned off, but re-initializing is causing issues)
What is working?
Phone
Data
Sound
GPS
Keyboard
Wifi
Hardware 3d
What is NOT working?
Camera
Bluetooth
3.5mm headphone jack

Heh, only a matter of time before this thread made it over onto XDA. Thanks Nate

testing
has anybody here tested yet and if so... please note the outcome of the testing i would like to test but i would need more elaborate install instructions so that it is done right the first time ...also a couple of links are not working

ksper6986 said:
has anybody here tested yet and if so... please note the outcome of the testing i would like to test but i would need more elaborate install instructions so that it is done right the first time ...also a couple of links are not working
Click to expand...
Click to collapse
Thanks for the heads up. The copy/paste from PPCG killed some of the links. They should be working now
And this does work great. You can find the thread over at PPCGeeks here: http://forum.ppcgeeks.com/tp2-andro...esting-12-11-panel-power-off-now-working.html

First of all i want to thank all devs who are involved in the NAND Booting Section. I think i will test this in the next days but i must ask some questions first to do it .
1. So, do i need to do the Task 29 or is it just in case of problems.
2. Am i able to flash WinMob back if i'm failing?

yes u can go back to windows. infortunately i have been following all the steps correctly and it loads up the with letters showing its working and then i get a black screen so i think im stuck at boot any help. can someone tell me what im doing wrong. the files are in sd card/ andboot

Bieka said:
First of all i want to thank all devs who are involved in the NAND Booting Section. I think i will test this in the next days but i must ask some questions first to do it .
1. So, do i need to do the Task 29 or is it just in case of problems.
2. Am i able to flash WinMob back if i'm failing?
Click to expand...
Click to collapse
Task29 is just recommended to make sure everything is nice and clean. It makes troubleshooting much easier because it ensures nothing weird is being read from the internal nand.
You can easily flash back to WinMo by starting the phone in bootloader mode and flashing. Unfortunately, you will not be able to do the ActiveSync connection through USB and flash that way.
kabu said:
yes u can go back to windows. infortunately i have been following all the steps correctly and it loads up the with letters showing its working and then i get a black screen so i think im stuck at boot any help. can someone tell me what im doing wrong. the files are in sd card/ andboot
Click to expand...
Click to collapse
You should have three files in /sdcard/andboot: rootfs.img, system.ext2, and modules (don't rename the modules). Now flash the NBH and it should generate the data.img, and you should be good to go. It should be loaded in under 10 minutes, so if it isn't, I would check the contents of the memory card. Also note the card must be FAT32 formatted and have not be partitioned.
The panel power on/down is apparently fixed for some panels but not others. ACL and bzo have been working together on this and found that there are several different panels being used in our phones, and ACL is working on a patch to fix up the panels that aren't functioning perfectly.

mcnutty said:
RootFS
A custom rootfs.img is required to automatically configure the keyboard. You can override the automatic keyboard by creating a .kb file in your andboot folder. Accepted inputs are: rhod500.kb, rhod400.kb, rhod210.kb, and tilt2.kb
Click to expand...
Click to collapse
What about the rhod100? I have a modified rootfs.img for correct german keylayout in haret version of xdandroid. Can i use that too or do i need to delete all other .kb's? And is it even possible to get a working rhod100 keyboard? I know many questions but i think this should be BEFORE i get lost .

Bieka said:
What about the rhod100? I have a modified rootfs.img for correct german keylayout in haret version of xdandroid. Can i use that too or do i need to delete all other .kb's? And is it even possible to get a working rhod100 keyboard? I know many questions but i think this should be BEFORE i get lost .
Click to expand...
Click to collapse
Ahh yess the custom keyboard and how to create it. This threw me for a bit too and when i realized that all I had to do was open up notepad and then do a saveas rhod400.kb, I laughed at myself.
yep that easy a blank text file with the correct name and you are good to go

Well now that the thread is over on xda I tried again but still to no avail even tried two different SD cards both end with it booting but freezing at SMD: ch 0 OPENING -> OPENED. Pretty sure I have everything setup correctly three files in andboot folder on sdcard renamed rootfs to just rootfs.img but left the other two files. By the way this is on a tilt2.

Thordim said:
Ahh yess the custom keyboard and how to create it. This threw me for a bit too and when i realized that all I had to do was open up notepad and then do a saveas rhod400.kb, I laughed at myself.
yep that easy a blank text file with the correct name and you are good to go
Click to expand...
Click to collapse
Does that mean i just had to rename my rhod100_de.kb file to a rhod400 or something? That would be TO Easy ... ok i always think around corners ))

Bieka said:
Does that mean i just had to rename my rhod100_de.kb file to a rhod400 or something? That would be TO Easy ... ok i always think around corners ))
Click to expand...
Click to collapse
Actually, I didn't account for the non-US variants when creating the rootfs. I have some other modifications that I'm testing for the rootfs at the moment, so I will be sure to add the other variants back in for at least the KB overrides. I will need help with a variable for the automatic detection to work properly.
If anyone has any of the non-US variants, it would be extremely helpful for you to flash to NAND, hook up to ADB, and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is.

wifi
i want to start off by saying this is an amazing project.
But my problem is that wifi is not working for me. When i try to start wifi, it immediately says "error." I have done many flashes and used task29. i was just wondering if anyone else had this issue.

mcnutty said:
Actually, I didn't account for the non-US variants when creating the rootfs. I have some other modifications that I'm testing for the rootfs at the moment, so I will be sure to add the other variants back in for at least the KB overrides. I will need help with a variable for the automatic detection to work properly.
If anyone has any of the non-US variants, it would be extremely helpful for you to flash to NAND, hook up to ADB, and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is.
Click to expand...
Click to collapse
I will do that for you in the next days. Before Christmas it's a turbulent time for me. As soon as i can get the Time for it i will flash to nand and follow your instructions. If i need help, can i PM you?
Cheers

I'm using Neopeek's rom instead..how can i set it up? since this rom doesnt use the system.ext2 file

getting calibration without visible points to touch aka the boxes. also, boot ani glitches out on screen with a "solid" animation, and video glitchs on the bottom half of the screen. sits here indefinately.... still waiting..... haha
update: loads to lockscreen, so far can't get screen to stay on??? strange
update2: got it working, but keeps turning screen off immediately... any ideas>?

hmm, i have been trying this and i feel like i have everything right
tilt2.kb, rootfs.img, modules, and system.ext in an andboot folder in my storage card and then, a nbh with the same name as the module in a folder with customRUU.exe. I flash and then it gets to the linux boot screen, after a couple lines go by, the screen fades out and dies and restarts. My battery says 88 percent when i flash back to windows, anybody know what could be going wrong?

HTC Sense
will it only recognize only an ext2 or will it recognize squashfs.

blitzer320 said:
Well now that the thread is over on xda I tried again but still to no avail even tried two different SD cards both end with it booting but freezing at SMD: ch 0 OPENING -> OPENED. Pretty sure I have everything setup correctly three files in andboot folder on sdcard renamed rootfs to just rootfs.img but left the other two files. By the way this is on a tilt2.
Click to expand...
Click to collapse
I'm on the rhod210 (T-Mobile), and I've been having this exact issue. Any ideas?
btw, this is my first post here, but I've been reading and following this project for quite a long time. You guys are great! Thanks for all the work you do!

Arch Linux for Shield TV

I present to you instructions on how to get Arch Linux working natively on your shield TV dual booted with your Android rom. This is all thanks to the amazing people in this thread for getting Ubuntu on the shield and would not be possible without them.
http://forum.xda-developers.com/shield-tv/general/ubuntu-utopic-nvidia-shield-tv-t3150352
This install will put arch Linux on a micro SD card, and does not modify your shield at all if you so choose. First download these 2 files.
Archlinux Stage 3 install
http://archlinuxarm.org/os/ArchLinuxARM-aarch64-generic-latest.tar.gz
Kernel (Credits to jagger11 from his thread) You only need nvidia_boot.img
https://drive.google.com/folderview...ZSS1VxUVBJZmFqSXNFYUhpN2lHcklhVzZtX0Z5OENxdU0
To intstall
1. Unlock your shield TV
2. Format your SD card to EXT4
3. Mount the SD card
4. As the root user on your linux distro (not sudo) run this command (From the same directory that you downloaded that file to, and replacing mountpoint to where you mounted the SD to)
bsdtar -xpf ArchLinuxARM-aarch64-generic-latest.tar.gz -C mountpoint
5. Unmount the drive, then run the command "sync". When that finishes, pull the SD card from the computer.
6. Put the SD in the shield
7. Reboot to bootloader (adb reboot fastboot) with your preferred method
8. Boot Linux
To boot it once run this
a) fastboot boot nvidia_boot.img
To save to recovery run this (Reboot android to recovery to boot arch after)
b) fastboot flash recovery nvidia_boot.img
Default users and passwords are
root:root
alarm:alarm
For more information, check this page.
http://archlinuxarm.org/platforms/armv8/generic
Tested Working
*Ethernet
*USB
*TTY Terminals
*Framebuffer (Install X11 as usual and xf86-video-fbdev)
Untested
*WIFI (Should work)
*Bluetooth (Probably doesn't work)
Broken
*3D acceleration (Will work on this in the future)
*You tell me
*Sometimes does not boot after a few working boots (I think it's a problem with my SD, or my android install messing with it. Working that out now, but please report if you have this issue only after it boots fine at least once)
My request to you. I am not a kernel dev any more. I once was, but things have unfortunately changed, and I don't have the time or resources to learn it all again. If anyone wants to develop a kernel for this, please do and I'll add it in the OP. Unless something changes, and Ubuntu kernel from the Utopic thread will work fine here)
I'll format this a bit better later, but hopefully this is a good start. I have some good tips and tricks to add if people are interested in this, and was able to watch quite a lot of my videos in vlc even on framebuffer. Please give me some feedback on what you want to see, and ask any questions. I'll be glad to help!

kdb424 said:
I present to you instructions on how to get Arch Linux working natively on your shield TV dual booted with your Android rom. This is all thanks to the amazing people in this thread for getting Ubuntu on the shield and would not be possible without them.
http://forum.xda-developers.com/shield-tv/general/ubuntu-utopic-nvidia-shield-tv-t3150352
This install will put arch Linux on a micro SD card, and does not modify your shield at all if you so choose. First download these 2 files.
Archlinux Stage 3 install
http://archlinuxarm.org/os/ArchLinuxARM-aarch64-generic-latest.tar.gz
Kernel (Credits to jagger11 from his thread) You only need nvidia_boot.img
https://drive.google.com/folderview...ZSS1VxUVBJZmFqSXNFYUhpN2lHcklhVzZtX0Z5OENxdU0
To intstall
1. Unlock your shield TV
2. Format your SD card to EXT4
3. Mount the SD card
4. As the root user on your linux distro (not sudo) run this command (From the same directory that you downloaded that file to, and replacing mountpoint to where you mounted the SD to)
bsdtar -xpf ArchLinuxARM-aarch64-generic-latest.tar.gz -C mountpoint
5. Unmount the drive, then run the command "sync". When that finishes, pull the SD card from the computer.
6. Put the SD in the shield
7. Reboot to bootloader (adb reboot fastboot) with your preferred method
8. Boot Linux
To boot it once run this
a) fastboot boot nvidia_boot.img
To save to recovery run this (Reboot android to recovery to boot arch after)
b) fastboot flash recovery nvidia_boot.img
Default users and passwords are
root:root
alarm:alarm
For more information, check this page.
http://archlinuxarm.org/platforms/armv8/generic
Tested Working
*Ethernet
*USB
*TTY Terminals
*Framebuffer (Install X11 as usual and xf86-video-fbdev)
Untested
*WIFI (Should work)
*Bluetooth (Probably doesn't work)
Broken
*3D acceleration (Will work on this in the future)
*You tell me
*Sometimes does not boot after a few working boots (I think it's a problem with my SD, or my android install messing with it. Working that out now, but please report if you have this issue only after it boots fine at least once)
My request to you. I am not a kernel dev any more. I once was, but things have unfortunately changed, and I don't have the time or resources to learn it all again. If anyone wants to develop a kernel for this, please do and I'll add it in the OP. Unless something changes, and Ubuntu kernel from the Utopic thread will work fine here)
I'll format this a bit better later, but hopefully this is a good start. I have some good tips and tricks to add if people are interested in this, and was able to watch quite a lot of my videos in vlc even on framebuffer. Please give me some feedback on what you want to see, and ask any questions. I'll be glad to help!
Click to expand...
Click to collapse
Thanks for the new thread. You are correct that the "nvidia_boot.img" from jagger11 can boot to archLinux but the kernel I built can't.
I have always been using Ubuntu with desktop enabled by default. How did you install X11 under archLinux?

yahoo2016 said:
Thanks for the new thread. You are correct that the "nvidia_boot.img" from jagger11 can boot to archLinux but the kernel I built can't.
I have always been using Ubuntu with desktop enabled by default. How did you install X11 under archLinux?
Click to expand...
Click to collapse
Following the standard guide on their wiki.
I installed
xorg-server
xorg-server-utils
xorg-init
xf86-video-fb
And then just the standard startx after setting my xinitrc to the usual. In my case I used awesome WM, though you can use any, and exec that in your .xinitrc file

kdb424 said:
Following the standard guide on their wiki.
I installed
xorg-server
xorg-server-utils
xorg-init
xf86-video-fb
And then just the standard startx after setting my xinitrc to the usual. In my case I used awesome WM, though you can use any, and exec that in your .xinitrc file
Click to expand...
Click to collapse
I have to admit I was spoiled by Ubuntu which installs everything by default. I have to read archLinux wiki and try them tomorrow morning.

yahoo2016 said:
I have to admit I was spoiled by Ubuntu which installs everything by default. I have to read archLinux wiki and try them tomorrow morning.
Click to expand...
Click to collapse
Those packages will do you other than desktop manager, but I have to say, I'm pretty minimalist, and arch is by default, so don' feel too bad. I've just been using arch for the last few years, and was using Gentoo before that, which is all even more manual and source built.
https://wiki.archlinux.org/index.php/Xorg
That page will go through it all. Once you know what desktop manager you want (I recommend XFCE if you don't know what, or LXDE which is even lighter), check the pages out on there for them. It covers haw to do absolutely everything. I honestly use arch linux for the wiki. It's by far the best source of linux information on the net I'd be willing to bet.

kdb424 said:
Those packages will do you other than desktop manager, but I have to say, I'm pretty minimalist, and arch is by default, so don' feel too bad. I've just been using arch for the last few years, and was using Gentoo before that, which is all even more manual and source built.
https://wiki.archlinux.org/index.php/Xorg
That page will go through it all. Once you know what desktop manager you want (I recommend XFCE if you don't know what, or LXDE which is even lighter), check the pages out on there for them. It covers haw to do absolutely everything. I honestly use arch linux for the wiki. It's by far the best source of linux information on the net I'd be willing to bet.
Click to expand...
Click to collapse
What display driver should I install?
The wiki starts with
lspci | grep -e VGA -e 3D
But lspci does not work for shield TV.

yahoo2016 said:
What display driver should I install?
The wiki starts with
lspci | grep -e VGA -e 3D
But lspci does not work for shield TV.
Click to expand...
Click to collapse
xf86-video-fbdev works for me. Since we don't have access to the GPU directly, we are using the framebuffer at the moment.

kdb424 said:
xf86-video-fbdev works for me. Since we don't have access to the GPU directly, we are using the framebuffer at the moment.
Click to expand...
Click to collapse
That confused me since I thought xf86 meant x86 but Shield has Arm CPUs.

yahoo2016 said:
That confused me since I thought xf86 meant x86 but Shield has Arm CPUs.
Click to expand...
Click to collapse
Yeah, it's actually got nothing to do with architecture. Not quite sure why they are named as such. Also, xf86-video-fbdev isn't listed there as it's a last resort kinda thing, but it works well on the shield for the moment. Once I figure out why my system stops booting linux from time to time, I'll work on GPU drivers. Hard to know what broke it if I don't fix that first.

kdb424 said:
Yeah, it's actually got nothing to do with architecture. Not quite sure why they are named as such. Also, xf86-video-fbdev isn't listed there as it's a last resort kinda thing, but it works well on the shield for the moment. Once I figure out why my system stops booting linux from time to time, I'll work on GPU drivers. Hard to know what broke it if I don't fix that first.
Click to expand...
Click to collapse
You may want to have a look at this: https://github.com/NVIDIA/tegra-nouveau-rootfs
Arch Linux is the target rootfs and the Jetson TX1 is supported. Now the questions is how to get a mainline kernel running on shield tv. I guess one issue is the device tree which will not be provided by uboot like on normal arm systems. In the kernel configuration you can define that the device tree is appended to the kernel image (e.g. by "cat Image foster.dtb > newImage"). Maybe this is a solution.

Thanks_Meter said:
You may want to have a look at this: https://github.com/NVIDIA/tegra-nouveau-rootfs
Arch Linux is the target rootfs and the Jetson TX1 is supported. Now the questions is how to get a mainline kernel running on shield tv. I guess one issue is the device tree which will not be provided by uboot like on normal arm systems. In the kernel configuration you can define that the device tree is appended to the kernel image (e.g. by "cat Image foster.dtb > newImage"). Maybe this is a solution.
Click to expand...
Click to collapse
Thanks for the info. I'm going to have the next 2 days off work, so I'll definately get to work. I'm going to need assistance in getting a working kernel as I don't have an x86 machine around currently. Crazy, I know, but I don't. I'll see if I can get the drivers installed if someone works on a kernel. If not, I'll contact some of my linux friends and see what they come up with.

kdb424 said:
Thanks for the info. I'm going to have the next 2 days off work, so I'll definately get to work. I'm going to need assistance in getting a working kernel as I don't have an x86 machine around currently. Crazy, I know, but I don't. I'll see if I can get the drivers installed if someone works on a kernel. If not, I'll contact some of my linux friends and see what they come up with.
Click to expand...
Click to collapse
That link mentioned:
"The first prerequisite is that you must use an up-to-date U-Boot as bootloader"
Jetson TK1 and TX1 uses U-boot, Shield TV however uses fastboot not U-boot and the kernel is not Linux but Android.
I'd really like someone can have u-boot ported to Shield TV as 2nd or 3rd stage boot loader.

Damn! I just found out that this CONFIG_ARM_APPENDED_DTB trick only works with zImage but not with Image as needed for abootimg. Currently I don't have an idea how to get a mainline kernel running on the shield tv. I guess uboot makes no sense since we don't have an uart.

Thanks_Meter said:
Damn! I just found out that this CONFIG_ARM_APPENDED_DTB trick only works with zImage but not with Image as needed for abootimg. Currently I don't have an idea how to get a mainline kernel running on the shield tv. I guess uboot makes no sense since we don't have an uart.
Click to expand...
Click to collapse
u-boot could use netconsole:
http://forum.doozan.com/read.php?3,14,14
---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------
My kernel can boot to command line archLinux now, I updated the procedure:
http://forum.xda-developers.com/showpost.php?p=64330336&postcount=147

I'll try that kernel when get home with the gui running on framebuffer. Should work.

kdb424 said:
I'll try that kernel when get home with the gui running on framebuffer. Should work.
Click to expand...
Click to collapse
I uploaded my latest kernel tested with command line archLinux:
https://drive.google.com/file/d/0Bz5kaPQJx_AgUklNekxGeWFuNW8/view

yahoo2016 said:
I uploaded my latest kernel tested with command line archLinux:
https://drive.google.com/file/d/0Bz5kaPQJx_AgUklNekxGeWFuNW8/view
Click to expand...
Click to collapse
Any chance you can maybe try to patch in the Nouveau kernel driver from here?
With a kernel running that I can get 3D acceleration work started. Till I get that sorted out I can only guess if my changes are working or not.
I'll also be trying to get the closed source binaries running on this. I have decided to pay a decent sum of money for a VPS to get a compile machine. Hopefully we can get this project rolling.

kdb424 said:
Any chance you can maybe try to patch in the Nouveau kernel driver from here?
With a kernel running that I can get 3D acceleration work started. Till I get that sorted out I can only guess if my changes are working or not.
I'll also be trying to get the closed source binaries running on this. I have decided to pay a decent sum of money for a VPS to get a compile machine. Hopefully we can get this project rolling.
Click to expand...
Click to collapse
I did not expect it'd take me so long just to have gui running for archLinux. As I mentioned before this thread started, I'd like to try Cuda 7.0 on ArchLinux. I main goal is to have Cuda working so I can use Gpgpu of Tegra for image processing and other applications.
A script or procedure for post installation to quickly install gui is what I was interested. To install archlinux rootfs without gui was very simple and I did it the first day when I received my Shield TV to troubleshoot Utopic rootfs. I could read the wiki to have gui working for archLinux, but I have to spend my time on other things, e.g., without hope to have u-boot or multirom working for Shield TV, I have to learn Android kernel (I'm in the process of clone Android kernel source tree).

I'll write a script for you once I get home. Thanks for the input. Any requests for a desktop environment or window manager? If not I'll just pick a light one like lxde.

kdb424 said:
I'll write a script for you once I get home. Thanks for the input. Any requests for a desktop environment or window manager? If not I'll just pick a light one like lxde.
Click to expand...
Click to collapse
Any desktop is fine. I'd like to push Cuda 7.0 from my build PC to archLinux like I did for L4T. Network connection and any desktop are what I need. If it works, we can see performance differences between 32 bits and 64 bits
Thanks.