Database Develop

Unheard of Semi-Brick situation!!! HELP!

I was previously on Gingerbread 2.3 with CF-Root kernel. I flashed Ultimate XXLSC JB ROM v5.1 from here This ROM flashed fine from CWM as far as I know. It had a few issues since i forgot to wipe the data. I rebooted into recovery to do that. After which i lost root (im not sure if i had it before wiping the data though). The su binary was corrupted in some way (ES File explorer could not get its properties) and SuperSU said 'Installation failed'. I tried installing a simple rooting zip from CWM. This got stuck at 'Unmounting system' and did no effect to the su and busybox binaries. CWM was also causing problems. It refused to boot into system normally and could not unmount /system. I could not make a backup of this system since it would crash on backing up 'busybox'. I could not reflash the zip as it would not go further than the intial text logo. Here is the normal boot into recovery log:
Starting recovery on Sat Jan 26 17:22:13 2013
framebuffer: fd 4 (800 x 1280)
E:unknown volume for path [/system]
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /efs ext4 /dev/block/mmcblk0p1 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p10 (null) 0
7 /preload ext4 /dev/block/mmcblk0p12 (null) 0
8 /modem emmc /dev/block/mmcblk0p8 (null) 0
9 /emmc vfat /dev/block/mmcblk0p11 (null) 0
10 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
PhilZ Touch 3
CWM Base version: 6.0.1.9
Command: "recovery"
ro.sec_debug.enable=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.debug_level=unknown
ro.emmc_checksum=unknown
ril.dualmode.change=unknown
ro.hardware=smdk4210
ro.revision=8
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp
init.svc.ueventd=running
ro.crypto.keyfile.userdata=/efs/metadata
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand & OpenRecoveryScript...
I:Skipping execution of extendedcommand, file not found...
I:Skipping execution of OpenRecoveryScript, file not found...
IS THE RED PART THE ISSUE? HOW DO I FIX THIS? CAN I GO BACK TO A CWM BACKUP OF MY OLD GB SYSTEM SAFELY? The OS functions fine for now though.

You forgot to wipe when installing the JB CR. So the beginning gave you an unstable system.
And that's why you should install a fresh stock Rom with Odin.
After everything is working you might restore your GB backup (using a safe kernel like Philz 3.99).
I have to admit that I have difficulties to follow your steps.

Partition Table? Post plz

Can someone post the partition table block for me thanks. Need to see which one is SYSTEM, CACHE AND USERDATA.

@hatememarkz you are a d/a
@...awesome... hope this helps
Partition Table
/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
/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

Thread Closed as per OP request, Thank You.

[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

[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

Recover data from galaxy s plus with broken screen

Hello, I have a samsung galxy s plus with cm11 and a broken screen and i want to recover data from internal storage
when the phone is on i cannot access adb
in recovery i can use adb shell but don't know how to mount the internal storage.
I've tried several ways to mount but didn't work
here is my fstab
Code:
/dev/block/mmcblk0p16 /cache ext4 rw
/dev/block/mmcblk0p17 /data ext4 rw
/dev/block/mmcblk0p15 /system ext4 rw
and recovery.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mmcblk0p8 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p13 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p15 /system ext4 ro,errors=panic wait
/dev/block/mmcblk0p16 /cache ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/mmcblk0p17 /data ext4 nosuid,nodev,noatime,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/devices/platform/msm_sdcc.2/mmc_host/mmc1 /storage/sdcard0 vfat defaults voldmanaged=sdcard0:28,nonremovable
/devices/platform/msm_sdcc.4/mmc_host/mmc2 /storage/sdcard1 vfat defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host.0 /storage/usbdisk auto defaults voldmanaged=usbdisk:auto
can anyone help?

Google Android commander. Turn your phone on and use that to get all your files.
Sent from my SM-N900T using Tapatalk

the problem is i've modified build.prop to try to enable MTP instead of UMS but now i have boot loop (it vibrates) and even after pushing the backup of build.prop on the phone, the phone still doesn't boot. I can only use the recovery.

anyone?, Im sure there is a way but I just can't find one