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, we have the kernel and initrd in XIP, and four partitions: recovery, data, system, and cache.
How is NAND different than Haret?
Other than the fact that all files are running from the internal memory, NAND uses cmdline from Tinboot code instead of using startup.txt. This means you cannot change force_cdma or other settings like you can with Haret without recompiling. Also, NAND is a different kernel than the one used for Haret, so some commits on NAND may be ahead of Haret and some commits may not have made it over to us yet.
Where are the Android files stored and how do I update them?
Modules are stored in the data partition and are symlinked with /system/lib/modules. Every kernel update will also require a modules update which will be applied through the use of androidupdate.tgz in the /sdcard/andboot folder. Kernel updates will be applied through recovery, and modules will probably be handled at the same time.
My battery drained and now my phone is stuck in a boot cycle! AHHHHHH!
There are two different causes of this. If your phone died while in Android, the fix is quick and easy:
1) Unplug the USB cable, then remove the battery
2) Put the battery back in, and plug the USB cable back in
3) Let it charge for 5 - 10 minutes (it will vibrate like it is starting, ignore this)
4) Unplug the USB cable, then remove the battery
5) Put the battery back in, and start the phone
If you lost power while booting, the kernel may attempt to restart every time you plug the cable in (not confirmed this is the real cause yet). The only known solution to this is incremental charging of a few seconds at a time. Basically, follow the above steps, but you have to remove power every 5 - 10 seconds or so before it starts the kernel back up again. This sucks, and ACL is trying to reproduce so he can figure out how to fix it.
Kernel Status
FRX05 Build Status
Haret Console and ADB
This is going to be quick and ugly since I have to hit the sack. I'm assuming most of you are running Windows, so I'm going to start from there.
HaretConsole - http://dl.dropbox.com/u/11790134/Har...kageForWin.zip
Download, unzip, and connect your phone in ActiveSync mode.
On the phone, browse to Haret.exe and make sure there is no startup.txt or default.txt file in the same directory.
Run Haret.exe on the phone, and click Listen for Connections
Now, on your computer, run the batch file for haretconsole, and it should connect.
Until I get a chance to explain things, you can find details on commands here:
http://www.htc-linux.org/wiki/index..../Documentation
ADB Drivers - http://dl.dropbox.com/u/11790134/usb_driver.zip
First we need to unzip the drivers and connect your phone to the computer (must be at least booting into Android or in Android).
Now, open Device Manager (right click on Computer, click Manage, then click Device Manager)
You should see several unkown devices including one named XDA.
Right click on XDA, click Update Driver, click Browse, then click "Let me pick...", then click Have Disk.
Now browse to the unzipped drivers, and force it to use the ADB Interface driver. Say yes to any warnings.
You are now set to use ADB. I highly recommend checking out Droid Explorer from
http://de.codeplex.com. This will let you run console and a lot more against your phone when it is in Android.