Database Develop

Are there 2 copies of /system on the phone?

My phone (3T) has an unlocked bootloader, is encrypted, not rooted, and running stock OOS 5.0.
I flashed TWRP and discovered that stock OOS restores the stock recovery in boot.
I saw the Oreo dm-verity thread by xenet, had a look at the zip file, noticed that it just modified fstab to prevent force encrypt, so I flashed it to see what happens.
And nothing happens. After the system had booted, fstab is unchanged from the original stock copy.
So I'm wondering whether this file is also restored when booting up on stock.
I get aggressive and go back to TWRP and delete /system/etc and /system/bin and modify build.prop.
Surely now the phone won't boot!
Wrong! It boots up and everything is back to normal in /system.
I go back to TWRP and have a look at /system and it shows me one without the etc and bin folders and has the modified build.prop.
What's going on? How can I see one version of /system in TWRP but a different version (ie, stock) when the phone has booted?
By the way I've been an Android user for many years and have rooted and flashed custom ROMs on a variety of phones and I've never seen anything like what's happening on my 3T. I'm sure that dm-verity is somehow involved in this.

Happened to me on my earlier OOS 5.0 attempts...
But i suspected Magisk is involved in my case.
I downloaded Magisk Module "System Terminal Debloater,"
remove some apps like Duo, Chrome, and Google Play Movies.
Some restarts, they magically re-appear again on Apps Drawer...
Haven't touch them yet again after....

nicknacknuke said:
Happened to me on my earlier OOS 5.0 attempts...
But i suspected Magisk is involved in my case.
I downloaded Magisk Module "System Terminal Debloater,"
remove some apps like Duo, Chrome, and Google Play Movies.
Some restarts, they magically re-appear again on Apps Drawer...
Haven't touch them yet again after....
Click to expand...
Click to collapse
Thanks.
I should have mentioned that I'm also not rooted. So stock OOS 5.0.
Sent from my OnePlus 3T using XDA Labs

When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?

Jackhass said:
When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?
Click to expand...
Click to collapse
No, I don't get that message because my phone is encrypted with a password. So the first thing I see in TWRP is the request for the password and then I'm presented with the menus.
However, in the Mounted menu, system isn't mounted and I have the option of mounting it in read-only mode.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
No, I don't get that message because my phone is encrypted with a password. So the first thing I see in TWRP is the request for the password and then I'm presented with the menus.
However, in the Mounted menu, system isn't mounted and I have the option of mounting it in read-only mode.
Click to expand...
Click to collapse
After first time flashing TWRP a folder gets created on your internal storage, with a hidden file called .twrps, go delete it and reboot recovery to trigger the message "allowing system modifications" on TWRP's first boot...
It's not about encryption, it's just that TWRP remember the decision you made due to the file I pointed out...
Sent from my OnePlus 3T using XDA Labs

Sam Nakamura said:
After first time flashing TWRP a folder gets created on your internal storage, with a hidden file called .twrps, go delete it and reboot recovery to trigger the message "allowing system modifications" on TWRP's first boot...
It's not about encryption, it's just that TWRP remember the decision you made due to the file I pointed out...
Click to expand...
Click to collapse
Somehow the attachment strikes on previous post
Edit: still not working, check your TWRP Folder on storage to find the file
Sent from my OnePlus 3T using XDA Labs

Sam Nakamura said:
Somehow the attachment strikes on previous post
Edit: still not working, check your TWRP Folder on storage to find the file
Click to expand...
Click to collapse
Thanks, you are correct. I'd forgotten that that TWRP remembers. Deleting .twrps does bring up the RO prompt after decrypting storage.
Jackhass said:
When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?
Click to expand...
Click to collapse
I had allowed changes to the system otherwise I couldn't have made changes to it, which includes the ability to restore the system partition.
But I'm still unclear why if I make changes to the system partition and boot with the stock kernel, then after the boot none of the changes are present in the system partition, but if I boot back into TWRP then the changes are all there.

I recall someone in another OOS 5 thread saying that the stock kernal replaces TWRP with stock recovery if you don't flash root (magisk/superSU). Is it possible that the kernel re-flashes system on boot? Another possibility is that TWRP thinks it's making changes to system but it's not actually? Not quite sure, I've never heard of anything like this before either, just throwing other ideas out there.
I've never read anything about the OP3T or any oneplus phones for that matter having A/B system partitions like the pixels. *shrug*

@nhshah7, something's like what you suggest must be going on to account for what I'm seeing. I'm hoping that someone can confirm my observations and provide a definite answer.

@BillGoss
My thread has been updated relating to all your queries...
Thank you...
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748

Xennet said:
@BillGoss
My thread has been updated relating to all your queries...
Thank you...
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Click to expand...
Click to collapse
Actually it doesn't explain how TWRP can make changes to system yet the phone boots up on an unmodified system if using the stock kernel. And then, when you boot back into TWRP and look at system, the changes are still there.
Where does the unmodified system come from?
Where does the modified system live?
Why doesn't modifying system result in a failed boot due to dm-verity, while restoring a backup of system does result in a failed boot?
So many questions with no answers.

BillGoss said:
....So many questions with no answers.
Click to expand...
Click to collapse
Not sure if this is applicable in your case but the following possibilities may be worth considering for you:
1. Are you sure that the system image is actually getting modified? If the system partition is not mounted before flashing the zip and the zip being flashed does not mount the system partition in read / write, then no changes to system partitions will actually be written.
2. If dm-verity is enabled, then restoring system could result in an error as this is different from restoring a system-image (nandroid copy of the whole partition and not just the files in the system partition). DM-verity can be triggered if the files are all the same but the dm-verity signature computed by hashing the system partition has changed.
3. For boot partitions, strange behaviour can occur if remnants of the previous boot.img are still in the partition (...e.g. if the previous boot.img was of larger size and a new boot.img of a smaller is flashed, then there will be some bytes after the new boot.img that are from the previous boot.img). To verify this, format the boot partition from fastboot and see if you notice anything different with the new boot.img.
4. In Oreo / 8.0, dm-verity flags are stored in dtb (device tree blobs) inside the kernel and not in the fstab file. Only data encryption can be changed from the fstab file and dm-verity needs to be changed from changing the dtb (...Magisk beta v1456 and SuperSu 2.82 SR4 do this, I think).

rk2612 said:
Not sure if this is applicable in your case but the following possibilities may be worth considering for you:
1. Are you sure that the system image is actually getting modified? If the system partition is not mounted before flashing the zip and the zip being flashed does not mount the system partition in read / write, then no changes to system partitions will actually be written.
2. If dm-verity is enabled, then restoring system could result in an error as this is different from restoring a system-image (nandroid copy of the whole partition and not just the files in the system partition). DM-verity can be triggered if the files are all the same but the dm-verity signature computed by hashing the system partition has changed.
3. For boot partitions, strange behaviour can occur if remnants of the previous boot.img are still in the partition (...e.g. if the previous boot.img was of larger size and a new boot.img of a smaller is flashed, then there will be some bytes after the new boot.img that are from the previous boot.img). To verify this, format the boot partition from fastboot and see if you notice anything different with the new boot.img.
4. In Oreo / 8.0, dm-verity flags are stored in dtb (device tree blobs) inside the kernel and not in the fstab file. Only data encryption can be changed from the fstab file and dm-verity needs to be changed from changing the dtb (...Magisk beta v1456 and SuperSu 2.82 SR4 do this, I think).
Click to expand...
Click to collapse
I'll come back to 1.
2. That makes sense and accounts for why a restore of the system partition with the stock boot image causes me to get dumped back in fastboot mode. If I flash the stock system zip file then the system boots properly.
3. I've not had any issues with strange boot behaviour. I'm always starting with stock or flashing kernels that modify the stock boot image, like Blu Spark.
4. I gathered this from my reading of various threads. If I want to make changes to the system partition and get them to stick and not fail dm-verity then I have to flash a custom kernel. I've proven this in my testing. (A rooting solution would also work, but I've not done this).
Back to 1:
Here's what I've done:
Starting with pure stock image (flash OOS 5.0).
Boot into fastboot and flash TWRP.
Boot into recovery.
Mount system as rw. (In ro mode the next step fails)
Delete the bin, etc, and lib folders in system using the TWRP file manager. (Screenshot a)
Reboot system.
... First interesting fact ...
System boots ok, deleted folders are present in file manager. (Screenshot b)
Boot into fastboot and flash TWRP. (Booting with stock restores stock recovery)
Mount system.
... Second interesting fact ...
TWRP file manager shows that deleted folders are missing. (Screenshot c)
Flash custom kernel or patched boot image
Reboot system
... Third interesting fact ...
System fails to boot. Hangs on splash screen.
So TWRP made the changes (otherwise how could they be visible between reboots, including a replacement of recovery) and I only did them once.
Yet they don't actually take effect until I replace the stock boot image.
So, where are the changes hiding? What did TWRP actually change?
Screenshots (note that TWRP has the wrong timezone set so the time shown is wrong):

BillGoss said:
....
Back to 1:
Here's what I've done:
Starting with pure stock image (flash OOS 5.0).
Boot into fastboot and flash TWRP.
Boot into recovery.
Mount system as rw. (In ro mode the next step fails)
Delete the bin, etc, and lib folders in system using the TWRP file manager. (Screenshot a)
Reboot system.
... First interesting fact ...
System boots ok, deleted folders are present in file manager. (Screenshot b)
Boot into fastboot and flash TWRP. (Booting with stock restores stock recovery)
Mount system.
... Second interesting fact ...
TWRP file manager shows that deleted folders are missing. (Screenshot c)
Flash custom kernel or patched boot image
Reboot system
... Third interesting fact ...
System fails to boot. Hangs on splash screen.
So TWRP made the changes (otherwise how could they be visible between reboots, including a replacement of recovery) and I only did them once.
Yet they don't actually take effect until I replace the stock boot image.
So, where are the changes hiding? What did TWRP actually change?
Screenshots (note that TWRP has the wrong timezone set so the time shown is wrong):
Click to expand...
Click to collapse
Some more thoughts for you to consider:
1. Have you tried this with the official TWRP recovery version 3.2.0-0?
2. Is there anything inside the folders that you see using the file manager after a regular boot? Folders of same name may exist in the boot ramdisk and these are merged with system folders after boot.
3. Try wiping cache between reboots and see if that changes any of your observations.

rk2612 said:
Some more thoughts for you to consider:
1. Have you tried this with the official TWRP recovery version 3.2.0-0?
2. Is there anything inside the folders that you see using the file manager after a regular boot? Folders of same name may exist in the boot ramdisk and these are merged with system folders after boot.
3. Try wiping cache between reboots and see if that changes any of your observations.
Click to expand...
Click to collapse
Good questions. They got me thinking more about how this could possibly work.
I had a look at the cache and there's definitely no copy of the system hiding there.
I also unpacked the ramdisk in the boot image and it had nothing in system. Furthermore, the boot position is only 64 MB, no where near enough to hold the system.
Then I installed Magisk so that I could browse around the phone's partitions and take copies.
I learnt two things from this:
1. If there's a second copy of the system there are only three partitions large enough to hold it (/proc/partitions shows the sizes in 1 kB blocks). The system is about 1 GB. There is space in the system partition (sde20) for 3 GB. There's also space in the data partition (sca15). And there's space in the major partition holding the modems (sdf).
I could eliminate the data partition by formatting it but restoring the internal storage (sdcard) is such a a pain.
So I'll just accept that there is space for a copy, but I'm unlikely to find out exactly where.
2. When I had Magisk installed installed and the system boot, I added a folder and file to /system/priv-app using a file manager (so not using TWRP). I then booted into recovery, flashed the stock boot image, and rebooted. I was expecting it to fail dm-verity (modified system) but it didn't. After booting up there's no evidence of the folder I added to priv-app.
And if I restore the Magisk boot image then the additions show up again.
I'm actually very impressed with how the stock system (kernel, recovery, system) protects itself from modification. Very cool!

[HELP] [URGENT] ONLY OxygenOS not Booting up !!!!

Hi guys
I am having a weird issue , I am able to flash ANY custom ROM ( mark my words "any") be it skydragon os, havoc os, lineage os but I am unable to flash OxygenOS (tried 5.0.7 and 5.0.8) . When I start the first boot after flashing the OOS zip file, it always get stuck on boot animation and the animation goes on forever. Please Help !!!!!
Note:
- Have tried with different versions of TWRP but no success
- Always Did a clean install
- When after being stuck at boot animation for 40 mins , i FORCE restarted my phone to recovery and found that all system files and folders have been made as normally so i think there was no error in flashing process but still ROM not booting up.
Also:
- If someone has successfully booted the latest OOS from scratch ( I mean clean install) so please can you provide your ( links !)
1. TWRP file
2. OOS zip file

PreciousPulkit said:
Hi guys
I am having a weird issue , I am able to flash ANY custom ROM ( mark my words "any") be it skydragon os, havoc os, lineage os but I am unable to flash OxygenOS (tried 5.0.7 and 5.0.8) . When I start the first boot after flashing the OOS zip file, it always get stuck on boot animation and the animation goes on forever. Please Help !!!!!
Note:
- Have tried with different versions of TWRP but no success
- Always Did a clean install
- When after being stuck at boot animation for 40 mins , i FORCE restarted my phone to recovery and found that all system files and folders have been made as normally so i think there was no error in flashing process but still ROM not booting up.
Also:
- If someone has successfully booted the latest OOS from scratch ( I mean clean install) so please can you provide your ( links !)
1. TWRP file
2. OOS zip file
Click to expand...
Click to collapse
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs

BillGoss said:
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Exactly How Much Time can the re-encryption process could take?? Cause I gave it good 1 hour
Also to make sure i am getting it right , you mean to say that i should use the TWRP file you mentioned below your statement
"-------update 2" or is it some (img file) that i need to flash through TWRP

BillGoss said:
If you're coming from a decrypted data partition and then flash stock OOS and nothing else, it will re-encrypt your data. This could take a long time.
I recently did some testing of TWRP for fixing formatting and decryption (see https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78339714) and I did a totally clean install of OOS including formatting the data partition.
I used a TWRP version from this post https://forum.xda-developers.com/on...al-twrp-touch-recovery-t3742894/post78332159. The one I used is the very last one which is described as:
-----update2
This one fixes ext4 encryption on Pie: https://androidfilehost.com/?fid=11410963190603866112
PS: you can get the OOS 5.0.8 zip from https://www.oneplus.com/au/support/softwareupgrade
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
To Avoid Any Further Confusion , Could You Give me step by step instructions for what to do , please?
Please also give me details to which TWRP to use and all the configurations ( like ext4 or f2fs on system or data , whether to use format button, or advanced wipe) all that! Thanks in advance

Issue solved !!
How I solved ?
1. Using TWRP 3.2.2-0 I first Formatted data.
2.Then used advanced wipe to clean everything.
3.Then using change file system option in WIPE category changed my "data" partition from whatever to f2fs.
4.Then changed back to ext4.
5.Then changed back to f2fs.
6.Using PC transferred OOS zip file (5.0.8) to internal storage.
7.Flashed The file
8.Bingo !!! Phone booted up without a problem
Thanks @BillGoss , your provided links helped alot, though i used nothing from it but they helped me to recognize what the problem was, it was i think an encyption as well as changed file system format issue due to my previous flashing of pie roms.:good:

PreciousPulkit said:
How I solved ?
1. Using TWRP 3.2.2-0 I first Formatted data.
2.Then used advanced wipe to clean everything.
3.Then using change file system option in WIPE category changed my "data" partition from whatever to f2fs.
4.Then changed back to ext4.
5.Then changed back to f2fs.
6.Using PC transferred OOS zip file (5.0.8) to internal storage.
7.Flashed The file
8.Bingo !!! Phone booted up without a problem
Thanks @BillGoss , your provided links helped alot, though i used nothing from it but they helped me to recognize what the problem was, it was i think an encyption as well as changed file system format issue due to my previous flashing of pie roms.:good:
Click to expand...
Click to collapse
Well done. And because you worked this out yourself, you've learnt a lot.
Sent from my OnePlus3T using XDA Labs

[guide] steps to flash gsi on redmi note 7

[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]​
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this

shouldn't you be flashing disable_encrypt zip too?

repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside

PROdelision said:
shouldn't you be flashing disable_encrypt zip too?
Click to expand...
Click to collapse
No, its not required.
chiplovez9x said:
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
Click to expand...
Click to collapse
Make sure you have allowed modifications on system partition and also you dont have system as read only.

Does fingerprint working on GSI?

what is gsi?

I don't know much but gsi means u can flash almost all roms (which have images). And most of ROMs do have gsi images.. So u can install any rom on your phone. I don't know the steps to do so.. ?

bryanngapopala said:
what is gsi?
Click to expand...
Click to collapse
Simple speaking it's a image with clear android from google

Has anyone tested RR PIE GSI on RN7? Does it work?

Is it possible to boot Android O GSI? :silly:

letsmakecakes said:
No, its not required.
Click to expand...
Click to collapse
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.

Is the. Method the same for the global version with global rom?

letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]​
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Which GSI should be needed to take? A-only or A/B ?

PROdelision said:
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Click to expand...
Click to collapse
I have no experience with GSI images, but I know in general that PIE breaks the encryption, if you roll back the security patch level. I don't know it this happened in your case, but I have lost couple of times my encrypted storage when I have tried to restore a backup of rom with older android patch level. After that, the bootup encryption pin is no longer accepted, neither by android nor by twrp, so the only option is to format data to remove encryption and start from scratch.
Were your miui beta and rr gsi of the same android security patch level?

Getting WRONG PIN error after setting up pin ???

letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Hi!
Did you not disable dm-verity and force-encryption?
Another question, the dev MIUI roms contain both the system and vendor partitions, right? How do you install only the vendor partitions from them? Or do you just flash MIUI and then reflash the custom ROM system? In that case, won't that affect dm-verity and encryption on the data partition?

Flashing correctly a GSI like in this guide; with vendor ecc ecc, will gcam work? Actually i'm on stock MIUI 10 and obv all working fine with a perfect version. My doubt is it.

Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?

any recommended gsi rom with no bug?

booladi said:
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Did you not erase your /data partition through TWRP?
Click to expand...
Click to collapse
I did wipe userdata but not internal storage. heard its because i have unencrpyed data partition?

Update Xiaomi.eu manually?

Hi
I have a problem with my twrp recovery when i want update the rom via updater app and i choose file package then reboot to update it will show twrp logo then it reboot again and twrp logo display again and twrp open normally without updating anything, im on 9.8.15 and wanna install 9.8.22 ,i installed twrp and the rom with this guide https://forum.xda-developers.com/Mi-9/how-to/guide-how-flashed-twrp-xiaomi-eu-rom-t3912952[/URL] is that twrp img wrong ?
If yes show me the right one
If no tell me what should i wipe while i install the rom ? System,data,dalvik,cache.... ???

It sounds like your device is encrypted, so you need to format the device before installing anything. Make sure to have the latest TWRP installed (you can find it in another thread) and afterwards you can install whatever you want.

when you boot into TWRP, can you see files and folders or can you see foldernames with alot off numbers?
if the second is the case, yeah you are encrypted and need to format data in TWRP.
first you can copy and save all the needed data in normal use off the phone or usb otg, or aus cable connected to laptop

catalindobre said:
It sounds like your device is encrypted, so you need to format the device before installing anything. Make sure to have the latest TWRP installed (you can find it in another thread) and afterwards you can install whatever you want.
Click to expand...
Click to collapse
I formated it before like in the guide said!
When i was in global i installed twrp then inside twrp i did format data then facrory reset then i installed eu , do i need to do that again ??

marcel112 said:
when you boot into TWRP, can you see files and folders or can you see foldernames with alot off numbers?
if the second is the case, yeah you are encrypted and need to format data in TWRP.
first you can copy and save all the needed data in normal use off the phone or usb otg, or aus cable connected to laptop
Click to expand...
Click to collapse
Yeah i dont see my folders like downloads android and others i just see 6 or 7 folders with lots of numbers and letters, but i formated data before i install the eu version do i need to do that again ? Will that change it to normal ?

sounds like encryption, most likely you've deleted the system and the device became encrypted again. format it again and then copy the installation files in the device . after this follow normal installation steps.

REALME X2 PRO (CN version) bricked... TWRP backup.

Hi , guys.
I have bricked my real x2 pro (CN version).
I tryed to restore several ways (MSMDOWNLOAD, QPST, QFiL) , but none of them leaded me success.
The frail possibility is It still works in TWRP mode.
So maybe it is impudent favor to ask you,
Can someone give me the clean backup of its system etc. of TWRP ?
It seems to me the final way to resolve this problem.:crying:

You try this, install twrp-3.3.1-12-RMX1931-mauronofrio.img , flash official ozip file with this version twrp, then fastboot official recovery.img, clear data under official recovery. this work for me. but I lost modemst1 modemst2 fsg persist partition( bakcup and restore with Chinese version twrp 3.3.1-1107 zwsx), and brick my x2 pro too.

Thank you, friend !
The official .ozip is chinese version ?
I could'nt find one than for RMX1931EX.
I already tried to flash it from TWRP.
But it is for RMX1931EX not for RMX1931 (installer showed me just 1931, no EX nor CN), so I could'nt.

yox2580 said:
Thank you, friend !
The official .ozip is chinese version ?
I could'nt find one than for RMX1931EX.
I already tried to flash it from TWRP.
But it is for RMX1931EX not for RMX1931 (installer showed me just 1931, no EX nor CN), so I could'nt.
Click to expand...
Click to collapse
the official ozip for RMX1931CN chinese version is this:
https://www.realme.com/support/software-update
direct link is:
https://download.c.realme.com/osupdate/RMX1931_11_OTA_0130_all_3jeZN7pIEWts_local.ozip

yox2580 said:
Thank you, friend !
The official .ozip is chinese version ?
I could'nt find one than for RMX1931EX.
I already tried to flash it from TWRP.
But it is for RMX1931EX not for RMX1931 (installer showed me just 1931, no EX nor CN), so I could'nt.
Click to expand...
Click to collapse
Flash the ozip
Rename system root to system
Flash the cn fw via fastboot enjoy
Sent from my RMX1931 using Tapatalk

I tried to flash CN rom from TWRP.
Not successed.
flash the ozip
failed saying ,For RMX1931CN not for RMX1931.
TWRP version is twrp-3.3.1-12-RMX1931-mauronofrio.
I'm sure my phone is CN version.
I just want clean backup file of system by TWRP...

Try changing file system in advanced wipe from ext 4 > ext 2 then back to ext 4 before flashing CN ozip.

chino1234 said:
Try changing file system in advanced wipe from ext 4 > ext 2 then back to ext 4 before flashing CN ozip.
Click to expand...
Click to collapse
thx ,
Now I tried .
'sysyem_root' and 'vendor' files
advanced wipe format ext4 →ext2 →ext4
then flash ozip.
Same resulted...
Didn't I do correctly ?

https://fixerrorcode.com/status-error-7-in-twrp-recovery/
maybe this will help you out.

Hi,
Now I dont know how to overwrite recovery image from PC.
The phone doesnt be accessed in debugging mode.
Just external memory of PC.
And my phone wakes only in TWRP.
So for flashing, I send files from PC to twrp folder of my phone.
This is why I begged for the backup of system by TWRP.

Dude if you would follow my unbrick guide your phone would work
---------- Post added at 03:39 AM ---------- Previous post was at 03:36 AM ----------
Fix
natedogg20050 said:
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.
Click to expand...
Click to collapse

I have resored my phone after install the official .ozip file with OTG, and everything went back. then I tried follow:
install magsick 20.3, reboot, worked.
install opengapps, brick too.

springwind said:
I have resored my phone after install the official CN versiom .ozip file with OTG, and everything went back. then I tried follow:
install magsick 20.3, reboot, worked.
install opengapps, brick too.
Click to expand...
Click to collapse
BTW, I install the official ozip file with offcial recovery.