Please take anything off topic to either Private messages or to a different forum post, allowing this topic to stay on track. Thanks
Please take anything off topic to either Private messages or to a different forum post, allowing this topic to stay on track. Thanks
Here's the latest partition map info I have. This is more detailed than my previous post where I linked to the Galaxy W partition map (but that link turned out to be absolutely correct, just missing some of this info):I think we have found a matching partition map from the Galaxy W? I don't remember where I read that.
I think if a ROM does become in development, it should keep the stock Samsung Browser, as it provides the smoothest scrolling through hardware acceleration.
Here's the latest partition map info I have. This is more detailed than my previous post where I linked to the Galaxy W partition map (but that link turned out to be absolutely correct, just missing some of this info):
I'm unemployed, and could use some encouragement. Get $10 at wepay.com by using my referral link: https://www.wepay.com/x2walzl - it's like paypal without the evil.
- /dev/block/mmcblk0p1 secboot2 partition map
- /dev/block/mmcblk0p2 dbl.mbn (boot loader)
- /dev/block/mmcblk0p3 osbl.mbn (boot loader)
- /dev/block/mmcblk0p4 MBR extended partition table
- /dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
- /dev/block/mmcblk0p6 amss.mbn
- /dev/block/mmcblk0p7 emmcparam.bin
- /dev/block/mmcblk0p8 boot.img (linux kernel)
- /dev/block/mmcblk0p9 adsp.mbn (baseband)
- /dev/block/mmcblk0p10 rmt
- /dev/block/mmcblk0p11 rmt
- /dev/block/mmcblk0p12 persist.ext4
- /dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
- /dev/block/mmcblk0p14 param
- /dev/block/mmcblk0p15 system.ext4
- /dev/block/mmcblk0p16 cache.ext4
- /dev/block/mmcblk0p17 data.ext4
- /dev/block/mmcblk0p18 preload.ext4
- /dev/block/mmcblk0p19 not clear - apparently part of the bootloader
- /dev/block/mmcblk0p20 all 0's
- /dev/block/mmcblk0p21 all 0's
- /dev/block/mmcblk0p22 all 0's
- /dev/block/mmcblk0p23 all 0's
- /dev/block/mmcblk0p24 all 0's
- /dev/block/mmcblk0p25 all 0's
- /dev/block/mmcblk0p26 all 0's
- /dev/block/mmcblk0p27 efs (encrypted fs)
- /dev/block/mmcblk0p28 /mnt/sdcard (the entire /dev/block/mmcblk0 is an emmc "sd card" which is why if you add a micro-sd it's mounted at /mnt/sdcard/external)
What really scares me is the encrypted files. Is this the same stuff the HTC's were coming out with? Cause I don't think anyone is gonna leak a s-off bootloader, if I remember those guys had a gazillion signature petition to change HTC's mind.
Ours is unlocked. HTC just unlocked theirs, big change for HTC users. Thank goodness Samsung didn't try pulling that trick.I thought our boot loader was unlocked if it isn't is there a work around
Did I miss the custom recovery or something?Thank God now let the madness begin cm9 miui here we come
sent from my exhibit 2 greatness
For info, there is now a joint development thread for the galaxy W and the exhibit 2.
http://xdaforums.com/showthread.php?t=1428580