My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?
renatogui said:
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I had frozen twrp screen before but usually managed to fix just by restarting the phone and using twrp offain in adb.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?
Click to expand...
Click to collapse
1- Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2- Create a new folder on your C drive and name it: adb
3- Extract & place everything from the platform-tools into your adb folder
4- Download this: https://drive.google.com/open?id=1SKIlWS-y6kNI4YIE2Sj4_9CcRJ9W0xTh
5- Extract & place it to your adb folder
6- Reboot your phone to TWRP and wipe it, then reboot to bootloader
7- Connect your phone to your PC
8- Go into the daisy_global_images_V10.0.9.0.PDLMIXM_9.0 folder and run: flash_all.bat
A window will pop up and install the stock mi a2 lite rom. Let it finish then your phone boot up. You will have to update your phone since this stock rom that I linked is a pretty old one.
Someone had a similar question in another forum, so I just copy my answer from there. If you have adb already installed you can ignore the first 3 steps.
I had frozen twrp screen a couple of times but managed to fix it by restarting the phone and re-open the powershell window in adb. I use twrp-daisy-3.2.3-0-offain.img
I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.
I was thinking I did not try to install stock image using MiFlash tool. I can do it if I get a windows computer available.
I saw people suggesting fastboot oem edl but I could not find a clear explanation of the procedure.
I understood that I must use MiFlash in that case too but the steps are not clearly defined and I need a windows computer anyway.
Does someone have a step by step to use fastboot oem edl?
renatogui said:
I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.
Click to expand...
Click to collapse
No particular reason behind 10.0.9.0 ... I just had that uploaded to my drive and when I posted this to another forum I didn't wanted to "waste" time to search for a link so I just used mine. Anyways u have to wipe your phone before installing stock rom.
The way I fixed mine is not working for you so Im afraid Im out of ideas.
Hope someone can help you out with it
thanks, anyway for your kind and quick answer.
I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue. When it comes to EDL flashing:
1 - Grab the 20160401 version of MiFlash from here : https://www.xiaomiflash.com/download/ (You need this version because it's the only MiFlash version that's capable of EDL flashing, mind you, you need a Windows PC and 64-bit hardware for this)
2 - Connect the phone in fastboot mode and type this command :
Code:
fastboot oem edl
Hit enter, this will take the phone into EDL mode, which means the screen will go black and the notification LED will start blinking.
3 - Now you're in EDL mode, open the MiFlash version I mentioned and Browse to find the location the stock ROM is stored, then hit refresh so that the software can recognize the phone.
4 - Hit flash to start flashing, but remember EDL flashing is a very fragile process, so make sure you don't lose power/shutdown the app while it's doing its job. After a successful flash, the app will say it is successful. Unplug the phone and start holding the power button to reboot. If you want to lock the bootloader, make sure to hold vol down as well and go into fastboot then re-lock the bootloader with :
Code:
fastboot oem lock
5 - Voila!
Thank you marstonpear for the detailed answer.
I will try MiFlash this evening and will post the result here.
I am very glad to count with more experienced people in fixing my errors.
Hello marstonpear,
I downloaded daisy image v10.0.13.0 that was suggested in XiomiFlash how to and try to flash it.
I got the error "mismatch image and device". This is very strange. Never had this before flashing with fastboot.
Do you think I could scrambled mi A2 lite so MiFlash cannot recognize it as a mi A2 lite anymore?
The only different think I did was interrupting my first flasing try using ^C when it was frozen.
I made 2 other tries after this with no errors. The only problem was the never ending boot.
My next try will be using image v10.0.18.0, the one I had installed before all this problems begin.
renatogui said:
Hello marstonpear,
Click to expand...
Click to collapse
marstonpear said:
I'd suggest giving MiFlash a try.
Click to expand...
Click to collapse
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.
coolwei1 said:
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.
Click to expand...
Click to collapse
I'm sorry. I tried hard how to quote and did'nt find.:cyclops:
I am almost learning...
marstonpear said:
I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue.
Click to expand...
Click to collapse
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?
renatogui said:
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?
Click to expand...
Click to collapse
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?
renatogui said:
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?
Click to expand...
Click to collapse
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.
marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Now I know the reason of mismatching. All the scripts bundled with Xiaomi_Mi_A2_Lite_V10.0.13.0.PDIMIXM_20190807.0000.00_Global_9.0_XFT are made for jasmine. I will find another image more trustworthy than this one.
marstonpear said:
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.
Click to expand...
Click to collapse
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:
renatogui said:
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:
Click to expand...
Click to collapse
for others having the same probem I've learn in another thread that this error is issued because I did not choose the lock option below right of MiFlash tool. That is why it didn't catch the lock checkpoint. But the end of the message is not true because at this checkpoint, the flashing is already done. I simply turn the phone off and on again and the boot was normal.
Thanks for all that help me specially marstonpear.
Thread closed... until next problem.
Related
Really need help!
I successfully unlocked my Mi Max 3 using the official process. 14 day wait. No issues...booted back into MIUI 10' restored backup from MiCloud and was back to normal, except now it showed "unlocked" on startup screen.
It was running CN MIUI 10 V10.0.6.0 OEDCNFH
I had been reading that it was possible to flash the device with the global version of the ROM
I had several Google related issues with the Chinese ROM so I downloaded the MiFlash tool (2018.5.28.0), got the ROM from here: https://xiaomifirmware.com/roms/latest-official-miui-roms-for-xiaomi-mi-max-3/
and tried to flash it with Global 10.0.1.0 OEDMIFH
Result was the error "flash crclist error"
screenshot here
https://1drv.ms/u/s!ArN9mSbbMVT8gohpA03ob7X2FhjspQ
After this, the device is stuck in Fastboot mode and seems to no longer have a bootable ROM. Booting into recovery mode with vol up + power and restarting that way also just boots back into Fastboot.
I downloaded the Fastboot version of the ROM the phone was originally running 10.0.6.0 OEDCNFH and tried to flash that.
It also failed with the same error.
This user had the same issue with a Mi8:
https://forum.xda-developers.com/mi-8/help/failed-to-install-global-rom-via-mi-t3851636
The thread did not help me. There seems to be almost nothing related to this issue "flash crclist error" on XDA
My phone is not bootable now. No idea what to try next, I am a total novice in this area. I have since been reading about Anti Rollback Protection, I just don't know if this has anything to do with my issue. My device is not dead....it is booting into Fastboot, and I can still see it in MiFlash. If anyone could advise me I would be very grateful.
https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2
See my post there on page 2. It should fix your issue.
The path of the rom seems too long.
Create a new folder at the root of your C drive and give it a name without spaces, move all the contents of the extracted rom to that folder and try to flash again
opasha - thanks for reply
opasha said:
https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2
See my post there on page 2. It should fix your issue.
Click to expand...
Click to collapse
Hi and thank you for responding to my question.
I have tried the steps in your thread as follows:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi-...-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
When I try step 3, what you describe does not seem to be the behaviour I am seeing. If I hold volume up + volume down + power simultaneously for 10 seconds, the device reboots straight back into the Fastboot screen (the one with the bunny). Is this normal? If not, what screen should be displayed on the device? There is no sign of MiFlash tool detecting the device differently at this point (COM XX or XXX)
When I refresh MiFlash it detects the device as pictured:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEJOYos6rGjNSM8vQ
If I flash it, it produces the same "flash crclist error" pictured here:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEIec-cB8pUMAVqLg
FYI the only way I can get the device to start in anything other than the Fastboot screen is to hold down the VOLUME UP key + power. This boots it into the Mi-Recovery 3.0 screen where I can see the Main Menu with 3 buttons: Reboot - Wipe Data - Connect with MiAssistant
Reboot goes back to Fastboot
Wipe Data also just reboots into Fastboot.
Connect with MiAssistant prompts to connect to Mi PC suite with diagram of device + USB cable + URL (I tried this but PC suite (version 3.2.1.3111_2717) does not recognise my device....this was also the case when the phone was working normally). If I don't try to connect with USB cable at this point it times out after about 30 seconds and boots back into the Fastboot screen.
The remaining steps in your thread did not seem to apply after step 3 failed.
No idea what to do. I posted this on MIUI forums too. Some people are suggesting I use ADB and install TWRP but I would need an idiots guide, I don't have any experience with either and would have no idea what I was doing....and I'm finding it extremely difficult to unearth anything useful from the **vast** number of Android related sites and forums relating to ROMs etc. For example, I can't find anything helpful about "flash crclist error". Maybe I should ask Xiaomi support?
At this point I just need to get *any* working ROM onto the device. I would not have unlocked it and attempted the switch from Chinese to Global if I hadn't read so much advice that this could be done very simply and without issues as long as the bootloader was unlocked. If you have any other advice for me please let me know!
Thanks again.
richard.rea said:
Hi and thank you for responding to my question.
I have tried the steps in your thread as follows:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi-...-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
When I try step 3, what you describe does not seem to be the behaviour I am seeing. If I hold volume up + volume down + power simultaneously for 10 seconds, the device reboots straight back into the Fastboot screen (the one with the bunny). Is this normal? If not, what screen should be displayed on the device? There is no sign of MiFlash tool detecting the device differently at this point (COM XX or XXX)
When I refresh MiFlash it detects the device as pictured:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEJOYos6rGjNSM8vQ
If I flash it, it produces the same "flash crclist error" pictured here:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEIec-cB8pUMAVqLg
FYI the only way I can get the device to start in anything other than the Fastboot screen is to hold down the VOLUME UP key + power. This boots it into the Mi-Recovery 3.0 screen where I can see the Main Menu with 3 buttons: Reboot - Wipe Data - Connect with MiAssistant
Reboot goes back to Fastboot
Wipe Data also just reboots into Fastboot.
Connect with MiAssistant prompts to connect to Mi PC suite with diagram of device + USB cable + URL (I tried this but PC suite (version 3.2.1.3111_2717) does not recognise my device....this was also the case when the phone was working normally). If I don't try to connect with USB cable at this point it times out after about 30 seconds and boots back into the Fastboot screen.
The remaining steps in your thread did not seem to apply after step 3 failed.
No idea what to do. I posted this on MIUI forums too. Some people are suggesting I use ADB and install TWRP but I would need an idiots guide, I don't have any experience with either and would have no idea what I was doing....and I'm finding it extremely difficult to unearth anything useful from the **vast** number of Android related sites and forums relating to ROMs etc. For example, I can't find anything helpful about "flash crclist error". Maybe I should ask Xiaomi support?
At this point I just need to get *any* working ROM onto the device. I would not have unlocked it and attempted the switch from Chinese to Global if I hadn't read so much advice that this could be done very simply and without issues as long as the bootloader was unlocked. If you have any other advice for me please let me know!
Thanks again.
Click to expand...
Click to collapse
Sorry, didn't realize this was new to you. Your fastboot mode is fine. Ignore my step 3 (my apologies for not clarifying since this step is not needed for you since your phone is in fastboot). All you need to do is have your phone flash this version of miui global through Miflash Tool. Let it reboot on its own.
can not flash ROM
opasha said:
Sorry, didn't realize this was new to you. Your fastboot mode is fine. Ignore my step 3 (my apologies for not clarifying since this step is not needed for you since your phone is in fastboot). All you need to do is have your phone flash this version of miui global through Miflash Tool. Let it reboot on its own.
Click to expand...
Click to collapse
I can not flash the ROM Global Stable fastboot 10.0.1.0 (or any other ROM I have tried)
In the MiFlash tool I get the error "flash crclist error" as I have tried to explain in my previous posts.
richard.rea said:
I can not flash the ROM Global Stable fastboot 10.0.1.0 (or any other ROM I have tried)
In the MiFlash tool I get the error "flash crclist error" as I have tried to explain in my previous posts.
Click to expand...
Click to collapse
You're not extracting properly. Use 7zip. Then extract the folder and point Miflash to this extracted folder. - make sure inside this folder there are simply files and no other single folders - single folders within single folders usually means you have to extract again.
Just run the damn flash-all.bat for God sake...
SOLVED thank you!
opasha said:
You're not extracting properly. Use 7zip. Then extract the folder and point Miflash to this extracted folder. - make sure inside this folder there are simply files and no other single folders - single folders within single folders usually means you have to extract again.
Click to expand...
Click to collapse
You were right. I extracted using 7Zip instead of Winzip. Pointed MiFlash at the extracted folder. 10.0.1.0 Global flashed successfully.
**HUGE** thanks to you for your replies and help. Painful learning curve for me. Very happy to get my phone working again, this time with the ROM I wanted.
Thanks again
best regards
so im on the same version but xiaomi.eu... 10.0.6.0 can i go downgrade that global? using same method?
flashed over x.eu 10.0.6.0 with Global 10.0.1.0 using Miflash with fastboot rom, it rebooted into recovery screen saying "this version cannot be installed on this device"...at this point i started crying lol.
Plugged into mi suite to see if i could recover back to original china rom it shipped with, discovered the BL was locked again, unlocked again via mi tool and hey presto, it booted up with fully working Global rom!
I'm now in a good place.
flashed over x.eu 10.0.6.0 with Global 10.0.1.0 using Miflash with fastboot rom, it rebooted into recovery screen saying "this version cannot be installed on this device"...at this point i started crying lol.
Plugged into mi suite to see if i could recover back to original china rom it shipped with, discovered the BL was locked again, unlocked again via mi tool and hey presto, it booted up with fully working Global rom!
I'm now in a good place.
Hello,
I was on stable global indian 10.4.4 (INMX), unlocked, rooted, twrp.
Then got notification of update, downloaded update, reboot (as prompted by updater app), update failed, error 7.
Rebooted phone to system. Updater said to download full rom now which i did,, and reboot again, same error.
I thought twrp might b incompatible with update so i flashed stock recovery n repeated all above.
Now phone stuck at bootloop and does not boot into recovery or fastboot by pressing vol+/- and power,, also pressing all three together is not working.
PC doesn't detect phone as it keeps rebooting in loop.
Any way to force boot in fastboot??
beachfl said:
When it very first shuts down (the redmi logo first disappears and it goes black), before it starts to boot up again, press and hold Volume Down and Power until it takes you to fastboot.
Click to expand...
Click to collapse
Cannt go to fastboot bro by this way
majidmjmn said:
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx
Click to expand...
Click to collapse
same problem bro. let me know how you solve this problem please
yeswe61155 said:
Cannt go to fastboot bro by this way
Click to expand...
Click to collapse
If it is bootlooped... you can get to fastboot... keep trying... you just have to catch it at the right time.
Letting the battery run out, then charge and try to start in quick start
danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
Thank you. Will do that and update.
danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
Update : didn't work. Still went into same. Tried 4-5 times.
I think you have to open the back cover, disconnect the battery connector, connect it to computer, hopefully it will get detected as mediatek then you can follow this guide
danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
gugelgigel said:
I think you have to open the back cover, disconnect the battery connector, connect it to computer, hopefully it will get detected as mediatek then you can follow this guide
Click to expand...
Click to collapse
Unfortunately that didn't work either. Sent to Mi Service center, they tried EDL by opening back cover,, didn't work. Now sent phone to xiaomi by service center, i'll get either this one repaired or new one in a week. (as per Mi)
Surprisingly i wasn't the only one or first one to report this. There have been similar incidences earlier as well and even the ones that were on stock everything and locked bootloader. Apparently the new update 11.0.1 is troublesome. - as reported by Mi executive.
Here's my solution
I've got my brand new Redmi Note 8 Pro and just unlocked it yesterday. Today I install the Global ROM and it just work fine BUT I when further : root and install magisk... Then I got a recovery boot loop, I try to solve the issue by flashing another TWRP and then BAM no more fastboot and no more recovery, really bricked hard.
I was using this custom TWRP mention here: https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Please share this solution everywhere because that really solve my issue:
(1) Flash recovery using adb YESSSSS
Source: https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
2) Good now I was able to be back in the LR Team TWRP. From there I removed root and thus magisk, completely disabled DM Verify (because this custom TWRP install everything it can also remove it) and wonder happen, I was able to boot my phone and fastboot is back !
pmesolution.ca said:
I've got my brand new Redmi Note 8 Pro and just unlocked it yesterday. Today I install the Global ROM and it just work fine BUT I when further : root and install magisk... Then I got a recovery boot loop, I try to solve the issue by flashing another TWRP and then BAM no more fastboot and no more recovery, really bricked hard.
I was using this custom TWRP mention here: https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Please share this solution everywhere because that really solve my issue:
(1) Flash recovery using adb YESSSSS
Source: https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
2) Good now I was able to be back in the LR Team TWRP. From there I removed root and thus magisk, completely disabled DM Verify (because this custom TWRP install everything it can also remove it) and wonder happen, I was able to boot my phone and fastboot is back !
Click to expand...
Click to collapse
you should share this information in the other posts, to see if it works for others
djzero86 said:
you should share this information in the other posts, to see if it works for others
Click to expand...
Click to collapse
Yes I did share it to the other post which I followed the tutorial But I think my method will allow anyone having access to adb and not Fastboot to flash and boot a new TWRP image which could allow them to flash once again a ROM from the Recovery or modify the source code an fix their issue.
Redmi note 8 pro no recovery and fastboot
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx
My phone keeps restart
I have the same issiue and my phone keeps restart i can't give any command to solve this proplem please help me
Similar issue,
I get the Redmi splash screen, and then it reboot after about 3 seconds. During the reboot cycle, which takes another few seconds - thats the only time my PC can detect the phone.
So Smart Phone Flash Tool can detect it for those few seconds, starts download but then timeouts after 2 minutes (status protocol err). I guess it loses connection.
Phone can't boot into recovery or fastboot. Is it hardbricked/beyond repair ?
More details:
https://forum.xda-developers.com/showpost.php?p=82467553&postcount=16
poster74 said:
Similar issue,
I get the Redmi splash screen, and then it reboot after about 3 seconds. During the reboot cycle, which takes another few seconds - thats the only time my PC can detect the phone.
So Smart Phone Flash Tool can detect it for those few seconds, starts download but then timeouts after 2 minutes (status protocol err). I guess it loses connection.
Phone can't boot into recovery or fastboot. Is it hardbricked/beyond repair ?
More details:
https://forum.xda-developers.com/showpost.php?p=82467553&postcount=16
Click to expand...
Click to collapse
How you brick your phone?
Flash without autorized account
Does any of you guys use the method that mentined in this site bellow
Just type how to flash redmi note 8 pro without authorized accound in google and clike on link proveded by romprovider..(link was deleted by xda so i coulden't share it)
Use it and let me know if it works for you...
Nasser Nody said:
I have the same issiue and my phone keeps restart i can't give any command to solve this proplem please help me
Click to expand...
Click to collapse
use the method that mentined in this site bellow
and let me know if it works for you...
just type how to flash redmi note 8 pro without authorized accound in google and clike on link proveded by romprovider..(link was deleted by xda so i coulden't share it)
majidmjmn said:
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx
Click to expand...
Click to collapse
Now you all already solved this problem? plz mention me plz plz
yeswe61155 said:
Now you all already solved this problem? plz mention me plz plz
Click to expand...
Click to collapse
When it very first shuts down (the redmi logo first disappears and it goes black), before it starts to boot up again, press and hold Volume Down and Power until it takes you to fastboot.
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
Click to expand...
Click to collapse
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
Click to expand...
Click to collapse
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
idog8818 said:
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
Click to expand...
Click to collapse
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Same
Hello,
I think I did the same error, flashing a wrong boot.img...
I tell you if I manage to do something.
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
danyv77 said:
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
Click to expand...
Click to collapse
This only helps when boot image is not damaged.
Duchan_xda said:
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Click to expand...
Click to collapse
I'm with you. The boot image has error and when MTK realize it has something wrong it will NOT enter into fastboot. The only way to fix this is too use SP Flash Tool for deep flash. Mi store uses this way as well to fix the issue.
Try this:
https://c.mi.com/thread-2173190-1-0.html
ppthom said:
Try this:
https://c.mi.com/thread-2173190-1-0.html
Click to expand...
Click to collapse
This does NOT work. Please don't waste time on it.
:good:Thanks for clarifying this. Back to square one ...
idog8818 said:
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Click to expand...
Click to collapse
Are you recover your phone? I'm still waiting one year...
Duchan_xda said:
Are you recover your phone? I'm still waiting one year...
Click to expand...
Click to collapse
I didn`t find any background on your issue, just something like you actually have a device with white led light blinking.
I read this thread before (yes, some weeks ago) this happened to me yesterday https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-unlock-note-8-pro-authorised-t4168805 the short story is that I were trying to return to Miui 12 after of using some custom ROMs and something in the flashing process failed I mean it was an incomplete flashing and I assumed that most probably just the bootloader partition was damaged. The whole important fact in this situation is that you have yet available fastboot mode but like the splash partition with its image was gone I couldn `t see it and I were anyway in fastboot mode so I could flash the proper files to "unbrik" it. (my device is unlocked)
What you should try is connect it with PC while you`re pressing the volume down, enter to adb/fastboot environment and type fastboot commands to see if device is recogniced, you don`t have to hear constant reboot sounds or in this case press the power button simulating that you are powering off device.
Hello guys, i have a mi 10t pro, today try after unlock devices 7 days to flashed and downgrade because my battery drain is significative, i had 12.5.1 eea firmware and try to downgrade to 12.0.19, but now phone is in continus reboot in to fastboot, i try to flash with last miflash tool, but after 2sec is tell me that firmware upgrade is complete and now i can't start my smartphone. i can try to flash last rom fastboot 12.5.1 but without result. How i can resolve this problem? thanks in advance
When trying to do any major change like a downgrade, you must factory reset. MiFlash should have done that for you, but I guess there's a chance it didn't.
To do a factory reset from Fastboot you can use a compatible version of TWRP and just boot into it (not installing it).
Eg. fastboot boot TWRP_apollo_3.5.0_10-beta_1_whyle.img
From within TWRP you can then do a factory reset and see if it'll boot.
If it still boots into fastboot then you have the option of an alternative ROM. Xiaomi.eu provides a debloated version of the Chinese MIUI ROM. I'm running its latest 12.6 version and it has no problems with battery drain. https://xiaomi.eu/community/threads/21-6-23.61942/
chisnz said:
When trying to do any major change like a downgrade, you must factory reset. MiFlash should have done that for you, but I guess there's a chance it didn't.
To do a factory reset from Fastboot you can use a compatible version of TWRP and just boot into it (not installing it).
Eg. fastboot boot TWRP_apollo_3.5.0_10-beta_1_whyle.img
From within TWRP you can then do a factory reset and see if it'll boot.
If it still boots into fastboot then you have the option of an alternative ROM. Xiaomi.eu provides a debloated version of the Chinese MIUI ROM. I'm running its latest 12.6 version and it has no problems with battery drain. https://xiaomi.eu/community/threads/21-6-23.61942/
Click to expand...
Click to collapse
Thanks i can try any solution. i install trought cmd fastboot comand twrp image file and after try to reset it? help me if you have other solution to I was hoping there was a way to bring it back to a stock firmware or a recovery firmware. I tried to flash all.bat inside firmware 12.5.1 my last firmware, proceeded it's fine and complete but after install my phone reboot continuos after logo. as if it didn't have a firmware installed.
P.s. Explain to me the procedure to start twrp without installing it step by step. Thanks so much ^^
To use TWRP to factory reset, first find a compatible TWRP. I used the latest version from:
https://forum.xda-developers.com/t/...r-mi-10t-mi-10t-pro-redmi-k30s-ultra.4187427/
which was TWRP_apollo_3.5.0_10-beta_1_whyle.img
Boot into download mode
Then type this exactly (or change to a different file name if you're using a different version of TWRP):
fastboot boot TWRP_apollo_3.5.0_10-beta_1_whyle.img
Once TWRP starts up, go into Advanced, Wipe.
Tick
- data
- cache
- dalvik (dalvik cache)
and select to wipe it.
Reboot system.
That should leave you with no account set up and enable you to boot and setup from scratch in most cases.
chisnz said:
To use TWRP to factory reset, first find a compatible TWRP. I used the latest version from:
https://forum.xda-developers.com/t/...r-mi-10t-mi-10t-pro-redmi-k30s-ultra.4187427/
which was TWRP_apollo_3.5.0_10-beta_1_whyle.img
Boot into download mode
Then type this exactly (or change to a different file name if you're using a different version of TWRP):
fastboot boot TWRP_apollo_3.5.0_10-beta_1_whyle.img
Once TWRP starts up, go into Advanced, Wipe.
Tick
- data
- cache
- dalvik (dalvik cache)
and select to wipe it.
Reboot system.
That should leave you with no account set up and enable you to boot and setup from scratch in most cases.
Click to expand...
Click to collapse
ok it's fine i have enter in twrp now and format data + cache + dalvik, But now reboot in fastboot mode and it always starts in fastboot continuos. how should i proceed now to install a basic firmware and be able to start the mi 10t pro eea?
i want to try to install with twrp, what rom i need? fastboot rom tgz or full rom .zip from mi.com site? thanks
update Mi-flash. There's 2021 version.
Code:
fastboot reboot bootloader
disconnect USB cable and reconnect it again
flash again with Mi-flash, do not lock it.
Fastboot ROMs are more than 3GB.
pl1992aw said:
update Mi-flash. There's 2021 version.
Code:
fastboot reboot bootloader
disconnect USB cable and reconnect it again
flash again with Mi-flash, do not lock it.
Fastboot ROMs are more than 3GB.
Click to expand...
Click to collapse
hELLO PL1992, i have use now MiFlash20210226 version installed for 1sec and nothing is installed, the mobile is in fastboot but I can't figure out how to complete the flash of the fastboot rom. I am using the latest EEA fastboot rom for my device, I have tried several versions even earlier but nothing. he says he has completed the procedure but in 1 sec he does absolutely nothing. Do you have solution ideas to try? alternatives to miflash? I also tried to install by extracting the Fastboot rom from inside the rom with flash all.bat, the procedure always go well, but the phone keeps restarting after the MIUI logo every 2sec. I have windows 10 pro i don't know if it is the problem
fantidus90 said:
hELLO PL1992, i have use now MiFlash20210226 version installed for 1sec and nothing is installed, the mobile is in fastboot but I can't figure out how to complete the flash of the fastboot rom. I am using the latest EEA fastboot rom for my device, I have tried several versions even earlier but nothing. he says he has completed the procedure but in 1 sec he does absolutely nothing. Do you have solution ideas to try? alternatives to miflash? I also tried to install by extracting the Fastboot rom from inside the rom with flash all.bat, the procedure always go well, but the phone keeps restarting after the MIUI logo every 2sec.
Click to expand...
Click to collapse
Did you execute the code given to you before you flash it?
In Mi-flash, click Driver, then install.
After it's done, reboot your PC.
Then do the
Code:
fastboot reboot bootloader
command.
The flashing process should be more than 500 seconds if it's done correctly.
The fastboot ROM should be extracted, not using directly the tgz file.
Rename the extracted folder name short, like "1", and put in C:/ drive.
pl1992aw said:
Did you execute the code given to you before you flash it?
In Mi-flash, click Driver, then install.
After it's done, reboot your PC.
The flashing process should be more than 500 seconds if it's done correctly.
The fastboot ROM should be extracted, not using directly the tgz file.
Rename the extracted folder name short, like "1", and put in C:/ drive.
Click to expand...
Click to collapse
I followed your advice but nothing has changed. i have make a screen, i create in C:/miui/1/all extracted rom .tgz, but flashed for 5sec and completed process =/
fantidus90 said:
I followed your advice but nothing has changed
Click to expand...
Click to collapse
Run command:
Code:
fastboot reboot bootloader
Phone will reboot to fastboot.
Change a USB port.
Do not use USB hub.
If you are using desktop PC, connect it to the motherboard USB port.
fantidus90 said:
I followed your advice but nothing has changed. i have make a screen, i create in C:/miui/1/all extracted rom .tgz, but flashed for 5sec and completed process =/
Click to expand...
Click to collapse
Click the log to see what it done.
If you think this is bothersome, then do the TWRP way you want to.
For TWRP way, you flash the recovery version zip.
pl1992aw said:
Click the log to see what it done.
If you think this is bothersome, then do the TWRP way you want to.
For TWRP way, you flash the recovery version zip.
Click to expand...
Click to collapse
i have 3 report in log. posted here the file. thanks for help bro. Hope that you can find my problem and i can use my new xiaomi again.
fantidus90 said:
i have 3 report in log. posted here the file. thanks for help bro. Hope that you can find my problem and i can use my new xiaomi again.
Click to expand...
Click to collapse
Code:
echo Missmatching image and device
It seems the ROM and your device is not matching, so it don't flash.
First confirm what your phone model is. The model should be written on the box came with the phone.
Install this program:
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
It will need java SE, follow the FAQ guide in that github to use the program.
It should show you what phone you have.
Like this
fantidus90 said:
i have 3 report in log. posted here the file. thanks for help bro. Hope that you can find my problem and i can use my new xiaomi again.
Click to expand...
Click to collapse
Hi there, probably found the answer. It can be because of your PC CPU.
Read here:
https://forum.xda-developers.com/t/3638653/post-82085077
If you are very sure your phone is apollo, then you can do similar to this one and try again:
https://forum.xda-developers.com/t/3638653/post-73105436
Do not lock bootloader
pl1992aw said:
Hi there, probably found the answer. It can be because of your PC CPU.
Read here:
https://forum.xda-developers.com/t/3638653/post-82085077
If you are very sure your phone is apollo, then you can do similar to this one and try again:
https://forum.xda-developers.com/t/3638653/post-73105436
Do not lock bootloader
Click to expand...
Click to collapse
I have resolve thanks pl1992, i want to share my solution. Use Twrp to boot with fastboot boot twrp name.img command. After i copy recovery firmware .zip on my usb stick/type C connection and i connect directly on my mi 10t pro type c, not read first time in ntfs system, after i format with fat32 and recopy recovery firmware .zip and install throught TWRP. ALL is Ok now. Thank you
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5