Sprint Galaxy Note 5 SM-N920P Partition Table
credits @rlmiller for helping retrieve this
lrwxrwxrwx root root 2015-08-30 20:02 BOOT -> /dev/block/sda7
lrwxrwxrwx root root 2015-08-30 20:02 BOTA0 -> /dev/block/sda1
lrwxrwxrwx root root 2015-08-30 20:02 BOTA1 -> /dev/block/sda2
lrwxrwxrwx root root 2015-08-30 20:02 CACHE -> /dev/block/sda17
lrwxrwxrwx root root 2015-08-30 20:02 CARRIER -> /dev/block/sda18
lrwxrwxrwx root root 2015-08-30 20:02 DNT -> /dev/block/sda12
lrwxrwxrwx root root 2015-08-30 20:02 EFS -> /dev/block/sda3
lrwxrwxrwx root root 2015-08-30 20:02 OTA -> /dev/block/sda9
lrwxrwxrwx root root 2015-08-30 20:02 PARAM -> /dev/block/sda6
lrwxrwxrwx root root 2015-08-30 20:02 PERSDATA -> /dev/block/sda15
lrwxrwxrwx root root 2015-08-30 20:02 PERSISTENT -> /dev/block/sda13
lrwxrwxrwx root root 2015-08-30 20:02 RADIO -> /dev/block/sda10
lrwxrwxrwx root root 2015-08-30 20:02 RECOVERY -> /dev/block/sda8
lrwxrwxrwx root root 2015-08-30 20:02 STEADY -> /dev/block/sda14
lrwxrwxrwx root root 2015-08-30 20:02 SYSTEM -> /dev/block/sda16
lrwxrwxrwx root root 2015-08-30 20:02 TOMBSTONES -> /dev/block/sda11
lrwxrwxrwx root root 2015-08-30 20:02 USERDATA -> /dev/block/sda19
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs1 -> /dev/block/sda4
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs2 -> /dev/block/sda5
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs3 -> /dev/block/sdd1
Examples of some new mounting points for the SM-N920P:
Kernel - "/dev/block/platform/15570000.ufs/by-name/BOOT"
Recovery - "/dev/block/platform/15570000.ufs/by-name/RECOVERY"
System - "/dev/block/platform/15570000.ufs/by-name/SYSTEM"
Thanks for sharing. That's gonna be very helpful. The note 5 tar ball sure is light. No carrier img and lacking several other common files in the tar that we're used to seeing. Makes me wonder why Samsung has streamlined the tar balls for the note 5.
tdunham said:
Sprint Galaxy Note 5 SM-N920P Partition Table
credits @rlmiller for helping retrieve this
lrwxrwxrwx root root 2015-08-30 20:02 BOOT -> /dev/block/sda7
lrwxrwxrwx root root 2015-08-30 20:02 BOTA0 -> /dev/block/sda1
lrwxrwxrwx root root 2015-08-30 20:02 BOTA1 -> /dev/block/sda2
lrwxrwxrwx root root 2015-08-30 20:02 CACHE -> /dev/block/sda17
lrwxrwxrwx root root 2015-08-30 20:02 CARRIER -> /dev/block/sda18
lrwxrwxrwx root root 2015-08-30 20:02 DNT -> /dev/block/sda12
lrwxrwxrwx root root 2015-08-30 20:02 EFS -> /dev/block/sda3
lrwxrwxrwx root root 2015-08-30 20:02 OTA -> /dev/block/sda9
lrwxrwxrwx root root 2015-08-30 20:02 PARAM -> /dev/block/sda6
lrwxrwxrwx root root 2015-08-30 20:02 PERSDATA -> /dev/block/sda15
lrwxrwxrwx root root 2015-08-30 20:02 PERSISTENT -> /dev/block/sda13
lrwxrwxrwx root root 2015-08-30 20:02 RADIO -> /dev/block/sda10
lrwxrwxrwx root root 2015-08-30 20:02 RECOVERY -> /dev/block/sda8
lrwxrwxrwx root root 2015-08-30 20:02 STEADY -> /dev/block/sda14
lrwxrwxrwx root root 2015-08-30 20:02 SYSTEM -> /dev/block/sda16
lrwxrwxrwx root root 2015-08-30 20:02 TOMBSTONES -> /dev/block/sda11
lrwxrwxrwx root root 2015-08-30 20:02 USERDATA -> /dev/block/sda19
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs1 -> /dev/block/sda4
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs2 -> /dev/block/sda5
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs3 -> /dev/block/sdd1
Click to expand...
Click to collapse
tx_dbs_tx said:
Thanks for sharing. That's gonna be very helpful. The note 5 tar ball sure is light. No carrier img and lacking several other common files in the tar that we're used to seeing. Makes me wonder why Samsung has streamlined the tar balls for the note 5.
Click to expand...
Click to collapse
Thank you both for all you have done for us on the sprint n5
Thanks,
Chaz187
You're welcome. Having more than one mastermind on this will definitely get things rolling right along. LOL I don't mind helping out. @tdunham has done more than his fair share of helping others here at XDA and I am the same way... I help whenever I can. Enjoy that note 5 @Chaz187
hiii
http://forum.xda-developers.com/note5/help/nvdata-bin-note5-t3194669/post62685509#post62685509
does anyone have the exact pit file and/or the BL,AP,CP, CSC firmware files? I flashed the wrong firmware to it, and it's never been the same even after flashing a single tarball OGD for the N920p, thanks in advance
how can i get n920c running 6.0.1 partition table
i dont have dev/block/sda19 for user data
my last sda is sda17
i want to recover its information s i need to create raw file from my userdata
i need it badly
....
---------- Post added at 09:45 AM ---------- Previous post was at 09:45 AM ----------
how can i get n920c running 6.0.1 partition table
i dont have dev/block/sda19 for user data
my last sda is sda17
i want to recover its information s i need to create raw file from my userdata
i need it badly
....
any chance of a screenshot of that partition list? I need the exact sizes for the 64gb version
newbreedsoftware said:
any chance of a screenshot of that partition list? I need the exact sizes for the 64gb version
Click to expand...
Click to collapse
That is exactly what gets displayed, there's nothing graphical to display. The partition list was generated from a terminal session. I'm not sure how it gets divided size wize and I own the 32gb version.
tdunham said:
That is exactly what gets displayed, there's nothing graphical to display. The partition list was generated from a terminal session. I'm not sure how it gets divided size wize and I own the 32gb version.
Click to expand...
Click to collapse
yeah im looking for the list that shows how many bytes each partition is and where each one stops and starts, like the one attached here that was from my LG v410 that has a messed up partition list i fixed
This is mine. If you want a different view, let me know the list command you prefer to use.
Code:
Filesystem Size Used Free Blksize
/dev 1.8G 140.0K 1.8G 4.0K
/sys/fs/cgroup 1.8G 12.0K 1.8G 4.0K
/mnt 1.8G 0.0K 1.8G 4.0K
/mnt/runtime/default/emulated 24.7G 21.6G 3.0G 4.0K
/mnt/runtime/read/emulated 24.7G 21.6G 3.0G 4.0K
/mnt/runtime/write/emulated 24.7G 21.6G 3.0G 4.0K
/system 4.2G 2.7G 1.5G 4.0K
/efs 15.7M 1.4M 14.3M 4.0K
/cache 290.6M 5.7M 284.9M 4.0K
/data 24.7G 21.6G 3.1G 4.0K
/persdata/absolute 4.9M 292.0K 4.6M 4.0K
/firmware 86.0M 66.9M 19.1M 16.0K
/cpdump 150.0M 0.0K 150.0M 4.0K
/carrier 40.3M 56.0K 40.2M 4.0K
/storage 1.8G 0.0K 1.8G 4.0K
/storage/emulated 24.7G 21.6G 3.0G 4.0K
/su 90.5M 2.4M 88.1M 4.0K
Related
help my CWM for SM G360H
courier72 said:
help my CWM for SM G360H
Click to expand...
Click to collapse
attach your stock boot.img and stock recovery.img and I will try to help.
y300-0100 said:
attach your stock boot.img and stock recovery.img and i will try to help.
Click to expand...
Click to collapse
View attachment boot.img View attachment recovery.img
twrp recovery test version
try this recovery. if not working i made stock recovery flashable via odin.
sources are here for you to check out (partitions , names):
https://github.com/Y300-0100/twrp_samsung_core33gxx
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
hanyyyy said:
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
Click to expand...
Click to collapse
Its stock recovery. Just made for odin.
did you tried twrp recovery? .
Y300-0100 said:
Its stock recovery. Just made for odin.
did you tried twrp recovery? .
Click to expand...
Click to collapse
i tried twrp recovery to by Odin
not work to when i git in recovery mod its gif me boot log and never get in recovery mod at all
hanyyyy said:
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
Click to expand...
Click to collapse
Y300-0100
Maybe more, need other files? Can I help?
courier72 said:
Y300-0100
Maybe more, need other files? Can I help?
Click to expand...
Click to collapse
Full partition table by name and block number.
what not working little more details like black screen or stuck in splash screen etc.
logcat if possible.
"Not working " answer doesn't mean anything for me.
It's like " my blender is not working. Any solution?
:.
Y300-0100 said:
Full partition table by name and block number.
:.
Click to expand...
Click to collapse
how to do it?
Y300-0100 said:
what not working little more details like black screen or stuck in splash screen etc.
Click to expand...
Click to collapse
stuck in splash screen
courier72 said:
how to do it?
Click to expand...
Click to collapse
for my device command is this:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
but for your you should check this for your device "sprd-sdhci.3"
Just check your fstab. Command is same as for G355HN
Code:
1|[email protected]:/ $ ls -al /dev/block/platform/sprd-sdhci.3/by-name
lrwxrwxrwx root root 2014-12-17 11:33 CSC -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-17 11:33 FIXNV1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-17 11:33 FIXNV2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-17 11:33 FOTA_SIG -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-17 11:33 HIDDEN -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-17 11:33 KERNEL -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-17 11:33 MODEM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-12-17 11:33 MODEM_BACKUP -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-17 11:33 OTA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-17 11:33 Odin_reserved -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-17 11:33 PARAM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-17 11:33 RECOVERY -> /dev/block/mmcblk0p18lrwxrwxrwx root root 2014-12-17 11:33 RUNTIMENV1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-17 11:33 RUNTIMENV2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-17 11:33 SBL1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-17 11:33 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-17 11:33 WDSP -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-17 11:33 WDSP_BACKUP -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-17 11:33 efs -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-17 11:33 fixnv1 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV2
lrwxrwxrwx root root 2014-12-17 11:33 fixnv2 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV1
lrwxrwxrwx root root 2014-12-17 11:33 prodnv -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-17 11:33 runtimenv1 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV1
lrwxrwxrwx root root 2014-12-17 11:33 runtimenv2 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV2
lrwxrwxrwx root root 2014-12-17 11:33 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-17 11:33 userdata -> /dev/block/mmcblk0p22
Y300-0100 said:
Just check your fstab. Command is same as for G355HN
Click to expand...
Click to collapse
Is not entirely clear. To do this, you need a computer and Linux?
courier72 said:
Is not entirely clear. To do this, you need a computer and Linux?
Click to expand...
Click to collapse
Just install android terminal.( from play store ) Command work's with non roted phones also .
and you shoud get this:
.
Y300-0100 said:
Just install android terminal.
Click to expand...
Click to collapse
But I do not understand what to do next
courier72 said:
But I do not understand what to do next
Click to expand...
Click to collapse
Oopen terminal, type command from above and hit enter...
k/platform/sprd-sdhci.3/by-name <
lrwxrwxrwx root root 2015-03-02 22:43 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-03-02 22:43 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-02 22:43 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-03-02 22:43 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-03-02 22:43 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-02 22:43 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-02 22:43 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-03-02 22:43 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-03-02 22:43 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-03-02 22:43 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-02 22:43 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-02 22:43 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-03-02 22:43 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-02 22:43 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-03-02 22:43 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-03-02 22:43 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-03-02 22:43 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-02 22:43 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-02 22:43 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-03-02 22:43 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-03-02 22:43 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-03-02 22:43 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-02 22:43 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-02 22:43 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-02 22:43 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
Y300-0100 said:
Full partition table by name and block number.
what not working little more details like black screen or stuck in splash screen etc.
logcat if possible.
"Not working " answer doesn't mean anything for me.
It's like " my blender is not working. Any solution?
:.
Click to expand...
Click to collapse
stuck in splash screen
and this is the Full partition table by name and block number
ਊock/platform/sprd-sdhci.3/by-name <
lrwxrwxrwx root root 2015-03-02 21:27 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-03-02 21:27 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-02 21:27 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-03-02 21:27 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-03-02 21:27 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-02 21:27 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-02 21:27 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-03-02 21:27 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-03-02 21:27 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-03-02 21:27 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-02 21:27 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-02 21:27 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-03-02 21:27 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-02 21:27 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-03-02 21:27 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-03-02 21:27 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-03-02 21:27 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-02 21:27 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-02 21:27 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-03-02 21:27 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-03-02 21:27 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-03-02 21:27 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-02 21:27 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-02 21:27 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-02 21:27 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
�
Cwm for samsung galaxy core prime
Any one can plz make cwm for core prime
twrp recovery test version
Changes I made :
https://github.com/Y300-0100/twrp_samsung_core33gxx/commit/8dde6d106ef5abf6ea52203d13091cb1b11480be
I will upload test build later
adb shell ls -la /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 2015-01-02 19:51 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-02 19:51 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-02 19:51 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-02 19:51 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-02 19:51 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-02 19:51 cache -> /dev/block/mmcblk0p54
lrwxrwxrwx root root 2015-01-02 19:51 carrier -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-02 19:51 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-02 19:51 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-02 19:51 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-01-02 19:51 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-02 19:51 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-02 19:51 eri -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-02 19:51 factory -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-02 19:51 felica -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-02 19:51 fota -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-02 19:51 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-02 19:51 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-02 19:51 grow -> /dev/block/mmcblk0p56
lrwxrwxrwx root root 2015-01-02 19:51 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-02 19:51 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-02 19:51 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-02 19:51 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-02 19:51 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-02 19:51 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-02 19:51 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-02 19:51 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-02 19:51 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-02 19:51 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-02 19:51 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-02 19:51 operatorlogging -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-01-02 19:51 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-02 19:51 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-02 19:51 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-02 19:51 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-02 19:51 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-02 19:51 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-01-02 19:51 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-02 19:51 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-02 19:51 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-02 19:51 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-02 19:51 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-02 19:51 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-02 19:51 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-02 19:51 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-02 19:51 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-02 19:51 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-02 19:51 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-02 19:51 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-02 19:51 spare3 -> /dev/block/mmcblk0p50
lrwxrwxrwx root root 2015-01-02 19:51 spare4 -> /dev/block/mmcblk0p52
lrwxrwxrwx root root 2015-01-02 19:51 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-02 19:51 system -> /dev/block/mmcblk0p53
lrwxrwxrwx root root 2015-01-02 19:51 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-02 19:51 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-02 19:51 userdata -> /dev/block/mmcblk0p55
Thx. System dump possible?
Please, adb pull /system.
What are the partitions spare1-4 used for? I've pulled mine using dd, but they appear to be completely empty.
can fix boot loop?
How can i use this to fix my boot loop g4?
I'm trying to create a partition dump, specifically to have a backup of my efs partition. My first 6p had it's efs partition corrupted (while stock, unrooted, locked bl). I've got my new 6p in hand, bl unlocked, twrp installed, and chainfires systemless root up and running. I was trying to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2450045
but i cannot access / using any file explorer. The SU prompt never appears. I tried running cat /proc/emmc, and that was a no go as well. I was able to get the partition list, but only in mmcblkxxxx format. I would like the names, so that i can properly organize the dump. If anybody could point me in the right direction, that'd be awesome! Thanks in advance.
Never mind, I've found it. For other's reference, the correct path is:
/dev/block/platform/soc.0/f9824900.sdhci/by-name.
Hope this helps someone in the future
beats4x said:
Never mind, I've found it. For other's reference, the correct path is:
/dev/block/platform/soc.0/f9824900.sdhci/by-name.
Hope this helps someone in the future
Click to expand...
Click to collapse
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?
makers_mark said:
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?
Click to expand...
Click to collapse
Will have to be when I get home from work, but yeah I definitely can
Sent from my Nexus 6P using Tapatalk
makers_mark said:
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?
Click to expand...
Click to collapse
Here you go bro. Sprry for the delay. Been a crazy couple of days at work.
[email protected]:/ # ls -al /dev/block/platform/soc.0/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-26 16:23 DDR -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-26 16:23 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-26 16:23 abootbak -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-26 16:23 apdp -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-26 16:23 boot -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-26 16:23 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-26 16:23 cmnlib -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-26 16:23 cmnlibbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-26 16:23 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-26 16:23 dpo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-26 16:23 frp -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-26 16:23 fsc -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-26 16:23 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-26 16:23 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-26 16:23 hypbak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-26 16:23 keymaster -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-26 16:23 keymasterbak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-26 16:23 keystore -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-26 16:23 limits -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-26 16:23 metadata -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-26 16:23 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-26 16:23 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-26 16:23 modemst1 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-26 16:23 modemst2 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-26 16:23 msadp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-26 16:23 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-26 16:23 oeminfo -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-26 16:23 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-26 16:23 persistent -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-26 16:23 pmic -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-26 16:23 pmicbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-26 16:23 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-26 16:23 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-26 16:23 rpmbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-26 16:23 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-26 16:23 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-26 16:23 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-26 16:23 sec -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-26 16:23 ssd -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-26 16:23 system -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-26 16:23 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-26 16:23 tzbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-26 16:23 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-26 16:23 vendor -> /dev/block/mmcblk0p37
beats4x said:
...
Click to expand...
Click to collapse
I've been looking since they released the images, I think you may of been the first to post it anywhere that I have access to, thanks!!:good:
makers_mark said:
I've been looking since they released the images, I think you may of been the first to post it anywhere that I have access to, thanks!!:good:
Click to expand...
Click to collapse
No problem, glad I could assist!
Sent from my Nexus 6P using Tapatalk
Hey guys, so recently I've been trying to extract the stock Android 7.1.1 firmware from my AT&T Tab E so that I can package it into a flashable .tar.md5 file for Odin.
So far this is what I have:
First I typed this into the Terminal Emulator app on the tablet:
Code:
ls -al /dev/block/platform/13540000.dwmmc0/by-name
And it spit this out:
Code:
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 TDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-06-02 00:30 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2018-06-02 00:30 m9kefs3 -> /dev/block/mmcblk0p7
This information lets us know which partition file in /dev/block is for the boot, system, recovery etc.
But when I try using this command to dump any of the files into my internal SD card:
Code:
dd if=/dev/block/mmcblk0pXX of=/sdcard/XXXXXXXX.img bs=4096
or external SD card:
Code:
dd if=/dev/block/mmcblk0pXX of=/storage/C35A-1CE6/XXXXXXXX.img bs=4096
It keeps on spitting out "Permission denied" and it doesn't do anything.
Correct me if I'm wrong, but I think it has something to do with me not having root access on my Tab E :/
Anyways, if somebody can help me with this it would be awesome!
Hello, I was trying to dump my MCU partition into img file. That way I could try to reflash it back within the update mcu settings on device. My goal was to flash it with the dmcu.ext file that controls the resolution. I read I am supposed to flash MCU with text file dmcu.ext "screen:1" in the root of where the mcu image is. When I flash the entire image it does not seem to work, thought it could be because firmware is in one large bin file that contains all of the images like system and boot. I dumped the tee1 and tee2 to image file, would that be mcu? My resolution is showing 1024x600, instead of 800x480.
no matter what mcu img I attempt to update, MCU update says failed to update file. I was reading about mismatch, but don't see that error.
If I am not on the right track here, please correct me.
FF-5000:/ # ls -al /dev/block/platform/soc/11230000.mmc/by-name
total 0
drwxr-xr-x 2 root root 560 2010-01-01 00:01 .
drwxr-xr-x 4 root root 680 2010-01-01 00:01 ..
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 ANDROID -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 ARM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 BOOTIMG -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 CACHE -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 DKB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 EXPDB -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 FRP -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 KB -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 LK -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 LOGO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 METAZONE -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 MISC -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 NVRAM -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 ODMDTBO -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PROTECT_F -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PROTECT_S -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PRO_INFO -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 SECCFG -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 SEC_RO -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 TEE1 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 TEE2 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 VENDOR -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 forfanzone -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 tszone -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 userdata -> /dev/block/mmcblk0p26