Originally Posted by championswimmer

we do not really have an official unlocked bootloader....what we really have is bypass which neglects checking the kernel headers(yes the-laser's method is also essentially a bypass ... only the OEM can actually unlock bootloader and Sony has NOT done so for x10)... thus accessing partitions is still not possible.



Sent from my X10S using xda premium

That's wrong... The signature is still checked by the hacked loader of the_laser...

Sent from my HTC One X using XDA

Originally Posted by DooMLoRD

That's wrong... The signature is still checked by the hacked loader of the_laser...

Sent from my HTC One X using XDA

oh... ok...sorry... my ignorance

OFFTOPIC
what are these mtd4 and userdate partitions for.. seem like hidden partitions.... or for baseband usage?

___continuing here and not spamming the thread more ____

yes i was talking of the fourth one
apps log? hmm i didnt know that...other three i knew
thanks


Sent from my X10S using xda premium

Originally Posted by championswimmer

oh... ok...sorry... my ignorance

OFFTOPIC
what are these mtd4 and userdate partitions for.. seem like hidden partitions.... or for baseband usage?

Sent from my X10S using xda premium

the mtds are for:
/system
/data
/cache

and i think there is one for apps log...

MTD format is usually used for NAND based device..

....so I guess that means no I could have sworn it was possible while building the kernel (in cygwin or preferably linux of course) when I looked at the code a while back, but I gave up because it'd require a custom recovery image. Oh well, I've gotten used to TB-Pro "Integrate System App" filters I use to save space on /data.

Medium user

---

I um...I'm lost I download pearl and the file from this trend but what next? I wanna extra the system.sin from my x10 2.3.3. someone please reply. I'm using Windows Xp.

Originally Posted by brenty108

I um...I'm lost I download pearl and the file from this trend but what next? I wanna extra the system.sin from my x10 2.3.3. someone please reply. I'm using Windows Xp.

Completely different. You need to use SIN2BIN tool then extract (or mount) the img with some .img tool that can read yaffs2 filesystems. On Windows it's complicated, you are better off just flashing the stock FTF ROM then doing adb pull /system with USB Debugging.

If you don't know how to do that, you probably shouldn't be doing whatever it is you're trying to do

I have maybe a stupid question, but bear with me..

I have a boot.img is around 10MB in size.

When I use unpack_kernelsin or the method explained by iridaki and after repacking the new-boot.img the total size is only around 5.2MB .. why is that?

also that new-boot.img is not working on my tablet. the --cmdline (in ./repack_bootimg.pl) says it is: ''androidboot.hardware=qcom", that's the only parameter I inpup in --cmdline,

anyways some light on this issue is appreciated.

Originally Posted by rocketero

I have maybe a stupid question, but bear with me..

I have a boot.img is around 10MB in size.

When I use unpack_kernelsin or the method explained by iridaki and after repacking the new-boot.img the total size is only around 5.2MB .. why is that?

also that new-boot.img is not working on my tablet. the --cmdline (in ./repack_bootimg.pl) says it is: ''androidboot.hardware=qcom", that's the only parameter I inpup in --cmdline,

anyways some light on this issue is appreciated.

This tool you are referring tool is only to be used with Xperia 2011 devices.
It will not work on any other tablet/smartphone model.

Originally Posted by iridaki

This tool you are referring tool is only to be used with Xperia 2011 devices.
It will not work on any other tablet/smartphone model.

who know, I found this tool: the DsiXDA's Kitchen tool and made a successful newboot.img that I could flash. but still not full support for scripts running at /system/etc/init.d at boot time.

Originally Posted by rocketero

who know, I found this tool: the DsiXDA's Kitchen tool and made a successful newboot.img that I could flash. but still not full support for scripts running at /system/etc/init.d at boot time.

You need to edit the ramdisk accordingly for that.