I apologize in advance if this is somewhere in the threads here but I could not find this information. thanks to our team member @stratatak7 for getting me this info. hopefully we can bring some good things to the Moto X section.
Code:
aboot -> /dev/block/mmcblk0p5
abootBackup -> /dev/block/mmcblk0p13
boot -> /dev/block/mmcblk0p33
cache -> /dev/block/mmcblk0p36
cid -> /dev/block/mmcblk0p29
clogo -> /dev/block/mmcblk0p31
customize -> /dev/block/mmcblk0p39
devtree -> /dev/block/mmcblk0p32
dhob -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p25
hob -> /dev/block/mmcblk0p21
kpan -> /dev/block/mmcblk0p35
logo -> /dev/block/mmcblk0p30
logs -> /dev/block/mmcblk0p9
mbl -> /dev/block/mmcblk0p20
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p18
modemst2 -> /dev/block/mmcblk0p19
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p17
padC -> /dev/block/mmcblk0p37
pds -> /dev/block/mmcblk0p28
persist -> /dev/block/mmcblk0p23
recovery -> /dev/block/mmcblk0p34
rpm -> /dev/block/mmcblk0p6
rpmBackup -> /dev/block/mmcblk0p14
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl2Backup -> /dev/block/mmcblk0p11
sbl3 -> /dev/block/mmcblk0p4
sbl3Backup -> /dev/block/mmcblk0p12
sp -> /dev/block/mmcblk0p26
ssd -> /dev/block/mmcblk0p24
system -> /dev/block/mmcblk0p38
tz -> /dev/block/mmcblk0p7
tzBackup -> /dev/block/mmcblk0p15
userdata -> /dev/block/mmcblk0p40
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p16
Oh yeah...let's get this thing started.
Nice to see you around the Moto X forums Mr. V. You still have the GS4?
Sent from my XT1053 using xda app-developers app
oquinones said:
Nice to see you around the Moto X forums Mr. V. You still have the GS4?
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
yep, still have it. gonna be doing work for both devices for a while
Related
Hi there,
I've been trying to find a decent way to recover some photo/video files I unintentially removed from my Nexus 4. I have a rooted phone, but the most obvious (root only) apps I could find didn't solve my problem. I've found a guide here on XDA that I have some faith in, but I have one question about it, before I can even begin the process.
Link to the guide: http://forum.xda-developers.com/showthread.php?t=1994705
Part I don't understand: "*****Based on the number of people having trouble with this step it is now my recommendation that you choose to recover your entire memory block instead of just the data partition. In my phone's case that is mmcblk0. Please discover if yours is different.***** Identify which block/partition you want to recover. For our purpose here we are seeking to recover the userdata partition: /dev/block/mmcblk0p12''
What my question is about: As you can see, the guide is written for the Galaxy Nexus phone, but the topic starter states that it can be used for other phones as well. He's using the following name/number for his Galaxy Nexus: mmcblk0. What kind of number do I need to use for my Nexus 4? Or how can I find it.
Excuse me if this is a noob question, I just can't find the answer anywhere.
Thanks in advance
Bump! If I'm looking for something that doesn't exist, please let me know as well. I have no idea how I should handle this
modem -> /dev/block/mmcblk0p1
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p4
tz -> /dev/block/mmcblk0p5
boot -> /dev/block/mmcblk0p6
recovery -> /dev/block/mmcblk0p7
m9kefs1 -> /dev/block/mmcblk0p8
m9kefs2 -> /dev/block/mmcblk0p9
m9kefs3 -> /dev/block/mmcblk0p10
rpm -> /dev/block/mmcblk0p11
aboot -> /dev/block/mmcblk0p12
sbl2b -> /dev/block/mmcblk0p13
sbl3b -> /dev/block/mmcblk0p14
abootb -> /dev/block/mmcblk0p15
rpmb -> /dev/block/mmcblk0p16
tzb -> /dev/block/mmcblk0p17
metadata -> /dev/block/mmcblk0p18
misc -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p21
cache -> /dev/block/mmcblk0p22
userdata -> /dev/block/mmcblk0p23
DDR -> /dev/block/mmcblk0p24
grow -> /dev/block/mmcblk0p25
Source: http://forum.xda-developers.com/showthread.php?t=1993036
I used that same guide and recovered block 23. Although I was looking for something very specific and it was done after a complete wipe by flashing stock images. Hopefully it yields better results for you but at least you'll know the guide works as intended. PM me if you need help I'll try my best
Sent from my Nexus 4 using xda app-developers app
Here are the partition mount points
Code:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p12
boot -> /dev/block/mmcblk0p32
cache -> /dev/block/mmcblk0p36
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p29
customize -> /dev/block/mmcblk0p35
dhob -> /dev/block/mmcblk0p20
factorytune1 -> /dev/block/mmcblk0p10
factorytune2 -> /dev/block/mmcblk0p34
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p31
logo -> /dev/block/mmcblk0p28
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p30
recovery -> /dev/block/mmcblk0p33
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p37
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p38
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
Thank you so much for this! I am interested in themeing the stock ROM, and I'm using ArchiKitchen to help in the deodexing(last time i tried any themeing, it was on JB and the only way i knew how to theme was on a deodexed ROM). In the process of recreating the ROM, ArchiKitchen asks for the kernel path since it doesn't seem to be specified in the stock system.img. Would the system path be the correct path to use or is there one that I missed? Any help is appreciated!
EDIT:
Upon selecting the system path, ArchiKitchen responded with this:
The final effect is:
=-=-=-=-=-=-=-=-=
package_extract_file("boot.img", "/dev/block/mmcblk0p37");
I guessing that this means i should specify the boot path instead. I won't make a move until i know for sure, though.
Seems like the partition block numbers have changed between 4.4.4/first 5.0 leak and the newest 5.0 OTA. What does this mean? Be VERY careful when flashing stuff using the block number (mmcblk0p37) The partition you are trying to flash might have changed and you could brick your ****. Use by-name instead
Partition Layout in 4.4.4 and first 5.0 Soak test OTA:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p12
boot -> /dev/block/mmcblk0p32
cache -> /dev/block/mmcblk0p36
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p29
customize -> /dev/block/mmcblk0p35
dhob -> /dev/block/mmcblk0p20
factorytune1 -> /dev/block/mmcblk0p10
factorytune2 -> /dev/block/mmcblk0p34
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p31
logo -> /dev/block/mmcblk0p28
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p30
recovery -> /dev/block/mmcblk0p33
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p37
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p38
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
New Partition layout after the .6 OTA
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p12
boot -> /dev/block/mmcblk0p33
cache -> /dev/block/mmcblk0p37
cid -> /dev/block/mmcblk0p26
clogo -> /dev/block/mmcblk0p30
customize -> /dev/block/mmcblk0p36
dhob -> /dev/block/mmcblk0p21
factorytune1 -> /dev/block/mmcblk0p10
factorytune2 -> /dev/block/mmcblk0p35
frp -> /dev/block/mmcblk0p16
fsc -> /dev/block/mmcblk0p23
fsg -> /dev/block/mmcblk0p22
hob -> /dev/block/mmcblk0p20
kpan -> /dev/block/mmcblk0p32
logo -> /dev/block/mmcblk0p29
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p28
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p18
modemst2 -> /dev/block/mmcblk0p19
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p17
pds -> /dev/block/mmcblk0p27
persist -> /dev/block/mmcblk0p31
recovery -> /dev/block/mmcblk0p34
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sp -> /dev/block/mmcblk0p25
ssd -> /dev/block/mmcblk0p24
system -> /dev/block/mmcblk0p38
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p39
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
I have unlocked my Australian xt1572 and booted twrp with the following command:
fastboot boot twrp.img
Then I made a nandroid backup selecting all the options apart from /data
Does this backup my original modem as a part of the backup or is there a specific way to back up my modem from twrp?
I want to make sure that I can revert back to stock (Vodafone) so I can return to original state by restoring the nandroid backup i made and apply the 6.0 ota when its get released down here.
-Ivar
This is something I am trying to find out as well. Anyone able to confirm it?
ivaho said:
I have unlocked my Australian xt1572 and booted twrp with the following command:
fastboot boot twrp.img
Then I made a nandroid backup selecting all the options apart from /data
Does this backup my original modem as a part of the backup or is there a specific way to back up my modem from twrp?
I want to make sure that I can revert back to stock (Vodafone) so I can return to original state by restoring the nandroid backup i made and apply the 6.0 ota when its get released down here.
-Ivar
Click to expand...
Click to collapse
LBSpeller said:
This is something I am trying to find out as well. Anyone able to confirm it?
Click to expand...
Click to collapse
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
For example, here are the partitions of the Pure Edition:
ls -al /dev/block/bootdevice/by-name
DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p5
abootBackup -> /dev/block/mmcblk0p12
bluetooth -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p36
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p45
cid -> /dev/block/mmcblk0p26
clogo -> /dev/block/mmcblk0p32
customize -> /dev/block/mmcblk0p43
dhob -> /dev/block/mmcblk0p23
frp -> /dev/block/mmcblk0p33
fsc -> /dev/block/mmcblk0p25
fsg -> /dev/block/mmcblk0p24
hob -> /dev/block/mmcblk0p22
hyp -> /dev/block/mmcblk0p9
hypBackup -> /dev/block/mmcblk0p15
keystore -> /dev/block/mmcblk0p42
kpan -> /dev/block/mmcblk0p35
limits -> /dev/block/mmcblk0p30
logo -> /dev/block/mmcblk0p31
logs -> /dev/block/mmcblk0p29
logs-charging -> /dev/block/mmcblk0p39
metadata -> /dev/block/mmcblk0p28
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p20
modemst2 -> /dev/block/mmcblk0p21
oem -> /dev/block/mmcblk0p44
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p19
padC -> /dev/block/mmcblk0p40
persist -> /dev/block/mmcblk0p34
pmic -> /dev/block/mmcblk0p2
pmicBackup -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p37
rpm -> /dev/block/mmcblk0p6
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sdi -> /dev/block/mmcblk0p8
sp -> /dev/block/mmcblk0p41
ssd -> /dev/block/mmcblk0p38
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p7
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p48
utags -> /dev/block/mmcblk0p10
utagsBackup -> /dev/block/mmcblk0p16
Click to expand...
Click to collapse
"modem" = /dev/block/mmcblk0p1
"fsg" = /dev/block/mmcblk0p24
"modemst1" = /dev/block/mmcblk0p20
"modemst2" = /dev/block/mmcblk0p21
To back them up in Terminal:
For modem: dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
For modemst1: dd if=/dev/block/mmcblk0p20 of=/sdcard/modemst1
For modemst2: /dev/block/mmcblk0p21 of=/sdcard/modemst2
For fsg: dd if=/dev/block/mmcblk0p1 of=/sdcard/fsg.mbn
Check on your internal storage for those files and save them somewhere.
Spasticdroid said:
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
Click to expand...
Click to collapse
Guess I am out of luck then since I already have installed the indian MM modem :crying:
But luckily the phone works great with this version of mm so at least I dont have a brick
SpasilliumNexus said:
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
For example, here are the partitions of the Pure Edition:
"modem" = /dev/block/mmcblk0p1
"fsg" = /dev/block/mmcblk0p24
"modemst1" = /dev/block/mmcblk0p20
"modemst2" = /dev/block/mmcblk0p21
To back them up in Terminal:
For modem: dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
For modemst1: dd if=/dev/block/mmcblk0p20 of=/sdcard/modemst1
For modemst2: /dev/block/mmcblk0p21 of=/sdcard/modemst2
For fsg: dd if=/dev/block/mmcblk0p1 of=/sdcard/fsg.mbn
Check on your internal storage for those files and save them somewhere.
Click to expand...
Click to collapse
How can I restore modem which is backed up in TWRP?
Dear Friends,
I need help to find where is the IMEI data of this phone?Is it saved in hardware or in a partition that I can not find it??
This is partition table of this phone:
DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p5
abootBackup -> /dev/block/mmcblk0p12
bluetooth -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p36
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p45
cid -> /dev/block/mmcblk0p26
clogo -> /dev/block/mmcblk0p32
customize -> /dev/block/mmcblk0p43
dhob -> /dev/block/mmcblk0p23
frp -> /dev/block/mmcblk0p33
fsc -> /dev/block/mmcblk0p25
fsg -> /dev/block/mmcblk0p24
hob -> /dev/block/mmcblk0p22
hyp -> /dev/block/mmcblk0p9
hypBackup -> /dev/block/mmcblk0p15
keystore -> /dev/block/mmcblk0p42
kpan -> /dev/block/mmcblk0p35
limits -> /dev/block/mmcblk0p30
logo -> /dev/block/mmcblk0p31
logs -> /dev/block/mmcblk0p29
logs-charging -> /dev/block/mmcblk0p39
metadata -> /dev/block/mmcblk0p28
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p20
modemst2 -> /dev/block/mmcblk0p21
oem -> /dev/block/mmcblk0p44
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p19
padC -> /dev/block/mmcblk0p40
persist -> /dev/block/mmcblk0p34
pmic -> /dev/block/mmcblk0p2
pmicBackup -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p37
rpm -> /dev/block/mmcblk0p6
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sdi -> /dev/block/mmcblk0p8
sp -> /dev/block/mmcblk0p41
ssd -> /dev/block/mmcblk0p38
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p7
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p48
utags -> /dev/block/mmcblk0p10
utagsBackup -> /dev/block/mmcblk0p16
It's mmcblk0p20 and mmcblk0p21 according to a twrp backup.
No, they are not there.I checked I think IMEI saved in hardware of this phone because not possible to change still with efspro program,the phone connected but get error in restore but backing up efs is ok