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

[natemcnutty]

Originally Posted by [ACL]

ahh also can you verify this. You are not longer catting the xip onto the payload correct? back to the original method ?

yes, I am using the original method with the nbtools and all that. I will be playing with the cat method tomorrow just to see if it matters.

[[ACL]]

Originally Posted by natemcnutty

yes, I am using the original method with the nbtools and all that. I will be playing with the cat method tomorrow just to see if it matters.

Works like a charm. I didnt commit those changes to tinboot but i made them on the autobuild so the rest of the peeps can test from a reference build.

Index of /files/rhodium_nand/

Thanks a lot fellas.. we are almost there.

[natemcnutty]

Originally Posted by [ACL]

Works like a charm. I didnt commit those changes to tinboot but i made them on the autobuild so the rest of the peeps can test from a reference build.

Index of /files/rhodium_nand/

Thanks a lot fellas.. we are almost there.

Thanks ACL. I've got a ton more testing to do, but I did find that the cat method leaves some issues in the partition table. If we had a kernel/initrd.gz that was too large, I think it would have issues. This is probably why the Vogue uses lzma now.

When we use the nbtools, it adjusts all of the partition information based on the size of the crap we are shoving into it. I think we might even be able to build any size initrd we want using this method since it auto-adjusts the table. As long as our mtdparts partition 1 does not overlap with the fatfs partition (which would require changing tinboot code), then we are good to go.

[Boominsvx]

Originally Posted by [ACL]

also dont use the menu to install. The script is whacko and does other things its not supposed to do. So install via the script only for now.

Could this be why I'm having some trouble with this nbh? after A N D R O I D, I freeze up with "Unable to open persistent property directory /data/property errno: 2" using the files from the NAND server.

User error, or adjustment necessary?

Originally Posted by [ACL]

Works like a charm. I didnt commit those changes to tinboot but i made them on the autobuild so the rest of the peeps can test from a reference build.

Index of /files/rhodium_nand/

Thanks a lot fellas.. we are almost there.

[[ACL]]

Originally Posted by Boominsvx

Could this be why I'm having some trouble with this nbh? after A N D R O I D, I freeze up with "Unable to open persistent property directory /data/property errno: 2" using the files from the NAND server.

User error, or adjustment necessary?

Probably.. just dont use it.. use the install script.. in the andboot folder, if you have the install script it will automatically execute and do all the goodness. Once it runs it will disable itself so it does not run again.

Put this in your andboot folder with the android and updates .

http://htcdevs.wirelesstcp.net/files...install-seq.sh

Eventually this script will make it into the menu but its too xdandroid ish and wont support other builds.. so i need to come up with a happy medium where we should be able to install future builds instead of having to hack our initrd all the time.

[natemcnutty]

Originally Posted by [ACL]

Probably.. just dont use it.. use the install script.. in the andboot folder, if you have the install script it will automatically execute and do all the goodness. Once it runs it will disable itself so it does not run again.

Put this in your andboot folder with the android and updates .

http://htcdevs.wirelesstcp.net/files...install-seq.sh

Eventually this script will make it into the menu but its too xdandroid ish and wont support other builds.. so i need to come up with a happy medium where we should be able to install future builds instead of having to hack our initrd all the time.

I think we provide the script as a template, and it should get modified by the chef if needed.

As for Boominsvx, the issue he is having could also be because he did the system install without doing the update part from replimenu.

[[ACL]]

Originally Posted by natemcnutty

I think we provide the script as a template, and it should get modified by the chef if needed.

As for Boominsvx, the issue he is having could also be because he did the system install without doing the update part from replimenu.

yeah.. but then should we remove he ability to install from replimenu? Do we even need it ? I guess the wiping cache and permissions check are a good thing to have. But i wouldnt install through it. it doesnt get easier than the install script.. just sit back and let it do all the goodies.

ahh just wait till we do cyanogen.. its a different animal ..