Previsouly, I used TWRP v8 and EU MIUI 8.7.19 and today I updated EU MIUI 8.8.3.
After ROM installation, my system is booted to TWRP mode.
I successfully reinstalled EU MIUI ROM, and worked well until TWRP work.
After using TWRP, my system is booted to TWRP mode..
How can I fix this TWRP loop problem.
Please help me.
Thank you.
Format data and working.
Gesendet von meinem MIX 2S mit Tapatalk
Related
I don't understand anything
First I unlock bootloader and install recovery (many failures with recovery versions, drivers etc, but in the way all ok)
Then, directly wipe all from phone (stock 5.0.2) and flash 7.1.2 AOKP.
The phone don't boot, I can't enter to recovery, fastboot is not recognized properly. The Eluga tool saves the phone, the panasonic 5.0.2 firmware works.
Now, I flash the 3.0.0-1 TWRP and flash FlyOs 6.0.1 and the phone stuck on Powered by Android logo.
I flash anothet 2 roms with the same.
ROMs like aokp or lineageOs.
What kind of magic is this?
Please, help
Thanks!
Enviado desde mi Redmi Note 3 mediante Tapatalk
cbd dvd said:
I don't understand anything
First I unlock bootloader and install recovery (many failures with recovery versions, drivers etc, but in the way all ok)
Then, directly wipe all from phone (stock 5.0.2) and flash 7.1.2 AOKP.
The phone don't boot, I can't enter to recovery, fastboot is not recognized properly. The Eluga tool saves the phone, the panasonic 5.0.2 firmware works.
Now, I flash the 3.0.0-1 TWRP and flash FlyOs 6.0.1 and the phone stuck on Powered by Android logo.
I flash anothet 2 roms with the same.
ROMs like aokp or lineageOs.
What kind of magic is this?
Please, help
Thanks!
Enviado desde mi Redmi Note 3 mediante Tapatalk
Click to expand...
Click to collapse
Upgrade to MM (DarkOr or Googly) then upgrade to N. Recommended to use FireLord's TWRP.
Huskied said:
Upgrade to MM (DarkOr or Googly) then upgrade to N. Recommended to use FireLord's TWRP.
Click to expand...
Click to collapse
The phone stuck on Alcatel logo (bootanimation of ROM) when I flash DarkOr
The link of Googly ROM is broken in the thread
cbd dvd said:
The phone stuck on Alcatel logo (bootanimation of ROM) when I flash DarkOr
The link of Googly ROM is broken in the thread
Click to expand...
Click to collapse
I would suggest downgrading back to LP then to MM and finally to N.
I have mediapad x2 gem-702l b006, I flashed twrp 5.1 by accident and now it won't boot into recovery and it would factory reset, no adb, only fast boot. Nothing works, please help!
Did you try to fastboot flash another recovery, stock or TWRP ?
recovery sources:
https://www.androidfilehost.com/?w=files&flid=168446
https://forum.xda-developers.com/mediapad-x2/general/mediapad-x2-gem-703l-easy-stock-t3173506
https://yadi.sk/d/5YI63uiAhz5UD/Recovery/Original
http://cn.club.vmall.com/thread-3975008-1-1.html
flash the original recovery. I extracted the file for you from this new B206 and uploaded it herehttps://drive.google.com/file/d/1SZEaIptVnPygxRRNA72iymdUbcjirOJp/view?usp=sharing
fastboot flash recovery recovery.img
then flash the 6.0 TWRP to recovery2 partition to have both.
fastboot flash recovery2 TWRP_3.1.1-0_DeepBlue_X2.img
Please report if you were able to root this version.
@aut92 did you had success?
Gesendet von meinem MHA-L29 mit Tapatalk
audioralf said:
@aut92 did you had success?
Gesendet von meinem MHA-L29 mit Tapatalk
Click to expand...
Click to collapse
I did Indeed thank you
Hi all,
Is anyone rooted on global hardware global ROM 10.3.1.0? I've been getting the update notifications for a while but have been hesitant to update in case I loose root, I've never updated with an OTA on a rooted device before. To update, can I just download the OTA then reflash TWRP and Magisk and be good to go? Has anyone tried this? If so, what version of TWRP and Magisk did you use successfully?
Thanks in advance for any input/advice!
Download the OTA, install it via TWRP, boot into the system and flashing TWRP via ADB again. Boot into the TWRP and flash again magisk. That's how it worked for me. At least with my mix 2 [emoji1360]
Gesendet von meinem MIX 3 mit Tapatalk
I'm running Android 10 and OOS 10.0.2 GM21AA.
I'v clean flashed the OOS 10.0.2 and rooted the phone by flashing Magisk through TWRP Latest build. Initially the root was going well.
After installing youtube vanced module from magisk, i rebooted the phone and it doesn't rebooted. It got stuck in OEM Unlock Warning screen for a while then automatically shifted to fastboot mode.
Then i flashed the stock boot.img and phone became good to go.
I flashed the stock boot.img patched with magisk. But the phone doesn't get any signal(SIM UNKNOWN) after reboot.
I tried changing magisk and twrp versions also, but it didn't work.
I need help of you guys. Please suggest me.
Use the following thread!
It works fine!
https://forum.xda-developers.com/showthread.php?t=3940368
Gesendet von meinem GM1913 mit Tapatalk
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
I flash magisk 20.1 after every eu update.
First i flash the eu update. After that i boot in recovery again. Then i flash magisk and clean dalvik and cache. Then i boot system.
If you flash into the recovery magisk after the eu update without restarting, it ends in the bootloop.
At least it was with me like that.
Gesendet von meinem MIX 3 mit Tapatalk
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
I'm running Magisk 19.4 (the one for Xiaomi devices obviously) on Xiaomi.eu beta 9.12.12. No initial issues or any since
You should always reboot first, otherwise magisk will bootloop
Giuskiller said:
You should always reboot first, otherwise magisk will bootloop
Click to expand...
Click to collapse
A reboot into twrp is enough
Gesendet von meinem MIX 3 mit Tapatalk
I can confirm that magisk 19.3 work fine on lastest eu stable 11.0.1.0 android 10.
i have the last xiaomi.eu beta and the last magisk and all work good
kiwan955 said:
i have the last xiaomi.eu beta and the last magisk and all work good
Click to expand...
Click to collapse
I too [emoji1360]
Gesendet von meinem MIX 3 mit Tapatalk
Dathrex said:
Hey guys, yesterday I got EU update to Android 10. And flashed Magisk 17. but I got bootloop. Then updated TWRP to latest and flashed Magisk 20.1
No luck. Do I need specific version?
Thank you
Click to expand...
Click to collapse
From my experience in mix 2s. If i have a MIUI with magisk modules active, then flash new rom, restart, flash magisk, then wipe dalvik, i get bootlooped. The solution was to disable all magisk modules before updating and then flash magisk, wipe dalvik and restart. After getting into the OS, reactivate the modules.
If you have a twrp based recovery that allows you to disable magisk modules from the recovery (like orange fox) that may help you get out of the bootloop.
Give it a try