Question [Solved] Help with fixing my phone back to Normal after playing with Roms & Twrp - Redmi 9 Power / 9T

Got the bootloader unlocked..should've read more & implemented over a proper guide.
long story short:
stared with magisk apk..when phone was fine.. then got into bootloop;
quickly downloaded & flashed the global (lime) MIUI V12.0.5.0.QJQMIXM;
installed twrp; should've done this before.
wasn't able to copy anything into internal storage.
Used Twrp to wipe phone.. & flashed the stock_global_miui_(lime)12.0.5 boot.img in fastboot
because twrp was saying "unable to decrypt fbe device" on internal storage
formatted using twrp.
booted properly but setup says device is locked because associated with existing mi account can't open wifi but was able to activate device upon entering password on mobile data setup completes but device restarts frequently & still unable to access wifi
I think it has something to do with "unable to decrypt fbe device"..
should I try flashing custom rom boot img?
please don't ban me..tell if I did something wrong, I'll correct that..
..
Edit:
MiFlash-tool Worked
Flashing other compaitable custom Rom also worked
..
Had twrp wipe the whole phone and the format the partions
& then flashed in fastboot & everything was normal.
..
FBE device encryption is basically storage encryption that prevents dirty flashing miui rom via fastboot.
this can be avoided by implementing proper procedure of magisk & use of lazypatcher.
Thank you so much.. @Cursader & @zoel.fahmi for pointing me in the right direction.. godbless
[solved]
Currently I'm running Miui just like a new device.
I will make another guide thread on rooting systemlessly & flashing other custom rooms... if I succeed I will link it here..

Try to reboot bootloader
then flash twrp
wipe everything and format the data partition
reboot to twrp again
then flash custom rom
If you're flashing miui again, your phone bootloader will be lock again and you need something like lazy2flasher if you wanna keep miui with twrp and magisk etc.

zoel.fahmi said:
Try to reboot bootloader
then flash twrp
wipe everything and format the data partition
reboot to twrp again
then flash custom rom
If you're flashing miui again, your phone bootloader will be lock again and you need something like lazy2flasher if you wanna keep miui with twrp and magisk etc.
Click to expand...
Click to collapse
first of all thank you for taking out the time to read & respond..
I found an article with lazy 2 flasher earlier, I'll look into it..
is there any where I should look to find a suited custom rom for my phone..

xhykari said:
first of all thank you for taking out the time to read & respond..
I found an article with lazy 2 flasher earlier, I'll look into it..
is there any where I should look to find a suited custom rom for my phone..
Click to expand...
Click to collapse
you can use custom rom from Poco M3 since it's used the same SoC (662)
here : https://forum.xda-developers.com/f/poco-m3-roms-kernels-recoveries-other-develop.11969/
check the thread name Poco M3 / Redmi 9T or unified or codename like citrus and lime

whats the difference between Lime, Citrus, & Juice..
Mine is Lime
Juice is Lime & Citrus I think..
So will Juice work on a device which previously ran Lime?
..
basically can I install PixelPlusUi_Juice
or should I first try the lazy2flasher.. & @zoel.fahmi
where do I get lazy2flasher

If anything goes for me (RedmiNote9Pro) i just use miflash to flash original miui and start all over from there, might not be the quickest method but is easy and reliable

Cursader said:
If anything goes for me (RedmiNote9Pro) i just use miflash to flash original miui and start all over from there, might not be the quickest method but is easy and reliable
Click to expand...
Click to collapse
THERE IS AN MI FLASH TOOL too.. :O
whydoinotknowofthis.. What the heck..
can it bypass dm verity as well? like does it apply flash without lazypatcher?
do we need to provide it rom or can it fetch itself?
would you be please share some links for me?
..

xhykari said:
THERE IS AN MI FLASH TOOL too.. :O
whydoinotknowofthis.. What the heck..
can it bypass dm verity as well? like does it apply flash without lazypatcher?
do we need to provide it rom or can it fetch itself?
would you be please share some links for me?
Click to expand...
Click to collapse
If the bootloader unlocked and you can go into fastboot you can flash stock rom and It's just like it came from the store! Here you have link for your convinience: https://c.mi.com/oc/miuidownload/detail?guide=2

MiFlash-tool Worked..
(its the best tool for bringing mi devices from rom mess back to scratch new)
Flashing other Rom also worked..(pixelui)
juice = lime + citrus (works for both)
Thank you so much.. @Cursader & @zoel.fahmi for pointing me in the right direction..

Related

Question regarding procedure to safely install (MIUI eu) rom

Hi,
The Mi8 i've bought is a Chinese version which came with the bootloader unlocked and the global rom installed.
Now I want to install the MIUI eu rom on my phone, but since there are so many brick reports I try to get clear what the right procedure is. I figured out that this procedure is the right one and I assume it can be usefull for alot of users.
As far as I understand, most of the bricks are the continuation of installing another rom via MiFlash with accidently enabled the "lock bootloader" option or trying to lock the bootloader after succesfully installing another rom (other than Chinese rom), so DONT DO IT
Since I am more familiar with TRWP, I used this to install the rom.
I've used the procedure below and succesfully installed MIUI 10 EU 10.0.4.0 8.1 rom on my phone.
1. Install TWRP by following this:
Download TWRP image
Transfer TWRP image from pc to phone
Boot to TWRP via fastboot
This should result in the following screen:
NOTE: If you phone is still encrypted, a password prompt will show up. Enter your
pin to decrypt
Click "Install", select the recovery file and swipe to install the image. To make the .img file visible in TWRP, click on the button in the right corner below saying: "Install Img"
After TWRP is succesfully installed, head back to the the start page of TWRP:
Select "Wipe" and in the next screen press on "Format Data". The following screen will appear:
Type in "yes" to start formatting the data. Dont touch the phone now and patiently wait till this is finished.
Once the data formatting is done, press the back button a couple of times to return to the start page of TWRP.
Now select "Reboot" and click on "Recovery". The phone will now reboot and start TWRP again. You will now see that you dont have to decrypt your phone anymore, since the encryption is removed.
2. Install MIUI eu (or any) rom
Since the data is formatted, all the data on the phone is removed. Connect your phone to your pc and transfer the rom to the phone.
From the start page of TWRP click on "Install"
In my case I've installed the MIUI 10 EU rom (v10.0.4.0)
Click on the rom you want and swipe to install it.
Patiently wait untill the rom is installed. Now you can click on reboot and your phone will now boot to the freshly installed rom.
3. Enjoy
Note: Do not try to lock the bootloader when you are using a Chineese phone with a rom other than the Chineese rom. This will brick you phone
Note2: Always remember to check the "fastboot getvar anti" status before installing another rom. This should be implemented starting from the Android 9 based roms, but just check to be sure. If the "getvar anti" commands results in a FAILED you should be good to go.
@AL_IRAQI wrote a nice post with more information about this policy. https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Thanks in advance!
Correct steps u got it right, don't forget if u flash a android pie rom u cannot downgrade it to a previous miui version because of the anti roll back that Xiaomi implemented from Android 9.0 aka pie.
Wipe cache/dalvik is not needed after a clean flash.
bassbounce said:
Correct steps u got it right, don't forget if u flash a android pie rom u cannot downgrade it to a previous miui version because of the anti roll back that Xiaomi implemented from Android 9.0 aka pie.
Wipe cache/dalvik is not needed after a clean flash.
Click to expand...
Click to collapse
Thanks for your quick reply! Does this anti rollback policy even counts when formatting data before installing the new rom? And how about installing a rom like lineage os? Do you know if can (for example) install lineage os 15.1 after I've used an Android 9.0 based MIUI rom?
I will try to install the MIUI eu rom tomorrow.
@tharonny
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
He explains a bit about the anti roll back system.
It was first introduced to the Redmi note 5 pro they got lots of information about it.
bassbounce said:
@tharonny
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
He explains a bit about the anti roll back system.
It was first introduced to the Redmi note 5 pro they got lots of information about it.
Click to expand...
Click to collapse
Thanks, I'll look into it
I would like to ask: What if I installed eu rom, but I didn't flash "Disable Dm-Verity" is there a risk? If I am correct "Disable Dm-Verity" is required to disable encryption. Eu rom doesn't have encryption I think, but if the system is at some stage encrypted I should decrypt and format data I think...Am I right - at most not a brick, but a potential loss of data will occure?
s7eVe90 said:
I would like to ask: What if I installed eu rom, but I didn't flash "Disable Dm-Verity" is there a risk? If I am correct "Disable Dm-Verity" is required to disable encryption. Eu rom doesn't have encryption I think, but if the system is at some stage encrypted I should decrypt and format data I think...Am I right - at most not a brick, but a potential loss of data will occure?
Click to expand...
Click to collapse
You don't need it. Just flash twrp format and flash Xiaomi EU ROM. Done
SPOCK_VULKAN said:
You don't need it. Just flash twrp format and flash Xiaomi EU ROM. Done
Click to expand...
Click to collapse
Are you sure about this? I thought I've read some posts about people not be able to install the rom when the disable dm verity is not flashed?
tharonny said:
Are you sure about this? I thought I've read some posts about people not be able to install the rom when the disable dm verity is not flashed?
Click to expand...
Click to collapse
Yes I am sure. Dmverity is need to boot miui official ROM not xiaomi.eu
SPOCK_VULKAN said:
Yes I am sure. Dmverity is need to boot miui official ROM not xiaomi.eu
Click to expand...
Click to collapse
And what about roms like Lineage os? Does that rom require dm verity to be disabled?
tharonny said:
And what about roms like Lineage os? Does that rom require dm verity to be disabled?
Click to expand...
Click to collapse
Neither. Dmverity is only need for miui official ROM
SPOCK_VULKAN said:
Neither. Dmverity is only need for miui official ROM
Click to expand...
Click to collapse
Thanks, good to know!
Good news! Today I've successfully installed MIUI 10 eu rom. I did indeed not need to flash the disable dm-varity. I will update the FP so it matches the steps I've taken. Next week I will make a complete tutorial with images.
Thanks again!
What's the reason to flash the recovery from the recovery itself and not directly from fastboot? I mean :
fastboot devices
fastboot flash recovery xxx.img
TIA
descarao81 said:
What's the reason to flash the recovery from the recovery itself and not directly from fastboot? I mean :
fastboot devices
fastboot flash recovery xxx.img
TIA
Click to expand...
Click to collapse
To be honest, i dont know. I know about the fastboot flash recovery command, but since flashing via twrp worked good for me I've keeped it in the procedure
Little question:
Do I have to select "wipe data" under "Advanced wipe" or should I select "Format Data" in Wipe menu?
baddevil2 said:
Little question:
Do I have to select "wipe data" under "Advanced wipe" or should I select "Format Data" in Wipe menu?
Click to expand...
Click to collapse
"Format Data" is the one your looking for. If you follow the steps in the first post you should be fine.
Wipe data is a factory reset. You need to format your data which will entirely remove your current rom and remove the encryption
Can't boot to recovery (twrp) after unlocking:
C:\Users\Dominic\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 5.886s
Any ideas?
tharonny said:
Hi,
The Mi8 i've bought is a Chinese version which came with the bootloader unlocked and the global rom installed.
Now I want to install the MIUI eu rom on my phone, but since there are so many brick reports I try to get clear what the right procedure is. If this procedure is the right one, I assume it can be usefull for alot of users.
As far as I understand, most of the bricks are the continuation of installing another rom via MiFlash with accidently enabled the "lock bootloader" option or trying to lock the bootloader after succesfully installing another rom (other than Chinese rom).
Since I am more familiar with TRWP, I would like to use this to install the rom
Now I think I got the procedure clear to safely install the MIUI eu rom and I was hoping that someone can confirm this:
1. Install TWRP by following this:
Download TWRP image
Transfer TWRP image from pc to phone
Boot to TWRP via fastboot
*If encryped: Enter your
pin to decrypt
Select and install TWRP image
Format data
Reboot to recovery
2. Install MIUI eu (or any) rom
Transfer the rom from the pc to the phone
Install rom
Reboot
3. Enjoy
By following the steps above there should'nt be any chance of bricking the phone if I'm correct. If someone could confirm the above, i will update the procedure above with some images to make it more helpfull/usefull for other users who are in the same situation as me.
In another topic I've read something about flashing a region fix (since I'm using a Chinese phone), but I cannot find this elsewere. I reckon that this step is not needed?
EDIT: Topic updated. I've successfully installed MIUI 10 eu rom using the steps above!
Thanks in advance!
Click to expand...
Click to collapse
First, thank you very much for such informations. Flashing rom isn't hard for me but I'm so afraid to brick the device that costs me 450 euros....
Could you please put some screens as you mentioned ?
Could you please detail more in this first thread if you format or wipe which partition (data for example).
Thanks for your time man !
Can someone confirm antirollback bricks the phone from official miui to lower version miui but doesn't brick miui x.x.x to xiaomi.eu rom any versions ?
baddevil2 said:
Can't boot to recovery (twrp) after unlocking:
C:\Users\Dominic\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 5.886s
Any ideas?
Click to expand...
Click to collapse
Tonight Ill look into it

TWRP asking for password for Decrypt Data on (8.1) international global rom

Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
Flash official recovery from twrp website. If I remember right it will work. But change language to English
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
strakell said:
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
Click to expand...
Click to collapse
Data partition he needs to wipe.
ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
You answering all of my question very nice and clear... Yes i will having fun next week, i hope... (Still in other city now, i need my phone)... But, when the time comes, i will try it and post the update here... big thanks, Appriciate it... Yes i'm hungry now
methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
If only i can help you guys out cooking the rom... I'm only animator and designer... Not chef programmer or coder
methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
ABM30 said:
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
Click to expand...
Click to collapse
There are logs on phh thread about sound and other issues on gsi. Take a look if you have any knowledge. You don't need to take logs again I guess. But new GSI don't even boot last time this month when I checked. Maybe I was wrong.
It's just my point of view. You should try to bring up lineageOs with Omni sources coz lot of developers are there to help you if you have knowledge. The device tress are there from Omni. Well 8.1 is still there as lineageOs is still updating and giving security fixes. And most of commits are there for ok our phones in Omni GitHub.
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
ianseer said:
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
Click to expand...
Click to collapse
Well, if you are encrypted you will need to uncrypt your phone.
!!!!!!!But you will lose everithing saved in internal memory!!!!!!!!
Just follow steps 1 to 8 from my previous guide. Then you can reinstall the ROM. If you will install International ROM you will get encrypted again if you don't run Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip right after installing ROM in TWRP!!!!!!!
Wiping everything with original recovery is the best way to clear your phone!!! sometimes is mandatory this, even with advanced wipe in TWRP you wont achieve what you can with original recovery wipe!
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
methuselah said:
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
Click to expand...
Click to collapse
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
well it doesn't work. It's a part of kernel I guess. There are no sounds from loudspeaker. and there are huge issues with pie in phh treble. He needs logs for that. You can't even login into the google account. There are logs with on treble Phh thread. August images are there. Start taking logs after reading the thread. You will be happy to help him.
ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
Did you posted any log?
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: [url]http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file[/URL]
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : [url]http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file[/URL]
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : [url]http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file[/URL]
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688[/URL]
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
[url]https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list[/URL] ,
or here:
[url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development[/URL]
About treble experimentation here: [url]https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29[/URL]
For example I like the DESCENDANT 3.1.1 : [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578[/URL] but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello sir, I followed each and every step, but device ended up in bootloop. Mostly a soft brick. Every time I power on the device, the logo comes and phone turns off.
I even tried to patch the fstab in /vendor/etc. Same results.
By the way, I could not get the V114 stock global rom which you have mentioned but was able to get V109 stock global rom. If you have the link of the stock rom you mentioned, please provide a link for it. I will just revert back to stock and use it that way. Seems like the device doesn't wants to have an unlocked bootloader and a uncrypted data state ?
ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Zenith9082 said:
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Click to expand...
Click to collapse
you mean twrp mentioned that your device is locked?

How to reset firmware

so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Um, i think ur in the wrong category
thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .
thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help

Merlin , bricked , cant enter fastboot or recovery, cant turn device off , bootloop

Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Ifuckinghatemyselfandall said:
Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Click to expand...
Click to collapse
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
flairepathos.info said:
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
Click to expand...
Click to collapse
I am going to try the mtk bypass tool, is that going to work? if not i am going to try your instructions, however it did not boot into the recovery even after reflashing , i have tried that before with the twrp app
It cannot detect the device, it isnt in device manager either, i am getting scared
edit: actually it gets detected in device manager as "usb serial device (com4)" when i hold the power button, volume up and volume down at the same time, when i do that, the device stays with a black screen
SP flash tool still does not detect it
it seems to be disconnecting while in this state
Please help, i cant turn the device off
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Ifuckinghatemyselfandall said:
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Click to expand...
Click to collapse
You need to flash the SAME miui version present on the device first.
VD171 said:
You need to flash the SAME miui version present on the device first.
Click to expand...
Click to collapse
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
It is now giving me "error status error" please help
Ifuckinghatemyselfandall said:
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
Click to expand...
Click to collapse
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
VD171 said:
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
Click to expand...
Click to collapse
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Ifuckinghatemyselfandall said:
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Click to expand...
Click to collapse
Custom recovery will never brick a device.
VD171 said:
Custom recovery will never brick a device.
Click to expand...
Click to collapse
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Ilovethewholeworldbutme said:
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Click to expand...
Click to collapse
Just flash the full stock miui again.

Question Phone Soft Bricked ?

Hi guys,
I was on "xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.20.0.RKACNXM_v12-11.zip" (rooted with Magisk and with 2-3 modules), this Rom is from end of 2021 so I decided that I have to move on and give a try to "xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12".
First I decided to update my TWRP. I can't remember but I think that it was the one included in the v12.5.20 Xiaomi.EU Rom. I wanted to install "twrp-3.6.2_12-v5.1_A12-star-skkk.img".
First I removed PIN + Fingerprint and then restarted in Fastboot and booted with this kkk TWRP with "fastboot boot twrp.img", then I installed it with "Install Recovery Ramdisk", then rebooted to recovery (it was still ok) and finally rebooted to system ... and now it reboots in Fastboot.
I still have access to TWRP and I can see my files, so before I mess up more I'm backuping some files but it's f#£%ing slow .
What step(s) should I do to make the rom work again ?
I think of flashing Magisk-uninstaller (new TWRP told me at the end of installation that root was lost and that I had to re install it). Maybe there is something remaining from Magisk ?
Then, I think I'll flash "xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.20.0.RKACNXM_v12-11.zip" again.
Do you have any advice ?
Thanks in advance.
P.S. : I know that I should post on Xiaomi.EU but I've tried to create an account on their forum since many years and it's insane but I used ~10 emails and I always have been detected as a bot or spam .
chrissss91 said:
Hi guys,
I was on "xiaomi.eu_multi_MI11Pro_MI11Ultra_V12.5.20.0.RKACNXM_v12-11.zip" (rooted with Magisk and with 2-3 modules), this Rom is from end of 2021 so I decided that I have to move on and give a try to "xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.13.0.SKACNXM_v13-12".
Click to expand...
Click to collapse
Always unroot before.
2 options:
Xiaomi eu rom v12 or 13, but you will need to format the data before flashing
Twrp/wipe/format data/type yes/reboot twrp.
If errors(red lines)repeat the operation.
Or use Miflash https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
In both cases you will lose your data.
You can try a backup with the twrp (without guarantee).
NOSS8 said:
2 options:
Xiaomi eu rom v12 or 13, but you will need to format the data before flashing
Twrp/wipe/format data/type yes/reboot twrp.
If errors(red lines)repeat the operation.
Or use Miflash https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
In both cases you will lose your data.
You can try a backup with the twrp (without guarantee).
Click to expand...
Click to collapse
Thank you for your answer.
So nothing special, just flash and format data before if it's a different one ?
The simplest would be to flash again the Rom I was on ?
chrissss91 said:
The simplest would be to flash again the Rom I was on ?
Click to expand...
Click to collapse
Of course but my answer was along the lines that it wouldn't work.
NOSS8 said:
Of course but my answer was along the lines that it wouldn't work.
Click to expand...
Click to collapse
Flashed old Rom and everything is fine
So I'm back to the beginning .
Now I don't know how to move to last Xiaomi.EU.
Since kkk TWRP was ok to flash the old ROM, do you think it'll be ok to install last Xiaomi.EU ? Or maybe there is a better/safer TWRP to do it ?
And thx again for your support
chrissss91 said:
Flashed old Rom and everything is fine
So I'm back to the beginning .
Now I don't know how to move to last Xiaomi.EU.
Since kkk TWRP was ok to flash the old ROM, do you think it'll be ok to install last Xiaomi.EU ? Or maybe there is a better/safer TWRP to do it ?
And thx again for your support
Click to expand...
Click to collapse
Use the lastest Twrp.(updated today).
Make a backup before(Micloud).

Categories

Resources