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

[MassStash]

Originally Posted by [ACL]

damn.. you look hungry.. like you wanna test. sounds like you are ready to modify some partition tables..

lol you have noooo idea. day off so i wanna put it to use on this but i fear i lack a slight knowledge of that shit.... please point me to some stuff n i'll try n go buck wiiild on it haha

[[ACL]]

Originally Posted by MassStash

lol you have noooo idea. day off so i wanna put it to use on this but i fear i lack a slight knowledge of that shit.... please point me to some stuff n i'll try n go buck wiiild on it haha

well i dunno if anyone knows how to modify our os.nb.payload file. Do you know how to modd it ?

[MassStash]

Originally Posted by [ACL]

well i dunno if anyone knows how to modify our os.nb.payload file. Do you know how to modd it ?

this might help someone other than me, but it's easy to find. yet on the other hand, that could be backwards lol -= How to build your own WM6 Big Storage OS.nb/XIP on Hermes =- - xda-developers ::currently reading::

as i feared, i'm behind the curve on this one...

[[ACL]]

Originally Posted by MassStash

this might help someone other than me, but it's easy to find. yet on the other hand, that could be backwards lol -= How to build your own WM6 Big Storage OS.nb/XIP on Hermes =- - xda-developers ::currently reading::

as i feared, i'm behind the curve on this one...

you got a head start.. im still at work so by the time i even touch this you will be a master..

[natemcnutty]

Originally Posted by [ACL]

well i dunno if anyone knows how to modify our os.nb.payload file. Do you know how to modd it ?

Why would we mod it? Vogue just renames their partition table to os.nb.payload, then cat tinboot with os.nb.payload. The tinboot is the XIP, and the os.nb.payload is what would normally contain the OS files. We don't have any OS files contained in the payload, right? We also don't need to merge the empty imgfs if we incbin it in using Tinboot.S.

I would seriously consider trying this. Generate the XIP using our makexip script, then use the vogue's partition layout and blank imgfs to do the NBH:

cp partition_table output.nb.payload
# rhod500 here is our output from makexip.sh
cat rhod500 >> output.nb.payload
# we still use wine, but we could comment out and use their nbmerge instead 
# wine /usr/share/LinuxRomKitchen/NBMerge.exe -kaiser output.nb
./nbmerge < output.nb.payload > output.nb
yang -F RHODIMG.NBH -f output.nb -t 0x400 -s 64 -d RHOD****0 -c 11111111 -v Tinboot -l WWE

[[ACL]]

Originally Posted by natemcnutty

Why would we mod it? Vogue just renames their partition table to os.nb.payload, then cat tinboot with os.nb.payload. The tinboot is the XIP, and the os.nb.payload is what would normally contain the OS files. We don't have any OS files contained in the payload, right? We also don't need to merge the empty imgfs if we incbin it in using Tinboot.S.

I would seriously consider trying this. Generate the XIP using our makexip script, then use the vogue's partition layout and blank imgfs to do the NBH:

cp partition_table output.nb.payload
# rhod500 here is our output from makexip.sh
cat rhod500 >> output.nb.payload
# we still use wine, but we could comment out and use their nbmerge instead 
# wine /usr/share/LinuxRomKitchen/NBMerge.exe -kaiser output.nb
./nbmerge < output.nb.payload > output.nb
yang -F RHODIMG.NBH -f output.nb -t 0x400 -s 64 -d RHOD****0 -c 11111111 -v Tinboot -l WWE

thats the confusing part. their partition table has no imgfs while ours does. So how do we change that? thats where i'm confused as to if we need to mod it or just create a new one from scratch.

So you want to just use the vogue partition table and imgfs ? thats ballsy.. do it.. lol

[MassStash]

I think that's wat he's getting at

Sent from my rhod400 using Tapatalk

[[ACL]]

Originally Posted by MassStash

I think that's wat he's getting at

Sent from my rhod400 using Tapatalk

you do it !!! .. do it !!!

[coolsilver]

Android is based off linux. I would figure however the imgfs is mounted it is some subset that is eventually merged into the full disk structure on boot.

I'd say you could setup the system and rootfs in the same partition and some how mount the rest as part of it.

More or less how /data could be on a separate partition but otherwise doesn't matter once it is mounted.

Not all sure how it all fits together but has to be a logical fit.

[natemcnutty]

Originally Posted by [ACL]

thats the confusing part. their partition table has no imgfs while ours does. So how do we change that? thats where i'm confused as to if we need to mod it or just create a new one from scratch.

So you want to just use the vogue partition table and imgfs ? thats ballsy.. do it.. lol

they are just using a blank imgfs which they are including at the end of tinboot:

kernel:
        .incbin "zImage"
initrd:
        .incbin    "initrd.lzma"
        .align
fin:
        .org XIP_END-0x20000,0xff
        .incbin "emptyimgfs"

I'll break down their imgfs and compare it with ours. I'll also dig a little deeper into the os.payload, but I really don't think that part matters for much of anything since the XIP is what we care about (since it contains the tinboot code).

I'll gladly try flashing the vogue's partition table and blank imgfs like they do it. Like I said, my phone is fairly useless with the USB being broken. I have to keep it on a charger almost all day long because the pins are broken inside keeping the current flowing through the USB all day long...

EDIT: I'm retarded

Now I just have to figure out the difference between the partition table from Vogue and our os.nb.payload file. I believe that is the only difference between what we are doing and what they are doing. And like DZO said, they had to use a tiny partition table to only use one cell. Seems we should be able to do the same thing, so I'm going to try it.