Develop Bugs

Android on X50v (and maybe others in future)

Yes, I've decided to take on a mammoth task, welcome to "ROSS"... "Replacment Operating System Structure" for Mobile phones & PDA's =]
The website is located here!
Yeah, you all think i'm crazy "hang on, you can't port Android to X50v!"
Well, not YET, but with help It will be done.
What is android you may ask?
Android is google's open source platform for Mobile phones and PDA's =]
So yes, I plan to create a operating system for X50v to replace WM6 with and allow users to develop/change bits of the operating system they don't like.
There will be a few "flavours"
Lite: Basics, very Basics, just Wifi/bluetooth support, a simple GUI and No applications (just a few settings). This free's up a LOT of RAM + ROM
Medium: The one "hopefully" most people will use, This is the standard one, basic office applications (replacing all the standard WM6 ones) a few games, decent GUI etc.
Heavy: The one that leaves least RAM and ROM available, the one with the most applications + usability, although it may lag a little.
Of course, we're going to build a "super-lite" version first, just to make sure it's flashable to the X50v =]
Maglite_RUS & Football may be willing to help, maybe not, we hope for his help + support throught this project
but first we need a team!!!
If you have any experience in making ROMS for X50v (ONLY, we will work on others after the X50v is done) or developing operating systems (various Linux distro's included) and Java (what the majority is coded in) then please please sign up. I plan to help develop the applications rather than the operating system myself, but I will work on ALL aspects of the project of course
If you're interested, and have found this link of google or something, then don't hesitate to email me here
Feel free to discuss =]

Hi Obsidiandesire...
This could be a great project!
It's very nice to see you're a PPC enthusiast like me...
I'm a PC software developer (not PPC) with quite experience but to start this project we need some black belt coders...
Another Linux project was already started here
http://www.handhelds.org/moin/moin.cgi/DellAximX50 but the developing speed was not so fast...
Another issue would surely be the ROM compaction problem that will kick in also on a different OS.
The only thing that could solve this on x50v would be to hack the bootloader in a way to load OS from SD or CF , so all data will be written on a fast write NAND device... By the way this would mean loosing the internal ROM!

But your approach seems to be the most sensible one, as one would never lose the possibility to startup the phone's default os (windows mobile).
It seems quite an interesting project, i have to admit i have a strong will to help you out, as i am also a professional programmer, however i am not a java, or C developer (long time i do not do anything in C), so i guess i am more of a designer myself
Well, i will keep up with this post and maybe we will colaborate in the future, i feel it's time to have our own software in the mobile's, i hate the microsoft's approach to the os handling.

Glad to see we're getting some interest in this project!!!
Hopefully, soon we could set up a website and start developing =]
who knows, we may be the lucky winners of the google competition and get $10 million! (not much use to me because im british lol)
So, you're Idea would be basically multi-boot?
sounds good, but we'd need to modify the bootloader (maybe hold enter, power + reset to switch to ROSS-Mobile?)
Sounds good! and i've just started learning Java too, so this project could take a while, hopefully, if it starts getting quite a bit of attention, we could move it to other platforms (HTC touch etc) which would make us Gods within the PDA community
I do like the posibilities of Android as it looks like it could make good use of the graphics chip in the X50v and it wouldn't have Windows Mobile lagging it down
How much RAM does it have again? It would be as powerfull as an old PC if you overclock it slightly (700mhz, 32MB RAM, 16MB graphics or something like that) and slap on a minimal OS and you could have your own [email protected] Pocket version! lol
Sorry if i've gone off on a tangent, i'm really excited about Android and it's possibilities.
First steps though, how would you get the DEFAULT android software to boot on the X50v? I think this should be our goal before starting on the project itself

this is cool. if anyone gets this to work i would be happy to be a tester. i don't know much about programming but have flash other devices with Linux.
A bit a info i picked up on flashing Linux on ipaqs is that you had to flash a new bootloader that would boot both wince and Linux. don't know why both but maybe to return to wince because to flash the boot loader you did it with a app that ran on wince and after that you would boot the bootloader and make a serial connection so that you could send the linux distro and erase wince.

Thanks for the info, more help on how to do this would be great! (I could try this on my X50v for testing purposes)

would it not be actually possible to boot the android/linux directly from a storage card? so as to effectively allow users to 'dual' boot?

duke_stix said:
would it not be actually possible to boot the android/linux directly from a storage card? so as to effectively allow users to 'dual' boot?
Click to expand...
Click to collapse
Each time you would boot a os you would erase saved data (hard reset) because you would need the memory were the settings are for each os. but thats is what i think i haven't flash a device for a long time so im out of date on this as far as if they gotten a doul boot win ce and linux but i assume that this will be a problem with win ce and android dual boot.
You would have to put both os in the flash mamory(were the os goes) and find a way to save the settings from a os and store them so that it can load the settings for the other os and vice versa
but you could do it like linux on a palm zire72. i have linux on my zire but linux is on the memory card when i reset the device it will reboot onto the palm os, so no flashing happens just load the bootloader through the palm os and linux kernel loads, but at the same time palm os is hard reseted, this is palm but same linux that is used on ppc. You would need to find a way too load a bootloader during win ce but dont see that this is possible. only one os at a time.
And Obsidiandesire i will try to get an old friend that used to work on porting linux to ppc he might help on the bootloader part but haven't herd from him for a long time but will try hard on finding him. but as long as we get many people this might be possible. i will post later if i find him.(good luck on your leg)

or, the flash memory card from which you 'boot' the android/linux from could actually hold a partition which served as a flash drive/storage drive aswell? so effectively it would mean you would require something like a 1gb or 512mb card, splitting that to allow you RAM and ROM space but i cant see why that would be too difficult. it would just be a matter of tricking the linux to thinking the local on-drive storage is its 'root' drive and the default drive to save to and to completely and totally NOT access any of the WM stuff on the flash memory that is hard-soldered onto the handset.
not sure if this helps, just bandying ideas around at the mo!

duke_stix said:
or, the flash memory card from which you 'boot' the android/linux from could actually hold a partition which served as a flash drive/storage drive aswell? so effectively it would mean you would require something like a 1gb or 512mb card, splitting that to allow you RAM and ROM space but i cant see why that would be too difficult. it would just be a matter of tricking the linux to thinking the local on-drive storage is its 'root' drive and the default drive to save to and to completely and totally NOT access any of the WM stuff on the flash memory that is hard-soldered onto the handset.
not sure if this helps, just bandying ideas around at the mo!
Click to expand...
Click to collapse
I see what you mean, but then the card might not be recognised in windows =/
However, denying the operating system access to writing the rom (and store everything in RAM) might work, but all settings would have to be stored on the SD card which could lead to a slow application.
The SDK (with the sample apps) itself is around 100MB, but Methinks that the final OS will be around 30MB (Without any apps)
Expanding on the partition Idea, what about partitioning the ROM itself? This might require a special WM6/5/CE ROM but one flash compared to many (everytime the device boots) could be worth it, and it could get round the setttings loss if we restrict each one to not write over the other?
My leg is getting better thankyou, seems like a severe muscle strain (The doctor said) so i should be back in school tomorrow.... great

i see what you mean by the card not being recognised by windows and offer a simple solution:
have a DEDICATED card for android and a seperate card for storage under WM.
to be completely honest with you, theres people on here spending hundreds and hundreds of pounds to have the latest device (and im one of them) im sure they wouldnt mind spending an extra few pounds for another memory card which would allow amazing functionality without actually jeapordising their current WM install (so they can have an install of WM6 to fall back onto)
what i propose is the following system:
1) MEMORY card formatted and partitioned to allow more or less the same sort of structure of memory/ram as the onboard memory does
2) INSTALL the actual android/linux to the memory card utilising the space as you would the hard-soldered memory on the phone without actually modifying the handset itself in any way whatsoever.
3) THIS method allows people to effectively dual-boot android/WM6/5 without the danger of them actually ruining their WM6 install, effectively using the android/linux platform to play about with whilst having the original WM6 to fall back onto for day-to-day usage.
shouldnt be too difficult to accomplish, im sure a modified bootloader would do the job pretty well, cant see why without the help of Olipro and Pof this cant be done!
LETS GET THE BALL ROLLING!

Seems good, but what, have the SD card for storage and CF for the OS? 'cos you obviously can't have 2 SD cards in the X50v (unless there's a CF-SD card adapter lying around somewhere on the web or on a shelf)
But as far as getting the ball rolling, yeah!!
Work on having the vanilla build of android (one included in the SDK) running before starting from scratch!

Obsidiandesire said:
Seems good, but what, have the SD card for storage and CF for the OS? 'cos you obviously can't have 2 SD cards in the X50v (unless there's a CF-SD card adapter lying around somewhere on the web or on a shelf)
But as far as getting the ball rolling, yeah!!
Work on having the vanilla build of android (one included in the SDK) running before starting from scratch!
Click to expand...
Click to collapse
another problem would be on getting the bootloader to see the cf card and that maybe a problem, we would need to add one of the slots(sd or cf) to the bootloader and let us choose what os to boot or what memory to boot(sd,cf, or rom mem).
the other way if we don't want to modify anything would be loading a bootloader during winidows mobile.
i hate this time difference

i cant see why you cant actually have the android on the SD card and stick to having the CF card as storage for both WM and Linux
that way, it would mean a sort of 'standardising' for people to port over to other phones which use SD based memory cards.rather than making it bespoke to CF capable devices (of which there arent many!)

Yes, the problems will be a rebuild of the bootloader to recognise both SD + CF cards.
And loading the bootloader under Windows mobile could be good, but you'd then have to terminate WM (which could be a problem)
And which part of the USA do you live in? There's probably an 8 or 9 hour time difference :-(
@dude_stix
well, even so, you'd need both SD + CF storage, which AGAIN could be a problem. But (in my experience) CF is more expensive, and considering Android will take up less space, It seems a more viable option (in my example, a 32MB CF card would be useless if I installed Android on a 2GB SD card and nullified the rest of the space for use (which could happen))
I think the easier option would be to modify the bootloader to look for images on both cards and install on the one with the image on it.
What about drivers etc? Obviously these would be needed for most things.

drivers????
thats all i got but it would not be hard if htc releases its android devices soon so we can get ideas from them. still today linux devices have problems with bluetooth, wifi, backlight, sd, etc...
posted on 5:23 pm here in south central US (Texas)

That's a 6 hour time differance :/
The Drivers being the things (mainly DLL's in WM) that controll the wifi/bluetooth etc.
This is why Linux has problems with them, i think they have to rebuild their own or something, which could pose a problem.
Do you think we should set a website & Forums up, or is it too early at the moment?

ultraprimeomega said:
drivers????
thats all i got but it would not be hard if htc releases its android devices soon so we can get ideas from them. still today linux devices have problems with bluetooth, wifi, backlight, sd, etc...
posted on 5:23 pm here in south central US (Texas)
Click to expand...
Click to collapse
Yeah... ...Drivers!!
This will be the hard one...
With WM6 cooked rom it was easy... We could reuse WM5 drivers written specifically for that device (x50v and x51v needed a specific driver for the 2700G chipset).... So if there won't be any Smartphone with such chipset with Android pre-installed it would be very hard to write that drivers from scratch... By the way somewhere I remeber I found a PowerVR driver source code for Linux that could be useful to do the job...
Cheers

Antineutrino said:
Yeah... ...Drivers!!
This will be the hard one...
...
Cheers
Click to expand...
Click to collapse
Isn't the drivers' job what the linux kernel is supposed to do? Why don't you go grab the kernel from the gpe/opie project and add the android image to it, partition the sd card with a windows and a linux partition like the other linux guys do, load the ramdisk like they do and see if it works. At least they have a start on the drivers for the Axim.

wovens said:
Isn't the drivers' job what the linux kernel is supposed to do? Why don't you go grab the kernel from the gpe/opie project and add the android image to it, partition the sd card with a windows and a linux partition like the other linux guys do, load the ramdisk like they do and see if it works. At least they have a start on the drivers for the Axim.
Click to expand...
Click to collapse
Well, this could be a start indeed, now how do we get android actually ON the x50v??

Bootloader for booting WM and Android off one device?

Hello,
like the title says i'd like to know if it's possible to create a bootloader or somewhat which is able to boot the standard OS from the device and a second OS from the memory card?
Let's say - if you switch the device on, you could choose whether to boot from the device (WM) or the memory card (Android).
Is it possible? Let's say - for the HTC HD2 for example?
What i found so far, is this and this article, as well as several threads in this forum. At least some really good dev's made it and ported Android to Touch HD for example. A bootloader would be needed in order to select, what to boot.
Thanks in advance.
Sincerely, nitrate

What currently happens is WM gets booted and then Haret gets run which acts as a bootloader.
You could streamline the process, and have haret run sooner, but given Android is currently not that stable I'd want to boot to WM myself.

l3v5y said:
but given Android is currently not that stable I'd want to boot to WM myself.
Click to expand...
Click to collapse
What?? I switched to my Android phone from a WinMO and I am upset because I didn't do it sooner.

Android on non-android devices is a little unstable, native android devices are stable enough. As far as bootloaders go, what most would like to see is a way of getting Android off SD and into ROM, so that we could boot directly into Android without needing to involve WM at all.
However unless someone can rewrite something like the OpenHandHeld bootloader for use with HTC devices, Haret will be the only way to boot Android for the forseeable future, plus, with the lack of stability on non-android hardware, I like the option of having WM there, just to fall back on if needed.

zenity said:
Android on non-android devices is a little unstable, native android devices are stable enough. As far as bootloaders go, what most would like to see is a way of getting Android off SD and into ROM, so that we could boot directly into Android without needing to involve WM at all.
Click to expand...
Click to collapse
This is what i want to know as well. A bootloader which let's you choose between booting WM from the devices' internal space or Android from the microSDHC-card.
And of course this bootloader should boot at first, just before WM does - kinda a boot menu of a Desktop PC which has Windows and Linux installed.

If it were possible to run a boot loader on your WM* device and dual boot there would be one major draw back (in my opinion); the architecture of these devices, without a storage card, uses the available memory for RAM and storage. Unlike your home PC that has specific Memory Chips and a Hard Disk Drive used for RAM and Storage specifically (if we ignore virtual memory for a minute) which means you can pack the disk space pretty much full and not effect the performance of the system.
Mobile Devices use some sort of Eeprom/solid state memory with XXXmb of memory. The more data files that you put inside the XXXmb of memory (in storage) means that the software you are running (WM6.5 + HTC Sense etc.) have less RAM to do their work, and the system is noticeably slower.
So back to the original topic, dual boot would suggest two OS residing in the devices ROM / XXXmb and a drastic reduction in performance, regardless of the OS WinMo or Android (linux)...
Saying that i have Android on my HD, using Haret.exe... I don't use it often and it is buggy - but the fact I've got it there shows that I'm still on the fence.

[How-To] properly install Android

It is not quite self-explaining how to install Android on our Windows Mobile devices. Therefore I took some time and wrote down all the steps for people who are new to "Android".
More testers -> more experience -> more knowledge -> faster/better development.
I hope this way the forum is kept clean(er) from all kinds of questioned that have already been answered many times.
ReadMe Includes:
- Partitioning
- Device preparations
- Boot loader
- Install steps
- Fixes
- Links
- more...
If you are a developer (you create your own package) feel free to use my ReadMe for your packages (update regularly though).
to download the ReadMe click the [Android Repository] button in my signature.

It goes to a rapidshare page with 3 files, and when I click on the filename Android_README.TXT
or start download, I get the error
The file could not be found. Please check the download link.

ok thanks. i fixed it (rs bug when renaming files ^^)

How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.

ATHiEST said:
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
Click to expand...
Click to collapse
normally just calculate how i wrote in the readme:
whole space -768 (3* 256) and then the other 3 x 256
but in ur case i would make the swap smaller (i think its not even used at all) and the fat32 bigger; for instance:
fat32 - 384 MB
ext2 - 256 MB
ext2 - 256 MB
swap - 128 MB (rest)

To be honest the bit I find most confusing is all the different versions!

i didnt create any partitions on my card, and android works as good as it does on any, mind you i have not updated the files fo0r a month so alot might have changed

ReadMe updated!
updated a bit...

Geeba said:
To be honest the bit I find most confusing is all the different versions!
Click to expand...
Click to collapse
i agree...
i've been looking these posts here for a couple of days now and i still don't know how to do it....
especially the DualBoot thing...
is it possible to make a little bigger how-to manual?
or at least explain the versioning and the needed thing a little more?

the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally

N!ghty said:
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
Click to expand...
Click to collapse
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...

qtype said:
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
Click to expand...
Click to collapse
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+

N!ghty said:
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
Click to expand...
Click to collapse
ok... thanks for the help... you helped me a lot just with the claryfication of the versions that need partitioning and the ones that don't...
i didn't know that...
good luck with studying!!!!

one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????

qtype said:
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
Click to expand...
Click to collapse
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.

N!ghty said:
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
Click to expand...
Click to collapse
yep, I downloaded it but I didn't know that i have to rename it...
It did the trick... booting up Android
thanks for all of your help...

updated the readme, not includes DualBoot howto and some other changes...

I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????

qtype said:
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
Click to expand...
Click to collapse
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider

N!ghty said:
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
Click to expand...
Click to collapse
sorry about that...I realized it later that I should ask in another thread that question...
I managed to figure it out... I just needed to manually configure my APN settings...

Installing Android without SD, to test NAND?

Is it possible to install Android on Kaiser without SD? Has anyone investigated bundling the /system partition with tinboot so the whole thing is installed with a single KAISIMG?
I ask because I have one Kaiser whose SD reader is broken. If I could install more than a kernel, I could try risky changes to fix the NAND driver. If I brick the phone or kill its flash, it's no big loss.

No, you can't do it now, maybe i can suggest you to look after a method do dump the nand after install and use it as kaiser image

Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?

PoXFreak said:
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
Click to expand...
Click to collapse
I don't think thats l1q1d idea... perhaps a complete nand dump, and reflash it to another kaiser.
The kernel and partitions must be configures before the dump...

I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.

This is possible, in fact there was a time where an empty img file was being incorporated into the NBH where on a windows NBH the system files would normally be copied. A windows NBH consists of a number of parts, I can't remember what they are all called right now, but they can all be merged using NBHmerge. I can't give you specific instructions but there's no reason why it can't be done, not sure it'll be much fun though!

n2rjt said:
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
Click to expand...
Click to collapse
pre-beta that you're testing on HTC What ??

daedric said:
pre-beta that you're testing on HTC What ??
Click to expand...
Click to collapse
HTC Wizard. I have two of them, which I have named Radagast and Gandalf. It's my all-time favorite smartphone, although it is obviously even more obsolete than the Kaiser. I use one of them as my primary phone whenever Android is giving me fits. Right now I'm testing H3r7 beta 2 preview where the cook has adeptly squeezed WM6.5 into a tiny, fast, stable package.

If I knew that I wouldn't have given my Wizard away...
I thought Ham3r was finished when he hit 6.1 but I stand corrected...pfft.

help androidinstall.tgz
please share for me : file androidinstall.tgz 2.1 or 2.2 but must run wifi and 3G.
Send for me by: [email protected] thanks i come from VietNam

I think with the proper memory map Android could be installed via FrankenKaiser or something of that sort. Something that addresses the NAND directly through OEMSBL, bypassing the need for a HardSPL. Of course the phone would have to be CID unlocked to do this, but I think it's possible to install via CustomRUU if the mapping was done beforehand.
I have read somewhere that NAND marked as bad in the map still gets "written" to, meaning whatever is supposed to go there is put there and never read. Once unmarked the written info comes back, but that requires a full format anyway.
I say very possible...

I have stopped trying to do this, but wanted to record my latest thoughts in case someone reads this in the future.
I think the best way to install Android on a Kaiser that can't read its sdcard is to edit the initrd then use recovery mode:
* install adbd so it gets started in recovery mode
* allow the menu when sdcard is not installed
* change scripts to look for /data/andboot
* change recovery mode to mount /data partition to usb
Then, of course, you boot the kernel, use the menu, enter recovery mode, transfer androidinstall.tgz and androidupdate.tgz to /data/andboot, then install system, install updates, clear data, and run. If something doesn't work, adb shell or adb push can help.
I think it's too much work to be worth it on this old phone.

Still only Android virtual roms possible for TP2 within Windows ?

It's been a while since i've been here, still work with the old Energy Rom in WM6.5 from June
Last time I visited this forum, they mentionned the TP2 would never be able to run Android.
Now I see there is an Android section here and I tested the latest Thunderbolt_V1 but that's a rom that runs into windows with a virtual machine.
Isn't it still possible to boot a 100% Android rom?
Somebody must find some tweaks and tricks, even if it's to heavy maybe a light-Android

No one is running android in a virtual machine on their TP2. Winmo is used to initialize hardware before xdandroid boots (don't know anything about thunderbolt, but I haven't heard good things about tiad, so maybe that wasn't your best bet for a first run). I hear there are some super unobtrusive light-weight winmo roms that will boot up without loading all the interface stuff and then auto boot to xdandroid. But it's still going to be kind of slow because it's a hack running off the sd card and optimization is a trial and error sort of thing by generous volunteers here.
As far as a real nand build, some folks are working on it, I mostly see activity at ppcgeeks. I hear it's not ready for primetime. It's possible it might never be, though I wouldn't want to discourage the kind souls plugging away at it. Best way to get it IMO is to hit some donate links for the people working on it.

Hi,
android doesn't run off a virtual machine, HaRET is a program that kicks winmo from memory, and initializes linux. Any changes you make in android are saved on real partitions, not containers or such, as is used in virtual machines, and changes are also permanent. Basically your external sd card's 3 ext2 partitions mimic the setup that is inside a normal android phone.
Thunderbolt v1 so far is a great rom for me (the first fully functioning one; because of that, android now my daily os), and its installed on your SD card. If you want an internal android os, try tiad8's NAND builds on his website, he has one or two versions (at your own risk, they're VERY experimental AFAIK).

waltibaba said:
Hi,
android doesn't run off a virtual machine, HaRET is a program that kicks winmo from memory, and initializes linux. Any changes you make in android are saved on real partitions, not containers or such, as is used in virtual machines, and changes are also permanent. Basically your external sd card's 3 ext2 partitions mimic the setup that is inside a normal android phone.
Thunderbolt v1 so far is a great rom for me (the first fully functioning one; because of that, android now my daily os), and its installed on your SD card. If you want an internal android os, try tiad8's NAND builds on his website, he has one or two versions (at your own risk, they're VERY experimental AFAIK).
Click to expand...
Click to collapse
Please don't direct people to other websites. NAND development started here on the TP2. He's only stolen the work of the brilliant devs here, and branded it as his own.
Did you somehow miss this thread?
NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery
tiad8 is a hack and a fraud, there is the proof.

andriod for tp2 isn,t virtual it,s real and i advise you not to install it on your phone as you don't know that it is virtual and then you come and say xda briked my phone