Originally Posted by natemcnutty (Post 2053882)

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

Originally Posted by natemcnutty (Post 2053882)

they are just using a blank imgfs which they are including at the end of tinboot:
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: OK, I just broke down and compared the hex of the blankimgfs from Vogue and our imgfs.bin, and they are identical.

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.

Originally Posted by [ACL] (Post 2053897)

I posted the difference yesterday between the partition tables, look at the pastebins.

also my vbin diff shows differences between the imgfs.bin. Looks like we use xpr while dzo uses lzx for compression. So how are you comparing your emptyimgs ?

Originally Posted by natemcnutty (Post 2053904)

Crap, you're right! I renamed the damned file when I was messing around with compiling tinboot and compared it to itself... Just downloaded them directly off the gits and compared with HxD, and I do see the differences from 0x2C to 0x32:
Unfortunately, my battery is dead at the moment, and I have to let it fully charge before I can flash these test tinboots. I might get lucky and be able to try this tonight. If not, tomorrow morning when I get in to work, I have a folder with 4 different tinboots to try out in order of least to most brick risk :P

Originally Posted by Lmiller1708 (Post 2053923)

You "should" be good on not bricking, they are pretty good at handling a bad flash! Once you build them you can try to extract them just as a test... If you can't do that then you shouldn't flash them. ;)

I was trying to do the same thing today, had a couple of bad flashes...
I think I was missing something.

If you want I can test, probably better with a USB cord, send me a PM or stop over at IRC chat...

What did you do to get them made?


Our imgfs.bin is getting inserted during the making process with the ImgfsToNb.exe. The Vogue's emptyimgfs is just getting built right in the kernel, this is why we don't see it on the NBHInfo.exe.

So... We should be able to just add it do the kernel like you have it above and forget about it. We might not even need it however, I read somewhere that it was just there because some flashing utilitly's (older one's like the Vogue) can't handle it.

Originally Posted by [ACL] (Post 2054043)

modded partition table.

Hotfile.com: One click file hosting: rhod_payload

any brave souls ? just attach the empty imgfs to tinboot and hope the phone gods have mercy..

This is how it looks .. note no imgfs and 0 size in fat like vogue.

edit: ok tried it and so far no brick.. but cant boot since we dont have lzma support on the kernel. i can work on that but i really wanna test it. We need to put the initrd on a diet. right now its 1.6mb which is too big

Originally Posted by natemcnutty (Post 2054063)

Looks awesome. I'll be playing with it tomorrow. One way to get the size down a bit would be better referencing the files in sbin since they already exist in bin. I was thinking of a ln -s ../bin/adbd and ln -s ../bin/busybox for all the rest of those files. I can test that out tomorrow and see how it works. Still not even sure if we need the sbin folder...

Edit: Also, good news! In a couple of weeks, I may have a TMOUS TP2 to test with. No data, but that would give me a GSM device with a working USB port to mess around with :D

Originally Posted by MassStash (Post 2053927)

i'll try anything not TOO risky haha rhod400 fullycharged

lmiller: yea, you try and get at joojoobee or something?