Database Users

Do I Now Own A Brick?

So im stuck on the kindle fire logo on boot after using kindle fire utility V .8 and well i think im bricked. No commands are working and the power button is basically useless. My main question is ive seen some people say they sent it to amazon and got a new one. How would i go about doing this?

Why don't you go read the many threads describing your exact same problem you can fix it.
No you can not return it your warranty is now void.

go into irc with vashypool and he might be able to fix it, donate if u can..

mguinta25 said:
So im stuck on the kindle fire logo on boot after using kindle fire utility V .8 and well i think im bricked. No commands are working and the power button is basically useless. My main question is ive seen some people say they sent it to amazon and got a new one. How would i go about doing this?
Click to expand...
Click to collapse
It does seem that this is a very popular problem... I am not sure what amazon's requirements are exactly on returns once bricked especially if you rooted, but I will say with how popular this problem seems to be, I am sure many of the experienced devs on this site are working on a fix for this (hopefully)... If not I would suggest donating to one of your choice if possible for the work that they have already put into it, explain your problem to them and I am sure it would motivate them to come up with an easy fix for this. Whatever happens you should definitely post back with your findings so that you can help the comunity further with knowledge...

it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further

b63 said:
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
Click to expand...
Click to collapse
Thank you just had to change the bootmode!

My KF is in a boot loop. Boots to the kindle fire logo, sometime does the animation (highlights letters from right to left), sometimes doesnt.
I've downloaded the KFU and installed the drivers. When I run the bootmode menu, it says ADB Status online, ADB rooted no (even though my kindle IS rooted).
When I try to change bootmode to normal, I get a number of errors:
Error: Could not access the Package Manger. Is the system running?
Error type 2
android.util.AndroidException: Can't connect to the activity manager; is the system running?
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
then it says root activated and that the kindle is running in root mode
<idme> Invalid permission
reboot: Operation not permitted
Then despite all the errors, says kindle has been told to reboot in normal mode.
Kindle still gets stuck in boot loop when I try to power on. I've tried powering off the kindle and then on and retrying, I've tried powering off and disconnecting the kindle and computer, still no luck.
Any advice?

if your kf is constantly rebooting (2-3 sec) read this thread:
http://forum.xda-developers.com/showthread.php?t=1424379
if not and you can connect via kfu set bootmode to normal or do it manually depending on the bootstate your in:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot

FWIW, Amazon are really liberal when it comes to returns on the entire Kindle family.
At a X-Mas Eve party, a friend dedcided it would be a good idea to stream some things with AirTwist and left his KF laying on a table, it recieved some pretty serious damage from being dropped, stepped on and having stuff spilled in it, we dont know how, but Amazon replaced it.
So I would say your best bet in case of brick is to at least simulate damage=\

b63 said:
1. run kfu - select change bootmode - select normal -> success ?
Click to expand...
Click to collapse
Thank you.
I just wanted to mention this "as it might help others": I was stuck in Kindle fire screen, can't boot, and can't see the ADB status.
In the device manager I was seeing the yellow mark.
I restarted the device, then the yellow mark went.
Selected change bootmoe -> normal from KFU (even though the status is offline), and worked!
Thank you again.

Having this issue
b63 said:
it's not bricked - i never saw a really bricked one
he's in the wrong bootmode - a common problem and a matter of minutes
read the kfu thread in the dev section !!!
basically here are the following things to do:
1. run kfu - select change bootmode - select normal -> success ?
if not
2. shutdown kf by holding button for ~20 sec and power back up - then point 1 -> success ?
if not
3. disconnect and shutdown KF - shutdown computer and turn on again (no restart) - connect kf (don't turn it on - kf will do at connect) - then point 1 -> success ?
if not
4. you have a driver issue - did you run install_drivers.bat before using KFU ? - correct your driver problem - then point 1 -> success ?
if not
5. ask further
Click to expand...
Click to collapse
I am having this exact issue and i have tried to install drivers but it will not install the drivers it just brings up a code 10 this device cannot start. The device is in my DM as android ADB Interface but it has the yellow "!" sign. kfu when trying to fastboot just says waiting for device and none of the drivers i have tried allow KFU to do its thing and normal boot it.

I just wanted to add, I just had a similar issue last night. I was loading up the MIUI ICS rom, wiped like normal and rebooted to the firefirefire triangle. ...Did not like... Anyhow, I was following the many unbrick guides and couldn't get anything to work. The KF would reboot, and my system (win 7 x64), would see the KF as an unknown device with, "error 43", device cannot start. Then the unit would disconnect(windows sound) from usb, and reconnect and disconnect and then go no where. Each time I rebooted the KF it would do the same thing, also would not go into recovery if I hit the power button during boot. I made a factory cable from an extra usb micro cable I had, to force it into fastboot, and it would come up in device manager as an android usb device. still could not see it via adb directly or in KFU. I found it was the android sdk drivers messing it up. I uninstalled the Android SDK and reinstalled the KF driver package that came with the KFU and viola! I was able to run the TWRP install, and successfully get into recovery. I tried the MIUI ICS Rom install again with a new download just in case, but with the same results. wash, rinse, repeat. I restored my previous ROM in recovery and it booted up like a champ. I'm assuming that since the SDK drivers were causing the issue, I could have probably got the fastboot in firefirefire(during boot) to work properly, and not needed the factory cable. Just wanted to share my late evening fun.
Cheers!
Rob

alfy984 said:
I am having this exact issue and i have tried to install drivers but it will not install the drivers it just brings up a code 10 this device cannot start. The device is in my DM as android ADB Interface but it has the yellow "!" sign. kfu when trying to fastboot just says waiting for device and none of the drivers i have tried allow KFU to do its thing and normal boot it.
Click to expand...
Click to collapse
maybe this helps to sort out the driver issue:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

not able to boot into bootloader/recovery/fastboot

So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format

From your description, it seems like TWRP was not installed correctly. But don't worry, on this phone you do not have to install the recovery to use it. You can boot straight into recovery from your PC while the phone is in 'fastboot' mode. The 'fastboot' mode is what you get when you do 'adb reboot bootloader'. The screen off, blue LED is signalling that the phone is ready for fastboot commands. You can then run:
Code:
fastboot boot <recovery image file>
The phone should load and run the recovery.
Please note that adb will not see your device while it is in fastboot mode. Likewise, fastboot does not work while the phone is accessible through adb. adb support comes from the ROM, but TWRP also supports adb, so you can also use adb while in TWRP.

Rendini said:
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
Click to expand...
Click to collapse
Switch the phone off.
To enter fastboot mode: Hold the Volume UP and connect your phone to the USB port of your PC. The blue LED should come on and provided you have correctly installed drivers, you will be able to use fastboot commands.
To enter bootloader/flashmode: Hold Volume DOWN button and plug USB cable to your PC. Green LED should lit up and provided you have correctly installed the drivers, you will be able to use Flashtool, Emma or other software to flash firmware files.

FAILED (remote: Command not allowed)
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD

Rendini said:
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Click to expand...
Click to collapse
because your bootloader is not unlocked. you have set your bootloader to allow unlocking in developers options, but you need to do the actual unlock using "fastboot unlock" command. you need a unique unlock code from Sony Developers portal and keep in mind that unlocking your device irrevocably deletes DRM keys. it is advisable that you backup your DRM keys before unlocking your device.
the problem is not Sony device, but your unability to read and follow guides and get yourself informed and educated before you dive into trial and error, finaly blaming manufacturer for your own faults...

Lenovo Tab 4 7 TB-7504X - boot charge

But i have new tablet Lenovo Tab 4 7 TB-7504X can you help me from " boot charge" ?
Iam read any ideas with ADB:
adb devices
fastboot bootloader
fastboot getvar all ( iam see: off-mode-charge: 1)
fastboot oem off-mode-charge 0
but my device after take: off-mode-charge 0, does not change ,,1" to ,,0"
if you have any idea, what i am doing bad?

I have tried also multiple times. It seems lenovo has locked that setting
If anybody has ideas how to turn on boot-on-charge i would be willing to pay a small donation
Im using the tablet integrated in my car and I cannot physically access the power button without removing my dashboard.

How to root and twrp levono tab 7504x??

Were you able to get `fastboot oem off-mode-charge` 0 working on this tablet?

OnePlus 5 Bootup when plugged in

Hello,
If my OnePlus 5 is powered off: and I then plug it in; it will semi turn on and go to the battery charging graphic. The phone wont boot into Oxygen OS
I would like to figure out how to get the phone to boot up when plugged in.
I have searched the web and have not come up with any working results. I have tried the following 2 methods:
- Go Into Fastboot and run fastboot oem off-mode-charge 0 ( the system accepts the command and says "okay" but this doesn't get the phone to power on.
- change the lpm or playlpm file ( these files dont exist on this phone so I have no idea which file is in place of lpm)
Thanks!

Ultra Bricked Mi 9t

Hi !
I need your help please, my phone doesn't want to enter in fastboot mode.
* Black Screen 100%
* If I press power button after 4 or 5 seconds it does a vibration
* Power button + Volume Up (looks llike it turn off the phone)
* Power button + Volume Down (looks like it want to enter in fastboot mode)
When my phone is connected to the PC it is recognized as: Unknown USB Device ( Device Descriptor Request Failed )
Blue LED always turned on (once the phone is recognized as Unknown)
The first that I tought when I saw the message ( Unknown USB Device ) was... ok this phone is really hard bricked and is needing a Test Point.
I did the Test point and my phone still giving the same message.
I tried different USB ports and same problem. (USB ports are ok)
I didn't tried a different USB cable and it has higher probabilities that my USB could be damaged. because (Device Descriptor Failed) is a problem from faulty USB ports or Cable.
But my USB Cable looks like new and it was used few times... also I tried moving a bit the connectors to see if it does something but no.. nothing happened.
The USB Port from the phone is like new. (I opened the phone)
If you have experience with the message: "Unknown USB Device (Descriptor Request Failed)
Please give me some help !

Hi !
Looks like the real problem was from drivers. Finally I installed the K20 drivers from this site : https://gsmusbdriver.com/xiaomi-redmi-k20
Then I did the test point
1) I Pressed power button with the test point
2) I heard a vibration
3) I released the power button but I continued with the test point
4) Voila the drivers were installed correctly and now my phone is recognized as: " Qualcomm HS-USB QDLoader 9008 "
EDITED:
If you are experiencing in device manager: USB Device Unknown Descriptor Request Failed maybe could be faulty USB port or cable. In my case was the cable. Now is working perfectly everything with a new USB Cable.

Now I'm trying to flash the phone using " Mi Flash Tool "
I downloaded the stock rom from Xiaomi site.. By the way my phone is with bootloader locked and is not rooted.
I pressed Flash button and the program asked for EDL Authentication. "I Created a new account" Logged suscessfull and then:
"Error" Root Element is missing.
WTF? why xiaomi is asking me for a rooted phone??
Please Help, any Idea about what I'm doing wrong?

romeosantos said:
Now I'm trying to flash the phone using " Mi Flash Tool "
I downloaded the stock rom from Xiaomi site.. By the way my phone is with bootloader locked and is not rooted.
I pressed Flash button and the program asked for EDL Authentication. "I Created a new account" Logged suscessfull and then:
"Error" Root Element is missing.
WTF? why xiaomi is asking me for a rooted phone??
Please Help, any Idea about what I'm doing wrong?
Click to expand...
Click to collapse
I think EDL is a special account authorised by Xiaomi.
Enviado do meu Mi 9T através do Tapatalk

Yeah u need a EDL Flash and for that an EDL verified Account, which u can't get anymore from xiaomi ..
you have to find someone who are willing to do it for you. Usually you have to pay for it .. around $50.
or try this
https://forum.xda-developers.com/showpost.php?p=79004670&postcount=82

solved said:
Yeah u need a EDL Flash and for that an EDL verified Account, which u can't get anymore from xiaomi ..
you have to find someone who are willing to do it for you. Usually you have to pay for it .. around $50.
or try this
https://forum.xda-developers.com/showpost.php?p=79004670&postcount=82
Click to expand...
Click to collapse
I went to S-Unlock and they said "Service offline" do you know or somebody know from other site? or someone that can help me?

romeosantos said:
I went to S-Unlock and they said "Service offline" do you know or somebody know from other site? or someone that can help me?
Click to expand...
Click to collapse
Did you try this :
- Download the stock ROM from xiaomi website, no tools needed, just adb and fastboot installed
- Extract the rom to a folder and launch "flash_all.bat" with admin.
- If you encounter an issue try it with another OS (try this if you don't want to install another OS : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755)
Tell us if it works.

Gimlouuuu said:
Did you try this :
- Download the stock ROM from xiaomi website, no tools needed, just adb and fastboot installed
- Extract the rom to a folder and launch "flash_all.bat" with admin.
- If you encounter an issue try it with another OS (try this if you don't want to install another OS : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755)
Tell us if it works.
Click to expand...
Click to collapse
Good news? I think that my phone now is booting on Fastboot mode? I don´t know how but today it was recognized by the PC as:
MTP USB Device
Please help What I can do to flash my phone¿? it is fastboot mode right? in fastboot mode I can do flash without an account authenticated righT?
Im trying to use Mi Flash TOOL again and Im getting this message:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Im using the latest rom for the K20 global phone but dont know why it is stuck with that message and STATUS: Flashing but it doesnt do any progress.
What Can I do?? is ok MTP USB Device? is that the correct drivers to do a flash in fastboot mode??
Thanks guys!

romeosantos said:
Good news? I think that my phone now is booting on Fastboot mode? I don´t know how but today it was recognized by the PC as:
MTP USB Device
Please help What I can do to flash my phone¿? it is fastboot mode right? in fastboot mode I can do flash without an account authenticated righT?
Im trying to use Mi Flash TOOL again and Im getting this message:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Im using the latest rom for the K20 global phone but dont know why it is stuck with that message and STATUS: Flashing but it doesnt do any progress.
What Can I do?? is ok MTP USB Device? is that the correct drivers to do a flash in fastboot mode??
Thanks guys!
Click to expand...
Click to collapse
Does the phone display the fastboot logo? If it does, then you have to remove some lines from the flash_all.bat file. The first ones where it says something about getvar product.

you can fastboot and just push it in cmd if fastboot active. I bever use bat files, because its only 2 lines to flash

yaro666 said:
you can fastboot and just push it in cmd if fastboot active. I bever use bat files, because its only 2 lines to flash
Click to expand...
Click to collapse
This is what happened:
I was watching my phone recognized as MTP USB Device and I tought yeah! my luck is from my side! now will be possible to flash my pohne in fastboot mode !!
I tried a lot of times with FLASH TOOL and it never passed from:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
then I tried in adb: "adb devices" but I never saw my device connected even with MTP USB Device driver activated in Device Manager.
so I tried anyway to use the flash_all.bat and same message received "getvar anti" bla bla..
I never deleted the lines about getvar from the file "flash_all.bat" because now my phone it is exactly as in the begin....
Now the PC doesn't want to recognize the phone... again the same ****.. " USB Device Unknown (Descriptor Request Failed) "
I did the test point and the same crap... the phone doesn't want to be recognized USB Unknown...
Come on... I can't believe it... I had decided to pay for the service flash with EDL authentication in the next week and now I can't even make it boot in EDL... exactly as in the begin I'm.... the phone it is with the same sympthoms.. :crying:
EDITED:
Now the Phone was recognized by the PC again as: MTP USB Device but with yellow sign..
I disconnected, reconnected the cable and nothing yellow sign.
I did the test point and boom Im back again into the same ****... USB UNknown (Descriptor Request Failed)
what the **** is happening?? Im not so sure how the phone can be recognized as MTP USB Device but i guess that it is fastboot mode. and that is what I want to try the solution from the first post of this threads.
or the second solution understand what I have to do to put the phone into EDL. Because I did a lot of times with sucess at the begin and now Im doing exactly the same and nothing. it doesnt want to work.
Looks like drivers problem?

romeosantos said:
This is what happened:
I was watching my phone recognized as MTP USB Device and I tought yeah! my luck is from my side! now will be possible to flash my pohne in fastboot mode !!
I tried a lot of times with FLASH TOOL and it never passed from:
fed4e139]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s fed4e139 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
then I tried in adb: "adb devices" but I never saw my device connected even with MTP USB Device driver activated in Device Manager.
so I tried anyway to use the flash_all.bat and same message received "getvar anti" bla bla..
I never deleted the lines about getvar from the file "flash_all.bat" because now my phone it is exactly as in the begin....
Now the PC doesn't want to recognize the phone... again the same ****.. " USB Device Unknown (Descriptor Request Failed) "
I did the test point and the same crap... the phone doesn't want to be recognized USB Unknown...
Come on... I can't believe it... I had decided to pay for the service flash with EDL authentication in the next week and now I can't even make it boot in EDL... exactly as in the begin I'm.... the phone it is with the same sympthoms.. :crying:
EDITED:
Now the Phone was recognized by the PC again as: MTP USB Device but with yellow sign..
I disconnected, reconnected the cable and nothing yellow sign.
I did the test point and boom Im back again into the same ****... USB UNknown (Descriptor Request Failed)
what the **** is happening?? Im not so sure how the phone can be recognized as MTP USB Device but i guess that it is fastboot mode. and that is what I want to try the solution from the first post of this threads.
or the second solution understand what I have to do to put the phone into EDL. Because I did a lot of times with sucess at the begin and now Im doing exactly the same and nothing. it doesnt want to work.
Looks like drivers problem?
Click to expand...
Click to collapse
Most likely. I had similar issues with a rn7. Try it on another pc. I had issues getting the phone recognized in w10, then I switched to an old laptop I had with w7. Didn't install drivers, didn't do anything, windows installed it's driver and the phone was there. So it may be a issue with your OS. And again, delete the first two lines from the flash_all.bat to get over that error.
Edit: The flashing with MiFlash tool will only work if you see the fastboot logo on your phone. If the phone is seen in cmd after you type "fastboot devices".

attitude12 said:
Most likely. I had similar issues with a rn7. Try it on another pc. I had issues getting the phone recognized in w10, then I switched to an old laptop I had with w7. Didn't install drivers, didn't do anything, windows installed it's driver and the phone was there. So it may be a issue with your OS. And again, delete the first two lines from the flash_all.bat to get over that error.
Edit: The flashing with MiFlash tool will only work if you see the fastboot logo on your phone. If the phone is seen in cmd after you type "fastboot devices".
Click to expand...
Click to collapse
Thanks for the answer, I have the notebook with two windows.
W10 64 bits and W7 32 Bits.
Same problem in both, don't know how can be driver problem, because I installed exactly the correct versión. (I know that is the correct because I could do the test point correctly two days ago) and it was recognized as: "Qualcomm HS-USB QDloader 9008 (COM4)" But today it doesnt want to recognize anymore the phone. Only "USB Device Unknown (Descriptor Request Failed)"
So hard is to make it boot in EDL mode? i saw the picture for test point (k20 xiaomi) and it is really easy. but PC recognize the phone as Unkonwn after test point. The first day that I did the test point happened the same ****.. I was hours and hours trying to make it work.. till I installed the correct drivers. and now is happening the same.. hours and hours trying to boot in EDL and using the same drivers, same process, but nothing.
Except at 3:00 pm dont know how the phone was recognized as MTP USB Device (with yellow sign error in device manager) so i did again the test point and boom.. USB Unknown again...
If I press Power button + volume up the phone looks like turn off and instantly I do the connection from usb cable and nothing appears in device manager but 2 mins or 3 mins later the phone is recognized as unknown and blue led light start to blink every 1 second.
If i do the test point it is recognized instantly as Unknown but there isnt any blue led light blinking.
I tried test point without battery and same. problem.. I tried to do the test point without release the pins so fast.. and same problem I tried releasing fast.. slow... etc
I tried to removed the battery and press power button to drain all the energy from board.
I tried to charging battery with power supply and the blue led light is turned on after 2 mins and it continue on over 10 or 15 mins then it is off the blue light. I used a tester to see the voltage from battery and is ok looks like it is full of charge.
If I do the EDL Cable could it be different? or is the same as test point?
Thanks for your help guys you are good people!

Have you tried with Linux? With the distribution I mentioned?

Gimlouuuu said:
Have you tried with Linux? With the distribution I mentioned?
Click to expand...
Click to collapse
Hi! Thanks for your help.
The problem was the usb cable. Now works perfectly with a new cable. But now I have to unbrick it hahaha

romeosantos said:
Hi! Thanks for your help.
The problem was the usb cable. Now works perfectly with a new cable. But now I have to unbrick it hahaha
Click to expand...
Click to collapse
great, good news. To unlock it, go back at my first message.

Gimlouuuu said:
great, good news. To unlock it, go back at my first message.
Click to expand...
Click to collapse
Hi! Thanks! Yes I tried to flash in fastboot mode. I did adb devices command and it was recognized ok.
But when I tried to flash_all.bat it gave me error: "bootloader locked" looks like I need the bootloader unlocked to flash via ADB in fastboot mode.
what I want to try is like a bug in xiaomi mi flash tool. The first time that I tried to use it. I made a new account and I received a message like:
"Logged Suscessfull"
"Your Account was blind to this PC. Now you can start the process"
Then I received an error like "no root permission" or something like that (maybe was because the usb cable was bad)
Looks like the xiaomi flash tool passed the EDL Authentication. because now each time that Im trying to use MI TOOL this is the message that Im getting.
"Logged Sucessfull"
You are not authorized for this operation

romeosantos said:
Hi! Thanks! Yes I tried to flash in fastboot mode. I did adb devices command and it was recognized ok.
But when I tried to flash_all.bat it gave me error: "bootloader locked" looks like I need the bootloader unlocked to flash via ADB in fastboot mode.
what I want to try is like a bug in xiaomi mi flash tool. The first time that I tried to use it. I made a new account and I received a message like:
"Logged Suscessfull"
"Your Account was blind to this PC. Now you can start the process"
Then I received an error like "no root permission" or something like that (maybe was because the usb cable was bad)
Looks like the xiaomi flash tool passed the EDL Authentication. because now each time that Im trying to use MI TOOL this is the message that Im getting.
"Logged Sucessfull"
You are not authorized for this operation
Click to expand...
Click to collapse
Ok, suddenly you can not reinstall via all these methods because your bootloader is locked... Have you tried asking a member here if anyone has an EDL account (a real haha) ?