[Q] ] Accidentally deleted photos! Need G2 /dev/block userdata partition to recover. - G2 Q&A, Help & Troubleshooting

Hey Guys.
Help! I Accidentally deleted my vacation photos :crying: I am planning to use the method described here. For that I need to know the /dev/block userdata partition. Can any of the awesome devs help me?
Any other method too is welcome.
Any help will be massively appreciated :good:
Thanks.

androidmaniac123 said:
Hey Guys.
Help! I Accidentally deleted my vacation photos :crying: I am planning to use the method described here. For that I need to know the /dev/block userdata partition. Can any of the awesome devs help me?
Any other method too is welcome.
Any help will be massively appreciated :good:
Thanks.
Click to expand...
Click to collapse
Are you by chance on Google + or Dropbox? Did you maybe have photo sync turned on at any time?
Sent from my LG-D800 using Tapatalk

Jank4AU said:
Are you by chance on Google + or Dropbox? Did you maybe have photo sync turned on at any time?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
During the vacation, I had turned off the sync to save battery :crying:

androidmaniac123 said:
During the vacation, I had turned off the sync to save battery :crying:
Click to expand...
Click to collapse
Ouch. I wish I could help with your partition question but I'm not a developer. Hopefully someone here can help you soon. Good luck, dude.
Sent from my LG-D800 using Tapatalk

What comes first to my mind is flashing the dualboot/fastboot bootloader and using fastboot to pull the data partition. However I'm not really sure if this will work as it's so long since I last used fastboot.
Sent from my LG D802

Jank4AU said:
Ouch. I wish I could help with your partition question but I'm not a developer. Hopefully someone here can help you soon. Good luck, dude.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Thank you

?
Is here any information you need?
http://forum.xda-developers.com/showpost.php?p=50790181&postcount=49

androidmaniac123 said:
During the vacation, I had turned off the sync to save battery :crying:
Click to expand...
Click to collapse
Question. So your next vacation, what are you going with, sync Dropbox or battery life?
Just had to do that.
On a serious note, I hope you are able to retrieve your vacation photos.

Kickoff said:
Is here any information you need?
http://forum.xda-developers.com/showpost.php?p=50790181&postcount=49
Click to expand...
Click to collapse
Hey Kickoff,
Is /dev/block/mmcblk0 the entire internal memory or just the user data partition?
Sorry I am not that familiar with partition blocks. Can you provide more details?
I am running a rooted Malladaus 2.0 4.4.2 Kitkat ROM BTW.
Much appreciated bro :good:

leroybrute said:
Question. So your next vacation, what are you going with, sync Dropbox or battery life?
Just had to do that.
On a serious note, I hope you are able to retrieve your vacation photos.
Click to expand...
Click to collapse
Thanks mate...My next vacation will be with a DSLR!:good: And hopefully I dont delete the contents of the SD Card like a fool

androidmaniac123 said:
Hey Kickoff,
Is /dev/block/mmcblk0 the entire internal memory or just the user data partition?
Sorry I am not that familiar with partition blocks. Can you provide more details?
I am running a rooted Malladaus 2.0 4.4.2 Kitkat ROM BTW.
Much appreciated bro :good:
Click to expand...
Click to collapse
The entire. userdata is p35, but you can check it yourself.
You could try this as well: http://www.recovery-android.com/android-data-recovery.html

Kickoff said:
The entire. userdata is p35, but you can check it yourself.
You could try this as well: http://www.recovery-android.com/android-data-recovery.html
Click to expand...
Click to collapse
Hey Kickoff, Sorry for not getting back to u immediately. After a few attempts I was able to make partition images. I tried mmcblk0p38 (entire image), mmcblk0p34 (user data) but none of them contained the DCIM photos. I was able to recover many whatsapp images and mp3 files etc but I couldnt find the DCIM pictures. Any idea which partition contains the DCIM photos?

androidmaniac123 said:
Hey Kickoff, Sorry for not getting back to u immediately. After a few attempts I was able to make partition images. I tried mmcblk0p38 (entire image), mmcblk0p34 (user data) but none of them contained the DCIM photos. I was able to recover many whatsapp images and mp3 files etc but I couldnt find the DCIM pictures. Any idea which partition contains the DCIM photos?
Click to expand...
Click to collapse
Why not to try the software I linked? It worked well for me.
Have you installed parted, changed the permission and ran the following commands?
Code:
adb shell
su
cd /system
parted /dev/block/mmcblk0
This is is the way how you did identify the partitions? Your number seem to be totally different. Try this as well.

Kickoff said:
Why not to try the software I linked? It worked well for me.
Have you installed parted, changed the permission and ran the following commands?
Code:
adb shell
su
cd /system
parted /dev/block/mmcblk0
This is is the way how you did identify the partitions? Your number seem to be totally different. Try this as well.
Click to expand...
Click to collapse
Thanks Kickoff.
I used the find command:
find /dev/block/platform/ -name 'mmc*' -exec fdisk -l {} \;
to identify the partitions. According to this command, mmcblk0p38 had the user data. But when I tried to recover from p38, I am able to recover only the thumbnail sized pics of the ones i lost. Any comments?
Output from the above command:
[email protected]:/ # find /dev/block/platform/ -name 'mmcblk0p3*' -exec fdisk -l {} \;
find /dev/block/platform/ -name 'mmcblk0p3*' -exec fdisk -l {} \;
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p39: 12 MB, 12566016 bytes
4 heads, 16 sectors/track, 383 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p39 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p38: 26.3 GB, 26357006336 bytes
4 heads, 16 sectors/track, 804352 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p38 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p37: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p37 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p36: 83 MB, 83886080 bytes
4 heads, 16 sectors/track, 2560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p36 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p35: 838 MB, 838860800 bytes
4 heads, 16 sectors/track, 25600 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p35 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p34: 3489 MB, 3489660928 bytes
4 heads, 16 sectors/track, 106496 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p34 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p33: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p33 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p32: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p32 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p31: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p31 doesn't contain a valid partition
table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p30: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p30 doesn't contain a valid partition

With parted I see as follows
1|[email protected]:/system # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 032G96 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 31.2GB 27.1GB ext4 userdata
36 31.2GB 31.3GB 62.9MB grow
(parted)
Tapatalk-kal küldve az én LG-D802-el

Recovery software it worked for me on my og g but i forget what it was, it was cheap enough imo
Sent from my LG-D800 using xda app-developers app

Kickoff said:
With parted I see as follows
1|[email protected]:/system # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 032G96 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 31.2GB 27.1GB ext4 userdata
36 31.2GB 31.3GB 62.9MB grow
(parted)
Tapatalk-kal küldve az én LG-D802-el
Click to expand...
Click to collapse
But you would think that the partition with the biggest size is the user data partition correct?? Also the DCIM pictures would be stored in the user data partition correct?
Thanks Kickoff.

Think so. Emulated sdcard must be on that partition as well.
Tapatalk-kal küldve az én LG-D802-el

Related

[DEV][R&D] FW & Partition Tables (Here!)

I'm working on a project doing Firmware/Bootloader analysis and documentation.
This will eventually be crucially important in providing service, repair and
unbricking of these device. And if you think that these will not soft-brick,
just remember that the OS have "Windows" in it's name...
However, this project requires detailed knowledge of the following two components:
Bootloader & Firmware files
Partition Table
To make things more simple for this project, I have chosen to only focus on devices using the Qualcomm
Snapdragon S4 Plus/Pro processors, these are also known as the MSM8960, MSM8960T and MSM8930.
So if you have any of the devices shown in the list below, please try to extract and post these details,
when and if they become available. (I recommend using Sendspace to upload large files.)
Code:
[SIZE=2]HTC Windows Phone 8X LTE ADR6990 Verizon
HTC Windows Phone 8X LTE
Nokia Lumia 820 (Nokia Arrow)
Nokia Lumia 820.2 (Nokia Arrow)
Nokia Lumia 822 (Nokia Atlas) Verizon
Nokia Lumia 920 (Nokia Phi)
Nokia Lumia 920.2 (Nokia Phi)
Samsung GT-i8750 Ativ S 16GB (Samsung Odyssey)
Samsung GT-i8750 Ativ S 32GB (Samsung Odyssey)[/SIZE]
[Obtained from the PDAdb web site.]
This list is in no way exhaustive, and it may be very likely that you have another device or still using
Windows Phone 7 (?) with that same processor. That would also be interesting. Another thing that may
be very useful, is documentation related to the Windows Phone build structure.
The results of this project will be published here and will benefit the development community
in several different ways.
Please do not post any general unrelated questions here, they will be removed.
And I will not answer to any support related PM's.
Thanks in advance.
< Here Be Snap ! Dragons >
Good start .. E.V.A have u trued to contact Cotulla on htc-linux or DFT team. They might have something that might interest you . I'll post once i grab my hands on them.
Sent from my GT-I9300 using xda premium
If someone has a working Windows Phone 8, and if at all possible, please follow these instructions to dump the partition tables. As you're on a windows phone, you may need to connect it to a linux based PC, to get these...
Hi, I am in possession of an HTC 8X engineering unit (see here http://forum.xda-developers.com/showthread.php?t=1966327). How can I help? Someone on my thread suggested that I should post here.
Hi! Yes, you could be of great help, if you could provide the partition tables from that device. I know it's politically incorrect to ask you to use a linux tool for doing this, but that is (probably) the only way it will be useful, as you cannot trust native windows partition information...
The way to do it, is by connecting your WP to a linux computer or possibly by using some linux distribution under a virtual machine (VirtualBox, VMware etc.) Then follow the instructions found here.
Thanks in advance.
8X Partition table
Hello. Also have a 8X engineering unit. This is the Partition Info:
Code:
# fdisk -l /dev/sdb
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 15.6 GB, 15634268160 bytes
1 heads, 32 sectors/track, 954240 cylinders
Units = cylinders of 32 * 512 = 16384 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 444417 7110656 ee GPT
Partition 1 does not end on cylinder boundary.
# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: Qualcomm MMC Storage (scsi)
Disk /dev/sdb: 15,6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 62,9MB 61,9MB pg1fs
2 62,9MB 66,1MB 3146kB MODEM_FSG
3 66,1MB 67,1MB 1049kB board_info
4 67,1MB 75,5MB 8389kB DPP
5 75,5MB 77,6MB 2097kB SSD
6 77,6MB 78,6MB 1049kB SBL1
7 78,6MB 79,7MB 1049kB SBL2
8 79,7MB 81,8MB 2097kB SBL3
9 81,8MB 83,9MB 2097kB UEFI
10 83,9MB 84,9MB 1049kB RPM
11 84,9MB 86,0MB 1049kB TZ
12 86,0MB 87,0MB 1049kB WINSECAPP
13 87,0MB 88,1MB 1049kB BACKUP_SBL1
14 88,1MB 89,1MB 1049kB BACKUP_SBL2
15 89,1MB 91,2MB 2097kB BACKUP_SBL3
16 91,2MB 93,3MB 2097kB BACKUP_UEFI
17 93,3MB 94,4MB 1049kB BACKUP_RPM
18 94,4MB 95,4MB 1049kB BACKUP_TZ
19 95,4MB 96,5MB 1049kB BACKUP_WINSECAPP
20 96,5MB 138MB 41,9MB RADIO
21 138MB 139MB 262kB UEFI_BS_NV
22 139MB 140MB 262kB UEFI_NV
23 141MB 149MB 8389kB PLAT
24 149MB 192MB 43,0MB fat16 EFIESP
25 192MB 193MB 1049kB pg2fs
26 193MB 194MB 1049kB RFG_0
27 194MB 195MB 1049kB RFG_1
28 195MB 196MB 1049kB RFG_2
29 196MB 197MB 1049kB RFG_3
30 197MB 198MB 1049kB RFG_4
31 198MB 199MB 1049kB RFG_5
32 199MB 200MB 1049kB RFG_6
33 200MB 201MB 1049kB RFG_7
34 201MB 202MB 1049kB RFG_8
35 202MB 207MB 4194kB MODEM_FS1
36 207MB 211MB 4194kB MODEM_FS2
37 211MB 211MB 262kB UEFI_RT_NV
38 212MB 212MB 131kB UEFI_RT_NV_RPMB
39 213MB 214MB 1049kB MFG
40 214MB 215MB 1049kB MISC
41 215MB 228MB 13,4MB fat16 MMOS
42 235MB 2698MB 2463MB ntfs MainOS
43 2698MB 5114MB 2416MB fat32 CrashDump
44 5117MB 15,6GB 10,5GB ntfs Data
(parted) q
# gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 30535680 sectors, 14.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): AE420040-13DD-41F2-AE7F-0DC35854C8D7
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 2048-sector boundaries
Total free space is 27687 sectors (13.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 122879 59.0 MiB FFFF pg1fs
2 122880 129023 3.0 MiB FFFF MODEM_FSG
3 129024 131071 1024.0 KiB FFFF board_info
4 131072 147455 8.0 MiB 0700 DPP
5 147456 151551 2.0 MiB FFFF SSD
6 151552 153599 1024.0 KiB FFFF SBL1
7 153600 155647 1024.0 KiB FFFF SBL2
8 155648 159743 2.0 MiB FFFF SBL3
9 159744 163839 2.0 MiB FFFF UEFI
10 163840 165887 1024.0 KiB FFFF RPM
11 165888 167935 1024.0 KiB FFFF TZ
12 167936 169983 1024.0 KiB FFFF WINSECAPP
13 169984 172031 1024.0 KiB FFFF BACKUP_SBL1
14 172032 174079 1024.0 KiB FFFF BACKUP_SBL2
15 174080 178175 2.0 MiB FFFF BACKUP_SBL3
16 178176 182271 2.0 MiB FFFF BACKUP_UEFI
17 182272 184319 1024.0 KiB FFFF BACKUP_RPM
18 184320 186367 1024.0 KiB FFFF BACKUP_TZ
19 186368 188415 1024.0 KiB FFFF BACKUP_WINSECAPP
20 188416 270335 40.0 MiB FFFF RADIO
21 270336 270847 256.0 KiB FFFF UEFI_BS_NV
22 272384 272895 256.0 KiB FFFF UEFI_NV
23 274432 290815 8.0 MiB FFFF PLAT
24 290816 374783 41.0 MiB 0700 EFIESP
25 374784 376831 1024.0 KiB FFFF pg2fs
26 376832 378879 1024.0 KiB FFFF RFG_0
27 378880 380927 1024.0 KiB FFFF RFG_1
28 380928 382975 1024.0 KiB FFFF RFG_2
29 382976 385023 1024.0 KiB FFFF RFG_3
30 385024 387071 1024.0 KiB FFFF RFG_4
31 387072 389119 1024.0 KiB FFFF RFG_5
32 389120 391167 1024.0 KiB FFFF RFG_6
33 391168 393215 1024.0 KiB FFFF RFG_7
34 393216 395263 1024.0 KiB FFFF RFG_8
35 395264 403455 4.0 MiB FFFF MODEM_FS1
36 403456 411647 4.0 MiB FFFF MODEM_FS2
37 411648 412159 256.0 KiB FFFF UEFI_RT_NV
38 413696 413951 128.0 KiB FFFF UEFI_RT_NV_RPMB
39 415744 417791 1024.0 KiB FFFF MFG
40 417792 419839 1024.0 KiB FFFF MISC
41 419840 446031 12.8 MiB 0700 MMOS
42 458752 5269094 2.3 GiB 0700 MainOS
43 5269504 9988095 2.2 GiB 0700 CrashDump
44 9994240 30535646 9.8 GiB 0700 Data
#
^^ Very nice!
Also for everybody's information. I was looking into one of the FFU files of the WP7 (?) Nokia Lumina 800 (RM-801), and it appears that hidden partitions (or mounts) are set in a registry key...
Code:
[SIZE=2][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MMC\IMGFS]
"MountHidden"=dword:1
"MountAsROM"=dword:1
"XIP"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SDMemory\IMGFS]
"MountHidden"=dword:1
"MountAsROM"=dword:1
"XIP"=dword:0
[HKEY_LOCAL_MACHINE\Drivers\BlockDevice\UniBlk]
"InternalStoreProfile"="MMC"
"InternalPartitionType"=dword:4[/SIZE]
and that the write protection is set by these registry items:
Code:
[SIZE=2][HKEY_LOCAL_MACHINE\System\StorageManager\WMPART\WriteProtectRegions\Region1]
"StartSector"=dword:0
"SectorCount"=dword:60000
[HKEY_LOCAL_MACHINE\System\StorageManager\WMPART]
"EnableHardwareWriteProtection"=dword:1
"PadAlignment"=dword:10000[/SIZE]
of course I could be wrong, since there are loads of similar items in there.
But it will perhaps help someone finding out where to look.

Is there a way to create a NAND partition?

As far as I know, there is:
/boot
/bootloader
/userdata
/system
/cache
/recovery
/radio
Is there a way for me to create a new partition on the NAND to which I can write to and from?
Sinfamy said:
As far as I know, there is:
/boot
/bootloader
/userdata
/system
/cache
/recovery
/radio
Is there a way for me to create a new partition on the NAND to which I can write to and from?
Click to expand...
Click to collapse
There are actually more partitions that you thought.
Code:
# parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.2MB 524kB sbl1
3 68.2MB 68.7MB 524kB sbl2
4 68.7MB 70.8MB 2097kB sbl3
5 70.8MB 71.3MB 524kB tz
6 71.3MB 94.4MB 23.1MB boot
7 94.4MB 117MB 23.1MB recovery
8 117MB 118MB 799kB m9kefs1
9 118MB 119MB 799kB m9kefs2
10 119MB 120MB 799kB m9kefs3
11 120MB 121MB 524kB rpm
12 121MB 121MB 524kB aboot
13 121MB 122MB 524kB sbl2b
14 122MB 124MB 2097kB sbl3b
15 124MB 124MB 524kB abootb
16 124MB 125MB 524kB rpmb
17 125MB 125MB 524kB tzb
18 125MB 126MB 524kB metadata
19 126MB 143MB 16.8MB misc
20 143MB 159MB 16.8MB ext4 persist
21 159MB 1040MB 881MB ext4 system
22 1040MB 1627MB 587MB ext4 cache
23 1627MB 15.8GB 14.1GB ext4 userdata
24 15.8GB 15.8GB 524kB DDR
25 15.8GB 15.8GB 507kB grow

[Q] Have 16Gb instead of 32

Hey,
My phone display 16Gb instead of 32Gb !
I had restored my phone multiple times lately because of some things I shouldn't do..
I've a LG G2 D802, get back to stock rom (KOR) rooted but no recovery as I have "adbd cannot run as root in production builds" issue.
So if anyone know how to go back to normal or just install a recovery in order to go under a non stock rom, i'd be glad to follow his advice.
By the way when I go to hardware information on Android I see 32Gb but anywhere else even on PC i see 16Gb (10 actually).
You may want to have a look here http://forum.xda-developers.com/showthread.php?t=2432476 sounds like you have to install a kdz from a country that uses 32gb G2. I had a similar issue when restoring a stock rom on my G pro once, some kdz files are for 16gb variants.
PallyBud said:
You may want to have a look here http://forum.xda-developers.com/showthread.php?t=2432476 sounds like you have to install a kdz from a country that uses 32gb G2. I had a similar issue when restoring a stock rom on my G pro once, some kdz files are for 16gb variants.
Click to expand...
Click to collapse
Ok, thank you! I'll give it a shot tomorow, internet is too slow here ...
Will say if it worked tomorow! Thanks again!
shark_max said:
Ok, thank you! I'll give it a shot tomorow, internet is too slow here ...
Will say if it worked tomorow! Thanks again!
Click to expand...
Click to collapse
I do not think it will help you might have a partition problem like many of us have had. Try this http://forum.xda-developers.com/showpost.php?p=50790181&postcount=49
K,
Kickoff said:
I do not think it will help you might have a partition problem like many of us have had. Try this http://forum.xda-developers.com/showpost.php?p=50790181&postcount=49
K,
Click to expand...
Click to collapse
Hey!
I was actually trying it on my own as I find it on another forum but the output is different than yours :
Code:
[email protected]:/system/bin # ./parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: MMC 032GE4 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 15.7GB 11.6GB ext4 userdata
36 15.7GB 15.8GB 37.7MB grow
Edit : ok, I will try to be a better student and try to actually read your post.. I will send the result later..
Edit2 : Thanks a lot, it worked perfectly!

Working on unbricking hard bricked Moto E

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

How to install a new rom with bootloader loocked?

Hello I have a machine Redmi2 that does not boot, only boots with fastboot when I pressed the power off button ans Vol - button
I can execute fastboot commands.
For example:
fastboot devices
Click to expand...
Click to collapse
967354587d12 fastboot
Click to expand...
Click to collapse
fastboot oem device-info
Click to expand...
Click to collapse
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
I could dowloaded various rom (official from xiaomi and not official like aosp-caf_wt88047_64-21-05-2017-eng.pirej.zip or xiaomi-miui-hellas-5.1_wt88047_V8_XTRVbeta2_7.2.24.zip) but I can install a new system in this machine.
First I try to unlock the bootloader with official method from Xiaomi but the result is error.
Now I try to boot with twrp and this is works.
To boot with twrp I cam execute this with fastboot
fastboot flash recovery twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'recovery' (11426 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.184s]
finished. total time: 0.544s
Click to expand...
Click to collapse
fastboot flash boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'boot' (11426 KB)...
OKAY [ 0.361s]
writing 'boot'...
OKAY [ 0.132s]
finished. total time: 0.493s
Click to expand...
Click to collapse
And with this comand boots the machine with twrp
fastboot boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
When machine boots I have access to external card from my PC and I can put the rom to try to install.
When try to clean the partitions I can not do it:
This is the errors
Error al desmontar '/system' (invalid argument)
Error al desmontar '/data' (invalid argument)
Error al desmontar '/cache' (invalid argument)
Incapaz de montar almacenamiento
Click to expand...
Click to collapse
When I try to install RR-N-v5.8.3-20170516-wt88047-OFFICIAL.zip for example I can not install this rom.
Do you know if it is possible install a rom with bootloader locked?
Doy you know if it is possible unlocked the bootloader if xiaomi unlocker does not works?
Any ideas to install a rom in this machine?
Best regards.
i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?
AKHILR4J said:
i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?
Click to expand...
Click to collapse
Thanks for your help,
I have downloaded the lastest twrp img from redmi 2, and I have the same problems.
Machine boots with twrp but I can not write in the internal partitions and I can not install a rom.
I think that I need unlock the bootloader to can to modify the android partitions but I do not know to do it.
try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS
Liquid2 said:
try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS
Click to expand...
Click to collapse
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.
Hello again, I have tried to mount /system with a terminal in TWRP with this command
Code:
# Montamos la carpeta /system como lectura(r) y escritura(w)
mount -o remount,rw /system
but the problem is my /proc/mounts file
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=967420k,nr_inodes=153983,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=967420k,nr_inodes=153983 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p25 /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /firmware vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
Do you know how can I can change this file to include the /system partition to mount read/write and I can install a rom os.
Regards,
jriosa said:
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.
Click to expand...
Click to collapse
have u tried another twrp?? make sure it for your device
Liquid2 said:
have u tried another twrp?? make sure it for your device
Click to expand...
Click to collapse
Thanks for your help, I have tried different versions from twrp with the same result.
Regards, Julio.
sori, cant help much, maybe
i myself in very newbie
how about if you flash fresh with flashboot rom using miflash, see if it can boot into official miui first
then you can try install twrp again and flash custom rom
have you tried twrp
Hello Now I access to android with adb.
When I boot the android with TWRP, I can access with my PC using adb.
I execute this.
adb root
Click to expand...
Click to collapse
adb shell
Click to expand...
Click to collapse
This is the partitions on my machine
~ # cat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1048576 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 13557743 mmcblk0p30
179 32 4096 mmcblk0rpmb
179 64 30375936 mmcblk1
179 65 30371840 mmcblk1p1
Click to expand...
Click to collapse
~ # cd /dev
/dev # find -inme mmcblk0
find: unrecognized: -inme
Segmentation fault
/dev # find -iname mmcblk0
./block/mmcblk0
./block/platform/soc.0/7824900.sdhci/mmcblk0
Click to expand...
Click to collapse
I have added parted to managed partitions in my machine
To see parttions in my disk
~ # /sbin/parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Click to expand...
Click to collapse
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
Click to expand...
Click to collapse
To see my partitions
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 32.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 13.4G 15.6G 46% /external_sd
Click to expand...
Click to collapse
I think that I can not install a new rom (offcial or unofficial) because the system I can not access to partitions /system for example and I think that system partitions is mmcblk0p23.
Do you know how I can modify my partitions to see in df -h and launch a new rom with twrp?
Thanks a lot,
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
jriosa said:
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
Click to expand...
Click to collapse
Have you unmounted the data partition in twrp before executing the rm command?
SidOfficial said:
Have you unmounted the data partition in twrp before executing the rm command?
Click to expand...
Click to collapse
This is my commands and my point mounts are
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
Click to expand...
Click to collapse
I see a new error
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
Click to expand...
Click to collapse
maybe the first partition I think is OK
~ # parted /dev/block/mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 67.1MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 67.1MB 67.1MB fat16
Click to expand...
Click to collapse
adb shell
~ # cp /external_sd/parted /sbin/parted
~ # chmod +x /sbin/parted
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit MiB
unit MiB
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) rm 30
rm 30
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) q
q
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
(parted)
Click to expand...
Click to collapse
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?
jriosa said:
This is my commands and my point mounts are
I see a new error
maybe the first partition I think is OK
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?
Click to expand...
Click to collapse
Yes, you can recreate all the partitions and can even resize the system and data partitions. Head over to this link https://forum.xda-developers.com/redmi-2/how-to/wt88047-redmi-2-resize-partition-t3612933

Categories

Resources