Develop Bugs

[Q]Getting Error In installing cwm recovery from fastboot!

I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?

http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Go to this thread and follow the simple instructions...dnt go through such command prompts..when an easy way is available hit thanks if i helped

MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed

Your recovery partition is locked.
1. Make yourself a developer (go to Settings -> About Phone -> Tap on Build until developer
2. In Developer options turn on Enable OEM unlock
3. Flash the new recovery, don forget to "fastboot oem unlock"
4. Important: don't allow phone to complete a normal reboot after flash. When rebooting, press Vol Up + Vol Down + Power to enter CWM recovery directly. Otherwise the stock recovery will replace CWM again.

When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!

sbpetrack said:
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
Click to expand...
Click to collapse
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...

marc2800 said:
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
Click to expand...
Click to collapse
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.

Thi is NOT the exact same issue as we have: you are stuck in a boot-loop; we have a version of fastboot which seems to have disabled the volumeUp button, thereby making it impossible to confirm our request to unlock the bootloader. e can only press VolumeDown (which cancels our request to unlock the bootloader).
i posted at http://forum.xda-developers.com/showpost.php?p=65462453&postcount=48 a suggestion for how to proceed in your case: just use SP Flash tools to reinstall a stock recovery image, and then use that recovery to install a complete stock ROM.
,BTW, Sir, when you say:
> ...with the Alcatel One Touch Pop 3 - 5015x. I ... had a problem with the OEM, solved it by finding the top post on THIS thread
note that the solution given in the top post of this thread is designed for Android One devices, and your Alcatel One Touch does NOT appear in the list of supported devices for that "fix." can't say it's entirely surprising that you would get into a bootloader problem if you apply top your phone a bootloader unlock solution for some random other platform!! LUck would not likely be with you when doing that.

zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
I can't understand why volume down is working fine and not volume UP...

zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
Go in bootloader mode, connect your phone to your computer and tell me what do you get if you tape in your console "fastboot devices"
I want to know the number before fastboot.. mine is strange and maybe not the original

MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
That is also my problem with my phone!
---------- Post added at 05:56 AM ---------- Previous post was at 05:54 AM ----------
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
Hi, I had done that fastboot oem unlock command and pressed Volume Up but nothing happened and my bootloader still locked could you help? Thanks, my phone is Starmobile UP HD MTK6582 :laugh:

GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
really thanks:angel:

I can't
I have an error installing a ROM, partition x not allowed.
I can't go in recovery mode + I can't open my phone to enable usb debugging.
I don't have root & and I don't have my OEM unlocked.
How can I install my ROM for Asus Zenfone GO ZC500TG? :'( :'(

Anyone, please?!!

ADB devices allowed?
I have the same problem, but i just resolve it now. First, i've connected my phone in normal mode, then i opened cmd and wrote: adb devices, and a popup displayed in my phone to allow adb debug. I allowed and reboot to bootloader and follow all steps to unlock bootloader.

I also have problems, my phone is a polaroid turbo c4 plus and i cand get through the setup, so i can't install cwm and i am searching for methods to recover it, it's pretty hard since theres nothing online about it

phone is dead. only access to fastboot

phone is dead
when plug in for charging it shows charging logo then restart and restart again. loop
second when i try to go in recovery , again it restart never go to recovery.
i can only access fastboot option.
i never try to root or unlock bootloader.
my phone is locked.

arixeon said:
phone is dead
when plug in for charging it shows charging logo then restart and restart again. loop
second when i try to go in recovery , again it restart never go to recovery.
i can only access fastboot option.
i never try to root or unlock bootloader.
my phone is locked.
Click to expand...
Click to collapse
i had the same problem please some one answer

arixeon said:
phone is dead
when plug in for charging it shows charging logo then restart and restart again. loop
second when i try to go in recovery , again it restart never go to recovery.
i can only access fastboot option.
i never try to root or unlock bootloader.
my phone is locked.
Click to expand...
Click to collapse
1. What phone model? What version of firmware 5.0.2 or 6.0.1?

Yes, same this with me. 6.0. I tried reset, but reset is not working. So I unlocked device , installed twrp, but twrp sometimes starts and only for few seconds. Mostly phone is either stuck in logo, or just shuts down after boot vibration. No luck in recovery. My phone crashed suddenly and got into this situation.

gSingh05 said:
Yes, same this with me. 6.0. I tried reset, but reset is not working. So I unlocked device , installed twrp, but twrp sometimes starts and only for few seconds. Mostly phone is either stuck in logo, or just shuts down after boot vibration. No luck in recovery. My phone crashed suddenly and got into this situation.
Click to expand...
Click to collapse
you unlocked your device after it was dead or before
because mine 820 is locked and i cant do anything

arixeon said:
you unlocked your device after it was dead or before
because mine 820 is locked and i cant do anything
Click to expand...
Click to collapse
After it was dead. I got into fastboot. And from linux , using tutorial from HTC unlocked the device.

gSingh05 said:
After it was dead. I got into fastboot. And from linux , using tutorial from HTC unlocked the device.
Click to expand...
Click to collapse
please share the link or method to unlock bootloader while phone is dead. in current situation im unable to write or update the firmware .

arixeon said:
please share the link or method to unlock bootloader while phone is dead. in current situation im unable to write or update the firmware .
Click to expand...
Click to collapse
http://www.htcdev.com/bootloader
You have to register.
For Windows: Install HTC drivers, HTC Sync Manager(optional), fastboot, adb.
For linux: Install android-tools
Put phone into Hboot -> Fastboot.
Connect to PC and from cmd/terminal you have to execute commands as told by HTC site.
> fastboot oem get_identifier_token
This will give you a string , copy paste from '<<Identifier Token start>>' to '<<Token End>>' , only this column, no prefix.
Paste this into website. There will be text box while following steps.
You will get a file in email attachment. It will be something like this 'Unlock_code.bin'
And also the link to further steps will be provided.
> fastboot flash unlocktoken Unlock_code.bin
You will get option on phone screen. 'Yes' 'No'. Use volume button and select Yes.
and its done.
It hardly takes a minute

gSingh05 said:
http://www.htcdev.com/bootloader
You have to register.
For Windows: Install HTC drivers, HTC Sync Manager(optional), fastboot, adb.
For linux: Install android-tools
Put phone into Hboot -> Fastboot.
Connect to PC and from cmd/terminal you have to execute commands as told by HTC site.
> fastboot oem get_identifier_token
This will give you a string , copy paste from '<<Identifier Token start>>' to '<<Token End>>' , only this column, no prefix.
Paste this into website. There will be text box while following steps.
You will get a file in email attachment. It will be something like this 'Unlock_code.bin'
And also the link to further steps will be provided.
> fastboot flash unlocktoken Unlock_code.bin
You will get option on phone screen. 'Yes' 'No'. Use volume button and select Yes.
and its done.
It hardly takes a minute
Click to expand...
Click to collapse
thanks
now i unlocked the bootloader abd installed recovery but unable to enter in the recovery.. it shows that entering recovery and then restart loop .

arixeon said:
thanks
now i unlocked the bootloader abd installed recovery but unable to enter in the recovery.. it shows that entering recovery and then restart loop .
Click to expand...
Click to collapse
Yes it happens sometimes.
Make sure the recovery step was complete. For win: The .exe cmd should exit on clicking enter or automatic, till then don't remove the phone.
Try some combinations:
- turn phone OFF from Hboot then start recovery
- if screen shows 'entering recovery' let it be , wait for reboot or shutdown
- try alternative options of 'reset' and 'recovery' both will get you to twrp
- remove sdcard then try
- check charging
- don't try if overheating, let the phone be in normal temperature.
I had similar problem, but trying combos started twrp.
The mistake I did was to wipe everything. Don't do that, try to wipe cache, the first default option provided by twrp and start phone. (no sdcard/sim)
I was able to install Tomal's Discovery ROM but after some time phone again rebooted and stuck in loop.
For any restore/flash use internal memory. SDcard failed to work for me ( i tried many different sdcards).

Tried flashing CM13, now can't enter normal boot

So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks

Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.

[BRICKED] Stuck in android 8.1 bootloop

I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks

Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.

BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked

Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem

droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.

BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...

after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool

LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....

try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash

Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.

Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?

I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.

I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?

droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?

Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]

How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?

had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again

Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.

Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse

Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !

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