yashsingh1/xdaforums huggingface dataset:
[HD Mini Android Development] jumperfreak:
I also have a bootloop.

Only errors I can find in dmesg are these:

<6>[ 32.830608] yaffs: dev is 32505861 name is "mtdblock5" rw

<6>[ 32.830638] yaffs: passed flags ""

<7>[ 32.830658] yaffs: Attempting MTD mount of 31.5,"mtdblock5"

<6>[ 32.991788] gpio_keys_scan_keys: key 1-116, 0 (20) changed to 0

<4>[ 33.336834] ###BAD BLOCK 2486 136C0000###

<7>[ 33.336856] block 720 is bad

<4>[ 33.479721] ###BAD BLOCK 3095 182E0000###

<7>[ 33.479741] block 1329 is bad

maybe this can help?
[HD Mini Android Development] Mystikal57:
I already have bootloop

I think this dmesg could help developer:

http://pastebin.com/wFJYvVF5

It is a dmesg until the reboot
[HD Mini Android Development] jomaga:
Finally a fully working dmesg.txt from 0.00000

Hope it helps!

http://www.mediafire.com/?38cgo8rv2app6l8
[HD Mini Android Development] ToughGuy:
Hey devs~ i got dmesg and logcat log before reboot loop!

In recovery logcat command not working so i only can get dmesg log!

In recovery:

~ # logcat -d
logcat -d
/sbin/sh: logcat: not found

So~~~~:(

dmesg_booting.zip >> Get it before CM7 reboot loop.

logcat_booting.zip >> Get it before CM7 reboot loop.

dmesg_recovery.zip >> Get it In recovery.

Sorry for my bad english! Just hope everyone can understand i mean...:D:D
[HD Mini Android Development] schlund:
tanks again for your involvement!

Finally i found something very interesting!

only difference in logs are:

CONFIRMED AS WORKING:

<6>[ 0.745711] msm_nand: allocated dma buffer at ffa47000, dma_addr 252ea000
<6>[ 0.745823] status: [COLOR="Red"][B]c03020[/B][/COLOR]
<6>[ 0.745840] nandid: 5500bcec maker ec device bc
<6>[ 0.745858] Found a supported NAND device
<6>[ 0.745873] NAND Id : 0xBCEC
<6>[ 0.745886] Buswidth : 16 Bits
<6>[ 0.745900] Density : 512 MByte
<6>[ 0.745913] Pagesize : 2048 Bytes
<6>[ 0.745928] Erasesize: 131072 Bytes
<6>[ 0.745941] Oobsize : 64 Bytes
<6>[ 0.745985] msm_nand: read CFG0 = [COLOR="Red"][B]ea5400c0[/B][/COLOR], CFG1 = a7476
<6>[ 0.746003] CFG0 Old: [COLOR="Red"][B]0xea5400c0[/B][/COLOR]
<6>[ 0.746018] CFG1 Old: 0x000a7476
<6>[ 0.746031] CFG0 Init : 0xea5400c0
<6>[ 0.746046] CFG1 Init : 0x000a7476
<6>[ 0.746066] CFG0: cw/page=3 ud_sz=512 ecc_sz=10 spare_sz=4 num_addr_cycles
=5
<6>[ 0.746111] DEV_CMD1: f00f3000

CONFIRMED AS NOT WORKING:

<6>[ 0.745895] status: [COLOR="Red"][B]c03120[/B][/COLOR]
<6>[ 0.745911] nandid: 5500bcec maker ec device bc
<6>[ 0.745930] Found a supported NAND device
<6>[ 0.745945] NAND Id : 0xBCEC
<6>[ 0.745958] Buswidth : 16 Bits
<6>[ 0.745971] Density : 512 MByte
<6>[ 0.745985] Pagesize : 2048 Bytes
<6>[ 0.746000] Erasesize: 131072 Bytes
<6>[ 0.746013] Oobsize : 64 Bytes
<6>[ 0.746056] msm_nand: read CFG0 = [COLOR="Red"][B]aa5400c0[/B][/COLOR], CFG1 = a7476
<6>[ 0.746075] CFG0 Old: [COLOR="Red"][B]0xaa5400c0[/B][/COLOR]
<6>[ 0.746088] CFG1 Old: 0x000a7476
<6>[ 0.746103] CFG0 Init : 0xea5400c0
<6>[ 0.746118] CFG1 Init : 0x000a7476
<6>[ 0.746138] CFG0: cw/page=3 ud_sz=512 ecc_sz=10 spare_sz=4 num_addr_cycles
=5

finally that seems to be the only difference between working and not working devices.

It would be helpful if ALL (people with working AND not-working devices) could confirm that from their dmesg!

no i have to investigate what this matters, maybe sp3dev knows about it as our nand chief :)

EDIT: i can confirm bootloop is NOT caused by Bad Blocks, i repartitioned not to use them and bootloop still appears
[HD Mini Android Development] huahaonam:
I am waiting Offcial Release Nand Android To sp3dev,
[HD Mini Android Development] Mystikal57:
Confirmed for me
[HD Mini Android Development] SonixTheBishop:
Confirmed...http://pastebin.com/4FSuwuD1
[HD Mini Android Development] sp3dev:
Could you guys having bootloop try flashing this recovery and installing update.zip?

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

After flashing update.zip, go to fastboot and flash this boot.img

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

fastboot flash boot boot.img

---------- Post added at 09:13 PM ---------- Previous post was at 09:12 PM ----------

Also, here is my dmesg

[ 0.850636] msm_nand: allocated dma buffer at ffa47000, dma_addr 24502000

[ 0.850736] status: c03120

[ 0.850753] nandid: 5500bcec maker ec device bc

[ 0.850771] Found a supported NAND device

[ 0.850788] NAND Id : 0x5500BCEC

[ 0.850801] Buswidth : 16 Bits

[ 0.850815] Density : 512 MByte

[ 0.850830] Pagesize : 2048 Bytes

[ 0.850843] Erasesize: 131072 Bytes

[ 0.850856] Oobsize : 64 Bytes

[ 0.850903] msm_nand: read CFG0 = aa5400c0, CFG1 = a7476

[ 0.850921] CFG0 Old: 0xaa5400c0

[ 0.850936] CFG1 Old: 0x000a7476

[ 0.850950] CFG0 Init : 0xea5400c0

[ 0.850965] CFG1 Init : 0x000a7476
[HD Mini Android Development] jumperfreak:
Still bootlooping

EDIT: my dmesg

<6>[ 0.815746] msm_nand: allocated dma buffer at ffa47000, dma_addr 24814000

<6>[ 0.815856] status: c03120

<6>[ 0.815873] nandid: 5500bcec maker ec device bc

<6>[ 0.815891] Found a supported NAND device

<6>[ 0.815906] NAND Id : 0xBCEC

<6>[ 0.815920] Buswidth : 16 Bits

<6>[ 0.815935] Density : 512 MByte

<6>[ 0.815948] Pagesize : 2048 Bytes

<6>[ 0.815961] Erasesize: 131072 Bytes

<6>[ 0.815976] Oobsize : 64 Bytes

<6>[ 0.816020] msm_nand: read CFG0 = aa5400c0, CFG1 = a7476

<6>[ 0.816038] CFG0 Old: 0xaa5400c0

<6>[ 0.816053] CFG1 Old: 0x000a7476

<6>[ 0.816066] CFG0 Init : 0xea5400c0

<6>[ 0.816081] CFG1 Init : 0x000a7476
[HD Mini Android Development] Mystikal57:
Still bootlooping :(
[HD Mini Android Development] schlund:
well, that eliminates the differences here...

this issue is driving me crazy..

maybe someone with a working device could perform a clean install (with booting at least once), create a nandroid backup in recovery and upload it ?
[HD Mini Android Development] Mystikal57:
it's a very good idea !

If someone make a backup, it will works for all ?
[HD Mini Android Development] jomaga:
A clue... or maybe not

I had a working nand, you know

Well, playing a bit with lock screen, I activated some widgets (time, battery indicator) and phone restarted (to apply changes, I suppose). After that I have a pretty loopboot screen and android don't start. So I reflashed again Winmo and Haret. Tonight I'll reflash nand to make a backup from recovery
[HD Mini Android Development] Mystikal57:
Fine...

it's not the answer of differents problems, but, i find another nand version on 4pda.. and

no bootloop !

This version works very fine
[HD Mini Android Development] milan7171:
can you put this version of nand on this forum?
[HD Mini Android Development] Mystikal57:
I don't think so.. xda don't permise that and i don't know if they want.. but you can find it easily on 4pda.
[HD Mini Android Development] Vogelhaus7:
where ? i cant find it :o

link?:(
[HD Mini Android Development] milan7171:
Mystikal57,can you upload this nand version file on this forum?if you can ,please upload it.

thanks
[HD Mini Android Development] NoxinHH:
Very good idea and nearly too easy! :)
[HD Mini Android Development] schlund:
finally found the reason for the bootloop problem:

missing line in build.prop:

rild.libargs=-d /dev/smd0 nand_init

you can add this to spedevs builds (extract the zip, add line in build.prop, zip again)

and it will work!

now i can finally start collecting, i see some other developers made some progress, going to contact them ;)
[HD Mini Android Development] NoxinHH:
After searching for an hour or so and google translating a lot of Russian stuff I have finally found the download link for the russian Photon build...

First important thing, just to safe you the day: It WORKS!!!

I have flashed the build on my 3 HD Mini devices, took me just 5 minutes,

no boot loop, devices start fine. But I haven't tested anything yet...

All you need to do is to install this zip file from SD card:

http://www.mediafire.com/?651n5jj93s88052

I have formated (wiped) all partitions befor flashing. After rebooting you will see another screen with white letters. Don't panic. That's OK.

@Devs: Hope this helps to find the problem with "our" current build!

Have a nice evening,

Noxin
[HD Mini Android Development] NoxinHH:
Schlund, you are my hero!!!!! Confirmed, it's working!
[HD Mini Android Development] old.splatterhand:
@ Schlund

One question: Do you still use CWM Recovery 5.0.2.6 from Post #278 (and everythings working in it so far) or the one from sp3dev?
[HD Mini Android Development] jomaga:
Great Schlund! Thanks a lot
[HD Mini Android Development] schlund:
they are both working
[HD Mini Android Development] huahaonam:
Not Work For me:(

---------- Post added at 09:20 AM ---------- Previous post was at 09:13 AM ----------

Good Work For Me, Thanks Noxin Very Much :D:D
[HD Mini Android Development] derefas:
http://www.mediafire.com/?651n5jj93s88052

you forgot etc.rar

i had problem with libhtc_ril_wrapper with write reading in /etc/ and rewrite lib for sdcard etc , this is dirty fix , but data connection working
[HD Mini Android Development] wencyv:
to sum it all

what files and steps are needed to get it done? please advise... thanks
[HD Mini Android Development] NoxinHH:
Good morning!

Derefas, thanks for clarifying, do you have a download link for the etc.rar?
[HD Mini Android Development] derefas:
yes of course, i am create this build)

View attachment etc.rar
[HD Mini Android Development] huahaonam:
Please update.zip fix batterry :), :)
[HD Mini Android Development] Mystikal57:
thanks Schlund :)

Wifi doesn't work ?
[HD Mini Android Development] SonixTheBishop:
what it fix?
[HD Mini Android Development] derefas:
data connection with my build , put it into sdcard
[HD Mini Android Development] y0:
Anyone please confirm about the BATTERY DRAIN issue i mean not too much but it wont last for more than 12hrs of normal usage .How about that russian build? Battery backup is fine enough?
[HD Mini Android Development] SonixTheBishop:
ok thank you...anyway adding that line in builds.prop i get still bootloop so i have tryed the new version 7.2 its work...
[HD Mini Android Development] multicoms:
Greats thanks for all the pro effort, but it's there any guide to install this for the newbies with all the latest download link? :D

thx!
[HD Mini Android Development] derefas:
this build already had this line , you didn't need to add this

PS: format all partition and try again to flash system
[HD Mini Android Development] pwel:
multicoms,

I believe newbies should still wait a bit since the version available is still experimental. Please be patient and leave the devs do their work
[HD Mini Android Development] multicoms:
noted and will wait for dev to release the guide and stable version ... :p
[HD Mini Android Development] Ciccius:
well, I tried both version (sp3dev and deferas), that's my feedback.

sp3dev ver.: don't work wifi neither 3g connection. gps not tested, I don't have any app to test it

deferas ver.: wifi is ok, but 3g connection no (tried lastest package with etc patch). gps doesn't work, too (tested with 'gps status'). The button backlight, when is on, is always at max bright

both ver.: seems that battery drain is slightly higher then SD version
[HD Mini Android Development] NoxinHH:
I had working WiFi with SP3DEVs version but suddenly it stopped, showing "error" in the settings and is not willing to start again, I have tried several reboots.

No big deal for me. I will also wait for a new release, just wanted to let you know.
[HD Mini Android Development] maxxoros:
It s amazing news, I will test now. Waiting for nand for a long time
[HD Mini Android Development] SonixTheBishop:
hi all guys i have a question, i want to remove a feature in our cynogenmod, when i reach the end of the page a color come from the top or from the bottom, how can i remove it i hate that! any ideas? bye:p
[HD Mini Android Development] huahaonam:
I hope Have Soon :), Thank
[HD Mini Android Development] HALOHA:
THANKS for your work.

I use deferas ver and work very good.

But have a little problem.I have two HD mini,all use deferas ver.

Two phone both can use wifi....but can not use at the same time.

AP will auto disconnect one phone.

I guess the problem is the Phone MAC address.

ALL use deferas ver's phone seem use the same MAC address

"00:23:76:9E:9E:9E"

Maybe that's the reason for AP only can connect wifi to only one phone.
[HD Mini Android Development] Mystikal57:
The mac addresse isn't randomly calculated ? if you reboot your phone ?

And if you use theses commands in terminal ?

busybox ifconfig eth0 hw eth "0E:00:A0:03:1E:FF"

verify your command with:

busybox ifconfig

if you see the mac address your entered => it's ok
[HD Mini Android Development] Ciccius:
No, in deferas version it seems to be fixed (I have "00:23:76:9E:9E:9E" mac address, too). Using the that command the mac change without problem.

I installed sp3dev ver. again. When turn on wifi, I get an error message just below the wifi checkbox and in Wifi Advanced Option the mac address field is empty.
[HD Mini Android Development] HALOHA:
Your guess is right.MAC address isn't randomly.

I type your commend in terminal,but no work.

It's show "ifconfig: SIOCSIFHWADDR: Operation not permitted"

And the MAC address still not change....QQ....

BUT still THANK YOU for your idea^^
[HD Mini Android Development] Ciccius:
write the 'su' command before
[HD Mini Android Development] NoxinHH:
[TUTORIAL] How to change wi-fi MAC addres on CyanogenMOD and others rom's based on it

Did you try this one?

http://xdaforums.com/showthread.php?t=1343695
[HD Mini Android Development] Ciccius:
I didn't found the file @ point 3 of tutorial
[HD Mini Android Development] sp3dev:
The problem is that when RPC on arm9 is initialized, it calls some services on arm11 (like time_remote). This is done by winmo on haret. But if you do not register those on nand boot, the arm9 will crash. Also, you should comment out the code to control uart1-uart3 clocks - if linux disables them on early nand boot, the modem will crash.

Actually I am not extermely fond of MSM and want to get myself a device with omap or samsung since there are opensource drivers for X11 and v4l2 drivers for camera, just need to finish my xperia project first.

Anyway, an hd mini would be nice if someone in Moscow could just give me one. Since I'm living in a dorm, it's a bit of a problem for me to get stuff shipped by mail. Actually looks like most stuff is done for hd mini so there's not much job for me except the nand loader although porting cm7 and kernel 2.6.35.7 would be nice to do.
[HD Mini Android Development] munjeni:
Aha, ok, understand now diference. I ported 2.6.35 but it could not booting -> http://gitorious.org/2-6-35-photon not understand why, only tried one time! Maybe it is nand kernel?
[HD Mini Android Development] djfastest:
see inside
[HD Mini Android Development] djfastest:
sp3dev say: stupid enough to copy all that we have done for the 7200A, and despite the fact that HD MINI 7227 - code to manage the processor speed is not there, and everything else in these same SoC. So take my lk with gitorious, add your claret as has been done to htckovsky and htcrhodium. Carefully check the file target/msm7200a_htc_wince/init.c - it is necessary to check that the address is read from the phone model name

oad in two ways - by collecting nbh wrapper or Haret with the command line

set ramsize 0x08000000

set ramaddr 0x00000000

set KERNEL lk.bin

set MTYPE 2006 / / something else ,becose LK not need this,but hareed need To deceive HARET

set TAGS_OFFSET 0x300000

set KERNEL_OFFSET 0x00000000

PFW 0xa8250800 0 / / DISABLE MPU (Protection of operative memory)

boot2

https://gitorious.org/lk-msm7200a-htc-wince/tinboot-for-lk-xda/trees/master
[HD Mini Android Development] munjeni:
Ok I will try ading photon to init.c. Are you sure it will working?
[HD Mini Android Development] sp3dev:
Well, probably msm7227 does not need it, but qsd8250 does. In fact, you should start from downloading LK from CA, comparing smem/rpc against linux values and if they differ, port code from our 7200A LK. You should be able to boot lk.bin via haret with the script provided before.. Sorry, but you need to look yourself, I don't have time to support yet another device now.
[HD Mini Android Development] munjeni:
I tried to boot lk without sucess (tried 0x200000 tried 0x2820000 tried 0x2exxxxx tried 0x10000xxxx address) no way to get it. I see lk use dex calls, but we used raphael smem/dex only for battery, microphone and to set low speed/sleeping, I do not know other dex definitions is compatible for photon, it is problem now! There is alot of dex calls..

Is there any "primitive" "hallo" bootloader? I want to see if it is able to boot or I need to change radio or something other? If I see "hallo" on my screen than I will try to get something! Any way to see dmesg or something from kernel? No jtag pinouts for photon! No one want to help! All asking money! I asking him again to pay him, he say we not use money...etc! No .pdf documents...etc, so hard job with photon!
[HD Mini Android Development] sp3dev:
well, if there's dex, it should be compatible. but you don't really need dex unless you want to control display power. you should try to replace all rpc clock stuff with setting them on arm11 via the clock code ported from linux (as done for msm7200A). I cannot test it but if you don't have success with it, I'll try to make some test version by the end of next week
[HD Mini Android Development] munjeni:
It will be great, thanks!

haret is ported for photon to use 0x200000 instead of "set ramaddr 0x00000000", also kernel is ported to boot from 0x200000, I need to change "set ramaddr and kernel offset" or not need? Also I can not see haret in mtd dump, hmmm, why? Where is tags from haret startup.txt in mtd, I can not see? In ram? How to dump ram? ...etc...etc , curently I am in learning mode (I buyed hd2 from that reason)
[HD Mini Android Development] sp3dev:
You must use 0x0 for LK because it sets irq and special mode handlers at 0x0 (this is default for arm. you can probably override it for armv7, but msm7200A is armv6 so I don't know for sure)

You can use haret to operate on physical memory

like

pfw 0x10000000 1 0xdeadbeef writes 0xdeadbeef to 0x10000000

pd 0x10000000 0x4000 dumps 0x4000 bytes from 0x10000000

also

vfw, vd operate on virtual memory
[HD Mini Android Development] munjeni:
Ok, I know that, I replaced some butes (rsa modulus) from spl but it reset to normal after reboot (good thing, I not bricked my device :)), allso I tried android side to hack spl (see wifi_nvs.c from my git, but after reboot all back to normal spl), only I not understand why phys memory offset is different from haret and from mtd (I dumped spl haret side, spl is located at 0x0, but after dumping spl from mtd (photon-debian side) spl is located in 0x2400000. Do you know how to use haret to execute something, example: uploading spl to memory (I use pfw, ok), disabling mmu...etc(not know how), executing spl (not know how)? I seen on some irc chats, spl have crc checksum, what will be if I upload modified spl to memory, do I need to change crc of the spl? I tried jumpspl (added Cotulla asm code), but spl could not be loaded (I see nothing after boot), only I loaded Cotulla dumped sspl (dumped from photon memory) with jumpspl , but I seen only black screen on boot! So it mean sspl can booting but something is wrong, but spl not booting (no way to boot it).
[HD Mini Android Development] sp3dev:
You have a mess in your head ;)

mtd is nand. of course the offsets in mtd and ram can be different. to write to ram at 0x0, you need to disable mpu.

do a

pfw 0xa8250800 1 0x0

to disable smi mpu (0x0)

pfw 0xa8240800 1 0x0

to disable ebi mpu (0x10000000)

after it, you can load spl to ram via jumpspl or haret. but you don't need to mess with spl, just with LK
[HD Mini Android Development] munjeni:
Is it safe? I will see mpu disabled? How to know if it is disabled?
[HD Mini Android Development] sp3dev:
If you write sth to say 0x1000 and can read it back - mpu is disabled. It is safe unless you disable the nand mpu (which is another register)
[HD Mini Android Development] munjeni:
Hmm, how to write sth, I not understand?

Now I looked in lk code for Kovsky and Rhodium, sorry I can not do it, it is hard job for me to port to photon, I need to do it from begining, but I am not c developer, I am php/web developer, I understand something in c but not have knownledge to create new code for photon. I will be happy with tinboot, sorry!

Please, we will make donation to you, you will buy photon and finish nand boot, ok?
[HD Mini Android Development] sp3dev:
You can try tinboot, but that's not much easier and you won't be able to use recovery. I am not sure about donations, but I'll think that over
[HD Mini Android Development] munjeni:
If you are ready to do the porting lk for the photon we will easily organize the donation for you! Many many peoples reading this forum, Chinese forum, Rusian forum...etc and waiting any new news about photon progress/fix. I agre obout recovery but it is needed now? I think yes and no. If option fota update is needed now? I think not becouse nand image will be in nbh format. We need menu like in magldr, tetris, boot ad sd...etc? I think not needed, for sd card boot we have haret, for hard reset we have mtty ot putty...etc. We need hspl? I think not becouse we have sspl and we not want to brick device. Only we need is to have option "simple bootloader", with that option I will be happy to see zImage and initrd booting from nand! LK is great but need team work to finish port for photon. If I got something, learn something, I will not steall tutorials, steal code...etc, all we be explained in details, how to, where, what, why...etc, maybe I will create simple aplication in php language for generating nbh like my project in php csx...
[HD Mini Android Development] sp3dev:
The whole idea about NAND and recovery is to flash the bootloader nbh once and use recovery to install updates from now on and never use nbh. This gives a lot of options like installing themes for CM.

If you want me to work on HD Mini, you should discuss it with people from the 4pda.ru. I don't currently have a bank card and therefore cannot use paypal for large sums of money, therefore I'd prefer that someone in Moscow gets the device and gives it to me.
[HD Mini Android Development] munjeni:
I think Rusian guys reading our forum, I think it will be organized soon!
[HD Mini Android Development] HALOHA:
I try it:

step1---type:su

Show I got superuser power.

step2---type:busybox ifconfig eth0 hw eth "0E:00:A0:03:1E:FF"

then show 「SIOCSIFHWADDR:No such device」

And Mac address still not be changed.....

BUT THANK YOU FOR YOUR IDEA TOO.
[HD Mini Android Development] Ciccius:
wifi must be ON
[HD Mini Android Development] old.splatterhand:
If somebody is interested in a working Sense Theme for CM 7 look here:

Push me
[HD Mini Android Development] HALOHA:
OK I try it again..........

Step1---open WIFI and not connect to my AP.

step2---type:su

Show I got superuser power.

step3---type:busybox ifconfig eth0 hw eth "0E:00:A0:03:1E:FF"

this time show nothing

step4---type:busybox ifconfig

Show the new MAC address!!!

Than I try to connect my AP...but can't succeed now.

I reboot my phone.MAC address auto change to old one.

And can connect to my AP again.

But still need to THANK YOU .maybe something I need to note??
[HD Mini Android Development] milan7171:
in nand android in hd mini screen is cutting,can anybody improve it?