Any ideas? It just give me an error 1. Tried several versions and still the same problem.
Is it not needed anymore?
After installing the rom or magisk you must restart from the twrp in recovery mode and voila, you can install. in fact I cannot install 2 things in a row, I must install 1 at a time, restarting in recovery mode
17007501 said:
After installing the rom or magisk you must restart from the twrp in recovery mode and voila, you can install. in fact I cannot install 2 things in a row, I must install 1 at a time, restarting in recovery mode
Click to expand...
Click to collapse
Tried it several times. Wiped cache etc and restarded the phone. Nothing helps.
Try this https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
17007501 said:
Try this https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
Click to expand...
Click to collapse
EDIT: Nope Flashing was fine but after the reboot i get a bootloop with only mi logo showing.
So now what?
you can try entering twrp, format data and flash dm
17007501 said:
you can try entering twrp, format data and flash dm
Click to expand...
Click to collapse
Nope. Not working
Use LR twrp, there's "script" file
Boot into recovery
Format data, keep in recovery
Transfer script and flash
Reboot to recovery
Transfer ROM, GAPPS, Magisk, and script
Flash ROM, GAPPS, then script
Reboot to recovery
Flash Magisk then script
Reboot to recovery
Format data, keep in recovery
Transfer script and flash
Reboot to recovery
Reboot to system
I actually had the same error. instead of booting, I flashed the LineageOS ROM I wanted to load and it worked fine.
Perhaps some phones do not have this check ? For me it's a Galaxy S9. I have TWRP 3.5.x now and LineageOS 18.1 and no message of knox tripped or anything yet. Not rooted yet though
Related
I am having serious battery drain on any OOS 4.x.x rom. I used to have very good battery life in 3.5.2. can anyone give me a proper step by step guide to downgrade? Battery is a huge issue for me.
i have my own steps that i found it by my self but it will earse all ur data so backup ur data to pc.
here are the steps :
1. make sure u have unlocked bootloader, custom recovery (twrp) i prefer use blu_spark twrp latest version
2. pur ur 3.5.x firmware in internal storage
3. boot to twrp recovery and do a clean wipe(dalvik, data, internal, system, cache)
4. flash ur 3.5.x firmware. it will take a long time just wait it
5. reboot to system, ull get a no os installed warning in twrp just reboot it(swipe)
6. when the devices boot up ull get a enter password for decrypt data. just reboot to bootloader
7. when u in fastboot mode connect ur devices to pc
8. use op3/op3t toolkit to flash twrp from fastboot u can find the toolkit here: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
9. then wait when it boot to twrp and when it boot up wipe data, internal storage only
10. reboot to system. done
sorry for my bad english. i hope it works
Ok that sounds easy. Reboot to recovery after flashing ROM retains the recovery I guess. Do you have any suggestion of custom kernel for 3.5.x ? Also i have the latest twrp. Will is allow me to flash 3.5?
arafat_mw said:
Ok that sounds easy. Reboot to recovery after flashing ROM retains the recovery I guess. Do you have any suggestion of custom kernel for 3.5.x ? Also i have the latest twrp. Will is allow me to flash 3.5?
Click to expand...
Click to collapse
u can try this i guess https://forum.xda-developers.com/on...mm-6-0-1-oxygen-3-5-4-kernel-3-18-48-t3567781
Thank you guys. It wasn't really tough. Flashed OOS 3.5.4 full zip. Rebooted to recovery then rebooted to system. However it was bootloop at the start then I restarted and flashed SuperSU zip, it booted up. Don't know why SuperSU is required to boot up. However I am not getting the support for Magisk. I tried cleaning up SuperSU and then flashing the Magisk zip but it didn't work. Any advice ?
arafat_mw said:
Thank you guys. It wasn't really tough. Flashed OOS 3.5.4 full zip. Rebooted to recovery then rebooted to system. However it was bootloop at the start then I restarted and flashed SuperSU zip, it booted up. Don't know why SuperSU is required to boot up. However I am not getting the support for Magisk. I tried cleaning up SuperSU and then flashing the Magisk zip but it didn't work. Any advice ?
Click to expand...
Click to collapse
You have to reflash stock boot image to get Magisk to work
Hello, everyone!
I hope anyone can help me.
Yesterday I assisted with rooting and flashing a Mi 9 T Pro with Xiaomi.eu firmware.
Here are the steps which were done:
1. Unlocking bootloader via MiFlash Tool.
2. Flashing TWRP (this one: https://androidfilehost.com/?fid=6006931924117906979)
3. First trouble: It only booted once into TWRP with "fastboot boot recovery xxx.img, after formatting data and a restart of TWRP it refused to get access again, neither with a command nor with hardware keys. It was stuck in fastboot.
4. With the MiFlash Tool I reverted to the stock global (this one: http://bigota.d.miui.com/V10.3.1.0....M_20190805.0000.00_9.0_global_135788d537.tgz)
5. After successfully flashing the stock ROM, I downloaded and flashed this TWRP: https://www.androidfilehost.com/?fid=1899786940962577905
6. Flashing this version of TWRP went perfectly fine.
7. In TWRP I formatted data again. I restarted TWRP and copied the following files to storage:
ROM: https://androidfilehost.com/?fid=1899786940962578113
Magisk 19.2.zip
Disable_dm verity_ForceEncrypt
8. I wiped Dalvik, cache, system and data.
9. I flashed ROM - it went through without problems
10. I tried to flash the dm verity, then an error occurred (please see the attached picture).
Can you please tell me what I'm doing wrong? Root is mandatory for me, I definitely need it.
I'm looking forward to your input and your help, it's very appreciated!
try to unmount system then flash it again
SkipperRyujin said:
try to unmount system then flash it again
Click to expand...
Click to collapse
Thanks for your input. I tried that, unfortunately this didn't work.
But I found the solution a few minutes ago:
I downloaded TWRP 3.3.1-13 (one version newer) and flashed it inside of my old TWRP. I rebooted to recovery again and then flashed Magisk without problems.
(The dm verity still refuses to install but the phone is booting and running.)
Well, it always work for me, or simply reboot recovery also work. Try wzsx twrp, it has remove DM verity & forced encryption remover in advanced menu
I'm trying to instal Magisk 19.3 through Magisk Manager Version: v7.3.4
and getting this error:
Device platform: arm64-v8a
Coping image to cache
unpacking boot image
!unsupported/unknown image format
!installation failed
Any ideas how to solve it?
I have used Stable Magisk Version: v19.3 (also tried Beta Magisk Version: v19.4)
Maybe something's wrong with the boot image? Try to re-download magisk stable zip and reintall it via TWRP.
@LogicalMaverick, tried to download it again from this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 but still the same error message
I did try to install in TWRP mode and also from the Magisk Manager and still not working.
When I install in TWRP mode the result is the phone is getting into loop mode and the only way out if it is to uninstall it
try to wipe data after flashing magisk before booting to system
Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Yeah, for me there are 2 ways:
1. Wipe data after flashing magisk before booting system
2. Complete phone setup first after installing new ROM, and then boot into recovery, then you're good to install magisk
Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk
What phone are you using?
cohenelad said:
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk
Click to expand...
Click to collapse
are you on stock or custom ROM (if stock what MIUI Ver)
Kzak25 said:
are you on stock or custom ROM (if stock what MIUI Ver)
Click to expand...
Click to collapse
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help
cohenelad said:
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help
Click to expand...
Click to collapse
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again
reboots to fastboot
Kzak25 said:
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again
Click to expand...
Click to collapse
I can flash over twrp. then it says no rom installed so flash over magisk-error unknown image. this is a fresh download tried 3 new downloads same error. use adb sideload to flash rom. successful do the reboot and it reboots to fastboot. what do i do
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
dev-DaT said:
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
Click to expand...
Click to collapse
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Robbo.5000 said:
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Click to expand...
Click to collapse
thanks, i always thought that a wipe was sufficient, or at least equal to a format... anyways will report back later when i have time to try it. lets hope it works because i can't handle this chinese rom
dev-DaT said:
thanks, i always thought that a wipe was sufficient, or at least equal to a format... anyways will report back later when i have time to try it. lets hope it works because i can't handle this chinese rom
Click to expand...
Click to collapse
The format is needed to temporarily remove encryption
I've just remembered that I missed an important step. Call it step 1.5
If you going to flash immediately after flashing official MIUI you must boot into MIUI once before doing anything else. You don't need to go through the set-up, you can boot immediately into fastboot after you get to the initial set-up page. The first boot finalises the install and is needed before you flash over the top of it. That may be the cause of your issue if you had missed this before.
Robbo.5000 said:
The format is needed to temporarily remove encryption
I've just remembered that I missed an important step. Call it step 1.5
If you going to flash immediately after flashing official MIUI you must boot into MIUI once before doing anything else. You don't need to go through the set-up, you can boot immediately into fastboot after you get to the initial set-up page. The first boot finalises the install and is needed before you flash over the top of it. That may be the cause of your issue if you had missed this before.
Click to expand...
Click to collapse
Ok so i flashed TWRP again, rebooted to stock rom and then rebooted into recovery, but the stock recovery is still there.
When i flash TWRP and reboot into recovery immediately i can enter TWRP, but if i reboot the phone to MIUI and then reboot again, TWRP is gone again...
It seems like TWRP does not persist... now iam stuck again on fastboot screen because i wiped + formatted everything.
Edit:
When i want to flash recovery it says "OKAY" but it is unable to boot:
Sending 'recovery' (65536 KB) OKAY [ 1.562s]
Writing 'recovery' OKAY [ 0.333s]
Finished. Total time: 1.989s
Sending 'boot.img' (65536 KB) OKAY [ 1.547s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
dev-DaT said:
Ok so i flashed TWRP again, rebooted to stock rom and then rebooted into recovery, but the stock recovery is still there.
When i flash TWRP and reboot into recovery immediately i can enter TWRP, but if i reboot the phone to MIUI and then reboot again, TWRP is gone again...
It seems like TWRP does not persist... If i wipe all data trough TWRP and then reboot, i don't have OS but i do reboot back into TWRP, because well, there is nothing else...
Click to expand...
Click to collapse
This is normal, MIUI will restore stock recovery of the recovery partition changes. In order to persist TWRP you need to either install Magisk, disable dm-verity or install a custom ROM.
If you are going to flash a custom ROM, then you should do so immediately after flashing TWRP.
After formatting data, TWRP has an issue seeing the data partition, so go to the reboot menu in TWRP and select to reboot to recovery.
Then you can immediately install the ROM of choice. You cannot boot back into system as you'll lose TWRP.
Robbo.5000 said:
This is normal, MIUI will restore stock recovery of the recovery partition changes. In order to persist TWRP you need to either install Magisk, disable dm-verity or install a custom ROM.
If you are going to flash a custom ROM, then you should do so immediately after flashing TWRP.
After formatting data, TWRP has an issue seeing the data partition, so go to the reboot menu in TWRP and select to reboot to recovery.
Then you can immediately install the ROM of choice. You cannot boot back into system as you'll lose TWRP.
Click to expand...
Click to collapse
Ok, it appears that everytime i wipe system, i am not able to boot anymore into TWRP... Am i supposed to wipe System? or only wipe data & format data
dev-DaT said:
Ok, it appears that everytime i wipe system, i am not able to boot anymore into TWRP... Am i supposed to wipe System? or only wipe data & format data
Click to expand...
Click to collapse
There is no need to wipe system. You only need to wipe cache and dalvik and format data. (I choose to factory reset because it's easier in TWRP, but you could do advanced wipe and select cache and dalvik, then format data. Follow the steps exactly, but include my later step 1.5
I've just followed this myself today, as I've moved from LOS to the latest unofficial Havoc build.
In theory you could start by booting to fastboot and flashing TWRP again, then follow the steps from that point. You probably don't need to install MIUI.
Robbo.5000 said:
There is no need to wipe system. You only need to wipe cache and dalvik and format data. (I choose to factory reset because it's easier in TWRP, but you could do advanced wipe and select cache and dalvik, then format data. Follow the steps exactly, but include my later step 1.5
I've just followed this myself today, as I've moved from LOS to the latest unofficial Havoc build.
In theory you could start by booting to fastboot and flashing TWRP again, then follow the steps from that point. You probably don't need to install MIUI.
Click to expand...
Click to collapse
Ok thanks a lot! So no need to wipe system partition after stock rom install. just wipe cache/dalvik/data, got it.
Most ROM install guides tell you to wipe /system when coming from stock rom. I guess this requirement has changed? or depends on what ROM you're coming from?
Use can use my guide
https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
it has how to flash roms, and fastboot fix. (which tells why the Recovery isn't staying)
Robbo.5000 said:
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Click to expand...
Click to collapse
I need help... The reason why I'm flashing custom rom is, when the latest update came MIUI 12.5 android 11, all sensors of my phone stopped working like (Gyroscope, accelerometer, proximity sensor) I tied to flash the rom by fastboot method but still the problem persists. because of that I unlocked bootloader and flashed twrp. After flashing custom rom when I tried to boot it, it stuck on booting screen and when I tried to reboot into recovey it is showing fastboot mode. I'm unable to boot into custom rom.
dev-DaT said:
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
Click to expand...
Click to collapse
Bro I have one doubt, I installed pixel os successfully then I roll back into stock os(miui) with locking bootloader, the. Again I unlock bootloader successfully, but the problem is I am unable to install os, i tried wipe data, catch. But the stock rom was not removed. What can I do?
Using orange fox in resmi note 10 pro