yashsingh1/xdaforums huggingface dataset:
[HD Mini Android Development] RicardoAlves27:
This is going to be the "real" Android with no problems? :) And we boot with the Sd Card like the others versions?
[HD Mini Android Development] sp3dev:
Sure this is going to be "real" Android with recovery and stuff like rom manager. If I have time, we'll probably even merge kernel with CM7 liberty and port CM7 to photon.
[HD Mini Android Development] ¨K¨:
this is great news, thx a lot!!
[HD Mini Android Development] RicardoAlves27:
And it`s just normal boot by Sd Card?
[HD Mini Android Development] BATFINK74:
this is excellent news,you sure do know your stuff,brilliant!
[HD Mini Android Development] kiretocin:
no, it gonna be boot from the main memory of the phone
[HD Mini Android Development] RicardoAlves27:
But it`s not a rom right? It`s like an app?
[HD Mini Android Development] kiretocin:
yes it is gonna be ROM, and you have to erase windows from the phone
[HD Mini Android Development] RicardoAlves27:
:( So i have to unlock my phone?
[HD Mini Android Development] kiretocin:
when it will be done, the developer will make tutorial how to install it
[HD Mini Android Development] RicardoAlves27:
If it is a Rom i have to flash my phone :(
[HD Mini Android Development] kiretocin:
yes, and it gonna work only on android, not dual boot, it gonna be like every other android phone
[HD Mini Android Development] RicardoAlves27:
It`s gonna be very good. But i`m afraid to flash my phone and then Android doesn`t work well...
[HD Mini Android Development] codiak:
In that case you can just flash back the wimo rom.
[HD Mini Android Development] gastrella:
i'm so excited .... hpw much days do you think we need to wait to have it? thank you very much !!!!
[HD Mini Android Development] okkie:
hey sp3dev what about your tests every thing fine ...?
[HD Mini Android Development] SonixTheBishop:
I think sp3dev is working very hard for us and i think isn a good idea stress him every day...when nand will be ready he will post the news no?
[HD Mini Android Development] okkie:
1- thanx for ur advice

2- i didnt stress on him iam just asking him about his tests on his university

3- i think its a good idea that you let hims tell that if he complain

cheers :)
[HD Mini Android Development] sp3dev:
Hey! My university stuff is fine. Tonight I'm devoting sime time to studying some math and computer graphics and plan to work a bit on the hd mini tomorrow.

So, in short, minor stuff is done - LK boots, framebuffer works fine, clock code is ready (btw, i have pushed the patches to LK into my git so now both xperia and hd mini are in the same tree). But there are issues with usb. I have already refactored usb to use separate queues for RX/TX and it works on my xperia. On hd mini, however, no matter how I configure the controller, incoming transactions end up with failures or short reads. So my plan is to port the driver from linux..
[HD Mini Android Development] munjeni:
Great works sp3dev! I extracted partition info from radio, maybe help you in future works:

Partition-Info :
------------------

0:MIBIB
---------------------------------------------------------
Page:	0x0
Size:	0xA
Address:	0x00000000 - 0x00140000
Block:	0x00000000 - 0x00000280
Flash:	0x00000000

0:QCSBL
---------------------------------------------------------
Page:	0xA
Size:	0x4
Address:	0x00140000 - 0x001C0000
Block:	0x00000280 - 0x00000380
Flash:	0x00000000

0:OEMSBL1
---------------------------------------------------------
Page:	0xE
Size:	0x6
Address:	0x001C0000 - 0x00280000
Block:	0x00000380 - 0x00000500
Flash:	0x00000000

0:OEMSBL2
---------------------------------------------------------
Page:	0x14
Size:	0x6
Address:	0x00280000 - 0x00340000
Block:	0x00000500 - 0x00000680
Flash:	0x00000000

0:HTC
---------------------------------------------------------
Page:	0x1A
Size:	0x10
Address:	0x00340000 - 0x00540000
Block:	0x00000680 - 0x00000A80
Flash:	0x00000000

0:AMSS
---------------------------------------------------------
Page:	0x2A
Size:	0xC0
Address:	0x00540000 - 0x01D40000
Block:	0x00000A80 - 0x00003A80
Flash:	0x00000000

0:EFS2
---------------------------------------------------------
Page:	0xEA
Size:	0x2C
Address:	0x01D40000 - 0x022C0000
Block:	0x00003A80 - 0x00004580
Flash:	0x00000000

0:FOTA
---------------------------------------------------------
Page:	0x116
Size:	0x8
Address:	0x022C0000 - 0x023C0000
Block:	0x00004580 - 0x00004780
Flash:	0x00000000

0:RESERVED
---------------------------------------------------------
Page:	0x11E
Size:	0x2
Address:	0x023C0000 - 0x02400000
Block:	0x00004780 - 0x00004800
Flash:	0x00000000

0:APPSBL
---------------------------------------------------------
Page:	0x120
Size:	0x6
Address:	0x02400000 - 0x024C0000
Block:	0x00004800 - 0x00004980
Flash:	0x00000000

0:MISC_MFG
---------------------------------------------------------
Page:	0x126
Size:	0x2
Address:	0x024C0000 - 0x02500000
Block:	0x00004980 - 0x00004A00
Flash:	0x00000000

0:WLAN
---------------------------------------------------------
Page:	0x128
Size:	0x2
Address:	0x02500000 - 0x02540000
Block:	0x00004A00 - 0x00004A80
Flash:	0x00000000

0:SPLASH1
---------------------------------------------------------
Page:	0x12A
Size:	0x9
Address:	0x02540000 - 0x02660000
Block:	0x00004A80 - 0x00004CC0
Flash:	0x00000000

0:SPLASH2
---------------------------------------------------------
Page:	0x133
Size:	0xE
Address:	0x02660000 - 0x02820000
Block:	0x00004CC0 - 0x00005040
Flash:	0x00000000

0:APPS
---------------------------------------------------------
Page:	0x141
Size:	0x278
Address:	0x02820000 - 0x07720000
Block:	0x00005040 - 0x0000EE40
Flash:	0x00000000

0:EXT_ROM
---------------------------------------------------------
Page:	0x3B9
Size:	0x47
Address:	0x07720000 - 0x08000000
Block:	0x0000EE40 - 0x00010000
Flash:	0x00000000
[HD Mini Android Development] gastrella:
there is some kind of problem to make the port working? if you need a beta tester you can ask to me
[HD Mini Android Development] milan7171:
hi sp3dev,i want ask an question:are you working on nand android?,we are expecting for this.

i can help you to finish nand quickly!

thanks for your effrots in dev

---------- Post added at 10:25 AM ---------- Previous post was at 10:19 AM ----------

does finish nand in this weakend?please answer this question.

nand news can happy everything in the world.

if you have problem in nand,you can bring up it on xda that sovled it!!
[HD Mini Android Development] Wowser:
Give the man a break and live with dual booting for the time being rather than anxiously looking at this read on a daily basis. When Sp3dev has updates, he will provide updates in his own time to these posts.

It might take weekends of work to work out the coding and workarounds given all the complications. Sp3dev has already said there are problems with the USB recognition just for starters in his last update.

And even when the NAND project is accomplished, the existing Photon ROM development still needs to be properly ported and tested to work on it.
[HD Mini Android Development] fernando2610:
Any progress?? sp3dev could you tell us if there any progress in the project. Thanks
[HD Mini Android Development] milan7171:
hi

sp3dev could you tell us if there any progress in the project

thanks
[HD Mini Android Development] sp3dev:
When there *is* progress, I'll let you know.

I have no ideas about why usb is not working when booting LK via HaRET (I have added flushing whole data cache but that did not help.. it's weird since usb works in linux). So I am working on getting LK to boot from NAND on cold boot. First attempts were not successful but I have disassembled the bootloaders of photon and liberty and figured out some issues, so now that at least basic debugging via vibra is available I'll try to figure out where exactly the booting process fails.
[HD Mini Android Development] ¨K¨:
thx a lot for your time on this project sp3dev!
[HD Mini Android Development] sp3dev:
**** yea.. After spending two weeks and reading lots of manuals usb did not work. But the problem was stupid. Due to the peculiarities of msm MPU (memory protection unit) and because part of device RAM was not mapped as device memory, USB could not write to the buffer which was a static array in code. Replacing it with a malloc'ed memory from the heap in another memory area did the trick and fastboot works.

Other news is that I was not yet able to boot LK from NAND (I'm booting test versions via HaRET now) but that's not a priority now. Right now there are still small issues to fix, including charger support and adding NAND chip config to the driver.

For those who want to look at the sources, the pathes are in git, as usual.

http://img683.imageshack.us/img683/9646/dsc0083rq.jpg
[HD Mini Android Development] baggino:
Sp3dev Hello... good news...:) you're a great....;), good work, I hope to read them very soon
[HD Mini Android Development] okkie:
thanks sp3dev its a great news ... good luck with other issues

hope to see this nand soon
[HD Mini Android Development] munjeni:
Hi it's great, maybe config from revskills app will give you small help:

<device name="MSM72xx">
<flashmode>3</flashmode>
<id>01B0</id>
<NAND_FLASH_BASE>A0A00000</NAND_FLASH_BASE>
<NAND_FLASH_CMD>A0A00000</NAND_FLASH_CMD>
<NAND_EXEC_CMD>A0A00010</NAND_EXEC_CMD>
<NAND_FLASH_STATUS>A0A00014</NAND_FLASH_STATUS>
<NAND_BUFFER_STATUS>A0A00018</NAND_BUFFER_STATUS>
<NAND_FLASH_READ_STATUS>A0A00044</NAND_FLASH_READ_STATUS>
<NAND_FLASH_BUFFER>A0A00100</NAND_FLASH_BUFFER>
<NAND_FLASH_ID_DATA>A0A00040</NAND_FLASH_ID_DATA>
<NAND_FLASH_CHIP_SELECT>A0A0000C</NAND_FLASH_CHIP_SELECT>
<FLASH_MACRO1_REG>A0A00064</FLASH_MACRO1_REG>
<NAND_DEV0_CFG0>A0A00020</NAND_DEV0_CFG0>
<NAND_DEV0_CFG1>A0A00024</NAND_DEV0_CFG1>
<NAND_DEV1_CFG0>A0A00030</NAND_DEV1_CFG0>
<NAND_DEV1_CFG1>A0A00034</NAND_DEV1_CFG1>
<FLASH_XFR_STEP1>A0A00070</FLASH_XFR_STEP1>
<FLASH_XFR_STEP2>A0A00074</FLASH_XFR_STEP2>
<FLASH_XFR_STEP3>A0A00078</FLASH_XFR_STEP3>
<FLASH_XFR_STEP4>A0A0007C</FLASH_XFR_STEP4>
<FLASH_XFR_STEP5>A0A00080</FLASH_XFR_STEP5>
<FLASH_XFR_STEP6>A0A00084</FLASH_XFR_STEP6>
<FLASH_XFR_STEP7>A0A00088</FLASH_XFR_STEP7>
<FLASH_DEV_CMD0>A0A000A0</FLASH_DEV_CMD0>
<FLASH_DEV_CMD1>A0A000A4</FLASH_DEV_CMD1>
<FLASH_DEV_CMD2>A0A000A8</FLASH_DEV_CMD2>
<FLASH_DEV_CMD3>A0A000D0</FLASH_DEV_CMD3>
<FLASH_DEV_CMD4>A0A000D4</FLASH_DEV_CMD4>
<FLASH_DEV_CMD5>A0A000D8</FLASH_DEV_CMD5>
<FLASH_DEV_CMD6>A0A000DC</FLASH_DEV_CMD6>
<FLASH_DEV_CMD_VLD>A0A000AC</FLASH_DEV_CMD_VLD>
<EBI2_MISR_SIG_REG>A0A000B0</EBI2_MISR_SIG_REG>
<NAND_ADDR0>A0A00004</NAND_ADDR0>
<NAND_ADDR1>A0A00008</NAND_ADDR1>
<NAND_ADDR2>A0A0000C</NAND_ADDR2>
<SFLASHC_BURST_CFG>A0A000E0</SFLASHC_BURST_CFG>
<NAND_EBI2_ECC_BUF_CFG>A0A000F0</NAND_EBI2_ECC_BUF_CFG>
<TLMM_INT_JTAG_CTL>A900026C</TLMM_INT_JTAG_CTL>
<NAND_CMD_RESET>1</NAND_CMD_RESET>
<NAND_CMD_ABORT>31</NAND_CMD_ABORT>
<NAND_CMD_PAGE_READ>32</NAND_CMD_PAGE_READ>
<NAND_CMD_PAGE_READ_ECC>33</NAND_CMD_PAGE_READ_ECC>
<NAND_CMD_PAGE_READ_ALL>34</NAND_CMD_PAGE_READ_ALL>
<NAND_CMD_SEQ_PAGE_READ>15</NAND_CMD_SEQ_PAGE_READ>
<NAND_CMD_PRG_PAGE>36</NAND_CMD_PRG_PAGE>
<NAND_CMD_PRG_PAGE_ECC>37</NAND_CMD_PRG_PAGE_ECC>
<NAND_CMD_PRG_PAGE_ALL>39</NAND_CMD_PRG_PAGE_ALL>
<NAND_CMD_ERASE_BLOCK>3A</NAND_CMD_ERASE_BLOCK>
<NAND_CMD_FETCH_ID>B</NAND_CMD_FETCH_ID>
<NAND_CMD_STATUS>C</NAND_CMD_STATUS>
<NAND_CMD_RESET_MEMORY>D</NAND_CMD_RESET_MEMORY>
<!--<init addr="TLMM_INT_JTAG_CTL" MODE="4" VAL="A900026C">9</init>-->
<init addr="DISABLE_NAND_MPU" MODE="4" VAL="A0B00000">0</init>
</device>
[HD Mini Android Development] sp3dev:
Well, that's cool of course, but we do have NAND drivers in LK and linux. The only thing needed is the device config (like erase block size, oob size and other stuff).

like

{0x005c00ec, 0xFFFFFFFF, (256 << 20), 0, 2048, (2048 << 6), 64, 1},

Settings for our NAND chip can probably be ripped from the wince bootloader, but I think they should just match other Samsung chips and differ only in flash size.. We'll see how it goes
[HD Mini Android Development] milan7171:
actually,the only thing needed?!!

its great,you are the best dev

you can happy people in the world who have hd mini

thanks
[HD Mini Android Development] munjeni:
Hi, I think nand driver is good in linux becouse I installed Debian in Photon, compiled mtd_utils directly in Debian Photon and tried to write to nand, to erase nand, to mount yaffs (yaffs can mount but yaffs2 not working, see my git -> http://gitorious.org/2-6-32-photon there I added some changes for yaffs...)...etc but only not worked was offset 0 to 0x2820000, only offset from 0x2820000 to xxxxxxxxx working!!! So I think we not need to touch offset between 0 to 0x2820000, right? See my post about mtd utils...
[HD Mini Android Development] sp3dev:
Actually, I have read the NAND id in winmo and added the line from LG Optimus LK to our. The offset indeed should be 0x2820000, as it is in other wince devices including Kovsky.

One major thing left to do in LK itself is adding proper support for charger/battery and reading gpio keys so that the user can choose between a normal boot and fastboot. Now the problem is that my code to load LK that works on Kovsky and Rhodium does not work on Photon. Actually, the device does not even start executing it. I am yet to try replacing XIP in wince rom with LK instead of building the whole rom from scratch. My guess is that Photon's bootloader may need extra bytes with OS version at 0x1000 in XIP, but I have not verified whether it helps.

And one little problem.. The linux kernel does not yet boot via fastboot (while loading LK via fastboot works). This probably has do to with L2 cache and will just work on NAND but I'd prefer to fix this issue anyway.

Unfortunately, I cannot get flashing via USB with HTC bootloader to work in linux and I won't have access to a windows computer any time soon. So either I will have to make my own sspl which will allow me to flash from sd card or try KVM as VirtualBox fails to work with the USB when the device in bootloader.

Overall photon is similiar to older msm7200A devices but there are some strange issues and bugs that were not encountered on msm7200A due to which porting takes more time than I expected..
[HD Mini Android Development] munjeni:
Huh, did you tried installing wine and xp in wine (for sspl work?) or maybe live xp from usb stick? About battery, we worked 2 mounths for battery algorithm (it's ~90% good now) maybe contacting r0bin for help, I think he will help you for battery! See attachment there is some nand chips and nand configs

<flid name="Samsung KBY00N00HM" id="[COLOR="Red"]5500BCEC[/COLOR]">
<blockcount>1000</blockcount>
<pagecount>40</pagecount>
<pagesize>800</pagesize>
<totalpagesize>840</totalpagesize>
<makerid>EC</makerid>
<deviceid>BC</deviceid>
<devicewidth>2</devicewidth>
<devicetype>1</devicetype>
<deviceflag1>0</deviceflag1>
<deviceflag2>0</deviceflag2>
</flid>
[HD Mini Android Development] superzuan:
woowwwwwww great work here .
[HD Mini Android Development] munjeni:
hahaha :D http://xdaforums.com/showthread.php?p=18961847#post18961847 juhuuuuu:)
[HD Mini Android Development] kiretocin:
and? what this have to do with htc hd mini nand
[HD Mini Android Development] munjeni:
I will help here for custom spl (hspl) after find solution for spl from hd2, I have all needed to unbrick hd2 and than I not care if I brick hd2 becouse it will be unbricked for 2 minutes...see picture ;)
[HD Mini Android Development] multicoms:
i have a friend here showing me before he able to boot direct from hd2 without any problem, do you want me to ask for the info?
[HD Mini Android Development] munjeni:
Hi, what to boot?
[HD Mini Android Development] pwel:
Munjeni, I read the link and it seems your HD2 is alive again! Congratulations! I know you will also help the HD mini NAND issues now! Good luck.
[HD Mini Android Development] okkie:
yes we need help from any dev here ... this is a big project i think! and sp3dev really

work hard in it! and i know he will do it soon ... but a little help will be nice.

good luck for all ... and good luck on our project :)
[HD Mini Android Development] munjeni:
Yes hd2 is alive again... trying to get my own (H)spl for hd2 but my knownledge in asm is 0, will be happy to see an spl full disasembled to see what I need to do with it! I going to buy an secondhand hd mini again becouse I realy love that phone becouse is small and compact... did anyone found jtag pins for hd mini or maybe aria, gratia, liberty?
[HD Mini Android Development] iPlasm:
Welcome back to htc HD mini, :)

We're very sorry munjeni :( ... I tried to search every, but nor could find anything for Scheme marks for JTAG's pins htc HD mini, Aria, Gratia and Liberty, as we talked before: http://xdaforums.com/showthread.php?t=1239958&page=5

Also Sp3Dev is welcome to our htc mini.... hope he likes his phone. :)
[HD Mini Android Development] sp3dev:
Okay, I've finally managed to get LK and linux to boot from NAND. Cleaning up stuff now. Will try to make a release next week
[HD Mini Android Development] okkie:
very good news :)

i know that you will do it ... thanks a lot for this good news and hoping every thing go well.
[HD Mini Android Development] sp3dev:
Ok, here is the updated status

1. Linux boots if loaded via usb with fastboot. Unfortunately, only uncompressed images work, gzip'ed ones seem to hang (TODO: figure out why and enable L2 cache to see if it is a performance issue)

2. NAND can be written to, but reading fails (TODO: figure out why DMA transfers fail)

I'm preparing the sources for the NBH/NB flashable rom builder for release. Meanwhile, those of you who want to play with the current setup, can try out the alpha build (which has the above-mentioned issues)

http://www.mediafire.com/?ni6qmwmxyio1vna

To try it out, do

1. Boot the lk by launching haret and clicking the 'Run' button

2. When LK has started booting, press and hold volume down to enter the fastboot mode

3. When fastboot is started, connect the usb cable

4. on the host pc, use fastboot to execute the following command

fastboot flash lkbootloader out.nb
fastboot reboot

so, you can update the lk in the same way later.

to boot the kernel image (note that it should be Image, not zImage now), do

fastboot boot Image initrd.gz
[HD Mini Android Development] munjeni:
Hey, great job, I temporarily took the phone back and will try something... what kernel you use now for booting? Did you tried recovery? What is usb driver for hd mini for windows xp?
[HD Mini Android Development] sp3dev:
Sorry, don't know about windows. A driver for G1 or Nexus One should work fine since usb VID/PID are the same.

I'm using the svn kernel, here is the uncompressed Image for you to test

http://www.mediafire.com/?m8zhhoc9l2m4s0m
[HD Mini Android Development] munjeni:
svn kernel from liberty? For usb driver I going to install jdk7u1-windows-i586 and android sdk http://xdaforums.com/showthread.php?t=1119507 will try it now :)

lk tinboot is abble to run lk?? spl is protected from overwriting... I not want to brick device heh?
[HD Mini Android Development] milan7171:
hi,you are great dev,please tell me when will be come nand??

can you uploade nand rom?

i want to test nand rom!

thanks

---------- Post added at 08:19 PM ---------- Previous post was at 08:16 PM ----------

i can help you to build nand android

---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------

did build nand in tomorrow?
[HD Mini Android Development] sp3dev:
You have a great confusion over how the device works. SPL in NAND is protected with the NAND MPU (memory protection unit). We do not need to touch it since we're using LK instead of wince kernel.

In RAM, LK is loaded to the same address as wince (somewhere at 0x1600000) and then copies itself to 0x0. On msm7200A we had to disable RAM MPU to do it, on msm7227 it does not matter, on qds8250 the RAM MPU is activated once you initialize the NAND controller.

Basically, the only way to brick is to both change partition table in LK to make it write before 0x2820000 and disable NAND MPU, which you should never ever try to do.
[HD Mini Android Development] munjeni:
ok, thanks will try. Hey I tried mine zImage and initrd.gz and good news is it booting, console white text is displaying on screen on boot, wuhu good :) lets create an initrd and system image
[HD Mini Android Development] sp3dev:
Wait. So, the compressed zImage boots? Nice then. I had troubles with svn kernel. Generally I think the kernel would need a rewrite and port to a later version like .38. And it would be nice to have framebuffer console always enabled to see if it works or not.
[HD Mini Android Development] munjeni:
Yes it booting with framebufer at boot and without uncopresing kernel \o/ :)

Tried booting kernel and initrd from lk (it booting) and android from sd card but can not booting hmm maybe kernel crashed before android boot?
[HD Mini Android Development] milan7171:
will be come nand tomorrow?

please tell me

thanks
[HD Mini Android Development] sp3dev:
No it will not and do not ask when. When it work and is ready for an average user (i.e., with basic protection against full battery discharge and with the ability to reboot into recovery/bootloader from android), an announcement will be made.
[HD Mini Android Development] M O R T Y:
thanks to you, all developers!

we're waiting for you, and we're very Avid!!!!!!!!!

pls when the nand work is complete, upload files in some places like upload sites, too! (4shared, mediafire, rapidshare and etc) because we have trouble in downloading files from code.google.com! (we have site filtering problem)
[HD Mini Android Development] toni0815:
sp3dev :) You are the best one!
[HD Mini Android Development] munjeni:
For someone who have problem with usb drivers in xp here is fastboot, usb drivers, some changes inside lk:

static struct udc_device htcphoton_udc_device = {
.vendor_id = 0x0bb4 /*0x18D1*/,
.product_id = 0x0c01 /*0xD00D*/,
.version_id = 0x0100,
.manufacturer = "HTC Corporation",
.product = "HD Mini",
};

Extract amd and i386 in same folder, if computer ask for drivers, browse to usb drivers folder and install.

Becouse tinboot is not ok (not booting) here is hex edited sp3dev out.nb (added lk.bin compiled from source with included changes about udc_device changes... for nandboot test!).
[HD Mini Android Development] munjeni:
Got bootimage booting from nand, is it correct?

lkbootloader = 0x2820000 to 0x2840000

recovery = 0x2840000 to 0x3240000

misc = 0x3240000 to 0x32e0000

boot = 0x32e0000 to 0x3ce0000

system = 0x3ce0000 to 0xaee0000

userdata = 0xaee0000 to 0x1eee0000

cache = 0x1eee0000 to 0x1fee0000

./mkbootimg --kernel zImage --ramdisk initrd.gz --cmdline 'mtdparts=msm_nand:00a00000@0x032e0000(boot),0x07200000@0x03ce0000(system),0x14000000@0x0aee0000(userdata),0x01000000@0x1eee0000(cache)' --board photon --base 0x00200000 --pagesize 2048 --ramdiskaddr 0x00a00000 -o ./boot.img

system I think need to be increased (now it is 119537664 bute)

sending 'system' (136030 KB)...
OKAY [ 34.031s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 57.922s
[HD Mini Android Development] munjeni:
problem in initrd: unpacking initramfs failed - junk in compressed archive, what's wrong? Tried mine initrd and tried cm7 Liberty initrd no one working?
[HD Mini Android Development] derefas:
i tried to boot froyo with cm7 initrd from nand , i have constant boot animation and in adb have many errors and warns with dalvik

with froyo initrd - android booting but after desktop

system crash

logcat:

http://pastebin.com/LGiJpQPn
[HD Mini Android Development] munjeni:
Hi, what kernel you using?