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

[Boominsvx]

Originally Posted by Lmiller1708

Ok. Here is what I found out...
First here is my partition table:
[CODE]NBInfo 2.1rc2

..............
As you can see partitions do not make that big of a difference. What seems to matter is having the imgfs found at 0x380000. I did the math in tinboot to do this. With a little playing around too..
This boots just fine now. (For me of course )

Nate I'm yours works because the tinboot is found somewhere on the on the partitions. Not sure why mine didn't work before. Your tinboot is getting inserted at 0x20000 to where mine is inserted at 0x2000. This is what Magldr roms use. I then had to change the .org in tinboot from 1000 to 2000. Now I'm not sure at all why this was not needed to be changed before but I think it has something to do with the not having the boot section in the partition table... Just a guess.

But I would like someone else to test my latest NBH.

EDIT: Just need the NBH... Sorry forgot to remove the modules...

Lmiller, sorry buddy. Still no boot ova hea. I make for do it right. It jus no work.

Sorry, I'm la' tired. I make for sleep now.

[Lmiller1708]

Originally Posted by Boominsvx

Lmiller, sorry buddy. Still no boot ova hea. I make for do it right. It jus no work.

Sorry, I'm la' tired. I make for sleep now.

Uploading the wrong one... Sorry can you test again?
I updated the post.

[Boominsvx]

Originally Posted by Lmiller1708

Uploading the wrong one... Sorry can you test again?
I updated the post.

Still a no go. No double vibe.

[Lmiller1708]

Originally Posted by Boominsvx

Still a no go. No double vibe.

Well... I'm beginning to think that placing the tinboot at a early address does not work for all devices. I'm thinking that this will be a problem for Cotulla also.

I will try inserting it at a later location to see if that will help. Just not sure where yet?

[natemcnutty]

Originally Posted by Lmiller1708

Well... I'm beginning to think that placing the tinboot at a early address does not work for all devices. I'm thinking that this will be a problem for Cotulla also.

I will try inserting it at a later location to see if that will help. Just not sure where yet?

Take a look at your resulting NBH files in a hex editor. You will be able to see where the tinboot code is all at (just remember it is now offset by the NBH header). I'm still thinking there is some sort of validation going on because if I take a working NBH, then edit the fatfs size to be 0 or something really small like 128 KB, it refused to boot up. All of the tinboot code was in the right place, and nothing overlapped by me just removing some of the space allocated to the fatfs partition (that I know of).

Really, it isn't that big of a deal. If you look through the resulting NBH, even if we were to perfect this thing to maximize on our space allocation, we would only be gaining back like 5-8 MB of wasted space. I think it is a good idea to have those buffers there just in case we need the extra space for initrd or the kernel.

[coolsilver]

Originally Posted by Boominsvx

No, you'll be missing a few files. Might want to go back and re-read the thread.

Androidupdate.tgz - Andboot folder
Androidinstall.tgz - Andboot Folder
install-seq.sh - Andboot Folder
RHODIMG.NBH - Sdcard Root

Still, re-read one more time before asking further support questions. I've done a good enough job at butting in to the development and I'm sure the developers wouldn't want to drag any more newbies in... if ya know what I mean.

Alright. Thanks for the info.

I'll keep the nand/sd version I have on my phone. I knew more files were needed and more or less was only being given to certain others to help. I'll patiently wait as I am more concerned about the Thunderbolt release anyway.

[natemcnutty]

Originally Posted by coolsilver

Alright. Thanks for the info.

I'll keep the nand/sd version I have on my phone. I knew more files were needed and more or less was only being given to certain others to help. I'll patiently wait as I am more concerned about the Thunderbolt release anyway.

Don't worry, once we've got a few more fixes in the system, we'll get this upped and ready for everyone to use. Right now, we have no root, no data, and some other minor issues. All of them are because of us blowing up rootfs and moving stuff around. It should be just a little more refactoring and we'll be good to go.

[coolsilver]

Cool. Good to hear :P

[[ACL]]

howdy from texas.. i wish i had my phone her to dev since i have some good down time..

[Boominsvx]

PhoneMyPC!!! Dooo iiiit.

Enjoy the week buddy. You know it'll get heavy when you get back.