So normally, nexus devices have easy partition names... For example, the /dev/block/platform/by-name directory contains things like system, boot, recovery, data, modem, efs, etc.. Well here is the result of "ls -al" of the partition directory on my nexus 9.
[email protected]_lte:/ # ls -al /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2014-12-30 12:10 APP -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-12-30 12:10 CAC -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-12-30 12:10 CDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-12-30 12:10 DIA -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-30 12:10 DTB -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-30 12:10 EF1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-30 12:10 EF2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-12-30 12:10 EKS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-30 12:10 EXT -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-30 12:10 FST -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-30 12:10 GPT -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-12-30 12:10 KEY -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-30 12:10 LNX -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-30 12:10 MD1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-12-30 12:10 MD2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-12-30 12:10 MFG -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-12-30 12:10 MSC -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-30 12:10 NCT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-30 12:10 OTA -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-12-30 12:10 PG1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-30 12:10 PST -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-12-30 12:10 RCA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-30 12:10 RV1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-30 12:10 RV2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-30 12:10 RV3 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-12-30 12:10 SER -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-30 12:10 SOS -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-30 12:10 SP1 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-30 12:10 TOS -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-30 12:10 UDA -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-12-30 12:10 VNR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-12-30 12:10 WB0 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-30 12:10 WDM -> /dev/block/mmcblk0p7
My question is, which is which? How can i tell which is the recovery block, system block, recovery and so on? Is there a list of translations for these partition names? Thanks
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
peterk-1 said:
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
Click to expand...
Click to collapse
For example, nexus 5 has a symlinks like /dev/block/platform/msm_sdcc.1/by-name/boot that is linked to /dev/block/mmcblk0p19. Clearly this is the kernel block. Because its called "boot". Right? So, the nexus 9 is different from most other nexus devices. The by-name folder has 3 character names that dont really translate to "boot" or "system" or "recovery". It has names like "dia" and "vnr". I know that the "vnr" is the Vendor block. So which one is the "boot" block, is it "dia", or is it"svn". Do you understand what im asking? How in the heck is one supposed to figure out which block device is which???
bynarie said:
How in the heck is one supposed to figure out which block device is which???
Click to expand...
Click to collapse
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
thanks!
peterk-1 said:
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
Click to expand...
Click to collapse
Thanks!! That fstab flounder page is a really good starting list of exactly what i was looking for. {{Presses Thanks Button}}
Is it possible to delete some partitions like system image and resize data partition?
wizzardsk said:
Is it possible to delete some partitions like system image and resize data partition?
Click to expand...
Click to collapse
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Vartom said:
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Click to expand...
Click to collapse
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
wizzardsk said:
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
Click to expand...
Click to collapse
you are mistaken, he has one system partitions (APP).
What is this?
wizzardsk said:
What is this?
Click to expand...
Click to collapse
Same thing. One is a regular backup, one is to backup as an image (system.img) pick the way you want to backup.
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
wizzardsk said:
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
Click to expand...
Click to collapse
Yes there is only 1 system partition. TWRP is offering 2 ways to make a system backup, either a standard backup, or backup as an image.
Related
Hello, i try port miui to our galaxy...
I need partition layout of GT-I9305 to set up the installation script. Can anyone post it here?
Sent from my GT-I9305
I cant help
Gut it would be great if u create a miui Rom
Thanks For your work homey
Here you go
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
---------- Post added at 12:11 PM ---------- Previous post was at 11:39 AM ----------
Let us know how you go, honestly I dont know why experienced devs have not done this yet to other roms, it really doesnt seem so hard for a dev that knows what they are doing, all it really needs is the base firmware changed and the edited files in the I9300 JB base can probably be used in replace of the non-edited ones in the i9305 base saves you from editing the files again. then all the system files should be easily transferable and then the mounting points changed , that sounds like pretty much it or am i missing something?
btemtd said:
Here you go
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
---------- Post added at 12:11 PM ---------- Previous post was at 11:39 AM ----------
Let us know how you go, honestly I dont know why experienced devs have not done this yet to other roms, it really doesnt seem so hard for a dev that knows what they are doing, all it really needs is the base firmware changed and the edited files in the I9300 JB base can probably be used in replace of the non-edited ones in the i9305 base saves you from editing the files again. then all the system files should be easily transferable and then the mounting points changed , that sounds like pretty much it or am i missing something?
Click to expand...
Click to collapse
Because there is no Stock jb Version out for s3 but should Come in a few days maybe weeks....
What do you mean no stock JB ? There is stock jb out now for the i9300
Sent from my GT-I9305 using xda app-developers app
I ported MIUI JB for i9300 on AOSP CM10 base, maybe I can help. What base do you want to use?
Well the Xxali5 is the original release and most internationally used and most popular base at the moment
But Some countries released there ph0ne later with a firmware number xxali9. Not sure if there is even any changes. But your choice.
Sent from my GT-I9305 using xda app-developers app
btemtd said:
What do you mean no stock JB ? There is stock jb out now for the i9300
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
there is noch stock jb miui!!!!!!!!!!!!!!!!!!!!!!!! its coming in future
aosp or cm doesnt work for our device!
greetz
F1tty said:
there is noch stock jb miui!!!!!!!!!!!!!!!!!!!!!!!! its coming in future
aosp or cm doesnt work for our device!
greetz
Click to expand...
Click to collapse
Yes indeed...
But as u said there is no stock JB that is what got me confused cause you didnt say MIUI!!!!!!
btemtd said:
Yes indeed...
But as u said there is no stock JB that is what got me confused cause you didnt say MIUI!!!!!!
Click to expand...
Click to collapse
Cause that thread belongs to miui.... If miui for I9300 JB is aviable i Port IT for i9305 specially for english and german maybe more depending on Base rom
Then i think that is part of the instructions. Maybe u can use a miui i9300 jb base and merge it the i9305 base
Sent from my GT-I9305 using xda app-developers app
I cant wait
Can u tell us your progress?
dying to hear the good news
any advance on this? would be amazingg
is there some news on porting ?
Porting is easy, if no one is going to do it I might do it if I get some spare time.. just don't expect any support or updates ok?
Sent from my GT-I9300 using xda app-developers app
Hi, I have bought a prototype z ultra, probably BROWN - the tech support said customers aren't allowed to have these, and there's no way to update it. Can I install any custom roms on it? Please, help me, I'm really despaired...
UPDATE:
I flashed cyanogenmod 10.2 on it, but it didn't recognize my sim card, the radio was off, mobile service not working.
Then I flashed the AOSB ROM, now the IMEI has gone lost. Before I made any changes I backed up that TA partiton, maybe that can help in some way? Then I unlocked the bootloader, and flashed the cyanogen.
Does someone know if it's safe to flash an ftf file on a prototype device?
dkanas said:
Hi, I have bought a prototype z ultra, probably BROWN - the tech support said customers aren't allowed to have these, and there's no way to update it. Can I install any custom roms on it? Please, help me, I'm really despaired...
UPDATE:
I flashed cyanogenmod 10.2 on it, but it didn't recognize my sim card, the radio was off, mobile service not working.
Then I flashed the AOSB ROM, now the IMEI has gone lost. Before I made any changes I backed up that TA partiton, maybe that can help in some way? Then I unlocked the bootloader, and flashed the cyanogen.
Does someone know if it's safe to flash an ftf file on a prototype device?
Click to expand...
Click to collapse
Was it on the latest firmware?
I thought that prototypes mostly couldn't unlock the BL, but then there as some on here that could...? confused...
blueether said:
Was it on the latest firmware?
I thought that prototypes mostly couldn't unlock the BL, but then there as some on here that could...? confused...
Click to expand...
Click to collapse
It was on some early software, 14.1.B.1.263, android 4.2.2. I couldn't update it with pc companion and the update center on the phone. The imei was beginning with 0044.
dkanas said:
It was on some early software, 14.1.B.1.263, android 4.2.2. I couldn't update it with pc companion and the update center on the phone. The imei was beginning with 0044.
Click to expand...
Click to collapse
restoring the correct, or even a new, FTF will bring back the imei.
the next issue is if flashtool will flash a new FTF, if it will then you can then use a 4.4.4 or 5.0 ROM hopefully
blueether said:
restoring the correct, or even a new, FTF will bring back the imei.
the next issue is if flashtool will flash a new FTF, if it will then you can then use a 4.4.4 or 5.0 ROM hopefully
Click to expand...
Click to collapse
Yes, i know. But I don't know if the partitions in this prototype match the production models partitions, there could be a difference, like in the gpe model. I don't want to brick this device, it's worth a half of the usual monthly salary in my country Does someone know what exactly is the difference between the regular and the gpe editions?
Update: I think I pulled out the partition layout from my prototype:
Code:
lrwxrwxrwx root root 1970-01-02 04:33 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:33 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:33 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:33 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:33 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:33 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:33 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:33 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:33 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:33 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:33 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:33 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:33 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:33 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:33 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:33 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:33 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:33 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:33 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:33 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:33 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:33 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:33 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:33 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:33 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 04:33 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:33 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:33 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:33 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:33 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:33 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:33 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:33 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:33 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:33 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:33 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:33 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:33 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:33 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:33 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:33 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:33 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:33 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:33 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:33 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:33 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:33 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:33 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:33 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:33 userdata -> /dev/block/mmcblk0p25
What further information can I provide you?
I flashed cyanogenmod 10.2 back, the IMEI is now back - but still no mobile service. Any ideas what could be wrong?
Settings -> About phone -> Status:
Network: unknown
Mobile network type: unknown
Service state: radio off
Roaming: no roaming
Mobile network state: disconnected
IMEI: 0044***********
IMEI SV: 17 (before messing with custom roms it was 01, or 11, can't recall now...)
Baseband version: 8974-AAAAANAZQ-10220006-17
Signal strenght: 2147483647 ASU 255 - that's weird.
Also, network mode is set on WCDMA preferred and I can't switch to another option - it immediately switches back.
Update:
Dial *#*#4636#*#* ---> phone info ---> there is a switch to turn on/off radio - >didn't work either
dkanas said:
I flashed cyanogenmod 10.2 back, the IMEI is now back - but still no mobile service. Any ideas what could be wrong?
Settings -> About phone -> Status:
Network: unknown
Mobile network type: unknown
Service state: radio off
Roaming: no roaming
Mobile network state: disconnected
IMEI: 0044***********
IMEI SV: 17 (before messing with custom roms it was 01, or 11, can't recall now...)
Baseband version: 8974-AAAAANAZQ-10220006-17
Signal strenght: 2147483647 ASU 255 - that's weird.
Also, network mode is set on WCDMA preferred and I can't switch to another option - it immediately switches back.
Update:
Dial *#*#4636#*#* ---> phone info ---> there is a switch to turn on/off radio - >didn't work either
Click to expand...
Click to collapse
I cant see that the partition layout would have changed can uou use adb shell to list the partitions?
Code:
adb shell
su
fdisk -l /dev/block/platform/msm_sdcc.1/mmcblk0
output should be:
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 30535680 sectors, 2622M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 25 entries
First usable sector is 34, last usable sector is 30535646
Number Start (sector) End (sector) Size Code Name
1 256 4351 2048K 0700 TA
2 4352 5375 512K 0700 sbl1
3 5376 5887 256K 0700 s1sbl
4 5888 6015 65536 0700 dbi
5 6016 7039 512K 0700 aboot
6 7040 8063 512K 0700 rpm
7 8064 9087 512K 0700 tz
8 9088 10111 512K 0700 alt_sbl1
9 10112 10623 256K 0700 alt_s1sbl
10 10624 10751 65536 0700 alt_dbi
11 10752 11775 512K 0700 alt_aboot
12 11776 12799 512K 0700 alt_rpm
13 12800 13823 512K 0700 alt_tz
14 13824 54783 20.0M 0700 boot
15 54784 75263 10.0M 0700 ramdump
16 75264 108031 16.0M 0700 FOTAKernel
17 108032 108095 32768 0700 DDR
18 114688 147455 16.0M 0700 LTALabel
19 147456 150527 1536K 0700 modemst1
20 155648 158719 1536K 0700 modemst2
21 163840 166911 1536K 0700 fsg
22 172032 188415 8192K 0700 apps_log
23 188416 4947967 2324M 0700 system
24 4947968 5357567 200M 0700 cache
25 5357568 30535646 12.0G 0700 userdata
[email protected]:/ #
@blueether
Code:
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1 1 1901 15267839+ ee EFI GPT
This is what I got
I see I have EFI, and not MBR, which doesn't sound good, am I right?
dkanas said:
@blueether
Code:
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1 1 1901 15267839+ ee EFI GPT
This is what I got
I see I have EFI, and not MBR, which doesn't sound good, am I right?
Click to expand...
Click to collapse
not sure on the effect of EFi vs MBR
@blueether
I got this from parted: (sorry it's only a screenshot)
Althought diskinfo utility for android is showing the same values as your fdisk results
{
"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"
}
dkanas said:
@blueether
I got this from parted: (sorry it's only a screenshot)
Althought diskinfo utility for android is showing the same values as your fdisk results
Click to expand...
Click to collapse
@blueether
I flashed the newest FTF and it's working! I'll be grateful to death!
for partitions you can also use parted
Code:
adb shell
cd /dev/block
# you can use
Code:
ls
if you want to see which partitions are in this folder. mmcblk0 is the one were everyting in is stored, mmcblk1 is your sdcard.
Code:
parted mmcblk0
print
.
now you see your partitions, with parted you can also adjust them (Don't do that, you'll brick when you make a mistake)
for commando options in parted use
Code:
help
or
Code:
parted
(i forgot)
Anyway good that you fixed your phone, just wanted to share
Can brown devices receive OTA updates? Ever since I have my prototype XZL, I never received a single update from sony, the only updates I receive are those from apps installed via the playstore.
This partition apparently holds the IMEI (well on the Moto G 2013 it does) but I don't even see that it exists on this phone (xt1527). I can't seem to make a backup of it but the phone works so, is it even there or have they changed how it works?
bump, same issue
seems a bunch of us have this issue.
sad there seems to be no answer anywhere..
edit:
here is what i got listing partitions.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]_umts:/ $ su
[email protected]_umts:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-06-10 11:47 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-06-10 11:47 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-06-10 11:47 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-06-10 11:47 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-06-10 11:47 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-06-10 11:47 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-06-10 11:47 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-06-10 11:47 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-06-10 11:47 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-06-10 11:47 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-06-10 11:47 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-06-10 11:47 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-06-10 11:47 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-06-10 11:47 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-06-10 11:47 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-06-10 11:47 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-06-10 11:47 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-06-10 11:47 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-06-10 11:47 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-06-10 11:47 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-06-10 11:47 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-06-10 11:47 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-06-10 11:47 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-06-10 11:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-06-10 11:47 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-06-10 11:47 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-06-10 11:47 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-06-10 11:47 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-06-10 11:47 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-06-10 11:47 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-06-10 11:47 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-06-10 11:47 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-06-10 11:47 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-06-10 11:47 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-06-10 11:47 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-06-10 11:47 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-06-10 11:47 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-06-10 11:47 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-06-10 11:47 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-06-10 11:47 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-06-10 11:47 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-06-10 11:47 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-06-10 11:47 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-06-10 11:47 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_umts:/ #
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
conductive said:
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
Click to expand...
Click to collapse
on another phone it's mmcblk12 (i have been doing a LOT of searching on this)
i looked at the root folder on my phone and i see a shortcut to "pds"
when i open it it's empty.
i have some experience with Linux but i am no pro and it's been a while for my nix activity.
and i have almost no experience with Android.
i am good with computer stuff though. cracking, coding reversing, graphics etc.
i love modding everything i can.
i say that to give a bit of context to this..
if anyone else has any idea or leads on what i can do or where to look i am all ears.
i posted that partition command because i found it on Google
and i remember using it (ls) before trouble shooting driver issues on Linux in the past.
you guys will notice the console log i posted does not list a pds partition by-name..
is it because it's not mounted maybe ? or is it using a different name on this phone ?
i'd love to try and update to 5.1 (from 5.0..2) on my Telus XT1527 but i think it's time i make a PDS backup before i carry on any further.. so far i have installed a custom kernel and TWRP + root.
So i can't continue until i figure out a way to back that stuff up (irresponsible otherwise i think)
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
conductive said:
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
Click to expand...
Click to collapse
That says Atrix though and on another posting i found it was mmcblk0p12
If you look at the log i posted earlier that number mmcblk0p3 is mapped to DDR
I have been dumping the partitions and checking them (if the file size is roughly correct)
I heard it was suppose to be about 8mb as an .img on another device.
and i have one downloaded as an image and extracted (some other guys data)
so if i find the files on my phone i think i can match them to my downloaded files.
i also got a windows tool to extract the images ready..
One last thing i said i seen a shortcut to "pds" on the filesystem of my Telus XT1527
so i take it that it's there just that i can't see it or something.
I'm basically poking around in the dark LOL
edit:
oh and i seen on other phones that pds partition can be backed up with TWRP.
The TWRP i have installed does not show it for me (i am using Squid's TWRP)
The partitions are probably associated with the OS version and not the hardware so you should probably compare your version to a similar version.
If you can find fstab file you should be able to (cat fstab) and see what the partitions are mounted as.
The partition should be mounted or else your device will not work.
I've modded fstab on linux before but i am not finding it i think on the XT1527
found a couple with "fstab" in the title and it don't say much..
just one line about mounting the sdcard.
Thanks but i am lost.. i wonder how it's created because it's prob not files in the Firmware package right ?
So then i'd have to assume the contents of PDS would be created on the phones first boot maybe.
i don't know what else to do really i am going around in circles ..i might just say screw it and give up.
too bad guys here who DO have the ability to find it can't help
100% of Moto-E users seem to carry on flashing their phones with out it
so i take it backing up the PDS is pointless ?
Just kind of dumb i see tutorials on how to do it all over but no one can claim it actually works LOL
If you google it you will see what i am saying (people tell you to you to do it becuase it's sooooo important..
then it doesn't work ahahaha
thanks for your help conductive.
edit:
Oh and guys.. i tried to do this because... Q13:
http://forum.xda-developers.com/moto-e-2015/help/faq-frequently-questions-moto-e-2015-t3044929
The stickied topic here tells us all how to do it.
..but did anyone at all bother to verify it actually works ?
Ok so i think i got it.. sort of.
I installed "Root Explorer Pro" and when i opened it this time it showed files/folders.
I then selected .zip it up and copied it manually to my sdcard then to my PC.
I have been hex viewing the contents with UltraEdit and the files contain data.
I also compared to a pds dump from an Atrix and they are some what similar.
I did see a reference in one of the root config files about the pds partition though..
I can't recall which file it was but it said something about
setting the dummy directory "pds" as persistent.
I don't know what is going on but i got the content off the phone i think.
edit:
Here is what the root of that folder looked like (folder names)
Code:
.bt_nv.bin
batt_health
bt
camera
data
factory
lost+found
public
security
WCNSS_wlan_dictionary.dat
wifi
wmdrm
STOCK FIRMWARE FOR E2303 FLASHABLE ZIP
UPDATE: Uploading because this time IT WORK! Thanks to @TheVektor for updater-script! But this isn't pre-rooted, because it not flash SuperSU. But it's still awesome because if you have problems with flashmode or other you can flash this as a recovery zip! Tested on E2303 with TWRP. Made with PRFCreator
alby_var said:
STOCK PRE-ROOTED FIRMWARE FOR E2303 FLASHABLE ZIP
Hey guys! I had a problem entering flashmode and the only way for unbrick my phone was enter into recovery/flash a zip or fastboot flash.
For this, i made a pre-rooted firmware with PRFcreator. Now I am testing it. It will not install a recovery because xzdualrecovery is not compatible with our device. That means you have to flash it manually before start installing this.
STATUS: RECOVERY NOT INSTALL ZIP FILE....
Download: testing and uploading...
Click to expand...
Click to collapse
Hey! I'm interested in this ROM, my device has a locked bootloader and I think this would solve out the issue of rooting without unlocking the bootloader. I can test the ROM. My model is: E2306
Do you have any finished projects?
Quien mucho abarca poco aprieta
rascayus said:
Quien mucho abarca poco aprieta
Click to expand...
Click to collapse
English please
Don'te bite more than you can chew
I think every thread you have created is pointless. "Uploading"... yeah great.
Maybe get something uploaded first, then create a thread instead of having multiple threads that are pointless...
I respect your efforts but still
Guys, the rom are completed, the problem is that we haven't a working updater-script file. It is needed for flash roms, and I am working to make one that work. I can upload the rom and give you the link, but if it not flash, where is the sense in that?
Code:
if
run_program("/tmp/busybox", "ls", "/dev/block/platform/msm_sdcc.1/by-uuid/F9CDF7BA-B834-A72A-F1C9-D6E0C0983896") != "0"
then
abort("Error: UUID link to system partition does not exist");
endif;
assert(package_extract_file("system.ext4", "/dev/block/platform/msm_sdcc.1/by-uuid/F9CDF7BA-B834-A72A-F1C9-D6E0C0983896"));
M4 Aqua (E2303) does not have "msm_sdcc.1" and "by-uuid" folders or whatever is it....
We have MMC device partitions:
Code:
lrwxrwxrwx root root 1970-02-06 11:48 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-02-06 11:48 FOTAKernel -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-02-06 11:48 LTALabel -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-02-06 11:48 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-02-06 11:48 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-02-06 11:48 alt_aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-02-06 11:48 alt_hyp -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-02-06 11:48 alt_rpm -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-02-06 11:48 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-02-06 11:48 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-02-06 11:48 alt_tz -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-02-06 11:48 apps_log -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-02-06 11:48 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-02-06 11:48 cache -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-02-06 11:48 config -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-02-06 11:48 fsg -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-02-06 11:48 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-02-06 11:48 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-02-06 11:48 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-02-06 11:48 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-02-06 11:48 oem -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-02-06 11:48 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-02-06 11:48 rdimage -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-02-06 11:48 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-02-06 11:48 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-02-06 11:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-02-06 11:48 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-02-06 11:48 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-02-06 11:48 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-02-06 11:48 userdata -> /dev/block/mmcblk0p29
So we need create updater-script using similar formats:
Code:
run_program("/tmp/busybox", "ls", "/dev/block/mmcblk0p30") != "0"
AND
assert(package_extract_file("system.ext4", "/dev/block/mmcblk0p30"));
Im not 100% sure this is the problem, but i hope it can help for you.
Edit:
OK! zip flashing finished (system flashed!), but supersu not installed by updater-script... idk why.
My updater-script: http://pastebin.com/8Lg7UseV
Ohh! Really Really Really thank you!! Now i can unbrick my phone and finally complete the roms!
alby_var said:
STOCK FIRMWARE FOR E2303 FLASHABLE ZIP
UPDATE: Uploading because this time IT WORK! Thanks to @TheVektor for updater-script! But this isn't pre-rooted, because it not flash SuperSU. But it's still awesome because if you have problems with flashmode or other you can flash this as a recovery zip! Tested on E2303 with TWRP. Made with PRFCreator
Click to expand...
Click to collapse
Its flashable zip too... not important pre-rooted or not after flashing is done, simple you can install supersu.zip too. :good:
But You try to build pre rooted Rom?
Wysłane z mojego E2303 przy użyciu Tapatalka
Later I will try to make a flashable working prerooted, tomorrow i will upload it ( i tried today but still at 60% uploading) but for now I will complete de-bloated and other projects....
Ok, I uploaded to Mediafire but it not give me the link.... I am uploading again to Mega and its at 30%
alby_var said:
Ok, I uploaded to Mediafire but it not give me the link.... I am uploading again to Mega and its at 30%
Click to expand...
Click to collapse
And ?? Can you upload pre rooted Rom ?
I not successfully can upload it. All hosting websites stop uploading or still for 2-3 days and i have to shut down pc.
Upload it to google drive and share link,ty
Stock firmware for e2303 flashable zip
Link?
26.1.a.2.167/r12a
Can someone explain what means R12A in 26.1.A.2.167/R12A ?
so, does anybody have this flashable stock rom? I could really use it right now...
Hello!
I have an off-brand (PumpkinX) Android 5.1 tablet that freezes at the Intel logo screen during boot. I can still get into Fastboot and recovery. The tablet identifies itself in fastboot as inet_w I101B. The serial number starts with Baytrail. When booting, the PumpkinX logo appears, then the Intel logo, at which point the tablet freezes.
Long story short...after several months of operation, some kind of corruption happens, and the tablet will not boot. The first one was replaced by the vendor. And the second one has now done the same thing. I have a logcat (attached) of what happens. In summary, the tablet starts throwing
Code:
E/EM FG ALGO Iface:(xxx): Failed to get File Descriptor
errors shortly after boot, and does this until it is turned off. I am trying to understand what is going on, so I can fix the problem myself.
When I got the second tablet, I made images of all the partitions, so if a partition is bad, I can restore it. What I am trying to figure out is which partition might be corrupted, and I am hoping that someone could look at the logcat and make a guess as to what point in the boot process this happens and what has been corrupted. The partition layout is as follows:
Code:
[email protected]_w:/ # ls -l /dev/block/platform/80860F14:00/by-name
lrwxrwxrwx root root 2016-09-10 17:12 ESP -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-09-10 17:12 boot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-09-10 17:12 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-09-10 17:12 config -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-09-10 17:12 data -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-09-10 17:12 factory -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-09-10 17:12 fastboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-09-10 17:12 logs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-09-10 17:12 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-09-10 17:12 panic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-09-10 17:12 persistent -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-09-10 17:12 recovery -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-09-10 17:12 system -> /dev/block/mmcblk0p12
Thanks for any help!
Bump...still looking for some insight/help! Thanks!