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

[natemcnutty]

Originally Posted by [ACL]

latest theory is spl might be wiping nand. i cant prove it yet but thats what i gather from convos.

wonder if cmonex might know something from when she was working on HSPL. How exactly does tinboot stay resident, and how does WinMo do it? Maybe we need to use yang to develop a true NBH with all the parts like WinMo and reference them based on the addresses given to yang?

[Lmiller1708]

Guys here is my initrd.gz file. I added .zip so I can up it here just remove it.

Not working:
Keeping data after Reboot.
Data (3G/EV icon is there)
Wi-Fi
Keyboard. (Most likely in the init, all the files should be there.)
Might be others...

Everything else seem to work great.

My androidinstall.tar should not be too different from yours but it you want it let me know.

Edit: This also has Nate's latest SBIN folder with the addition of the adbd file. (tested)

[natemcnutty]

Originally Posted by Lmiller1708

Guys here is my initrd.gz file. I added .zip so I can up it here just remove it.

Not working:
Keeping data after Reboot.
Data (3G/EV icon is there)
Wi-Fi
Keyboard. (Most likely in the init, all the files should be there.)
Might be others...

Everything else seem to work great.

My androidinstall.tar should not be too different from yours but it you want it let me know.

Edit: This also has Nate's latest SBIN folder with the addition of the adbd file. (tested)

Thanks for the post, I'll look through it when I get home. Just as an FYI, a lot of those files get copied over into the system when all is said and done, so we could just merge those into the system ahead of time and yank in out of initrd. That would give us a faster boot and reduce the overall size.

That being said, I don't think the size of initrd is the cause of the problem here. Because my phone is already hosed, I'm going to be making some risky changes to tinboot in an effort to mimic the WinMo OS layout and address ranges. I'm going to actually try compiling everything into an NBH and see what happens...

For data, have you tried manually setting it up in the APN settings?

[[ACL]]

Originally Posted by natemcnutty

Thanks for the post, I'll look through it when I get home. Just as an FYI, a lot of those files get copied over into the system when all is said and done, so we could just merge those into the system ahead of time and yank in out of initrd. That would give us a faster boot and reduce the overall size.

That being said, I don't think the size of initrd is the cause of the problem here. Because my phone is already hosed, I'm going to be making some risky changes to tinboot in an effort to mimic the WinMo OS layout and address ranges. I'm going to actually try compiling everything into an NBH and see what happens...

For data, have you tried manually setting it up in the APN settings?

Ballsy.... but let's hope we get something fruitful. Did u contact that person ?

I spent most of my day chatting with cotulla.. boucing ideas around. So tonight ill run more tests.

[arrrghhh]

Originally Posted by natemcnutty

Because my phone is already hosed, I'm going to be making some risky changes to tinboot in an effort to mimic the WinMo OS layout and address ranges. I'm going to actually try compiling everything into an NBH and see what happens...

I know it's partially busted, just don't do the 'full Woz' so to speak - wouldn't want another guy to bite the dust from bricking his phone!

[Lmiller1708]

Originally Posted by natemcnutty

Thanks for the post, I'll look through it when I get home. Just as an FYI, a lot of those files get copied over into the system when all is said and done, so we could just merge those into the system ahead of time and yank in out of initrd. That would give us a faster boot and reduce the overall size.

That being said, I don't think the size of initrd is the cause of the problem here. Because my phone is already hosed, I'm going to be making some risky changes to tinboot in an effort to mimic the WinMo OS layout and address ranges. I'm going to actually try compiling everything into an NBH and see what happens...

For data, have you tried manually setting it up in the APN settings?

Yeah I was looking at that stuff too, but didn't know for sure... Smaller is always better!

I'm not thinking it was the size now either. Did some testing and it didn't make a difference.
I think if we use the partition table we will need to change how the nbh file is being made (I think). It looks like it is made different on the vogue.

I did try to manually set the APN but then it just disappeared after I saved it. I then had to start all over... Haven't tried too much more with it yet. Once we get the data to stick I sure it won't take long to get it working.

[[ACL]]

Originally Posted by natemcnutty

wonder if cmonex might know something from when she was working on HSPL. How exactly does tinboot stay resident, and how does WinMo do it? Maybe we need to use yang to develop a true NBH with all the parts like WinMo and reference them based on the addresses given to yang?

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"

[Lmiller1708]

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

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]

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?