Related
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
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.
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
Code:
fastboot -w && fastboot erase system && fastboot flash recovery recovery.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
ceesiama said:
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
Click to expand...
Click to collapse
zip isn't installed successfully? can you also send screenshot, so I can help you.
4j17h said:
zip isn't installed successfully? can you also send screenshot, so I can help you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Yes, since device is decrypted lock screen doesn't work. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
4j17h said:
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
Click to expand...
Click to collapse
I'm sorry I mistyped in the above comment, when i followed your method, zip installed successfully but it bootlooped into stock recovery everytime. I hope that clarifies a bit. I''ll be very grateful if you can help me..
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
Try install magisk manager, maybe ur device still rooted
haditriw said:
Try install magisk manager, maybe ur device still rooted
Click to expand...
Click to collapse
no that's not how magisk works in Realme 3 Pro, if device is restarted there will be no magisk. You need to goto fastboot then goto recovery, it boots to system. We have magisk. Yes this method tricky. I am going to publish new guide, it will be simple & straight forward.
Bricked/ Bootlooping
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootloop :'(
malakaz27 said:
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
pls help me, im stuck on bootloop :'(
Click to expand...
Click to collapse
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
this method worked perfectly fine for me. i tried both lineage os roms available and both of them caused bootloop or end up destroying boot. so thanks to developer for making this zip file.
4j17h said:
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
Click to expand...
Click to collapse
hi i am stuck in bootloop after flashing all stuff in fastboot guide
leo77g said:
hi i am stuck in bootloop after flashing all stuff in fastboot guide
Click to expand...
Click to collapse
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
4j17h said:
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
Click to expand...
Click to collapse
formatting worked and thanx for help )
Moderators' Announcement: I've removed the links to Telegram and references to it. This is not a development thread, and support is to be provided through XDA. Many posts proved this has not been the case!
You may be asking, "Why was my Telegram or Whatsapp thread closed?"
Well, it's just becoming too much.
Going forward, we will only allow one Telegram chat link on a development thread by the ROM's developer and only if thorough support is still provided in the ROM thread on XDA.
All discussion channels, photography channels, whatnot channels will be strongly discouraged and removed with immediate effect. Please reference the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Also, we now have an official XDA Discord Server. We would encourage you to try it out.
Announcing the Official XDA-Developers Discord Server
FYI
Thanks,
The Moderation Team
Click to expand...
Click to collapse
Need Help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
ResSetOk said:
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
Click to expand...
Click to collapse
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
4j17h said:
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
Click to expand...
Click to collapse
I did Wipe before and after firmware, on P2Q is stitched without problems, but under firmware in Q2P in recovery writes, that not managed wipe userdata. The data was not encrypted, the password is not asked.
do you have video for Fastboot Method ?
[No message]
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?
So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).
remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?
harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly
GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.
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