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

[[ACL]]

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

#
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]

Originally Posted by [ACL]

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

#
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]]

just one last one..

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..

[Lmiller1708]

Originally Posted by [ACL]

just one last one..

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..

Here is my tinboot folder. Hope it helps!

[coolsilver]

Commit and I'll flash away.

I've just been too lazy to rebuild my dev environment.

[tiad8]

@ THE A TEAM

I been following you guys for a long time. I have so much respect for this team. You guys are true hereos in my book.

I have never seen a team of people like you guys. It's just simply amazing works. The XDA, PPC. WE ARE REALLY PROUD TO HAVE A TEAM LIKE YOU GUYS.

THANK YOU GUYS FOR YOUR AMAZING WORK

FROYO X/SPRINT TOUCH PRO 2/RHOD

[[ACL]]

Originally Posted by tiad8

@ THE A TEAM

I been following you guys for a long time. I have so much respect for this team. You guys are true hereos in my book.

I have never seen a team of people like you guys. It's just simply amazing works. The XDA, PPC. WE ARE REALLY PROUD TO HAVE A TEAM LIKE YOU GUYS.

THANK YOU GUYS FOR YOUR AMAZING WORK

FROYO X/SPRINT TOUCH PRO 2/RHOD

thanks dood. You are my first target. I'm cooking up a large post bout the rom process. I've yet to commit the camera portion to the kernel but once thats done you can go to town.

[tiad8]

Originally Posted by [ACL]

thanks dood. You are my first target. I'm cooking up a large post bout the rom process. I've yet to commit the camera portion to the kernel but once thats done you can go to town.

Your the man buddy plus the A TEAM

thanks

FROYO X/SPRINT TOUCH PRO 2/RHOD

[natemcnutty]

ACL, I'm custom building a busybox for us, and I've already compiled a flash_erase from the latest mtd utils. I currently have the initrd.gz at 1.1 MB, but I think I can shave quite a bit off if I remove some of the unnecessary stuff from busybox.

Here's what I need to know. Do we only need the commands that are used in initrd.gz and init.rc to be referenced to busybox, or do we need all of the commands that are in the /bin folder for initrd? There are quite a few commands in there that we do not use, and I'm wondering if I need to keep them, or if I can just add them in the future if we need them.

Once finished cleaning that up, I think we can get initrd.gz under 1 MB. I also think we can clear up another 3 MB of space by shifting the partition table, but I'll play with that later. Also, I'm still not sure why we are starting at an offset of 64MB for our partitions, and we can reclaim some of that space if we can find where it is safe to move it to. I'm trying to get us enough space in the system partition that we can accommodate the chefs while still having plenty of room for user date

[[ACL]]

Originally Posted by natemcnutty

ACL, I'm custom building a busybox for us, and I've already compiled a flash_erase from the latest mtd utils. I currently have the initrd.gz at 1.1 MB, but I think I can shave quite a bit off if I remove some of the unnecessary stuff from busybox.

Here's what I need to know. Do we only need the commands that are used in initrd.gz and init.rc to be referenced to busybox, or do we need all of the commands that are in the /bin folder for initrd? There are quite a few commands in there that we do not use, and I'm wondering if I need to keep them, or if I can just add them in the future if we need them.

Once finished cleaning that up, I think we can get initrd.gz under 1 MB. I also think we can clear up another 3 MB of space by shifting the partition table, but I'll play with that later. Also, I'm still not sure why we are starting at an offset of 64MB for our partitions, and we can reclaim some of that space if we can find where it is safe to move it to. I'm trying to get us enough space in the system partition that we can accommodate the chefs while still having plenty of room for user date

Right now to get it to be small i removed e2fsck from the bin folder. This is because we dont check on ext2 partitions anymore so no need to have it there. That file alone is pretty big so im going to commit my change. This isnt part of busybox, but the vogue script supported ext2 img files which we dont, so it can be removed.

Well the system partition already has its own bin directory with all the goodies possible so the busybox for initrd should be the bare essentials to boot and run the install script. So i think we will be safe with a small busybox.. I think we should be good to test your busybox.

edit: oops.. not a bin directory but xbin is on system. Not sure if it has a full busy box in there..

Edit2: Also here is the latest install, update and install-seq

You are big boys so you can make your own NHB and harvest your own modules and apply it to the android update. Wifi is working for me but i cant test cdma data. I'll leave that up to you fellas.

http://htcdevs.wirelesstcp.net/files/xdandroid/