Related
Is it just me with this issue? Any known fixes or something? I'm using lineage os version 15.1 with latest update that released today.
i got it too. i always encrypt on lineage OS and omni, today i don't remember what last build i was on but i cleaned my phone and installed latest LOS, after that i can't encrypt my device anymore. even i tried older builds of LOS, NLOS and also OMNI. i can't encrypt my device anymore.
I formatted Data many times and formatted everything but still can't encrypt. anyone can solve this issue?
---------- Post added at 03:45 AM ---------- Previous post was at 03:10 AM ----------
just figured out the problem, problem was in TWRP 3.2.3-1. please install 3.2.3-0, and problem solved
I also have this issue on 15.1-20190127-NIGHTLY-oneplus3, has anybody got a fix yet?
Here's what I would do in your situation:
0. Take a backup of your current rom and internal storage and save it on your PC.
1. Try a different rom to see if it can encrypt your phone, eg Los 16 beta from https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC
See: https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post78144505
If that works, you're done and can restore your backup. If not ...
2. Do a clean install of OOS 5.0.8 full zip from https://www.oneplus.com/support/softwareupgrade
Don't flash Magisk or custom kernel. Let the phone reboot normally. Check that the phone is encrypted.
OOS forces the storage to be encrypted. It will also replace TWRP, but you can flash it (use the version mentioned in the next step) after the phone has booted.
If this doesn't give you an encrypted phone then:
3. !!!This step will complete wipe your data partition (including user storage)!!!
Use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112 and tap the Format Data button under the Wipe menu. Do not use the Advanced Wipe option.
This should give you a properly formatted data partition with the correct encryption space.
I would flash stock OOS 5.0.8 at this point and boot it to get a properly encrypted phone (I did this when I was testing this version of TWRP and it works).
You can then restore your data backed up in step 0. Also restore TWRP (the version mentioned above) and restore your backed up rom.
For discussion and info on this version of TWRP see https://forum.xda-developers.com/on...ial-twrp-touch-recovery-t3742894/post78661632
You could just do steps 0 and 3, but that's a fair bit of time and effort, which is why I suggested steps 1 and 2.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Here's what I would do in your situation:
0. Take a backup of your current rom and internal storage and save it on your PC.
1. Try a different rom to see if it can encrypt your phone, eg Los 16 beta from https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC
See: https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post78144505
If that works, you're done and can restore your backup. If not ...
2. Do a clean install of OOS 5.0.8 full zip from https://www.oneplus.com/support/softwareupgrade
Don't flash Magisk or custom kernel. Let the phone reboot normally. Check that the phone is encrypted.
OOS forces the storage to be encrypted. It will also replace TWRP, but you can flash it (use the version mentioned in the next step) after the phone has booted.
If this doesn't give you an encrypted phone then:
3. !!!This step will complete wipe your data partition (including user storage)!!!
Use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112 and tap the Format Data button under the Wipe menu. Do not use the Advanced Wipe option.
This should give you a properly formatted data partition with the correct encryption space.
I would flash stock OOS 5.0.8 at this point and boot it to get a properly encrypted phone (I did this when I was testing this version of TWRP and it works).
You can then restore your data backed up in step 0. Also restore TWRP (the version mentioned above) and restore your backed up rom.
For discussion and info on this version of TWRP see https://forum.xda-developers.com/on...ial-twrp-touch-recovery-t3742894/post78661632
You could just do steps 0 and 3, but that's a fair bit of time and effort, which is why I suggested steps 1 and 2.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Appreciate your advice appreciate, not sure what the OP would think but I wish I didn't have to flash different image and/or wipe, will see how I get on though.
da_n said:
Appreciate your advice appreciate, not sure what the OP would think but I wish I didn't have to flash different image and/or wipe, will see how I get on though.
Click to expand...
Click to collapse
At this stage I trust OOS more than the custom ROMs to correctly encrypt my phone. Once it's encrypted I'm happy to use custom ROMs.
Also, this is my personal view, so others may have different views.
You could, if you wanted, just install a custom rom after formatting the data partition and see if that works.
Sent from my OnePlus3T using XDA Labs
Edit: Figured out the missing step! Wasn't mentioned on any guide I read, or if it was, I'm afraid it wasn't clear :'( Hopefully this guide helps other people though, I've highlighted the step I added!
Hi Mi9 Forum!
Longtime S7 user here, I've flashed (literally) hundreds of roms over the years, but unfortunately lost my device so switched to a Mi9 (Which is ****ing huge!)
Earlier today, after the (arduous 1-week wait) I unlocked my phone (now reads unlocked on boot up), and set about testing three different roms.
From what I understood, I needed to flash a Vendor image before the actual rom itself, so I installed TWRP, flashed the vendor image, then tried flashing the ROM, but alas, I got kicked back to TWRP.
The steps I've taken a listed below, perhaps I've missed something obvious, or not so obvious, but any help would be appreciated!
UNLOCKING
Unlocked phone with Mi tool (Reads unlocked on bootscreen now)
Booted into Fastbook (Vol down + Power)
Plugged in
Used MinimalADB to push TWRP (3.3.1.42) onto my device
Unplugged and rebooted (Vol up + Power)
Plugged back in and entered into TWRP (Huzzah!)
Pushed two files into my "/tmp/" folder, these were xiaomi.eu_multi_MI9_V11.0.2.0.QFACNXM_v11-10.zip, and Magisk (V20)
Went to Wipe > Format Data > "Yes"
Back to TWRP Home, went to Install, and installed the xiaomi.eu mentioned above, then installed Magisk
Once both were done, I restarted, phone loaded up perfectly fine, and had Magisk installed
It was at this point I decided to try a custom rom:
CUSTOM ROM
Booted into TWRP
[*]Selected to Wipe > Format Data > "Yes"
I wiped System, Vendor, Data, Cache, and Dalvik
Pushed the Vendor 9.8.1 file into my "/tmp/" folder, along with whatever ROM I was testing (Tried with Syberia project, AOSPExtended, and ResurrectionRemix), GAPPS, and Magisk
Flashed the Vendor file
Flashed the ROM
Flashed GAPPS (Where it wasn't included with whatever ROM I was testing)
Flashed Magisk (This began giving me ERROR-1 here, even though it was exactly the same file that worked fine earlier.)
Once all that was done, I restarted the phone, it booted up fine, I saw the "Mi" bootscreen along with the "unlocked" at the bottom...Then the phone restarted.
It went to the same bootscreen once more, before restarting once again, and kicking me into TWRP.
I've tried it several times now, with different roms, both with/without installing GAPPS/Magisk, but I always get the same result.
I've been on these forums for a while, I know usually people post without reading, but that's not what I've done, I've read up on what to do, downloaded all the necessary (I think!) files ahead of time, and documented everything I did (in-case of a cockup!). So yes, I really have tried, and I really have searched
Any help, or direction, or hints, or magic wishes anybody can give me regarding this would be much appreciated!
same problem happened to me
i face the same problem every time without any solution i can only flash miui roms not aosp roms?
maheg said:
i face the same problem every time without any solution i can only flash miui roms not aosp roms?
Click to expand...
Click to collapse
Using the above steps, I have been able to flash AOSP, and Miui roms.
Though I always go back to Miui because it has the best camera app.
Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.
Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?
Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.
I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off
I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.
I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.
Same happens for my SO's Mi 9 too as well.
Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....
Hardware test shows Main and Top as PASS.
Any tips would be appreciated! I feel like I've tried everything possible.
Thanks in advance~
AZ_Miss_Murder said:
Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.
I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off
I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.
I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.
Same happens for my SO's Mi 9 too as well.
Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....
Hardware test shows Main and Top as PASS.
Any tips would be appreciated! I feel like I've tried everything possible.
Thanks in advance~
Click to expand...
Click to collapse
Your TWRP is right.
Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.
If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.
Laptapper said:
Your TWRP is right.
Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.
If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.
Click to expand...
Click to collapse
I'm actually going to follow the Evolution instructions (just missed the part about flashing EEA)
So i'm using MiFlash with the MIUI11 EEA boot rom file, then I'll do the normal TWRP -> format data -> install Evolution ROM and test.
Thanks!
So it seems like I'm completely out of luck at this point - I've tried basically everything I can think of, and I think something big must be wrong with the phone's file system.
I've followed Evolution's steps to a T (minus MiFlash having an error at the end of the EEA flashing, but the firmware seeming to load fine) and still run into the no Mic issue.
"Flash MIUI11 eea with miflash
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (Download here)
Flash TWRP
Wipe (dont wipe system/vendor)
Format data
Reboot recovery
Flash rom
Reboot system"
Wipe (don't wipe system/vendor) I assume means just a normal factory reset wipe via TWRP, which I've tried.
I've tried both fw+vendor files (the newest for Android 10 and newest from Xiaomi.eu)
Any other last suggestions before I assumed the phone is broken?
Try to flash xiaomi.eu_multi_MI9_9.11.7_v11-10.zip
With miflash and after factory reset.
https://sourceforge.net/projects/xi...iaomi.eu_multi_MI9_9.11.7_v11-10.zip/download
SO! Update here
I was able to use Evolution X's Android 9 instructions to get everything working fine....but everytime I try to duplicate that for MIUI 11 it does not work.
Reboot to recovery
- Flash the latest 9.8.1 vendor image or full stock ROM.
- Reboot to twrp and format data
- Wipe cache/dalvik
- Reboot back to recovery and flash
I tested using the newest Xiaomi.EU Vendor for Android 10 and the stock one with no luck....more thoughts?
Did you try turning off the VoLTE?
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