Database Develop

Accidentally formatted sdcard prior to flashing

Hey guys, I need some help here
I accidentally formatted the sdcard when preparing a clean flash. I also formatted system ect. so now all I can do is boot into recovery but no files to flash.
Is there some way I can transfer files to the sdcard og another way to get the device working again?
Thanks in advance.

You are softbricked. Restore factory image using wugfresh
http://www.wugfresh.com/nrt/

Download the factory images, boot into bootloader (not recovery) by holding power+down, then flash the factory images.

I'm in exactly the same boat here, but every time I try to use fastboot commands, I get a write failed. I'm fairly certain the drivers are installed properly, as fastboot devices shows me the device. What else could be done?

codemonkey85 said:
I'm in exactly the same boat here, but every time I try to use fastboot commands, I get a write failed. I'm fairly certain the drivers are installed properly, as fastboot devices shows me the device. What else could be done?
Click to expand...
Click to collapse
Give the exact steps and exact messages, cut and paste is best, otherwise there is not enough info to go on.

I installed the drivers using Nexus Root Toolkit 1.5.5. (I used option #2, which is to install the signed drivers.)
I copied the extracted contents of the Nexus 7 4.2 factory image into my adb folder. I ran a command prompt in that folder.
I type: fastboot devices
I get: 015d25687443fe0f fastboot
I type: fastboot flash bootloader bootloader-grouper-4.13.img
I get: FAILED (command write failed (Unknown error))
I type: fastboot -w update image-nakasi-jop40c.zip
I get: FAILED (command write failed (Unknown error))

Well, I don't know how or why, but I just tried the same thing again using the Nexus Toolkit and it worked this time. I'm booting into a stock ROM right now.

Im unable to turn on USB debugging, cause i have no ROM. What to do?

codemonkey85 said:
I installed the drivers using Nexus Root Toolkit 1.5.5. (I used option #2, which is to install the signed drivers.)
I copied the extracted contents of the Nexus 7 4.2 factory image into my adb folder. I ran a command prompt in that folder.
I type: fastboot devices
I get: 015d25687443fe0f fastboot
I type: fastboot flash bootloader bootloader-grouper-4.13.img
I get: FAILED (command write failed (Unknown error))
I type: fastboot -w update image-nakasi-jop40c.zip
I get: FAILED (command write failed (Unknown error))
Click to expand...
Click to collapse
exactly the same error im getting.. how did you solve it?

Tried again on another USB port and now it worked.
Thanks for the help guys.

codemonkey85 said:
Well, I don't know how or why, but I just tried the same thing again using the Nexus Toolkit and it worked this time. I'm booting into a stock ROM right now.
Click to expand...
Click to collapse
Out of interest why didn't you just run the small script that comes with the factory image to wipe and reflash everything.
It's what I did to make sure I had a nice clean install.
Or were you trying to keep some data from /data for example.

KFHD7 Tate Bootloop

Hi,
I updated my good old Kindle Fire HD 7 (tate) to cm 12.1 and because of problems with the Play store I made a factory reset. Since then it is in a bootloop showing only the blue teamwin screen with some flickering about every 5-6 seconds.
As I read here (http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html), I need to use fastboot.exe to start a new recovery but... fastboot does not recognize the device.
What is working?
adb status-window shows
...Android Debug Bridge
State: unknown (or recovery)
adb reboot revovery - reboots the device
adb reboot bootloader - reboots the device showing a "fastboot logo"
fastboot devices
< waiting for device > / or just no reaction
fastboot -i 0x1949 getvar product
TATE-PUT-08
Okay, after some research I updated my driver (as seen here http://forum.xda-developers.com/showthread.php?t=2271909) and they seem to be installed properly but nothing changes to the behaviour shown above.
What to do?
And thanks a lot!
My systems: Windows 7 Professional 64 bit or Windows 7 Home Premium 64 Bit

..getting creative, I tried
fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
creating boot image...
creating boot image - 8343552 bytes
downloading 'boot.img'...
OKAY [ 2.817s]
booting...
OKAY [ -0.000s]
finished. total time: 2.817s
..and it reboots into the same teamwin splash screen boot loop
...with adb status-window saying "recovery"

Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working

Same problem! PLEASE HELP!
I'm stuck with THE EXACT same problem.
Please tell me how to go about this step-by-step?
I hope you reply asap..
TIA.

Diplominformatiker said:
Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working
Click to expand...
Click to collapse
can you please do a step by step write-up please?

1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck

Diplominformatiker said:
1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck
Click to expand...
Click to collapse
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?

whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...

hiii
Same situation , no solution until now

unimoose said:
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?
Click to expand...
Click to collapse
In device managment, set to see the hidden devices, must appear as TATE-PVT-8, depending the version of Windows you're using must set the signed drivers to disable.
Then update the driver to tate with this controllers.
And use fatbootmode, can use: KFHD_SRTool_v1.2 to revert to completly stock.
Hopes works for you.

Enomaly said:
whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...
Click to expand...
Click to collapse
Are you saying that the above mentioned method will not work? So what is the possible solution?

Mi A2 Can't flash anything via fastboot (bootloader unlocked, oem critical too)

When I flash TWRP
It shows me this
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
PS C:\adb>
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
Code:
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
PS C:\adb>
I try to use another way
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot getvar current-slot
getvar:current-slot FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
PS C:\adb>
But without fastboot devices
Code:
PS C:\adb> fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
PS C:\adb> fastboot flash boot_b recovery.img
sending 'boot_b' (41314 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
-------------------------------------------------------------
UPDATE!!
I just use a USB2.0 Port (USB HUB)
and I got the problem solved!!!!

You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......

bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(

same problem here , please help anyone

cs853120 said:
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(
Click to expand...
Click to collapse
reset your phone once then try........also try to unlock your boot loader & see if you can flash the stock rom from the official website......make sure that the entire rom file is in a folder on your desktop.......for some reason MI flash does not like long system paths.....

cs853120 said:
When I flash TWRP
It shows me this
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
I try to use another way
But without fastboot devices
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
Click to expand...
Click to collapse
Hi there.
I have the same problem. Can't do anything with my phone on any USB 3.0/3.1-Port on my Ryzen desktop (works neither on Win10 nor Linux Mint). I have to use my old Win8.1 Intel laptop and there everything works flawlessly but only on the USB 2.0 port. I used the same tools/commands/Mi-drivers but it only works on the laptop. Tried different drivers for MB/USB-host controller and different cables but to no avail... Connecting the phone and mtp works but no adb/fastboot.
I read on different threads that other people have the same problem with other hardware setups but most of them were able to fix it with MB drivers from the manufacturer instead of the Windows ones. Maybe that could work for you.
For now I keep the laptop around for flashing my A2....

whenever you get "press any key to shutdown" on fastboot it's because of the usb port, use usb 2.0

I have the same problem , and change to 2.0 USB Ports works! Thanks!

Did you found a solution?

Please help. Facing exact same issue. Tried all USB ports on my PC. Switched between Ubuntu and Win10. All to no avail.

It's a USB 3 problem. I had it too in my laptop. You gotta find a USB 2 port, maybe in another PC. Good luck.
Sent from my Mi A2 using XDA Labs

i was also fasing same problem so what is did is
fastboot flashing unlock_critical
then
fastboot oem edl
and flashed stock

Mi A2 Boot loop
The first thing you'll want to do here is extract the factory images archive that you downloaded from your manufacturer's website. For that part, I'd recommend using 7-Zip, as it's free and works with most archive formats , move all of the contents of the archive to the platform-tools folder inside of your ADB installation directory, then open an ADB Shell window in this folder.
Flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders.
there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
//
fastboot flash boot <boot image file name>.img
//
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
//
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
//
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
//
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
//
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
//
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
//
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot
/
Thanks to Android gadget hacks .
P.S : Including today , it was 22nd time that i rooted , enabled camera2api .. but i think till know its useless .

After dealing with this issue for a long time I found that using a USB hub solved it for me.
This is the one I'm using: https://es.aliexpress.com/item/USB-...342.html?spm=a2g0s.9042311.0.0.1d6e63c04tJJe6
Hope this helped!

the same problem
have tried all USB port, unfortunately, no success

Hi everyone,
Today I have a big problem
I install jasmine__V10.0.8.0.PDIMIXM and after I set "fastboot oem lock" but Now my MI A2 Can't enter in OS.
I have this message on screen
"Your device has loaded a different operation system"
and another page says
"Your device software can'tbe checked for corruption. Plese lock the bootlader.
But when I check in fastboot I have bootloader locked.
Any suggestion to unlock ? I can't enter in OS.
Thanks

HELP
bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
Can you help me with my thread?? Thank you!

Same error.

Download TWRP and TWRP installer
DONT CONNECT YOUR PHONE!!
Put your phone in Fastboot
in cmd type
fastboot boot twrp.img (twrp name instead of twrp.img)
Then when you see <Waiting for Device> connect your phone !
Check if it's working.
This was fix for me, when I was unable to even boot into recovery.
Once you boot into recovery, wipe everything, flash twrp zip, and error should be gone

Hey guys,
same issue here but i don't have any usb2.0 port on my laptop now. Any workaround? Totally sure that i used fastboot + usb3.0 on Sony, LG, Samsung ROMs with no hassles whatsoever. Is this only happening with Xiaomi?
Cheers

How to Unlock Bootloader and Install TWRP

--------------------------------> DISCLAIMER: <------------------------------------​
Guide for pure educational purpose. If you are going to use it, you do it to *your risk and danger, I will not be held responsible if your phone will not work anymore.
Depending on the phone manufacturer, root and unlock the bootloader could invalidate the warranty of the phone​
-------------------------------> PRE-REQUIREMENTS <---------------------------------​
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-for-all-android-devices.html or from attachment:
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-minimal-adb-fastboot-tool.html or from attachment:
Scrolling through the page you will have 2 options: Download or Portable
(choose the one that you prefer)
Pre-Requisite 3
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device (read all tutorial before do it, because it will be wiped all data from the phone)
Settings -> Applications -> Developer Options
Settings -> Applications -> Development
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'Build version' entry
A pop-up should appear, telling you 'now you are a developer'
In case of disaster follow this tutorial:​Restore Stock Image and Lock the Bootloader (for Warranty)​
-------------------------------> UNLOCK BOOTLOADER <---------------------------------​
IMPORTANT NOTE: Before doing this, know that this operation completely reset your device and after rebooting, you will find the phone as if he had just left out of the box. So you'll need to configure your phone again and reinstall all apps.
To unlock bootloader tap on:
Settings -> Applications -> Developer Options
(If you don't see the delevopers option you need to un-hide. To activate developer option click 7 times on ZUI version under settings -> system -> about. Once you did that you get developer options in settings -> system)
Now Click on it (Developers option) and activate the options OEM unlocking and USB debugging
If you have a Pin or Password, it will ask you to re-enter it.
You will see a popup where you will be asked to confirm this operation.
Now start the phone in boolader by doing this:
1) Connect the phone to the PC
2) Start the Minimal ADB & Fastboot program from the PC
3) On the PC screen, type: adb reboot bootloader​
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Booloader mode.
4) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot -i 0x2b4c oem unlock-go​
The response will look like this:
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>​Type:
fastboot reboot​
Now, during the reboot phase, the phone will proceed with a factory reset and will restart normally (it could take a couple of minutes)​
Done, now your phone has the bootloader unlocked.
-------------------------------> HOW TO INSTALL TWRP <---------------------------------​
Download the TWRP from here or mirror
1) Open the folder where your TWRP Recovery .img file is saved.
2)Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
3) Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader​ If your asks for permission to “Allow USB debugging”, tap OK.
4) Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery recovery-TWRP-3.2.3-0110-LENOVO_Z5PRO-CN-wzsx150​
5) Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot​
Well, now you have installed the TWRP Recovery.
If you are interested to know how to root your phone: Follow this TUTORIAL

HOW TO INSTALL TWRP no.2
I can't find cmd.
I can only see the power shell

hohoim said:
HOW TO INSTALL TWRP no.2
I can't find cmd.
I can only see the power shell
Click to expand...
Click to collapse
because you are using win 10, inside the option there is "use powershell instead cmd" of something about that, uncheck it!

Can you push it with original rom like Xiaomi Mi flash?
BadCluster said:
because you are using win 10, inside the option there is "use powershell instead cmd" of something about that, uncheck it!
Click to expand...
Click to collapse
thank you

BadCluster said:
because you are using win 10, inside the option there is "use powershell instead cmd" of something about that, uncheck it!
Click to expand...
Click to collapse
i need help, i cant unlock bootloader a have 10.0.355 version firmware

nerak11111 said:
i need help, i cant unlock bootloader a have 10.0.355 version firmware
Click to expand...
Click to collapse
im on the same firmware, I'm able to input the adb reboot bootloader command and the phone loads in to the bootloader mode but after my pc doesnt recognise the phone, and when i input the fastboot -i 0x2b4c oem unlock-go, nothing happens and it displays waiting for any device,
i think the problem is that after the phone load in to the bootloader mode, the doesnt recognize it anymore so i cant send any commands to it,
can you help please,

i found a way to lock the bootloader after you installed the original rom!
this will solve the < waiting for devices > error when phone is connected to pc
follow this tutorial to install the propper driver if your PC does not recognize the phone in fastboot: tutorial
how do i know if i need this?
to know if the proper drivers are installed open adb and type "adb devices" to see if your device is connected
if your device is connected and seen by adb, proceed to type "fastboot devices". if your device is recognized, you are good to go, if not, please follow the youtube tutorial as it helped me solve this problem.
when your device is read as a adb fastboot device, reboot into bootloader using "adb reboot bootloader"
after this, type "fastboot flashing lock" to relock your device. you will get a message on the device to ask for permission.
BE AWARE! THIS WILL WIPE YOUR PHONE TO FACTORY RESET!
this steps will probably also help to unlock the bootloader in version355, but i have not tried that. please leave your findings below if you tried this!

does it work with lenovo z5 pro gt?

Thanks man i will try this as soon as they deliver my phone still waiting on it.

[/COLOR]
anonOmattie said:
i found a way to lock the bootloader after you installed the original rom!
this will solve the < waiting for devices > error when phone is connected to pc
follow this tutorial to install the propper driver if your PC does not recognize the phone in fastboot:
how do i know if i need this?
to know if the proper drivers are installed open adb and type "adb devices" to see if your device is connected
if your device is connected and seen by adb, proceed to type "fastboot devices". if your device is recognized, you are good to go, if not, please follow the youtube tutorial as it helped me solve this problem.
when your device is read as a adb fastboot device, reboot into bootloader using "adb reboot bootloader"
after this, type "fastboot flashing lock" to relock your device. you will get a message on the device to ask for permission.
BE AWARE! THIS WILL WIPE YOUR PHONE TO FACTORY RESET!
this steps will probably also help to unlock the bootloader in version355, but i have not tried that. please leave your findings below if you tried this!
Click to expand...
Click to collapse
I tried, But I can't.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ver: 355
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
c4aec27a device
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing lock
...
FAILED (remote: Device already : locked!)
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing lock
...
FAILED (remote: Device already : locked!)
finished. total time: 0.059s

SrCDA said:
does it work with lenovo z5 pro gt?
Click to expand...
Click to collapse
i am not sure, but except for cpu the phones are similar. you can try the steps i provided and see if it will lock. no chance of bricking your phone if following shown commands.
please reply if this work!
vinashiny said:
[/COLOR]
I tried, But I can't.
ver: 355
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
c4aec27a device
[B]------------phone is seen by adb as device[/B]
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
[B]-------------phone is not seen as fastboot device, so follow tutorial provided[/B]
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing lock
...
[B]FAILED (remote: Device already : locked!)[/B]
[B]------------why try to lock a already locked phone??[/B]
finished. total time: 0.012s
[/QUOTE]
Click to expand...
Click to collapse

How do I update the OS once i've unlocked the bootloader and rooted?
Do i just simply install the zip update via TWRP? Or do i need to flash it with the qualcomm flashing tool?

I have activate the oem , but in th bootloader it still show that the oem is failed ,it means it haven't turn on the button i don't know why i can't unlock the oem

maxihinz said:
How do I update the OS once i've unlocked the bootloader and rooted?
Do i just simply install the zip update via TWRP? Or do i need to flash it with the qualcomm flashing tool?
Click to expand...
Click to collapse
you should wait for the rom to be updated, and flash it with qfil flasher. there are currently nop twrp roms available...
Blade_zheng said:
I have activate the oem , but in th bootloader it still show that the oem is failed ,it means it haven't turn on the button i don't know why i can't unlock the oem
Click to expand...
Click to collapse
so you want to open or close bootloader?

anonOmattie said:
you should wait for the rom to be updated, and flash it with qfil flasher. there are currently nop twrp roms available...
so you want to open or close bootloader?
Click to expand...
Click to collapse
I will be wait.i want to open the bootloader

doesnt work for me, it only shows :
< waiting for any device >
Click to expand...
Click to collapse
and nothing happens, did i miss a step ? should i do something on the bootloader menu ?

anonOmattie said:
i found a way to lock the bootloader after you installed the original rom!
this will solve the < waiting for devices > error when phone is connected to pc
follow this tutorial to install the propper driver if your PC does not recognize the phone in fastboot:
Click to expand...
Click to collapse
i did this
still gives me the dreadful waiting for any device message

Does NOT work on Win 10!!
It can Reboot to the Bootloader but cant Unlock it always is Say < waiting for any device > and nothing happen....

I have a Lenovo Z5 Pro, firmware 10.0.355, bootloader unlocked and TWRP (no root).
Can I flash the OTA update (I received the 10.5.153 - Android 9.0 OTA update) with the TWRP or I must flash again the original recovery?
If I need the original recovery, anyone knows where I can download the original one (10.0.355).
Thank you.

what about TWRP for Z5 Pro GT 855 version ??

Question Problem with adb devices command on fastboot

I succeeded in unlocking my phone's bootloader.
I enabled usb debugging.
The problem is when the phone is on, my pc can detect this device when I entered 'adb devices' in powershell/ cmd.
But when I entered fastboot, my pc is unable to detect the device whenever I entered 'adb devices' in powershell/ cmd.
It baffles me because I have never encountered this problem before. I had successfully installed twrp recovery on other phones in the past.
On device manager, it shows Android Phone -- Android Bootloader Interface when I connect the phone in fastboot mode. When I boot it, under Universal Serial Bus devices, it shows Redmi Note 11.
I used Google's SDK Platform Tools from here by following this method to install it.
I'm using windows 10 x64 21H2 with latest update.
My phone is spesn.
How do I fix this problem in order to be able to install TWRP recovery?

Have you tried using "fastboot devices" while in fastboot mode, instead of the adb one?

Vagelis1608 said:
Have you tried using "fastboot devices" while in fastboot mode, instead of the adb one?
Click to expand...
Click to collapse
Entering "fastboot devices" detects my device.
But when I entered "fastboot flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img", I get this error:
D:\Data\Library\desktop\Spesn>fastboot flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
Sending 'recovery' (131072 KB) OKAY [ 3.973s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Click to expand...
Click to collapse
Edit:
I fixed it by following this guide and managed to install twrp properly.
Thank you @Vagelis1608 for your help earlier.

Yeah, on AB devices you need to boot the recovery and flash it through there.
Good to see you figured it out though.

redmi note 11 doesnt have recovery partition,you need to use command fastboot flash boot ...