Related
I've got this wierd issue.. I decided to give a try CM12, so I updated TWRP to 2.8.5.0 and flashed cm-12-20150301-NIGHTLY-falcon.zip, all great, worked like a charm :good: but video playback was bugged so I returned to my KitKat nandroid.. yesterday I tried to flash cm-12-20150304-NIGHTLY-falcon.zip to see if there were any changes to video playback, I did the flashing process using a 8GB pendrive (OTG) but the problem was that it got stuck on a bootloop (phone never entered Android nor restarted, just the bootanimation logo animation) so I said it might be the ROM, tried cm-12-20150301-NIGHTLY-falcon.zip (the one that worked for me on the first try) and flashed it via OTG, but again the same problem.. okay so OTG must be the problem, reinstalled cm-12-20150301-NIGHTLY-falcon.zip via internal storage AND THE SAME PROBLEM! I tried a lot of Lollipop ROM's but all have the same problem.. so did OTG mess up something? Is there any 'repair' script for this?
Before every attempt I do a nandroid of my current ROM and format System, Cache, Dalvik and Data, flash ROM and then gapps, reboot and stuck on bootlogo.
Any help would be appreciated :fingers-crossed:
Feche said:
I've got this wierd issue.. I decided to give a try CM12, so I updated TWRP to 2.8.5.0 and flashed cm-12-20150301-NIGHTLY-falcon.zip, all great, worked like a charm :good: but video playback was bugged so I returned to my KitKat nandroid.. yesterday I tried to flash cm-12-20150304-NIGHTLY-falcon.zip to see if there were any changes to video playback, I did the flashing process using a 8GB pendrive (OTG) but the problem was that it got stuck on a bootloop (phone never entered Android nor restarted, just the bootanimation logo animation) so I said it might be the ROM, tried cm-12-20150301-NIGHTLY-falcon.zip (the one that worked for me on the first try) and flashed it via OTG, but again the same problem.. okay so OTG must be the problem, reinstalled cm-12-20150301-NIGHTLY-falcon.zip via internal storage AND THE SAME PROBLEM! I tried a lot of Lollipop ROM's but all have the same problem.. so did OTG mess up something? Is there any 'repair' script for this?
Before every attempt I do a nandroid of my current ROM and format System, Cache, Dalvik and Data, flash ROM and then gapps, reboot and stuck on bootlogo.
Any help would be appreciated :fingers-crossed:
Click to expand...
Click to collapse
You should go to fast boot and
mfastboot erase userdata
Plz make a backup in advance and then you can flash anything via. A custom recovery
Lucas Eugene said:
You should go to fast boot and
mfastboot erase userdata
Plz make a backup in advance and then you can flash anything via. A custom recovery
Click to expand...
Click to collapse
I lost my photos but not big deal, now it's working, thanks! :good:
Tried using Twrp 2.7.1 and 2.8.1 as mentioned in the first post still getting the error failed ,also i am able to flash other roms perfectly fine currently trying to flash latest nightly help me out with this guys..
it shows unable to mount '/system'
now tried another nightly aslo ,also i was am using paranoid android which uses ext4 does this roms works on ext4 or it requires f2fs file system
update tried with phliz recovery too same error
Sent from my Moto G using XDA Premium 4 mobile app
Every time I try to flash a MM ROM, I never get past the boot logo. It just continues on for 30 minutes before I finally turn it off with the 10 second power button hold. Then I don't have an OS and TWRP shows no files so I can't restore - it looks like the internal SD card was wiped. I figured out to make a nandroid over OTG so I could restore, but I have the same result trying to flash any MM ROM. I have tried to first flash plain CM, as well as the firmware/modem files beforehand, but that has not worked. I updated to TWRP 2.8.6.0 with no difference. Any ideas?
phoneturf said:
Every time I try to flash a MM ROM, I never get past the boot logo. It just continues on for 30 minutes before I finally turn it off with the 10 second power button hold. Then I don't have an OS and TWRP shows no files so I can't restore - it looks like the internal SD card was wiped. I figured out to make a nandroid over OTG so I could restore, but I have the same result trying to flash any MM ROM. I have tried to first flash plain CM, as well as the firmware/modem files beforehand, but that has not worked. I updated to TWRP 2.8.6.0 with no difference. Any ideas?
Click to expand...
Click to collapse
Hum. To me it sounds/feels like when I've tried to update, but forgot to flash the new modem... but you have tried that. I'd go back to TWRP 2.8.6, flash your old rom/modem, and see if you can get back there... and are able to boot into system
then if that works, full wipe, flash MM, the modem, google package and reboot.
I tried again a few days ago and was successful flashing to marshmallow using a plain CM13 rom. It was okay, but not an improvement over the LP rom I was using, and with less features, so I tried to nandroid back to LP. I kept getting an error with TWRP Restore. It looked like I was stuck on MM. I messed around in TWRP and changed system and data to EXT4 (figuring they were now F2FS and that was the problem). This worked. Once I formatted to EXT4, I was able to restore over OTG. Formatting to EXT4 wiped my internal memory so it was lucky I had a backup on OTG.
I have a Boost 1031 and I unlocked bootloader and rooted with no issues. Phone was 4.4.1 and auto-updated to 4.4.4. I installed TWRP and tried flashing CM13 which indicated 1031 was compatible. Couldn't install due to outdated bootloader version so followed post saying edit text out of rom to bypass and it will update automatically. I did, and it worked, but I just got the CM13 logo bootloop. Thought maybe I could go back to stock and take it slower with a stock 5.1 or GPE but can't "downgrade" now since CM13 did successfully flash.
via command in fastboot I am on bootloader version 411A.
I have tried:
adb sideloading factory image for Boost Falcon - failed due to partition error.
adb sideloading 5.1 optimized rom, CM12 and CM13 - failed due to not able to mount anything.
extracted and via fastboot:
4.4 stock factory image - successfully installed w/initial errors relating to downgrade as warned, stuck on 'unlocked bootloader' screen
5.1 optimized rom - successfully installed, stuck on loop of sad broken android on his side.
CWM recovery
3 versions of TWRP
Is there anything else I can try? I can still get into fastboot and the custom recovery.
Thanks!
static.chaos73 said:
I have a Boost 1031 and I unlocked bootloader and rooted with no issues. Phone was 4.4.1 and auto-updated to 4.4.4. I installed TWRP and tried flashing CM13 which indicated 1031 was compatible. Couldn't install due to outdated bootloader version so followed post saying edit text out of rom to bypass and it will update automatically. I did, and it worked, but I just got the CM13 logo bootloop. Thought maybe I could go back to stock and take it slower with a stock 5.1 or GPE but can't "downgrade" now since CM13 did successfully flash.
via command in fastboot I am on bootloader version 411A.
I have tried:
adb sideloading factory image for Boost Falcon - failed due to partition error.
adb sideloading 5.1 optimized rom, CM12 and CM13 - failed due to not able to mount anything.
extracted and via fastboot:
4.4 stock factory image - successfully installed w/initial errors relating to downgrade as warned, stuck on 'unlocked bootloader' screen
5.1 optimized rom - successfully installed, stuck on loop of sad broken android on his side.
CWM recovery
3 versions of TWRP
Is there anything else I can try? I can still get into fastboot and the custom recovery.
Thanks!
Click to expand...
Click to collapse
Try to flash the 5.1 Factory Firmware Image:
http://forum.xda-developers.com/showthread.php?t=2542219
http://forum.xda-developers.com/moto...mware-t3110795
From that point you can move on to custom ROMs if you wish
satanas17 said:
Try to flash the 5.1 Factory Firmware Image:
http://forum.xda-developers.com/showthread.php?t=2542219
http://forum.xda-developers.com/moto...mware-t3110795
From that point you can move on to custom ROMs if you wish
Click to expand...
Click to collapse
Yes I have tried that. The problem is that I can't flash anything because there is no recognized system. No matter what rom it is, it can't mount sd card, data, /dev/block/platform etc. After more research I think I may need to reformat the partitions but in adb I get an error of no superuser. I'm trying to see if I can do it in fastboot instead.
static.chaos73 said:
Yes I have tried that. The problem is that I can't flash anything because there is no recognized system. No matter what rom it is, it can't mount sd card, data, /dev/block/platform etc. After more research I think I may need to reformat the partitions but in adb I get an error of no superuser. I'm trying to see if I can do it in fastboot instead.
Click to expand...
Click to collapse
OK, finally got it working! I used fastboot to partition with the gpe image of the rom I was trying to flash, then fastboot to format. Then I went into recovery and tried to mount data/system/cache. Data was still not available, so I used recovery to format data and got it mounted. I tried a few different roms and finally was able to get cyanpop marshmallow to load up and run. I'm going to try and figure out what the difference is because I want CM13 nightly eventually. I tried to downgrade back to 4.4 stock but never could get past the downgrade errors when flashing in recovery, and flashing via fastboot or adb sideload would just fail.
Anyway, thanks for your help!
You seem to be making things more complicated than necessary. You should be aware Firmware Images can only be flashed via Fastboot. Flashing the GPE firmware image formatted userdata (/data) to EXT4. Stock ROMs will not boot if you have an EXT4 /data partition. See the FAQ in my Stock ROM collection thread.
lost101 said:
You seem to be making things more complicated than necessary. You should be aware Firmware Images can only be flashed via Fastboot. Flashing the GPE firmware image formatted userdata (/data) to EXT4. Stock ROMs will not boot if you have an EXT4 /data partition. See the FAQ in my Stock ROM collection thread.
Click to expand...
Click to collapse
OK that makes sense. I will read through your FAQ before attempting to flash anything else. Thank you for the information!
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.
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