Database Develop

[Q] Where is the boot partition in Optimus Black?

I wanted to extract boot.img from an existing rom, following this wiki:
http://android-dls.com/wiki/index.p..._Images#Structure_of_boot_and_recovery_images
But it seems that on Stock Rom (actually I'm using Zeus rom, based on stock) there is no /proc/mtd that would tell me where to find the "boot" partition. I think it should be one of these:
179 0 1912832 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 660480 mmcblk0p8
179 9 1161088 mmcblk0p9
179 10 65536 mmcblk0p10
179 11 128 mmcblk0p11
179 12 128 mmcblk0p12
179 16 15637504 mmcblk1
179 17 15633408 mmcblk1p1
Do anyone know where the boot partition is hiding? Or have an idea on how to find where it is?

Here are some of the partitions:
Code:
loop0 =
/dev/block/mmcblk0 =
/dev/block/mmcblk0p1 =
/dev/block/mmcblk0p2 =
/dev/block/mmcblk0p3 = /boot
/dev/block/mmcblk0p4 = /recovery
/dev/block/mmcblk0p5 = /lgdrm
/dev/block/mmcblk0p6 = /dvp/userdata
/dev/block/mmcblk0p7 =
/dev/block/mmcblk0p8 = /system
/dev/block/mmcblk0p9 = /data
/dev/block/mmcblk0p10 = /cache
/dev/block/mmcblk0p11 =
/dev/block/mmcblk0p12 =
/dev/block/mmcblk1 =
/dev/block/mmcblk1p1 = /sdcard
dm-0 =

Format SD Card? How?

Hey,
i booted CM9 on my tablet. now it says "SD Card damaged". If i format it via CM9, it still says "SD CARD damaged..."...
Even CWM says that there was an error mounting SD Card when i want to mount it!
But i need it want to install CM10 on my touchpad...
i can access via adb, cat says:
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 31160320 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 500 mmcblk0p5
179 6 750 mmcblk0p6
179 7 2500 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 30504960 mmcblk0p14
254 0 581632 dm-0
254 1 65536 dm-1
254 2 16384 dm-2
254 3 24576 dm-3
254 4 262144 dm-4
254 5 139264 dm-5
254 6 26877952 dm-6
254 7 409600 dm-7
254 8 311296 dm-8
254 9 204800 dm-9
254 10 1572864 dm-10
~ #
How to format/mount the sd card via adb that it works with CM9 so that i can copy files on it for flashing?
Thanks!

You should be able to format it from CWM or TWRP recovery. If that doesn't work you could always run ACMEUninstaller which will reset all Android partitions and you'll have to reinstall using ACMEInstaller.

When you re-install, use acmeinstaller 3.
Edit : on rereading your post, you might have to use this : http://forum.xda-developers.com/showthread.php?t=1426244
If you're having trouble with novaterm, on page 12 of the thread there's a good work around for that.
I know doctoring is a PITA, but you can update from 3.0.0 to 3.0.5 (in webOs) OTA.

Just do not do it through windows
Sent from my SAMSUNG-SGH-T989 using xda premium

chicle_11 said:
When you re-install, use acmeinstaller 3.
Edit : on rereading your post, you might have to use this : http://forum.xda-developers.com/showthread.php?t=1426244
If you're having trouble with novaterm, on page 12 of the thread there's a good work around for that.
I know doctoring is a PITA, but you can update from 3.0.0 to 3.0.5 (in webOs) OTA.
Click to expand...
Click to collapse
Worked for me thanks! =)

File request aboot

I have an LG Motion and I would like a copy of your aboot file to try to see if I can get the bootloader unlocked while it's flashed on the motion.
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
and send that file to me please
Thanks in advaced.
Screw LG's locked bootloaders!!!
Also this may be in the wrong place. If it belongs in development, I'm sorry.

dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: No such file
or directory

reas0n said:
dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: No such file
or directory
Click to expand...
Click to collapse
tegra platform...and we have no partition named aboot

i have x-loader.img and u-boot.img. here:
https://www.box.com/s/a6pyad63qwauos7zdw2b

Tim_Pan said:
tegra platform...and we have no partition named aboot
Click to expand...
Click to collapse
Hmmmm, you think it will still work?
Edit: what are the blocks and names of your partitions?
Sent from my LG-MS770

[email protected]:/ # cat proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15645696 mmcblk1
179 49 15644672 mmcblk1p1

Code:
ls -l /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2013-03-10 23:24 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-03-10 23:24 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-03-10 23:24 CAL -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-03-10 23:24 DRM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-03-10 23:24 FOT -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-03-10 23:24 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-03-10 23:24 MLT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-03-10 23:24 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-03-10 23:24 NVA -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-03-10 23:24 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-03-10 23:24 UDA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-03-10 23:24 UDB -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-03-10 23:24 USP -> /dev/block/mmcblk0p6

reas0n said:
[email protected]:/ # cat proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15645696 mmcblk1
179 49 15644672 mmcblk1p1
Click to expand...
Click to collapse
No name of partitions?
Guess I'll have to figure out which partition is which on my own
I figure if your bootloader even does boot, I gotta make sure the partitions are still the same, and if not the same, flash things to the correct partitions according to your bootloader.
Sent from my LG-MS770

Can't flash the file given....our bootloader is 512KBs...yours is 10MBs............

sammyz said:
Can't flash the file given....our bootloader is 512KBs...yours is 10MBs............
Click to expand...
Click to collapse
i dont know if u still need, but download .tot or kdz for your phone and use lg binextractor(is not from lg,search google)extract the tot or kdz and get the aboot.i only have the nexus 4 and l5 so i cant help u much.

Our bootloader cannot be dumped from partitions. It's built into a lower level on the device. The two devices are in no way similar. Ours has a Tegra 3 chipset, yours is MSM.
If you really want to take a look at our bootloader, you can find a dump somewhere in the development section. But even if you find it and it fits for your device, DO NOT flash it by any means!!! It's one of the worst ideas one can come up with. You can very easily brick your device.
reas0n said:
i have x-loader.img and u-boot.img. here:
https://www.box.com/s/a6pyad63qwauos7zdw2b
Click to expand...
Click to collapse
Where did you get these from? It's not for the O4X.
Sent from my OmniROM-powered LG Optimus 4X HD

Gear 2 Rom Firmware extracted

I have extracted the Gear 2 firmware to a zip so people can look at the structure and possibly start modding the device. Its extracted from the newest rom available on Sammobile. If you have any questions let me know.
htt p://bit.ly/1m4mj5m

Velrix said:
I have extracted the Gear 2 firmware to a zip so people can look at the structure and possibly start modding the device. Its extracted from the newest rom available on Sammobile. If you have any questions let me know.
htt p://bit.ly/1m4mj5m
Click to expand...
Click to collapse
Updates..
I am trying to backup the current partitions to see the kernel/recovery and not getting far. Has anyone else been working on this?
sh-3.2$ cat /proc/partitions
major minor #blocks name
7 0 19732 loop0
179 0 3817472 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 12288 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 65536 mmcblk0p12
259 5 131072 mmcblk0p13
259 6 2996224 mmcblk0p14
259 7 524288 mmcblk0p15
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179:0 179:3 179:7 1:10 1:14 1:4 1:8 259:2 259:6 7:2 7:6
179:1 179:4 179:8 1:11 1:15 1:5 1:9 259:3 259:7 7:3 7:7
179:16 179:5 1:0 1:12 1:2 1:6 259:0 259:4 7:0 7:4
179:2 179:6 1:1 1:13 1:3 1:7 259:1 259:5 7:1 7:5
Current information I can receive from the watch.
If I try to make a backup obviously it fails with the following message..
D:\tizen-wearable-sdk\tools>sdb shell
sh-3.2$ chmod 755 /tmp/rkdump
sh-3.2$ /tmp/rkdump /dev/mmcblk0boot0 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0boot0: Permission denied
sh-3.2$ /tmp/rkdump /dev/mmcblk0p1 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0p1: Permission denied
sh-3.2$ /tmp/rkdump /dev/mmcblk0p2 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0p2: Permission denied

[Q] Why do I have 39 partitions?

I've been blundering through the world of rooting for a few days, stumbling around in the dark. Many of the steps I've taken I didn't fully understand at the time, but I've come a long way towards understanding.
My getvar dump should answer most basic questions:
Code:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 1.00.20.0315
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: ############
imei: ###############
meid: ##############
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4319mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
I just flashed "RUU Zip M7_WLS_JB_50_Sprint_1.29.651.10_RUU_decrypted.zip"
Ok, here's my problem. My phone has 39 partitions instead of 37. I think this happened when I flashed "Sprint_HTC_One_m7wls_4.06.651.4_RUU" but I'm not sure about the timing. I went S-OFF and flashed to an older firmware, hoping that would clear up the issue, but it remains as before.
Code:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 256 mmcblk0p29 skylink [NEW]
179 30 25600 mmcblk0p30 carrier [NEW]
179 31 72870 mmcblk0p31 reserve [SMALLER]
179 32 54270 mmcblk0p32 reserve_2
179 33 76800 mmcblk0p33 radio
179 34 98303 mmcblk0p34 reserve_3
179 35 16384 mmcblk0p35 boot
179 36 16383 mmcblk0p36 recovery
179 37 1900543 mmcblk0p37 system
179 38 655359 mmcblk0p38 cache
179 39 27262976 mmcblk0p39 userdata
Because of this, TWRP incorrectly mounts the system partition to /data and fails to mount /cache and /system. When I modify /etc/fstab to reflect my partitions, it works. Until I try to restore from a backup or install a custom ROM. Then it somehow manages to remount something by the old scheme and fails. The device boots and runs fine, but anything to do with recovery is broken.
If anyone knows what's going on or how I can coerce TWRP to use my new partitions, it would mean a lot to me. Thanks.

terrabite3 said:
I've been blundering through the world of rooting for a few days, stumbling around in the dark. Many of the steps I've taken I didn't fully understand at the time, but I've come a long way towards understanding.
My getvar dump should answer most basic questions:
Code:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 1.00.20.0315
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: ############
imei: ###############
meid: ##############
[/HIDE][B][COLOR="Red"]product: m7_wls[/COLOR][/B]
platform: HBOOT-8064
[B][COLOR="Red"]modelid: PN0720000
cidnum: SPCS_001[/COLOR][/B]
[HIDE]battery-status: good
battery-voltage: 4319mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
I just flashed "RUU Zip M7_WLS_JB_50_Sprint_1.29.651.10_RUU_decrypted.zip"
Ok, here's my problem. My phone has 39 partitions instead of 37. I think this happened when I flashed "Sprint_HTC_One_m7wls_4.06.651.4_RUU" but I'm not sure about the timing. I went S-OFF and flashed to an older firmware, hoping that would clear up the issue, but it remains as before.
Code:
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15 dsps
179 16 61441 mmcblk0p16 adsp
179 17 8190 mmcblk0p17 radio_config
179 18 32768 mmcblk0p18 reserve_1
179 19 1022 mmcblk0p19 misc
179 20 4096 mmcblk0p20 modem_st1
179 21 4096 mmcblk0p21 modem_st2
179 22 20480 mmcblk0p22 devlog
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24 pdata
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26 local
179 27 64 mmcblk0p27 extra
179 28 1024 mmcblk0p28 cdma_record
179 29 256 mmcblk0p29 skylink [NEW]
179 30 25600 mmcblk0p30 carrier [NEW]
179 31 72870 mmcblk0p31 reserve [SMALLER]
179 32 54270 mmcblk0p32 reserve_2
179 33 76800 mmcblk0p33 radio
179 34 98303 mmcblk0p34 reserve_3
179 35 16384 mmcblk0p35 boot
179 36 16383 mmcblk0p36 recovery
179 37 1900543 mmcblk0p37 system
179 38 655359 mmcblk0p38 cache
179 39 27262976 mmcblk0p39 userdata
Because of this, TWRP incorrectly mounts the system partition to /data and fails to mount /cache and /system. When I modify /etc/fstab to reflect my partitions, it works. Until I try to restore from a backup or install a custom ROM. Then it somehow manages to remount something by the old scheme and fails. The device boots and runs fine, but anything to do with recovery is broken.
If anyone knows what's going on or how I can coerce TWRP to use my new partitions, it would mean a lot to me. Thanks.
Click to expand...
Click to collapse
It's because you have a Sprint phone. The partition table is correct for Sprint (which is different from the M7_U/UL), you need to use TWRP for M7_WLS
http://techerrata.com/browse/twrp2/m7wls

Ahhhh! Thank you! The only question that remains is how I switched from the RIGHT one to the WRONG one at some point.

terrabite3 said:
Ahhhh! Thank you! The only question that remains is how I switched from the RIGHT one to the WRONG one at some point.
Click to expand...
Click to collapse
you took a left turn somewhere
make sure you stick with recoveries/kernels/ROMs mean for Sprint.... due to the different partition table, unless you are 100% sure "it's" Sprint compatible (m7_wls), then don't flash it.