Related
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Jonny6921 said:
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Click to expand...
Click to collapse
Perhaps you should say which version of NitrogenOS you're using. Also asking in Nitrogen's thread has a higher chance of answers for your question.
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
runekock said:
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
Click to expand...
Click to collapse
Additionally TWRP's format function is broken.
Try "fastboot format userdata" if TWRP isn't properly formatting.
Elektroschmock said:
Additionally TWRP's format function is broken.
Click to expand...
Click to collapse
Can you elaborate on this?
I usually try to erase and format in fastboot anyway. But fastboot throws a can't format raw partition or something like that.
format (not wipe) data or use oreo builds
i've already done it
upgrade your twrp if it keeps failing, i'm using the latest release
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Flaco05 said:
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Click to expand...
Click to collapse
Without explaining what the problem is, it is hard to help you. Since you are using TWRP, you should have backup to restore.
Thank you for replying. I have the exact problem described by OP. And yes, I have a backup, so technically not bricked, you are right. Just very disappointed that following the flashing instructions let to this problem. Thank you again.
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Hi, that is exactly what I did! I have repeated the process with LineageOS 15.1 (and the matching GApps) and it worked. Might this be an encryption problem related to LinerageOS 16? And thank you for responding.
Incidentally, what GApps package is the one most recommend? I used Open GApps Stock, but some of the Google Apps are acting up.
I use Opengapps Pico Arm (not Arm64).
All I can say is that I've installed LineageOS 16 on 2 N5s, 2 N4s and a Lenovo 8" tablet, all with no problems at all. Your problem is not device-specific, since the original query was not for an N6, and I myself know about this "corrupt" problem because I suffered from it myself a year or so ago on my own N6. The procedure I specified has always worked 100% for me every time.
Looking at the LineageOS 16 thread, there is a specific TWRP linked, and MindTheGapps is also linked which is different than openGapps.
If you haven't decrypted by FORMATING user data (not wiping), that may also be a problem.
Thanks, ktmom. The format was part of my instructions, and Flaco05 says he did exactly that. Normally I don't use fastboot to format - I just rely on TWRP and it's worked fine.
I've always used the standard Opengapps Pico and TWRP 3.3.1, no special versions, and they have always worked flawlessly - never any problems. Still, since Flaco05 is having problems, I guess he has nothing to lose by trying the recommended versions...
Thank you all. I will try some of these things tomorrow. I love this community!
dahawthorne said:
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Click to expand...
Click to collapse
OK, I did all this, but have been stuck at the Google screen upon reboot for 30 minutes. Is this bad news, or this normal?
No, definitely not normal. A new ROM takes longer to boot but it's generally ten minutes maximum.
Have you tried flashing only the ROM & Gapps, without Magisk? Once you boot successfully you can then flash Magisk later. Try starting again from the top and see if that works.
(P.S. In a slow quiet thread, as this one is at the moment, there's no need to copy the entire post to which you're replying... )
Edit: No, sorry, not from the top. TWRP will still be there after formatting & wiping, so start at the third (format data) part.
Thank you. There is still some kind of a problem. After I finish flashing ROM and Gapps using the instructions, and then reboot (after wiping cache/davlik, right?), I get the Lineage OS logo in motion, and then finally boots into recovery (not system) again. Not sure what to do. Maybe try a different build? I am currently using the latest LineageOS 16 nightly.
Strange. Maybe try LineageOS 15.1?
I enjoy playing with bleeding-edge software, but when you can't get it to work at all then it sort of ruins the fun. A lot of people seem to prefer the stability of 15.1. Personally I never see much difference between even major versions. Maybe I'm just a bit unobservant...
Hi,
I bought a new phone and thought I would get in to custom ROMs again. Mostly to get rid of bloatware. However, after following multiple guides I'm still no where closer to achieving my goals. The phone is a MI 9.
I found there's a lot of different steps depending on guide but most of the once I've tried does the following:
* Unlock bootloader, working
* Installing twrp via fastboot, working
* Deleting data in twrp, working
* Transfering a rom.zip file (depending on rom), working via usb cable
* Some guides recommends to install disable force Encryption via another zip file transferred from the computer, however, that seems to not be necessary, tried i few times
* Installing rom via twrp, seems to work
* In some guides you then need to remove cache, working
* Rebooting from twrp, working
After these steps I find myself in one of three different cases,
1. Phone is stuck in fastboot, have to reflash it with MIflash and global MIUI rom to get phone to work again
2. Phone in boot loop, logo shows up, phone waits for awhile, phone reboots, logo shows up
3. Phone boots up, logo is shown, phone reboots into twrp
I've also tried both XiaoMiTool and XiaoMiTool V2,
XiaoMiTool seems to write the global ROM to the phone whatever I choose (Have tried Xiaomi.eu and LineageOS 17)
XiaoMiTool V2, fails in second to last step, it wants to remove some cache before the installation in twrp is done.
Things I've not tried:
* Moving file to twrp with adb instead, should not make a difference
* Installing magisk
Now, I'm a bit afraid my phone will get hard bricked, have reinstalled the OS 20 times the last day to test different approaches and steps. Nothing seem to work. Does anyone have a proven method working in 2020?
Another way to go might be to just get rid of the commercials, run a different launcher to get app list and get rid of the bloatware. This is not really what I want but I can live with it.
As you can hear I'm about to just throw in the towel and give up. But I've heard a lot good about the xda forums so I thought it might be worth a try even though I do understand if no one has time or energy to help out a newbie.
Help please!
Edit: I do realize I've accidentally put this under Guides and not Q&A. I find no way of moving it nor deleting the thread so I guess some moderator will have to come help. Sorry for this.
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
mxxt01 said:
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
sangbuana said:
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
Click to expand...
Click to collapse
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Step 6 is to type adb push rom.zip /tmp/
I renamed the zip file to rom.zip so that I don't typo when typing.
Sent from my MI 9 using Tapatalk
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
From personal experience of using xiaomi.eu's ROM, I never did install vbmeta.img or dmverity, since that particular rom is based on the official beta Chinese MIUI ROMs, and the latest TWRP from Mauronofrio supports decryption. Not sure about other ROMs though.
Just to be safe, just download the stock fastboot ROM as a backup just in case anything goes wrong. Always remember to NOT lock your bootloader when flashing back to stock, in case your persist partition gets corrupted, you can flash it to recover.
ZevSwe said:
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Click to expand...
Click to collapse
Like written by toscha42 you should flash the latest fastboot stock rom (tgz) for your phone first, as after all the attempts you have made your phone is probably kind of ****ed up... Do not lock bootloader.
What I do and it works for me, starting from stock ROM.
1. Unlock bootloader (you already done that)
2. Flash in fastboot latest TWRP for your device (I use Mauronofrio)
3. After flashing disconnect the phone and push VOLUME UP + POWER to enter from fastboot directly to TWRP recovery
4. Format data with yes
5. Reboot to recovery
6. Flash xiaomi.eu custom rom for your device with USB OTG (usb otg is the easiest way I guess as you don't need to move the rom to internal storage)
7. Reboot to recovery
8. Wipe cache and dalvik cache
8. Reboot to system
And that's all.
Poslano z mojega MI 9 z uporabo Tapatalk
toscha42 said:
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
Click to expand...
Click to collapse
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
ZevSwe said:
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
Click to expand...
Click to collapse
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
mxxt01 said:
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
sangbuana said:
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
Click to expand...
Click to collapse
Right, well I wish to switch to another ROM so installing MIUI Global ROm will not help.
I'm able to install TWRP without touching verfiedboot at all and get it to work even after reboot so that is not a problem. If that is what verifiedboot does I believe I can skip that?
ZevSwe said:
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
Click to expand...
Click to collapse
than try once again by following my steps in post #8
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
sangbuana said:
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
That seems to have made the trick! Thanks so much!
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
thecdn said:
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
Click to expand...
Click to collapse
Since you noted that you have been doing a backup to a USB stick, it could be the USB stick is failing.
Honestly, all the installation guides for custom Roms i came across on XDA in the recent years are complete garbage. It fills like copy pasted from a guide that has been copypasted from a copypasted thread which has been copypasted and never worked.
For me, this guide works just fine. I just had to find the files for my Mi 9 instead of the k20 Pro. I would upload them for you but my upload speed is garbage.
https://www.youtube.com/watch?v=w_u_w6SrTDY&t=249s
I have flashed a lot of ROMs custom and official, fastboot and recovery. Never had any problems, the steps is here in thread.
Just remember 2 thing:
1. If you have ROM which using encryption, you must format data, because wipe will not remove encryption and you will see gibberish names
2. If you wipe system (which is mean less, because every ROM flash will do that, when you flash it, but many people insist in wiping it) then you must flash a ROM without reboot or you will stuck in fastboot and only option to repair is to flash official fastboot ROM (Non official fastboot ROMs, don't exist).
Hello, I have flashed twrp, made a backup and tried to flash arrow os on my xiaomi mi 9t pro. However, now I'm stuck and it's just booting to twrp automatically. I've tried restoring boot, system, vendor, but no success. Does anyone know what to do? Also, how do I figure out which vendor I have, I didn't look previously and now it's not booting (so I could try to flash the original rom).
krifpv said:
Hello, I have flashed twrp, made a backup and tried to flash arrow os on my xiaomi mi 9t pro. However, now I'm stuck and it's just booting to twrp automatically. I've tried restoring boot, system, vendor, but no success. Does anyone know what to do? Also, how do I figure out which vendor I have, I didn't look previously and now it's not booting (so I could try to flash the original rom).
Click to expand...
Click to collapse
You probably needed to Format (not just Wipe) Data.
This is a MUST whenever you flash custom ROMs - something that everyone must read/learn about before going for custom ROMs
However, if you messed up your vendor or other partitions, you will probably need to flash the full tgz/fastboot firmware - Google is your friend
zgfg said:
You probably needed to Format (not just Wipe) Data.
This is a MUST whenever you flash custom ROMs - something that everyone must read/learn about before going for custom ROMs
However, if you messed up your vendor or other partitions, xou will probably need to flash the full tgz/recovery firmware - Google is your friend
Click to expand...
Click to collapse
Oh my ****ing god. Thank you so so much!! Formatting data worked!
zgfg said:
You probably needed to Format (not just Wipe) Data.
This is a MUST whenever you flash custom ROMs - something that everyone must read/learn about before going for custom ROMs
However, if you messed up your vendor or other partitions, you will probably need to flash the full tgz/fastboot firmware - Google is your friend
Click to expand...
Click to collapse
Google is not your friend when you want help with your phone. There is so much bad information that is easily found when using Google (same with YouTube). If you are not sure what you're doing, how can you verify a random article/video is giving good information.
Better to stick with XDA where many members can verify info and advice. XDA search is your friend.
krifpv said:
Oh my ****ing god. Thank you so so much!! Formatting data worked!
Click to expand...
Click to collapse
You need to format data whenever you flash over MIUI (or MIUI derived custom ROM).
Flashing over another AOSP ROM you won't need to format data. However it is strongly advised to remove lockscreen security before updating a custom ROM or flashing a new custom ROM.
I tried flashing evolution x 11 today, after wiping i realized i forgot to update the vendor, so i tried restoring thr backup but that didnt work so i downloaded the latest vendor and flashed it followed by the rom but it still didnt work. So i flashed an old android 10 rom but that didnt work either. Anything i do, it just keeps booting into recovery.
is formatting data gonna help?
SatouKazuma said:
is formatting data gonna help?
Click to expand...
Click to collapse
Yes. Also read this thread, mainly posts 2 & 3. It has very useful info about backup, restore, etc for encrypted phones.
format first, download latest vendor for your phone https://downloads.akhilnarang.dev/MIUI/raphael/ from here. flash vendor, reboot recovery, then flash everything else.
I'm having a big problem. I've had to unbrick my Mi11 ultra 5 times with the miflash tool because every time I flash the custom rom through TWRP it complete then reboots with no OS. I copy the rom to the phone. Go in to TWRP and then I go to install and find the zip file. I choose it and it goes through the process but it still reboots into TWRP with no OS. I've tried it with and without root with Magisk. WHAT AM I DOING WRONG?! Please help. Here is the link for the ROM I'm trying to use https://androidfilehost.com/?fid=14943124697586336463
Format data after flashing the EU ROM.
The first time you load the system, the screen will stay a loooong time with the MIUI logo; don't panic and be patient.
Hope it works for you.
Regards.
Yes, as above. If you don't format data with the confirmation of yes in the twrp wipe menu, it will alway go back to twrp.
The reason is that when you change kernal branch, there may be partition differences between them. A format clears out old data crossing the new partition layout and allows boot.
portamento said:
Format data after flashing the EU ROM.
The first time you load the system, the screen will stay a loooong time with the MIUI logo; don't panic and be patient.
Hope it works for you.
Regards.
Click to expand...
Click to collapse
Buddy as best try to flash over Fastboot, then after that install TWRP and mount all partitions. Then klick wipe-- factory reset and wipe and after that format data with confirm yes. after that you need to install inject TWRP inject. You can find it in ADVANCED. After that klick fix Contexts. And reboot.
After that the OS will reinstall . Try it, that will work 100%
portamento said:
Format data after flashing the EU ROM.
The first time you load the system, the screen will stay a loooong time with the MIUI logo; don't panic and be patient.
Hope it works for you.
Regards.
Click to expand...
Click to collapse
Sathelp said:
Yes, as above. If you don't format data with the confirmation of yes in the twrp wipe menu, it will alway go back to twrp.
The reason is that when you change kernal branch, there may be partition differences between them. A format clears out old data crossing the new partition layout and allows boot.
Click to expand...
Click to collapse
THANK YOU BOTH!!! IT WAS CAUSE I DIDNT FORMAT DATA AFTER THE ROM INSTALL!! Thank you so much
Mag_e said:
THANK YOU BOTH!!! IT WAS CAUSE I DIDNT FORMAT DATA AFTER THE ROM INSTALL!! Thank you so much
Click to expand...
Click to collapse
Glad to know that it worked . I had the same problem when I changed from European stock ROM to Xiaomi.eu one. The tutorials I read didn't say anything about formatting data after installing the new ROM.
Mag_e said:
I'm having a big problem. I've had to unbrick my Mi11 ultra 5 times with the miflash tool because every time I flash the custom rom through TWRP it complete then reboots with no OS. I copy the rom to the phone. Go in to TWRP and then I go to install and find the zip file. I choose it and it goes through the process but it still reboots into TWRP with no OS. I've tried it with and without root with Magisk. WHAT AM I DOING WRONG?! Please help. Here is the link for the ROM I'm trying to use https://androidfilehost.com/?fid=14943124697586336463
Click to expand...
Click to collapse
Check this steps