Database Users

Did Factory Reset in Custom Rom now i have a TWRP Bootloop. (Mediatek)

Hello Guys it´s me again. (i know im annoying )
Well, i did a Factory Reset in dotOS and it Rebooted into TWRP.
However, Normally a Phone would then Perform the Action in the Recovery but in this Case it did not do it. So i Reflashed the Rom.
After that it Rebooted into TWRP again. I Tried to Access the Bootloader with Vol Down + Power. That also Booted into TWRP. After that i Selected Bootloader in the TWRP Reboot Options. That Booted the Phone into the Mode where i Flashed the Recovery but it did not Give me the Options like META MODE, FACTORY MODE etc, when i tapped the Volume Buttons. Only a Black Background with White text Saying :
> FASTBOOT mode...
> device unlocked
I Tried to Restore my Stock TWRP Backup but that did not Solve the Issue. I also tried to Reflash dotOS but same issue.
What else Can i do to get this fixed ? I never had a Problem Like this on any Sony or Samsung Device i tinkered with. Thats why im asking that much.

@Marc_Xperia Do not forget to install no-verity-opt-encrypt zip file or simple disable *system verifier* in kernel ramdisk.

TheHitMan said:
@Marc_Xperia Do not forget to install no-verity-opt-encrypt zip file or simple disable *system verifier* in kernel ramdisk.
Click to expand...
Click to collapse
I Tried that but still no luck. Might Revert to stock and try it that why. If i can find the VCOM Driver...

Marc_Xperia said:
Hello Guys it´s me again. (i know im annoying )
Well, i did a Factory Reset in dotOS and it Rebooted into TWRP.
However, Normally a Phone would then Perform the Action in the Recovery but in this Case it did not do it. So i Reflashed the Rom.
After that it Rebooted into TWRP again. I Tried to Access the Bootloader with Vol Down + Power. That also Booted into TWRP. After that i Selected Bootloader in the TWRP Reboot Options. That Booted the Phone into the Mode where i Flashed the Recovery but it did not Give me the Options like META MODE, FACTORY MODE etc, when i tapped the Volume Buttons. Only a Black Background with White text Saying :
> FASTBOOT mode...
> device unlocked
I Tried to Restore my Stock TWRP Backup but that did not Solve the Issue. I also tried to Reflash dotOS but same issue.
What else Can i do to get this fixed ? I never had a Problem Like this on any Sony or Samsung Device i tinkered with. Thats why im asking that much.
Click to expand...
Click to collapse
It's very simple
-boot into recovery
-wipe
-advanced wipe
-clear / format cache & dalvik
-reboot _choose reboot recovery
-select mtp file transfer mode in twrp
-push LATEST* magisk zip
-push clean copy of dotOs
-then do FULL WIPE (all) but not your sd or internal sd/data
-install first dotOs zip
-install magisk zip
-wipe cache
-reboot
* If you fail check what is selected under the mount section & report back
If problem persists flash an older version of recovery using SPflashtools and then older version of dotOs with magisk
_do full wipe first
#some new recoveries had errors so make sure you are running ABSOLUTE latest or OLDEST version of twrp
# I haven't tried the last or latest version of dotOs yes ( older versions worked 100%)

KevMetal said:
It's very simple
-boot into recovery
-wipe
-advanced wipe
-clear / format cache & dalvik
-reboot _choose reboot recovery
-select mtp file transfer mode in twrp
-push LATEST* magisk zip
-push clean copy of dotOs
-then do FULL WIPE (all) but not your sd or internal sd/data
-install first dotOs zip
-install magisk zip
-wipe cache
-reboot
* If you fail check what is selected under the mount section & report back
If problem persists flash an older version of recovery using SPflashtools and then older version of dotOs with magisk
_do full wipe first
#some new recoveries had errors so make sure you are running ABSOLUTE latest or OLDEST version of twrp
# I haven't tried the last or latest version of dotOs yes ( older versions worked 100%)
Click to expand...
Click to collapse
Do you have Some Links on the ABSOULTE latest or OLDEST Version of TWRP ? I dont trust the one i Have anymore.
I Used this one : https://androidfilehost.com/?fid=890129502657592740

Marc_Xperia said:
Do you have Some Links on the ABSOULTE latest or OLDEST Version of TWRP ? I dont trust the one i Have anymore.
I Used this one : https://androidfilehost.com/?fid=890129502657592740
Click to expand...
Click to collapse
Download this tool .
https://www.androidfilehost.com/?fid=817550096634801704
Extract the .rar
Inside the folder there is recovery by XNlogos with zero errors
This tool can also inject recovery using fastboot or unlock bootloader in automated manner & flash custom boot( with verity encrypt DISABLED)

After first boot /data mount is gone in TWRP

I've got a SM-G950F, and succesfully flashed TWRP on it.
Wiped /data, after that i flashed dm-verity and force encryption disabler, everything was ok until the first boot into the system.
It booted up, and immediately after that i turned off the phone and booted into TWRP, and for some reason it couldnt mount /data again.
The tutorial i have followed:
Thanks for the tutorial to: jesec
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Click to expand...
Click to collapse
Before the 1st boot i even rooted the device, that remained after the first boot, but no /data mount.
After the 5th try, i gave up.
What could be the problem, or is this normal on this phone?

Are you using latest twrp version 3.2.3.2

I'm using 3.2.1.0

kristof889 said:
I'm using 3.2.1.0
Click to expand...
Click to collapse
Use latest twrp 3.2.3.2 should have data mount and quota issues fixed.
You can flash the .Img file through twrp or flash the .img.tar file with Odin.
After flashing reboot straight into twrp and repeat part 2 of the guide you quoted.
I would be interested to know also if in download mode if you have a line in there saying rmm state?
Twrp for s8 exynos
https://dl.twrp.me/dreamlte/

Installed the 3.2.3.2 version, but nothing has changed. after the first boot into system, TWRP says cant mount /data..
I dont have anything like rmm state in download mode.

kristof889 said:
Installed the 3.2.3.2 version, but nothing has changed. after the first boot into system, TWRP says cant mount /data..
I dont have anything like rmm state in download mode.
Click to expand...
Click to collapse
I am assuming you followed the instructions that you quoted in your first post.(mainly part 2) after flashing twrp
Did you format data in twrp - not wipe - this is needed to decrypt your phone.
Rebooted back into twrp.
Did you flash the no verity opt zip (version 6) - this will disable re encryption of your phone when booting back into system.
This should all be done before booting back into system otherwise your phone will re encrypt itself.

I am assuming you followed the instructions that you quoted in your first post.(mainly part 2) after flashing twrp
Did you format data in twrp - not wipe - this is needed to decrypt your phone.
Rebooted back into twrp.
Did you flash the no verity opt zip (version 6) - this will disable re encryption of your phone when booting back into system.
This should all be done before booting back into system otherwise your phone will re encrypt itself.
Click to expand...
Click to collapse
I formatted data, not just wiped it.
I have installed the no verity opt, the latest version.
Even after these, my phone reencrypted itself.

kristof889 said:
I formatted data, not just wiped it.
I have installed the no verity opt, the latest version.
Even after these, my phone reencrypted itself.
Click to expand...
Click to collapse
When do the errors occur ie: during backup,restore,flashing something.
When first starting twrp did you swipe to allow modifications or did you leave it as read only.

You mean, the data mount error?
If yes, immediately after the 2nd boot into TWRP, after the first boot into system. Before i do anything in twrp, i check the log (with the button on the lower right) and it creates a bunch of errors, all in contact with the data partition.
So i can even do a proper backup.
If i flash any zip, upon the next boot into system it says something like verify failed, cannot reboot your phone and it gives a button wich used to restore the phone from recovery, but now i cant even do that bcoz it cant mount /data and thus can restore the phone.

kristof889 said:
You mean, the data mount error?
If yes, immediately after the 2nd boot into TWRP, after the first boot into system. Before i do anything in twrp, i check the log (with the button on the lower right) and it creates a bunch of errors, all in contact with the data partition.
So i can even do a proper backup.
If i flash any zip, upon the next boot into system it says something like verify failed, cannot reboot your phone and it gives a button wich used to restore the phone from recovery, but now i cant even do that bcoz it cant mount /data and thus can restore the phone.
Click to expand...
Click to collapse
Still sounds like you device is still encrypted.
Doing a factory reset with twrp should work to restore your phone or at worst you can re-flash your firmware.
If you can in twrp FORMAT data again and flash the no verity zip use version 6 zip file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I would be curious to know in twrp in the mount menu what options are ticked as well.

After the fresh flash, it was not encrypted because i could access the internal storage, and data was mounted.
Now in TWRP system(read only), cache and dalvik is mounted, and internal storage says 0MB

kristof889 said:
After the fresh flash, it was not encrypted because i could access the internal storage, and data was mounted.
Now in TWRP system(read only), cache and dalvik is mounted, and internal storage says 0MB
Click to expand...
Click to collapse
What Android version are you on?
When you flashed twrp it should have asked you whether or not to ' swipe to allow modifications ' did you swipe to allow or not.
In the mount menu of twrp I have ticked/checked data,cache,SD card the option at the bottom to allow read only I have ticked - this does not stop me from doing backups but does stop me from restoring (data mount error ) so you can leave it unticked.
I would.like to know your steps for twrp installation (not the one you quoted in first post) as I screwed up when I first tried.

I attached the software information bellow.
I have not swiped to allow for system modifications

First steps were the followimg:
Install .tra with odin
Immediately reboot to twrp
No swipe for system modifications
Format data
Flash no dm verity v6
(Flash magisk)
Reboot to system

kristof889 said:
First steps were the followimg:
Install .tra with odin
Immediately reboot to twrp
No swipe for system modifications
Format data
Flash no dm verity v6
(Flash magisk)
Reboot to system
Click to expand...
Click to collapse
Ok basically you have missed a step as far as I can see
(When I did mine I did swipe to allow modifications )
After you have formated data you will need to reboot back into twrp ( use reboot menu in twrp )
Then flash the no verity zip and magisk
If using magisk I would try the latest version 18 it's working ok for me.
Then boot into system to see if everything ok
Then reboot into twrp and see if the data mount issue is fixed.

spawnlives said:
Ok basically you have missed a step as far as I can see
(When I did mine I did swipe to allow modifications )
After you have formated data you will need to reboot back into twrp ( use reboot menu in twrp )
Then flash the no verity zip and magisk
If using magisk I would try the latest version 18 it's working ok for me.
Then boot into system to see if everything ok
Then reboot into twrp and see if the data mount issue is fixed.
Click to expand...
Click to collapse
Thank you for your advice. I will try it in the following days and will post the result.

I fixed this by flashing Renovate ICE's ROM and selecting the TWRP included in the AROMA installer.
Can access storage on TWRP now with no issues.

CoreyOS said:
I fixed this by flashing Renovate ICE's ROM and selecting the TWRP included in the AROMA installer.
Can access storage on TWRP now with no issues.
Click to expand...
Click to collapse
But i want to use the stock rom.
Maybe if i flash Renovate rom and after that again the stock?

kristof889 said:
But i want to use the stock rom.
Maybe if i flash Renovate rom and after that again the stock?
Click to expand...
Click to collapse
Why stock???
It pretty much is stock, just you have full control over the apps preinstalled and you can change colours of various UI elements.
It's just easier to flash a zip than it is to flash via ODIN, then flash TWRP and keep trying over and over to get this result when I know this rom works fine with CTSprofile.
You will only need to flash TWRP once and copy the rom to your phone.
The rest is magic (AROMA)
I haven't really had to mess with anything and have just installed and used the HSBC banking app as if it were an official phone. (ROOTED and custom ROM and Recovery)
One extra step you could take is to use Magisk hide and point it to the app you want to hide root from.

CoreyOS said:
Why stock???
It pretty much is stock, just you have full control over the apps preinstalled and you can change colours of various UI elements.
It's just easier to flash a zip than it is to flash via ODIN, then flash TWRP and keep trying over and over to get this result when I know this rom works fine with CTSprofile.
You will only need to flash TWRP once and copy the rom to your phone.
The rest is magic (AROMA)
I haven't really had to mess with anything and have just installed and used the HSBC banking app as if it were an official phone. (ROOTED and custom ROM and Recovery)
One extra step you could take is to use Magisk hide and point it to the app you want to hide root from.
Click to expand...
Click to collapse
So on that rom i can use s health and all knox based apps like normal?
If yes, i will try it, it looks very nice

Bootlooped after install of Lineage, twice!

Hey all,
Phone is new to me, t-mo version. Did the international conversion, unlocked the bootloader, installed TWRP 3.3.1.1.img. All with minimal issues. Installed the 20200121 nightly of LOS successfully, but it powered off a few minutes after getting through the setup menu. Bootlooped. I may have gotten it out of the bootloop with the vol up+down trick from the msmdownloadtool trick, or something, cause I got the screen to turn off and left it for the night.
Tonight, the phone was totally dead, but I was able to start over with the (patched) msmtool I used initially. All good. Went through the same steps and got TWRP and LOS installed. This time I used last nights nightly 20200123. All set for a minute, before it bootlooped again.
Here's some details that might be useful:
The phone powered off after unplugging it. This is when the bootloop started, I can't be sure it was after dissconnecting each time, but at least the last time. The battery was >80%. I also managed to get it to boot into LOS after the most recent bootloop, for a few minutes, and it powered off without being connected or disconnected. So probably not related.
I did a system wipe, along with the format, as recommended in the LOS installation steps from them
The system wipe maybe wasn't a good idea??
I tried to sideload LOS.zip, which seemed to work fine according to my terminal, but it warned me that I had no OS installed when I went to reboot. So I adb pushed LOS and installed. I got the same no OS warning, but rebooted anyway this time. LOS started up fine, for a few minutes, before powering off and then looping.
Could I have 2 instances conflicting??
Nothing else installed yet, not root, magisk, or anything yet.
I shut it down this time with a vol up + power, which worked. I'm done for tonight, but I would appreciate any ideas on what may be causing this so I can give it a third go tomorrow.
Thanks!

try this
BeansBeanson said:
Hey all,
Phone is new to me, t-mo version. Did the international conversion, unlocked the bootloader, installed TWRP 3.3.1.1.img. All with minimal issues. Installed the 20200121 nightly of LOS successfully, but it powered off a few minutes after getting through the setup menu. Bootlooped. I may have gotten it out of the bootloop with the vol up+down trick from the msmdownloadtool trick, or something, cause I got the screen to turn off and left it for the night.
Tonight, the phone was totally dead, but I was able to start over with the (patched) msmtool I used initially. All good. Went through the same steps and got TWRP and LOS installed. This time I used last nights nightly 20200123. All set for a minute, before it bootlooped again.
Here's some details that might be useful:
The phone powered off after unplugging it. This is when the bootloop started, I can't be sure it was after dissconnecting each time, but at least the last time. The battery was >80%. I also managed to get it to boot into LOS after the most recent bootloop, for a few minutes, and it powered off without being connected or disconnected. So probably not related.
I did a system wipe, along with the format, as recommended in the LOS installation steps from them
The system wipe maybe wasn't a good idea??
I tried to sideload LOS.zip, which seemed to work fine according to my terminal, but it warned me that I had no OS installed when I went to reboot. So I adb pushed LOS and installed. I got the same no OS warning, but rebooted anyway this time. LOS started up fine, for a few minutes, before powering off and then looping.
Could I have 2 instances conflicting??
Nothing else installed yet, not root, magisk, or anything yet.
I shut it down this time with a vol up + power, which worked. I'm done for tonight, but I would appreciate any ideas on what may be causing this so I can give it a third go tomorrow.
Thanks!
Click to expand...
Click to collapse
(BASE STOCK ROM)
OnePlus6TOxygen_41_OTA_063_all_2001032024_215eea3f e7c64e37.zip (BETA4)
whatever the rom requires(10.3.0) however the Q beta 4 works just fine, havent found any real bugs / newer security patches etc.
(CUSTOM ROM)
Latest rom that will work with BASE and TWRP decryption
(latest TWRP )
twrp 3.3.1-31 zip
(Latest)
Magisk Canary . Zip
(Latest)
open_gapps - Q
(Latest)
custom compatible kernel
(Latest)
NanoDroid - with con/fig read alter installation notes
(&)
India_Fake_Partition_Deleter
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE / U WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MYNE)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
From dirty or clean system - to - clean flash
in cmd type
fastboot boot twrp.img
Install twrp installer.
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!)
install OOS(BETA4).zip / TWRP installer
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
Flash TWRP installer
- - reboot to recovery - -
Flash Magisk
BOOT UP System
- - reboot back to recovery - -
Choose Reboot Option / (CHANGE YOUR SLOT) / Back / Reboot Recovery
Flash Magisk.
Reboot system
SETUP ROM
/////////////////////////////////////\OPTIONAL/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- - REBOOT TO RECOVERY - -
----------------------------------------------------------------------------------------------------
STEP *( .=./ )*
Flash GAPPS
Flash India_Fake_Partition_Deleter
Flash NanoDroid (With prefered pre-configured setup/overlay/apps files placed)
Flash Custom Kernel
Re-Flash Magisk again
Click - WIPE DALVIK & Reboot system right after
------------------------------------------------------------------------------------------------------
- - REBOOT TO RECOVERY - -
Choose Reboot (CHANGE YOUR SLOT TO THE OPPOSITE SLOT)
- - REBOOT BACK TO RECOVERY - -
REPEAT STEP " *( .=./ )* "
-------------------------------------------------------------------------------------------------
GAME OVER
1up
THIS is EXTENSIVE but will work for any particular rom setup for a/b devices based on Q
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
just follow install guide download latest linageos and gapps from open gapps. and latest magisk and after flash gapps if you cannot sign into a google account then you need to factory reset both slot in system settings menu and then just reinstall magisk and kernel settings modules etc
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
just switch slots in cmd or via twrp and reboot system and factory reset wipe all via the settings in the booted system, not twrp

I'm a little slow..
I got the phone back to factory with the msmtool, so I'm ready to do this! I get the general idea, but for a few of these, can you ELI5. Thanks so much for taking the time to help me out.
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE / U WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MYNE)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
From dirty or clean system - to - clean flash
in cmd type
fastboot boot twrp.img
Install twrp installer. Do I just find the zip in the file structure in twrp and install? I'm at this step in twrp and I don't see how to install it. Previously I had `adb push twrp.img /storage/` so that I had a file I could find and install. If it's already there just from `fastboot boot twrp.img`, I can't seem to find it.
--solved this by pushing the twrp-intaller.zip to /storage, and then installing. It did the expected installation to both a/b
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
I went to `mount` and checked all the boxes. Then went back to `wipe advanced` and checked all those boxes. Now I'm stuck at the fastboot screen and can't boot or start. :crying:
I can't do a `fastboot boot twrp.img either. Any suggestions before I blow it away with the msmtool again??????
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!) How was I doing it wrong? Or do you mean that these steps just now are the only mounting that should be done?
install OOS(BETA4).zip / TWRP installer What command should I use to move it from my pc to the phone? `adb push .zip storage` ?
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer Do it twice, exactly the same? Is this so it's on both slots?
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage. What command should I use for copying? Like above `adb push <files> storage`?
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
[/COLOR]just follow install guide download latest linageos and gapps from open gapps. and latest magisk and after flash gapps if you cannot sign into a google account then you need to factory reset both slot in system settings menu and then just reinstall magisk and kernel settings modules etc
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
just switch slots in cmd or via twrp and reboot system and factory reset wipe all via the settings in the booted system, not twrp
Not sure what you mean by this part here. I wasn't planning on installing gapps. I'm confused about the reseting both slots. Is the idea that I did the install twice above, so that it's on both a/b slots and I'd have to reset both if there's a problem?
Click to expand...
Click to collapse

Problems with MIUI v11.0.4 and TWRP/Magisk

Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder

coder111 said:
Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder
Click to expand...
Click to collapse
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both

Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
zgfg said:
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both
Click to expand...
Click to collapse

coder111 said:
Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
Click to expand...
Click to collapse
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP: https://mega.nz/#F!hllnSIpA!amAG8moMYW_tG8r731Tzgg

Thanks for your help.
I tried the thing with Magisk Manager & boot image file, and it worked. I can live with stock recovery for now. I just needed root.
You saved me quite a bit of hassle. Thanks again.
zgfg said:
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP:
Click to expand...
Click to collapse

Can not install any Custom rom_ TWRP/OrangFox tested

I am trying to install some custom rom, below roms are tested and no way to done it:
Xtended, Pixel experience, PE, MSMXtended!!!
all of them is not possible to install via TWRP or OrangFox!
after zip installation in recovery mode, the device will be on loop on fastboot and/or recovery and nothing happening on this type of installation!
I tested to sideload system.img, boot.img etc...
any help will be welcome.

You NEED to "Format Data" (not "Wipe" > "/data", it's the "Format Data" button).
EDIT: You may need to install a good firmware too, just follow installation steps of the custom ROM...

Im having the same issue did the format fix it?

xxjahasotoxx said:
Im having the same issue did the format fix it?
Click to expand...
Click to collapse
Guide for install custom ROM
1- boot to recovery
2- select format and type "yes"
3- reboot recovery
4- now wipe data, catch, dalvik catch
5- install ROM and reboot
** Some ROM work only with global vendor. You must first install vendor zip file with twrp (or vendor img with fastboot comment in your pc/linux/mac)
For example: My Mi 9T firmware is (Russian Gobal). I got error when try install Pixel Experience Plus. I install Global Vender with TWRP, then install rom zip file without any problem. (I am on stock miui with locked bootloader now)