Database Users

FIREFIREFIRE with dualboot/multiboot support

Hoping someone from the dev thread
reads this. Only reason I can't post there is I am "new".
I'm running into an issue booting using the alternate boot option.
My primary boot is Stock rooted 6.3
My alternate is Pure AOKP ICS with Hashcode 3.0 Kerne
This is my partition table.
Code:
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB splash
9 312MB 849MB 537MB ext4 system
10 849MB 2241MB 1392MB ext4 userdata
11 2241MB 2369MB 128MB ext4 cache
12 2369MB 5750MB 3381MB fat32 media msftres
13 5750MB 5761MB 11.0MB boot2
14 5761MB 6298MB 537MB ext4 system2
15 6298MB 7690MB 1392MB ext4 userdata2
16 7690MB 7818MB 128MB ext4 cache2
This is from my init.omap4430.rc file
Code:
on fs
log "== init.omap4430.rc: on fs ------------------------"
mount ext4 /dev/block/mmcblk0p14 /system wait ro
mount ext4 /dev/block/mmcblk0p15 /data wait noatime nosuid nodev errors=continue
mount ext4 /dev/block/mmcblk0p16 /cache wait noatime nosuid nodev errors=continue
mount ext4 /dev/block/mmcblk0p8 /dropbox wait noatime nosuid nodev errors=continue
And this is my update-script
Code:
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/system2", "0");
mount("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/system2", "/system");
......
package_extract_file("boot.img", "/dev/block/platform/mmci-omap-hs.1/by-name/boot2");
The install works fine, and everything seems to go to its correct place. But when I select the alternate boot option it sits indefinitely on the selection screen.

What recovery are you using? Many people are reporting that ClockworkMod seems to have trouble with ROMs using the 3.0 kernel, making them unbootable even on a stock boot layout. TWRP doesn't have issues with it, so I would try that if you're currently using CWM.
If that's not the issue, then try using the "/dev/block/mmcblk0p#" style to specify the partitions in the updater-script. I had some difficulty getting it to play nicely with the "by-name" style for whatever reason, especially with the boot images (I'm not really sure why, though).

eldarerathis said:
What recovery are you using? Many people are reporting that ClockworkMod seems to have trouble with ROMs using the 3.0 kernel, making them unbootable even on a stock boot layout. TWRP doesn't have issues with it, so I would try that if you're currently using CWM.
If that's not the issue, then try using the "/dev/block/mmcblk0p#" style to specify the partitions in the updater-script. I had some difficulty getting it to play nicely with the "by-name" style for whatever reason, especially with the boot images (I'm not really sure why, though).
Click to expand...
Click to collapse
I'm used TWRP 2.0 and 2.1, neither "worked".
The rom installed, that doesn't seem to be the issue, unless I am completely off base.
I was unable to install gapps because moding its install script to goto the mmcblk0p14 caused it to fail, I think it was because it was signed, and I modded it making the md5 invalid. I need to work on that, but that shouldn't cause an issue with booting.
The only thing I can think of is that your boot2 is on p16 while mine is on p13?? would that be the issue?

Changed to
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
.......
package_extract_file("boot.img", "/dev/block/mmcblk0p13");
and
Code:
on fs
mount ext4 /dev/block/mmcblk0p14 /system wait ro
mount ext4 /dev/block/mmcblk0p15 /data wait noatime nosuid nodev errors=continue
# mount ext4 /dev/block/platform/mmci-omap-hs.1/by-name/cache /cache wait noatime nosuid nodev errors=contin$
mount ext4 /dev/block/mmcblk0p8 /dropbox wait noatime nosuid nodev errors=continue
This time I am trying to put the 6.3 rooted version on the alternate.
The install occurs with no issue. It just gets stuck at the Alternate Boot menu.
I'm using 0.1, not sure if there is another version of the loader.

brick 7.7 - partition /data eror , need help

Pease , my 7.7 is unbootable now.
I need your help , please check partition table in your 7.7
my result from "parted" ( which should be incorrect) is :
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1153MB 872MB ext4 FACTORYFS
10 1153MB 15.3GB 14.1GB ext4 DATAFS
11 15.3GB 15.7GB 470MB ext4 HIDDEN
12 15.7GB 15.8GB 8389kB FOTA
The reason is after I update to custom ICS rom, my /data become invalid.
At that state I cannot format /data , it worse as cannot mount.
- I try repartition by PIT and fix by e2fsck but it cannot fix my error
- Repartition with "parted" app:
- if i set full size of /data ( it show around 14Gig ) , it will fail ( I/O error)
- if i limit size to 1.5 Gig : able to repartition and mount

I have the same issue

zoftdev said:
Pease , my 7.7 is unbootable now.
I need your help , please check partition table in your 7.7
my result from "parted" ( which should be incorrect) is :
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1153MB 872MB ext4 FACTORYFS
10 1153MB 15.3GB 14.1GB ext4 DATAFS
11 15.3GB 15.7GB 470MB ext4 HIDDEN
12 15.7GB 15.8GB 8389kB FOTA
The reason is after I update to custom ICS rom, my /data become invalid.
At that state I cannot format /data , it worse as cannot mount.
- I try repartition by PIT and fix by e2fsck but it cannot fix my error
- Repartition with "parted" app:
- if i set full size of /data ( it show around 14Gig ) , it will fail ( I/O error)
- if i limit size to 1.5 Gig : able to repartition and mount
Click to expand...
Click to collapse
I am experiencing the same issue (thread here : http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1799949)
Impossible to mount /data and /sdcard
the PIT just allowed me to flash CWM and gain acces to recovery and download mode again, though ODIN stock firmware flashing gets stuck on Factoryfs.img
Can you explain how you did to repartition with parted and to be able to mount /data again after that(don't care if the size is smaller).
Looking into the man of e2fsck and mke2fs help me a lot though. try this :
# e2fsck -p /dev/block/mmcblk0p9 (mmcblk0p10 if you're on P6800) or
# mke2fs /dev/block/mmcblk0p9 (or 10 for P6800)
if you manage to find a solution or even just going a step forward, please tell me on my thread, i'll do the same for you.
Good luck, we'll manage to fix it

[Q] Partition Table (Recovery Image)

Hey Guys
I am developing an App
and need to know the partition table of the Nexus
in general de /dev/block/... of the recovery image

Code:
# mount point fstype device
/system ext4 /dev/block/platform/dw_mmc.0/by-name/system
/cache ext4 /dev/block/platform/dw_mmc.0/by-name/cache
/data ext4 /dev/block/platform/dw_mmc.0/by-name/userdata
/boot emmc /dev/block/platform/dw_mmc.0/by-name/boot
/recovery emmc /dev/block/platform/dw_mmc.0/by-name/recovery
/misc emmc /dev/block/platform/dw_mmc.0/by-name/misc
/bootloader emmc /dev/block/mmcblk0boot0

Lost IMEI while flashing many roms, I have TWRP recovery, but IMEI did not return.

Hello all
I was using and changing many roms during the past time.
I was using it as my daily phone, but stopped using it in the last few months.
Yesterday I noticed that my IMEI is generic (0004999020640000)
I restored TWRP backup from the time I should have had good IMEI and modem files, OS changed to one that was restored, but IMEI is still the same.
When looking at TWRP backup info file recovery.log , there is mention of modem being backed up
/modem | /dev/block/mmcblk0p13 | Size: 88MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p13
Display_Name: modem
Storage_Name: modem
Backup_Path: /modem
Backup_Name: modem
Backup_Display_Name: modem
Storage_Path: /modem
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
previous to recovering from backup, I have tried flashing other modems but to no avail.
current baseband version is I9500XXUHPC1
I have tried others through ODIN but it seems that although I get the message that it went ok, my baseband version does not change
I have tried flashing with ODIN twice in a row, but second time it just stops at 'setup connection' row

Have you tried with PID file as well.

I do not know what is PID file , I cannot find much mention of samsung PID file on google

Have a look at xda for how to unbrick your model and you should find PID file in there

i-tec USBOTG device with HDMI and storage devices (SCSI HDD/SSD, SDcard, USB-3 + USB-C connector)

Hi everybody,
I am looking for ways to mount storage devices with more than one partitions via usbotg and my i-tec 'docking station'.
That worked on my old MOTO G5 on LINEAGEOS17.1 with an USB Stick for vfat and ext4 partitions out of the box, but the luks partitions were not mounted.
WIth my LGV20 and LINEAGEOS18.1 only the first partitions are showing up. The 2nd and 3rd partition are not mounted.
-> I would like to mount an USB Stick with vfat, ext4 (boot) and a luks partition.
-> I would like to mount an HDD with a vfat and luks partition
I somehow feel and know that this should be an easy task, if you know how to mount partitions in android.
I am thinking about trying to mount the partitions in the TWRP terminal and then copy the command in /fstab.elsa
/fstab.elsa content:
# 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
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/boot /boot emmc defaults recoveryonly
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults recoveryonly
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,noatime wait
/dev/block/bootdevice/by-name/userdata /data ext4 discard,nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue wait,check,encryptable=/dev/block/bootdevice/by-name/encrypt
/dev/block/bootdevice/by-name/cache /cache ext4 discard,nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue wait,check
/dev/block/bootdevice/by-name/modem /firmware vfat ro,nosuid,nodev,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/devices/soc/74a4900.sdhci/mmc_host* auto auto nosuid,nodev wait,encryptable=/dev/block/bootdevice/by-name/encrypt
/devices/soc/6a00000.ssusb/6a00000.dwc3/xhci-hcd.0.auto/usb* auto auto defaults defaults
/devices/soc/6a00000.ssusb/6a00000.dwc3/xhci-hcd.1.auto/usb* auto auto defaults defaults
/dev/block/bootdevice/by-name/persist /persist ext4 nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue wait
/etc/fstab content:
/dev/block/bootdevice/by-name/system /system_root ext4 rw 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat rw 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw 0 0
/external_sd vfat rw 0 0
/vendor ext4 rw 0 0
For the terminal mount /dev/sda1 didn't work.
Any ideas how I have to adress the USB device?