Hello everyone
I need help regarding a problem I am facing on my Poco F1.
I have installed custom roms on it and have went back to stock as well many times, but a couple of days back when I was trying to go back to stock after having installed a custom rom, I failed as every time the phone boots up, it gets stuck to the fastboot mode. I have reflashed the stock rom using miflash tool many times but to no avail. Initially the TWRP recovery got flashed but when I sent a command to boot to custom recovery it sent me back an error saying 'failed to load/authenticate boot image', but now I can't even get the device listed under 'ADB Devices' even though the system recognises it when using the MiFlash tools.
Eagerly waiting for any suggestions
Thanks
Check volume button for any damages
If no damage
Flash stock and boot to fastboot and flash official twrp
96thippesh said:
Check volume button for any damages
If no damage
Flash stock and boot to fastboot and flash official twrp
Click to expand...
Click to collapse
I am sure there is no damage to the volume down button.
I have tried flashing stock rom but to no avail, I can flash TWRP but when I send the command to boot to TWRP, it just shows a blank screen.
Thanks for your reply man.
AmitojSWasu said:
I am sure there is no damage to the volume down button.
I have tried flashing stock rom but to no avail, I can flash TWRP but when I send the command to boot to TWRP, it just shows a blank screen.
Thanks for your reply man.
Click to expand...
Click to collapse
try flashing a gsi using fastboot mode and see if it boots.
i am facing same problem during installation custom rom based on oreo 8.1.0 in 2020 can you help me my poco f1 showing fastbbot after restart
AmitojSWasu said:
Hello everyone
I need help regarding a problem I am facing on my Poco F1.
I have installed custom roms on it and have went back to stock as well many times, but a couple of days back when I was trying to go back to stock after having installed a custom rom, I failed as every time the phone boots up, it gets stuck to the fastboot mode. I have reflashed the stock rom using miflash tool many times but to no avail. Initially the TWRP recovery got flashed but when I sent a command to boot to custom recovery it sent me back an error saying 'failed to load/authenticate boot image', but now I can't even get the device listed under 'ADB Devices' even though the system recognises it when using the MiFlash tools.
Eagerly waiting for any suggestions
Thanks
Click to expand...
Click to collapse
Well from my experience flashing a fastboot ROM from mifkash is the final remedy for Xiaomi phones on a user level. If that doesn't work for some reasons you'll need to find someone who has an EDL authorised account and restore the phone.
Related
Hello everybody!
The last day my phone got stuck on bootloader screen. It just wouldn't boot the OS.
So I tried to fix that by flashing other rom. I have unlocked it trough MiUnlock.
Flashed in fastboot TWRP(rosy) recovery. It could boot TWRP but after a reboot, would launch MiRecovery.
After that the Android didnt start no more. After a new flash of TWRP I was able to enter recovery. I tried to flash a custom rom. After that the VOLUME UP + POWER wouldnt launch recovery no more (Also VOLUME DOWN+UP+POWER buttons, wont boot the Recovery)
Now i found an EDL mode to flash rom through XiaoMiFlash. Did it, Made the steps from tutorials. That, has changed the device to COM10 in MiFlash which let me try different official roms, and i always get the same error message: cannot receive hello packet, MiFlash is trying to reset status!
Also tried too flash a recovery img.
Tried everything i found on that, nothing worked to get those packets...
My only hope was to fastboot flash recovery TWRP or MiRecovery. And then flash new rom to fix my phone.
Tried many version of Twrp, but no success to actually flash.
I have tried removing recovery via adb and flashing another. Logs shows success but no effect on phone.
Still can't acces recovery mode on my phone.
Bootloop stuck. Shows MI logo and that its Unlocked.
Doesnt work flashing via fastboot - TWRP or MiRecovery images.
My phone is bricked for a week now. Please share a solution if you got one.
SOLVED
Good news. finally flashed chinese version through miflash tool.
had to rename some files from rom.
Flashed through BOOTLOADER.
Hi,
XT1527 surnia_retca_cus 2016-11-18
this phone doesn't seem to allow flashing a custom recovery (fastboot flash went ok but still boots into stock no matter what). Fastboot boot with twrp image didn't work either (stuck on splash screen)
I now tried flashing a stock rom but couldn't find exact same model. Phone is now bricked (flashing gpt.img fails).
Any suggestions? Thanks
Foldback said:
Hi,
XT1527 surnia_retca_cus 2016-11-18
this phone doesn't seem to allow flashing a custom recovery (fastboot flash went ok but still boots into stock no matter what). Fastboot boot with twrp image didn't work either (stuck on splash screen)
I now tried flashing a stock rom but couldn't find exact same model. Phone is now bricked (flashing gpt.img fails).
Any suggestions? Thanks
Click to expand...
Click to collapse
Flash the twrp and the boot into it and allow modification to keep twrp then flash any custom rom
riyan65 said:
Flash the twrp and the boot into it and allow modification to keep twrp then flash any custom rom
Click to expand...
Click to collapse
Ok, I managed to flash both the twrp.img and the boot.img from a "surnia_retca...similar but not same...cid14" onto it but it still fails to start twrp, saying as before "Error: failed to load kernel! Boot up failed".
Foldback said:
Ok, I managed to flash both the twrp.img and the boot.img from a "surnia_retca...similar but not same...cid14" onto it but it still fails to start twrp, saying as before "Error: failed to load kernel! Boot up failed".
Click to expand...
Click to collapse
Are you on stock rom or custom???
If on stock you need to flash the firmware again, if on custom just flash the custom ROM again, it will fix your problem.
riyan65 said:
Are you on stock rom or custom???
If on stock you need to flash the firmware again, if on custom just flash the custom ROM again, it will fix your problem.
Click to expand...
Click to collapse
I originally only had the stock rom, which would not go into twrp as recovery after flashing (going into stock recovery instead).
I did not back up this stock rom and tried a similar, but slightly older one (XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip) which failed the gpt stage of flashing and after that the stock was gone.
It now only has the bootloader working, with the above problems.
Foldback said:
I originally only had the stock rom, which would not go into twrp as recovery after flashing (going into stock recovery instead).
I did not back up this stock rom and tried a similar, but slightly older one (XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip) which failed the gpt stage of flashing and after that the stock was gone.
It now only has the bootloader working, with the above problems.
Click to expand...
Click to collapse
You were lucky as your device didn't get hard Bricked, if you flash a older firmware then the device has, then it going to hard brick and you won't get bootloader too. So it just a paperweight.
If you want to flash stock rom then flash the ROM by removing the gpt and bootloader command, if any error occurs keep going and then reboot the device. Your device will work.
That worked, thanks very much! Using the XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip, it gave an error for the mfastboot erase customize line, but then booted into Android and stock recovery was back as well.
I am now back to the problem of getting the device to run the twrp recovery. It flashes OK but gives "Error: failed to load kernel! Boot up failed" when rebooting and going into Recovery from bootloader. Stock recovery is gone after this new attempt. What's going wrong? I am using twrp-3.3.1-0-condor.img
Foldback said:
That worked, thanks very much! Using the XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip, it gave an error for the mfastboot erase customize line, but then booted into Android and stock recovery was back as well.
I am now back to the problem of getting the device to run the twrp recovery. It flashes OK but gives "Error: failed to load kernel! Boot up failed" when rebooting and going into Recovery from bootloader. Stock recovery is gone after this new attempt. What's going wrong? I am using twrp-3.3.1-0-condor.img
Click to expand...
Click to collapse
Your using different twrp for different devices which cause the issue of kernal. Flash this twrp and it going to work.
https://twrp.me/motorola/motorolamotoelte.html
riyan65 said:
Your using different twrp for different devices which cause the issue of kernal. Flash this twrp and it going to work.
https://twrp.me/motorola/motorolamotoelte.html
Click to expand...
Click to collapse
You're a star! Surnia twrp is working. When I started I didn't know about the different Moto E's (I was looking at the /e/ fork of LineageOS for Moto E, and they officially only list condor). Hence I only tried condor...
Luckily there is an unofficial /e/ build for surnia. This installed successfully by adb sideload. Mission accomplished, thanks again for your help!
PS.
Check out https://doc.e.foundation/what-s-e
it's a very good idea.
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.
bootloader - unlocked
ROM - PE
i flashed derpfest ROM, but when I rebooted it, it went to fastboot. i was not able to boot into TWRP too. it just kept going to fastboot again and again. so I flashed stock ROM using mi flash tool (stock fastboot ROM). now I am able to access the mi recovery menu but there is no install from zip option, not able to boot into the system as it goes to fastboot while booting into the system. in short, now I have access to fastboot and limited access to the mi recovery menu.
i tried to flash custom recovery (TWRP and orange fox). it gets flashed but cannot boot into those recoveries and goes to fastboot again.
i tried to boot the custom recovery directly too with "fastboot boot twrp.img" it restarts but the recovery doesn't load.
does anyone know what to do now?
please tell me how to flash stock from or custom from anything will help.
------------------UPDATE---------------------------------
i am able to flash android 8.1 and run it but anything later then that reeboots to fastboot. cannot update from stock updater too. if i flash any firmware of PIE or later then it reeboots to fastboot.
rabin18181818 said:
bootloader - unlocked
ROM - PE
i flashed derpfest ROM, but when I rebooted it, it went to fastboot. i was not able to boot into TWRP too. it just kept going to fastboot again and again. so I flashed stock ROM using mi flash tool (stock fastboot ROM). now I am able to access the mi recovery menu but there is no install from zip option, not able to boot into the system as it goes to fastboot while booting into the system. in short, now I have access to fastboot and limited access to the mi recovery menu.
i tried to flash custom recovery (TWRP and orange fox). it gets flashed but cannot boot into those recoveries and goes to fastboot again.
i tried to boot the custom recovery directly too with "fastboot boot twrp.img" it restarts but the recovery doesn't load.
does anyone know what to do now?
please tell me how to flash stock from or custom from anything will help.
Click to expand...
Click to collapse
Hello,
Please take a look on my POCO F1 Ultimate Collection & Guides.
You will find everything you need.
Retrial said:
Hello,
Please take a look on my POCO F1 Ultimate Collection & Guides.
You will find everything you need.
Click to expand...
Click to collapse
nope nothing
rabin18181818 said:
nope nothing
Click to expand...
Click to collapse
Okey, check the guide clean install official stock rom(to unbrick ur device) and then follow the guide clean install custom rom.
Sir, i have updated my mi note 10 lite to android 11and after restart it works fine. But the problem is that when i reboot to recovery to install root, because i have installed twrp before. Unfortunately, its stuck on fastboot screen.
Can you help me out to solve this problem.
I tried to flash twrp but its not mounting partition, i reboot to recovery again but its go to fastboot mode again
I tried to flash fastboot rom through mi flash tool it errors because anti rollback.(android 10)
Still i am finding Android 11 fastboot images but not found.
You can contact dennis via Instagram that man reply you
Mi note 10 lite User ðŸ˜ðŸ˜ said:
You can contact dennis via Instagram that man reply you
Click to expand...
Click to collapse
Okay i dm you now check please
haadii said:
Sir, i have updated my mi note 10 lite to android 11and after restart it works fine. But the problem is that when i reboot to recovery to install root, because i have installed twrp before. Unfortunately, its stuck on fastboot screen.
Can you help me out to solve this problem.
I tried to flash twrp but its not mounting partition, i reboot to recovery again but its go to fastboot mode again
I tried to flash fastboot rom through mi flash tool it errors because anti rollback.(android 10)
Still i am finding Android 11 fastboot images but not found.
Click to expand...
Click to collapse
extract the official recovery from the global fastboot rom and flash through cmd to recover the boot, then wipe from the recovery and you will return to miui 12.1.1
what i'm trying to figure out is if i can go back to the previous version of android without risking to crash the device.
I ran the fastboot getvar anti command and the result was Anti: 2 but I am not quite clear what that means.
I am a new user at Xiaomi.
leinadagisiaol said:
what i'm trying to figure out is if i can go back to the previous version of android without risking to crash the device.
I ran the fastboot getvar anti command and the result was Anti: 2 but I am not quite clear what that means.
I am a new user at Xiaomi.
Click to expand...
Click to collapse
I tried it. When flashing fastboot images thorough miflash its error in anti roll back check... Or may your device hard brick
Now i am here with a new fu*kin error..
Any solution for this. I don't want to lose data
If stuck in fastboot mode, type "fastboot continue" in adb and it will proceed with boot
ApexPrime said:
If stuck in fastboot mode, type "fastboot continue" in adb and it will proceed with boot
Click to expand...
Click to collapse
No. Its not my problem now
My problem is mentioned above
Bro i think you can access your files from computer in recovery so make a backup and flash official firmware using miflash tool. I don't think there's any other way.
haadii said:
Now i am here with a new fu*kin error..
Any solution for this. I don't want to lose data
Click to expand...
Click to collapse
Before installing custom recovery and installing custom rom, it is recommended to backup.
You installed the recovery well, but in order to install custom ROMs you have to format and restart the recovery, then pass the ROM you want to flash and reboot system.
haadii said:
I tried it. When flashing fastboot images thorough miflash its error in anti roll back check... Or may your device hard brick
Click to expand...
Click to collapse
I managed to go back to miui 11 version 11.0.8
leinadagisiaol said:
I managed to go back to miui 11 version 11.0.8
Click to expand...
Click to collapse
How?? Can you show or tell me the process!! I don't like Android 11
haadii said:
How?? Can you show or tell me the process!! I don't like Android 11
Click to expand...
Click to collapse
Good evening ..
For all those interested in downloading the official ROM version of the Xiaomi mi note 10 Lite, I have news for you, at least for those who want and have not tried.
I tried the method of saving the MiFlash folder on Disk C, in the same way I did with the global ROM of miui 11.0.8 fastboot, to the latter I changed the name of the folder to a shorter one (example Miui11.0.8), then boot in fastboot mode and run my flash running the ROM (Miui11.0.8) and the result obtained is that, I'm back on Android 10 with miui 11.0.8.
I share this information to give security to all those who had doubts about this and did not dare to try.
This data I extracted from various forums and pointed to it to give credit to all those who previously published it.
Remember that the bootloader must be unlocked.
Regards.
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
salsaecoentros said:
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
Click to expand...
Click to collapse
Just format userdata. In fastboot mode command. Fastboot format userdata
Then flash new stock fastboot images of eu in miflash.
Note,
Backup your data first
Good Day. I have concern but after updating to Android 12. Currently my Mi Note 10 Lite is experiencing stuck in fastboot and mi logo. I already tried flashing using MIFlash 2020 but the error occur is "Erase is not allowed in Lock State".I also used MI PC Suite but it cant read my device (maybe because of lock state also). Even in MI-Unlock (batch_unlock application) it says its locked but when I sign-in it doesnt give permission to unlock (I used yahoo account).
goroshigeno56 said:
Good Day. I have concern but after updating to Android 12. Currently my Mi Note 10 Lite is experiencing stuck in fastboot and mi logo. I already tried flashing using MIFlash 2020 but the error occur is "Erase is not allowed in Lock State".I also used MI PC Suite but it cant read my device (maybe because of lock state also). Even in MI-Unlock (batch_unlock application) it says its locked but when I sign-in it doesnt give permission to unlock (I used yahoo account).
Click to expand...
Click to collapse
did you fix that problem?