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

**Lmiller1708** · #1 (**permalink**) 02-08-2011, 11:29 AM

Quote:

Originally Posted by [ACL]

we should ask.. or if you know em then ask away if SPL checks nand for winmo friendly partitions. If not fund, then wipe clean.

any mtty commands to prove this theory? i can install , reboot in bootloader mode and maybe see if it doesnt like it ?

Also our tinboot is aged.. We dont have this line at the bottom like vogue does. Not sure whats inside that emtptyimgfs but looks like we dont have it. Its times like these i wish i knew winmo better :-\

.org XIP_END-0x20000,0xff
.incbin "emptyimgfs"

Yeah, I think if we add that line we get a error... That's why Wozzer removed it. I think... I can try it out quick.

Update: Well it didn't give me a error, I must have missing something the last time it tried it. Installing the system now...

Update 2: Didn't work...

**[ACL]** · #2 (**permalink**) 02-08-2011, 11:59 AM

Quote:

Originally Posted by Lmiller1708

Yeah, I think if we add that line we get a error... That's why Wozzer removed it. I think... I can try it out quick.

Update: Well it didn't give me a error, I must have missing something the last time it tried it. Installing the system now...

Update 2: Didn't work...

didnt work as in ? details bro

Next test is to revert to the original initrd and go back to sdcard. Then try to intall android and see if it survives the reboot. I did this before and it did survive but only with some data. But thats better than no data.

**Lmiller1708** · #3 (**permalink**) 02-08-2011, 01:18 PM

Quote:

Originally Posted by [ACL]

didnt work as in ? details bro

Next test is to revert to the original initrd and go back to sdcard. Then try to intall android and see if it survives the reboot. I did this before and it did survive but only with some data. But thats better than no data.

Lol, sorry. It didn't work as in keeping the data.

I'm thinking that something is getting over written during the boot.
The Vogue's intrd.gz file is only 1.3 MB Comparing to Mine of 6.3 MB.
Maybe we need change tinboot file to allow more space for the intrd.gz file?

**[ACL]** · #4 (**permalink**) 02-08-2011, 01:41 PM

Quote:

Originally Posted by Lmiller1708

Lol, sorry. It didn't work as in keeping the data.

I'm thinking that something is getting over written during the boot.
The Vogue's intrd.gz file is only 1.3 MB Comparing to Mine of 6.3 MB.
Maybe we need change tinboot file to allow more space for the intrd.gz file?

I would say for now go back to the original initrd. Then try to mount the mtd partitions and write data onto em. See if it can withstand the reboot.

MassStash · #5 (**permalink**) 02-08-2011, 02:40 PM

how different is the no data problem people are havin with haret?

**[ACL]** · #6 (**permalink**) 02-08-2011, 03:22 PM

i need you gurus help me determine if this os.nb.payload file is good in our tinboot. I dont think its the same as vogue but if it is, then we may need to use our own right ?

Edit: ok cotulla is pretty sure spl is wiping our nand each reboot. No idea how to even stop this. may need to contact dzo ..

**arrrghhh** · #7 (**permalink**) 02-08-2011, 04:58 PM

Quote:

Originally Posted by [ACL]

i need you gurus help me determine if this os.nb.payload file is good in our tinboot. I dont think its the same as vogue but if it is, then we may need to use our own right ?

Edit: ok cotulla is pretty sure spl is wiping our nand each reboot. No idea how to even stop this. may need to contact dzo ..

He did respond to my PM, but it took almost a week. He's certainly helpful, just busy. So if there's a specific question we have for him, I'm sure he'd be glad to help - just don't expect a quick turnaround

.

**natemcnutty** · #8 (**permalink**) 02-08-2011, 07:38 PM

Quote:

Originally Posted by [ACL]

i need you gurus help me determine if this os.nb.payload file is good in our tinboot. I dont think its the same as vogue but if it is, then we may need to use our own right ?

Edit: ok cotulla is pretty sure spl is wiping our nand each reboot. No idea how to even stop this. may need to contact dzo ..

Ours is different than theirs, and they added that emptyimgfs to theirs because they were having issues with the Windows flashing utility. I'm curious what their partition table is for and if that might be the key to what we are trying to do.

My theory right now is that the partition table they use contains the MBR that says where the partitions are, then we point to the beginning of each partition using mtdparts. If we want to change the size of the partitions, we would need to modify the partition table. I'd be worried about having others try this out at messing around with tinboot is a brick risk, and I'm willing to do it since my phone is already screwed up.

Also, I believe Wozzer did this, but anyone willing to get me a mtty bootloader log as explained here:

http://forum.xda-developers.com/show...55&postcount=6

Edit 2: Guess we also need a full dump of mtd to find out what address it actually starts on. I'm sure Wozzer did a lot of this, but still might be a good thing to double check and start it from the beginning.