Having issue running into fastboot mode, my PC detects it as fastboot, but doesn't see my phone. Nothing i can do so i guess it's driver issues. I have BL unlocked, my pc companion says everything is up to date. Installed newest version of flashtool (and the drivers ofc) dunno what else should i try :\ Windows 7 btw..
Got the message driver installed successfully now, but still my PC wont detect device even in CMD with ADB on, i get note no device connected when i check adb devices :\ Was long time a go since i installed ADB (was total newb then) , could it be something with ADB drivers?
USB debug mode enabled in your phone settings ?
arturiu said:
USB debug mode enabled in your phone settings ?
Click to expand...
Click to collapse
yup
Have you installed adb drivers?
Sent from my ST18i
Really pissing me off coz i cant root coz of this
Guynan said:
Have you installed adb drivers?
Sent from my ST18i
Click to expand...
Click to collapse
yes
Go and install flash tool and there is a drivers folder when it is installed and run the .exe. If you want to do anything to your xperia, flash tool is worth getting to know
Sent from my ST18i
Guynan said:
Go and install flash tool and there is a drivers folder when it is installed and run the .exe. If you want to do anything to your xperia, flash tool is worth getting to know
Sent from my ST18i
Click to expand...
Click to collapse
installed them :\ there aint no V drivers but installed tx/vl and flash/fast ofc..
Can't even flash now everytime i try to flash it gets aborted :\ didnt try to flash back to 4.1 stock tho could it be wrong firmwares? But anyway tried everything with drivers and nothing works to get my fastboot on :\
BakiSaN said:
Can't even flash now everytime i try to flash it gets aborted :\ didnt try to flash back to 4.1 stock tho could it be wrong firmwares? But anyway tried everything with drivers and nothing works to get my fastboot on :\
Click to expand...
Click to collapse
I somewhat doubt that, you are flashing new ones. Did you flash the wrong rom?
TBH i tried nordic, got error (flashing aborted), global-LTE same ****. Using unbranded Swedis firmware atm (all flashing done through flashtool, i had no problems at all when i flashed it 1st time). I'm not very experienced with flashing, but i guess the FWs i tired to flash should work?
Here are infos:
Phone software version: 1264-2336_9.2.A.0.295
generic-user
Customization Version: 1268-5895_R4J
Active Customization:1268-5895_R4J
S1 Boot version:1264-2289 R11A023
Not sure if i made some nubish mistake (in be4 i did ^_^) i guess i can only use this customization version? Also bootloader unlocked. I've even got note that windows installed fastboot drivers and my PC sees my phone as Sony SA0106 Adb interface driver, but only when plugged in normally, in fastboot my PC just doesn't want to detect my phone :\ Feeling so handicapped
BakiSaN said:
Can't even flash now everytime i try to flash it gets aborted :\ didnt try to flash back to 4.1 stock tho could it be wrong firmwares? But anyway tried everything with drivers and nothing works to get my fastboot on :\
Click to expand...
Click to collapse
No I doubt it, you are flashing a new firmware each time. You could try a 4.1 .ftf, but if a 4.3 doesn't work, I don't see what that is going to change. Unless of course your .ftf file is corrupt, in which case I would try another mirror. So I would definitely try downloading the .ftf again or check that the md5 sums match. Because the fact that flashtool aborts is quite puzzling unless you have done some serious damage. But I doubt that too if you flashed the correct rom. You could also try updating flashtool, you might have some incomplete packages(?)
Edit: Sorry, just realised I replied to your last post twice, I'll read this one now. xD
---------- Post added at 01:20 PM ---------- Previous post was at 01:06 PM ----------
BakiSaN said:
TBH i tried nordic, got error (flashing aborted), global-LTE same ****. Using unbranded Swedis firmware atm (all flashing done through flashtool, i had no problems at all when i flashed it 1st time). I'm not very experienced with flashing, but i guess the FWs i tired to flash should work?
Here are infos:
Phone software version: 1264-2336_9.2.A.0.295
generic-user
Customization Version: 1268-5895_R4J
Active Customization:1268-5895_R4J
S1 Boot version:1264-2289 R11A023
Not sure if i made some nubish mistake (in be4 i did ^_^) i guess i can only use this customization version? Also bootloader unlocked. I've even got note that windows installed fastboot drivers and my PC sees my phone as Sony SA0106 Adb interface driver, but only when plugged in normally, in fastboot my PC just doesn't want to detect my phone :\ Feeling so handicapped
Click to expand...
Click to collapse
Righto, so if your computer detects adb drivers, then in a terminal/command prompt, type 'adb devices' and you should get the response "List of devices: SA0106'. It sounds to me that it is nothing to do with the drivers or the images you flash. You could of course try flashing a rom in through adb and fastboot. Though as this is somewhat hard to do and flashtool should definitely fix it, I think it stil could be an issue with how you are flashing the images. So just to confirm, you select flashmode on the computer and when prompted, you put your phone in 'flashmode' as opposed to 'fastboot' mode? Because they are for quite different things, so I would check that the button that you are pushing to start flashing is in fact the one appropriate for what you are trying to do. Could you also copy in the log of what is happening when the flashing fails? I hope I can help you.
Also, I don't know if this will apply to your device, but are you in MTP or MSC mode? If this is applicable, you will find out in Settings>Xperia>Connectivity>Usb connection mode. Should be in MSC, but if you can't find it, don't worry. I don't have an Xperia V, you see.
I'll try uninstalling flashtool and installing it again today after work (have the latest version currently). Well one of the roms i DLed was definetly the correct one, coz i have it installed (it's a bit buggy so i wanned to try install some other FW). Luckily we might get .299 soon but anyway, my ADB won't detect my phone in fastboot, even when i try with adb devices i just get empty space it just won't detect it.Yeah ofc i went into flashmode for flashing Not sure about MSC/MTP mode really, i guess it has something to do with mass storage? Anyway flashing is least problem for me now, untill .299 comes out at least But this **** with PC not detecting my device as fastboot is killing me :\
MTP currently, shaould i change it to MSC?
Didn't work -_- dunno woot to do, reinstalled everything ADB drivers are installed can't get into bloody fast boot
Tried flashing the same FW i have flashed on my phone, afaik nothing has changed but i always get that aborted message now and just can't flash..
Okay, yes, you should definitely be in MSC mode as opposed to MTP. And when you flash firmwares, you are attempting to get into flashmode as opposed to fastboot. So just to check, you are holding down the volume down when your phone is off when plugging into your computer to begin flashing? And also could you just copy a bit of the log from when flashing fails please?
Now the nordic version worked for me, nothing changed i had the same error after switching to MSC yesterday... I think it was my PC having to much **** running at the momment of flashing or something :\ Will see if fastboot works later on today, flashing is still going on atm but i gotta run
You do have to be in MSC mode though for flashmode. Okay I'm glad that it worked. You should be able to root that now then, and just install CWM and quickly flash a rom haha. I hope I have helped.
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 all,
Not really sure where to post this, so firgured id put it under general questions. I am currently trying to flash android 4.2 to an Xperia Z1 thats currently running 4.4.4 kitkat. - Now feel i should mention at the start, that i am not particually brilliant with android, and am slowly learning the basics.
I am using a program called Flashtool, I have the file that I want to flash over (the 4.2) - I have also gone through the program to install all the drivers. ( I have installed all drivers as i didnt know what i needed and didnt need, and initially tried just installing the z1 drivers ) Flashtool picks up my phone, and tells me what its currently running, it also detects that what version of android i am currently running, but for some reason dosent pick up that ive tried to plug in my phone in flash mode.
The system detects when I start the phone in fastboot mode, but whenever I use Flashtools to try and connect my phone in flash mode, it just keeps asking me to connect the phone. ( I am using Z1 and the standard key is vol down whilst plugging it into the usb cable, however the l.e.d. flashes red and green quickly and then shuts off, cant even be sure that the problem is Flashtools, it might be that i havent put it into flashmode properly??)
any help would be brillant, feel free to contact me via the xda site, or via e-mail [email protected] -
This might be a particularly basic problem to somebody, its had me stumped for days, any help you could give would be massively appreciated,
cheers
Try Older version of flashtool or you are missing some drivers in flashtool folder is file with drivers and you need to check flashtool drivers and z1 drivers and firstly connect the phone and wait to install drivers and next turn off phone and hold vol down and connect without flashtool to install flashtmode drivers and at the end try to flash via flashtool.
If you are sure you have installed drivers correctly then kill any other process on your pc which use adb drivers like pc companion or airdroid etc. Or use other usb port. Or use other pc. Wrong thread though.
mosespl said:
Try Older version of flashtool or you are missing some drivers in flashtool folder is file with drivers and you need to check flashtool drivers and z1 drivers and firstly connect the phone and wait to install drivers and next turn off phone and hold vol down and connect without flashtool to install flashtmode drivers and at the end try to flash via flashtool.
Click to expand...
Click to collapse
Thanks, will try the older version of flashtool to see if that makes a difference, still not sure ive got the Z1 in flashmode though, isnt a light suppose to stay on, rather than blink once? Anyway thanks for the help, will update
dan34321 said:
Thanks, will try the older version of flashtool to see if that makes a difference, still not sure ive got the Z1 in flashmode though, isnt a light suppose to stay on, rather than blink once? Anyway thanks for the help, will update
Click to expand...
Click to collapse
Update: phone now knows its in flash mode, however flashtool gets stuck on 'proccessing loader'?
you have been brilliant so far? Any guesses?
cheers
Dan
dan34321 said:
Update: phone now knows its in flash mode, however flashtool gets stuck on 'proccessing loader'?
you have been brilliant so far? Any guesses?
cheers
Dan
Click to expand...
Click to collapse
Re-download Rom i have same situation and I downloaded room again and it works
SORTED - Thanks all, managed to root, but have a fresh problem
mosespl said:
Re-download Rom i have same situation and I downloaded room again and it works
Click to expand...
Click to collapse
Thanks all, have now successfully rooted the phone, unfortunately for me that has yielded more questions than answers loll,
Now that its rooted, its running 4.2.2 and I am wondering if there is a way of keeping root access, but flashing it back up to 4.4.?
Really grateful to everyone!!
dan34321 said:
Now that its rooted, its running 4.2.2 and I am wondering if there is a way of keeping root access, but flashing it back up to 4.4.?
Click to expand...
Click to collapse
Just Flash already rooted 4.4 rom on it, should work !
If you are afraid of losing apps backup them with Titanium !
Hey chaps,
I'm having a spot of trouble with Emma, I'm afraid.
I've followed the bootloader unlocking steps, the fastboot driver is where it ought to be.
My machine is displaying the phone when in flash mode as "SOMC Flash Device". Can't uninstall the drivers, can't update them with the fastboot driver as it's shown.
As a result, (assuming I haven't missed things or mixed it all up like a twat) Emma isn't identifying my phone. I'm connecting it in flash mode of course, I'm getting nothing.
Any ideas what could be the trouble?
what are you trying to do?
meaniez said:
what are you trying to do?
Click to expand...
Click to collapse
Flash a sony build
why are you using emma and not the Flashtool ?
Tried that too, connected in flash mode and keep getting errors.
At this point I'm thinking it's a driver issue, but for the life of me I can't fix it.
Really unsure where to go from here.
just some thoughts
1. try to download and install ADB driver if you haven't already.
2. try connecting the phone to a different usb port [sounds incredibly stupid, but it does work sometimes].
3. [assuming you're using windows] while the phone is connected, go to the device manager, look for phone [presumably under android device or sony] and uninstall the driver.
what kind of errors are you getting using the flashtool?
meaniez said:
just some thoughts
1. try to download and install ADB driver if you haven't already.
2. try connecting the phone to a different usb port [sounds incredibly stupid, but it does work sometimes].
3. [assuming you're using windows] while the phone is connected, go to the device manager, look for phone [presumably under android device or sony] and uninstall the driver.
what kind of errors are you getting using the flashtool?
Click to expand...
Click to collapse
3. Yeah I've done that. When it's connected in flash mode, it's detected as S1 Service (SOMC Flash Device). I'm fairly sure that's where the trouble lays, but everytime I try to uninstall the drivers to prepare installing the "correct" ones, the system hangs and I'm forced to hard reset.
Literally just says:
INFO - Checking header
INFO - Ending flash session
ERROR -
ERROR - Error flashing. Aborted
INFO - Device connected in flash mode
The drivers are there in the flashtool folder. Install the flashmode and fastboot mode drivers from there and then try connecting your phone into flashmode as a trial. If you see it connects, then proceed to flash the firmware
Sent from my D5833 using XDA Free mobile app
Could you please tell which sony build you are trying to flash?
I think you are flashing a wrong rom..
Alright I'm fairly convinced I'm just a dumbass. I haven't switched roms on a phone since my S3.
So far all I've done is unlock the bootloader, following the instructions from the sony dev video.
I've got a D5833, running 23.0.1.A.1.49 build. Doesn't seem to be any further updates OTA or through PC companion.
Flashtool and drivers are installed. ADB as well.
I haven't got CWM or anything running on it thus far, and I'm suspecting that that might be the problem.
Help a newbie, save the rainforest. <3
My phone unsuddenly bricked after I reboot my phone.Can't even boot into recovery cause Sony logo appear for a second and turned off.My phone even don't charge.I tried to flash stock rom via flashtool but phone not detected or after pressing vol down button nothing happened.I also tryed to use fastboot mode to flash boot.img but nothing happened though My phone can turn into fastboot mode.What should I do now?Senior XDA members please help.:crying:
Edit:how can i fix adb "device not found" issue?I installed all the necessary drivers but still not solved. Can't flash stock rom because vol down button not working but the button is fine.
Edit2:How can I fix adb driver issue that not recognizing my phone?
Problem solved!
Maybe died flash boot
Chum.zuizui said:
Maybe died flash boot
Click to expand...
Click to collapse
So is that mean my phone hard bricked?
Røbin said:
So is that mean my phone hard bricked?
Click to expand...
Click to collapse
Yes.i think so
Chum.zuizui said:
Yes.i think so
Click to expand...
Click to collapse
I don't think so because this happened to me long ago when I tried to unlock bootloader.But I did something to the driver to work adb properly and it worked.And now I forgot that method and couldn't find in google also.So I'm really in big trouble.I just don't know why when I want to flash the stock rom and flashtool show in popup to power off the phone and press vol down button and connect to computer using usb cable but vol button don't work or not give any signal to computer.So I can't flash the rom.
Go to sony official site and download drivers.. ZR drivers dont exist but you can use drivers for Z, install those on your computer and use the fastboot method again and you should be fine.. Your phone is only soft bricked.. Hard brick is when there are absolutely no life in the phone at all.. Use a boot.img you know will work and no need to flash stock ROM once you're in recovery.. Unless you want to of course.. Custom ROM will boot your phone just fine
Also take your battery out and re-insert to make sure your phone is properly off.. Flashtool should also work after that
Røbin said:
I don't think so because this happened to me long ago when I tried to unlock bootloader.But I did something to the driver to work adb properly and it worked.And now I forgot that method and couldn't find in google also.So I'm really in big trouble.I just don't know why when I want to flash the stock rom and flashtool show in popup to power off the phone and press vol down button and connect to computer using usb cable but vol button don't work or not give any signal to computer.So I can't flash the rom.
Click to expand...
Click to collapse
Yes.good luck for you
hagar006 said:
Go to sony official site and download drivers.. ZR drivers dont exist but you can use drivers for Z, install those on your computer and use the fastboot method again and you should be fine.. Your phone is only soft bricked.. Hard brick is when there are absolutely no life in the phone at all.. Use a boot.img you know will work and no need to flash stock ROM once you're in recovery.. Unless you want to of course.. Custom ROM will boot your phone just fine
Also take your battery out and re-insert to make sure your phone is properly off.. Flashtool should also work after that
Click to expand...
Click to collapse
ZR driver exist in Sony developer website and I installed the driver but I don't know why my computer not recognizing my phone.My phone can turn into fastboot mode(blue light on when pressing vol up and connecting cable to pc) but when I type command "adb devices" the listed device is empty I mean no adb fastboot device found.I'm just asking the drivers are not working beacuse of windos 10?Actually when after I use custom rom I couldn't connect my phone to pc.So any driver can fix this problem?I searched really hard on google but couldn't find any proper sloutions.
Chum.zuizui said:
Yes.good luck for you
Click to expand...
Click to collapse
This isn't helping!
Windows 10 is a pain to install drivers into.. But use fastboot in flashtool instead of flasmode.. Should recognize your phone and flash the boot image from there
hagar006 said:
Windows 10 is a pain to install drivers into.. But use fastboot in flashtool instead of flasmode.. Should recognize your phone and flash the boot image from there
Click to expand...
Click to collapse
I know you are trying to help me but I tried everything and nothing is working.I installed driver from flashtool but still no clue why pc not recognizing my phone.My phone is like a live junk.My phone soft bricked many times and I could recover my phone with flashtool so I know what to do but this problem is way more confusing.I just need to know what is causing this issue.
You've managed to install the drivers inc the lagan drivers in flashtool and connected your phone in fastboot mode with flashtool running and flashtool still don't recognize your phone? I've done that loads of times even with no drivers installed and flashtool has been able to recognize the device in fastboot.. If that's the case, then I'm sorry I'm not able to help any further as flashtool has always been my failsafe when things have gone wrong.. Adb and fastboot are usually no help for me in Windows 10..
hagar006 said:
You've managed to install the drivers inc the lagan drivers in flashtool and connected your phone in fastboot mode with flashtool running and flashtool still don't recognize your phone? I've done that loads of times even with no drivers installed and flashtool has been able to recognize the device in fastboot.. If that's the case, then I'm sorry I'm not able to help any further as flashtool has always been my failsafe when things have gone wrong.. Adb and fastboot are usually no help for me in Windows 10..
Click to expand...
Click to collapse
Flashtool is the best tool to recover soft bricked phone I know but this problem is way more complicated.
Thanks that you tried to help me.I hope I'll figure it out some time later.
Røbin said:
This isn't helping!
Click to expand...
Click to collapse
I dont meant it like that .did you fix it
Chum.zuizui said:
I dont meant it like that .did you fix it
Click to expand...
Click to collapse
Unfortunately no.For some reason pc not detecting fastboot device even after I installed fastboot driver.
same problem plz help
I have same problem . phone not charging ,not booting , just sony logo comes for a sec then it turns off .
I'm tired of searching for a solution almost a week but nothing helped me.
Last day i flashed a stock rom via flash tool , still problem persists .
Pc companion -no detection of device , can't boot into recovery mode..
Please guys help me.. I'm in serious trouble with my phone
pralay445 said:
I have same problem . phone not charging ,not booting , just sony logo comes for a sec then it turns off .
I'm tired of searching for a solution almost a week but nothing helped me.
Last day i flashed a stock rom via flash tool , still problem persists .
Pc companion -no detection of device , can't boot into recovery mode..
Please guys help me.. I'm in serious trouble with my phone
Click to expand...
Click to collapse
My problem was created because local charger damaged my phone battery.So I couldn't turn on my device like yours.I replaced the battery and charger from Sony Center and now my phone is good as new.So Try to use other good battery(small or similer size that suites to your phone's battery pin)and see if your phone turns on without any issue.Then you can target the problem.
[EDIT: It's all good now... A stupid mistake of mine]
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Moischen said:
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Click to expand...
Click to collapse
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Mooatreides said:
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Click to expand...
Click to collapse
Yeah, good question... But it's too late for that now
Try another pc
emprazol said:
Try another pc
Click to expand...
Click to collapse
same thing
Manually install adb driver
Moischen said:
same thing
Click to expand...
Click to collapse
One time, I had such an issue with drivers, what I did is use a free VM machine software on Windows to install a Linux distro (or you could dual boot it), and from Linux it worked to detect my device.
On the other hand, there are really probably easier ways to fix your issue, but who knows, it may help and does not take too long.