I wanted to extract boot.img from an existing rom, following this wiki:
http://android-dls.com/wiki/index.p..._Images#Structure_of_boot_and_recovery_images
But it seems that on Stock Rom (actually I'm using Zeus rom, based on stock) there is no /proc/mtd that would tell me where to find the "boot" partition. I think it should be one of these:
179 0 1912832 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 660480 mmcblk0p8
179 9 1161088 mmcblk0p9
179 10 65536 mmcblk0p10
179 11 128 mmcblk0p11
179 12 128 mmcblk0p12
179 16 15637504 mmcblk1
179 17 15633408 mmcblk1p1
Do anyone know where the boot partition is hiding? Or have an idea on how to find where it is?
Here are some of the partitions:
Code:
loop0 =
/dev/block/mmcblk0 =
/dev/block/mmcblk0p1 =
/dev/block/mmcblk0p2 =
/dev/block/mmcblk0p3 = /boot
/dev/block/mmcblk0p4 = /recovery
/dev/block/mmcblk0p5 = /lgdrm
/dev/block/mmcblk0p6 = /dvp/userdata
/dev/block/mmcblk0p7 =
/dev/block/mmcblk0p8 = /system
/dev/block/mmcblk0p9 = /data
/dev/block/mmcblk0p10 = /cache
/dev/block/mmcblk0p11 =
/dev/block/mmcblk0p12 =
/dev/block/mmcblk1 =
/dev/block/mmcblk1p1 = /sdcard
dm-0 =
Here is the partition list of all Nexus 5 partitions with parted:
Code:
C:\Users\cargo\tools>adb shell
~ # umount /cache
umount /cache
~ # umount /system
umount /system
~ # umount /data
umount /data
~ # parted /dev/block/mmcblk0
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
print
print
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
(parted)
Here is a simple list:
Code:
C:\Users\cargo\tools>adb shell
cat /proc/partitions~ #
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 28551146 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ #
Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )
przemo_li said:
Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )
Click to expand...
Click to collapse
You won't get much speed out of a hosed phone. No you can't.
jd1639 said:
You won't get much speed out of a hosed phone. No you can't.
Click to expand...
Click to collapse
Meaning, kernel must support F2FS otherwise it wont boot? Obvious (for me at least) Just wanted to know if I can find such kernels (already build), and if there are tools to convert existing partitions. (So that changes performed are not too invasive )
Or if there are some mods that already employ F2FS.
(Moto G is my inspiration here, btw)
Any info and specs on the MMC model?
eng.stk said:
Any info and specs on the MMC model?
Click to expand...
Click to collapse
Do not know what MMC is, but if it was question for me I will just assume its hw question about storage specs for my phone.
1) I do not have that phone yet
2) It will be internetional version of Nexus 5 (16GB or 32GB).
eng.stk said:
Any info and specs on the MMC model?
Click to expand...
Click to collapse
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf
rootSU said:
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
Click to expand...
Click to collapse
404 error
przemo_li said:
404 error
Click to expand...
Click to collapse
Because the url has [1] in it. Try and copy / paste
rootSU said:
Because the url has [1] in it. Try and copy / paste
Click to expand...
Click to collapse
Did that before I posted 404
No [1], and still 404
przemo_li said:
Did that before I posted 404
No [1], and still 404
Click to expand...
Click to collapse
It works, don't forget [1].pdf in the end.
przemo_li said:
Did that before I posted 404
No [1], and still 404
Click to expand...
Click to collapse
OK I fixed the link.
rootSU said:
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf
Click to expand...
Click to collapse
Sustained Read:15 MB/sSustained Write:9 MB/s
Biggest bottleneck of this great device
"Why Google?" or "Why LG?"
przemo_li said:
Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )
Click to expand...
Click to collapse
Lol, i do
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
dennes544 said:
Lol, i do
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
Click to expand...
Click to collapse
I know you're trying to be helpful but why revive and answer a thread that's been dead for 3 months?
Sent from my Nexus 5 using Tapatalk
Partition Stock
Hi I have a problem a wipe system VOL, I have /sdcard/ /sdcard/0/ /sdcard/0/0/ When I use usb have to goo /sdcard/0/0/ to much problem my question .. How I cant reset all partitions? and leave my fone like new..?? So I have 28 Gb free but I didnt put any file.. I wanna clean all fone and start with OEM partition, Thx ...sorry for english
how do you get parted on your N5? I only get sh: parted: not found lol
Can you please post the table again using bits or sectors as units? That will be very helpful.
jd1639 said:
You won't get much speed out of a hosed phone. No you can't.
Click to expand...
Click to collapse
Formatting cache and data DOES provide a speed boost but not with system. System should stay EXT4 because F2FS improves the performance of write operations the most and, typically, system is read only. Stick LineageOS 13 and 14.1 support data and cache as F2FS. Be aware though that switching data to F2FS WILL wipe internal storage so back it up. If you wish to keep your data the backup the data partition in TWRP and then backup the entire internal storage directory to a computer. After you've backed up everything you can go to wipe, advanced wipe and select data and hit repair or change and change it to F2FS. Once that is done you should reboot back into TWRP, open settings and enable "use rm -rf instead of formatting". When in recovery you can copy your entire internal storage back to your phone, ensure you copy it right, the TWRP directory should be in the root of your internal storage, this is important because it contains your precious data backup. After that reboot back into TWRP and you may have to enable rm -rf in settings, make sure that is enabled! These reboots are for good measure, it's best to just do them. After that you can go to restore and restore your data backup. After it is fully restored you may disable rm -rf in settings and format cache as F2FS. Then reboot to system and enjoy!
Sent from my Pixel using XDA Labs
I have extracted the Gear 2 firmware to a zip so people can look at the structure and possibly start modding the device. Its extracted from the newest rom available on Sammobile. If you have any questions let me know.
htt p://bit.ly/1m4mj5m
Velrix said:
I have extracted the Gear 2 firmware to a zip so people can look at the structure and possibly start modding the device. Its extracted from the newest rom available on Sammobile. If you have any questions let me know.
htt p://bit.ly/1m4mj5m
Click to expand...
Click to collapse
Updates..
I am trying to backup the current partitions to see the kernel/recovery and not getting far. Has anyone else been working on this?
sh-3.2$ cat /proc/partitions
major minor #blocks name
7 0 19732 loop0
179 0 3817472 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 12288 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 65536 mmcblk0p12
259 5 131072 mmcblk0p13
259 6 2996224 mmcblk0p14
259 7 524288 mmcblk0p15
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179:0 179:3 179:7 1:10 1:14 1:4 1:8 259:2 259:6 7:2 7:6
179:1 179:4 179:8 1:11 1:15 1:5 1:9 259:3 259:7 7:3 7:7
179:16 179:5 1:0 1:12 1:2 1:6 259:0 259:4 7:0 7:4
179:2 179:6 1:1 1:13 1:3 1:7 259:1 259:5 7:1 7:5
Current information I can receive from the watch.
If I try to make a backup obviously it fails with the following message..
D:\tizen-wearable-sdk\tools>sdb shell
sh-3.2$ chmod 755 /tmp/rkdump
sh-3.2$ /tmp/rkdump /dev/mmcblk0boot0 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0boot0: Permission denied
sh-3.2$ /tmp/rkdump /dev/mmcblk0p1 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0p1: Permission denied
sh-3.2$ /tmp/rkdump /dev/mmcblk0p2 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0p2: Permission denied
Device: OnePlus 3t Rooted with magisk TWRP installed.
Android 8.0
BusyBox is installed
On PC I have Cygwin 64bit installed with util linux, pv, netcat packages installed, including platform tools.
I'm trying to get into my partition directory user data by-name as I want to make an image of my OnePlus Internal storage and copy it on PC.
I can view cat /proc/partitions
$ adb shell
OnePlus3T:/ # cat /proc/partitions
major minor #blocks name
8 0 119062528 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 118718956 sda15
8 32 4096 sdc
8 33 4052 sdc1
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 16 4096 sdb
8 17 4052 sdb1
8 80 1572864 sdf
8 81 2048 sdf1
8 82 2048 sdf2
8 83 4 sdf3
8 84 512 sdf4
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
254 0 118718940 dm-0
Can anyone help me to find partition by-name lists on OnePlus 3t? I have also tried Diskinfo to find the details but it didn't helped me. I have also followed this https://forum.xda-developers.com/t/guide-internal-memory-data-deleted-files-recovery.3093292/ but it's getting hard for me to get into the b-name partition list of my device.
Or do you guys know any other alternatives on how to make an image of OnePlus internal storage to PC?
I'm stucked since days. Please need some help.
is there any genius who can help me on this matter?
Have a look at both of these commands:
Bash:
cat /proc/partitions
ls -l /dev/block/bootdevice/by-name
BillGoss said:
Have a look at both of these commands:
Bash:
cat /proc/partitions
ls -l /dev/block/bootdevice/by-name
Click to expand...
Click to collapse
after typing
ls -l /dev/block/bootdevice/by-name
it says system/bin/sh: 1s: not found.
I'm really stucked here.
Lol! The command is lower case L - ls. Not 1 - 1s.
BillGoss said:
Lol! The command is lower case L - ls. Not 1 - 1s.
Click to expand...
Click to collapse
thanks for the clarification bro..
I have unlocked my redmi 7A using unlock tool provided by Xiomi.
I can boot TWRP by:
adb reboot-bootloader
fastboot flash recovery 'TWRP-3.3.1-1003-REDMI7A-CN-wzsx150.img'
fastboot reboot
and holding volume key. ( up or down I don't remember)
I also flashed vbmeta to Disable VerifiedBoot:
fastboot flash --disable-verification vbmeta vbmeta.img
because I was modifying /vendor
Now redmi 7A was running twrp and was connected to my ubuntu PC using USB cable.
On PC I typed:
adb shell
now I got root shell. I created a directory in /mnt to mount /vendor partition.
# mkdir /mnt/dirName
# mount /dev/block/mmcblk0p58 /mnt/dirName
How did I know that /dev/block/mmcblk0p58 was /vendor? Previously I had copied all of phone's emmc flash disk to PC by:
** On PC **
adb pull /dev/block/mmcblk0
I mounted mmcblk0 image file using:
[email protected]:/home/username# losetup --show --nooverlap --partscan --find '/path/to/mmcblk0'
** output **
/dev/loop20
got partition table information using:
** On PC **
[email protected]:/home/username# gdisk /dev/loop20
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Number Start (sector) End (sector) Size Code Name
1 40 55 8.0 KiB A029 fsc
2 56 71 8.0 KiB A02C ssd
3 72 87 8.0 KiB A024 dpo
4 88 119 16.0 KiB A01D sec
5 120 183 32.0 KiB A01A DDR
6 184 247 32.0 KiB A040 limits
7 248 311 32.0 KiB FFFF config
8 312 383 36.0 KiB 8300 bk1
9 384 511 64.0 KiB 8300 bk2
10 512 639 64.0 KiB FFFF vbmeta
11 640 767 64.0 KiB 0700 vbmetabak
12 768 1023 128.0 KiB 8300 bk3
13 1024 1535 256.0 KiB FFFF devcfg
14 1536 2047 256.0 KiB FFFF devcfgbak
15 2048 2559 256.0 KiB A022 apdp
16 2560 3071 256.0 KiB A023 msadp
17 3072 4095 512.0 KiB A012 sbl1
18 4096 5119 512.0 KiB 0700 sbl1bak
19 5120 6143 512.0 KiB A018 rpm
20 6144 7167 512.0 KiB 0700 rpmbak
21 7168 8191 512.0 KiB 0700 mota
22 8192 9215 512.0 KiB A02D keystore
23 9216 10239 512.0 KiB A018 syscfg
24 10240 12287 1024.0 KiB FFFF cmnlib
25 12288 14335 1024.0 KiB FFFF cmnlibbak
26 14336 16383 1024.0 KiB FFFF cmnlib64
27 16384 18431 1024.0 KiB FFFF cmnlib64bak
28 18432 20479 1024.0 KiB FFFF keymaster
29 20480 22527 1024.0 KiB FFFF keymasterbak
30 22528 24575 1024.0 KiB A01F misc
31 24576 26623 1024.0 KiB A015 aboot
32 26624 28671 1024.0 KiB 0700 abootbak
33 28672 30719 1024.0 KiB FFFF dip
34 30720 32767 1024.0 KiB 8300 bk4
35 32768 36863 2.0 MiB A016 tz
36 36864 40959 2.0 MiB 0700 tzbak
37 40960 49151 4.0 MiB 0700 mcfg
38 49152 65535 8.0 MiB A03A devinfo
39 65536 81919 8.0 MiB FFFF dtbo
40 81920 98303 8.0 MiB 0700 dtbobak
41 98304 114687 8.0 MiB A027 modemst1
42 114688 131071 8.0 MiB A028 modemst2
43 131072 147455 8.0 MiB A02A fsg
44 147456 163839 8.0 MiB 8300 bk5
45 163840 196607 16.0 MiB A036 splash
46 196608 229375 16.0 MiB 0700 dsp
47 229376 262143 16.0 MiB 0700 dspbak
48 262144 327679 32.0 MiB A026 persist
49 327680 393215 32.0 MiB A026 persistbak
50 393216 458751 32.0 MiB FFFF mdtp
51 458752 524287 32.0 MiB FFFF mdtpbak
52 524288 655359 64.0 MiB A036 boot
53 655360 786431 64.0 MiB A025 recovery
54 786432 917503 64.0 MiB FFFF logdump
55 917504 1441791 256.0 MiB A039 cache
56 1441792 1703935 128.0 MiB 0700 modem
57 1703936 7995391 3.0 GiB A038 system
58 7995392 10092543 1024.0 MiB A038 vendor
59 10092544 11141119 512.0 MiB A03A cust
60 11141120 11272191 64.0 MiB 8300 userdata
Command (? for help): q
[email protected]:/home/username#
you may observe that size of userdata is 64MB that is because I resized the image to reduce it's size.
from above we can see that /vendor is partition 58 that is /dev/block/mmcblk0p58
after mounting I edited /vendor/etc/fstab.qcom using nano
** On redmi 7A:
# nano /mnt/dirName/etc/fstab.qcom
I changed
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,fileencryption=ice,quota,reservedsize=128M
to
# /dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,fileencryption=ice,quota,reservedsize=128M
/dev/block/mmcblk1p2 /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,quota,reservedsize=128M
notice that I have also removed fileencryption=ice mount option to disable encryption.
I also changed
/devices/platform/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
to
# /devices/platform/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
# /devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
to disable mountng of fat32 partition on sdcard as external sdcard
I inserted 128gb microSD card ( class 10 ) into USB card reader and connected the card reader to Ubuntu PC. created GPT patition table on microSD. left 16 GB space at begining of microSD empty so that ext4 fs is aligned with flash storage blocks. created 1 fat32 partition and 1 ext4 partition on sdcard.
after editing fstab I unmounted /vendor and turned off the phone using:
# poweroff
Inserted microSD into phone and turned on. It took few minutes on first boot.
On setup screen do not enter lockscreen password or pattern. because Phone shows incorrect password even if password is correct. I was locked out of my phone because of password error. I had to delete some file/ files ( I don't remember filename ) from /data by connecting microSDcard to pc to remove screen lock.
Microsd card is slightly slower that emmc nand. I have noticed that the phone took slightly longer to start a game after moving /data to microSD. I am on stock rom and haven't updated after fstab modification. Sometimes there is "Updater has stopped" error 1 or 2 minutes after boot.
Pros:
prevents damage to EMMC NAND caused by writes as most reads/writes are from microSD.
easly increase storage by using larger sdcard.
Cons:
cannot use screen lock. phone will be unlocked always.
Phone may have issues after OS update. Or can't update at all. (I have not updated so cann't say)
stock fstab file:
###################################################################################################
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,avb
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,fileencryption=ice,quota,reservedsize=128M
/devices/platform/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/platform/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/devices/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/config /frp emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337,context=ubject_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait
###################################################################################################
Modified fstab file:
###################################################################################################
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,avb
# /dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,fileencryption=ice,quota,reservedsize=128M
/dev/block/mmcblk1p2 /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,quota,reservedsize=128M
# /devices/platform/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
# /devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/platform/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/devices/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/config /frp emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337,context=ubject_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait
###################################################################################################
{
"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"
}
How you root miui 10.2.7.0.Please tell me..
RsAbubokor3 said:
How you root miui 10.2.7.0.Please tell me..
Click to expand...
Click to collapse
I have not rooted my phone.
Hi, can you please do a tutorial? Because I need to do this to my redmi 7a, but i'm very new on all this. I'l be very thankful with you
LucianoApP said:
Hi, can you please do a tutorial? Because I need to do this to my redmi 7a, but i'm very new on all this. I'l be very thankful with you
Click to expand...
Click to collapse
I wrote all the steps in the post. you need:
1. usb sdcard reader.
2. 8 gb usb flash drive (for ubuntu OS)
3. ubuntu OS ( to set up sdcard.)
4. twrp.img available on this forum.
5. vbmeta.img available on this forum.
reply and I will guide you.