Database Info

Cannot start ROM / permanent reboot into recovery

Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy

jjeans said:
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
Click to expand...
Click to collapse
Download fastboot rom and flash it

thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS

jjeans said:
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
Click to expand...
Click to collapse
How do you flash recovery tell me the procedure?

Talha7866 said:
How do you flash recovery tell me the procedure?
Click to expand...
Click to collapse
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy

jjeans said:
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
Click to expand...
Click to collapse
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.

zhart said:
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
Click to expand...
Click to collapse
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.

jjeans said:
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
Click to expand...
Click to collapse
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.

Sorry, what exaclty is a fastboot rom and where do i get it?

zhart said:
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Click to expand...
Click to collapse
I don't know what happens all the time.
Currently I used MiFlash to make a clean fastboot install. I choosed in MiFlash "flash_all.bat" to do it. (flash_all.bat means everything was reinstalled, also recovery.img). Afterwards everything was normal, MiRecovery 2.x and Mi4C MiUI 7 chinese version was installed without error. But after manual flashing TWRP with "fastboot flash recovery xxx", the recovery loop was again! :/
So AGAIN I made a clean fastboot install again with MiFlash application, but this time I REPLACED the recovery.img with the newest TWRP (renamed to recovery.img) within the fastboot rom installation folder "images". I could see that MiFlash flashed THIS! recovery.img, but after that again the old Mi Recovery was on the device and no TWRP. But why? I replaced the original recovery.img file! How can that happen?
The flash_all.bat included flashing recovery and I could confirm it during the fastboot flash. Strange.
I used fastboot rom libra_images_V7.0.16.0.LXKCNCI_20151104.0000.4_5.1_cn
MiFlash newest version and I tried with 2 TWRP versions (one from decuro and one from sMiUI)

Maybe my phone has a problem with flahing recoverys in general I don't know.

jjeans said:
Maybe my phone has a problem with flahing recoverys in general I don't know.
Click to expand...
Click to collapse
it sound very strange i did all these steps and my phone was all good after it. is it the newest recovery? the one with material theme and touch fix you are using? if not, then thats the only difference between your procedure and mine :/
i hope you can fix it
Edit: I can see that i have the following fastboot roms downloaded, so i used one of these:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn_4dd76a55cb.tgz
or libra_images_V7.0.15.0.LXKCNCI_20151104.0000.4_5.1_cn_f6e955ee14.tgz

What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...

Hello, don't know if applicable. I've read on mi forums that dev Roms need dev recovery, that's different from twrp for stock rom.....

guegangster said:
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Click to expand...
Click to collapse
Hallo,
thank you, that worked for me finally
I have now used another TWRP 2.8.7.1 with touch-issue, but that is now no problem.
I flashed also xiaomi.eu rom, for now seems to be stable and cleaned.
strange everything, but now it is fixed.
BR,
Jimmy

Leeco le2 x526 stock 5.8.19s

Those who are looking for stock 19s ROM, the g drive link is here
https://drive.google.com/uc?id=0BwU--kMdOmZiREUxUXR2eTgwX2s&export=download
How to flash?
Put the file downloaded in root directory
Boot into fastboot mode
Flash stock recovery
Now boot into TWRP recovery using following command
fastboot boot TWRP.img
Wipe Cache, dalvik cache and system.
Reboot to recovery
Now you will be in stock recovery
Update from here.
First boot might take time.

Is it possible to flash this with twrp?
Sent from my X520 using Tapatalk

lak2004mi said:
Is it possible to flash this with twrp?
Sent from my X520 using Tapatalk
Click to expand...
Click to collapse
No only via stock recovery

djdeve said:
Those who are looking for stock 19s ROM, the g drive link is here
https://drive.google.com/uc?id=0BwU--kMdOmZiREUxUXR2eTgwX2s&export=download
How to flash?
Put the file downloaded in root directory
Boot into fastboot mode
Flash stock recovery
Now boot into TWRP recovery using following command
fastboot boot TWRP.img
Wipe Cache, dalvik cache and system.
Reboot to recovery
Now you will be in stock recovery
Update from here.
First boot might take time.
Click to expand...
Click to collapse
if i flash stock recovery thn if i try to boot into recovery thn phone will open in stock recovery only thn hw cn i flash?

cjcool_123 said:
if i flash stock recovery thn if i try to boot into recovery thn phone will open in stock recovery only thn hw cn i flash?
Click to expand...
Click to collapse
True..
Use Chinese twrp and flash .. Works for me and many others .. Ensure to flash no verity zip post flashing
Or do changes in updater script and repack the zip

cjcool_123 said:
if i flash stock recovery thn if i try to boot into recovery thn phone will open in stock recovery only thn hw cn i flash?
Click to expand...
Click to collapse
After flashing stock recovery don't reboot you phone in stock recovery, bcoz you can't wipe system in stock recovery to do so ,
Reboot your phone into fastboot mode by pressing vol down and power button and connect your phone to PC and from CMD prompt run the following command
Fastboot boot twrp.img

Actually my phone was bootlooped when i tried installing twrp img of chinese version and im unable to flash ROM. Before this i used latest twrp and flashed RR and lineage OS. Volte worked fine in both the roms and in stock rom too. After this happened i installed AIO tool kit and flashed chinese twrp again. Then done flashing with lineage OS there the volte is broken. I thought it would be some software error and i tried flashing RR and found the same broken volte! Can anyone help me out in enabling volte in my le eco le2 (s2) x526.

Bootloader and Modem S2
Try flashing 19s bootloader and modem from here
https://host.llamasweet.tech/codeworkx/lineage/s2/
Thankx @codeworkx for this.

one more link for stock 19s rom
https://drive.google.com/file/d/1BgXejpbVug4KR5Mc6-eFWom6gVR96UhK/view?usp=drivesdk

custom to stock rom
if we are in custom rom and we have to go back for stock rom with stock recovery will it work by just copying the zip file into the phone and rename into update.zip
And then clicking on update will it work Guys ??

error while installing This package is for "le_s2_ww" devices;this is a "s2'.

bootloop
I tried to install the stock ROM provided by 2 ways :-
1) booting into previous version of twrp using fastboot commands and then the regular install after wiping required files.
2) Renaming it to update.zip and placing it into sdcard then via stock recovery.
it gets installed every time without any error but gets into boot loop with both steps.
Is there any way to get completely stock again ?

akakumar said:
I tried to install the stock ROM provided by 2 ways :-
1) booting into previous version of twrp using fastboot commands and then the regular install after wiping required files.
2) Renaming it to update.zip and placing it into sdcard then via stock recovery.
it gets installed every time without any error but gets into boot loop with both steps.
Is there any way to get completely stock again ?
Click to expand...
Click to collapse
Flash twrp via following toolkit .beacause only this recovery works to flash stock roms
https://forum.xda-developers.com/devdb/project/?id=16391#downloads
Open twrp do factory reset and wipe data , cache , dalvik cache . Dont wipe system . Then flash the rom . Dont flash magisk or any root app . Reboot . You got a notification from twrp that replace stock recovery . Dont replace recovery . Once rom boot setup everything .now bootloader is locked and twrp replaced via stock recovery .

Deepjashan said:
Flash twrp via following toolkit .beacause only this recovery works to flash stock roms
https://forum.xda-developers.com/devdb/project/?id=16391#downloads
Open twrp do factory reset and wipe data , cache , dalvik cache . Dont wipe system . Then flash the rom . Dont flash magisk or any root app . Reboot . You got a notification from twrp that replace stock recovery . Dont replace recovery . Once rom boot setup everything .now bootloader is locked and twrp replaced via stock recovery .
Click to expand...
Click to collapse
Hard Luck !!
its been more than half an hour and still at the same boot loop. the installation was successful as well , screenshot attached below.
PS: Ignore the cracked screen.

akakumar said:
Hard Luck !!
its been more than half an hour and still at the same boot loop. the installation was successful as well , screenshot attached below.
PS: Ignore the cracked screen.
Click to expand...
Click to collapse
I use this mathod everytime when i need stock rom. It works for me

my phone caps my speed to 4 Mbps after few minutes. It's not a isp or router based problem.
Actually I faced this problem after I flashed back to Eui 19s from 21s.

akakumar said:
I tried to install the stock ROM provided by 2 ways :-
1) booting into previous version of twrp using fastboot commands and then the regular install after wiping required files.
2) Renaming it to update.zip and placing it into sdcard then via stock recovery.
it gets installed every time without any error but gets into boot loop with both steps.
Is there any way to get completely stock again ?
Click to expand...
Click to collapse
Deepjashan said:
Flash twrp via following toolkit .beacause only this recovery works to flash stock roms
https://forum.xda-developers.com/devdb/project/?id=16391#downloads
Open twrp do factory reset and wipe data , cache , dalvik cache . Dont wipe system . Then flash the rom . Dont flash magisk or any root app . Reboot . You got a notification from twrp that replace stock recovery . Dont replace recovery . Once rom boot setup everything .now bootloader is locked and twrp replaced via stock recovery .
Click to expand...
Click to collapse
Alright I found a way ...I read it in some other discussion on le2 .
The step by step procedure to get stock back is listed :-
1) As usual reboot to recovery
2) wipe cache, dalvik, system and data
3)install the stock ROM
Now when you reboot you will get stuck into boot loop at the leeco logo.... wait for 5 mins and test your luck if it works otherwise follow next
4) go back to recovery by pressing vol up and power button.
5) install Andromodx kernel
Reboot and voila you have it running.
Also you can flash the stock recovery and lock OEM by fastboot commands
The only issues I have right now are two
1) the display scale is set to zoom and even if I set it to standard it reboots but doesn't change. I scaled down pixel density by adb commands but still its weird at some places
2) it crashes a lot ... sometimes when I press home or multitasking button it just goes black and EUI reboots. I also did a factory reset but no use.
If anyone can help me in that ....:laugh:

flash
djdeve said:
No only via stock recovery
Click to expand...
Click to collapse
give complted process for flash stock rom to letv le 2 x526

Error while flashing
Error while installing This package is for "le_s2_ww" devices;this is a "s2'.
Can you do something about it ?

akakumar said:
Hard Luck !!
its been more than half an hour and still at the same boot loop. the installation was successful as well , screenshot attached below.
PS: Ignore the cracked screen.
Click to expand...
Click to collapse
Just figured this out with the help of another post on a separate thread.
It seems that the latest twrp for x526 (v 3.2.1.0) has a bug such that when you format the data partition - it writes a wrong partition size.
This causes the boot loop with the stock ROM (other custom ROMs seems to be happy living with the error).
An associated side effect of the wrong partition size is that you wont be able to encrypt your phone on the custom ROM (the encryption process simply causes the phone to reboot without doing anything).
To resolve this, downgrade twrp to v 3.0.2. Then format cache/system/data.
Then mount the phone to your PC (enable MTP) and copy the stock ROM of your choice.
You need to update the "updater-script" and comment out the version check - and then you can install the stock ROM using twrp.
This worked for me.
Hope it works for you as well.
PS: Once you install the stock ROM, the data partition gets encrypted and first boot takes a lot of time.
Be patient and also know that twrp will no longer be able to decrypt your data partition (I think either twrp is broken OR the stock ROM uses some other default password to encrypt the data partition and hence decryption fails. I have tried using my screen lock PIN and it doesn't work and "default_password" does not work either.
All the best.
---------- Post added at 06:56 AM ---------- Previous post was at 06:52 AM ----------
satyamsahu366 said:
Error while installing This package is for "le_s2_ww" devices;this is a "s2'.
Can you do something about it ?
Click to expand...
Click to collapse
Open the update.zip file on your PC and navigate to META-INF/com/google/android.
You will find a file by the name updater-script.
Use your favourite text editor to open this file and then find the following line:
get_device_compatible("le_s2_ww") == "OK" || abort("This package is for "le_s2_ww" devices; this is a "" + getprop("ro.product.device") + "".");
Insert a # at the beginning of the line to get the installer to ignore the version mismatch and you should be good to go.
It should now look like this:
#get_device_compatible("le_s2_ww") == "OK" || abort("This package is for "le_s2_ww" devices; this is a "" + getprop("ro.product.device") + "".");
Now save this file and update the zip file / create a zip file again and then proceed with the installation as usual.

How To Successfully Install Twrp For G7 Play

Im Pretty Sure Everyone that will read this thread will have an unlocked bootloader.
Requirments: an Unlocked Bootloader. A PC. And Some Knowledge about Android Coustomization.
So for twrp to boot Correctly Your Going to need a modified dtbo image with out it your going to have twrp boot into a black screen with minimal file transfer capabilities
The DTBO image i use is This One
https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing
next your going to need a twrp thats stable i suggest this one
https://drive.google.com/file/d/13MROGlEA_TdgHFTaiqOswo4w0NgXhGbx/view?usp=sharing
now that you have the files
first hold power and volume up till you see a black screen with text saying fastboot flash mode
now we are going to get the recovery installed by running two commands in fastboot
first command fastboot flash dtbo /path/to/yours.img
run the next command fastboot boot twrp4.img
now you should see the twrp recovery splash screen
now we are going to go to mount this will pop up a file transfer window on your pc
drag twrp4.img to a directory you know where its at
backout of mount and go to install
select the directory where your twrp4.img is at
then click install image
it should show you that twrp is there click on twrp4.img
select install to recovery ramdisk
swipe to confirm flash
wait till its done then click back
go to advanced click fix recovery bootloop
swipe to confirm
then go back click reboot
select recovery
you can unplug your phone now
and you will see twrp is now installed on your device
click reboot select poweroff
hold volume down and power untill you see that text again from fastboot
this time use volume up to scroll through your options untill you find recovery mode then press power
you will be booted into twrp do that for when ever you need to access your recovery
hope this tutorial helps
and thanks to spaceminer for making this twrp
and thanks to scritch007 for modifing the dtbo img

it doesnt work we need a flashable.zip method
---------- Post added at 07:35 AM ---------- Previous post was at 07:11 AM ----------
must add must wipe data first , flash disable verity.zip will post , then install recovery to ramdisk after copying it to the sdcard , didnt click fix recovery bootloop and it works perfectly fine

thenatti said:
it doesnt work we need a flashable.zip method
---------- Post added at 07:35 AM ---------- Previous post was at 07:11 AM ----------
must add must wipe data first , flash disable verity.zip will post , then install recovery to ramdisk after copying it to the sdcard , didnt click fix recovery bootloop and it works perfectly fine
Click to expand...
Click to collapse
flash this after format data , then follow steps mentioned above , thank you everyone for your hardwork on bringing us a stable release

thenatti said:
flash this after format data , then follow steps mentioned above , thank you everyone for your hardwork on bringing us a stable release
Click to expand...
Click to collapse
Yeah I forgot to put the decryptor zip in the tutorial
I did use it tho ill edit the tutorial in a few

Linuxassassin said:
Yeah I forgot to put the decryptor zip in the tutorial
I did use it tho ill edit the tutorial in a few
Click to expand...
Click to collapse
I noticed with stock firmware it boot loops I'm currently running the dot os treble image and it's consistent , but not with stock unless there is no data ,.but when data is created it boot loops , I recommend flashing the treble gsi image , the only bug is no proper notch support and I don't have a Linux but to attempt to create an overlay

thenatti said:
I noticed with stock firmware it boot loops I'm currently running the dot os treble image and it's consistent , but not with stock unless there is no data ,.but when data is created it boot loops , I recommend flashing the treble gsi image , the only bug is no proper notch support and I don't have a Linux but to attempt to create an overlay
Click to expand...
Click to collapse
the notch is
the notch isnt terible to be honest also to flash gapps get the device id apk will help you certify your device to be able to install stuff from the google play store

Well. The touchscreen is not working for me. But I think is because I am on 1952-1.

Savinu' said:
Well. The touchscreen is not working for me. But I think is because I am on 1952-1.
Click to expand...
Click to collapse
what slot are you on

Linuxassassin said:
what slot are you on
Click to expand...
Click to collapse
On slot a

thenatti said:
flash this after format data , then follow steps mentioned above , thank you everyone for your hardwork on bringing us a stable release
Click to expand...
Click to collapse
Can you tell me the right how should I flash this zip? I'm new to TWRP and Magisk, and I'm trying to get root for my G7 Play. I know there is the sideload flashing from ADB and the install update option in stock recovery, but I don't know if one of them is the way to flash it or if it's a way that I don't know.
Thanks in advance

on my moto g7 play xt1952-2 the touchscreen stopped how to solve?

great job
big thank you to all that had a hand in getting a working twrp for the g7 play!!! it worked perfectly the first time i did it

Fails to install twrp to recovery ramdisk
Hi!
I've tried to follow the guide but somehow I fail to install the twrp image to the recovery ramdisk.
When updating partition details, it fails to mount '/vendor' (invalid argument)
Then when it tries to backing up the boot it fails:
cd /tmp/repackorig/ && /sbin/magiskboot --unpack -h '/tmp/repackorig/boot.img' process ended with Error 1. Error unpacking image.
Any suggestions to solve this?
Output from recovery.log
[IMAGE FLASH STARTED]
Image to flash: '/sdcard/twrp4.img'
Unpacking Boot...
Backing up Boot...
I:Reading '/dev/block/bootdevice/by-name/boot_b', writing '/tmp/repackorig//boot.emmc.win'
I:Restored default metadata for /tmp/repackorig//boot.emmc.win
Parsing boot image: [/tmp/repackorig/boot.img]
cd /tmp/repackorig/ && /sbin/magiskboot --unpack -h '/tmp/repackorig/boot.img' process ended with ERROR: 1
I:Error unpacking /tmp/repackorig/boot.img!
Error unpacking image.
I:Set page: 'action_complete'
Iperation_end - status=1

Got stuck trying to follow the above recipe as it hasn't yet been edited to include the additional details about for example the no-verity thing... Would appreciate an update. Thx.

There's a new build that should work on all models including RETUS. You guys can find that here. It has /vendor & /oem backup and restore but they're untested. I do need some help with it if anyone here is savvy enough. In it's current state, it bootloops with the stock OS installed. But not when a GSI is installed. The recovery loop fix in twrp doesn't work, and I'm not sure how to make it work.

need help
i can boot to twrp using fastboot but any other time it just flashes and wont load plz help also i dont have root just saying

Spaceminer said:
There's a new build that should work on all models including RETUS. You guys can find that here. It has /vendor & /oem backup and restore but they're untested. I do need some help with it if anyone here is savvy enough. In it's current state, it bootloops with the stock OS installed. But not when a GSI is installed. The recovery loop fix in twrp doesn't work, and I'm not sure how to make it work.
Click to expand...
Click to collapse
I'm pretty sure I've sussed it out.
I noticed that G7 River has an extra step.. once TWRP in ramdisk and also bootloop fix ran...
They use https://dl.twrp.me/river/twrp-installer-3.3.1-2-river.zip.html
So , Hope you don't mind, I unpacked your TWRP and exchanged the ramdisk-trwp.cpio in the river zip with yours.
Flashed it after the bootloop fix and it installs to boot a and b.
I then formatted data, installed latest canary magisk manager zip
then no verity from here
it's succesfully rebooted to setup (as I formatted data obviously) .... now to go through setup... but the fact it's got this far looks good

CFKod said:
I'm pretty sure I've sussed it out.
I noticed that G7 River has an extra step.. once TWRP in ramdisk and also bootloop fix ran...
They use https://dl.twrp.me/river/twrp-installer-3.3.1-2-river.zip.html
So , Hope you don't mind, I unpacked your TWRP and exchanged the ramdisk-trwp.cpio in the river zip with yours.
Flashed it after the bootloop fix and it installs to boot a and b.
I then formatted data, installed latest canary magisk manager zip
then no verity from here
it's succesfully rebooted to setup (as I formatted data obviously) .... now to go through setup... but the fact it's got this far looks good
Click to expand...
Click to collapse
I'm not upset at all, if anything I am very pleased. Nice work!

Man so close but still not quite. Installed magisk manager but no root...
When I reboot to Twrp it shows the two front screen but then starts having a seizure flashing n ****....... Works to fastboot into the IMG again...
So close.. ummmm

CFKod said:
Man so close but still not quite. Installed magisk manager but no root...
When I reboot to Twrp it shows the two front screen but then starts having a seizure flashing n ****....... Works to fastboot into the IMG again...
So close.. ummmm
Click to expand...
Click to collapse
Try dumping the boot.img after you've done everything to install twrp, then manually patch it with magisk, and flash it with fastboot.

Ultimate guide to install stable or Dev rom from Xiaomi.eu

Hello everyone,
First of all, rom and recovery are not from me... I just want to make a full guide to help you
So let's go !!!!!
1 step: unlock bootloader
https://en.miui.com/unlock/
BE CAREFUL unlocking your bootloader will erase all your data (internal storage) so don't forget to make a backup
2 step: flash twrp recovery
Download the recovery image from here
https://drive.google.com/file/d/1-1CSfT4lQwFZngu6RI9eowLA9CmEMEPw/view?usp=drivesdk
Be sure to have adb and fastboot tools on your computer ... If not take a look at here
https://forum.xda-developers.com/showthread.php?t=2317790
Past TWRP_umi.img on minimal adb and fastboot directory.
Open a cmd here.
Enable usb debugging on your device
Reboot your phone on bootloader (hold volume down + power), connect it to PC and tape:
fastboot devices
fastboot flash recovery TWRP_umi.img
Then tape fastboot reboot while holding volume up button on your devices to reboot in recovery
3 step:
At the first launch of Twrp You have to choose SWIPE TO ALLOW MODIFICATION
4 step:
THIS ONE OF THE MUST IMPORTANT STEP
In twrp menu you have to go in Wipe data on choose format data
Otherwise the ROM will not boot.
5 step:
Reboot into recovery from twrp.
6 step:
Connect your phone to your PC and paste the xiaomi.eu ROM of your choice (stable or Dev)
7 step:
Flash ROM from recovery
8 step:
REBOOT AND ENJOY :good::good::good:

Does Xiaomi EU Rom run either on encrypted and unencrypted storage?

I cant get this to work, ive been trying everything for hours. I am sure i am missing something stupid but if anyone has any new ideas please let me know. I unlocked my device today, flashed twrp via fastboot, rebooted to recovery, formatted data then went on to install xiaomi eu rom. Ever since trying this, i am constantly booting into recovery or hitting a boot loop. i have formatted data more times than i care to think of ha ha. ive tried flashing the latest fastboot rom via mi unlock tool to do a fresh start but keep getting ''flash crclist error". Ive also tried flashing miui stock via twrp and it also, doesn't boot. ive tried many combinations in between. My next option is to try the fastboot global rom (though i believe i have a chinese device), i am waiting for it to download. If anyone knows what i am doing wrong i will be eternally grateful if you can tell me what it is. I'm so frustrated, been flashing roms for years, never had anything take as long as this :crying:

carolef1984 said:
I cant get this to work, ive been trying everything for hours. I am sure i am missing something stupid but if anyone has any new ideas please let me know. I unlocked my device today, flashed twrp via fastboot, rebooted to recovery, formatted data then went on to install xiaomi eu rom. Ever since trying this, i am constantly booting into recovery or hitting a boot loop. i have formatted data more times than i care to think of ha ha. ive tried flashing the latest fastboot rom via mi unlock tool to do a fresh start but keep getting ''flash crclist error". Ive also tried flashing miui stock via twrp and it also, doesn't boot. ive tried many combinations in between. My next option is to try the fastboot global rom (though i believe i have a chinese device), i am waiting for it to download. If anyone knows what i am doing wrong i will be eternally grateful if you can tell me what it is. I'm so frustrated, been flashing roms for years, never had anything take as long as this :crying:
Click to expand...
Click to collapse
try rhis
format data (not wipe)
put rom.zip unto ur internal storage
wipe cache an dalvik cache
now flash the zip
now reboot to recovery
wipe cache an dalvik cache
an now go to reboot menu
an now power off
an now power it on

-fluffy- said:
try rhis
format data (not wipe)
put rom.zip unto ur internal storage
wipe cache an dalvik cache
now flash the zip
now reboot to recovery
wipe cache an dalvik cache
an now go to reboot menu
an now power off
an now power it on
Click to expand...
Click to collapse
Thank you for trying to help, unfortunately it just rebooting to my recovery still. I dont suppose anyone has any other ideas do they please I cant understand what on earth ive done wrong. Does anyone know why mi flash tool comes up with that error (flash crc list error)? qualcomm drivers are installed.

carolef1984 said:
Thank you for trying to help, unfortunately it just rebooting to my recovery still. I dont suppose anyone has any other ideas do they please I cant understand what on earth ive done wrong. Does anyone know why mi flash tool comes up with that error (flash crc list error)? qualcomm drivers are installed.
Click to expand...
Click to collapse
write what u do wen u try to flash the zip
an have u downloadet the correct zip file

Thanks everyone, i think it must have been something to do with the qualcomm drivers installed incorrectly. i have re-done that from scratch and managed to get mi flash tool working. Sorry to waste everyones time.

Greetings
I have followed the tutorials to perfection like 2-3 times and I still face the same issue
I always go back to TWRP after trying to boot into system.
I have tried 2 different recovery files
The experimental one asks for a password. and the other one works but keeps going back to recovery after flashing.
MIUI 11 rom
MIUI 12 rom
No matter what I do It keeps going back to recovery.
It's my only device so I truly need help.
I have tried re installing everything already.
At this point I just want to install stock rom and keep using it without flashing anything please help.
PHONE FINALLY REBOOTING INTO SYSTEM. I myself don't know what i did!!!

Bootloop (stuck on 5G logo) after flashing Xiaomi.eu ROM
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.
The problems started when I tried to install Xiaomi.eu Custom ROM : xiaomi.eu_multi_MI10_V11.0.25.0.QJBCNXM_v11-10
Downloaded the Xiaomi.eu ROM to PC, then copied to the Download folder of the Phone.
Started phone in upload mode or TWRP. > Wipe > Swipe to Factory Reset + Format Data.
When formatting data I erase all folders in the phone, including the Xiaomi.eu ROM copied in the Download folder.
Some tutorials suggest to copy the Xiaomi.eu ROM from PC to phone after formatting the data, just by connecting the phone in TWRP to the PC, by going to > Mount and enabling MTP.
Tried this method but when I send the Xiaomi.eu ROM file to the phone the progress bas doesn’t move.
So I restarted the phone, without installing the Custom ROM, went through all the screens of initial phone configuration. Lost Magisk and root (but I supposed that it’s not mandatory to install Custom ROM). Copied again the Xiaomi.eu ROM zip file to the Download folder. Rebooted to TWRP. This time I just did Factory Reset but without Format Data. Then > Install to install the Xiaomi.eu new ROM. Cleared Dalvik Cache then reboot.
PROBLEM : bootloop. Stuck with the 5G logo forever, waited more than 30 min, no change.
Still have access to recovery TWRP and to bootloader mode. I suppose this is a soft brick?
I did > Wipe, Swipe to Factory Reset + Format Data, restarted… no change.
Copied this time the Xiaomi.eu ROM to a clean formatted (FAT32) USB drive. As shown in some tutorials, you can us an external USB drive via USB OTG to install the Custom ROM via TWRP.
Factory Reset + Format Data, then I installed again the same Xiaomi.eu ROM from the external USB. Still stuck in bootloop.
Please I need help to fix the problem
I’m not an expert developer, but I’m not a complete noob either.
This is the first time I have troubles with a brand new Xiaomi Phone.
It’s the first time I get a very expensive phone, but had no choice (they are getting very expensive), because I always buy a Flagship Xiaomi to get all the community support possible.
And I had to change the ROM to Xiaomi.eu, because the Official Global ROM is full of bloatware I had a good experience with Xiaomi.eu ROMs with my old Xiaomi Mi 4 and Mi 5.
At this point I don’t mind going back to stock MIUI Global ROM.
I suppose that with access to boot loader I can flash the Official ROM from PC with MiFlash2020-3-14-0? If it’s the case can somebody show me detailed steps to do that?
For Mi 10 Official Global there is the Stable Full ROM (miui_UMIGlobal_V11.0.2.0.QJBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBMIXM_20200328.0000.00_10.0_global_09b168ff9e) (3.76 GB). Which One to flash from PC with MiFlash?
I can’t afford to hard brick the device
Thank you very much.

andromomo said:
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.
The problems started when I tried to install Xiaomi.eu Custom ROM : xiaomi.eu_multi_MI10_V11.0.25.0.QJBCNXM_v11-10
Downloaded the Xiaomi.eu ROM to PC, then copied to the Download folder of the Phone.
Started phone in upload mode or TWRP. > Wipe > Swipe to Factory Reset + Format Data.
When formatting data I erase all folders in the phone, including the Xiaomi.eu ROM copied in the Download folder.
Some tutorials suggest to copy the Xiaomi.eu ROM from PC to phone after formatting the data, just by connecting the phone in TWRP to the PC, by going to > Mount and enabling MTP.
Tried this method but when I send the Xiaomi.eu ROM file to the phone the progress bas doesn’t move.
So I restarted the phone, without installing the Custom ROM, went through all the screens of initial phone configuration. Lost Magisk and root (but I supposed that it’s not mandatory to install Custom ROM). Copied again the Xiaomi.eu ROM zip file to the Download folder. Rebooted to TWRP. This time I just did Factory Reset but without Format Data. Then > Install to install the Xiaomi.eu new ROM. Cleared Dalvik Cache then reboot.
PROBLEM : bootloop. Stuck with the 5G logo forever, waited more than 30 min, no change.
Still have access to recovery TWRP and to bootloader mode. I suppose this is a soft brick?
I did > Wipe, Swipe to Factory Reset + Format Data, restarted… no change.
Copied this time the Xiaomi.eu ROM to a clean formatted (FAT32) USB drive. As shown in some tutorials, you can us an external USB drive via USB OTG to install the Custom ROM via TWRP.
Factory Reset + Format Data, then I installed again the same Xiaomi.eu ROM from the external USB. Still stuck in bootloop.
Please I need help to fix the problem
I’m not an expert developer, but I’m not a complete noob either.
This is the first time I have troubles with a brand new Xiaomi Phone.
It’s the first time I get a very expensive phone, but had no choice (they are getting very expensive), because I always buy a Flagship Xiaomi to get all the community support possible.
And I had to change the ROM to Xiaomi.eu, because the Official Global ROM is full of bloatware I had a good experience with Xiaomi.eu ROMs with my old Xiaomi Mi 4 and Mi 5.
At this point I don’t mind going back to stock MIUI Global ROM.
I suppose that with access to boot loader I can flash the Official ROM from PC with MiFlash2020-3-14-0? If it’s the case can somebody show me detailed steps to do that?
For Mi 10 Official Global there is the Stable Full ROM (miui_UMIGlobal_V11.0.2.0.QJBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBMIXM_20200328.0000.00_10.0_global_09b168ff9e) (3.76 GB). Which One to flash from PC with MiFlash?
I can’t afford to hard brick the device
Thank you very much.
Click to expand...
Click to collapse
try this
format data
reboot recovery
connect phone to pc
put zip file ro phone
wipe cache an dalvik cache
install zip
wipe again
reboot recovery
wipe again
go to reboot
power off the phone
now wen its shut down power it on
an it shut boot
it will take a litle time

andromomo said:
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.JBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBM
Thank you very much.
Click to expand...
Click to collapse
hi didt it work for u

IT WORKED properly like a charm!!!
Dear -fluffy-,
Thank you very much for your quick reply.
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.
---------- Post added at 12:57 PM ---------- Previous post was at 12:47 PM ----------
Dear -fluffy-,
Thank you very much for your quick reply.
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.
---------- Post added at 01:15 PM ---------- Previous post was at 12:57 PM ----------
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.

Quick questions, do netflix and google pay work after the flash?

tott2003 said:
Quick questions, do netflix and google pay work after the flash?
Click to expand...
Click to collapse
yes

cedric3320 said:
4 step:
THIS ONE OF THE MUST IMPORTANT STEP
In twrp menu you have to go in Wipe data on choose format data
Click to expand...
Click to collapse
Hello,
i have a silly question about step 4:
someone says we should "Wipe Data", someone says we should "Format Data" ,
i don't see a real difference unless we want to change the filesystem type.
Advices ?
And also, when we format ( or wipe ) the "Data" partition, are we formatting the 256 GB partition ?
if yes, this is a really huge drawback for us who want to change ROM more frequently than other android users, because we have to backup a 256 GB partition ...
This is not fast to do online ( at least with my poor connection ) and it is not fast to do on PC or on a USB KEY.
So we have 256 GB and we need to format at each ROM change ? Too bad ...
In the good old times i did extract my microSD card and i was safe .
Someone could explain me please ?
thank you all for your patience...

adario73 said:
Hello,
i have a silly question about step 4:
someone says we should "Wipe Data", someone says we should "Format Data" ,
i don't see a real difference unless we want to change the filesystem type.
Advices ?
And also, when we format ( or wipe ) the "Data" partition, are we formatting the 256 GB partition ?
if yes, this is a really huge drawback for us who want to change ROM more frequently than other android users, because we have to backup a 256 GB partition ...
This is not fast to do online ( at least with my poor connection ) and it is not fast to do on PC or on a USB KEY.
So we have 256 GB and we need to format at each ROM change ? Too bad ...
In the good old times i did extract my microSD card and i was safe .
Someone could explain me please ?
thank you all for your patience...
Click to expand...
Click to collapse
Hello,
You have to format data the first time you flash xiaomi.eu rom because their rom is base on Chinese firmware (if you don't or just wipe it will not boot)
Each time you will flash a rom with different base (from Chinese base to global base or global to Chinese) you will have to format data !!

You format data to remove encryption.

tott2003 said:
Quick questions, do netflix and google pay work after the flash?
Click to expand...
Click to collapse
Google pay isn't working as the safety net doesn't pass on stable realeses, someone made it to work on betas but I had no luck though

Stuck without solutions
Hello,
I tried to flash the latest miui 12. I followed all the steps...
But now I can't acess recovery nor rom.
Basically when i try to flash TWRP with bootloader it just goes back to fastboot.
Also note that the flash is successful. But I somehow can't acess TWRP, just goes back to fastboot
And when I flash the experimental TWRP on the dev thread it boots to recovery but asks for a password.. Impossible to flash anything.. Even after I formated data and everything
I tried flashing other TWRP I found but nothing boots even after trying a lot of time.
I tried <fastboot boot recovery.img> as well
I tried <fastboot erase recovery> and then flash the TWRP as well
I've been trying hard for the last 8 hours.
I also have a backup of when I had MIUI 12. But impossible to flash it with the only recovery I can boot to.
I feel so desperate. I'm out of ideas.
If you have any ideas, I'm listening
Thanks for the help guys.

Dallee said:
Hello,
I tried to flash the latest miui 12. I followed all the steps...
But now I can't acess recovery nor rom.
Basically when i try to flash TWRP with bootloader it just goes back to fastboot.
Also note that the flash is successful. But I somehow can't acess TWRP, just goes back to fastboot
And when I flash the experimental TWRP on the dev thread it boots to recovery but asks for a password.. Impossible to flash anything.. Even after I formated data and everything
I tried flashing other TWRP I found but nothing boots even after trying a lot of time.
I tried <fastboot boot recovery.img> as well
I tried <fastboot erase recovery> and then flash the TWRP as well
I've been trying hard for the last 8 hours.
I also have a backup of when I had MIUI 12. But impossible to flash it with the only recovery I can boot to.
I feel so desperate. I'm out of ideas.
If you have any ideas, I'm listening
Thanks for the help guys.
Click to expand...
Click to collapse
an what is the latest miui12 u try to flash

Question Device stuck in BootLoop - PLEASE help

My realme gt neo2 is stuck on bootloop, already tried OFP Flash but nothing, still stuck.

update --
I have managed to get back to realme ui recovery, but not even if I format data, still on fastboot

is it on bootloop or just constantly restarting to fastboot? try flashing the stock rom with the twrp flashable stock rom firmware.

rafaelpcosta said:
is it on bootloop or just constantly restarting to fastboot? try flashing the stock rom with the twrp flashable stock rom firmware.
Click to expand...
Click to collapse
If I start the device, it goes on fastboot, if I click recovery it goes on rui recovery mode, but even if I format data and restart it does the same (start on fastboot)

Lucxq said:
If I start the device, it goes on fastboot, if I click recovery it goes on rui recovery mode, but even if I format data and restart it does the same (start on fastboot)
Click to expand...
Click to collapse
Flash twrp via fastboot and flashable stock rom from twrp.

Alexj7 said:
Flash twrp via fastboot and flashable stock rom from twrp.
Click to expand...
Click to collapse
already did, still nothing..

hi, i have mine since two days.
1. unlock bootloader
2. boot in twrp with "fastboot boot recovery.img"
3. install twrp by press "install -> image install"
4. install magisk in trwp et boot the stock rom
5. restart in twrp and install elixir..A13...
6. reboot the phone with result of touch screen not responding
7. 8. 9. ....... try format Data, change twrp version, flash other rom with no succes.
Now i'm on elixir[A13] and will give a try at arrowsOS.
my solution if it can help you:
1. go here: https://forum.xda-developers.com/t/...-realme-gt-neo-2-bitra-fastboot-mode.4399223/
and try to remember whaat was the last android version you had on your phone.
2. download it and flash it with the little application, if it failed or stuck on "flashing ..." WAIT first 10min, disconnect your phone and reflash it with same method (i flash it three time and no one go to the end).
3. reboot your phone and if you're lucky, you can enter in.
4. make all updates for your android version
5. when you will be on rui3.0, you can remade the first step for playing with bootloader, recovery and recent custom rom.
hope it help you...
soory for my english

sanzostef said:
hi, i have mine since two days.
1. unlock bootloader
2. boot in twrp with "fastboot boot recovery.img"
3. install twrp by press "install -> image install"
4. install magisk in trwp et boot the stock rom
5. restart in twrp and install elixir..A13...
6. reboot the phone with result of touch screen not responding
7. 8. 9. ....... try format Data, change twrp version, flash other rom with no succes.
Now i'm on elixir[A13] and will give a try at arrowsOS.
my solution if it can help you:
1. go here: https://forum.xda-developers.com/t/...-realme-gt-neo-2-bitra-fastboot-mode.4399223/
and try to remember whaat was the last android version you had on your phone.
2. download it and flash it with the little application, if it failed or stuck on "flashing ..." WAIT first 10min, disconnect your phone and reflash it with same method (i flash it three time and no one go to the end).
3. reboot your phone and if you're lucky, you can enter in.
4. make all updates for your android version
5. when you will be on rui3.0, you can remade the first step for playing with bootloader, recovery and recent custom rom.
hope it help you...
soory for my english
Click to expand...
Click to collapse
Hi!
I fixed the problem by using a OFP flash tool
The only thing that I have to do now is to upgrade the version of android (from 11 to 13)
Thanks for the reply tho!

Lucxq said:
Hi!
I fixed the problem by using a OFP flash tool
The only thing that I have to do now is to upgrade the version of android (from 11 to 13)
Thanks for the reply tho!
Click to expand...
Click to collapse
you're welcome, yesterday i cry about my two days phone so if that can help. and yes OFP is the link i post in my answer.

sanzostef said:
hi, i have mine since two days.
1. unlock bootloader
2. boot in twrp with "fastboot boot recovery.img"
3. install twrp by press "install -> image install"
4. install magisk in trwp et boot the stock rom
5. restart in twrp and install elixir..A13...
6. reboot the phone with result of touch screen not responding
7. 8. 9. ....... try format Data, change twrp version, flash other rom with no succes.
Now i'm on elixir[A13] and will give a try at arrowsOS.
my solution if it can help you:
1. go here: https://forum.xda-developers.com/t/...-realme-gt-neo-2-bitra-fastboot-mode.4399223/
and try to remember whaat was the last android version you had on your phone.
2. download it and flash it with the little application, if it failed or stuck on "flashing ..." WAIT first 10min, disconnect your phone and reflash it with same method (i flash it three time and no one go to the end).
3. reboot your phone and if you're lucky, you can enter in.
4. make all updates for your android version
5. when you will be on rui3.0, you can remade the first step for playing with bootloader, recovery and recent custom rom.
hope it help you...
soory for my english
Click to expand...
Click to collapse
there is one stock rom firmware that gives that problem, at least that's what happened to me previously or also when touch did not work it was when flashed custom rom on wrong firmware version, let's say rom required rui 3 c05 but I used rui 3 c07 which caused problems.

rafaelpcosta said:
there is one stock rom firmware that gives that problem, at least that's what happened to me previously or also when touch did not work it was when flashed custom rom on wrong firmware version, let's say rom required rui 3 c05 but I used rui 3 c07 which caused problems.
Click to expand...
Click to collapse
exactly. not really the first time for me. it can append when your recovery is out of date also.
i'm not a dev but interresting with for long year and i think flashing rom don't errase all that why we always need to flash custom rom according to our android version.