[android] NAND flashale android !!USER!! Questions UPDATED MANY HOW TO'S - Tilt, TyTN II, MDA Vario III Android Development

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.

Related

system.img Download?

So I am trying to follow the instructions found on the wiki (I'd like to it but the forums are preventing me from posting URLs at the moment) for installing Android on my HTC AT&T Tilt device and I was wondering, where do I download the system.img for Android from? I've been searching around online and cannot find it anywhere...
Many Thanks,
~Jeff
www.androidonhtc.com should have everything for your device
more specifically http://www.androidonhtc.com/wiki/Latest_Builds_(Kaiser) for kaiser http://www.androidonhtc.com/wiki/Latest_Builds_(Polaris) for polaris and http://www.androidonhtc.com/wiki/Latest_Builds_(Vogue) for vogue
R3TR3C said:
should have everything for your device
Click to expand...
Click to collapse
Thanks, I had downloaded the files from that page. It was just confusing because the step by step reads like you need to download a system.img from somewhere when this file in generated when you install Android. Got it loading... Now on to figuring out why it won't boot!
~Jeff
JeffHoogland said:
Thanks, I had downloaded the files from that page. It was just confusing because the step by step reads like you need to download a system.img from somewhere when this file in generated when you install Android. Got it loading... Now on to figuring out why it won't boot!
~Jeff
Click to expand...
Click to collapse
What do you mean when you say "won't boot"? Does your phone show the Linux logo and rolling text, does it show a boot logo animation. Give us some hints and we'll try and sort this out for you.
edit: I see you started another thread, I guess you are working out your issues in that one instead.
binlabin said:
edit: I see you started another thread, I guess you are working out your issues in that one instead.
Click to expand...
Click to collapse
Yea, sorry. One issue for one thread. Keeps things more organized.
~Jeff
linux logo and scolling txt
well, i will hijack her thread since i am at that point.
i did follow the wiki and downloaded the files for the kaiser. i looked at the files and noticed a zimage but no system img file. do i need to compile the package on my linux box then put it on the sd card to run the haret file?
System.IMG/SQSH is deprecated. Use a androidinstall.tar build such as myn warm android. Everything there work including BT and camera.
As thebulletfromhell said, the system.img/sqsh file method of installing Android is now very outdated, and the more mature builds are using the Androidinstall.tar method, this method has several advantages, a menu driven installer, easier updating, greater stability, less problems caused by mis-matched rootfs/system/zimage files.
The two main builds at the moment are; Myns Warm Donut : http://forum.xda-developers.com/showthread.php?t=619980
And Polyrhythmics Eclair 2.1 : http://forum.xda-developers.com/showthread.php?t=600154
Both of these are probably the best supported and most widely used ports to Kaiser hardware.
There are other builds of course, but as a newer user of android I'd recommend these two first.
Hello. I had some troubles running Android on my HTC TyTN II.
The system boots but I see on the console an error message saying "can't find system.img" or something similar.
I downloaded the latest versions of everything but androidinstall.tar is not enough.
i have same problem
Its due to the kernel's Sys & Data boot parameters. Just use any of the newer kernels which carry support for both NAND and SD

[Q] [Request] Can anyone make new andboot

Hi all,
I can't figure it myself, Can anyone from the experts here compile a andboot folder with latest initrd, kernel & Haret, so noobs like me run Android on their Kaiser from SD without deleting original WM.
many thanks in advance,
a) That's really really lazy man!
b) Not every kaiser has the same configurations (panel type, key mapping, etc)
c) Not all the users would like the same build
d) That's really really lazy! (again)
Try this guide: its noobs-proof and I assure you than in less than 15 mins ul be running android on ur kaiser:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret
What OS does this guide use? OSX.
what about Windows based PCs? like the one I have?
Is still possible to compile Andriod on Windows? I know the answer OF COURSE NOT.
Alberto, Not everyone see it easy as you did. If you want to help, give a hand. if not thanks.
yassermekled said:
What OS does this guide use? OSX.
what about Windows based PCs? like the one I have?
Is still possible to compile Andriod on Windows? I know the answer OF COURSE NOT.
Alberto, Not everyone see it easy as you did. If you want to help, give a hand. if not thanks.
Click to expand...
Click to collapse
LOL no man! that's why we are here right? to find answer to all our doubts... some months ago I had no idea bout android!! Now im a little more "versed" in this matters but compared to a lot of ppl here i find myself as a noob! But its not that complicated ull see:
First download Haret latest ver:
http://it029000.massey.ac.nz/vogue/files/
download haret-for-kernel-2-6-32.exe file
ull copy it to your SD later...
also look at the forum and search for a build, an example can be this one, its a donut build and i have found it really stable under NAND installation:
http://forum.xda-developers.com/showthread.php?t=796193
its not the latest version of android (froyo) but ull find it easy and reliable, you can try a froyo build too but be carefull, not all builds are made to run in haret.
then download python (needed to run atools, no need of OS X )
http://www.python.org/download/
please be sure to download only the 2.6 or 2.7 version
install it
Downoad version 1.04 of atools from here:
http://sourceforge.net/projects/androidhtc/files/AtoolsRelease/
look for atools-1.0.4.py
Run it
Follow the guide I provided you before,
1. Select haret on the button "D"
2. under device select kaiser
3. select the resolution u prefer, 240 is the native res for our kaisers, but you could try the other ones..
4. select wich version you will install, in my example you would select donut, but you should try different builds and keep the one you prefer.
5. the panel type... well this is a little complicated, kaisers have diferent types of screens and there's no accurate way to now wich panel type u have unless you try out! so basically ull have to try each one of the types (1, 2 or 3) if you see strange colors, or black dots in the screen, ull have to reflash the kernel so lets start with the panel 1, you could try to use the auto option but im not totally sure it would work...
6. key map: if you have a unbranded TyTn II (not the AT&T tilt) select normal, if u got the tilt select this option or one of the other special key mappings
7. ill recomend u to leave all the rest of options unchecked for the first time, but if you want to give it a shot, try reading the guide i posted before.
8. save the file with the diskette button
Format your SD with FAT32, create a folder named andboot
copy the file previously made to it,
copy haret to it too.
download the latest zImage with the world button, save it to the andboot folder.
download latest initrd from the button with a box and an arrow, again copy it to the andboot folder.
lastly copy the androidinstall.tar (could be .tgz too dont worry) of the build u prefer to the andboot folder
insert the SD to your phone, run winmo, go to the file browser, search the andboot folder, run haret, press run, the phone will reboot, and ull se a pretty lil penguin and a lot of text scrolling down, put attention and press d-pad (silver center button) when the system prompts u to do so, select install system and wait for it to return to the main menu, select quit, and voila! remember if you find issues on the display, go back to atools and make another default.txt but this time with panel 2, or panel 3 type.
this is not as good as the guide l1qu1d made, i wrote this in 5 mins, he probably spent a lot more time writing it and testing it, i really suggest you to read that guide before trying anything, m not responsible of anything going wrong, actually the worst thing that could happen is u to NOT run android , thats why i suggested it on my post....
Thank you for this guide, i personaly found the original very hard to understand. I have spent an entire day trying to get android on my phone but to now avail. I did managed to get super froyo on for about 5 mins before it white screened on me and froze. It was also very slow. All other attempts didn't get past the linux screen. I'll keep persevering though!

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!

[HaRET] hx4700 linux development - ubuntu image available

Soft chewy center
Here are instructions and downloads that will have you on your way in no time, to running Linux on an IPAQ hx4700.
Step 1: Download a disk image
Ubuntu light weight X desktop download
Android download currently this barely boots
Step 2: Uncompress the file
See p7zip link
Step 3a: Copy the image to a CF or SD card using Linux
Open a terminal and navigate to the directory where you extracted the img file.
Code:
cd somedirectory
Copy the image to the card using dd
Code:
sudo dd if=image-name.img of=/dev/sdx
Where x is the destination of your card. Note there is no partition number "i.e. /dev/hda1" Just the destination letter /dev/hda
Step 3b: Copy the image to a CF or SD card using Windows
Code:
stub
Step 4: Edit startup.txt if you are using a SD card
Code:
stub
Step 5: Run HaRET
Safely remove the card from your computer, insert it in to your hx4700 navigate to the card directory using the file manager then click on haret.exe
Hard crunchy shell
Stuff for the masochist that lives inside you.
Kernel 2.6.21-hh20
Found the source tarball for 2.26.21-hh20 on this link.
I found an android patch for 2.6.21 at this link.
Finally I hammered out this patch that applies smoothly with no fuzz.
And here is my .config file.
Android usb gadget and the low memory killer currently need some love. But without configuring them the kernel compiles nicely
A-Z build instructions
Code:
stub
HaRET
I use HaRET to boot linux on the hx4700, until that day comes when I have learned enough about the hx4700 to provide a ROM, tinboot isn't really that hard to use.
Also the latest HaRET does not boot the hx4700 maybe it is being built with a newer instruction set, until I get a newer version compiling there is an older version in the .img files that works fine.
stub- haret from source
Filesystems
These xxx.img files should be written to a cf card using dd, or sd card if you change startup.txt and the swap file in /dev/fstab. The card should be no less than 1 GB. Gparted can resize/move your partitions if you have a larger card.
I have to admit I don't have a 1gb card to test the img file on, only a 4 and 2 GB card. If someone who does have one finds out that it doesn't boot or something let me know.
Card image layout:
fat16 16mb [haret] partition 1
ext 880mb [root] partition 2
linux-swap 128mb [swap] partition 3
Creating an Ubuntu file system
Creating a file system to run Linux on the hx4700 via HaRET. Rootstock is a tool the will pull down precompiled packages suitable for various devices, from a server. Then install, unpack, and configure them on a disk image file system inside a virtual machine, all without you leaving the comfort of your x86 compatible environment.
For rootstock I followed this guide link.
I used this command to create the image.
Code:
sudo ./rootstock --fqdn ubuntu --login xda --password xda --imagesize 3G --seed tslib,build-essential,openssh-server,lxde,gdm --dist jaunty
I'm still thinking of including gnome-core simply for more function but lxde will have to do as the session manger. Gnome is just to heavy.
Light weight X download link at top of page
working:
the Mouse pad is configured
all drivers and firmware load
auto login via gdm.conf
/etc/network/interfaces is preconfigured for usb net and stubbed out for wireless.
not working:
touch screen - needs configured
wireless?? - I think only OPEN or WEP is supported ATM.
Android
stub- building the android filesystem
android.img download link located at top of post
now if I could just get the hang of making my forum post... not ugly
Nice! very nice!
Marvelous news, THX man!
...i love you! :']
As soon as I found this thread I smiled like a giddy school girl. My hx4700 might just be useful once again! I know nothing on programming... but i'd be glad to help out in any way possible!
Update folks,
I was up all night slaving away at this but, WE HAVE AN ANDROID PATCHED KERNEL!!! its 2.6.21.hh20 with android patches. This means the drivers should be easier to get worked out.
And Android almost boots, I suspect its the generic "goldfish" file system or some other trivial thing stopping it from booting all the way.
After mounting root and running /init, It shows the message "A N D R O I D_" then freezes well not really freezes the cursor continues to blink. but still almost there...
edit - links added
thanks
thanks a lot it's very usefull
Just seen a boot animation, it just got real people... but still not booting all the way.
keep up the good work...seems that this is the only development going on for my trusty iPaq 4700.......
I just want to say thanks for all the supportive comments. It's a real shot in the arm when I'm feeling over whelmed by the complexities of this. I did something really stupid with "sudo dd" last night and boogered up my root file-system, so I'm spending today re-setting up my build environment
All of the hardware is supported but just not pushed upstream but I’m working on a new 3.0 kernel right now for the universal when I finish I will add the hx4700 patches and post the source and message you. But I know wifi, Bluetooth, touchpad, sound, led, and all buttons work in 3.0. And these are the same on the universal and I have these working with froyo now. But I can post my 2.6.36 kernel I’m using now after I make a few corrections.
Here's my form page link
And this is where some of my code and android builds are: link
The common.tar.gz is my old 2.6.36 kernel I have to make some corrections and fix the hx4700 code I messed up and reload it in a day or so.
--I had to post this here as I got a message that you cannot receive private messages.
Thanks!
Don't know why you got that message, I did get your PM.
Could you make a tutorial, step by step how to run android(haret, etc.) on hx4700, please?
I'm noob in windows mobile tools
im currently running Angstrom on my hx4700
but would love android too..
havent tried any of these images yet. but ill probably have some
spare time this week..
/Kyndal
On tenterhooks ...
It failed to boot (couldn't mount /dev/hda2 I think) when I tried to install and run from a Compact Flash, so I'm in the middle of dd-ing to an SD card instead. Fingers crossed ...
EDIT: It boots fine from the SD card.
However, it's rather sluggish at best, and there don't seem to be many productivity apps -- and no onscreen keyboard. Still, it's a start!
EDIT 2: Attached a small photograph for the curious. Sorry about the blur, but I couldn't manage a better shot, given the lighting and the camera's fudged-up CCD.
kyndal said:
im currently running Angstrom on my hx4700
Click to expand...
Click to collapse
How in the world did you manage that? I've been trying to get Angstrom working on my hx4700 for months now, without success. (Aside from an old bootpack that literally has no useful programs.)
I haven't had much luck with any "new" Angstrom builds from the
narcissus online builder..
Right now. im running an older X11 build
booting from SD card .img file
Functional.. but ya. not up to date..
/Kyndal
kyndal said:
I haven't had much luck with any "new" Angstrom builds from the
narcissus online builder..
Right now. im running an older X11 build
booting from SD card .img file
Functional.. but ya. not up to date..
/Kyndal
Click to expand...
Click to collapse
I would like a copy of this .img file (cleaned of personal stuff, of course). It'd be nice to have a usable Angstrom for a change.
you can try it out with the prebuild images (OLD)
apparently im not allowed to post external links yet...
so go to this address
angstrom-distribution.org/releases/2007.12/images/hx4700/
and download
Angstrom-x11-image-glibc-ipk-2007.12-hx4700.rootfs.img.bz2
Angstrom-boot-2.6.21-hh20-r6-hx4700.exe
extract the .img file from bz2 to a FAT SD card
and place the .exe there too..
run the .exe select the img file. can be a little fiddly on the "touchpad"
"enter" is like in the middle. and half the time moves the cursor up/down
this linux lives in the loop .img file on vfat..
not on partitions. so pretty easy to try..
run these commands to get online with wifi
su
/sbin/modprobe acx
/sbin/modprobe hx4700-acx
/sbin/iwconfig wlan0 essid ACCESSPOINT
/sbin/ifconfig wlan0 up
/Kyndal
kyndal said:
you can try it out with the prebuild images (OLD)
Angstrom-x11-image-glibc-ipk-2007.12-hx4700.rootfs.img.bz2
Angstrom-boot-2.6.21-hh20-r6-hx4700.exe
Click to expand...
Click to collapse
Yeah, I've tried the image before - months ago -- but I didn't know about those commands /sbin! I'll give them a try and see if I can get anything useful installed (the image comes without any useful GUI - or even CLI, for the most part - applications).
EDIT: Unfortunately, even though the package manager seems to be capable of fetching the correct packages (it's hard to tell), it consistently fails to install them -- I even tried installing man and nano (one at a time) and was met with failure even though the URLs check out. (abiword took longer before failure, hence my suspicion it downloads fine).
I apologize for derailing the thread like this, but this is the only place I've found since I got interested in putting Linux on my iPAQ where someone is actually *answering* my questions.
It's ok Strife89, I appreciate you all actively helping out, I was out of town house hunting last week.
Maybe everyone here could come up with a "wish list" request for packages to be installed among other useful things/configuring/etc, so we can all help polish the ubuntu installation, and make it something nice/useful.
As far as android goes, I have more confidence in the kernel than I do the file system, as to where I am right at this moment, donut will boot and show a boot animation. That is as far as I have gotten, but still it is progress.
I look forward to working with anyone interested with helping out, so lets here some thoughts/suggestions.
Well let me add mine first I guess we need a clearer easier tutorial on getting linux booting from the sd or cf card. both of these options have subtle differences and need better defined instructions.
edit- As far as installing apps to the ubuntu.img. The usbnet interface is configured on the hx4700 side hopefully, if some one wants to do some googling on how to get it setup all the way on the PC side of things, I think we would all appreciate that. Then we could just ssh in and apt-get anything we wanted to try out or change. Later we could make it part of the download/tutorial after testing.

LG Fathom / VS750 kitchen and tools

Hi guys, here's some stuff for you to play and cook custom roms for your beloved(?) fathom.
I'm sorry for the delay but I really couldn't release those tools before.
Please note that I don't have a tool to decrypt other roms. To decrypt those vs750 roms, I had to hack the flash procedure, using an ARM disassembler attached on the flashing tool during a flash. It took me almost 2 weeks to find out a way to get decrypted files without bricking the phone, so hopefully you'll enjoy this and will build great Fathom roms.
Special thanks to trueg for experimenting/testing these tools.
So what do you need ?
- the last lg kitchen (available here)
- a decrypted rom (v5 or v7 available the the bottom of the kitchen's 1st post)
OR
- a full vs750 v7 kitchen (everything ready to cook)
mirror : bad upload, back soon
*****************************
Full vs750 v7 Kitchen info :
- SYS is already extracted (in 21000 folder)
- XIP is already modified to work with erviuskitchen (no more dsm files)
- OEM is stock v7, nothing more, nothing less
Build Procedure :
- Add your packages to EXT folder as usual
- Launch erviuskitchen.exe
- Select vs750, 21000 for ext, sys, xip
- Choose the packages you want to add/remove
- Check 6.5 aku and build rom
- Launch start.bat
- Select vs750 (9)
- Hit "u" to build rom.bin (you must use "vs750" as the beginning of the file name)
- flash it as described below
*****************************
Now the steps to flash the phone :
1- Install drivers
- LGUnitedMobileDriver_S4981CAN33AP22_ML_WHQL_Ver_3.3
- LGWindowsMobile_USBDriver_WHQL_ML_Ver_1.0
- LGSmartPhone_ModemlinkDUNDrive_WHQL_ML_Ver_1.0
You should easily find them (or more recent version) using your favorite search engine.
2- Install the flash tool
The only one that I know of being able to flash decrypted roms is LGNPST. Sorry, you'll have to search for it on the web (shouldn't be too difficult to find).
If using lgnpst, you'll also need to register this dll (using regsvr32 vs750.dll in a dos command prompt)
3- Connect the phone
To be able to connect the vs750 to lgnpst, you have to be in composite mode (on the phone, go to "settings/connections/Switch usb" then select "VzAccess Manager", click "save" and finally wait for it to reboot.
It's possible to flash this phone in emergency mode (if anything goes wrong and the fathom doesn't boot), but if you do so, you might lose your nv (and MEID info). To boot in emergency mode, shutdown your phone, unplug it, then press the "5" key on the keyboard and while keeping it down, plug the usb cable.
Don't do it unless necessary.
4- Save NV (just to be able to recover in case of problems)
- Put your phone in composite mode
- Plug the phone to your pc
- Launch LGNPST.exe, it should detect your phone (filename on the top right panel should be "VS750.dll").
- Click on "phone settings", wait a few secondes for a new window to appear
- Click on read button
- It will create a VS750_COMx.nvs in C:\LG Electronics\LGNPST
- Close the windows and click on "click here to continue".
5- Flash the Rom
- Put your phone in composite mode
- Plug the phone to your pc
- Launch LGNPST.exe
- Go in provision Tab (should be selected by default)
- Select Upgrade
- BIN file : "c:\VS750\BIN\VS750XXX5.BIN"
- Check SCR File, then select "C:\VS750\SCR\VS750VZ7_04.scr"
- Check PRL, Nam1 (uncheck nam2), select "C:\VS750\PRL\58006 - EVDO OEM Factory Default.prl"
- Don't check Eri file
- Click on "start"
- Keep fingers crossed for approximately 10min. The phone will reboot a few times, this is normal.
- Enjoy your 1st VS750 custom rom
Also note that for lgnpst to accept your rom, its name will need to start with "vs750".
And don't worry, there is almost no risk of really bricking the phone (especially if you saved the nvs).
I can confirm that you don't need to be too concerned about bricking your phone. As long as you can boot in to emergency mode and you have a backup of your NV data (made with LGNPST - it's very important that you do this - heck make two copies) you can recover it from an unbootable state.
TrueG
Would you be able to provide a pre-configured pack for the Fathom? I am trying my best to figure out how to get the kitchen working, but I haven't gotten it to fully work.
Thanks in advance.
-EDIT- I need to go back to school and learn to read - I saw LGNPST written 3 times, but only 1 was the program. The other 2 were component addons for it, all 3 having version numbers attached to the filename (hence my confusion lol).
@Pizzaboy: I'll help out with getting a filepack together. Which version of windows are you working with? Win7/WinXP, 32bit/64bit
@Trueg: Which version of windows are you working with? Win7/WinXP, 32bit/64bit
I run 7, both 32 and 64. My main dev is a 64bit system, and my porta-dev is a 32bit.
I've tried following the directions on the kitchen page, but I can't seem to get the XIP to work. It throws errors when I have to start pushing buttons.
da_reeseboy said:
@Trueg: Which version of windows are you working with? Win7/WinXP, 32bit/64bit
Click to expand...
Click to collapse
XP 32bit
TrueG
I guess I'll start with a WinXP 32 bit pc, and once I have it working right there I'll move on to a Win7 machine.
...my weekend is planned lol.
da_reeseboy said:
I guess I'll start with a WinXP 32 bit pc, and once I have it working right there I'll move on to a Win7 machine.
...my weekend is planned lol.
Click to expand...
Click to collapse
If you get something working on XP, i'll be able to get it working on 7.
I'm mostly lost on getting the V5 ROM set to work in the kitchen. I've never done a ROM before, and most of the tutorials are either really long and confusing, or really short and confusing...
Are you just trying to flash a rom after going thru the kitchen or are you trying to build on a different sys version from the one in whichever decrypted rom you are using?
da_reeseboy said:
Are you just trying to flash a rom after going thru the kitchen or are you trying to build on a different sys version from the one in whichever decrypted rom you are using?
Click to expand...
Click to collapse
When i hit step 9 in the Kitchen walkthrough, I push "realloc p" and it throws errors. Then when I get to the kitchen, it can't see the XIP and won't let me build a ROM.
@pizzaboy192 : I think the errors you're getting are a "normal" behavior of xipport. I don't understand why the xip is not generated though.
Anyway, I've just uploaded a complete vs750 v7 kitchen. Just follow the instructions on 1st post to build the rom.
spocky12 said:
@pizzaboy192 : I think the errors you're getting are a "normal" behavior of xipport. I don't understand why the xip is not generated though.
Anyway, I've just uploaded a complete vs750 v7 kitchen. Just follow the instructions on 1st post to build the rom.
Click to expand...
Click to collapse
could you make a v5 one too? V7 has too many bugs to make it a base personally.
Sorry, what I uploaded was based on my previous work on a rom and is fully tested (I won't upload a kitchen not tested to successfully build and flash a rom). Not sure I will have time to do the same on v5 in the next few days.
spocky12 said:
Sorry, what I uploaded was based on my previous work on a rom and is fully tested (I won't upload a kitchen not tested to successfully build and flash a rom). Not sure I will have time to do the same on v5 in the next few days.
Click to expand...
Click to collapse
I"m not going to complain. Maybe we can actually fix the broken files in the ROM.
How would we go about using other WM files from the COM3+ builds in the kitchen? Would this make it possible to bake in fun features? Would it also be possible to bake-out OEM features like the stupid Arcsoft stuff?
pizzaboy192 said:
I"m not going to complain. Maybe we can actually fix the broken files in the ROM.
How would we go about using other WM files from the COM3+ builds in the kitchen? Would this make it possible to bake in fun features? Would it also be possible to bake-out OEM features like the stupid Arcsoft stuff?
Click to expand...
Click to collapse
Totally possible, we just need to have a working base to start from.
Thanks Spocky for the uploads.
I'd love to start with a V5 base so that I don't have to remove all the Arcsoft junk. I'd just have to replace a set of reg keys and bake in a few files. Seems like it would make more sense. Plus it'd get rid of that cheap android-esque homescreen.
pizzaboy192 said:
I'd love to start with a V5 base so that I don't have to remove all the Arcsoft junk. I'd just have to replace a set of reg keys and bake in a few files. Seems like it would make more sense. Plus it'd get rid of that cheap android-esque homescreen.
Click to expand...
Click to collapse
I totally understand that. I'm running into errors with the v5 build too, so I just want to be able to successfully build and flash something to my phone to start. Once I have that (pulling the wheelchair out of the closet and blowing the dust off, getting rolling again in an ervius kitchen) I can start changing things.
Its kinda depressing to me to run into errors and not remember what causes them... a sign that its been way too long.
da_reeseboy said:
I totally understand that. I'm running into errors with the v5 build too, so I just want to be able to successfully build and flash something to my phone to start. Once I have that (pulling the wheelchair out of the closet and blowing the dust off, getting rolling again in an ervius kitchen) I can start changing things.
Its kinda depressing to me to run into errors and not remember what causes them... a sign that its been way too long.
Click to expand...
Click to collapse
I wonder if we could hybridize this... Take the OEM stuff from the V5 rom and the XIP from V7... would it work?
It'd be pretty easy to do, both are running the same basic windows mobile platform. I personally would like to compare the drivers used to see if there are any newer versions in v7.
da_reeseboy said:
It'd be pretty easy to do, both are running the same basic windows mobile platform. I personally would like to compare the drivers used to see if there are any newer versions in v7.
Click to expand...
Click to collapse
I'm waiting for files to copy on my netbook and I'll see what happens and if the ROM builds.
I'd be a little cautious of drivers, as there's some reason that there were so many issues with the 3G connection dropping on the V7 rom, I'd want to pin it on the WWAN drivers...

Categories

Resources