Develop Bugs

Fast boot mode started, can't go to download mode

Hi Everyone
Sorry for my not so good English.
I have problem with my G3 and maybe someone can help? I instal root without problem, than I try to install Twrp recovery and after that I have that message ( [780] fast boot mode started) all the time, I try to do hard reset, click yes twice, but getting the same message, Is there any chance to unbrick that device when I can't go even to download mode?
Thank You very much for any suggestions

help!
help my G3 died the same thing happened!

same to me...

What model(s)? Youll need a pc, adb/fastboot, stock laf.img and boot.img for your device. Youll use adb commands to erase these img files and restore them with the new ones. Once you have adb running and recognizing your device with both files in same folder as adb you'll type adb erase laf [Enter] then adb flash laf laf.img [Enter] do the same steps for the boot.img. Next type adb reboot [Enter] you'll still be in fastboot but just pull the battery. Then replace battery and you should be able to enter download mode by inserting the usb and pressing vol +(i believe, it's been a while) and then kdz flash..

lg g3. maybe you have link ? how to do this..
Thanks.

nerija.nest said:
lg g3. maybe you have link ? how to do this..
Thanks.
Click to expand...
Click to collapse
I know its an lg g3 but what model. I dont have a link to these files and don't feel like searching youll have to search the forum.. Also I just told you how to do this..

D855 16gb , This is what needs to be missed for several days in search of forum. Will be a beautiful day..

nerija.nest said:
D855 16gb , This is what needs to be missed for several days in search of forum. Will be a beautiful day..
Click to expand...
Click to collapse
Ok well I'll meet you in the middle. Heres the link to the d855 partion files http://forum.xda-developers.com/showthread.php?t=2766437. I believe you'll need the second link in the ops first post. As far as adb.. If you dont know how to use it or get the files, Google should be able to help you.

Swizzle82 said:
Ok well Ill meet you in the middle. Heres the link to the d855 partion files http://forum.xda-developers.com/showthread.php?t=2766437. I believe youll need the second link in the ops first post. As far as adb.. If you dont know how to use it or get the files, Google should
be able to help you.
Click to expand...
Click to collapse
Did he drag the .img to the command prompt in order for it work. So its flash laf (the file that is dragged) next do the same thing with boot.img ( flash boot (drag boot file)) and the recovery.img
---------- Post added at 07:47 PM ---------- Previous post was at 07:46 PM ----------
Its suppose to boot up the phone with no problem

i have one problem, not can write files FAILED (remote: flash write failure fastboot unlock , bet I not can write and erase... failure...

download mode problem
I couldn't fix this problem.
[520] Fastboot mode started
[610]--reset--
[610]--portchange--
[730] fastboot: processing commads
can't go to download.I tried adb erase laf adb erase boot I guess I couldn't do.help

if not done contact fb tungkick777 i can help all every body free

fastboot mode started
plz
tungkick said:
if not done contact fb tungkick777 i can help all every body free
Click to expand...
Click to collapse

I have the same problem.. i have d852.. please help!!

i have the same problems after the new upgrade to lollipo 20E vodafone Italy..

Same here
Edit: Solved
1) Took battery and USB Cable off
2) Pressed Volume Up
3) Took battery back while pressing volume up
4) Inserted USB Cable while pressing volume up
5) Phone started Download Mode
6) installed kdz through LG Flash Tools
Right now typing from my LG G3

Great!!!
Thank you very mucho Fusquinha77!!!

I cant get it, I use every way(erase boot,system,recovery, use advence power menu ext..)
But i cant go to download mode
Sent from my Smartfren Andromax AD6B1H using XDA Free mobile app

Fusquinha77 said:
Same here
Edit: Solved
1) Took battery and USB Cable off
2) Pressed Volume Up
3) Took battery back while pressing volume up
4) Inserted USB Cable while pressing volume up
5) Phone started Download Mode
6) installed kdz through LG Flash Tools
Right now typing from my LG G3
Click to expand...
Click to collapse
I can see a different screen for a split of a second but it's going back to Fastboot mode...

@SaharLevi
Here's the fix Quick and easy
need to have fastboot, I used ubuntu can install with sudo apt-get install android-tools-fastboot
info on fastboot
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer
also need recovery.img, I used the lastest twrp
In terminal
fastboot boot recovery.img
this will boot your phone with the img on your computer.
in recovery restore or install a good boot or kernel.
your phone should be good to go after that.
I had my phone fixed in about 5 min, I really should not play around with boot partition.
Also should be able to flash boot if you have a good one,
fastboot flash boot boot.img

[Q] Random Reboots on ZF2 4gb/32gb

Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.

Suhas_JS said:
Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.
Click to expand...
Click to collapse
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.

kibmikey1 said:
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.
Click to expand...
Click to collapse
Just hard reset or complete wiping of cache, dalvik, data, root and then reload the stock/pre-rooted ROM?

It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.

Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app

i suspect this has alot to do with android 5.0. asus needs to work on getting 5.1 to the device.

Suhas_JS said:
Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
what rom did you install? latest or stock?
did you follow the step one or alternative??
please help me i got the same problem.

kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
stock ROM from Asus[/URL] or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
---------- Post added at 06:54 PM ---------- Previous post was at 06:48 PM ----------
kowsar684 said:
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
Click to expand...
Click to collapse
no problem is still there ...... should i install pre root rom???
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
what is the difference between stock ROM and pre root ROM???

can't install stock rom. how to flass

kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
Thanks a million man.
This saved me instead of sending back the phone rto newegg after a failed cache format.
Repped!!!

I have folowed all step successfuly but reboots are still there, i can't do **** about them, mostly happen installing / updating apps and playing games, sometime it's just random, listening music.

more ideas about why it's happen?

I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.

sandozer said:
I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.
Click to expand...
Click to collapse
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD

Anyone get a random shutdown with the 2.19.40.20 firmware? Happened to me overnight/this morning, at 98 to 96% charge. First time this has happened with this device.
No last_kmsg to share, so will keep a watch on it for now...
Edit: happened a second time, this afternoon. Maybe I will upgrade to 2.19.40.22, or at least install TWRP to see if I can grab a last_kmsg (if I can find it) to see what's going on..

chooks06 said:
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .

@sandozer..5.1 will do a lot of good for a lot of people

sandozer said:
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .
Click to expand...
Click to collapse
If you have not tried resetting the phone, it may be worth a try, though painful to start setting up all over again. You can try using the stock ASUS back up app to do your back up..
Sent from my ASUS_Z00AD

I am on 22 and have random reboots as well?

I had 2 random reboots on the 2gb/16gb version, but I think it was USB cable related. I'd plug the phone into the car and do something fast and then lock it, POOF! Reboot. It hasn't happened in awhile though and I believe I did an OTA update afterwards.

Find 7 (x9076) soft bricked, misread by device manager,

Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?

Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.

adb didnt recognize my device -but how do I do that just in case I'm able to get it working?

Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.

ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone

tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??

Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.

tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.

Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.

tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted

**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.

If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.

RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?

Hard Bricked Ze551ml?

Hi everyone, i'm kinda new here and noob i'll describe the problem.
I have already followed many guides about bricked phones, fastboot solving and xftsk.
I have this Zenfone 2 Deluxe that i have modded with Groovy Android, tried to root with magisk but it didn't work so i wiped everything with TWRP(every option). Only TWRP worked for 2 days telling me that there was no OS. So i tried to flash a stock firmware via ASUS Flash tool but it didn't work cause it couldn't enable ADB. ADB didn't work once, first it didn't detect phone, then it said device offline so I gave up. Found the xFTSK method. Tried it and worked ( it booted into bootloader with the rainbow icon and still does) but the serial changed to 0123456789ABCDEF. Tried Fastboot right after as guides said. Fastboot didn't and still don't work. He couldn't find files, couldn't load them and now it says " failed (write to device failed(unknown error)). So I tried ASUS flash tool again but he said flash image failure status read failed too many links, then that fastboot coulnd't be loaded and other errors.
Along the way recovery mode "disappeared" too. It doesn't work anymore. Plus sometimes the phone boots and keeps rebooting into a white usb icon.
What should I do? Feel free to re-link me guides, PM or something else, i'm open to almost everything to solve that.
Thanks in advance.
Edit: fastboot gaves some kinda errors with partitions too ex: can't erase cache.
Battery and cable are not ASUS original ones.

MixedFried said:
Hi everyone, i'm kinda new here and noob i'll describe the problem.
I have already followed many guides about bricked phones, fastboot solving and xftsk.
I have this Zenfone 2 Deluxe that i have modded with Groovy Android, tried to root with magisk but it didn't work so i wiped everything with TWRP(every option). Only TWRP worked for 2 days telling me that there was no OS. So i tried to flash a stock firmware via ASUS Flash tool but it didn't work cause it couldn't enable ADB. ADB didn't work once, first it didn't detect phone, then it said device offline so I gave up. Found the xFTSK method. Tried it and worked ( it booted into bootloader with the rainbow icon and still does) but the serial changed to 0123456789ABCDEF. Tried Fastboot right after as guides said. Fastboot didn't and still don't work. He couldn't find files, couldn't load them and now it says " failed (write to device failed(unknown error)). So I tried ASUS flash tool again but he said flash image failure status read failed too many links, then that fastboot coulnd't be loaded and other errors.
Along the way recovery mode "disappeared" too. It doesn't work anymore. Plus sometimes the phone boots and keeps rebooting into a white usb icon.
What should I do? Feel free to re-link me guides, PM or something else, i'm open to almost everything to solve that.
Thanks in advance.
Edit: fastboot gaves some kinda errors with partitions too ex: can't erase cache.
Battery and cable are not ASUS original ones.
Click to expand...
Click to collapse
do not use asus flash tool to flash raw firmware. use commands to flash firmware. second if you will use latest raw after xFSTK it will not work. Use old raw firmware provided in guide. Hoping that ASUS flash tool has not messed up your device. use old firmware in guide command's method. if fails once again use xFSTK and flash old firmware via commands. Stay away from asus flash tool.

sukhwant717 said:
do not use asus flash tool to flash raw firmware. use commands to flash firmware. second if you will use latest raw after xFSTK it will not work. Use old raw firmware provided in guide. Hoping that ASUS flash tool has not messed up your device. use old firmware in guide command's method. if fails once again use xFSTK and flash old firmware via commands. Stay away from asus flash tool.
Click to expand...
Click to collapse
Thanks for the advices. Fact is, fastboot commands do not work so I tried flashing varius raw files via Asus flash tool but without success. If u think u can help me I can post screenshots about the errors ( I don't know why they change everytime)

MixedFried said:
Thanks for the advices. Fact is, fastboot commands do not work so I tried flashing varius raw files via Asus flash tool but without success. If u think u can help me I can post screenshots about the errors ( I don't know why they change everytime)
Click to expand...
Click to collapse
yes a screenshot would be good. as i told earlier. new firmware version or bootloader have different set of commands. post raw firmware version number you are using along withifwi version and bootloader version you are on currently.

sukhwant717 said:
yes a screenshot would be good. as i told earlier. new firmware version or bootloader have different set of commands. post raw firmware version number you are using along withifwi version and bootloader version you are on currently.
Click to expand...
Click to collapse
Fine, bootloader version says " unknown " now, i'll try re-using xFSTK. About the screenshots here they are. http://puu.sh/D7tXU/b83ccf1502.png

Recovering data on a DEAD Redmi Note 8 PRO

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