Database Develop

[Q] What is STE_boot1.img? And where modem.bin?

Hi!
a few questions about the Parts of the I8190.
# Mount point fs device
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25
/efs ext4 /dev/block/mmcblk0p11
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
Where ist the MODEM points?????
And
In Stock ROM is included:
STE_boot1.img
STE_boot2.img
what is this??

Darkman said:
Hi!
a few questions about the Parts of the I8190.
# Mount point fs device
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25
/efs ext4 /dev/block/mmcblk0p11
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
Where ist the MODEM points?????
And
In Stock ROM is included:
STE_boot1.img
STE_boot2.img
what is this??
Click to expand...
Click to collapse
Hi Darkman
In this post HERE I have a Mobileodin.txt made by MobileOdin whit some data very interesting about S3 Mini partitions.
We see on it the modem is on partition 12.
ValenteL

ouya mounts for updater script

What are the correct commands for the updater script in a custom rom.zip when im writing to the /system, /data, /recovery, /boot i know the architecture which is.... but what would i put in the updater script from a custom rom....i built one but all thats in the there for mount is MTD
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/metadata emmc /dev/block/platform/sdhci-tegra.3/by-name/MDA
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA
*please move to general questions sorry devs

No4g4Me said:
What are the correct commands for the updater script in a custom rom.zip when im writing to the /system, /data, /recovery, /boot
Click to expand...
Click to collapse
the partition type is EMMC
Recovery is mmcblk0p1
Boot is mmcblk0p2
System is mmcblk0p3
http://forum.xda-developers.com/showpost.php?p=41808197&postcount=13
Sweet more roms!
Edit:
Here is what I am using, but the format isnt working, I'm getting status 6 in cwm, So just removing that from updater script and doing a manual wipe of system before flash;
format("ext4", "EMMC", "/dev/block/mmcblk0p3");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");

This is what I'm using because I pulled it straight from the OTA update updater-script file:
format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");

Yeah. I got status 6 when I tried using those commands as well. I'm not sure if it's something misconfigured with the CWM recovery or not.
Anyway, I was able to mount and unmount stuff with:
Code:
run_program("/sbin/mount","/system");
Code:
run_program("/sbin/umount","/system");
The partitions in the fstab are:
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/metadata emmc /dev/block/platform/sdhci-tegra.3/by-name/MDA
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA
/sdcard datamedia /dev/null
Click to expand...
Click to collapse
And as the professor pointed out, the corresponding mmcblk numbers are
lrwxrwxrwx root root 2013-05-25 02:23 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-05-25 02:23 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-05-25 02:23 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-05-25 02:23 MDA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-05-25 02:23 MSC -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-05-25 02:23 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-05-25 02:23 UDA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-05-25 02:23 UPP -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-05-25 02:23 USP -> /dev/block/mmcblk0p7
Click to expand...
Click to collapse

Ok, that's how I had to mount them on the Droid Bionic as well.

[Q] sm-g730a recovery help

I'm trying to build a recovery for the first time for this device and i was wondering if someone could look at my recovery.fstab and help me out with it. i found lots of tutorials on building cwm for a new device but editing the recovery.fstab and boardconfig.mk i havnt found really anything.
recovery.fstab
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p13
/cache ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p23
/recovery emmc /dev/block/mmcblk0p14
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p20
/sd-ext ext4 ?
---------------
boardconfig.mk
USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/samsung/s3mini/BoardConfigVendor.mk
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_BOOTLOADER_BOARD_NAME := s3mini
BOARD_KERNEL_CMDLINE := console=null androidboot.hardware=qcom user_debug=31
BOARD_KERNEL_BASE := 0x80200000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
TARGET_PREBUILT_KERNEL := device/samsung/s3mini/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
-------------------
used:
ls -l /dev/block/platform/msm_sdcc.1/by-name > /mnt/sdcard/partitions.txt
partitions are as follow:
lrwxrwxrwx root root 2013-01-02 01:11 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-02 01:11 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-01-02 01:11 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-01-02 01:11 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-01-02 01:11 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-02 01:11 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-01-02 01:11 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-01-02 01:11 hidden -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-01-02 01:11 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-02 01:11 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-01-02 01:11 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-01-02 01:11 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-02 01:11 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-02 01:11 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-01-02 01:11 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-01-02 01:11 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-02 01:11 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-02 01:11 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-02 01:11 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-02 01:11 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-01-02 01:11 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-01-02 01:11 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-02 01:11 userdata -> /dev/block/mmcblk0p23
EDIT: I think i understand the recovery.fstab

I unpacked a stock-recovery.img from another post and got a recovery.fstab, can someone help me understand it?
# mount point fstype device [device2]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs
/modem emmc /dev/block/platform/msm_sdcc.1/by-name/modem
/preload ext4 /dev/block/platform/msm_sdcc.1/by-name/hidden

assassinanex said:
I unpacked a stock-recovery.img from another post and got a recovery.fstab, can someone help me understand it?
# mount point fstype device [device2]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs
/modem emmc /dev/block/platform/msm_sdcc.1/by-name/modem
/preload ext4 /dev/block/platform/msm_sdcc.1/by-name/hidden
Click to expand...
Click to collapse
intended_mount_location type partition
by-name doesn't always exists, you'll need to check what initfs is creating on your particular phone. The opensource kernel is available for your phone from samsung, best place to look imo.
PS. if this helps you I'd appreciate a copy of the firmware from your phone for a project
m0tter

any updates on this?

m0tter said:
intended_mount_location type partition
by-name doesn't always exists, you'll need to check what initfs is creating on your particular phone. The opensource kernel is available for your phone from samsung, best place to look imo.
PS. if this helps you I'd appreciate a copy of the firmware from your phone for a project
m0tter
Click to expand...
Click to collapse
if you need s3 mini sm-g730a firmware how do i exctract it ? ill send nmine to any who need

[Q] Partition Label Assignments?

SOLVED!
Could someone please help decipher the partition tables on my N990A? I need to know partition assignments

Example:
adb shell
su
dd if=/dev/block/mmcblk0p15 of=/sdcard/recovery.img

DAMMIT! Wouldn't ya know it after I post a question on here that I'd find the answer. :silly:
http://forum.xda-developers.com/showthread.php?t=2450045
Here are the partition names with block address:
aboot = /dev/block/mmcblk0p6
apnhlos = /dev/block/mmcblk0p1
backup = /dev/block/mmcblk0p17
boot = /dev/block/mmcblk0p14
cache = /dev/block/mmcblk0p24
dbi = /dev/block/mmcblk0p4
ddr = /dev/block/mmcblk0p5
efs = /dev/block/mmcblk0p11
fota = /dev/block/mmcblk0p16
fsc = /dev/block/mmcblk0p19
fsg = /dev/block/mmcblk0p18
modem = /dev/block/mmcblk0p2
modemst1 = /dev/block/mmcblk0p12
modemst2 = /dev/block/mmcblk0p13
pad = /dev/block/mmcblk0p9
param = /dev/block/mmcblk0p10
persdata = /dev/block/mmcblk0p22
persist = /dev/block/mmcblk0p21
recovery = /dev/block/mmcblk0p15
rpm = /dev/block/mmcblk0p7
sbl1 = /dev/block/mmcblk0p3
ssd = /dev/block/mmcblk0p20
system = /dev/block/mmcblk0p23
tz = /dev/block/mmcblk0p8
userdata = /dev/block/mmcblk0p25

[Q] Creating partition images on 870A

Does anyone know the relation of which block devices in /dev/mmcblk0pXX belong to which partition? (ex: system, modem, boot, etc)
I'm looking to create a custom Odin AIO package for my install of lollipop, which has been rooted and such; going back to NE4 is a PITA and would like a faster route for when a full wipe is required.
Thanks in advance :good:

After scrounging the internet for awhile, I was able to answer my own question. I've posted the partition scheme below for others who might need it someday:
aboot -> /dev/block/mmcblk0p6
apnhlos -> /dev/block/mmcblk0p1
backup -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p15
cache -> /dev/block/mmcblk0p24
dbi -> /dev/block/mmcblk0p4
ddr -> /dev/block/mmcblk0p5
efs -> /dev/block/mmcblk0p12
fota -> /dev/block/mmcblk0p17
fsc -> /dev/block/mmcblk0p19
fsg -> /dev/block/mmcblk0p9
modem -> /dev/block/mmcblk0p2
modemst1 -> /dev/block/mmcblk0p13
modemst2 -> /dev/block/mmcblk0p14
pad -> /dev/block/mmcblk0p10
param -> /dev/block/mmcblk0p11
persdata -> /dev/block/mmcblk0p22
persist -> /dev/block/mmcblk0p21
recovery -> /dev/block/mmcblk0p16
rpm -> /dev/block/mmcblk0p7
sbl1 -> /dev/block/mmcblk0p3
ssd -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p8
userdata -> /dev/block/mmcblk0p25