yashsingh1/xdaforums huggingface dataset:
[Touch HD Android Development] fagyi:
I think it will be lot of work but its really possible, im working on it the right repo but this need time too. I know that some people hate me but one thing its just for blackstone users!!!

May be im a wrong but only one its really some time building everythings for right

Tapatalk 2-vel küldve az én Skate-ről
[Touch HD Android Development] Lothaen:
Are you able to post here when it's working or are there some issues there?

Thanks
[Touch HD Android Development] mfsr98:
only issue now is wifi (at least main issue).
[Touch HD Android Development] ich1991:
Hey

Just installed the Rom "BLAC-NAND-AOSP-GB-IceBread-edition-2012-09-10-Gapps-preinstalled.zip" its incredible smooth and stable. Just got an issue with the camera, it says it cant connect to camera any idea on this?

and i just wanted too know if you still working on wifi and 2g/3g? Hope so :rolleyes:

Btw why is the nand thread closed?

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Touch HD Android Development] mfsr98:
you better go to the "other site". For some reason the thread is closed (haters, haters...) 2g/3g works now, one more time, go to the "other site". Yes, camera is having problems, but one more time you should REALLY go to the "other site".
[Touch HD Android Development] Lothaen:
its a minor thing but it might be sensible to bung in a much smaller/simpler boot animation - it makes it look really slow booting :-p

ringtones don't work (but i think thats a known issue)

bluetooth and wifi don't work (again known issues)

other than the above its pretty smooth - makes calls - shame you can't hear an incoming call :)
[Touch HD Android Development] mfsr98:
You don't ahve the latest version I think. Go to the "other site", I guess :p
[Touch HD Android Development] Lothaen:
Care to PM me a link? I couldn't see it whatever site I visit
[Touch HD Android Development] adifeticu:
Hello

After almost one year of waiting i was instaled BLAC-NAND-AOSP-GB-IceBread-edition-2012-09-10-Gapps-preinstalled rom in my Blackstone. Very fast and stable OS. Problems meet are with camera, wi-fi, and BT, data comunications over GSM work fine. Another problem are when i turn off the phone, its freezing and must remove the battery, and when i want to open MUSIC aplication a meesage appear scanning sd card and another message wiht error accesing sd card apear even if i can acces sd card with file manager. I will inform you if are another problem.

Anyway congratulations for your work.
[Touch HD Android Development] mfsr98:
Not a message to post here...
[Touch HD Android Development] robbie2k:
Which "other site"??
[Touch HD Android Development] fagyi:
Hi all!

New build coming Saturday to the public. If anyone want test it.

Working on very hard with Kernel and wifi but Im very busy in my life/job at the moment.

Audio method same as via SD just csv files not reading from sdcard moved to the system/etc and reading from there. So this is a new htcacousic code which we using on SD build some day but now i can say that audio its done.

Just shortly:

Audio fully working ?

YES!

So we need a audio trick for enable ?

NO!

Audio Shuttering ?

NO!

Ringtone working ?

YES, with Cyantone as default from ICS

_____________________

and shortly:

- Synced with the latest google source 2012.09.25.

- Gsensor working now

- Battery usage : 9 hr 17 min -> 18 % lost -> sleep mode

- Incoming ringtone working on default. Cyantone ported from ICS and setting up to the default ringtone. I just love this ringtone.

- Audio rebuild to the latest htc-acoustic_wince

- Audio fully working now on nand, you need forget the trick

- Build.prop setup

- Boot.img configurations updated ( big )

- Better overall speed.

Kernel

- h2w support ( new headset )

- New acoustic_wince code base and neccessary modification for blackstone

- Shutter in music? not anymore

- Added camera support and neccessary drivers - seems to be need a minor fixes but it looks good.

- Config updated

- Clock-wince changes

- Improved shutdown and reboot funkcion. - seems to be need a minor fixes but it looks good.
[Touch HD Android Development] Lothaen:
sounds good!
[Touch HD Android Development] mfsr98:
it doesn't sound, it really IS good!
[Touch HD Android Development] fagyi:
Got it Bluetooth working on nand. Hope wifi too in the future.

Good night all
[Touch HD Android Development] fagyi:
Good news,

Got it camera working too.

Only big issue the wifi so far.

My tester said that BT audio working without noise with 3 car which is never working before on blackstone for example all SD version!
[Touch HD Android Development] masrterk:
Great news can´t wait for a new Nand Rom

thanks
[Touch HD Android Development] samizzlah:
Don't give up all hopes yet! Alot happening at neopeek

http://www.neopeek.com/viewtopic.php?f=12&t=5637
[Touch HD Android Development] willhard1986:
waiting for....
[Touch HD Android Development] Bunnybugs_007:
Well, I guess that it shouldn't be this hard... Not that I am such a geek or so, but what I know of regular computers with windows and linux is that it just takes to time to create a map and rewriting drivers.

Android is still open source, why don't we start making a complete new ROM? HTC has succeeded to make Android ROM's for other devices with WM as well, and it wasn't a problem. Just a stupid thing, but they might be interested in the work that is done here? I mean, they don't make up all of their code by themselves;)
[Touch HD Android Development] Srage87:
i would even donate for a stable nand android to get rid of my windows permanently from my blackstone.
[Touch HD Android Development] daddyload2:
So we could use these 2 files as the Hardware of Huawei U8150 is the same..?!

For me this sounds great (i'm not a geek - i don't know much )

if we only need to trace the NAND memory access points via haret to input the correct values into the tinboot source AND create a nbh with a kernel and all other relevant files (from U8150) to initialise tinboot?!?

Or did I missed something? :confused:

Go chefs, go! :):D
[Touch HD Android Development] g3rm0:
Well, we will need to add a lot of hardware init and proper drivers because now winmo does most of it for us.

ALSO, Huawei is not even remotely similar to our Blackstone. Sure... CPU is the same (and it's working v. good for us anyway). All other hardware (the stuff that gives us troubles) is completely different. Hell... HTC Sapphire and Hero are a MSM7k2 Android devices made by HTC and they're still very different.

Good news is the devs are thinking about switching to a new kernel and simultaneously start NAND development for all devices (same one for all approach as current "HaRET" kernel). Unfortunately there are some bugs (and of course camera) to fix before any of that can happen. Anyway, keep your fingers crossed ;)
[Touch HD Android Development] moharu:
well

i can say it will take a long time

but at least it is happening :)
[Touch HD Android Development] tatotata:
me too :)[/QUOTE]me too:)
[Touch HD Android Development] toricky2005:
Really waiting for it!!!!!!
[Touch HD Android Development] matthijs.o:
Please developers, release me from WiMo on my Blackstone!!! I can not wait for a native android rom for my phone!!!
[Touch HD Android Development] Stickman89:
Ok I understand NAND is going to be fairly difficult atm but it doesn't stop us getting Tinboot initialised and booting builds from SD Card.

Going through config files now and preparing work, need to get the correct information to update the following file for us blackstone users:

@
@ Tinboot V 1.0
@ Very simple bootloader for HTC Vogue
@ Martin Johnson - M.J.Johnson@massey.ac.nz
@
.ifdef kaiser
.equ LOAD_START, 0x10300000
.else
.ifdef polaris
.equ LOAD_START, 0x10300000
.else
.equ	LOAD_START,	0x10000000
.endif
.endif
.equ	RAM_START,	0x10000000
.equ	RAM_SIZE,	0x03000000
.equ	INITRD_START,	RAM_START+0x00800000

.equ	KERNEL_OFFSET, 0x8000
.equ	XIP_END,	0x0100000

.org 0
b boot

.org 0x40
.word 0x43454345
.word romhdr+0x80000000	@ location of wince romhdr
.word romhdr
.org 0x100
tags:	.word 5,0x54410001,1,0x1000,0	@ ATAG_CORE, pagesize=4K
.word 4,0x54410002,RAM_SIZE,RAM_START	@ ATAG_MEM
.word 4,0x54420005,INITRD_START,fin-initrd	@ ATAG_INITRD2
cmdline_start:	.word (cmdline_end-cmdline_start)/4,0x54410009	@ ATAG_CMDLINE

.ifdef rhod500
.asciz "gsensor_axis=2,1,3 msmvkeyb_toggle=off htc_hw.force_cdma=1 panic=0 pm.sleep_mode=2 lcd.density=240"
.endif

.ifdef rhod400
.asciz "gsensor_axis=2,1,3 msmvkeyb_toggle=off htc_hw.force_cdma=1 panic=0 pm.sleep_mode=2 lcd.density=240"
.endif

.ifdef rhod210
.asciz "gsensor_axis=2,1,3 msmvkeyb_toggle=off htc_hw.force_cdma=0 panic=0 pm.sleep_mode=2 lcd.density=240"
.endif

.ifdef tilt2
.asciz "gsensor_axis=2,1,3 msmvkeyb_toggle=off htc_hw.force_cdma=0 panic=0 pm.sleep_mode=2 lcd.density=240"
.endif

.align
cmdline_end:	.word 0,0	@ ATAG_END

.org 0x00001000

boot:	ldr r0,loadstart_ptr
ldr r1,ramstart_ptr
ldr r3,fin_ptr

copycode:	ldr r2,[r0],#4
str r2,[r1],#4
cmp r1,r3
blo copycode
ldr pc,start_ptr

start:	ldr r0,initrd_ptr
ldr r3,fin_ptr
ldr r1,ird_start_ptr

copyinitrd:	ldr r2,[r0],#4
str r2,[r1],#4
cmp r0,r3
blo copyinitrd

mov r0,#0
ldr r1,mtype
ldr r2,tags_addr
ldr pc,kernel_start

mtype:	.word MTYPE
start_ptr:	.word start+RAM_START
loadstart_ptr:	.word LOAD_START
ramstart_ptr:	.word RAM_START
initrd_ptr:	.word initrd+RAM_START
fin_ptr:	.word fin+RAM_START
ird_start_ptr:	.word INITRD_START
kernel_start:	.word RAM_START+0x8000
tags_addr:	.word RAM_START+0x100

romhdr:
.word 0x0	@ dllfirst
.word 0x0	@ dlllast
.word 0x80000000	@ physfirst
.word 0x80000000+fin	@ physlast
.word 0	@ num mods
.word 0x80000000+fin	@ ramstart
.word 0x80000000	@ ramfree
.word 0x83000000	@ ramend
.word 0	@ copyentries
.word 0x80000000	@ copyoffset
.word 0	@ profilelen
.word 0	@ profileoffset
.word 0	@ numfileshy
.word 0	@ flags
.word 0x20	@ fsrampercent
.word 0	@ drvglobstart
.word 0	@ drvgloblen
.word 0x201c2	@ cputype/flags
.word 0x80000000	@ pextensions
.word 0	@ trackingstart
.word 0	@ trackinglen

.org KERNEL_OFFSET
kernel:
.incbin "kernel/zImage"
initrd:
.incbin	"kernel/initrd.gz"
.align
fin:

Best Regards,

ST1Cl<^^aN
[Touch HD Android Development] chris1a3:
same here....

gudluck to all developers..
[Touch HD Android Development] Stickman89:
For Reference:

RAMADDR=10000000

RAMSIZE=0d000000

0x64000000 (tags)

0x64001000 (kernel)

0x6418c000 (initrd)

0x64580000 (index)

Best Regards,

ST1Cl<^^aN
[Touch HD Android Development] g3rm0:
Nice find, but after comparing Vouge/Rhod/Diam tinboot sources I think we need only those lines changed (or confirm they're correct):

.equ	RAM_SIZE,	0x03000000 @this one is probably ok

.equ	XIP_END,	0x0100000 @no clue about this one

--- .ifdef rhod500
---	.asciz "gsensor_axis=2,1,3 msmvkeyb_toggle=off htc_hw.force_cdma=1 panic=0 pm.sleep_mode=2 lcd.density=240"
--- .endif

+++ .ifdef blackstone
+++ .asciz "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=-2,-1,3"
+++ .endif

After that we will need modified initrd.gz (I'm sure [ACL]'s one will work w/o doing much) and NAND kernel for Blackstone. This last step will be most difficult since we can't use Rhod's NAND kernel - it's too device specific.
[Touch HD Android Development] cucuko:
re

waiting...
[Touch HD Android Development] Kapie:
yeh i want this too :D
[Touch HD Android Development] Mjuksel:
a smooth running NAND rom on the Touch HD aka Blackstone would be a dream come true !!
[Touch HD Android Development] accountabc:
They seem to be making progress booting topaz from NAND:

http://xdaforums.com/showthread.php?t=917287
[Touch HD Android Development] Stickman89:
Ok building NBH now to test.
[Touch HD Android Development] xdmcdmc:
Hi, I was able to compile a nbh for blackstone.

I have attached the modified scripts I used to compile the xip and nbh tinboot image.

After flashing the nbh and booting, I felt 2 consecutive vibrations (same as booting android via Haret on SD) followed by some text that I wasn't able to see, visible were only first 1 or 2 chars of each line, so basically I've got:

[

[

[

[

...

Rest of the text was hidden by HTC spashscreen.

Maybe somebody has an idea.

I have attached also the nbh file. I had problems seeing the SD card in the past so maybe some of you can test and post feedback.

Regards
[Touch HD Android Development] Kapie:
so it didn't work?
[Touch HD Android Development] Stickman89:
makenbh.sh seems to be broken for me...
[Touch HD Android Development] xdmcdmc:
It didn't work. At least for now. I will have to find a way to solve the display issue.

After that I will be able to continue the investigation.
[Touch HD Android Development] Stickman89:
got gmail?
[Touch HD Android Development] xdmcdmc:
@Stickman

Hi, I don't have a gmail account, but how may I help you?

What it doesn't work for you?
[Touch HD Android Development] Stickman89:
It's cool I don't need help, my environment is setup different. I've already created a new script that works for me.

Best Regards,

ST1Cl<^^aN
[Touch HD Android Development] Thegn:
It glads me to hear that progress is being made with Tinboot! Things have been slow here on the Blackstone forum. Most of us user have to look at the Tilt, Rhodium (etc) parts of the forum in order to get Android news.

Hope we can get a working Tinboot! :-)
[Touch HD Android Development] Stickman89:
No go for me too, Incorrect RAM_START I believe, trying again...
[Touch HD Android Development] g3rm0:
So it's not booting at all?
[Touch HD Android Development] Stickman89:
It reaches the HTC splashscreen then it vibrates twice and I can see part of tinboot verbose in the upper left corner and then it freezes.
[Touch HD Android Development] g3rm0:
Ehh... that's a shame. I was pretty sure that values pulled from Rhod's tinboot setup would work. Guess we'll need to recheck them. Anyway - good try Stickman89. I assume you won't stop trying now ;)

I hope I'll have some time to give it a try during weekend (if I won't be busy... again:S)
[Touch HD Android Development] moharu:
at least we got to a stage

we could ask for some developers to show us tricks or tweaks
[Touch HD Android Development] xdmcdmc:
I have tried several combinations already with same result, I believe it should boot but it doesn't because something is wrong on tinboot source file (most sure a memory address probably is diff than what we have there).

Regards

Also, I already had a look at kernel sources and found the files for our blackstone. Bootloader already run some kernel code and make some initialization there (double vibration is executed in the kernel, I found the code that does that). But we need first to fix the display issue, without this I can't tell what is wrong. After that is fixed we could start debugging and solve the issue.
[Touch HD Android Development] Kapie:
i hope you will succeed. Good luck!
[Touch HD Android Development] st3ph3nt3:
Wow.. At least we know our blackstone have hope in android os.. This is getting very exciting. Blackstone community is quietly waiting for the big news..Keep it up guys.. :D
[Touch HD Android Development] moharu:
too quiet

but atleast something is happening
[Touch HD Android Development] g3rm0:
Well successful jump to kernel is good news, but no verbose mode is a PITA. Also, don't expect it to boot. It should eventually crash/freeze somewhere before Android bootanim. That's because the Rhod NAND kernel is too device specific.

On the other hand - Blackstone board/panel code is such a mess. I don't know who's gonna clean it up (it will be needed for NAND eventually) :S

BTW. Ram memory address is 0x10000000 (phys) on all our devices so don't change that - you might brick your device. Ram size shouldn't have to be bigger than 0x03000000 and I wouldn't go over 0x06000000. I'm not sure about XIP end but it shouldn't matter that much. My bet is your issue must be kernel related.
[Touch HD Android Development] [ACL]:
Tinboot itself isnt the issue. If you hear a vibrate during the boot process it means kernel actually loaded. Read the damn code !!!!

Also i'm not sure what kernel yall are using. Haret kernel wasnt designed for nand. :-)

Also, lets pay some respects to the author of Tinboot .. The all mightly DZO.

Best of luck to you folks.
[Touch HD Android Development] Stickman89:
Yes I know ACL, since we never had a nand kernel in the first place I was simply preparing tinboot for action, I'm aware it's the kernel we need to work on hence why I have started on it already.

I was there all the way when DZO took over our current progress on porting his vogue tinboot for the kiaser, we were all very grateful and am still to this day on his work and dedication to give our old devices a new lease of life.

Since we are quite litterally getting next to no help we are aware this is not going to be a quick and easy task, but I am prepared to learn whilst I'm at it as I enjoy setting myself a challenge.

Best Regards,

ST1Cl<^^aN
[Touch HD Android Development] [ACL]:
Do you at least have some dmesg logs to see how far the kernel is getting?

i'm not sure how far you got but if you get some logs, then we can begin to get this moving.
[Touch HD Android Development] xdmcdmc:
Hi [ACL],

First of all it's an honor to have you here and thanks a lot for that.

Of course, you are right, we will pay our respect to DZO, you and all other guys that helped or will help achieving nandboot for our old devices.

As Sickman pointed out, we get almost no help, so I'm glad to see that you are watching this.

First I have tried with haret kernel and of course it didn't work. Next I have compiled the kernel you have made public available for rhodium, cause I think it will be a good start for this project:

git clone git://gitorious.org/~acl/linux-on-qualcomm-s-msm/linux-msm-rhod-nand.git

With this kernel I had same results so far, the same Sickman has reported, kernel was loaded (double vibrations) but overlapped verbose by spashscreen.

So far I didn't saw any dmsg logs, I believe I shall saw them on SD card right?

@g3rm0 Hi, indeed I din't changed the start address or address size and I also believe something is wrong in the kernel. I need a way to be able to see the logs, without that will be hard next to impossible to make progress.

Thanks to all of you for you help.
[Touch HD Android Development] Thegn:
I'm glad to see you here, and that you are joining forces with xdmcdmc, Stickman89, g3rm0 and others. Blackstone has been nearly forgotten and placed in the backwater far too long!

Is there a way we other (ie non-coders), can help in any way, please say. Maybe we could help with getting logs or something else. Just tell us how, and what you want. :)

Cheers!
[Touch HD Android Development] xdmcdmc:
Hi, I've managed to make some progress. Not only the kernel is loaded but also get the logs of boot process on SD card and data store (data.img) is created. Not sure if the following behaviour is right, but for now I see only the splashscreen (no verbose mode) and I have to remove the SD card from the device and look at logfile in order to see the progress.

All the time the log file ends with:

[ 14.429504] mmc1: host does not support reading read-only switch. assuming write-enable.

[ 14.429840] mmc1: new high speed SDHC card at address aaaa

[ 14.444213] mmcblk0: mmc1:aaaa SU08G 7761920KiB

[ 14.445434] mmcblk0: p1

I believe it has a problem with my SDCard but not sure.

Also something odd, some commands are not recognized:

[ 0.000000] Kernel command line: gsensor_axis=-2,-1,3 msmvkeyb_toggle=off lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=528 pmem.extra=1

[ 0.000000] Unknown boot option `lcd.density=240': ignoring

[ 0.000000] Unknown boot option `clock-7x00.a11=528': ignoring

[ 0.000000] Unknown boot option `pmem.extra=1': ignoring

I believe lcd.desnity param should be just fine!!!!

Maybe some more experienced developers can take a look at log file.

I believe we already need some testing on this (cause my SDcards have some issues):

Please try this only if you know what are you doing, otherwise you could loose data or stuck not knowing how to restore windows mobile!

1. Prepare SD card if you don't have it already setup with android (format FAT32, copy Android files to root or /andboot folder).

2. Extract modules-2.6.27.46-01231-g4b2e5f3.tar.gz to sdcard root or /andboot folder and erase any old module file (just to be sure).

3. Write new nbh file to device.

If need more help with setup please just ask.

The nbh file with CustomRUU can be found in BlackstoneNand.zip.

After booting and feeling one or two vibrations please let device run for some time, android will start to create data.img storage and this takes some time. If nothing happens after 4-5 minutes please remove SD card from device and using a card reader get "dmesg.txt" file from card root and post it here.

Also report any verbose mode if you see or any other info that could help.

It will help a lot if somebody that already runs Android fine via Haret will test this.

Regards

VERY IMPORTANT:

In order to enable logging you need to add following command to config file in custom shell commands block:

dmesg >> /sdcard/dmesg.txt

In the end that block should look like:

# custom shell commands, these commands run last

custom_shells{

rm -f /sdcard/fsck*.rec

dmesg >> /sdcard/dmesg.txt

}

The config file is located in /config folder and I have attached an example for froyo (aka Android 2.2)
[Touch HD Android Development] am20033:
hi all

i really would like to help you guys but first i want to ask few questions. is it possible to brick the phone or do i just lose my windows data? is it possible to restore my phone by flashing a windows rom from the bootloader?
[Touch HD Android Development] g3rm0:
pmem.extra=1 and clock-7x00.a11=528 are not used anymore IIRC. Maybe lcd.density was also hardcoded?!

I know that some cards are affected by wrong clock setup in Alex clock commit. It gives me "Waiting for SD Card..." error and it worked fine before. Don't know how it affects NAND but I have a feeling something else is wrong (but I do have a patch for this... just in case). You should pastebin full dmesg and ask devs @ #htc-linux for help. Also, may I ask which kernel you're using?

Unfortunately it's possible to brick you device this way (as always when flashing experimental roms), however if you can access bootloader you should be able to flash winmo rom back w/o problems.
[Touch HD Android Development] xdmcdmc:
@am20033 Hi, the nbh contains only the OS part, so it doesn't mess with bootloader, radio or spashscreen. Now, I can tell you that I bricked my old diamond 1 just writing all over again custom made roms on it, so you never know. I believe nobody can guarantee 100% that you won't brick your phone.

Normally you shall flash my nbh and after getting the log file just flash back the old rom using bootloader (vol down + reset).

Good luck.
[Touch HD Android Development] xdmcdmc:
I use the kernel modified for rhodium devices from:

http://gitorious.org/~acl/linux-on-qualcomm-s-msm/linux-msm-rhod-nand.

Blackstone code in the kernel is using a lot of code from rhodium too, so I believe this is a good start point.

Thanks for the info regarding commands :)
[Touch HD Android Development] [ACL]:
I see.

What changes did you make to get it to go this far? i can patch my kernel so you can benefit from our autobuilds.

Also a lot of changes we made kill other devices so i will see if i can get some fixed up. Microp code for example is completely broke for anyone else besides rhod.

Look for example we killed backlight control on the microp code.

[ 13.983581] Registered led device: <NULL>

So PM me the base patch and i will try to get to the point where we can at least get android up. Also let me know what tinboot changes were made as well.