Database Develop

[Q] HELP: Stuck in bootloader or no USB

Hi All,
from one moment to another my X1 decided to boot into bootloader mode.
The strange thing is however, that when I connect it to the USB of my PC and reset the X1, it boots normally. Well, almost normal as the USB doesn't seem to be working.
I flashed the rom to APP-SW_X1_GENERIC_UK_1213-6450_R3AA010__KOVS using the SDCard and that worked without a problem. But still the X1 boots into bootloader mode (except when connected to the PC).
I tried a hardreset, pressed the volume down button several times (to make sure it isn't stuck), tried to use MTTY (but that doesn't show a prompt), but nothing seems to help.
Is there anyone who can help me with this, because I'm out of ideas....
Update:
I managed to boot the OS (USB connected) and install HSPL using Xperia-SSPL-Manual. This succeeded and I now have SPL-0.78.OliNext. I flashed the phone to a new ROM (826x_KOVSKY_29017_2021), and that succeeded as well. It didn't solve my problem however. I still get the bootloader screen when I start the phone and can only start the OS by starting with USB connected...
Update2:
Yesterday evening I took the whole phone apart to make sure no buttons are/were stuck. Didn't find anything, put it back together and it still boots into bootloader.
I also managed to get a connection to the phone using NueTTY. I executed command Set 14 0, restarted the phone...and still it boots into bootloader.
If there is any one who knows of something that I haven't tried yet, PLEASE let me know....

same problem,,if there's a way to flash recovery from sd card in fastboot mode,,that'd be great

kldahmd said:
same problem,,if there's a way to flash recovery from sd card in fastboot mode,,that'd be great
Click to expand...
Click to collapse
Flashing the ROM is no problem, I can put every ROM on it that I like. But even after flashing the ROM the phone still starts in bootloader....

You can try to go into the bootloader on ur pc and use recovery.bat with fastboot.

xvink said:
Flashing the ROM is no problem, I can put every ROM on it that I like. But even after flashing the ROM the phone still starts in bootloader....
Click to expand...
Click to collapse
hi, I'm kind of having the same issue as you do..can you please be of help and tell me how did you manage to HSPL it to 0.78.OliNex?
Correct me If I am wrong, but you must copy Xpera_SSPL_Manual. exe on X1, run it from file explorer and then run X1_HardSPL.exe on your PC, whlie X1 is connected via usb (although mine also doesn't recognize the X1) ?
i would really apreciate it... thnx

i have the same problem guys, did anyone of you found any solution for this?

same problem
Have you tried to do a task29 with KovskyAdvancedRUU?

need help badly for my frp locked note 5 sm-n920p

so i rooted my note 5 sm-n920p phone using odin to flash everything i even had twrp flashed to it. the phone worked properly for months then one day i ended up switching off oem unlock forgetting it would trigger my frp lock if my phone had died well my phone died and when i went to turn it back on i got stuck in the frp boot loop i can get it into odin mode but it will not go into twrp recovery mode at all. i know how to flash the stock firmware to my phone but my problem is i cannot get any computer to recognize my phone it says one of the useb devices attatched to this computer has malfunctioned and windows does not recognize it. ive tried everything from uninstalling my usb drivers and reinstalling them and manually installing samsung android adb interface directly to the unkown device. odin will not pick up my phone and add it for me to flash it back to stock and factory reset it im willing to lose all my data i just want my phone to be able to work. if there is anyone with any advice or is willing to assist me to get my phone back to a proper working state id really appreciate it. also i am not sure if i even need the computer to recognize my phone not sure if i just need to keep trying different versions of odin but i know that my cable isnt the problem because ive tried it with my other note 5 and it works ive tried multiple cables with the frp boot looped phone that i have and i cant seem to figure it out why odin wont pick it up. as far as i know usb debugging is on and oem unlock is disabled on my frp locked note 5 please someone help me.

Right...
I'm going through the exact same thing right now. In all of the guides right now, it seems like theres always something that doesn't work out with our specific phone... lame sauce tbh.
xjackgimleyx said:
so i rooted my note 5 sm-n920p phone using odin to flash everything i even had twrp flashed to it. the phone worked properly for months then one day i ended up switching off oem unlock forgetting it would trigger my frp lock if my phone had died well my phone died and when i went to turn it back on i got stuck in the frp boot loop i can get it into odin mode but it will not go into twrp recovery mode at all. i know how to flash the stock firmware to my phone but my problem is i cannot get any computer to recognize my phone it says one of the useb devices attatched to this computer has malfunctioned and windows does not recognize it. ive tried everything from uninstalling my usb drivers and reinstalling them and manually installing samsung android adb interface directly to the unkown device. odin will not pick up my phone and add it for me to flash it back to stock and factory reset it im willing to lose all my data i just want my phone to be able to work. if there is anyone with any advice or is willing to assist me to get my phone back to a proper working state id really appreciate it. also i am not sure if i even need the computer to recognize my phone not sure if i just need to keep trying different versions of odin but i know that my cable isnt the problem because ive tried it with my other note 5 and it works ive tried multiple cables with the frp boot looped phone that i have and i cant seem to figure it out why odin wont pick it up. as far as i know usb debugging is on and oem unlock is disabled on my frp locked note 5 please someone help me.
Click to expand...
Click to collapse

NEVER let your phone die. Charge immediately if battery goes to 15%. You need a charged battery to do any flashing so yeah, you may need to replace or charge the battery to flash a 4 file firmware.

Phone bricked, need help :c

Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?

after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.

Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.

FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).

[HELP]My lg l90 does not connect to the pc in dowloand mode

First of all sorry for my bad English, I'm not very good
well ... what happens is that I was trying to partition my memory. witch this https://forum.xda-developers.com/lg-l90/orig-development/hack-partition-table-tool-lg-l90really-t2946323
but at the time of reinstalling the system again, I lost the twrp
I tried to see what to do, but to install twrp I needed to go back to the original rom of the cell phone. when connecting the phone to the PC in dowload mode I only see an error with the dirver "mtp"
I reinstalled everything, I already did everything but my cell phone does not connect to the PC
I do not know what to do, I do not have recovery twrp, I can not go back to the origianl rom, nor can I root the phone because it has slimrom installed now
I really need you to help

Josu0545 said:
First of all sorry for my bad English, I'm not very good
well ... what happens is that I was trying to partition my memory. witch this https://forum.xda-developers.com/lg...ck-partition-table-tool-lg-l90really-t2946323
but at the time of reinstalling the system again, I lost the twrp
I tried to see what to do, but to install twrp I needed to go back to the original rom of the cell phone. when connecting the phone to the PC in dowload mode I only see an error with the dirver "mtp"
I reinstalled everything, I already did everything but my cell phone does not connect to the PC
I do not know what to do, I do not have recovery twrp, I can not go back to the origianl rom, nor can I root the phone because it has slimrom installed now
I really need you to help
Click to expand...
Click to collapse
Which variant of the device do you have and can you be more specific with what error there was with the driver.

Loosing connection as soon as Fastboot starts

Hi
After googleing a lot and trying at least 1001 ADB and Fastboot-tutorials I still am stuck. I only want to flash my A2 with stock ROM, but as soon as fastboot kicks in the connection stops.
My phone is unstable (how? see below) but not bricked! I can ...
... access recovery mode and fastboot anytime
... establish data and PTP connections to my PC (Win 10)
... use it normally (apps, WLAN ...) as long as flight mode is on!!!!! :cyclops:
... connect the phone with XiaoMi Tool V2 to my PC
but as soon as fastboot kicks in I loose connection.
Meanwhile I'm out of ideas how to establish fastboot-connection.
Here's the reason I want to flash - in case it matters: After an Andorid update (or at least it seems this is the reason) the screen started to unlock/lock erratically. There never was enough time to enter the code, so I made a factory reset. The problem still prevails, but without screenlock (and looooots of patience) I can access my phone. Debugging and bootloader are turned on now. The only way to stop this screenlock/unlock behavior is to turn on flight mode ...
If the phone is connected to a PC I can hear the "unplug sound" as soon as fastboot starts and XiaoMi Tool V2 looses connection.
BTW: Even with many attempts I never managed to establish a connection to Mi PC suite.
And the USB-connection-preferences very often turn to "no data connection". To fix this I usually have to plug out/in or even change USBport or even the computer.
What should I try to flash mi Mi A2?
Thanks and greetings
Phillip

Philipp_P said:
Hi
After googling a lot and trying at least 1001 ADB and Fastboot-tutorials I still am stuck. I only want to flash my A2 with stock ROM, but as soon as fastboot kicks in the connection stops
My phone is unstable (how? see below) but not bricked! I can ...
... access recovery mode and fastboot anytime
... establish data and PTP connectios to my PC (Win 10)
... use it normally (apps, WLAN ...) as long as flight mode ist on!!!!! :cyclops:
... connect the phone with XiaoMi Tool V2 to me PC
but as soon as fasstboot kicks in I loose connection.
Meanwhile I'm out of Ideas how to establish fastboot-connection.
Here's the reason I want to flash - in case it matters: After an Andorid update (or at least it seams this is the reason) the screen startet to unlock/lock erratically. There never was enoug time to enter the code, so I made a factory reset. The problem still prevails, but without screenlock (and looots of patience) I can access my phone. Debugging and bootloader are turned on. The only way to stop this behaviour ist to turn on Flight Mode ...
If the phone ist connected to a PC I can hear the "unplug sound" as soon as fastbot starts and XiaoMi looses connection.
BTW: Even with many atempts I never managed to estabilsh a connection to Mi PC suite.
And the USB-Connection-Pfreferences very often turn to "no data connection". To fix this I usually have to plug out/in or even change USBport or even the computer (-> Win -Laptop)t! Whith no result.
What should I try to flash mi Mi A2?
Thanks and greetings
Phillip
Click to expand...
Click to collapse
Sounds strange . Does RIL work ? Like gsm and sim card ...anyway you need to buy a screwdriver from Amazon or Wish or Whereever and open your phone ..
Search for tutorial videos on youtube on " test point " . You will short the phone forcing it into edl ( deep flash ) mode . In edl you don't use fastboot but rather qualcomm 9008 drivers .
You can flash stock rom with QPST ( Qualcomm flash tool ) or just the regular Miflash from Xiaomi .
In any case ..UNINSTALL ALL I SAY ALL the stuff you have installed on your pc right now including adb .Reboot .Install Qualcomm 9008 drivers .Then download the LATEST VERY NEWEST version of Miflash that comes with drivers ..follow the instructions to install drivers and Mifash itself .
Then follow video tut to enter edl state with test point
VERY IMPORTANT HAVE MIFLASH PREPARED to flash very soon as in 1 or 2 minutes after you enter edl because there is a timeout after which you will get errors and would have to do the test point again ...
Good luck ..if the phone is stolen or contains stolen parts or you used some bypass to enter it to bypass lock screen once it connects to internet or gsm the troubles will most probably return ..if it was or is just some glitch this will solve it .

Thanks for your help!
I’m not familiar to what RIL is all about. I just googled it, and I guess it works. I can receive SMS when flight mode is turned off and I get a 4G-connection. I can’t do phone calls, but that’s due to the screenlock-problem as soon as flight mode is turned off. I can’t even enter a phone number then … :silly:
I never heard of edl before but found videos. I’ll give it a try. Thanks for all your tips, especially about the edl-timeout. :good:
One last question before I start regarding the uninstalling of EVERYTHING … How can I be sure, I got rid of EVERYTHING? Windows program uninstall showed be "Mi PC Suite", "Universal ADB driver" and "Windows driver package Android USB device class …" I uninstalled all of it.
But I also used Minimal ADB/fastboot and XiaoMi Tool V2 (and probably other stuff I don’t remember anymore) as portable versions. I can delete those fodlers, but is that really enough regarding the drivers that were installed?

Philipp_P said:
Thanks for your help!
I’m not familiar to what RIL is all about. I just googled it, and I guess it works. I can receive SMS when flight mode is turned off and I get a 4G-connection. I can’t do phone calls, but that’s due to the screenlock-problem as soon as flight mode is turned off. I can’t even enter a phone number then … :silly:
I never heard of edl before but found videos. I’ll give it a try. Thanks for all your tips, especially about the edl-timeout. :good:
One last question before I start regarding the uninstalling of EVERYTHING … How can I be sure, I got rid of EVERYTHING? Windows program uninstall showed be "Mi PC Suite", "Universal ADB driver" and "Windows driver package Android USB device class …" I uninstalled all of it.
But I also used Minimal ADB/fastboot and XiaoMi Tool V2 (and probably other stuff I don’t remember anymore) as portable versions. I can delete those fodlers, but is that really enough regarding the drivers that were installed?
Click to expand...
Click to collapse
sure for the portables just delete the folders

Giving up
Screwdrivers arrived, disassembling the phone was surprisingly easy. Actually hitting the tinytiny EDL-contacts was surprisingly difficult on the other hand. :silly: But I managed. But also with EDL my computer pretends my mobile doesn’t exist when plugged in. I guess there must be a hardware-problem somewhere. A this point I give up and buy another one. Thanks for your support, KevMetal.

Philipp_P said:
Screwdrivers arrived, disassembling the phone was surprisingly easy. Actually hitting the tinytiny EDL-contacts was surprisingly difficult on the other hand. :silly: But I managed. But also with EDL my computer pretends my mobile doesn’t exist when plugged in. I guess there must be a hardware-problem somewhere. A this point I give up and buy another one. Thanks for your support, KevMetal.
Click to expand...
Click to collapse
Sorry didn't work friend. Are you sure ? Did you remember to install Qualcomm 9008 drivers from Qualcomm ? Remembering to disable driver verification on windows 10 ...try just more time ...who knows ..

I used a computer with windows 7, because I found on the internet that there are less problems than with Win 10 …