Database Users

[DEV][R&D] FW & Partition Tables (Here!)

I'm working on a project doing Firmware/Bootloader analysis and documentation.
This will eventually be crucially important in providing service, repair and
unbricking of these device. And if you think that these will not soft-brick,
just remember that the OS have "Windows" in it's name...
However, this project requires detailed knowledge of the following two components:
Bootloader & Firmware files
Partition Table
To make things more simple for this project, I have chosen to only focus on devices using the Qualcomm
Snapdragon S4 Plus/Pro processors, these are also known as the MSM8960, MSM8960T and MSM8930.
So if you have any of the devices shown in the list below, please try to extract and post these details,
when and if they become available. (I recommend using Sendspace to upload large files.)
Code:
[SIZE=2]HTC Windows Phone 8X LTE ADR6990 Verizon
HTC Windows Phone 8X LTE
Nokia Lumia 820 (Nokia Arrow)
Nokia Lumia 820.2 (Nokia Arrow)
Nokia Lumia 822 (Nokia Atlas) Verizon
Nokia Lumia 920 (Nokia Phi)
Nokia Lumia 920.2 (Nokia Phi)
Samsung GT-i8750 Ativ S 16GB (Samsung Odyssey)
Samsung GT-i8750 Ativ S 32GB (Samsung Odyssey)[/SIZE]
[Obtained from the PDAdb web site.]
This list is in no way exhaustive, and it may be very likely that you have another device or still using
Windows Phone 7 (?) with that same processor. That would also be interesting. Another thing that may
be very useful, is documentation related to the Windows Phone build structure.
The results of this project will be published here and will benefit the development community
in several different ways.
Please do not post any general unrelated questions here, they will be removed.
And I will not answer to any support related PM's.
Thanks in advance.

< Here Be Snap ! Dragons >

Good start .. E.V.A have u trued to contact Cotulla on htc-linux or DFT team. They might have something that might interest you . I'll post once i grab my hands on them.
Sent from my GT-I9300 using xda premium

If someone has a working Windows Phone 8, and if at all possible, please follow these instructions to dump the partition tables. As you're on a windows phone, you may need to connect it to a linux based PC, to get these...

Hi, I am in possession of an HTC 8X engineering unit (see here http://forum.xda-developers.com/showthread.php?t=1966327). How can I help? Someone on my thread suggested that I should post here.

Hi! Yes, you could be of great help, if you could provide the partition tables from that device. I know it's politically incorrect to ask you to use a linux tool for doing this, but that is (probably) the only way it will be useful, as you cannot trust native windows partition information...
The way to do it, is by connecting your WP to a linux computer or possibly by using some linux distribution under a virtual machine (VirtualBox, VMware etc.) Then follow the instructions found here.
Thanks in advance.

8X Partition table
Hello. Also have a 8X engineering unit. This is the Partition Info:
Code:
# fdisk -l /dev/sdb
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 15.6 GB, 15634268160 bytes
1 heads, 32 sectors/track, 954240 cylinders
Units = cylinders of 32 * 512 = 16384 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 444417 7110656 ee GPT
Partition 1 does not end on cylinder boundary.
# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: Qualcomm MMC Storage (scsi)
Disk /dev/sdb: 15,6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 62,9MB 61,9MB pg1fs
2 62,9MB 66,1MB 3146kB MODEM_FSG
3 66,1MB 67,1MB 1049kB board_info
4 67,1MB 75,5MB 8389kB DPP
5 75,5MB 77,6MB 2097kB SSD
6 77,6MB 78,6MB 1049kB SBL1
7 78,6MB 79,7MB 1049kB SBL2
8 79,7MB 81,8MB 2097kB SBL3
9 81,8MB 83,9MB 2097kB UEFI
10 83,9MB 84,9MB 1049kB RPM
11 84,9MB 86,0MB 1049kB TZ
12 86,0MB 87,0MB 1049kB WINSECAPP
13 87,0MB 88,1MB 1049kB BACKUP_SBL1
14 88,1MB 89,1MB 1049kB BACKUP_SBL2
15 89,1MB 91,2MB 2097kB BACKUP_SBL3
16 91,2MB 93,3MB 2097kB BACKUP_UEFI
17 93,3MB 94,4MB 1049kB BACKUP_RPM
18 94,4MB 95,4MB 1049kB BACKUP_TZ
19 95,4MB 96,5MB 1049kB BACKUP_WINSECAPP
20 96,5MB 138MB 41,9MB RADIO
21 138MB 139MB 262kB UEFI_BS_NV
22 139MB 140MB 262kB UEFI_NV
23 141MB 149MB 8389kB PLAT
24 149MB 192MB 43,0MB fat16 EFIESP
25 192MB 193MB 1049kB pg2fs
26 193MB 194MB 1049kB RFG_0
27 194MB 195MB 1049kB RFG_1
28 195MB 196MB 1049kB RFG_2
29 196MB 197MB 1049kB RFG_3
30 197MB 198MB 1049kB RFG_4
31 198MB 199MB 1049kB RFG_5
32 199MB 200MB 1049kB RFG_6
33 200MB 201MB 1049kB RFG_7
34 201MB 202MB 1049kB RFG_8
35 202MB 207MB 4194kB MODEM_FS1
36 207MB 211MB 4194kB MODEM_FS2
37 211MB 211MB 262kB UEFI_RT_NV
38 212MB 212MB 131kB UEFI_RT_NV_RPMB
39 213MB 214MB 1049kB MFG
40 214MB 215MB 1049kB MISC
41 215MB 228MB 13,4MB fat16 MMOS
42 235MB 2698MB 2463MB ntfs MainOS
43 2698MB 5114MB 2416MB fat32 CrashDump
44 5117MB 15,6GB 10,5GB ntfs Data
(parted) q
# gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 30535680 sectors, 14.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): AE420040-13DD-41F2-AE7F-0DC35854C8D7
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 2048-sector boundaries
Total free space is 27687 sectors (13.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 122879 59.0 MiB FFFF pg1fs
2 122880 129023 3.0 MiB FFFF MODEM_FSG
3 129024 131071 1024.0 KiB FFFF board_info
4 131072 147455 8.0 MiB 0700 DPP
5 147456 151551 2.0 MiB FFFF SSD
6 151552 153599 1024.0 KiB FFFF SBL1
7 153600 155647 1024.0 KiB FFFF SBL2
8 155648 159743 2.0 MiB FFFF SBL3
9 159744 163839 2.0 MiB FFFF UEFI
10 163840 165887 1024.0 KiB FFFF RPM
11 165888 167935 1024.0 KiB FFFF TZ
12 167936 169983 1024.0 KiB FFFF WINSECAPP
13 169984 172031 1024.0 KiB FFFF BACKUP_SBL1
14 172032 174079 1024.0 KiB FFFF BACKUP_SBL2
15 174080 178175 2.0 MiB FFFF BACKUP_SBL3
16 178176 182271 2.0 MiB FFFF BACKUP_UEFI
17 182272 184319 1024.0 KiB FFFF BACKUP_RPM
18 184320 186367 1024.0 KiB FFFF BACKUP_TZ
19 186368 188415 1024.0 KiB FFFF BACKUP_WINSECAPP
20 188416 270335 40.0 MiB FFFF RADIO
21 270336 270847 256.0 KiB FFFF UEFI_BS_NV
22 272384 272895 256.0 KiB FFFF UEFI_NV
23 274432 290815 8.0 MiB FFFF PLAT
24 290816 374783 41.0 MiB 0700 EFIESP
25 374784 376831 1024.0 KiB FFFF pg2fs
26 376832 378879 1024.0 KiB FFFF RFG_0
27 378880 380927 1024.0 KiB FFFF RFG_1
28 380928 382975 1024.0 KiB FFFF RFG_2
29 382976 385023 1024.0 KiB FFFF RFG_3
30 385024 387071 1024.0 KiB FFFF RFG_4
31 387072 389119 1024.0 KiB FFFF RFG_5
32 389120 391167 1024.0 KiB FFFF RFG_6
33 391168 393215 1024.0 KiB FFFF RFG_7
34 393216 395263 1024.0 KiB FFFF RFG_8
35 395264 403455 4.0 MiB FFFF MODEM_FS1
36 403456 411647 4.0 MiB FFFF MODEM_FS2
37 411648 412159 256.0 KiB FFFF UEFI_RT_NV
38 413696 413951 128.0 KiB FFFF UEFI_RT_NV_RPMB
39 415744 417791 1024.0 KiB FFFF MFG
40 417792 419839 1024.0 KiB FFFF MISC
41 419840 446031 12.8 MiB 0700 MMOS
42 458752 5269094 2.3 GiB 0700 MainOS
43 5269504 9988095 2.2 GiB 0700 CrashDump
44 9994240 30535646 9.8 GiB 0700 Data
#

^^ Very nice!
Also for everybody's information. I was looking into one of the FFU files of the WP7 (?) Nokia Lumina 800 (RM-801), and it appears that hidden partitions (or mounts) are set in a registry key...
Code:
[SIZE=2][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MMC\IMGFS]
"MountHidden"=dword:1
"MountAsROM"=dword:1
"XIP"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SDMemory\IMGFS]
"MountHidden"=dword:1
"MountAsROM"=dword:1
"XIP"=dword:0
[HKEY_LOCAL_MACHINE\Drivers\BlockDevice\UniBlk]
"InternalStoreProfile"="MMC"
"InternalPartitionType"=dword:4[/SIZE]
and that the write protection is set by these registry items:
Code:
[SIZE=2][HKEY_LOCAL_MACHINE\System\StorageManager\WMPART\WriteProtectRegions\Region1]
"StartSector"=dword:0
"SectorCount"=dword:60000
[HKEY_LOCAL_MACHINE\System\StorageManager\WMPART]
"EnableHardwareWriteProtection"=dword:1
"PadAlignment"=dword:10000[/SIZE]
of course I could be wrong, since there are loads of similar items in there.
But it will perhaps help someone finding out where to look.

[Q] LG F70 D315 From tracfone No download mode

I achive for now:
!!!! Restore from any softbrick (any partition ful corrupted emmc) almost infalible!!! i have soft bricked bootloaders gpt, more than 10 times and resurrected again
A clowermod recovery
Semi flashed with f70 d315 stock?
I´m working when i can i post my results
Root
root is easy just use Towelroot
Clowermod Recovery
Tanks to OpenBump
put in sdcard and
Code:
adb shell
su
dd if=/sdcard/cwmrecovery_bumped.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery
Clower mod for L31L
Boot loader
The bootloader has some protection in aboot
if you disasemble with idapro is idem to the f70 d315, g2 mini and family the block that you have to patch
but this file is protected if you pach a single bit it bring you a raw disk when conect the phone (Q9006 mode)

-----OLD POST--------
I have a LG F70 D315 from tracfone whit this company the models change to LGL31L but I verify and many references says that is F70 an no other
I wan to flash whit a lesser restrictive firmware that not belong to this company to later flash a custom room, volume down while conet to get DOWNLOAD MODE are removed from this phone
I have KDZ, extracted to , i rooted sucefully the phone, got recovery mode
but the only way I find to flash is via download and this mode dosent apear
I think is rplace with a batery charging becouse that is what I see whit
Code:
adb reboot-bootloader
and others
and when try key conbinations to power up to download mode it bring me to the batery loader again
In the original extracted f70 d315 kdz the download mode is in the laf partition
I have it have a diferent size of the original fone laf
there is a way to push this to get download mode?
Sorry for my bad English and for post in this secction becouse I dont find LG 70 board
thanks
The partition info off the phone is this
Code:
shell># cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 22528 mmcblk0p15
179 16 22528 mmcblk0p16
179 17 22528 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 20480 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 32768 mmcblk0p29
179 30 512 mmcblk0p30
179 31 2097152 mmcblk0p31
259 0 921600 mmcblk0p32
259 1 4220416 mmcblk0p33
259 2 40943 mmcblk0p34
179 32 512 mmcblk0rpmb
shell># ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 20:09 DDR -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 20:09 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 20:09 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 20:09 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 20:09 cache -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-02 20:09 drm -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 20:09 eksst -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-02 20:09 encrypt -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 20:09 factory -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 20:09 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 20:09 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 20:09 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 20:09 grow -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-02 20:09 laf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 20:09 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 20:09 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 20:09 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 20:09 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 20:09 mpt -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-02 20:09 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 20:09 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 20:09 rct -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 20:09 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 20:09 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 20:09 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 20:09 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 20:09 sbl1b -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 20:09 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 20:09 sns -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 20:09 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 20:09 system -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-02 20:09 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 20:09 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 20:09 userdata -> /dev/block/mmcblk0p33
shell># parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8389kB 75.5MB 67.1MB fat16 modem
2 75.5MB 76.5MB 1049kB sbl1
3 76.5MB 77.1MB 524kB rpm
4 77.1MB 77.6MB 524kB tz
5 77.6MB 78.1MB 524kB sdi
6 78.1MB 80.2MB 2097kB aboot
7 80.2MB 80.7MB 524kB rpmb
8 80.7MB 81.3MB 524kB tzb
9 81.3MB 83.4MB 2097kB abootb
10 83.4MB 85.5MB 2097kB pad
11 85.5MB 88.6MB 3146kB modemst1
12 88.6MB 91.8MB 3146kB modemst2
13 91.8MB 109MB 16.8MB misc
14 109MB 143MB 33.6MB ext4 persist
15 143MB 166MB 23.1MB laf
16 168MB 191MB 23.1MB boot
17 191MB 214MB 23.1MB recovery
18 214MB 217MB 3146kB fsg
19 218MB 219MB 524kB fsc
20 219MB 219MB 524kB ssd
21 226MB 227MB 524kB DDR
22 235MB 235MB 524kB encrypt
23 235MB 236MB 524kB rct
24 243MB 252MB 8389kB ext4 drm
25 252MB 260MB 8389kB ext4 sns
26 260MB 281MB 21.0MB factory
27 281MB 315MB 33.6MB fota
28 319MB 320MB 1049kB sbl1b
29 320MB 353MB 33.6MB ext4 mpt
30 353MB 354MB 524kB eksst
31 361MB 2508MB 2147MB ext4 system
32 2508MB 3452MB 944MB ext4 cache
33 3452MB 7774MB 4322MB ext4 userdata
34 7776MB 7818MB 41.9MB grow
(parted) q
I copy laf to recovery partition with dd and bring me to Download Mode when I enter to recovery but i dont find a way to flash yet

unlock boot loader
I maybe try to flash via custom recovery but i have to unlock bootloader
This method
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
says change bites in this string 20 00 EB 00 00 50 E3 E0 FF FF 0A
The stock firmware have this string in aboot.img 20 00 eb 00 00 50 e3 e0 ff ff 0a 60 00 9f e5
but the aboot of my phone the string change to
20 00 eb 00 00 50 e3 08 00 84 e5 07 00 00 0a
and is the string only string that match to 20 00 eb 00 00 50 e3
20 00 eb 00 00 50 e3 e0 ff ff 0a 60 00 9f ->stock firm
20 00 eb 00 00 50 e3 08 00 84 e5 07 00 00 0a ->current room
If i change this with this conditions the phone may not boot anymore?

I am trying to get the download mode for the L31l and am wondering how you copied the files to the recovery partition.
I got the kdz file extracted it and extracted the dz files and have the binfiles.
I have also created an image file by combining the bin files but don't think this will do anything.
I am planning to use the method from:
htt p://ww w.lg-phone s.org/how-to-flas h-unbrick-lg-f70-bac k-to-stoc k.htm l
(Remove spaces)
To flash the kdz file of I can get download mode to work.
Thanks

Download mode
To get download mode:
1-To get download mode I rooted easy with towelroot
2-With dd made a backup of all partitions (nandroid backup)
3-Flash laf partition to recovery (change msm_sdcc I dont know exactly the name because I don´t have phone here and my tools):
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/dev/block/platform/msm_sdcc.1/by-name/recovery
4-Do
Code:
adb shell
reboot recovery
and you will enter to download instead of recovery
but for me was unseful because the firmware is for Lgf70 and is a lgl31l
and any flash sofware detected
I do the last I posted and dead:silly: to usb qualcom mode that see as raw disk
http://forum.xda-developers.com/showthread.php?t=2582142
this mode is easy to recover but intead I fail and dd other partition sbl
and have a mode that is very very triky and dont find how to solve
cause nothing worme form my phone
This a mode who I'am now QDLoader 9008
{
"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"
}
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830/page17#post58460319

I also got into download but couldn't get it to load the F70 rom.
Anybody have any ideas?

Thanks for your work. Have you been able to load the portion of the f70 rom that contains the hidden menu for unlock?
I know there is some information about adding it back to the verizon g2 available.
Thanks again

Any more info to share?
You mentioned a f70 rom. Any more luck getting it to work?
Thanks

f70 rom
1god 1Bad news I flash the f70 but the unlock menu says that not more atemps left (usseless)
Flash f70 room bricks me the phone many times with a backup I can bring back ever I want but may sometimes have to open the phone and make a tespoint
Frist backup all your phone whit dd
I backup all single partition
dd if=/dev/block/platform/msm_sdcc.1/by-name/xxx of=/sdcard/backup
and after backup the GPT partition table
you beter dd all then phone mmc instead
of course copy to a PC or any external
Extract boot.img and system.img of F70 room kdztools etc...
For f70 room you have to bumped boot.img of F70
frist have to repack whit bootimg.exe http://en.miui.com/thread-27657-1-1.html
descompress and compress
and after used open bump
http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
Better put frist system.img to sdcard
1)whit dd flash the recovery to the boot img after that youre phone start always in recovery
because no recovery convination
2)flash boot.img to recovery
3) Now when you turn your phone start in the recovery mount /sdcard /system...
conect in and this recovery have adb
flash whit dd system partition
don't exit recovery
4)wipe cache factory reset
5) in avanced revot recovery will boot system (anytimes you power on have to do this)
The gide is not easy and safe i can made a better but flash f70 dosen't worst
yes you have more usb modes enabled, wifi theter and hotspot
but no unock , even any unlock boxes that have f70 direct unlock
all becuse the nvram is not accesible????

i brick my d315 with update v10e
hello,
I have got a LG D315 with root and TWRP 2.8.0.0.
today i see there is a update v10e for my phone.
so i accept the install. the update download , pass de verify ( no problem cause root) and reboot.
but the phone boot on TWRP only and the update no run . i can't reboot normaly , I'm blocked on TWRP ( reboot on system, bootloader or recovery >> return to TWRP) , the phone refuse to upgrade or reboot normaly ?
any ideas ???
please help !!
ps : sorry I'm french and i write bad english

willowlefou said:
hello,
I have got a LG D315 with root and TWRP 2.8.0.0.
today i see there is a update v10e for my phone.
so i accept the install. the update download , pass de verify ( no problem cause root) and reboot.
but the phone boot on TWRP only and the update no run . i can't reboot normaly , I'm blocked on TWRP ( reboot on system, bootloader or recovery >> return to TWRP) , the phone refuse to upgrade or reboot normaly ?
any ideas ???
please help !!
ps : sorry I'm french and i write bad english
Click to expand...
Click to collapse
I resolved my problem ,
I have backup the LAF files so in TWRP I 've restore the laf
Code:
dd if=/sdcard/backup/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
after i reboot in download mode ( power off / button up + plug usb cable )
the LGFlashTool2014 detect my phone i Ican retore the D31510e_00.kdz file with this tools.
my data aren't destroy.
thanks!

Hi guys! My lg f70 phone broken after use flash tool, (Qdloader 9008), i search fixing on internet, and finding them QFIl and qpst.. My phone cpu msm8926, need emmc firehose 8926 file for flashing emmc and fastboot restore file, somebody help? Sorry my bad english!

How to mount the root filesystem in twrp recovery?

Sorry for this perhaps dumb question and I'm sure it was answered anywhere but searching for "mount root recovery" lists everything to root the device. Last time I need to do this was on my HTC Desire with that S-ON
Ok, but for the backgrounds:
I am running CM13 (rooted of cource) and I need to tweak /init.cm.rc startup script.
When doing this while running CM13 (/ filesystem mounted rw) any changes are gone after reboot.
So how can I do this?
My first thought was: Edit while in recovery. But in TWRP (3.0) the root filesystem isn't mounted - so how can I mount it?
Or on which partition is it located?
Thanks in advance!
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 44 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 16384 180223 80.0M 0700 modem
2 180224 182271 1024K 0700 sbl1
3 182272 182463 98304 0700 sdi
4 182464 184511 1024K 0700 tz
5 184512 185511 500K 0700 rpm
6 185512 186535 512K 0700 hyp
7 186536 186791 128K 0700 pmic
8 186792 188839 1024K 0700 DDR
9 188840 189095 128K 0700 sec
10 189096 197855 4380K 0700 aboot
11 197856 198111 128K 0700 pmicbak
12 198112 200159 1024K 0700 sbl1bak
13 200160 202207 1024K 0700 tzbak
14 202208 203207 500K 0700 rpmbak
15 203208 204231 512K 0700 hypbak
16 204232 212991 4380K 0700 abootbak
17 212992 212993 1024 0700 devinfo
18 229376 237567 4096K 0700 fsg
19 245760 245761 1024 0700 limits
20 262144 270335 4096K 0700 modemst1
21 270336 278527 4096K 0700 modemst2
22 278528 279039 256K 0700 apdp
23 279040 279551 256K 0700 msadp
24 279552 280063 256K 0700 keymaster
25 280064 280575 256K 0700 cmnlib
26 280576 281087 256K 0700 keymasterbak
27 281088 281599 256K 0700 cmnlibbak
28 281600 281601 1024 0700 dpo
29 281602 281603 1024 0700 fsc
30 281604 281619 8192 0700 ssd
31 281620 294911 6646K 0700 oeminfo
32 294912 311295 8192K 0700 persist
33 311296 344063 16.0M 0700 metadata
34 344064 409599 32.0M 0700 boot
35 409600 475135 32.0M 0700 recovery
36 475136 606207 64.0M 0700 oem
37 606208 1015807 200M 0700 vendor
38 1015808 1220607 100M 0700 cache
39 1220608 1222655 1024K 0700 misc
40 1222656 1223679 512K 0700 keystore
41 1223680 1224703 512K 0700 frp
42 1224704 1225703 500K 0700 persistent
43 1225704 7517159 3072M 0700 system
44 7517160 61071326 25.5G 0700 userdata

markusmuster said:
Sorry for this perhaps dumb question and I'm sure it was answered anywhere but searching for "mount root recovery" lists everything to root the device. Last time I need to do this was on my HTC Desire with that S-ON
Ok, but for the backgrounds:
I am running CM13 (rooted of cource) and I need to tweak /init.cm.rc startup script.
When doing this while running CM13 (/ filesystem mounted rw) any changes are gone after reboot.
So how can I do this?
My first thought was: Edit while in recovery. But in TWRP (3.0) the root filesystem isn't mounted - so how can I mount it?
Or on which partition is it located?
Thanks in advance!
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 44 entries
First usable sector is 34, last usable sector is 61071326
Click to expand...
Click to collapse
sorry but init.cm.rc is a RAMDISK file... that means you need to change it in the boot.img .... so you will need to compile a new boot.img with your changes or use android image kitchen... but i warn you... playing with boot.img is for devs so dont do mistakes in there!
Sent from my Xperia T using XDA Free mobile app

Thanks for the information. Already guesses that.
Yesterday I saw somewhere in the init scripts that there was a Cyan-test for a user script. I will investigate this.

How to install a new rom with bootloader loocked?

Hello I have a machine Redmi2 that does not boot, only boots with fastboot when I pressed the power off button ans Vol - button
I can execute fastboot commands.
For example:
fastboot devices
Click to expand...
Click to collapse
967354587d12 fastboot
Click to expand...
Click to collapse
fastboot oem device-info
Click to expand...
Click to collapse
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
I could dowloaded various rom (official from xiaomi and not official like aosp-caf_wt88047_64-21-05-2017-eng.pirej.zip or xiaomi-miui-hellas-5.1_wt88047_V8_XTRVbeta2_7.2.24.zip) but I can install a new system in this machine.
First I try to unlock the bootloader with official method from Xiaomi but the result is error.
Now I try to boot with twrp and this is works.
To boot with twrp I cam execute this with fastboot
fastboot flash recovery twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'recovery' (11426 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.184s]
finished. total time: 0.544s
Click to expand...
Click to collapse
fastboot flash boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'boot' (11426 KB)...
OKAY [ 0.361s]
writing 'boot'...
OKAY [ 0.132s]
finished. total time: 0.493s
Click to expand...
Click to collapse
And with this comand boots the machine with twrp
fastboot boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
When machine boots I have access to external card from my PC and I can put the rom to try to install.
When try to clean the partitions I can not do it:
This is the errors
Error al desmontar '/system' (invalid argument)
Error al desmontar '/data' (invalid argument)
Error al desmontar '/cache' (invalid argument)
Incapaz de montar almacenamiento
Click to expand...
Click to collapse
When I try to install RR-N-v5.8.3-20170516-wt88047-OFFICIAL.zip for example I can not install this rom.
Do you know if it is possible install a rom with bootloader locked?
Doy you know if it is possible unlocked the bootloader if xiaomi unlocker does not works?
Any ideas to install a rom in this machine?
Best regards.

i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?

AKHILR4J said:
i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?
Click to expand...
Click to collapse
Thanks for your help,
I have downloaded the lastest twrp img from redmi 2, and I have the same problems.
Machine boots with twrp but I can not write in the internal partitions and I can not install a rom.
I think that I need unlock the bootloader to can to modify the android partitions but I do not know to do it.

try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS

Liquid2 said:
try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS
Click to expand...
Click to collapse
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.

Hello again, I have tried to mount /system with a terminal in TWRP with this command
Code:
# Montamos la carpeta /system como lectura(r) y escritura(w)
mount -o remount,rw /system
but the problem is my /proc/mounts file
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=967420k,nr_inodes=153983,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
tmpfs /tmp tmpfs rw,seclabel,relatime,size=967420k,nr_inodes=153983 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p25 /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /firmware vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
Do you know how can I can change this file to include the /system partition to mount read/write and I can install a rom os.
Regards,

jriosa said:
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.
Click to expand...
Click to collapse
have u tried another twrp?? make sure it for your device

Liquid2 said:
have u tried another twrp?? make sure it for your device
Click to expand...
Click to collapse
Thanks for your help, I have tried different versions from twrp with the same result.
Regards, Julio.

sori, cant help much, maybe
i myself in very newbie
how about if you flash fresh with flashboot rom using miflash, see if it can boot into official miui first
then you can try install twrp again and flash custom rom
have you tried twrp

Hello Now I access to android with adb.
When I boot the android with TWRP, I can access with my PC using adb.
I execute this.
adb root
Click to expand...
Click to collapse
adb shell
Click to expand...
Click to collapse
This is the partitions on my machine
~ # cat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1048576 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 13557743 mmcblk0p30
179 32 4096 mmcblk0rpmb
179 64 30375936 mmcblk1
179 65 30371840 mmcblk1p1
Click to expand...
Click to collapse
~ # cd /dev
/dev # find -inme mmcblk0
find: unrecognized: -inme
Segmentation fault
/dev # find -iname mmcblk0
./block/mmcblk0
./block/platform/soc.0/7824900.sdhci/mmcblk0
Click to expand...
Click to collapse
I have added parted to managed partitions in my machine
To see parttions in my disk
~ # /sbin/parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Click to expand...
Click to collapse
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
Click to expand...
Click to collapse
To see my partitions
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 32.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 13.4G 15.6G 46% /external_sd
Click to expand...
Click to collapse
I think that I can not install a new rom (offcial or unofficial) because the system I can not access to partitions /system for example and I think that system partitions is mmcblk0p23.
Do you know how I can modify my partitions to see in df -h and launch a new rom with twrp?
Thanks a lot,

Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.

Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.

jriosa said:
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
Click to expand...
Click to collapse
Have you unmounted the data partition in twrp before executing the rm command?

SidOfficial said:
Have you unmounted the data partition in twrp before executing the rm command?
Click to expand...
Click to collapse
This is my commands and my point mounts are
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
Click to expand...
Click to collapse
I see a new error
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
Click to expand...
Click to collapse
maybe the first partition I think is OK
~ # parted /dev/block/mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 67.1MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 67.1MB 67.1MB fat16
Click to expand...
Click to collapse
adb shell
~ # cp /external_sd/parted /sbin/parted
~ # chmod +x /sbin/parted
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit MiB
unit MiB
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) rm 30
rm 30
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) q
q
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
(parted)
Click to expand...
Click to collapse
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?

jriosa said:
This is my commands and my point mounts are
I see a new error
maybe the first partition I think is OK
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?
Click to expand...
Click to collapse
Yes, you can recreate all the partitions and can even resize the system and data partitions. Head over to this link https://forum.xda-developers.com/redmi-2/how-to/wt88047-redmi-2-resize-partition-t3612933

TWRP for the SM-J727R4

If any of you SM-J727R4 users can run and get the output of these 2 commands, I'll create a TWRP build for the device (SM-J727R4).
Code:
adb shell ls -al /dev/block/bootdevice/by-name
Code:
adb shell cat /proc/partitions

adb shell ls -al /dev/block/bootdevice/by-name
total 0
drwxr-xr-x 2 root root 820 2009-12-31 18:00 .
drwxr-xr-x 4 root root 900 2009-12-31 18:00 ..
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apdp -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apnhlos -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 bota -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib64 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 ddr -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 devcfg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 dsp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 efs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 keymaster -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 lksecapp -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modem -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 msadp -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 param -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persist -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persistent -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 reserved2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 steady -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 system -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 userdata -> /dev/block/mmcblk0p39
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
adb shell cat /proc/partitions
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 256 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3328 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 128 mmcblk0p20
179 21 128 mmcblk0p21
179 22 12288 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4096 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 98304 mmcblk0p34
259 3 36864 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 3588096 mmcblk0p37
259 6 307200 mmcblk0p38
259 7 11157484 mmcblk0p39
179 32 4096 mmcblk0rpmb
253 0 1048576 vnswap0
254 0 3555328 dm-0
254 1 11157468 dm-1
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1

killertaz17 said:
total 0
drwxr-xr-x 2 root root 820 2009-12-31 18:00 .
drwxr-xr-x 4 root root 900 2009-12-31 18:00 ..
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apdp -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apnhlos -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 bota -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib64 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 ddr -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 devcfg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 dsp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 efs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 keymaster -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 lksecapp -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modem -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 msadp -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 param -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persist -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persistent -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 reserved2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 steady -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 system -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 userdata -> /dev/block/mmcblk0p39
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
adb shell cat /proc/partitions
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 256 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3328 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 128 mmcblk0p20
179 21 128 mmcblk0p21
179 22 12288 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4096 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 98304 mmcblk0p34
259 3 36864 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 3588096 mmcblk0p37
259 6 307200 mmcblk0p38
259 7 11157484 mmcblk0p39
179 32 4096 mmcblk0rpmb
253 0 1048576 vnswap0
254 0 3555328 dm-0
254 1 11157468 dm-1
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1
Click to expand...
Click to collapse
Do you have OEM Unlock available in developer settings?

Did not. I will re do it give me a few.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
adb shell ls -al /dev/block/bootdevice/by-name
total 0
drwxr-xr-x 2 root root 820 2009-12-31 18:00 .
drwxr-xr-x 4 root root 900 2009-12-31 18:00 ..
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apdp -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apnhlos -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 bota -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib64 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 ddr -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 devcfg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 dsp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 efs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 keymaster -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 lksecapp -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modem -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 msadp -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 param -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persist -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persistent -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 reserved2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 steady -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 system -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 userdata -> /dev/block/mmcblk0p39
--------------------------------------------------------------------------------------------------
adb shell cat /proc/partitions
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 256 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3328 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 128 mmcblk0p20
179 21 128 mmcblk0p21
179 22 12288 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4096 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 98304 mmcblk0p34
259 3 36864 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 3588096 mmcblk0p37
259 6 307200 mmcblk0p38
259 7 11157484 mmcblk0p39
179 32 4096 mmcblk0rpmb
253 0 1048576 vnswap0
254 0 3555328 dm-0
254 1 11157468 dm-1
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1

killertaz17 said:
Did not. I will re do it give me a few.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
adb shell ls -al /dev/block/bootdevice/by-name
total 0
drwxr-xr-x 2 root root 820 2009-12-31 18:00 .
drwxr-xr-x 4 root root 900 2009-12-31 18:00 ..
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apdp -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 apnhlos -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 boot -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 bota -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 cmnlib64 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 ddr -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 devcfg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 dsp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 efs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 keymaster -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 lksecapp -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modem -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 msadp -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 pad -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 param -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persist -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 persistent -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 reserved2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 steady -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 system -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2009-12-31 18:00 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2009-12-31 18:00 userdata -> /dev/block/mmcblk0p39
--------------------------------------------------------------------------------------------------
adb shell cat /proc/partitions
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 256 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 256 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3328 mmcblk0p17
179 18 256 mmcblk0p18
179 19 256 mmcblk0p19
179 20 128 mmcblk0p20
179 21 128 mmcblk0p21
179 22 12288 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4096 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 98304 mmcblk0p34
259 3 36864 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 3588096 mmcblk0p37
259 6 307200 mmcblk0p38
259 7 11157484 mmcblk0p39
179 32 4096 mmcblk0rpmb
253 0 1048576 vnswap0
254 0 3555328 dm-0
254 1 11157468 dm-1
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1
Click to expand...
Click to collapse
Oh, I didn't need you to redo it, I wanted to verify if it's present in Developer Settings or not. If you don't have OEM Unlock in Developer Settings, then you can't flash anything.

minz1 said:
Oh, I didn't need you to redo it, I wanted to verify if it's present in Developer Settings or not. If you don't have OEM Unlock in Developer Settings, then you can't flash anything.
Click to expand...
Click to collapse
Yeah i turned it on. I know how to flash with odin. Ive rooted before just dont know how to debug and all that fun stuff. But guide me thru and im sure i can do it.

Are you making one? Because That would be awesome I havent been able to root or anything with this phone

v0idd said:
Are you making one? Because That would be awesome I havent been able to root or anything with this phone
Click to expand...
Click to collapse
Yeah, but currently I'm neck deep in resolving a bug on the other J7 variant. Soon I'll have a build up for ya guys, and if all goes well, we can have an official build for the J727R4.

minz1 said:
Yeah, but currently I'm neck deep in resolving a bug on the other J7 variant. Soon I'll have a build up for ya guys, and if all goes well, we can have an official build for the J727R4.
Click to expand...
Click to collapse
Okay hopefully root will follow right behind it. Just let me know if you need anything

https://www.androidfilehost.com/?fid=746010030569960106
Try this, guys.

minz1 said:
https://www.androidfilehost.com/?fid=746010030569960106
Try this, guys.
Click to expand...
Click to collapse
installed using odin worked gave permission to write rebooted and got into a bootloop opened back up recovery and asked for permission to make writing permissions. i am now stuck in a boot loop will have to use stock rom to fix this. kinda my daily phone. i will try to flash just the stock recovery.

killertaz17 said:
installed using odin worked gave permission to write rebooted and got into a bootloop opened back up recovery and asked for permission to make writing permissions. i am now stuck in a boot loop will have to use stock rom to fix this. kinda my daily phone. i will try to flash just the stock recovery.
Click to expand...
Click to collapse
Format data and flash magisk/superSU and you'll be out of the bootloop. That's normal behavior because of dm-verity

minz1 said:
Format data and flash magisk/superSU and you'll be out of the bootloop. That's normal behavior because of dm-verity
Click to expand...
Click to collapse
i backup up my system with TWRP and flashed magisk. can i restore my backup with twrp? i will downlooad supersu when it boots up.

killertaz17 said:
i backup up my system with TWRP and flashed magisk. can i restore my backup with twrp? i will downlooad supersu when it boots up.
Click to expand...
Click to collapse
Oh I meant either magisk or superSU, but not both. Be sure you format data in twrp, and yes you can restore your system

minz1 said:
Oh I meant either magisk or superSU, but not both. Be sure you format data in twrp, and yes you can restore your system
Click to expand...
Click to collapse
oh okay i did magisk ill delete super su then. and we have root on sm-j727r4! checked with root checker.

killertaz17 said:
oh okay i did magisk ill delete super su then. and we have root on sm-j727r4! checked with root checker.
Click to expand...
Click to collapse
Cool, I'll get this device rolling with official TWRP builds, and I'll build Lineage for it once it's stable on the sprint J7

v0idd said:
Are you making one? Because That would be awesome I havent been able to root or anything with this phone
Click to expand...
Click to collapse
Still need root i can help you get it? Super easy.

I have installed xposed on my j7 works. Little to no bugs that i have found. No random reboots or anything.

killertaz17 said:
Still need root i can help you get it? Super easy.
Click to expand...
Click to collapse
Sorry for such A late response my apologies. For some reason I completely forgot about rooting. If you are around then yes I would love some help I really need to root lol I miss xposed.

v0idd said:
Sorry for such A late response my apologies. For some reason I completely forgot about rooting. If you are around then yes I would love some help I really need to root lol I miss xposed.
Click to expand...
Click to collapse
Supereasy just flash the twrp the link is in this thread then download magisk manger and flash that MAKE SURE TO WIPE DATA AND STUFF AFTER or bootloop will happen. I had to restore my device many times before finally getting it, verify with root checker no need for supersu. Once i booted and had root i backed up my boot and system incase a restore needed but havent had a issue at all since. Its been a while since i did this so ill try to remember if u have problems.