I found a Tmo GS8 with exploded battery in the trash, and when I replaced the battery and booted it up, realized it had an old eng build on it. Would anyone be interested in looking into whether this could be flashed to retail Tmo GS8s in order to unlock them for custom ROMs?
I'm currently uploading to AFH: https://www.androidfilehost.com/?w=files&flid=325176
Just be aware that while the 7z download is only 4.3GB, it extracts to the full 64GB flash.
This is meant for developers, NOT for users!
Spoiler: mount output
Code:
rootfs on / type rootfs (ro,seclabel,size=1628820k,nr_inodes=407205)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1699556k,nr_inodes=424889,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /dev/stune type cgroup (rw,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1699556k,nr_inodes=424889,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,size=1699556k,nr_inodes=424889,mode=700)
tmpfs on /mnt/secure/asec type tmpfs (rw,seclabel,relatime,size=1699556k,nr_inodes=424889,mode=700)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/sda19 on /system type ext4 (ro,seclabel,relatime)
/dev/block/sda20 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sda5 on /persist type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sdd7 on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/sda6 on /efs type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sda15 on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sda16 on /firmware-modem type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sda21 on /carrier type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc)
/dev/block/sda22 on /omr type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1699556k,nr_inodes=424889,mode=755,gid=1000)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/sda19 on /system/carrier type ext4 (ro,seclabel,relatime)
/dev/block/dm-0 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/data/knox/tmp_sdcard on /mnt/knox type sdcardfs (rw,nosuid,nodev,relatime,mask=0077)
/data/knox/sdcard on /mnt/knox/default/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=1015,multi_user,mask=0006)
/data/knox/sdcard on /mnt/knox/read/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,mask=0027)
/data/knox/sdcard on /mnt/knox/write/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,mask=0007)
/data/knox/secure_fs/enc_media on /mnt/shell/enc_media type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,reserved=20MB)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,multi_user,mask=0006,reserved=20MB)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,multi_user,mask=0006,reserved=20MB)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,multi_user,mask=0027,reserved=20MB)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,multi_user,mask=0007,reserved=20MB)
/data/knox/secure_fs/enc_user on /data/enc_user type ecryptfs (rw,seclabel,nodev,relatime,ecryptfs_fnek_sig=30cbf87c57ba04e7,ecryptfs_sig=30cbf87c57ba04e7,userid=0,sdp_enabled,partition_id=0,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_enable_cc,ecryptfs_passthrough,base=,label=)
/mnt/shell/enc_media on /mnt/shell/enc_emulated type ecryptfs (rw,seclabel,nodev,relatime,ecryptfs_fnek_sig=30cbf87c57ba04e7,ecryptfs_sig=30cbf87c57ba04e7,userid=0,sdp_enabled,partition_id=1,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_enable_cc,ecryptfs_passthrough,base=,label=)
/dev/block/vold/public:179,1 on /mnt/media_rw/0000-0000 type sdfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,utf8,namecase=0,adj_req,symlink=0,bps=512,errors=remount-ro)
/dev/block/vold/public:179,1 on /mnt/secure/asec type sdfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,utf8,namecase=0,adj_req,symlink=0,bps=512,errors=remount-ro)
/mnt/media_rw/0000-0000 on /mnt/runtime/default/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,mask=0006)
/mnt/media_rw/0000-0000 on /storage/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,mask=0006)
/mnt/media_rw/0000-0000 on /mnt/runtime/read/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,mask=0022)
/mnt/media_rw/0000-0000 on /mnt/runtime/write/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,mask=0022)
Spoiler: partitions
Code:
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
253 0 2097152 vnswap0
8 16 4096 sdb
8 17 3940 sdb1
8 0 62418944 sda
8 1 2048 sda1
8 2 2048 sda2
8 3 4 sda3
8 4 8 sda4
8 5 32768 sda5
8 6 20480 sda6
8 7 10240 sda7
8 8 1024 sda8
8 9 512 sda9
8 10 30720 sda10
8 11 21504 sda11
8 12 512 sda12
8 13 4096 sda13
8 14 16384 sda14
8 15 97280 sda15
259 0 87040 sda16
259 1 65536 sda17
259 2 65536 sda18
259 4 4812800 sda19
259 6 614400 sda20
259 8 46080 sda21
259 10 10240 sda22
259 12 6144 sda23
259 14 10240 sda24
259 16 56460112 sda25
8 48 61440 sdd
8 49 512 sdd1
8 50 2048 sdd2
8 51 512 sdd3
8 52 2048 sdd4
8 53 16 sdd5
8 54 512 sdd6
8 55 16384 sdd7
8 56 20480 sdd8
8 57 4 sdd9
8 58 1024 sdd10
8 59 384 sdd11
8 60 512 sdd12
8 61 512 sdd13
8 62 512 sdd14
8 63 256 sdd15
259 3 256 sdd16
259 5 4 sdd17
259 7 4 sdd18
259 9 128 sdd19
259 11 512 sdd20
259 13 1024 sdd21
259 15 13640 sdd22
8 32 4096 sdc
8 33 3940 sdc1
254 0 56460096 dm-0
179 0 125042688 mmcblk0
179 1 125026304 mmcblk0p1
boot screen
download screen
Yeah, ENG kernel's usually are open to ADB at recovery, making it easy to unlock, wipe FRP and put on a custom rom. I have two Tmo S8's here and I just fixed one, I'll report back about your kernel.... Thanks
AND BTW, thats a trip, both of the one's I have say fuse blown like that, I guess that from the battery's blowing up, but out of the two I managed to piece together a beautiful one.. Anyhow, I'll report back after flashing. I'm gonna slap lineage 19.1 on there. Even if your kernel doesn't work, which I'm sure it will, there's a full setup of eng boot, root, and modified odin @ https://forum.xda-developers.com/t/eng-boot-root.3608353/ that we can both use if this one is no good.
Related
Hi can anyone dump the recovery.img off thier galaxy s3mini. Im going to try and make a cwm but need this .img. i think its easier for people that a rooted there phones. Thanks in advance
Sent from my GT-I9300 using xda premium
you can get it sinply by extract recovery.img from the firmware.
avicohh said:
you can get it sinply by extract recovery.img from the firmware.
Click to expand...
Click to collapse
Its not in the firmware unfortunately
Sent from my GT-I9300 using xda premium
No it isn't. I already tried and failed.
Maybe we can extract it through ADB SHELL.
Currently i get:
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
none /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /modemfs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p23 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p24 /preload ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p19 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
But which one is the recovery ???
Try modem.
quendil said:
Maybe we can extract it through ADB SHELL.
Currently i get:
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
none /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /modemfs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p23 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p24 /preload ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p19 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
But which one is the recovery ???
Click to expand...
Click to collapse
Lol i dont have a clue. Could you try downloading this tool http://forum.xda-developers.com/showthread.php?t=1703488 its for normal galaxy s3. When installed click any firmware version and then select option to make nandroid backup through adb to computer. You need to have root to do it. Thanks again
Sent from my GT-I9300 using xda premium
I don't think recovery partition is mounted in normal boot. Try adb in recovery mode?
Skickat från min GT-P7500 via Tapatalk 2
---------- Post added at 01:30 PM ---------- Previous post was at 12:50 PM ----------
In terminal, cat /proc/partition gives me:
$ export PATH=/data/local/bin:$PATH
$ su
# cat /proc/partitions
major minor #blocks name
7 0 14585 loop0
7 1 2111 loop1
7 2 4190 loop2
7 3 5229 loop3
7 4 47849 loop4
7 5 2111 loop5
7 6 4190 loop6
7 7 13545 loop7
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 32113664 mmcblk1
179 97 16056320 mmcblk1p1
179 98 16048128 mmcblk1p2
254 0 14584 dm-0
254 1 2110 dm-1
254 2 4189 dm-2
254 3 5229 dm-3
254 4 47848 dm-4
254 5 2110 dm-5
254 6 4189 dm-6
254 7 13545 dm-7
7 8 21861 loop8
254 8 21861 dm-8
7 9 29138 loop9
254 9 29137 dm-9
7 10 13545 loop10
254 10 13545 dm-10
7 11 2111 loop11
254 11 2110 dm-11
7 12 5229 loop12
254 12 5229 dm-12
7 13 55125 loop13
254 13 55125 dm-13
7 14 2111 loop14
254 14 2110 dm-14
7 15 15624 loop15
254 15 15624 dm-15
#
Skickat från min GT-I8190
ops.. i forgot something.
the recovery built in the kernal, its more complicated then S3.
C:\Android>adb reboot recovery
C:\Android>adb shell
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p1 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
$
This is what I get in recovery mode. Hope it helps
Edit: Or not, damn it!
avicohh said:
ops.. i forgot something.
the recovery built in the kernal, its more complicated then S3.
Click to expand...
Click to collapse
Why do they have to make things so confusing. I dont think im able to do it now
Sent from my GT-I9300 using xda premium
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Benzonat0r said:
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Click to expand...
Click to collapse
Oh, damn! We need someone like chainfire to get this device goin' custom!
Skickat från min GT-P7500 via Tapatalk 2
Benzonat0r said:
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Click to expand...
Click to collapse
Can you extract that recovery.img i will then try and add cwm to it. What operating system are yiu using to unpack boot.img?
Sent from my GT-I9300 using xda premium
Windows 7 emulating Linux via Cygwin + dsixda's Android Kitchen
This it an extracted boot.img, the recovery is in here.
Benzonat0r said:
Windows 7 emulating Linux via Cygwin + dsixda's Android Kitchen
This it an extracted boot.img, the recovery is in here.
Click to expand...
Click to collapse
Ahh yeah ive dont that but there is no recovery.img in there
Sent from my GT-I9300 using xda premium
There's no image in there no, but I think it's integrated in it, just like in Galaxy Ace 2 there's no recovery.img in the stock firmware but the recovery its packed directly in kernel.bin
Benzonat0r said:
There's no image in there no, but I think it's integrated in it, just like in Galaxy Ace 2 there's no recovery.img in the stock firmware but the recovery its packed directly in kernel.bin
Click to expand...
Click to collapse
Yeah thats what i thought. Looks like im going to have to set up ubuntu to create it. Not many tools made for windows. Hopefully can get it set up in the next week. Dont hold me to it though as ive never done anything like this before. I usually do theming over at the galaxy s3 intetnational forum. Only problem is people are going to have to try it out for me if i can get it together as my girlfriend has the s3mini and doesnt like me doing thing to her phone.
Sent from my GT-I9300 using xda premium
Hahahaha that's totally understandable man girls are like that don't sweat it. We'd appreciate that very much.
Thing is that I don't have a spare hard drive to install Ubuntu and my disk space is nearly full, around 8 gigs free of 2TB of space.
hey i build a cwm version on koushik-lion for Galaxy S3 mini (alias Golden) ... its cwm recovery 6.0.2.7 Touch recovery.img - 6.10 MB but i don´t know how i can test it..... because its my first samsung device and I don´t want to brick it .... can i try "fastboot flash recovery recovery.img" or .... I hope someone knows a way ...
ps: link to recovery-builder: http://jenkins.cyanogenmod.com/job/recovery/14184/
Could somebody please provide the following (yes, searched here and google - no luck):
Partitions
Code:
# cat /proc/partitions
and
Mounted partitions
Code:
# mount
Could please somebody post their results from (preferable stock 2.3.6 and rooted) device here.
Thank you!
Solved my issue I was having, managed to get it, in case anybody else may need it:
Code:
# cat /proc/partitions
major minor #blocks name
137 0 513024 bml0/c
137 1 256 bml1
137 2 2048 bml2
137 3 2048 bml3
137 4 256 bml4
137 5 12800 bml5
137 6 5120 bml6
137 7 5120 bml7
137 8 5120 bml8
137 9 235520 bml9
137 10 40960 bml10
137 11 201984 bml11
137 12 256 bml12
137 13 256 bml13
137 14 256 bml14
137 15 1024 bml15
138 6 1280 stl6
138 9 227840 stl9
138 10 36864 stl10
138 11 194816 stl11
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl10 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/stl11 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
Straight Into the Topic.
This is based on Omni 6.0 Sources. My OWN FORK/REPO
Please Test, If woking/no please comment in comment section
Downloads:
twrp-3.0.2-1-oneplus3.img
twrp-3.0.2-0-oneplus3.img
Hope You Will Test It!
Source: https://github.com/HostZero/android_device_oneplus_oneplus3/tree/android-6.0
XDA:DevDB Information
[TWRP][ONEPLUS3][TESTING] TWRP 3.0.2-1 | Testing | Help of OP3 Users Required, Tool/Utility for the OnePlus 3
Contributors
HostZero
Version Information
Status: Testing
Created 2016-06-16
Last Updated 2016-06-19
HostZero said:
Straight Into the Topic.
This is based on Omni 6.0 Sources. My OWN FORK/REPO
Please Test, If woking/no please comment in comment section
Downloads:
twrp-3.0.2-0-oneplus3.img
Hope You Will Test It!
Source: https://github.com/HostZero/android_device_oneplus_oneplus3/tree/android-6.0
XDA:DevDB Information
[TWRP][ONEPLUS3][TESTING] TWRP 3.0.2-0 | Testing | Help of OP3 Users Required, Tool/Utility for the OnePlus 3
Contributors
HostZero
Version Information
Status: Testing
Created 2016-06-16
Last Updated 2016-06-16
Click to expand...
Click to collapse
How is this different from the one made by Grarak?
CircuitBug said:
How is this different from the one made by Grarak?
Click to expand...
Click to collapse
Sir, I don't even know the Grarak, made a TWRP. I am here to make official twrp for OP3 , so if booting and other features are fine. I will talk to my superiors to make it OFFICIAL. I hope you will test Recovery Now.
- HostZero
HostZero said:
Sir, I don't even know the Grarak, made a TWRP. I am here to make official twrp for OP3 , so if booting and other features are fine. I will talk to my superiors to make it OFFICIAL. I hope you will test Recovery Now.
- HostZero
Click to expand...
Click to collapse
My phone will arrive today, and I'll gladly test this for you. Any specific checks you need to be carried out?
CircuitBug said:
My phone will arrive today, and I'll gladly test this for you. Any specific checks you need to be carried out?
Click to expand...
Click to collapse
Thabkyou for the positive and quick replies.
I need Backup/Restore, CPU Temp.
And Major, Is it booting?
That's it sir.
- HostZero
I used your toolkit and everything worked well. I'm rooted and running Xposed on my OP3.
My device tree already has TWRP flags inside with decryption working.
And as an addition, Dees Troy will prolly be merging Grarak's sources for Official TWRP. He has tested everything on his phone himself, so
Sent from my OnePlus2 using XDA Labs
both storages in TWRP recovery shows 0 MB, any helps? thanks.
Naman Bhalla said:
And as an addition, Dees Troy will prolly be merging Grarak's sources for Official TWRP. He has tested everything on his phone himself, so
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
So its best that I forget TWRP for OnePlus3.
works very well thank you to you
backup not working
Installed there is not
HostZero said:
So its best that I forget TWRP for OnePlus3.
Click to expand...
Click to collapse
LoL
I should get my phone today. Still need more tests?
Is encryption supported already?
Gesendet von meinem OnePlus One
jejemc said:
works very well thank you to you
backup not working
Installed there is not
Click to expand...
Click to collapse
I found the bug, but has raised because of partition details I have provided. Please provide me new block/partition details so I can fix backup install etc issues.
Could I use it with oxygen?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
HostZero said:
I found the bug, but has raised because of partition details I have provided. Please provide me new block/partition details so I can fix backup install etc issues.
Click to expand...
Click to collapse
Hello what file? I do not see or take it thank you
Hi, Flashed it and its running.
There is a mouse cursor in the middle of the screen.
Backup is not working as I cant select any location where to backup too.
Edit. It seems that I can't mount the data partition to flash supersu.zip
Signor Rossi said:
Hi, Flashed it and its running.
There is a mouse cursor in the middle of the screen.
Backup is not working as I cant select any location where to backup too.
Edit. It seems that I can't mount the data partition to flash supersu.zip
Click to expand...
Click to collapse
Please your a senior member so you ksut be know about block details please provide me your device block info.
HostZero said:
Please your a senior member so you ksut be know about block details please provide me your device block info.
Click to expand...
Click to collapse
Not 100% sure if this is what you are looking for ?
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
7 0 32768 loop0
8 0 56582144 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 10240 sda9
8 10 10240 sda10
8 11 1024 sda11
8 12 8096 sda12
8 13 16192 sda13
8 14 512 sda14
8 15 56238572 sda15
8 16 4096 sdb
8 17 4052 sdb1
8 32 4096 sdc
8 33 4052 sdc1
8 80 1572864 sdf
8 81 2048 sdf1
8 82 2048 sdf2
8 83 4 sdf3
8 84 512 sdf4
8 64 4194304 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 16 sde8
8 73 512 sde9
8 74 512 sde10
8 75 97280 sde11
8 76 16384 sde12
8 77 1024 sde13
8 78 32768 sde14
8 79 8192 sde15
259 0 8192 sde16
259 1 16384 sde17
259 2 65536 sde18
259 3 65536 sde19
259 4 3080192 sde20
259 5 65536 sde21
259 6 4 sde22
259 7 1024 sde23
259 8 512 sde24
259 9 512 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 256 sde31
259 16 4 sde32
259 17 33424 sde33
259 18 2048 sde34
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
254 0 56238556 dm-0
[email protected]:/ $
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,seclabel,size=2846160k,nr_inodes=711540 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=2921120k,nr_inodes=730280,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=2921120k,nr_inodes=730280,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=2921120k,nr_inodes=730280,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,noatime,discard,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/bluetooth /bt_firmware vfat ro,context=u:object_r:bt_firmware_file:s0,relatime,uid=1002,gid=3002,fmask=0333,dmask=0222,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=2921120k,nr_inodes=730280,mode=755,gid=1000 0 0
/dev/block/dm-0 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,reserved_mem=50MB 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,reserved_mem=50MB 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,reserved_mem=50MB 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,reserved_mem=50MB 0 0
[email protected]:/ $
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/ 2.7G 4.8M 2.7G 4096
/dev 2.8G 124.0K 2.8G 4096
/sys/fs/cgroup 2.8G 12.0K 2.8G 4096
/mnt 2.8G 0.0K 2.8G 4096
/mnt/runtime/default/emulated 52.6G 22.8G 29.8G 4096
/mnt/runtime/read/emulated 52.6G 22.8G 29.8G 4096
/mnt/runtime/write/emulated 52.6G 22.8G 29.8G 4096
/system 2.8G 2.4G 417.4M 4096
/cache 248.0M 1.1M 246.9M 4096
/persist 27.5M 420.0K 27.1M 4096
/dsp 11.7M 4.1M 7.6M 4096
/firmware 95.0M 81.2M 13.8M 16384
/bt_firmware 1023.7M 112.0K 1023.6M 16384
/storage 2.8G 0.0K 2.8G 4096
/storage/emulated 52.6G 22.8G 29.8G 4096
/data 52.7G 22.8G 29.9G 4096
/su 27.5M 1004.0K 26.5M 4096
[email protected]:/ #
Delete
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
Grarak said:
My device tree already has TWRP flags inside with decryption working.
Click to expand...
Click to collapse
Garak, I installed your recovery and was able to back up successfully.
No problems so far.
Thanks!
phonepersonality said:
Delete
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
Garak, I installed your recovery and was able to back up successfully.
No problems so far.
Thanks!
Click to expand...
Click to collapse
You are in the wrong thread dude
Gesendet von meinem OnePlus One
Hi
To cut a long story short I went about trying to extend my system partition using GNU Parted and it has failed terribly to the point I have bricked my tablet. At the moment I have managed to execute the command
Code:
fastboot boot twrp-3.2.3-0-flo.img
but this is running from RAM as I'm unable to flash any of the partitions as they are "missing".
This is the my original partition table:-
Code:
Number Start End Size File system Name Flags
1 67108864B 156745727B 89636864B fat16 radio
2 201326592B 204472319B 3145728B modemst1
3 204472320B 207618047B 3145728B modemst2
4 268435456B 283795455B 15360000B ext4 persist
5 335544320B 336343039B 798720B m9kefs1
6 336343040B 337141759B 798720B m9kefs2
7 402653184B 403451903B 798720B m9kefs3
8 403451904B 406597631B 3145728B fsg
9 469762048B 471298047B 1536000B sbl1
10 471298048B 472834047B 1536000B sbl2
11 472834048B 474931199B 2097152B sbl3
12 474931200B 480174079B 5242880B aboot
13 480174080B 480698367B 524288B rpm
14 536870912B 553648127B 16777216B boot
15 603979776B 604504063B 524288B tz
16 604504064B 604505087B 1024B pad
17 604505088B 606041087B 1536000B sbl2b
18 606041088B 608138239B 2097152B sbl3b
19 608138240B 613381119B 5242880B abootb
20 613381120B 613905407B 524288B rpmb
21 613905408B 614429695B 524288B tzb
22 671088640B 1551892479B 880803840B ext2 system
23 1551892480B 2139095039B 587202560B ext4 cache
24 2147483648B 2148532223B 1048576B misc
25 2214592512B 2225078271B 10485760B recovery
26 2281701376B 2281709567B 8192B DDR
27 2281709568B 2281717759B 8192B ssd
28 2281717760B 2281718783B 1024B m9kefsc
29 2348810240B 2348843007B 32768B metadata
30 2415919104B 15468576255B 13052657152B ext4 userdata
From some reading on the internet Linux can only have 4 primary partitons. All I know is that I have 30 partitions and I don't know what partition type to set them to; primary, logical and extended.
I've played around with the three partition types but I get an error message saying "Too many primary partitions".
Could someone shine some light here please?
Many thanks
Will
Bump
Bump
Don't know if it helps, but here is some partition info from stock flo:
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 13029359 mmcblk0p30
127|[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 903.9M 76.0K 903.8M 4096
/sys/fs/cgroup 903.9M 12.0K 903.9M 4096
/mnt 903.9M 0.0K 903.9M 4096
/system 827.8M 823.8M 4.0M 4096
/cache 551.7M 10.6M 541.2M 4096
/data 12.2G 5.1G 7.1G 4096
/persist 14.5M 4.2M 10.2M 4096
/storage 903.9M 0.0K 903.9M 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 12.2G 5.1G 7.1G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
1|[email protected]:/ $ mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
This is my first foray into Wear OS. I seem to always end up with some locked down devices. It Always teaches me a thing or two though! Because all is not lost it seems. I've been trying to compile what I can see from the device into one spot. Information on this series of watches is spread out all over the place. Let me explain what I've found out about The MK Access Bradshaw, that makes me think there is a light at the end of the tunnel. If you have experience with these watches or the Fossil Q sister series, please share. Links to the Fossil Q firmware would be amazing at this point.
Code:
----------------------------------------------
Michael Kors Access Bradshaw Device Info
----------------------------------------------
MODEL: MKT5006
CHIPSET: SD Wear 2100
RAM: 512 MB
STORAGE: 4 GB
SCREEN: 1.4 inch
RESOLUTION: 320x290 pixels (309 ppi)
WEAR OS: 2.6
BUILD: fossil/gar/gar
8.0.0/OWD6.180205.022/53356216
user/release-keys
----------------------------------------------
1. FASTBOOT MODE
[adb reboot bootloader]
----------------------------------------------
PRODUCT_NAME - gar
VARIANT - PFW2
PHASE - SA
BOOTLOADER VERSION - GAR.EINSTEIN_0.083.00
BASEBAND VERSION - N/A
HW_CONFIG - 1
SERIAL NUMBER - XXXXXXXXX (9 Digits)
** A Direct Pin Connection is Needed
to utilize the Fastboot Protocol.
** Fastboot appears active and functional
and only missing a physical connection
** A Pin Connection can be made.
Now, when we finally make it into the recovery mode, we are presented with standard Android Oreo Recovery options. Including the Recovery Logs. It is in these logs I have found A LOT of Information. They have the Log Daemon configured to 'eng'. But I noticed that simply using the 'adb reboot recovery' command, would start recovery mode but never show the recovery menu before rebooting back to the system.
The recovery menu only ever appears for me when I boot into recovery mode from fastboot mode.
Code:
----------------------------------------------
2. RECOVERY MODE
[Boot to Recovery from Bootloader]
----------------------------------------------
* The Recovery Log displays the Recovery FSTAB
* Build.Prop Contents Can also been seen.
* ro.logd.kernel=eng
It is very verbose. But without actual access to the cache partition there is no way to copy & paste, or pull the logs from the watch. My "last_log" entry is from when I updated the device from WearOS 2.2 to version 2.6. In that log, so much of the nitty gritty partition details are revealed, here are a few I've wrote down so far:
Code:
/cache/recovery/last_log:
-----------------------------
0 /system ext4 /dev/block/platform/soc/7824900.sdhci/by-name/system 0
1 /cache ext4 /dev/block/platform/soc/7824900.sdhci/by-name/cache 0
2 /data ext4 /dev/block/platform/soc/7824900.sdhci/by-name/userdata -16384
3 /sdcard vfat /dev/block/mmcblk1p1 0
4 /boot emmc /dev/block/platform/soc/7824900.sdhci/by-name/boot 0
5 /recovery emmc /dev/block/platform/soc/7824900.sdhci/by-name/recovery 0
6 /misc emmc /dev/block/platform/soc/7824900.sdhci/by-name/misc 0
7 /oem ext4 /dev/block/platform/soc/7824900.sdhci/by-name/oem 0
8 /tmp ramdisk ramdisk 0
ro.sys.fw.use_trim_settings=true
ro.sys.fw.trim_enable_memory=1073741824
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.empty_app_percent=50
ro.sys.umsdirtyratio=20
ro.boot.hardware=gar
ro.boot.baseband=apq
ro.boot.console=null
ro.boot.ceibootmode=0
ro.boot.bootdevice=7824900.sdhci
ro.board.platform=msm8909
ro.build.host=abfarm648
ro.product.cpu.abi=armeabi-v7a
ro.boot.verifiedbootstate=green
ro.boot.authorized_kernel=true
ro.logd.kernel=eng
ro.bootimage.build.date=Thu Aug 9 00:39:05 UTC 2018
[11.364486]Verifying update package...
I:comment is 1476 bytes; signature is 1458 bytes from end.
I:signature (offset: 10127db, length: 5ac):
That log continues on with all of the signature, but on the watch screen it is quite a few pages long. But continues on during the whole verification process. And it really does say in so many words what it is doing and when. The log explains exactly what data it is putting where, and where the developers forgot to set expected values that the system must choose a default for.
What I need to do now is go through the log with an OCR App that can take pictures of the screen and extract the text. I believe the two most recent log files on my watch could explain just how to get at the bootloader & kernel. They definitely tell you where to go find the eFuse. Because even though it has Green Verified Boot Status, the boot log shows a few things for verified boot were never actually implemented. I'm working on getting these logs now.
Enable Developer Options:
Settings > System > About > Tap Build Number until it unlocks.
Connecting to ADB:
1.) Enable Developer Options
2.) Disable Bluetooth
3.) Connect Device to Wi-Fi
4.) Settings > Dev Options > ADB Debugging
5.) Settings > Dev Options > Debug Over Wi-Fi
6.) From a command line, start the adb server and then use this command with the watch's wifi ip address: "adb connect <ip_address>:5555"
7.) Run command "adb devices" and hit the yes button on the watch face to accept the connection.
Replacement 1st Gen Fossil Watch Chargers (2016-2017 Watches):
1.) 1st Party Marc Jacob's MJT0001/MKT0001
2.) 3rd Party Soarking Fossil Charger
Once I find a repair manual or schematic to this thing, I think I'm going to work on creating a cable to connect to the board for fastboot access.
MEMINFO
Code:
MemTotal: 455000 kB
MemFree: 8228 kB
MemAvailable: 179528 kB
Buffers: 2216 kB
Cached: 179400 kB
SwapCached: 7136 kB
Active: 153580 kB
Inactive: 154504 kB
Active(anon): 63348 kB
Inactive(anon): 64340 kB
Active(file): 90232 kB
Inactive(file): 90164 kB
Unevictable: 256 kB
Mlocked: 256 kB
SwapTotal: 338936 kB
SwapFree: 222520 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 125548 kB
Mapped: 78400 kB
Shmem: 1216 kB
Slab: 41732 kB
SReclaimable: 13440 kB
SUnreclaim: 28292 kB
KernelStack: 8544 kB
PageTables: 20392 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 566436 kB
Committed_AS: 26409868 kB
VmallocTotal: 499712 kB
VmallocUsed: 95544 kB
VmallocChunk: 291668 kB
MOUNTS
Code:
rootfs / rootfs ro,seclabel,size=205932k,nr_inodes=51483 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=221356k,nr_inodes=55339,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
none /config configfs rw,relatime 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,discard 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/oem /oem ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
PARTITIONS
Code:
major - minor - #blocks name
-------------------------------------
254 - 0 - 262144 zram0
179 - 0 - 3817472 mmcblk0
179 - 1 - 65536 mmcblk0p1
179 - 2 - 512 mmcblk0p2
179 - 3 - 512 mmcblk0p3
179 - 4 - 512 mmcblk0p4
179 - 5 - 512 mmcblk0p5
179 - 6 - 768 mmcblk0p6
179 - 7 - 768 mmcblk0p7
179 - 8 - 1024 mmcblk0p8
179 - 9 - 1536 mmcblk0p9
179 - 10 - 1536 mmcblk0p10
179 - 11 - 1536 mmcblk0p11
179 - 12 - 1 mmcblk0p12
179 - 13 - 1024 mmcblk0p13
179 - 14 - 8 mmcblk0p14
179 - 15 - 10240 mmcblk0p15
179 - 16 - 32 mmcblk0p16
179 - 17 - 16 mmcblk0p17
179 - 18 - 32768 mmcblk0p18
179 - 19 - 32768 mmcblk0p19
179 - 20 - 512 mmcblk0p20
179 - 21 - 1024 mmcblk0p21
179 - 22 - 1024 mmcblk0p22
179 - 23 - 32768 mmcblk0p23
179 - 24 - 32768 mmcblk0p24
179 - 25 - 1024 mmcblk0p25
179 - 26 - 512 mmcblk0p26
179 - 27 - 512 mmcblk0p27
179 - 28 - 16384 mmcblk0p28
179 - 29 - 256 mmcblk0p29
179 - 30 - 256 mmcblk0p30
179 - 31 - 256 mmcblk0p31
259 - 0 - 256 mmcblk0p32
259 - 1 - 65536 mmcblk0p33
259 - 2 - 655360 mmcblk0p34
259 - 3 - 2310127 mmcblk0p35
179 - 32 - 4096 mmcblk0rpmb
DF Utility
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
---------------------------------------------------------------------------
rootfs 205932 3460 202472 2% /
tmpfs 221356 532 220824 1% /dev
tmpfs 221356 0 221356 0% /mnt
/dev/block/mmcblk0p34 645056 630224 0 100% /system
/dev/block/mmcblk0p33 60400 1632 57460 3% /cache
/dev/block/mmcblk0p1 65488 22240 43248 34% /firmware
/dev/block/mmcblk0p28 12016 64 11628 1% /oem
/dev/block/mmcblk0p35 2237680 690400 1530896 32% /data
/data/media 2237680 690400 1530896 32% /storage/emulated
Since making this thread, this update no longer seems to be available. I think I am also leaving XDA, my words here have caused me too much trouble.