Database Develop

Magisk 19.1 KILLED my Note 7 4/128 Gb

Stock rom, bought Note 7 4/128 Gb 2 weeks ago and waited till yesterday to unlock bootloader. Without using the phone.
Finally... Flashed TWRP but understood that with stock rom, every time I reboot to system, stock recovery replaces my TWRP.
So... Today I've flashed MAGISK 19.1 and yeah, TWRP remains every time... But...
EVERY TIME I REBOOT INTO SYSTEM, PHONE REQUIRES 4 MINUTES !!!! It stays on Redmi logo, with sign "Unlocked" in the bottom of the screen for more than 3 minutes... Damn And now? What to do?

Download a fastboot flash file for redmi note 7 and flash it via miflash your problem should be fixed
but your bootloader will be locked again
and twrp will be gone

@engloa wrong category

anikbarai123 said:
Download a fastboot flash file for redmi note 7 and flash it via miflash your problem should be fixed
but your bootloader will be locked again
and twrp will be gone
Click to expand...
Click to collapse
R u joking man ?! For what? For waiting other 15 or 30 days in order to unlock again the bootloader? And try again to root this damned phone obtaining this same result? Rather I'll put it in the trash and buy another one, maybe a decent phone this time.
zhad0ws said:
@engloa wrong category
Click to expand...
Click to collapse
Sorry, u've right. I've reported my tread in order to let moderators move it. :good:

PYCON said:
Stock rom, bought Note 7 4/128 Gb 2 weeks ago and waited till yesterday to unlock bootloader. Without using the phone.
Finally... Flashed TWRP but understood that with stock rom, every time I reboot to system, stock recovery replaces my TWRP.
So... Today I've flashed MAGISK 19.1 and yeah, TWRP remains every time... But...
EVERY TIME I REBOOT INTO SYSTEM, PHONE REQUIRES 4 MINUTES !!!! It stays on Redmi logo, with sign "Unlocked" in the bottom of the screen for more than 3 minutes... Damn And now? What to do?
Click to expand...
Click to collapse
Question: do you have a bootloop? Or does your phone simply need 4 minutes to boot up? If so where is the problem?
EZ solution: flash xiaomi.eu rom (which is way better) or flash another AOSP project.
If you really want to stay on stockrom: take the stockrom.zip -> remove the "verification.zip (or whatever it is called)" within the stockrom.zip and flash it via twrp.
Also: you should be able to flash the stockrom fastboot file without locking your bootloader again (since this only happens if you execute respective batch file).
I have magisk 19.1 installed and nothing is bricked, your thread is very misleading. Modding your device to hell and back isn't that difficult! ^^
Edit: when I flashed twrp first my device got encrypted (with no password setup). Everything can be fixed after a while.

MarvinMe said:
Question: do you have a bootloop? Or does your phone simply need 4 minutes to boot up? If so where is the problem?
EZ solution: flash xiaomi.eu rom (which is way better) or flash another AOSP project.
If you really want to stay on stockrom: take the stockrom.zip -> remove the "verification.zip (or whatever it is called)" within the stockrom.zip and flash it via twrp.
Also: you should be able to flash the stockrom fastboot file without locking your bootloader again (since this only happens if you execute respective batch file).
I have magisk 19.1 installed and nothing is bricked, your thread is very misleading. Modding your device to hell and back isn't that difficult! ^^
Edit: when I flashed twrp first my device got encrypted (with no password setup). Everything can be fixed after a while.
Click to expand...
Click to collapse
Question: do you have a bootloop? => NO
Or does your phone simply need 4 minutes to boot up? => YES
If so where is the problem? => these 4 minutes to boot up this phone... that's the problem, I think it's sufficient no?
It doesn't matter what rom I'm using but I need 48 MPixel working so, I suppose, or Global or EU. Not AOSP based. It's correct?
EDIT : just to be more specific... Stock camera app doesn't open anymore after flashing Magisk I get simply a black screen.

PYCON said:
Question: do you have a bootloop? => NO
Or does your phone simply need 4 minutes to boot up? => YES
If so where is the problem? => these 4 minutes to boot up this phone... that's the problem, I think it's sufficient no?
It doesn't matter what rom I'm using but I need 48 MPixel working so, I suppose, or Global or EU. Not AOSP based. It's correct?
EDIT : just to be more specific... Stock camera app doesn't open anymore after flashing Magisk I get simply a black screen.
Click to expand...
Click to collapse
Hi, thanks for the quick reply.
I have a very special tincture for you (except your really like it between scylla and charybdis):
Rom
Debloating - you can delete pretty much everything
#Feel free to flash magisk afterwards
#In case you get and error while completing the setup wizzard: just restart it without having wifi enabled and you are good.
#Best Google camera mod (everything works + focus tracking n'stuff)
It's worth it: I've been on the Stock rom side for years but I think MIUI is superior (GCAM > MIUI cam but doesn't matter) "and all of it just works :fingers-crossed:"
Edit: all of your data will be lost & you have to do the setup of your device again but trust me: it'll be so worth it ^^ just amazing
Follow the instructions on xiaomi.eu (<ROM> link) carefully and you are good.

MarvinMe said:
Hi, thanks for the quick reply.
I have a very special tincture for you (except your really like it between scylla and charybdis):
Rom
Debloating - you can delete pretty much everything
#Feel free to flash magisk afterwards
#In case you get and error while completing the setup wizzard: just restart it without having wifi enabled and you are good.
#Best Google camera mod (everything works + focus tracking n'stuff)
It's worth it: I've been on the Stock rom side for years but I think MIUI is superior (GCAM > MIUI cam but doesn't matter) "and all of it just works :fingers-crossed:"
Edit: all of your data will be lost & you have to do the setup of your device again but trust me: it'll be so worth it ^^ just amazing
Follow the instructions on xiaomi.eu (<ROM> link) carefully and you are good.
Click to expand...
Click to collapse
I'll try this EU rom, hope it'll work fine again Thx for the moment man.

PYCON said:
I'll try this EU rom, hope it'll work fine again Thx for the moment man.
Click to expand...
Click to collapse
In case you need help feel free contact me (DM) ^^ always glad to help :highfive:
Cheers!

https://forum.xda-developers.com/re...oot-redmi-note-7-one-click-root-tool-t3925785
or you can try this. installed twrp and magisk v19 without hassle.
note that everything gets wiped after, but you are ok since you said you didn't use your phone yet.

Did you disable verified boot by flashing dmverity zip? I think that could be causing the problem.

mtencarguez said:
https://forum.xda-developers.com/re...oot-redmi-note-7-one-click-root-tool-t3925785
or you can try this. installed twrp and magisk v19 without hassle.
note that everything gets wiped after, but you are ok since you said you didn't use your phone yet.
Click to expand...
Click to collapse
Thx but why use Rooter? Magisk should do this job...
agenius5 said:
Did you disable verified boot by flashing dmverity zip? I think that could be causing the problem.
Click to expand...
Click to collapse
No! Really? Where's written this step?! Did u try this? In the tread of unlocking bootloader, TWRP and so on, this step is not shown or I haven't seen

PYCON said:
Thx but why use Rooter? Magisk should do this job...
it's a 1-click rooter. if you want root use this. you don't have to do anything but plug your phone to your computer, go to bootloader and click. it installs twrp 3.3 and magisk v19. hassle free, that's what it is.
Click to expand...
Click to collapse

mtencarguez said:
it's a 1-click rooter. if you want root use this. you don't have to do anything but plug your phone to your computer, go to bootloader and click. it installs twrp 3.3 and magisk v19. hassle free, that's what it is.
Click to expand...
Click to collapse
Ok, first I'll try with Xiaomi EU rom but then I'll try this too.
I hope that there's a way to unbrick the phone if something goes wrong

No, I have to wait 2 more days. I used to flash it with redmi 5a. I don't know why this step is not there with rn7.

Just some little info, before flashing EU.
1) EU tutorial reports to wipe Dalvik / Cache / Data but NOT System before flashing rom... Really?! So strange
2) If Magisk involves issues, maybe it's possible to use SuperSU instead. Or not? It's too old?
3) If after flashing EU rom something goes wrong, my Bootloader remains unlocked? Or not? Just to be sure.
4) If after flashing EU rom something goes wrong, my TWRP will remain? In order to try other ways.
5) If after flashing EU rom something goes wrong, it's possible to restore a Nandroid backup with TWRP? All partitions? Or I've to skip some partition?

PYCON said:
Just some little info, before flashing EU.
1) EU tutorial reports to wipe Dalvik / Cache / Data but NOT System before flashing rom... Really?! So strange
2) If Magisk involves issues, maybe it's possible to use SuperSU instead. Or not? It's too old?
3) If after flashing EU rom something goes wrong, my Bootloader remains unlocked? Or not? Just to be sure.
4) If after flashing EU rom something goes wrong, my TWRP will remain? In order to try other ways.
5) If after flashing EU rom something goes wrong, it's possible to restore a Nandroid backup with TWRP? All partitions? Or I've to skip some partition?
Click to expand...
Click to collapse
1) it's not strange at all, as xiaomi.eu ROM is a system partition image. So no need to wipe a partition that will be overwritten seconds later.
2) no doubt your issue happened after you flashed magisk, as you stated it, but magisk is most probably not the main cause of the issue. It's the safest way to get root, SuperSU should not be used/trusted anymore as it is not maitained by chainfire anymore (iirc he sold his app long ago to some company)
I'm currently using my rn7 4/64 xiaomi.eu + magisk 19.1 with no issue nor boot delay.
Before that I had global eeu stock rom.
Xiaomi.eu is based on Xiaomi stock, but is not provided by Xiaomi, so it's actually more a custom rom than stock, so...
3) bootloader will stay unlocked
4) TWRP will stay there
5) I don't know, I did not do it yet. I would not overwrite any partition other than system, data and cache without knowing exactly what I'm doing

Well, firstly... Thank u all :good:
It seems I solved. I've followed these steps:
* boot into TWRP
* from TWRP, Format Data
* reboot into TWRP
* from TWRP, Full Wipe ( Dalvik / Cache / Data / System )
* copy Xiaomi EU ZIP into Internal Memory ( TWRP MTP ) => Release 9.4.25
* copy Magisk into Internal Memory ( TWRP MTP ) => Release 19.1
* from TWRP, flash Xiaomi EU ZIP
* reboot System
* configure initial setup wizard ( language, country, etc )
* reboot into TWRP
* from TWRP, flash Magisk ZIP
* from TWRP, Wipe ( Dalvik / Cache )
That's all. System boots in few seconds, as normal :highfive:
* ROOT => OK
* TWRP => remains (OK)
* BOOTLOADER => remains unlocked (OK)

PYCON said:
Well, firstly... Thank u all :good:
It seems I solved. I've followed these steps:
* boot into TWRP
* from TWRP, Format Data
* reboot into TWRP
* from TWRP, Full Wipe ( Dalvik / Cache / Data / System )
* copy Xiaomi EU ZIP into Internal Memory ( TWRP MTP ) => Release 9.4.25
* copy Magisk into Internal Memory ( TWRP MTP ) => Release 19.1
* from TWRP, flash Xiaomi EU ZIP
* reboot System
* configure initial setup wizard ( language, country, etc )
* reboot into TWRP
* from TWRP, flash Magisk ZIP
* from TWRP, Wipe ( Dalvik / Cache )
That's all. System boots in few seconds, as normal :highfive:
* ROOT => OK
* TWRP => remains (OK)
* BOOTLOADER => remains unlocked (OK)
Click to expand...
Click to collapse
can you give me the link of "Xiaomi EU ZIP " file you used, i can't find that !?

aka70 said:
can you give me the link of "Xiaomi EU ZIP " file you used, i can't find that !?
Click to expand...
Click to collapse
Yes, I think it's possible to post links of Xiaomi EU here.
10.4 Release is 9.4.25 => https://xiaomi.eu/community/threads/9-4-25-26.50275/
Older releases, like 10.3 => https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-10-3-stable-release.47170/

Complete setup of Lineage OS

Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Unlock and flash recovery
Backup
Format Data! (It's important if you come from Miui)
Install Q Firmware + vendor
Install LineageOS followed by gapps
Reboot into system and setup device.
Reboot into recovery and flash magisk
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
I also dont know if its possible to get recovery and rom on android 10 versions.
Thanks

Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk

BJack0 said:
Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Flash a custom recovery
Create a backup
Root???
Install LineageOS
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
Thanks
Click to expand...
Click to collapse
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
You could also check LOS thread: Here and here
Remember:
Chinese firmware: Widevine L3 and NFC support
Indian firmware: Widevine L1 but no NFC support

ishaqtkr said:
Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
They may work as it but I was just wondering if anyone could go into more detail or if there was a better approach and from what Kollachi said there clearly is a better way that what I said.

Since I'm in stock ROM and haven't ever flashed AOSP ROM in this phone I'll just back off lol
Sent from my Redmi K20 Pro using Tapatalk

Kollachi said:
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
Click to expand...
Click to collapse
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it

Any of the two recoveries will work. Q firmware means Android Q. Wile data/cache dalvik that's it. Regarding firmware, there's a clear topic of Lineage OS in K20 Pro forum which is still in unofficially state
Sent from my Redmi K20 Pro using Tapatalk

BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
1. You can take what you want. Orangefox is based on TWRP.
2. Format data is needed if you come from miui. If you did it you are good to go. But it wouldn't be false to wipe system, dalvic, cache
3.https://downloads.akhilnarang.me/MIUI/raphael/ --> Take 10.4.6.0 or 10.4.8.0 (Android 10 = Q)
4. No there is no specific version.

BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
I would recommend the latest TWRP from here
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
https://forum.xda-developers.com/k20-pro/development/rom-lineageos-17-0-t3976469/post80406191

Robbo.5000 said:
I would recommend the latest TWRP from here
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
Click to expand...
Click to collapse
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE

BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.

Kollachi said:
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.
Click to expand...
Click to collapse
Yes flashing the whole fastboot ROM does add the risk, if you forget to change the flash option, but you are guaranteed a clean slate and so less likely to have any niggling issues that nobody else has. I would bet large sums of money that many of the issues you see on here, where only one person has some problem and everyone else is fine, would be solved by fastboot flashing MIUI before installing the ROM of choice.
If you know what you're doing and know when you'll be OK with what you've got and know when it's best to start clean, then going with the vendor and firmware is easier.
But if your unsure and new to flashing on Android phones, I will always suggest go with the overkill and know you've got the clean slate to start with.
---------- Post added at 10:56 AM ---------- Previous post was at 10:36 AM ----------
BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.

It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.
Click to expand...
Click to collapse
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.

BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
You connect your phone to computer while in recovery to transfer the OS zip
Sent from my Redmi K20 Pro using Tapatalk

BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
After format data, reboot your device into recovery again and transfer LOS, gapps and all files you need.
Format data kills the storage.

I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.

Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes I did that and it worked, unmounting and remounting helps detect the storage in PC
Sent from my Redmi K20 Pro using Tapatalk

Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes that works. Tried it myself but prefer to reboot into recovery again.:laugh:

Finally Successful
After a long post I have finally finished the process successfully. This was pretty educational for me since I didn't understand any of this at the start I would like to thank everyone who reply's and all the information that you have provided.

need help guys, i stuck in bootloop.
- fastboot rom global china V10.3.17.0 PFKCNXM
- fastboot twrp 3.3.1
- format data
- flash vendor image cn 10.4.6.0
- wipe cache/dalvik
- flash lineage os
- flash gapps nano
- reboot
- stuck bootloop

Custom Rom flashing problem.

Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?

Astrek said:
Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Click to expand...
Click to collapse
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.

You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:

Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Thnx for the guide. i will do this within a day or two and update you if it worked or not.

Kollachi said:
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Click to expand...
Click to collapse
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.

Astrek said:
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Click to expand...
Click to collapse
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.

Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Ohhh *****...!!!! It ****ing worked!!!! Though i made some mistakes like clean all and lock in first step, but was able to unlock bootloader almost instantly, no idea why but i can almost instantly unlock certain mi phone's bootloader instantly. But a lot of thanx for taking your time and writing this up... You really saved me from being stuck in MIUI forever!
A lot of thnx.... and also happy new year... 1st day of 2020 went quite well for me all thnx to you and i hope yours goes well too.!

Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
thanks for help
but no work for me
after flash rom and reboot booting to twrp auto..

Kollachi said:
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Click to expand...
Click to collapse
many times the tiniest msg has the greatest significance. thanks mate!!!

Guys i need your help,, i flashed my phones custom Rom tecno 7cs using sp flashing tool.
That worked and it showed the tick icon on my pc.
The problem is that it does nothing to my phone because the software issues are still there
my phone keeps restarting itself almost all the time and sometimes won't even boot it takes longer to boot,,, apps keep on crushing and many more.AM tired am going to break it and throw it if i don't get solutions asap!
So the flashing process only wiped data on the phone nothing else whatsoever.
tecno 7cs p121 Bi safaricom ke 20151111

[ROM][S9+/S9][LineageOS 17.1][UNOFFICIAL][05-06-20][OTA]

What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020

temp

Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English

Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.

so everything good other than Android Auto? Well done!

Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?

geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.

How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:

..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?

Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6

Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.

Great, glad all went good for you

Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse

Great work! ROM works great, even Google pay is working good!

I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel

Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?

Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!

oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel

Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse

Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.

Can't boot into new rom

I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.

sternje said:
I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.
Click to expand...
Click to collapse
Restore MIUI by flashing a MIUI fastboot ROM.
Get the fastboot ROM from here
https://xiaomifirmwareupdater.com/miui/raphael/
Choose the fastboot ROM for the phone you have (European or Global). Make sure it is a fastboot ROM, not a recovery ROM.
Use this guide to flash it
https://c.mi.com/oc/miuidownload/detail?guide=2
View the page in desktop mode if viewing on a phone.
In step 5 make sure you change flash option to 'clean all' before hitting flash. This is three radio button options at the bottom of the flash tool. The default locks the bootloader, so you need to change it to keep the bootloader unlocked.
After doing this boot into MIUI at least once before trying to install something again.
When flashing a custom ROM over MIUI you need to format data in TWRP.
After installing TWRP, boot into it a do the following.
Perform a factory reset.
Format data - make sure you format, not wipe, need to type 'yes' to confirm.
Reboot back into TWRP - this makes sure the data partition is properly mounted after formatting.
Now flash the ROM you want and GApps if needed.
Reboot to system and it should be good.
Flash Magisk if needed.
Do not wipe anything else in TWRP. It's not needed.

sternje said:
I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.
Click to expand...
Click to collapse
First Learn Basics while messing with your device.
Kernel is a part of ROM's Zip,
So even if you wiped kernel(so called boot), it will again gets re flashed with new ROM.
Second your problem is,
You are booting into wrong partition.
I am not sure , what you did.
But Mi9TPro has two partitions, Google's new A/B partition table for Android.
And you may have wiped both Flashed A(example) and booting into B.
Therefore it is not booting properly.
Ask in Telegram group for faster solution.
Or wait here for better solution in reply.
OR
Simply flash Fastboot,
And then try everything again.
Ans from next time, read everything step carefully and then proceed.
Sent from my Redmi K20 Pro using Tapatalk

itspdp said:
First Learn Basics while messing with your device.
Kernel is a part of ROM's Zip,
So even if you wiped kernel(so called boot), it will again gets re flashed with new ROM.
Second your problem is,
You are booting into wrong partition.
I am not sure , what you did.
But Mi9TPro has two partitions, Google's new A/B partition table for Android.
And you may have wiped both Flashed A(example) and booting into B.
Therefore it is not booting properly.
Ask in Telegram group for faster solution.
Or wait here for better solution in reply.
OR
Simply flash Fastboot,
And then try everything again.
Ans from next time, read everything step carefully and then proceed.
Click to expand...
Click to collapse
This phone does not have A/B partitions.

Robbo.5000 said:
This phone does not have A/B partitions.
Click to expand...
Click to collapse
It has, but you can't see then normally in twrp.
Ask in telegram group for fast solution.
And please do read about android partition tables feom android oreo.
Sent from my Redmi K20 Pro using Tapatalk

itspdp said:
It has, but you can't see then normally in twrp.
Ask in telegram group for fast solution.
And please do read about android partition tables feom android oreo.
Click to expand...
Click to collapse
It's an A only, system as root device. It is not an A/B device.
This is why MIUI updates need to be installed in system recovery. It does not install updates when the system is live.

if it's booting back into twrp. It's usually one of the three mistakes.
1. wrong vendor
2. didnt flash dfe
3. flashed dfe for stock rom
4. encrypted, so format data partition.
you can follow the guide: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, k20p is A partition only, not dual.
kernel is included with rom.
ask in telegram group for faster replies.

Sandeeep Kiran said:
if it's booting back into twrp. It's usually one of the three mistakes.
1. wrong vendor
2. didnt flash dfe
3. flashed dfe for stock rom
4. encrypted, so format data partition.
you can follow the guide: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, k20p is A partition only, not dual.
ask in telegram group for faster replies.
Click to expand...
Click to collapse
You don't need to flash dfe. I've not yet come across a situation where it is required. Flashing dfe will make life easier, at the cost of greatly reduced security, but there are always options to do what you want without flashing dfe.

Robbo.5000 said:
You don't need to flash dfe. I've not yet come across a situation where it is required. Flashing dfe will make life easier, at the cost of greatly reduced security, but there are always options to do what you want without flashing dfe.
Click to expand...
Click to collapse
It's required for oss based builds now.