NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery - Page 121

**Lmiller1708** · #**1201** (**permalink**) 02-11-2011, 05:20 PM

Quote:

Originally Posted by natemcnutty

Also, I've been messing with busybox, but menuconfig is broken for me, so I can't selectively decide what is including vs what isn't without manually editing every MAKEFILE in the structure. It's not going so well, but the basic busybox from defconfig is only 1MB. We could just use that and then include format_flash separately. Still looking into it all right now. With mtd_utils, I think I can actually get all the flash info I need for offsets without needing mtty

I had this problem earlier. If you can't see the options then you don't have access to your MTD.
Change your MTD command Line to what I have. Or just get rid or your '-'.

manekineko · #**1202** (**permalink**) 02-11-2011, 05:21 PM

Quote:

Originally Posted by natemcnutty

I think they are referring to this:
Commit in eclair-rootfs in XDANDROID Eclair - Gitorious

I still don't think that is the fix, but you could try updating the file in your system and see if that helps.

That's not the fix, this is the system server fix:
Commit in rootfs in XDAndroid - Gitorious

**arrrghhh** · #**1203** (**permalink**) 02-11-2011, 05:25 PM

Quote:

Originally Posted by natemcnutty

I think they are referring to this:
Commit in eclair-rootfs in XDANDROID Eclair - Gitorious

I still don't think that is the fix, but you could try updating the file in your system and see if that helps.

That's not the correct commit.

I'll try to find it, hold please.

Heh, manekineko beat me to it

.

**Lmiller1708** · #**1204** (**permalink**) 02-11-2011, 05:33 PM

Quote:

Originally Posted by manekineko

That's not the fix, this is the system server fix:
Commit in rootfs in XDAndroid - Gitorious

That did the trick!

Just applied it with androidupdate.tar

Now... Data.....

**[ACL]** · #**1205** (**permalink**) 02-11-2011, 05:40 PM

Quote:

Originally Posted by Lmiller1708

That did the trick!

Just applied it with androidupdate.tar

Now... Data.....

now you see the power of android update huh.. its just pure sexyness..

coolsilver · #**1206** (**permalink**) 02-11-2011, 07:10 PM

So... should I be grabbing a usb cable?

**Lmiller1708** · #**1207** (**permalink**) 02-11-2011, 07:40 PM

Nate/ACL,
I haven't tried it yet but I bet our cmdline mtdparts could change to something like this.

Code:

mtdparts=msm_nand:0x20000000@0x0(nand),0x01500000@0x04000000(root),0x07BA0000@0x05500000(system),-0x06f600000x0D0A0000(userdata)

I'm not sure if that will make a difference or not but it sounds correct, because the Vogue has 256MB of ROM while the TP2 has 516MB.
In my dmesg.txt this is what my mtdparts look like:

Code:

[    7.477172] 4 cmdlinepart partitions found on MTD device msm_nand
[    7.477294] Creating 4 MTD partitions on "msm_nand":
[    7.477447] 0x00000000-0x10000000 : "nand"
[    7.594635] 0x04000000-0x05500000 : "root"
[    7.607391] 0x05500000-0x0d0a0000 : "system"
[    7.690460] 0x0d0a0000-0x20000000 : "Partition_003"

The last one should say userdata but it doesn't...

If I Cat mtd partitions:
mtd1: 21 MB
mtd2: 123 MB
mtd3: 368 MB

Edit: If we change these values then a bunch of other values in tinboot will have to change too..

Edit2: Ok, all this crazy talk has a reason... Once I boot. I have a bunch of the default widgets on the home screen, I then reboot and some of the widgets will not be there.

Here is what I think the tinboot script should look like.. again untested... (Note:I also removed the if statements)

Code:

@
@ Tinboot V 1.0
@ Very simple bootloader for HTC Vogue
@ Martin Johnson - M.J.Johnson@massey.ac.nz
@
.equ    LOAD_START,     0x10000000
.equ    RAM_START,     0x10000000
.equ    RAM_SIZE,     0x0E600000
.equ    INITRD_START,     RAM_START+0x00800000
.equ    KERNEL_OFFSET,  0x8000
.equ     XIP_END,     0x2ff000

        .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 acpuclock.oc_freq_khz=786432 mtdparts=msm_nand:0x20000000@0x0(nand),0x01500000@0x04000000(root),0x07BA0000@0x05500000(system),-0x06f600000x0D0A0000(userdata)"
.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:

Edit again..: Updated tinboot above to something that boots.

**[ACL]** · #**1208** (**permalink**) 02-11-2011, 09:52 PM

Lmiller, can you check your script.. something doesnt make sense

Code:

#
compile tinboot
cp tools/rhod_payload os.nb.payload
echo "Inserting tinboot into payload"
cat xip/$1 >> os.nb.payload
mv os.nb.payload.NEW os.nb.payload >> tools/log
echo "Inserting blank imgfs into payload"
wine tools/ImgfsToNb.exe  tools/imgfs.bin OS.nb.payload OS-new.nb.payload >> tools/log
echo "Creating os.nb portion of nbh"
tools/nbmerge < OS-new.nb.payload > OS-new.nb
echo "Creating NBH"
wine tools/yang.exe -F ruu_signed.NBH -f OS-new.nb -t 0x400 -s 64 -d RHOD****0 -c 11111111 -v Tinboot -l WWE >> tools/log

Look at lines 4 and 5. First you append the xip onto os.nb.payload, but the next line you overwrite it with os.nb.payload.NEW ?

let me know if im reading this wrong since i dont know where os.nb.payload.NEW comes from.

**Lmiller1708** · #**1209** (**permalink**) 02-11-2011, 09:57 PM

Quote:

Originally Posted by [ACL]

Lmiller, can you check your script.. something doesnt make sense

Code:

#
compile tinboot
cp tools/rhod_payload os.nb.payload
echo "Inserting tinboot into payload"
cat xip/$1 >> os.nb.payload
mv os.nb.payload.NEW os.nb.payload >> tools/log
echo "Inserting blank imgfs into payload"
wine tools/ImgfsToNb.exe  tools/imgfs.bin OS.nb.payload OS-new.nb.payload >> tools/log
echo "Creating os.nb portion of nbh"
tools/nbmerge < OS-new.nb.payload > OS-new.nb
echo "Creating NBH"
wine tools/yang.exe -F ruu_signed.NBH -f OS-new.nb -t 0x400 -s 64 -d RHOD****0 -c 11111111 -v Tinboot -l WWE >> tools/log

Look at lines 4 and 5. First you append the xip onto os.nb.payload, but the next line you overwrite it with os.nb.payload.NEW ?

let me know if im reading this wrong since i dont know where os.nb.payload.NEW comes from.

Nope You aren't reading it wrong. Remove the mv ... line.
Sorry about that.

**[ACL]** · #**1210** (**permalink**) 02-11-2011, 10:17 PM

just one last one..

Code:

wine tools/ImgfsToNb.exe tools/imgfs.bin os.nb.payload os-new.nb.payload
ImgfsToNb 2.1rc2
Using bigstorage mode

Sector size is 0x800 bytes
Writing imgfs to offset byte 0x320000, sector 0x640
Input file tools/imgfs.bin cannot be read. Exiting.

Not sure whats up with the imgfs.bin but it just poops out.. anyways i gotta head out but ill be back later..