Dumping stock ROM and lost in the process. - OnePlus 2 Q&A, Help & Troubleshooting

Hello, everyone.
Since the ROM version on my OPT is not available for download (I got a phone with Oxygen 2.0.3), I decided to make a flashable image. This is the first time I do this, and I am kind of lost.
From this guide, I gathered that I need to find boot, kernel, system and misc partitions. Here are the partitions on OPT:
Code:
ls -al /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-24 09:32 DDR -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-24 09:32 DRIVER -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-24 09:32 LOGO -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-24 09:32 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-24 09:32 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-24 09:32 apdp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-24 09:32 bluetooth -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-24 09:32 boot -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-24 09:32 cache -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-24 09:32 config -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-24 09:32 devinfo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-24 09:32 dpo -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-24 09:32 fsc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-24 09:32 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-24 09:32 hyp -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-24 09:32 hypbak -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-24 09:32 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-24 09:32 limits -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-24 09:32 misc -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-24 09:32 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-24 09:32 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-24 09:32 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-24 09:32 msadp -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-24 09:32 oem_dycnvbk -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-24 09:32 oem_stanvbk -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-24 09:32 param -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-24 09:32 persist -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-24 09:32 pmic -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-24 09:32 pmicbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-24 09:32 recovery -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-24 09:32 reserve1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-24 09:32 reserve2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-24 09:32 rpm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-24 09:32 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-24 09:32 sbl1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-24 09:32 sbl1bak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-24 09:32 sdi -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-24 09:32 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-24 09:32 ssd -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-24 09:32 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-24 09:32 tz -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-24 09:32 tzbak -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-24 09:32 userdata -> /dev/block/mmcblk0p43
I see boot, system, and misc, but no kernel (there is kernel in the file system, though, I imagine it could be part of system), and I also see a bunch of strange names and a bunch of important-looking names.
Something tells me that Driver, DDR, Logo are somehow important and then there are modem and stuff, and tz looks important enough to back it up. Does anyone know what this all means? I saw links to stock Oxygen ROMs, so I imagine someone knows how to dump it.

Hey,
It's cool that you are trying to do this. Maybe try & send this guy a dm: Naman Bhalla
He's posted several other OxygenOS images, so I'm positive he can guide you in the process.

One interesting thing I noticed:
One OPT lets me connect ADB while it's in recovery rom. That is also automatically root if you do adb shell.
Another OPT does not let me connect with ADB at all. It also does not let me pick a proper ADB driver and insits on using a nexus driver instead. Very strange.

Related

[DEV] thread on LG G Pad 7.0/8.0/10.1

Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1
I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change
Help Wanted:
If you own a LG G Pad 8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs
Dump partition list/info : instructions
Dump /system/build.prop
Possibly need root for stuff below
Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
​
LG G Pad 7.0
Model Name: v400
Released with KitKat 4.4.?
Kernel Source:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v400
Root:
Towelroot works
Loki no longer works, can't bypass the locked bootloader to boot custom ROMs/kernels/recovery
Mode Name: v410 (LTE AT&T version)
Root: purpledrake works​
LG G Pad 8.0
Unknown device.... not released yet?​
LG G Pad 10.1
Model Name: v700, v700n (korean model?)
Released with KitKat 4.4.?
Kernel Source:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v700
Root:
Towelroot works​
paperWastage said:
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1
I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change
Help Wanted:
If you own a LG G Pad 7.0/8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs
Dump partition list/info : instructions
Dump /system/build.prop
Possibly need root for stuff below
Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
​
Click to expand...
Click to collapse
Hi, I own a G pad 7.0. It seems that I am the only one in the world I'm gonna try to help a little:
1. Dump partition:
-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34
- Dump build.prop, boot, aboot and recovery:
http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html
I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
Hammerhand.17 said:
Hi, I own a G pad 7.0. It seems that I am the only one in the world I'm gonna try to help a little:
1. Dump partition:
-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34
- Dump build.prop, boot, aboot and recovery:
http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html
I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
Click to expand...
Click to collapse
thanks for this.
@icedmayhem also provided similar files over PM, forgot to post updates here...
anyways, it looks like this device has the patched aboot source code.
loki won't work anymore (loki provides a way for us to bypass the locked bootloader to load non-stock recovery/kernels. This means there isn't an easy way to boot a custom recovery(TWRP) or custom ROM.
Can you check if you can unlock the bootloader? Don't know if LG provides a process to do this easily (for GPE / non-GPE devices)
strings aboot.img | fgrep overlap
The erase group overlaps the max requested for erase
kernel/ramdisk addresses overlap with aboot addresses.
Device tree addresses overlap with aboot addresses.
Boot image buffer address overlaps with aboot addresses.
Signature read buffer address overlaps with aboot addresses.
Click to expand...
Click to collapse
I wish I now how to do it, but I have no idea of how to do this
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
idelgado782 said:
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
Click to expand...
Click to collapse
Link? Or just any of them?
Thxfor the info looking for it now.
Impala126 said:
Link? Or just any of them?
Thxfor the info looking for it now.
Click to expand...
Click to collapse
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.
http://forum.xda-developers.com/showthread.php?p=54254055
No matter what, I can never stay away from android for long.
idelgado782 said:
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.
http://forum.xda-developers.com/showthread.php?p=54254055
No matter what, I can never stay away from android for long.
Click to expand...
Click to collapse
Yup worked like a champ. Turned on air plane mode, then usb debugging and then ptp. But I had to go to a term win on win7 and run bat file from there. wouldn't run with admin rights from windows explore.
idelgado782 said:
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
Click to expand...
Click to collapse
for your G Pad 7.0 AT&T LTE version, mind posting the same items that Hammerhand.17 provided (for the G Pad 7.0)?
more info the better, just easier for the next developer to try to help out
paperWastage said:
LG G Pad 7.0
Model Name: v400
Released with KitKat 4.4.?
Root:
Towelroot works​
Click to expand...
Click to collapse
It works also with a normal V400? I mean with NO at&t version.
(the site is towelroot.com, right?)
Yes, I have root in my normal V400 with no problem.
Hammerhand.17 said:
Yes, I have root in my normal V400 with no problem.
Click to expand...
Click to collapse
Thank you
Hammerhand.17 said:
Yes, I have root in my normal V400 with no problem.
Click to expand...
Click to collapse
One more question, it will work for sure on 4.4.2?
Has anyone tried or been successful pulling a factory image file for the LG V410 which is the AT&T G Pad 7.0? I tried the other day but there was not an image on their servers at that time
Giammysz said:
One more question, it will work for sure on 4.4.2?
Click to expand...
Click to collapse
Yes, 4.4.2 is the version of my tablet.
Giammysz said:
One more question, it will work for sure on 4.4.2?
Click to expand...
Click to collapse
Yes! Even if you have already did the OTA incremental update ..... You will need to install a SU manager though like Super SU etc after rooting with Towel root...
Hammerhand.17 said:
Yes, 4.4.2 is the version of my tablet.
Click to expand...
Click to collapse
Anthonol said:
Yes! Even if you have already did the OTA incremental update ..... You will need to install a SU manager though like Super SU etc after rooting with Towel root...
Click to expand...
Click to collapse
Thank you all
I successfully rooted my tab, it's really simple with towelroot! Install, tap and ready!

How to backup/change boot image?

Hi,
Do you know how to backup boot image?
I read that its in param partition but when I open it was nothing inside
I found the param by this:
ls -l /dev/block/platform/msm_sdcc.1/by-name
Code:
lrwxrwxrwx root root 2014-01-11 04:52 aboot -> /dev/block/mmcbl
k0p6
lrwxrwxrwx root root 2014-01-11 04:52 apnhlos -> /dev/block/mmc
blk0p1
lrwxrwxrwx root root 2014-01-11 04:52 backup -> /dev/block/mmcb
lk0p17
lrwxrwxrwx root root 2014-01-11 04:52 boot -> /dev/block/mmcblk
0p14
lrwxrwxrwx root root 2014-01-11 04:52 cache -> /dev/block/mmcbl
k0p24
lrwxrwxrwx root root 2014-01-11 04:52 dbi -> /dev/block/mmcblk0
p4
lrwxrwxrwx root root 2014-01-11 04:52 ddr -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 2014-01-11 04:52 efs -> /dev/block/mmcblk0
p11
lrwxrwxrwx root root 2014-01-11 04:52 fota -> /dev/block/mmcblk
0p16
lrwxrwxrwx root root 2014-01-11 04:52 fsc -> /dev/block/mmcblk0
p19
lrwxrwxrwx root root 2014-01-11 04:52 fsg -> /dev/block/mmcblk0
p18
lrwxrwxrwx root root 2014-01-11 04:52 hidden -> /dev/block/mmcb
lk0p25
lrwxrwxrwx root root 2014-01-11 04:52 modem -> /dev/block/mmcbl
k0p2
lrwxrwxrwx root root 2014-01-11 04:52 modemst1 -> /dev/block/mm
cblk0p12
lrwxrwxrwx root root 2014-01-11 04:52 modemst2 -> /dev/block/mm
cblk0p13
lrwxrwxrwx root root 2014-01-11 04:52 pad -> /dev/block/mmcblk0
p9
lrwxrwxrwx root root 2014-01-11 04:52 param -> /dev/block/mmcbl
k0p10
lrwxrwxrwx root root 2014-01-11 04:52 persdata -> /dev/block/mm
cblk0p22
lrwxrwxrwx root root 2014-01-11 04:52 persist -> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 2014-01-11 04:52 recovery -> /dev/block/mm
cblk0p15
lrwxrwxrwx root root 2014-01-11 04:52 rpm -> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 2014-01-11 04:52 sbl1 -> /dev/block/mmcblk
0p3
lrwxrwxrwx root root 2014-01-11 04:52 ssd -> /dev/block/mmcblk0
p20
lrwxrwxrwx root root 2014-01-11 04:52 system -> /dev/block/mmcb
lk0p23
lrwxrwxrwx root root 2014-01-11 04:52 tz -> /dev/block/mmcblk0p
8
lrwxrwxrwx root root 2014-01-11 04:52 userdata -> /dev/block/mm
cblk0p26
And I backup with :
dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p10 of=/storage/extSdCard/param.bin bs=4096
But when I opened param.bin with tar was empty.
Any idea?
You obviously don't know what you're doing, and are going to wind up in Bricktown.
That aside, dd creates images, NOT tar files. You need to know what format the binary image is in to mount and/or extract it to inspect contents.
Again, tar won't help you here.
Sent from my leanKernel 3.17 powered stock 4.4.2 SM-N900T
On Galaxy S I was able to open image with tar!
But this image contains only zeros.

Moto e us lte / boot.img / mounts

Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Excellent.... Thank u....I will try to release a ROM within a week
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
good news, good luck for your build
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
awesome, if you need a tester, please pm.
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
Shawn, you got a Moto E 2015? :laugh:
I find myself fortunate getting MotoG 2015 n Moto E 2015, both being worked upon by you! Thanks man!
If anybody who us good at linux knows how to add these mount points to cwm or philz touch im trying to port a build for us pm me.
WIFI tethering
I just picked this phone up today and cricket has ripped out the WIFI tethering. If anyone has a stock rooted rom please send me a link.
Mounting points are different on my cmda moto e2 will try to upload them later
bzo22 said:
Mounting points are different on my cmda moto e2 will try to upload them later
Click to expand...
Click to collapse
yup the cdma models and the 3g only models will probably have different mounts.
cmda xt1526 boostmobile surina
s -al /dev/block/platform/soc.0/by-name <
/dev/block/platform/soc.0/by-name: Permission denied
1|[email protected]_cdma:/ $ su
s -al /dev/block/platform/soc.0/by-name <
lrwxrwxrwx root root 1970-01-31 14:18 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-31 14:18 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-31 14:18 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-31 14:18 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-31 14:18 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-31 14:18 carrier -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-31 14:18 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-31 14:18 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-31 14:18 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-31 14:18 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-31 14:18 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-31 14:18 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-31 14:18 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-31 14:18 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-31 14:18 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-31 14:18 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-31 14:18 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-31 14:18 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-31 14:18 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-31 14:18 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-31 14:18 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-31 14:18 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-31 14:18 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-31 14:18 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-31 14:18 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-31 14:18 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-31 14:18 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-31 14:18 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-31 14:18 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-31 14:18 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-31 14:18 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-31 14:18 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-31 14:18 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-31 14:18 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-31 14:18 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-31 14:18 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-31 14:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-31 14:18 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-31 14:18 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-31 14:18 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-31 14:18 userdata -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-31 14:18 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-31 14:18 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_cdma:/ #
bzo22 said:
s -al /dev/block/platform/soc.0/by-name <
<SNIP>
[email protected]_cdma:/ #
Click to expand...
Click to collapse
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
aboot.img
bzo22 said:
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
Click to expand...
Click to collapse
Here u go the aboot.img
Rooted this Phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
i have root on this phone look and see.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
here are some more pictures of my phone.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#1
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#2
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#3
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#4.
there you go. im not giving you the files.because i can
fix-this! said:
Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Click to expand...
Click to collapse
hey bro i needed some help. first can this boot image be used for 3g version.
If not then please can you tell me how to extract the boot.img of moto e 3g version
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
hakr4life said:
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
Click to expand...
Click to collapse
Same here keep me in the loop. I'm eager to brick my new phone
Sent from my MotoE2(4G-LTE) using XDA Free mobile app
+1 for at%t/aio/cricket users on the XT1527 model. there has got to be a workaround for the unlock on this. @mdewii23 @hakr4life
Can someone provide stock recovery?
I've scoured the internet over and over and come up with nothing yet
Sent from my Nexus 4 using XDA Free mobile app

Partition LG-H818P and script backup all Partitions

This Script need ROOT. How to root ?
dd if=/dev/block/bootdevice/by-name/DDR of=/sdcard/DDR.img
dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/bootdevice/by-name/abootbak of=/sdcard/abootbak.img
dd if=/dev/block/bootdevice/by-name/apdp of=/sdcard/apdp.img
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/bootdevice/by-name/cache of=/sdcard/cache.img
dd if=/dev/block/bootdevice/by-name/cust of=/sdcard/cust.img
dd if=/dev/block/bootdevice/by-name/devinfo of=/sdcard/devinfo.img
dd if=/dev/block/bootdevice/by-name/dpo of=/sdcard/dpo.img
dd if=/dev/block/bootdevice/by-name/drm of=/sdcard/drm.img
dd if=/dev/block/bootdevice/by-name/eksst of=/sdcard/eksst.img
dd if=/dev/block/bootdevice/by-name/encrypt of=/sdcard/encrypt.img
dd if=/dev/block/bootdevice/by-name/factory of=/sdcard/factory.img
dd if=/dev/block/bootdevice/by-name/fota of=/sdcard/fota.img
dd if=/dev/block/bootdevice/by-name/fsc of=/sdcard/fsc.img
dd if=/dev/block/bootdevice/by-name/fsg of=/sdcard/fsg.img
dd if=/dev/block/bootdevice/by-name/grow of=/sdcard/grow.img
dd if=/dev/block/bootdevice/by-name/hyp of=/sdcard/hyp.img
dd if=/dev/block/bootdevice/by-name/hypbak of=/sdcard/hypbak.img
dd if=/dev/block/bootdevice/by-name/keystore of=/sdcard/keystore.img
dd if=/dev/block/bootdevice/by-name/laf of=/sdcard/laf.img
dd if=/dev/block/bootdevice/by-name/limits of=/sdcard/limits.img
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.img
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.img
dd if=/dev/block/bootdevice/by-name/mpt of=/sdcard/mpt.img
dd if=/dev/block/bootdevice/by-name/msadp of=/sdcard/msadp.img
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/persistent of=/sdcard/persistent.img
dd if=/dev/block/bootdevice/by-name/pmic of=/sdcard/pmic.img
dd if=/dev/block/bootdevice/by-name/pmicbak of=/sdcard/pmicbak.img
dd if=/dev/block/bootdevice/by-name/raw_resources of=/sdcard/raw_resources.img
dd if=/dev/block/bootdevice/by-name/raw_resourcesbak of=/sdcard/raw_resourcesbak.img
dd if=/dev/block/bootdevice/by-name/rct of=/sdcard/rct.img
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
dd if=/dev/block/bootdevice/by-name/rpm of=/sdcard/rpm.img
dd if=/dev/block/bootdevice/by-name/rpmbak of=/sdcard/rpmbak.img
dd if=/dev/block/bootdevice/by-name/sbl1 of=/sdcard/sbl1.img
dd if=/dev/block/bootdevice/by-name/sbl1bak of=/sdcard/sbl1bak.img
dd if=/dev/block/bootdevice/by-name/sdi of=/sdcard/sdi.img
dd if=/dev/block/bootdevice/by-name/sdibak of=/sdcard/sdibak.img
dd if=/dev/block/bootdevice/by-name/sec of=/sdcard/sec.img
dd if=/dev/block/bootdevice/by-name/sns of=/sdcard/sns.img
dd if=/dev/block/bootdevice/by-name/spare1 of=/sdcard/spare1.img
dd if=/dev/block/bootdevice/by-name/spare2 of=/sdcard/spare2.img
dd if=/dev/block/bootdevice/by-name/ssd of=/sdcard/ssd.img
dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
dd if=/dev/block/bootdevice/by-name/tz of=/sdcard/tz.img
dd if=/dev/block/bootdevice/by-name/tzbak of=/sdcard/tzbak.img
dd if=/dev/block/bootdevice/by-name/userdata of=/sdcard/userdata.img
Click to expand...
Click to collapse
Source
lrwxrwxrwx root root 2015-01-01 09:08 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-01 09:08 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-01 09:08 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-01 09:08 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-01 09:08 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-01 09:08 cache -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-01 09:08 cust -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-01 09:08 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-01 09:08 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-01 09:08 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-01-01 09:08 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-01 09:08 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-01 09:08 factory -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-01 09:08 fota -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-01 09:08 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-01 09:08 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-01 09:08 grow -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-01 09:08 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-01 09:08 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-01 09:08 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-01 09:08 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-01 09:08 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-01 09:08 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-01 09:08 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-01 09:08 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-01 09:08 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-01 09:08 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-01 09:08 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-01 09:08 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-01 09:08 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-01 09:08 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-01 09:08 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-01 09:08 raw_resources -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-01 09:08 raw_resourcesbak -> /dev/block/mmcblk
lrwxrwxrwx root root 2015-01-01 09:08 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-01 09:08 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-01 09:08 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-01 09:08 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-01 09:08 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-01 09:08 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-01 09:08 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-01 09:08 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-01 09:08 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-01 09:08 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-01 09:08 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-01 09:08 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-01 09:08 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-01 09:08 system -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-01 09:08 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-01 09:08 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-01 09:08 userdata -> /dev/block/mmcblk0p50
Click to expand...
Click to collapse

[Q] Android Kitchen edify_defs file for Samsung core prime [G360H]

so uhm yeah i need edify_defs for G360H but it's a Spreadtrum chip and i only find example for MTD and EMMC ( it's a chip or what ?? MTD is a chip but wth is EMMC chip ?? i'm so confuse )
can someone pls share that file with me and if you need specific details of mount point , it's all be low boiiii
Thx and pls help
[email protected]:/ $ ls -la /dev/block/platform/sprd-sdhci.3/by-name
lrwxrwxrwx root root 2018-04-15 02:30 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2018-04-15 02:30 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-04-15 02:30 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2018-04-15 02:30 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2018-04-15 02:30 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-04-15 02:30 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-04-15 02:30 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2018-04-15 02:30 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2018-04-15 02:30 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2018-04-15 02:30 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-04-15 02:30 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-04-15 02:30 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-04-15 02:30 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-04-15 02:30 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2018-04-15 02:30 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2018-04-15 02:30 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2018-04-15 02:30 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-04-15 02:30 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-04-15 02:30 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-04-15 02:30 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2018-04-15 02:30 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2018-04-15 02:30 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-04-15 02:30 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-04-15 02:30 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-04-15 02:30 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
I haven't got what you want!
What files you need?

Categories

Resources