Related
The DZ is advertised by HTC as having 1.5 GB internal storage, but the G2 is advertised as having 4 GB. As proved via teardown pictures (see http://forum.xda-developers.com/showthread.php?t=832686 ), the two phones have exactly the same 4 GB storage chip (NAND), but both also report a lot less memory available to the user (2.1 GB seems to be there if you examine the partitioning).
This has led people to try and investigate where the "missing" memory has gone, e.g. what is using it up, can we get access to it, etc.
This "mystery" seems now to have been solved, and has been posted up in the Wiki at http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#The_Missing_2GB
A summary of this was kindly posted up by dhkr123 in the G2 forums at http://forum.xda-developers.com/showpost.php?p=9174115&postcount=22 , specifically :
There are 2.1 GB of internal storage addressable by the kernel. This piece of space is divided up into several partitions, for the radio, the SPL, the SYSTEM, the USERDATA, the CACHE, and several other things. All of these partitions are accounted for within the 2.1 GB.
What has been found is that a 1-time write deal to the eMMC is responsible for converting most of the internal storage from MLC (multi-level cell, specifically, 2 bits per cell) into SLC (single-level cell, 1 bit per cell) for the purpose of improving performance and durability.
Specifically, the entire eMMC is 4 GB, and 2.1 GB are accessible, that means that ~200 MB remains MLC, the remaining 3.8 GB is converted into SLC, offering 1.9 GB. 1.9GB + 200MB = 2.1 GB.
Mystery solved, nothing you can do about it.
But understand that it is faster and more reliable like this.
Click to expand...
Click to collapse
So apparently the hardware has been setup so that there is 2.1 GB available for storage for performance and reliability reasons, and it is unlikely this can be changed.
Just found some further explanation and diagrams on this at http://tjworld.net/wiki/Android/HTC/EMMC/UnderstandingUserCapacity
Nice post
Thanks for sharing.
Even with the "hidden" partition, huh... I have installed more apps than never and I still have near-1GB free
And I think the internal mem for process and running system is a great idea since the phone runs smoother than butter
Maybe that's why nobody's talking 'bout apps2sd, which is a common topic @ other phone's fora
How do you have near 1gb free?
CacheMate for me reports 1,078MB (1.07 GB) total data, 338MB used, 760 whatever free, not 2.1GB. Is this with a ROMed DZ, stripped of major components in the system and whatnot? (ie, Sense)
GlitchZero said:
CacheMate for me reports 1,078MB (1.07 GB) total data, 338MB used, 760 whatever free, not 2.1GB.
Click to expand...
Click to collapse
That doesn't sound right at all. But I don't know anything about CacheMate.
It's a root app, clears out the dalvik (I believe) and app caches that have built up, but it shows Total Memory, Memory Used, and Free Memory, and those are my readings, and they are consistent to .01 of a megabyte with what it says in SD & Phone Storage in my Settings.
But there's 2.1 GB total user storage on the phone, so it doesn't sound like it's reporting it correctly ?
Here's the partitioning on a DZ, taken from http://tjworld.net/wiki/Android/HTC/Vision/EmmcPartitioning (duplicate rows deleted, see the link for more details) :
# fdisk -ul /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2332 MB, 2332033024 bytes
1 heads, 16 sectors/track, 284672 cylinders, total 4554752 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4554750 2272311 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 137216 3072 4a Unknown
/dev/block/mmcblk0p14 137218 143361 3072 4b Unknown
/dev/block/mmcblk0p15 143363 145410 1024 74 Unknown
/dev/block/mmcblk0p16 145412 163326 8957+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1343486 571391+ 83 Linux
/dev/block/mmcblk0p26 1343488 3577854 1117183+ 83 Linux
/dev/block/mmcblk0p27 3577856 4192254 307199+ 83 Linux
/dev/block/mmcblk0p28 4192256 4234750 21247+ 19 Unknown
/dev/block/mmcblk0p29 4234752 4235263 256 23 Unknown
If you add up the sizes of partitions 4, 25, 26 and 27 (i.e. the big ones) then there is 2.1 GB in total. I wonder if CacheMate is only looking at partition 4 (1.1 GB) and not the rest ? I could be way off though.
I faced an problem with sd card builds, need to see if it is only to me or is also present to you. Problem is with sd card (partition 1) coruption!
fdisk mmcmlk0 displayng no coruption!
Code:
fdisk /dev/block/mmcblk0
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7948 MB, 7948206080 bytes
245 heads, 62 sectors/track, 1021 cylinders
Units = cylinders of 15190 * 512 = 7777280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1021 7754464 b Win95 FAT32
but fdisk partition (mmcblkop1) displaying very very good coruption with 4 partitions inside partition
Code:
fdisk /dev/block/mmcblk0p1
The number of cylinders for this disk is set to 242327.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
p
Disk /dev/block/mmcblk0p1: 7940 MB, 7940571136 bytes
4 heads, 16 sectors/track, 242327 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 does not end on cylinder boundary
/dev/block/mmcblk0p1p2 ? 2635774 32886216 968014120 65 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p1p3 ? 29216898 59467339 968014096 79 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p1p4 ? 45088769 45089636 27749+ d Unknown
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
So its like we have problem! Also I think this is all a result of problems we have with the file transfer to disk!
Also in log I see all time enter/leave (but phone is in sleep mode!):
Code:
<4>[ 568.114746] msmsdcc_resume enter
<4>[ 568.114928] msmsdcc_resume leave
<4>[ 568.114986] msmsdcc_resume enter
<4>[ 568.115103] msmsdcc_resume leave
I don't know whats wrong but we have coruption in sd card, initrd related? or kernel side related? or android side related??? I created two fat32 partitions this time, first is for all android files /bootsdcard, seccond is mounted as a /mnt/sdcard, initrd is edited allso! Got coruption in all partitions Why???
Code:
Disk /dev/block/mmcblk0p1: 6892 MB, 6892752384 bytes
4 heads, 16 sectors/track, 210350 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1p1 ? 29215178 31850952 84344761 69 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p1p2 ? 26586242 55803140 934940732+ 73 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p1p3 ? 41 41 0 74 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p1p4 45088769 45089587 26207+ 0 Empty
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Command (m for help): q
q
# fdisk /dev/block/mmcblk0p2
fdisk /dev/block/mmcblk0p2
The number of cylinders for this disk is set to 32130.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
p
Disk /dev/block/mmcblk0p2: 1052 MB, 1052835840 bytes
4 heads, 16 sectors/track, 32130 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p2p1 ? 29215178 31850952 84344761 69 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2p2 ? 26586242 55803140 934940732+ 73 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p2p3 ? 41 41 0 74 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p2p4 45088769 45089587 26207+ 0 Empty
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Anyone who use google page release want to confirm our problem? How to see if coruption exist in your sd card? Simply open android terminal emulator, type "su" press enter and confirm administrator, type "fdisk /dev/block/mmcblk0p1" and press enter, type "p" and press enter, to exit from fdisk type "q" and press enter. I waiting you reply
Code:
Disk /dev/block/mmcblk0p1: 1971 MB, 1971416576 bytes
4 heads, 16 sectors/track, 60162 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1p1 ? 27627926 54209359 850605874+ 6e Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p1p2 ? 30526934 45850528 490354992+ ff Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p1p3 ? 28151302 30786496 84326194+ 74 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p1p4 1 55513776 1776440832 0 Empty
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Code:
# fdisk /dev/block/mmcblk0p1
The number of cylinders for this disk is set to 120880.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0p1: 3960 MB, 3960995840 bytes
4 heads, 16 sectors/track, 120880 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1p1 ? 27627926 54209359 850605874+ 6e Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p1p2 ? 30526934 45850528 490354992+ ff Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p1p3 ? 28151302 30786496 84326194+ 74 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p1p4 45088769 45089616 27106 0 Empty
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
In case this info is of use to someone...
Trying to understand what goes where,
Here is the partition table of a U8800:
#######################################
Disk /dev/sdb: 3959 MB, 3959422976 bytes
1 heads, 62 sectors/track, 124729 cylinders, total 7733248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 491520 245760 b W95 FAT32
/dev/sdb2 * 491521 492520 500 4d QNX4.x
/dev/sdb3 492521 498520 3000 46 Unknown
/dev/sdb4 498521 7733247 3617363+ 5 Extended
/dev/sdb5 524288 548863 12288 59 Unknown
/dev/sdb6 655360 921599 133120 4c Unknown
/dev/sdb7 1048576 1049575 500 5a Unknown
/dev/sdb8 1179648 1185791 3072 58 Unknown
/dev/sdb9 1310720 1324719 7000 50 OnTrack DM
/dev/sdb10 1441792 1447935 3072 4a Unknown
/dev/sdb11 1572864 1579007 3072 4b Unknown
/dev/sdb12 1703936 2154495 225280 83 Linux
/dev/sdb13 2228224 3457023 614400 83 Linux
/dev/sdb14 3538944 7733247 2097152 69 Unknown
#############################################
sdb1: This is the FAT32 partition that gets mounted when we boot into pink screen;
It holds, among other files, EMMCBOOT.MBN, which, if not present and as far as I've experimented, will get the phone straight into a blue screen and initiate a flash procedure if a 'dload' folder with a ROM is found in the sdcard. The contens of this partition are changed when a ROM is flashed.
sdb2: Is flagged as bootable, and holds an (so far) unknown filesystem (if any; could hold a raw binary image, for instance);
sdb3: Holds an unknown filesystem, if any. This partition is changed whenever you flash a ROM. dumping this partition back, from any 2.3BETA, to a 2.3 (B522) running phone, will get the USB pink screen mode working again, allowing acces to sdb1.
sdb5: holds an unknown filesystem if any; dumping this one back gets us the original "IDEOS" logo and, probably, whatever is needed to make previous CWM backups work again.
sdb6: ext3 filesystem with a directory called "recovery".
sdb7: Unknown filessytem, if any.
sdb8: Unknown filesystem, if any.
sdb9: Unknown filesystem, if any.
sdb10: Unknown filesystem, if any.
sdb11: Unknown filesystem, if any.
sdb12: ext3 filesystem; gets mounted at "/system".
sdb13: ext3 filesystem; gets mounted at "/data".
sdb14: vfat filesystem; represents the internal sdcard.
I'm trying to find out what needs to be restored in order to perform a clean, reliable downgrade. sdb5 is a must, but not the only one. I've flashed 2.2 and dumped it back right after. The result is an almost downgraded U8800. I say almost because charging the battery while the phone is off shows a different image (the one that comes with 2.3) and I can't power up the phone unless I take the cable out; this means there are still remnants of 2.3 somewhere...
UPDATE: Not being able to power up the phone was to due to the CWM recovery; restoring original recovery.img solved that one.
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?
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