When I try to flash ROM or recovery via fasboot on my phone mi 9 lite my phone exit fastboot by itself and disconnected from PC I have tried many things like try another cable or use other PC or even install older windows' versions but no luck at all and I really don't know the problem.. it always exit and shutdown when I try to do anything via fastboot..
xshad0w said:
When I try to flash ROM or recovery via fasboot on my phone mi 9 lite my phone exit fastboot by itself and disconnected from PC I have tried many things like try another cable or use other PC or even install older windows' versions but no luck at all and I really don't know the problem.. it always exit and shutdown when I try to do anything via fastboot..
Click to expand...
Click to collapse
In caserocedure
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
I had this problem and after trying everything, changing pc it worked the first time.
(problem with certain versions of windows and processors, AMD, INTEL).
Related
Hi guys,
I accidentally formatted /system on my T with UB.
Now it won't start (it says "Sony", then nothing happens). It now has no recovery and if I connect the phone in fastboot or flashmode, the usual PC I use to flash says me that "Sony ADB interface" is connected, but it can't find any driver.
What can I do now?
Thanks in advance for the reply.
DS-1 said:
Hi guys,
I accidentally formatted /system on my T with UB.
Now it won't start (it says "Sony", then nothing happens). It now has no recovery and if I connect the phone in fastboot or flashmode, the usual PC I use to flash says me that "Sony ADB interface" is connected, but it can't find any driver.
What can I do now?
Thanks in advance for the reply.
Click to expand...
Click to collapse
If it says "Sony ADB interface" when you connect it, then you don't need a driver, it's already installed (you can confirm this if you open Device Manager in Windows and check if it's listed as an "ADB interface" and there are no "Unknown Devices" and/or devices named in relation to your phone that have a yellow exclamation mark.
Just flash a stock FTF, or download one of the kernels for T that have a recovery, and flash any ROM you like.
First of all, thanks for the reply.
The strange thing about this time brick is that my pc doesn't recognize the phone. Other times, infact, I used it with the same phone to relive the Xperia T, after strange things happened.
Instead, this time the phone is recognized as "Sony ADB interface" and the pc says there's no driver in it. And it can't find in the system (I'm using an old laptop with Windows XP on it).
That's the reason why the system (and Flashtool, too: it says, in red, that I need to install the drivers for my phone) doesn't recognize the phone.
Now I'm trying the T into another Windows XP old laptop system...I hope it works (and I hope USB 1.1 will be fine, too...).
EDIT: this "new" pc see my phone, connected in fastboot mode, as "SEMC Flash Device" and it is installing the drivers. I've already installed fastboot/flashmode drivers from Flashtool Drivers folder.
RE-EDIT: PC can see the Xperia T, but Flashtool always says that it is connected in "flash mode", even if I connect it in fastboot mode. What should I do, now?
RE-RE-EDIT: The phone is recognized only in flashmode, even if I installed all the drivers. I'm trying to flash .141 and it seems to work. Let's see what happens.
Antiga Prime said:
If it says "Sony ADB interface" when you connect it, then you don't need a driver, it's already installed (you can confirm this if you open Device Manager in Windows and check if it's listed as an "ADB interface" and there are no "Unknown Devices" and/or devices named in relation to your phone that have a yellow exclamation mark.
Just flash a stock FTF, or download one of the kernels for T that have a recovery, and flash any ROM you like.
Click to expand...
Click to collapse
DS-1 said:
First of all, thanks for the reply.
The strange thing about this time brick is that my pc doesn't recognize the phone. Other times, infact, I used it with the same phone to relive the Xperia T, after strange things happened.
Instead, this time the phone is recognized as "Sony ADB interface" and the pc says there's no driver in it. And it can't find in the system (I'm using an old laptop with Windows XP on it).
That's the reason why the system (and Flashtool, too: it says, in red, that I need to install the drivers for my phone) doesn't recognize the phone.
Now I'm trying the T into another Windows XP old laptop system...I hope it works (and I hope USB 1.1 will be fine, too...).
EDIT: this "new" pc see my phone, connected in fastboot mode, as "SEMC Flash Device" and it is installing the drivers. I've already installed fastboot/flashmode drivers from Flashtool Drivers folder.
RE-EDIT: PC can see the Xperia T, but Flashtool always says that it is connected in "flash mode", even if I connect it in fastboot mode. What should I do, now?
Click to expand...
Click to collapse
Ok, well, no idea about it being stuck in flash mode, but, isn't that exactly what you want? To flash a stock FTF you need to be in flash mode. As a matter of fact, you can even flash only the kernel of an FTF in flash mode, it wouldn't have a recovery, since it would be a stock kernel, but at least you could get a working kernel, if that were the issue, which it is not.
What are you doing to put your phone into fastboot mode?
I wanted to use fastboot to flash a kernel with recovery and then flash the backup of my old ROM.
However, it doesn't worked. Only flashmode worked. So I flashed (really slowly, because of USB 1.1 ports of this old IBM laptop!) .141 and now the phone is living again.
Dunno why fastboot didn't work. Maybe because there wasn't any firmware on?
Antiga Prime said:
Ok, well, no idea about it being stuck in flash mode, but, isn't that exactly what you want? To flash a stock FTF you need to be in flash mode. As a matter of fact, you can even flash only the kernel of an FTF in flash mode, it wouldn't have a recovery, since it would be a stock kernel, but at least you could get a working kernel, if that were the issue, which it is not.
What are you doing to put your phone into fastboot mode?
Click to expand...
Click to collapse
DS-1 said:
Dunno why fastboot didn't work. Maybe because there wasn't any firmware on?
Click to expand...
Click to collapse
No because the whole point of fastboot mode is to be able to flash firmware related files. Fastboot mode, just as Flash mode, starts before the Android OS starts. If they depended on there being an OS installed it would defeat the whole point.
So I really dunno why it didn't work. Later I'll try to see if now fastboot is working again.
Antiga Prime said:
No because the whole point of fastboot mode is to be able to flash firmware related files. Fastboot mode, just as Flash mode, starts before the Android OS starts. If they depended on there being an OS installed it would defeat the whole point.
Click to expand...
Click to collapse
When you don't have a ROM installed,stock kernels recovery won't work. Flash CM 11s Kernel, you'll have recovery then restore you're backup
Hi,
Today i bricked/hard bricked my X620. I had TWRP 3.0.x, but i decide to flash with 3.1.x. I made it through by commands in windows using twrp.img file, and finished with fastboot reboot command, and phone died. Last info was something with the flow. I read many threads, and i found, that it's not alowd to finish flashing with this command. Now, im not able to switch on my phone, enter fastboot or TWRP, and when i conect my phone to pc, red light apears and i can hear a sound i win7 that something has been connected to pc, and disconnect, and connected, disconnected ...................., and nothing i happening with the phone. So, i'm not able to connect my phone to pc to make new flash by flash tool.
Can somebody help me with this problem????
Q
I can help you, just visit my blog
tickernel.tk
Present status
QbaQbaPL said:
Hi,
Today i bricked/hard bricked my X620. I had TWRP 3.0.x, but i decide to flash with 3.1.x. I made it through by commands in windows using twrp.img file, and finished with fastboot reboot command, and phone died. Last info was something with the flow. I read many threads, and i found, that it's not alowd to finish flashing with this command. Now, im not able to switch on my phone, enter fastboot or TWRP, and when i conect my phone to pc, red light apears and i can hear a sound i win7 that something has been connected to pc, and disconnect, and connected, disconnected ...................., and nothing i happening with the phone. So, i'm not able to connect my phone to pc to make new flash by flash tool.
Can somebody help me with this problem????
Q
Click to expand...
Click to collapse
Is it solved? I am also facing same problem.
BiswashKoirala said:
Is it solved? I am also facing same problem.
Click to expand...
Click to collapse
I am facing the same problem as well. Can anybody help pls??
No..I tried few solutions but the phone was still dead. So I bought a new phone.
Is there a way to flash to the stock ROM without booting into fastboot?
I cant recognize my device through fastboot. Tried in 2 pcs, and a MAC. (Yes, I installed the drivers).
CamposMIC said:
Is there a way to flash to the stock ROM without booting into fastboot?
I cant recognize my device through fastboot. Tried in 2 pcs, and a MAC. (Yes, I installed the drivers).
Click to expand...
Click to collapse
Did you use USB 2 or USB 3? With USB 3 there a some problems sometimes.
bavmouse said:
Did you use USB 2 or USB 3? With USB 3 there a some problems sometimes.
Click to expand...
Click to collapse
Used both.
For example: The device is recognized by miflash when it is on. When I boot to fastboot, it dont recognize.
Lool i was here looking for a solution and a find one, i wanted to revert to stock but my phone wasnt bricked and i wanted to enter edl mode but my pc dont recognize, i tried a lot of thing and i came up with the idea of disable USB debuggin, i didnt think it was gonna work but i tried and now my pc recognizes my phone and i can enter to edl. PD: Sorry for my english
hello :cyclops:,
i bricked my phone, so i want to restore it using fastboot mode; the thing is that the pc doesnt detect it (the phone is charging but not connected), so i cannot flash anything;
the phone is bricked, so i can only get it to enter fastboot mode, and i've tried different usb cables, ports and even different pcs;
my last option is changing the usb board, but i was looking for any other ideas before doing that... thanks in advance
TRy install Fastboot package ROM with XiaoMiFlash.exe...
https://c.mi.com/oc/miuidownload/detail?guide=2
// ou, pc doesnt detect it
jojovrtak said:
TRy install Fastboot package ROM with XiaoMiFlash.exe...
https://c.mi.com/oc/miuidownload/detail?guide=2
// ou, pc doesnt detect it
Click to expand...
Click to collapse
dont worry, i end up solving it by trying even more cables
I use Mi 9 Transparent Edition (Ram version 12G Rom 256G) unlocked bootloader. I installed the EU rom, it's ok to use. After I locked the bootloader, it was been hard brick and i had to flash a china rom via EDL mode. I want to install global rom but in fastboot mode the computer doesn't recognize it anymore, tried everything, changed many computers still won't recognize Mi 9 in fastboot mode, so there's no way to reinstall the rom.
Please help: now how to get Mi 9 back in fastboot mode? Please help guys (
p/s : it's also lost fast charging...
WValley said:
I use Mi 9 Transparent Edition (Ram version 12G Rom 256G) unlocked bootloader. I installed the EU rom, it's ok to use. After I locked the bootloader, it was been hard brick and i had to flash a china rom via EDL mode. I want to install global rom but in fastboot mode the computer doesn't recognize it anymore, tried everything, changed many computers still won't recognize Mi 9 in fastboot mode, so there's no way to reinstall the rom.
Please help: now how to get Mi 9 back in fastboot mode? Please help guys (
p/s : it's also lost fast charging...
Click to expand...
Click to collapse
maybe is the usb cable, try with other
Naet said:
maybe is the usb cable, try with other
Click to expand...
Click to collapse
thank u very much for the answer
i tried an original cable, not working
i turn on usb debugging, oem and update the lastest driver but still not working
Head over to Device Manager, and check if your device is correctly recognized.
if your device is categorized under 'Other Devices' and has yellow triangle, then you have to install fastboot driver.
download generic usb driver below.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
after unzipping downloaded file, right click 'android_winusb.nif' file inside 'usb_driver' folder and install it.
back to the 'device manager', locate your device and right click it, and choose 'update driver'.
select 'Search driver from my Computer' - 'Select from available driver list' - find 'Android Device' from the list and select next - select 'Android ADB Interface' and select next - click yes to proceed
and voila! you successfully installed fastboot driver, your device should be recognized as Android Device and good to go.