To run this commands you need a rooted device with BusyBox and parted. Using stock partition layout. You can change the partition layout to get more or less than 2GB of size for the data partition:
[MOD][GUIDE]Partition your internal memory for better App management (Pit Files)
List of devices by name:
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Click to expand...
Click to collapse
List of fdisk for all given partitions:
Command (needs Superuser or equivalent and Busybox):
su
find /dev/block/platform/dw_mmc/ -name 'mmc*' -exec fdisk -l {} \; > /sdcard/list_of_sgs2_partitions.txt
Click to expand...
Click to collapse
Code:
Disk ./mmcblk0boot0: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0boot0 doesn't contain a valid partition table
Disk ./mmcblk0boot1: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0boot1 doesn't contain a valid partition table
Disk ./mmcblk0p12: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p12 doesn't contain a valid partition table
Disk ./mmcblk0p11: 12.3 GB, 12356419584 bytes
4 heads, 16 sectors/track, 377088 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
./mmcblk0p11p4 1 1 0 0 Empty
Partition 4 does not end on cylinder boundary
Disk ./mmcblk0p10: 2147 MB, 2147483648 bytes
4 heads, 16 sectors/track, 65536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p10 doesn't contain a valid partition table
Disk ./mmcblk0p9: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p9 doesn't contain a valid partition table
Disk ./mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p8 doesn't contain a valid partition table
Disk ./mmcblk0p7: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p7 doesn't contain a valid partition table
Disk ./mmcblk0p6: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p6 doesn't contain a valid partition table
Disk ./mmcblk0p5: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p5 doesn't contain a valid partition table
Disk ./mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p4 doesn't contain a valid partition table
Disk ./mmcblk0p3: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p3 doesn't contain a valid partition table
Disk ./mmcblk0p2: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p2 doesn't contain a valid partition table
Disk ./mmcblk0p1: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p1 doesn't contain a valid partition table
Disk ./mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
./mmcblk0p1 1 1923456 15387647+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Mounted filesystems:
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 415M 32K 415M 4096
/mnt/asec 415M 0K 415M 4096
/mnt/obb 415M 0K 415M 4096
/system 503M 429M 74M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 666M 1G 4096
/mnt/.lfs: Function not implemented
/mnt/sdcard 11G 2G 9G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
temporal fstab:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (ro,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/259:3 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd type tmpfs (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000)
tmpfs on /mnt/sdcard/usbStorage type tmpfs (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000)
/dev/block/vold/179:25 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:25 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/org.ais.archidroid-1 type vfat (ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
AdamOutler said:
Hey guys. I'm doing some work to figure out how to recover Galaxy Nexus devices which are hard-bricked.. ie.. they have a bad or no bootloader installed.
the boot sequence
1. IROM - the Internal ROM which cannot be rewritten on the device. This loads the XLoader.
2. XLoader/MLO - This completes the initialization of the processor and memory, and loads up the relatively huge U-Boot ( Samsung modified this and calls it SBL)
3. UBoot/SBL - This "Bootloader" is almost a complete operating system. The U-Boot initializes the screen, provides Odin mode, Fastboot Mode as well as loading the kernel/recovery and provides a UART debugging mode (Yet to be unlocked).
4. Kernel - Once we reach this point, it's all clear.. the kernel is linux which loads android and all sorts of other things.
The Problem
People are bricking their devices at stage 2 and 3 of this boot sequence... This leaves them unable to boot Fastboot or Odin. The device is 100% interchangable with a brick. These devices are ending up hard bricked.
The solution
We must come up with a way to undo the hard brick. Here are some things i'm looking at to use the native hardware to recover itself.
When you plug in the device (when off), you will immediately notice a Texas Instruments D010 device gets enumerated. This is a debug mode for the processor.
Code:
Bus 001 Device 023: ID 0451:d010 Texas Instruments, Inc.
We've started looking at some bootloader output here: http://forum.xda-developers.com/showthread.php?t=1461986
You can find information about the OMAP4 bootloaders here: http://omapedia.org/wiki/Bootloader_Project
Help
I need help locating drivers to initialize the 0451:d010 device and make it readable from within Linux or Windows.. Generally Linux is easier to find appropriate drivers.
I could use some help collecting more reading materials and resources.
I think together as a community we can take care of this problem.
Click to expand...
Click to collapse
AdamOutler said:
There's more to the boot then the OP mentioned... there's 6 partitions involved, not 4.
irom = hard coded
IBL/PBL = initial bootloader and primitive bootloader
SBL = Secondadary Bootloader finds linux
param = contains paramaters to run the phone and required for boot.
SBL2 = download mode (included in SBL)
PIT = Partiton Information Table
Don't touch any of these files.
If you touch the param.ifs, the phone can still boot, however you will see a black screen if something goes wrong.
Code:
BOOT 00000000 0000 0003FFFF 0001
PIT 00040000 0001 0003FFFF 0001
EFS 00080000 0002 009FFFFF 0028
SBL 00A80000 002A 0013FFFF 0005
SBL2 00BC0000 002F 0013FFFF 0005
PARAM 00D00000 0034 004FFFFF 0014
KERNEL 01200000 0048 0077FFFF 001E
RECOVERY 01980000 0066 0077FFFF 001E
FACTORYFS 02100000 0084 11E7FFFF 047A
DBDATAFS 13F80000 04FE 085FFFFF 0218
CACHE 1C580000 0716 022FFFFF 008C
MODEM 1E880000 07A2 00C7FFFF 0032
07D4 1F500000
Click to expand...
Click to collapse
Aditional links:
* Definitive guide to Bricking *
[Guide] Types of Android backups
[REF] GT-I9100 PIT v Flash Analysis
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
[GUIDE] Making Dump Files Out of Android Device Partitions
/sdcard
This is nice, thank.
But where is from block device the sdcard. How working the "vold"?
How can I partition sdcard with fdisk or with parted?
gyurman said:
This is nice, thank.
But where is from block device the sdcard. How working the "vold"?
How can I partition sdcard with fdisk or with parted?
Click to expand...
Click to collapse
Partition the sdcard from clockworkmod recovery
Thanks, but I want use parted, or fdisk. But what mmcblk0? use sdcard? mmcblk0p11?
Related
Looking for an ODIN flashable SC02COMKF2 baseband as I borked mine.
Por Favor!
http://forum.xda-developers.com/showthread.php?t=1131950
jje
JJEgan said:
http://forum.xda-developers.com/showthread.php?t=1131950
jje
Click to expand...
Click to collapse
SC02COMKF2 in there?
nakagusukumike said:
SC02COMKF2 in there?
Click to expand...
Click to collapse
Have you looked ??
But post was meant to indicate that was the best place to ask as i don't believe what you are asking for exists .
SC02COMKF2 no
KF2 modem/baseband/radio yes .
jje
JJEgan said:
Have you looked ??
But post was meant to indicate that was the best place to ask as i don't believe what you are asking for exists .
SC02COMKF2 no
KF2 modem/baseband/radio yes .
jje
Click to expand...
Click to collapse
Yes, of course I've looked. I would not have posted this request thread if I had not already searched for the baseband (which DOES exist, BTW) in the "Here are all your basebands" thread.
Request remains.
If I end up finding one locally and extracting with ADB, I'll post it up for others with SC02C phones to revert back to.
Yes, of course I've looked.
One of the few then .
Have to assume on SGS2 that the majority don't know what a search button is for .
jje
don't let your pessimism fill threads with detrimental posts
In other news, I've got access to a stock but rooted phone with a baseband intact. Gonna try to dd the block devices out to SD and try to inject with ODIN.
Hmmm.... I wonder if the phone would get pissed off if you just dd'd the good file you want back into the block device! hahahahha
example:
on the stock phone: dd if=/dev/block/mybadassbaseband of=/sdcard/basebandbackupSC02COMFK2.img
then cart the file over to the busted phone and,
dd if=/sdcard/basebamdbackupSC02COMFK2.imb of=/dev/block/bustedbaseband
I know it works in linux if you know EXACTLY what you're doing. hahahah
Not mine, but:
Code:
$ df
df
Filesystem Size Used Free Blksize
/dev 418M 76K 418M 4096
/mnt/asec 418M 0K 418M 4096
/mnt/obb 418M 0K 418M 4096
/mnt/usb 418M 0K 418M 4096
/app-cache 7M 680K 6M 4096
/system 602M 447M 154M 4096
/cache 98M 5M 92M 4096
/efs 19M 8M 11M 4096
/data 1G 164M 1G 4096
/mnt/.lfs: Function not implemented
/mnt/sdcard 11G 160M 11G 32768
/mnt/sdcard/external_sd 7G 1G 5G 32768
/mnt/secure/asec: Permission denied
$ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=7168k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
nil /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
/dev/block/vold/179:17 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
maybe just dump all the block devices and see which ones are between... say 6-20MB?
so i opened all of the block devices with fdisk and found that they are sized as follows:
/dev/block/mmcblk0 15.7GB
/dev/block/mmcblk0p1 20MB /efs ext4
/dev/block/mmcblk0p2 1MB ??
/dev/block/mmcblk0p3 1MB ??
/dev/block/mmcblk0p4 8MB /mnt/.lfs j4fs???
/dev/block/mmcblk0p5 8MB ??
/dev/block/mmcblk0p6 8MB ??
/dev/block/mmcblk0p7 104MB /cache ext4
/dev/block/mmcblk0p8 16MB ??
/dev/block/mmcblk0p9 641MB /system ext4
/dev/block/mmcblk0p10 2147MB /data ext4
/dev/block/mmcblk0p11 12.3GB ??
/dev/block/mmcblk0p12 432MB ??
so I'm guessing either partition 4,5,6 or 8 is the baseband
should have this figured out shortly.
Here's the info for my borked baseband (i9100)
I'm hoping to find someone with an intact baseband and dump the baseband image (and figure out WHERE the baseband image is
Here's what I've got on my phone (which does NOT have the SC02C baseband on it anymore)
Disk /dev/block/mmcblk0p2: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p3: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p5: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p6: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p7: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p9: 641 MB, 641728512 bytes
4 heads, 16 sectors/track, 19584 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p10: 2147 MB, 2147483648 bytes
4 heads, 16 sectors/track, 65536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p11: 12.3 GB, 12356419584 bytes
4 heads, 16 sectors/track, 377088 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p12: 432 MB, 432013312 bytes
4 heads, 16 sectors/track, 13184 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
md5sums are:
6ced0bf7a897e05810253c7efd0fe2d8 /mnt/sdcard/mmcblk0p2.img
1045bfd216ae1ae480dd0ef626f5ff39 /mnt/sdcard/mmcblk0p3.img
7b8b44f05f7844b1f0814c92fac020be /mnt/sdcard/mmcblk0p4.img
84c09574f43239af4d635cf34d9bf335 /mnt/sdcard/mmcblk0p5.img
96995b58d4cbf6aaa9041b4f00c7f6ae /mnt/sdcard/mmcblk0p6.img
67f7f82e16890cd86237d30c79b988b5 /mnt/sdcard/mmcblk0p8.img
did some testing and I feel confident that p8 is the partition that is the modem/baseband on this phone.
I dd'd out all of my small block devices to .img files in the sdcard then MD5 summed them. Then I changed ONLY baseband from KF2 to KE4 and dd'd out ALL of the files, all over again. md5sum on all of them all over again, and only partition 8 changed sums.
NOW, I'm about to dd inject my OLD KF2 baseband image INTO the block device, and see if the OS doesn't take a **** when it reboots...
wish me luck..
Code:
# md5sum ./*.img
6ced0bf7a897e05810253c7efd0fe2d8 ./mmcblk0p2.img
1045bfd216ae1ae480dd0ef626f5ff39 ./mmcblk0p3.img
7b8b44f05f7844b1f0814c92fac020be ./mmcblk0p4.img
84c09574f43239af4d635cf34d9bf335 ./mmcblk0p5.img
96995b58d4cbf6aaa9041b4f00c7f6ae ./mmcblk0p6.img
f8b0f155f86fe161b6b3501ee2bfd20d ./mmcblk0p8.img
#md5sum ./basebands/*.img
md5sum: can't open './basebands/*.img': No such file or directory
# cd ./basebands
/mnt/sdcard/basebands
# ls
i9100KF2
# md5sum ./i9*/*.img
6ced0bf7a897e05810253c7efd0fe2d8 ./i9100KF2/mmcblk0p2.img
1045bfd216ae1ae480dd0ef626f5ff39 ./i9100KF2/mmcblk0p3.img
7b8b44f05f7844b1f0814c92fac020be ./i9100KF2/mmcblk0p4.img
84c09574f43239af4d635cf34d9bf335 ./i9100KF2/mmcblk0p5.img
96995b58d4cbf6aaa9041b4f00c7f6ae ./i9100KF2/mmcblk0p6.img
67f7f82e16890cd86237d30c79b988b5 ./i9100KF2/mmcblk0p8.img
#
so I just did:
Code:
dd if=/mnt/sdcard/basebands/i9100/mmcblk0p8.img of=/dev/block/mmcblk0p8
after it completed I pulled the battery and restarted the phone
MY PHONE HAS IN FACT REVERTED BASEBANDS BY DOING THIS ACTION!!!!!
SOOOO... my buddy (who still isn't here yet...) who still has the docomo baseband... I'll be extracting his and posting it for you all. hopefully soon.
We'll see if this fixes my ****ty reception and GPS not working. I know it won't fix 1seg though.
CHEERS MOFOS!!!
or is there anybody out there with a rooted SC02C still showing an SC02C baseband who feels like doing this:
Code:
su -
dd if=/dev/block/mmcblk0p8 of=/mnt/sdcard/mmcblk0p8.img
then send me the mmcblk0p8.img file that's on your SD card?
I'd be forever grateful!!
I'll try to do that tonight or tomorrow morning (I have only rooted, not changed CSC or for that matter even the rest of PDA). PM me an address to send to you at.
evildave_666 said:
I'll try to do that tonight or tomorrow morning (I have only rooted, not changed CSC or for that matter even the rest of PDA). PM me an address to send to you at.
Click to expand...
Click to collapse
PM Sent, thanks man!
IT WORKED, I'm back on
Baseband: SC02COMKF2
THANKS.
Will post the file in a few.
reception went up 2 or 3 bars at the same battery level and location in my house. Still no GPS on my ROM though, reverting back to stock backup and will see if I get GPS back...
GPS is still not working with the new baseband, but the reception is soooooooooooo much better.
Any chance I could get someone on a rooted, stock image to grab these:
Code:
su -
dd if=/dev/block/mmcblk0p2 of=/mnt/sdcard/mmcblk0p2.img
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/mmcblk0p3.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/mmcblk0p6.img
and send them to me? I'll figure out which one is GPS.
I'm gonna go to litening rom now and put the docomo baseband on.
battery life has been amazing on this baseband!
nakagusukumike said:
GPS is still not working with the new baseband, but the reception is soooooooooooo much better.
Any chance I could get someone on a rooted, stock image to grab these:
Code:
su -
dd if=/dev/block/mmcblk0p2 of=/mnt/sdcard/mmcblk0p2.img
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/mmcblk0p3.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/mmcblk0p6.img
and send them to me? I'll figure out which one is GPS.
I'm gonna go to litening rom now and put the docomo baseband on.
Click to expand...
Click to collapse
Any way to package this solution into something flashable for the rest of us? still having the GPS problem?
So, today I was transferring some files to my phone using the latest Cyanogenmod nightly in MTP mode. In this mode, there is no splash screen that allows you to disconnect your phone from USB mode, so I assumed that it was safe to just disconnect the USB cable when no transfer is occurring. I have done this many times with no problem.
Well, after disconnecting this time, the phone won't mount the internal SD either in the phone itself, by USB or in CWM. I did the following and it looks like the internal SD has a corrupted partition.
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # cd /dev/block
[email protected]:/dev/block # ls | grep mmcblk0
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
[email protected]:/dev/block # fdisk -l mmcblk0
Disk mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
[email protected]:/dev/block # fdisk -l mmcblk0p11
Disk mmcblk0p11: 11.8 GB, 11895046144 bytes
4 heads, 16 sectors/track, 363008 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk mmcblk0p11 doesn't contain a valid partition table
[email protected]:/dev/block #
What command would I use to reformat mmcblk0p11? mkfs.vfat /dev/block/mmcblk0p11?
Also, just a warning for others to not use MTP mode in Cyanogenmod due to this bug.
So, I did a factory reset in Cyanogenmod with the erase SD card option ticked and it looks like everything is working now. Hopefully they will soon fix the MTP splash screen so that others will not have this issue again.
I have a problem, I've flashed CWM Recovery v6.0.3.2 on my i9505, but when it starts I get the following errors:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
I've tried everything (fix permissions, format cache)
Why? How can I solve this?
Here's the log file:
Code:
Starting recovery on Sun Feb 22 07:06:52 1970
framebuffer: fd 4 (1080 x 1920)
ClockworkMod Recovery v6.0.3.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p20 (null) 0
2 /system ext4 /dev/block/mmcblk0p16 (null) 0
3 /data ext4 /dev/block/mmcblk0p29 (null) -16384
4 /cache ext4 /dev/block/mmcblk0p18 (null) 0
5 /recovery emmc /dev/block/mmcblk0p21 (null) 0
6 /sdcard datamedia /dev/null (null) 0
7 /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
W:failed to mount /dev/block/mmcblk0p18 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.hardware=qcom
ro.boot.debug_level=0x4f4c
ro.boot.cp_debug_level=0x55FF
ro.boot.emmc_checksum=3
ro.boot.bootloader=I9505XXUAMDM
ro.boot.nvdata_backup=0
ro.boot.boot_recovery=1
ro.boot.emmc=true
ro.boot.serialno=b3126c9c
ro.boot.baseband=mdm
ro.serialno=b3126c9c
ro.bootmode=unknown
ro.baseband=mdm
ro.bootloader=I9505XXUAMDM
ro.hardware=qcom
ro.revision=11
ro.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JDQ39E
ro.build.display.id=cm_jfltexx-userdebug 4.2.2 JDQ39E eng.hudson.20130608.221635 test-keys
ro.build.version.incremental=eng.hudson.20130608.221635
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Jun 8 22:17:19 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=GT-I9505
ro.product.brand=samsung
ro.product.name=jfltexx
ro.product.device=jflte
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
ro.build.product=jflte
ro.build.description=jfltexx-user 4.2.2 JDQ39 I9505XXUAMDE release-keys
ro.build.fingerprint=samsung/jfltexx/jflte:4.2.2/JDQ39/I9505XXUAMDE:user/release-keys
ro.build.characteristics=default
ro.cm.device=jfltexx
rild.libargs=-d /dev/smd0
telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.hwui.text_cache_width=2048
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.chipname=apq8064
ro.ril.hsxpa=1
ro.ril.gprsclass=10
persist.radio.add_power_save=1
persist.radio.snapshot_disabled=1
persist.radio.use_se_table_only=1
persist.radio.fill_eons=1
com.qc.hardware=true
persist.radio.apm_sim_not_pwdn=1
ro.telephony.call_ring.multiple=0
ro.sf.lcd_density=480
ro.ril.transmitpower=true
ro.opengles.version=131072
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
persist.audio.speaker.location=high
ro.qc.sdk.audio.fluencetype=fluence
persist.timed.enable=true
ro.emmc.sdcard.partition=17
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
persist.ims.regmanager.mode=0
ro.config.ehrpd=true
persist.omh.enabled=1
persist.data_netmgrd_nint=16
lpa.decode=true
rild.libpath=/system/lib/libril-qc-qmi-1.so
ril.subscription.types=NV,RUIM
ro.cdma.subscribe_on_ruim_ready=true
persist.radio.no_wait_for_card=0
media.aac_51_output_enabled=true
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ro.telephony.ril.v3=newDriverCall
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0
ro.telephony.ril_class=SamsungQualcommRIL
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.hwui.texture_cache_size=48
ro.hwui.layer_cache_size=32
ro.hwui.path_cache_size=8
ro.hwui.shape_cache_size=2
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=512
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130609-UNOFFICIAL-jfltexx
ro.modversion=10.1-20130609-UNOFFICIAL-jfltexx
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Deneb.ogg
ro.config.alarm_alert=Hassium.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p18 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p18 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p18 (Invalid argument)
W:Can't unlink /cache/recovery/command
I:Can't partition non-vfat: datamedia
I:Can't format unknown volume: /emmc
And the output of fdisk -l /dev/block/mmcblk*:
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk*
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Disk /dev/block/mmcblk0p1: 13 MB, 13078528 bytes
4 heads, 16 sectors/track, 399 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1p1 ? 12158374 29994462 570754815+ 72 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(357, 116, 40) logical=(12158373, 2, 5)
Partition 1 has different physical/logical endings:
phys=(357, 32, 45) logical=(29994461, 2, 3)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p1p2 ? 2635774 32886216 968014120 65 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(288, 115, 43) logical=(2635773, 3, 3)
Partition 2 has different physical/logical endings:
phys=(367, 114, 50) logical=(32886215, 0, 2)
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p1p3 ? 29216898 59467339 968014096 79 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(366, 32, 33) logical=(29216897, 3, 10)
Partition 3 has different physical/logical endings:
phys=(357, 32, 43) logical=(59467338, 1, 9)
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p1p4 ? 1 56831664 1818613248 d Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(372, 97, 50) logical=(0, 0, 1)
Partition 4 has different physical/logical endings:
phys=(0, 10, 0) logical=(56831663, 3, 16)
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Disk /dev/block/mmcblk0p10: 14 MB, 14286848 bytes
4 heads, 16 sectors/track, 436 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p11: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p12: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p13: 0 MB, 798720 bytes
4 heads, 16 sectors/track, 24 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p14: 0 MB, 798720 bytes
4 heads, 16 sectors/track, 24 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p14 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p15: 0 MB, 798720 bytes
4 heads, 16 sectors/track, 24 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p15 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p17: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p18: 2170 MB, 2170552320 bytes
4 heads, 16 sectors/track, 66240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p18 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p19: 6 MB, 6291456 bytes
4 heads, 16 sectors/track, 192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p19 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p2: 54 MB, 54030336 bytes
4 heads, 16 sectors/track, 1648 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p2p1 ? 12158374 29994462 570754815+ 72 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2p2 ? 2635774 32886216 968014120 65 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p2p3 ? 29216898 59467339 968014096 79 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p2p4 ? 1 56831664 1818613248 d Unknown
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Disk /dev/block/mmcblk0p20: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p20 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p21: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p21 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p22: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p22 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p23: 6 MB, 6291456 bytes
4 heads, 16 sectors/track, 192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p23 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p24: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p24 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p25: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p25 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p26: 9 MB, 9437184 bytes
4 heads, 16 sectors/track, 288 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p26 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p27: 524 MB, 524288000 bytes
4 heads, 16 sectors/track, 16000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p27 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p28: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p28 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p29: 9961 MB, 9961472000 bytes
4 heads, 16 sectors/track, 304000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p29 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p3: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p4: 0 MB, 262144 bytes
4 heads, 16 sectors/track, 8 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p5: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p6: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p7: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p8: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/mmcblk0p9: 17 MB, 17301504 bytes
4 heads, 16 sectors/track, 528 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/mmcblk1: 1977 MB, 1977614336 bytes
64 heads, 63 sectors/track, 957 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 957 1929244+ 6 FAT16
Disk /dev/block/mmcblk1p1: 1975 MB, 1975546368 bytes
4 heads, 16 sectors/track, 60288 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
UP
UP?
incompatible recovery.img?
This can be caused by an incompatible recovery.img. I had this issue by downloading a recovery.img for my phone, but turned out to have an incorrect recovery.fstab file in it. This caused wrong mount points being assigned. Digging into this problem, the contents of /proc/emmc should match the recovery.fstab in the recovery.img you're using. Where did you get the CWM recovery from?
Hello!
TL/DR version: I updated a L5 (E612F - Vivo BR) with a V20 KDZ file and the internal storage, that was 8GB is seen by fdisk as ~3GB. There seems to be something wrong with the partition table. Is it possible to revert it back to the original value?
Detailed version:
My girlfriend bought a L5 (E612F - Vivo BR) and urged me to remove all the LG crap that came with the phone.
E612f is known for not being easily rootable and so on, so it was a struggle to put CM10.x in it. After many attempts and a few boot loops, I managed to use an E610 KDZ + E610 recovery and other images from this thread: http://forum.xda-developers.com/showthread.php?t=2186161
The problem is that fdisk reports that the internal SD has only ~3GB of size, but the device ghas 8GB internal SD. Because of that, she gets low space errors all the time:
Code:
1|[email protected]:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 3 128 1003+ 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 256 1024 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 257 465152 3719168 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8193 8704 4096 47 Unknown
/dev/block/mmcblk0p6 8705 9216 4096 2c Unknown
/dev/block/mmcblk0p7 9217 9728 4096 58 Unknown
/dev/block/mmcblk0p8 9729 12800 24576 77 Unknown
/dev/block/mmcblk0p9 12801 13824 8192 48 Unknown
/dev/block/mmcblk0p10 13825 14336 4096 4a Unknown
/dev/block/mmcblk0p11 14337 14848 4096 4b Unknown
/dev/block/mmcblk0p12 14849 18432 28672 49 Unknown
/dev/block/mmcblk0p13 18433 22016 28672 6c Unknown
/dev/block/mmcblk0p14 22017 100096 624640 83 Linux
/dev/block/mmcblk0p15 100353 101376 8192 83 Linux
/dev/block/mmcblk0p16 101377 114176 102400 83 Linux
/dev/block/mmcblk0p17 114177 115200 8192 60 Unknown
/dev/block/mmcblk0p18 115201 116224 8192 83 Linux
/dev/block/mmcblk0p19 116225 117760 12288 6b Unknown
/dev/block/mmcblk0p20 117761 470656 2823168 83 Linux
/dev/block/mmcblk0p21 471041 471552 4096 ff Unknown
/dev/block/mmcblk0p22 471553 471680 1024 ff Unknown
/dev/block/mmcblk0p23 472065 474112 16384 83 Linux
Could the KDZ from another version (E610) be the culprit for this? Any idea how to deal with it? Thanks!
UPDATE:
Working on QPST tools now:
* Need to find prog_emmc_firehose_8x10.mbn
The goal of this project is to gather all the information and tools required in unbricking a hard bricked Moto E (1st Generation).
Possible methods:
1. Blankflash
Requires: singleimage_8x10.mbn, qboot utility for Moto E, programmer_8x10.mbn
2. MiFlash
Requires: fastboot script, fastboot or mfastboot, MPRG8x10.hex, 8x10_msimage.mbn, rawprogram0.xml, patch0.xml
3. QPST
Requires: QPST tool, rawprogram0.xml, patch0.xml, prog_emmc_firehose_8x10.mbn, flat build/single image, multi build/sparse images.
Click to expand...
Click to collapse
XDA:DevDB Information
Unbrick Moto E, Tool/Utility for the Moto E
Contributors
206bone
Version Information
Status: Testing
Created 2016-02-02
Last Updated 2016-02-05
Reserved
Creating partition.xml file:
1. Post from senior member darkspr1te:
http://forum.xda-developers.com/showpost.php?p=36019312&postcount=13
2. Another post from a blog.
Reserved
For reference:
eMMC Partition tool (QPST tools)
Qcom Partition Type Cross Reference (To find Partition IDs for creating partition.xml)
Moto G blank flash tutorial
Creating PIT
Moto E PITs
Moto G PIT
R&D on using Qualcomm
Unbrick Qualcomm Snapdragon devices
Decompiler
GPT Parser
PartitioningTool.py
Moto E source code distros
Sparse Converter
R&D Building Qualcomm Bootloaders
GUID Partition Table (GPT)
Master Boot Record (MBR)
EFI System Partition
Unified Extensible Firmware Interface (UEFI)
UEFI Programming
Test Boot loader
X86_Assembly/Bootloaders
Tell me how I can help and i'll try my best dude
iTudorS said:
Tell me how I can help and i'll try my best dude
Click to expand...
Click to collapse
Thank you so much bro... Could you please provide me the full partition information table? More the information, more better..
Here's the link on how to do it: Partition table
I've just dissected a 8x10_msimage.mbn file. And I found 4 partitions:
1. SBL1
2. DDR (No info on DDR.)
3. RPM
4. TZ
I don't know what this DDR file is. I'd like to see the size of this file(in Kb) on the partition table.
206bone said:
Thank you so much bro... Could you please provide me the full partition information table? More the information, more better..
Here's the link on how to do it: Partition table
I've just dissected a 8x10_msimage.mbn file. And I found 4 partitions:
1. SBL1
2. DDR (No info on DDR.)
3. RPM
4. TZ
I don't know what this DDR file is. I'd like to see the size of this file(in Kb) on the partition table.
Click to expand...
Click to collapse
Hi, I love to help and more in electronics field. Here's my contribution for MotoE XT1022 Condor Device.
Code:
major minor #blocks name
7 0 85648 loop0
7 1 22980 loop1
7 2 32380 loop2
7 3 91916 loop3
7 4 27160 loop4
7 5 4180 loop5
7 6 15668 loop6
7 7 3136 loop7
253 0 524288 zram0
179 0 3866624 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 512 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 465024 mmcblk0p33
259 2 917504 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 2350464 mmcblk0p36
179 32 512 mmcblk0rpmb
179 64 30466048 mmcblk1
179 65 30465024 mmcblk1p1
254 0 85648 dm-0
254 1 22980 dm-1
254 2 32380 dm-2
254 3 91916 dm-3
254 4 27160 dm-4
254 5 4180 dm-5
254 6 15668 dm-6
254 7 3136 dm-7
7 8 20892 loop8
254 8 20892 dm-8
7 9 61628 loop9
254 9 61628 dm-9
7 10 19848 loop10
254 10 19848 dm-10
7 11 36560 loop11
254 11 36560 dm-11
7 12 35516 loop12
254 12 35516 dm-12
7 13 7312 loop13
254 13 7312 dm-13
Here is the detailed partition info obtained from msm_sdcc.1:
Code:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
boot -> /dev/block/mmcblk0p31
cache -> /dev/block/mmcblk0p33
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p28
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p35
logo -> /dev/block/mmcblk0p27
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p29
recovery -> /dev/block/mmcblk0p32
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p12
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sdiBackup -> /dev/block/mmcblk0p14
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p34
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p13
userdata -> /dev/block/mmcblk0p36
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
Here is the detailed partition info obtained from msm_sdcc.2:
Code:
mmcblk1 -> /dev/block/mmcblk1
mmcblk1p1 -> /dev/block/mmcblk1p1
DDR partition contain DDR.bin. This image addresses the Physical RAM Memory in the device... common on Elpida Ram Powered Devices. Correct me if I'm wrong please.
Tell me anything that you need.
try this files
206bone said:
Can you please help me out with finding the IDs of each partition in mmcblk0 in the boot record?...
Click to expand...
Click to collapse
Hi friend, as requested:
IDs from mmcblk0:
Code:
Disk /dev/block/mmcblk0: 7733248 sectors, 3776M
Logical sector size: 512
Partition table holds up to 36 entries
First usable sector is 34, last usable sector is 7733214
Number Start (sector) End (sector) Size Code Name
1 256 131327 64.0M 0700 modem
2 131328 132351 512K 0700 sbl1
3 132352 132415 32768 0700 DDR
4 132608 133631 512K 0700 aboot
5 135608 136007 200K 0700 rpm
6 136608 137407 400K 0700 tz
7 137608 137671 32768 0700 sdi
8 137672 138695 512K 0700 utags
9 138696 142791 2048K 0700 logs
10 142792 147455 2332K 0700 padA
11 147456 148479 512K 0700 abootBackup
12 150456 150855 200K 0700 rpmBackup
13 151456 152255 400K 0700 tzBackup
14 152456 152519 32768 0700 sdiBackup
15 152520 153543 512K 0700 utagsBackup
16 153544 155647 1052K 0700 padB
17 155648 158719 1536K 0700 modemst1
18 158720 161791 1536K 0700 modemst2
19 161792 162767 488K 0700 hob
20 162768 162831 32768 0700 dhob
21 163072 166143 1536K 0700 fsg
22 166144 166145 1024 0700 fsc
23 166146 166161 8192 0700 ssd
24 166162 168209 1024K 0700 sp
25 168210 168465 128K 0700 cid
26 168466 174609 3072K 0700 pds
27 174610 182801 4096K 0700 logo
28 182802 190993 4096K 0700 clogo
29 191232 207615 8192K 0700 persist
30 207616 208639 512K 0700 misc
31 208640 229039 9.9M 0700 boot
32 229040 249599 10.0M 0700 recovery
33 249600 1179647 454M 0700 cache
34 1179648 3014655 896M 0700 system
35 3014656 3031039 8192K 0700 kpan
36 3031040 7731967 2295M 0700 userdata
Info from mmcblk0p1:
Code:
Disk /dev/block/mmcblk0p1: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders, total 131072 sectors
Info from mmcblk0p2:
Code:
Disk /dev/block/mmcblk0p2: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p3:
Code:
Disk /dev/block/mmcblk0p3: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p4:
Code:
Disk /dev/block/mmcblk0p4: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p5:
Code:
Disk /dev/block/mmcblk0p5: 0 MB, 204800 bytes
4 heads, 16 sectors/track, 6 cylinders, total 400 sectors
Info from mmcblk0p6:
Code:
Disk /dev/block/mmcblk0p6: 0 MB, 409600 bytes
4 heads, 16 sectors/track, 12 cylinders, total 800 sectors
Info from mmcblk0p7:
Code:
Disk /dev/block/mmcblk0p7: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p8:
Code:
Disk /dev/block/mmcblk0p8: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p9:
Code:
Disk /dev/block/mmcblk0p9: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders, total 4096 sectors
Info from mmcblk0p10:
Code:
Disk /dev/block/mmcblk0p10: 2 MB, 2387968 bytes
4 heads, 16 sectors/track, 72 cylinders, total 4664 sectors
Info from mmcblk0p11:
Code:
Disk /dev/block/mmcblk0p11: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p12:
Code:
Disk /dev/block/mmcblk0p12: 0 MB, 204800 bytes
4 heads, 16 sectors/track, 6 cylinders, total 400 sectors
Info from mmcblk0p13:
Code:
Disk /dev/block/mmcblk0p13: 0 MB, 409600 bytes
4 heads, 16 sectors/track, 12 cylinders, total 800 sectors
Info from mmcblk0p14:
Code:
Disk /dev/block/mmcblk0p14: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p15:
Code:
Disk /dev/block/mmcblk0p15: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p16:
Code:
Disk /dev/block/mmcblk0p16: 1 MB, 1077248 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2104 sectors
Info from mmcblk0p17:
Code:
Disk /dev/block/mmcblk0p17: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p18:
Code:
Disk /dev/block/mmcblk0p18: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p19:
Code:
Disk /dev/block/mmcblk0p19: 0 MB, 499712 bytes
4 heads, 16 sectors/track, 15 cylinders, total 976 sectors
Info from mmcblk0p20:
Code:
Disk /dev/block/mmcblk0p20: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p21:
Code:
Disk /dev/block/mmcblk0p21: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p22:
Code:
Disk /dev/block/mmcblk0p22: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders, total 2 sectors
Info from mmcblk0p23:
Code:
Disk /dev/block/mmcblk0p23: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders, total 16 sectors
Info from mmcblk0p24:
Code:
Disk /dev/block/mmcblk0p24: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors
Info from mmcblk0p25:
Code:
Disk /dev/block/mmcblk0p25: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders, total 256 sectors
Info from mmcblk0p26:
Code:
Disk /dev/block/mmcblk0p26: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders, total 6144 sectors
Info from mmcblk0p27:
Code:
Disk /dev/block/mmcblk0p27: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Info from mmcblk0p28:
Code:
Disk /dev/block/mmcblk0p28: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Info from mmcblk0p29:
Code:
Disk /dev/block/mmcblk0p29: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders, total 16384 sectors
Info from mmcblk0p30:
Code:
Disk /dev/block/mmcblk0p30: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p31:
Code:
Disk /dev/block/mmcblk0p31: 10 MB, 10444800 bytes
4 heads, 16 sectors/track, 318 cylinders, total 20400 sectors
Info from mmcblk0p32:
Code:
Disk /dev/block/mmcblk0p32: 10 MB, 10526720 bytes
4 heads, 16 sectors/track, 321 cylinders, total 20560 sectors
Info from mmcblk0p33:
Code:
Disk /dev/block/mmcblk0p33: 476 MB, 476184576 bytes
4 heads, 16 sectors/track, 14532 cylinders, total 930048 sectors
Info from mmcblk0p34:
Code:
Disk /dev/block/mmcblk0p34: 939 MB, 939524096 bytes
4 heads, 16 sectors/track, 28672 cylinders, total 1835008 sectors
Info from mmcblk0p35:
Code:
Disk /dev/block/mmcblk0p35: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders, total 16384 sectors
Info from mmcblk0p36:
Code:
Disk /dev/block/mmcblk0p36: 2406 MB, 2406875136 bytes
4 heads, 16 sectors/track, 73452 cylinders, total 4700928 sectors
Hope it helps!
Thanks dude...
Ready To Help
Hey Friend I dont know how to make this files But I hav trust on You so Please If you Make this File I have a hard Bricked Moto E and I an Ready to Test jst Give Me File And Instructions What to Do ... Thank You
206bone said:
Thanks dude...
Click to expand...
Click to collapse
You're welcome. :good:
Maybe its helpfull
Will this method mentioned for LG G2 with Qualcomm(QHSB BULK) fix the file or here it's totally different thing? I am really keen in this project because my device has been dead since 5 months.
Have you got a solution?
I would like to participate in this project
Can i be of some use in this project ? Ive tried all possible ways to get my phone to life but failed .
Keep it up Guys..... We all are waiting. ..
Thanks guyzz to start the project of reviving moto e back to life i too bricked it 2-3 month ago. ill help u guzz in testing and collecting data and giving it here.lets unbrick our device....
[Edit]- if u need files from moto e tell me ..... i have a spare working moto e also.
You can recreate all the files needed, but you can't sign them. Non-signed files won't pass verification and it won't work.
Don't let that demotivate you though, you may come up with something that we didn't see when the first Moto G bricks came around more than year ago.
Try and report back
Did anyone try this method for One Plus, please report back.
Klock2 said:
Did anyone try this method for One Plus, please report back.
Click to expand...
Click to collapse
those files are for one plus one, wont work on moto e
iTudorS said:
those files are for one plus one, wont work on moto e
Click to expand...
Click to collapse
Its not even proper for OnePlus One but ColorOS plays is its role here. So I think it might work as Qualcomm Device i.e QHSBULK