[Q] Stuck at CWM, USB mounting doesn't work, Can't copy ROMs over to the phone. - Sony Xperia S, Acro S, Ion

So, someone went and did something to my phone, I guess he deleted everything, and formatted the SD card, system folder, etc.
Now, I don't have any of my ROMS on my phone, and I'm stuck with just CWM. I cannot mount the USB storage using CWM, so I can't transfer any files over.
I'm using Windows 8.1, and I've tried installing the drivers using Flashtool. Installation of drivers was successful, but Windows still detects the phone as a "Xperia S" with an exclamation mark. Running Flashtool tells me I need to install the drivers from the driver folder. I installed the 3 drivers with Xperia S in its name, and the fastboot and adb drivers. Still doesn't work.
Any advice? Basically I just want to be able to copy a ROM over to the phone to install it, as I don't have any OS(?) on the phone right now.

You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.

pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Actually window 8 can! U have to Disable driver enforcement setting through advance reboot in window 8
Sent from my SGP321 using XDA Premium 4 mobile app

monivan said:
Actually window 8 can! U have to Disable driver enforcement setting through advance reboot in window 8
Sent from my SGP321 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done that. I installed the drivers, but the phone is still not recognised for some reason. Not entirely sure why, though I suspect it's got something to do with me using Windows 8.1.

pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Thanks. I'll try and see if I can find a Windows 8 or 7 machine. Not possible to do this in Mac, I suppose? Would a virtual machine work, you think?

markiemice said:
I've done that. I installed the drivers, but the phone is still not recognised for some reason. Not entirely sure why, though I suspect it's got something to do with me using Windows 8.1.
Click to expand...
Click to collapse
Maybe u could try Sony Update Service, so that the fastboot driver might install properly through official software from sony.
Sent from my SGP321 using XDA Premium 4 mobile app

Is it save to assume that you have experience flashing ROM? Just asking coz sometimes we missed some obvious step.

Yes, I do. I've flashed using CWM. Mostly it's pretty easy, just copy the ROM onto the phone, and install it using CWM after clearing caches.

pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Thanks for the idea to do a sideload! I used a virtual Windows XP, and was able to install a ROM onto my phone!
Thanks very much.

Related

[GUIDE] Install Portable ADB In 5 Easy Steps

No ADB knowledge needed. Just follow instructions.
1. Download mini-adb Here
2. Extract that and put it on your desktop.
3. Go download HTC sync Official Page or HTC sync Direct Download and install it. If you are NOT HTC, then download whatever you need to get the drivers needed for your phone onto your PC (like samsung Kies)
4. Plug your phone into your computer and make sure debugging mode is on.
5. Now go to your mini-adb folder on your desktop and double click RunMe.bat
6. When the black command prompt window pops up, type the following:
adb devices
7. If it lists your Device, then you did it!
8. To push any file, make sure you place it in the same folder as your RunMe.bat, and the command will be
adb push WHATEVERTHEFILENAMEIS /WHEREEVERYOUWANTITTOGO
For example, to push a file called libSwypeCore.so into /system/lib/
Adb remount
adb push libSwypeCore.so /system/lib/
+1 Thanks if this worked for you!
P.S. Technically you have installed ADB by step 5. Step 5 and onwards just tells you how to use it.=P Title doesn't lie.
why not just install Android SDK from http://developer.android.com/sdk/index.html
and you got ADB right after the installation.
By the way if you wanna push something to /system, you have to "adb remount" first to set it "r/w"
When I click runme it opens for a split second and then disappears
I so wish i could of found this earlier to save me the 4 hours of WTF moments i was having.
Also beats not having to install the SDK of 31megs not counting install/setup as well.
jzhyok said:
why not just install Android SDK from http://developer.android.com/sdk/index.html
and you got ADB right after the installation.
By the way if you wanna push something to /system, you have to "adb remount" first to set it "r/w"
Click to expand...
Click to collapse
I almost gave up on adb cuz that way didn't work for me. And yes, I forgot to include adb remount.
this should be stickied for the nooblets.
Fantastic; this is definitely going to make getting CM6 my fiancée's G2 easier. Now, which of the 3 rooting processes below should be the one I use for her stock T-Mobile G2:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
http://forum.xda-developers.com/showthread.php?t=834228
http://forum.xda-developers.com/showthread.php?t=886023
Thanks!!
How do I flash a radio with this? Cause I don't see any "fastboot" folder, whatever that is.
BradBot said:
Fantastic; this is definitely going to make getting CM6 my fiancée's G2 easier. Now, which of the 3 rooting processes below should be the one I use for her stock T-Mobile G2:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
http://forum.xda-developers.com/showthread.php?t=834228
http://forum.xda-developers.com/showthread.php?t=886023
Thanks!!
Click to expand...
Click to collapse
I edited my post to answer ur Q
convolution said:
I almost gave up on adb cuz that way didn't work for me. And yes, I forgot to include adb remount.
Click to expand...
Click to collapse
Same boat..I saw your post on Jan 20th in the Guide for ADB thread, which is really nice..
But I got to the same point(you also outlined in that thread) of after uninstalling the previous Android usb drivers on my system, and trying to choose a specific location to look for a x86 driver, I was left with Windows not allowing me to click 'OK' to denote the USB driver folder from the Android SDK that I wanted to scan. Not sure what was up, but I was elated to see the link to this thread in your sig.
Thanks for the guide! My Evo 4g Shift thanks u as well
How do I install a Radio with this?
Broman400 said:
How do I install a Radio with this?
Click to expand...
Click to collapse
don't know.
I assume you find the apk, find the lib files, and push stuff to places?
LOL I wiped my laptop cause it had viruses and I forgot how to install ADB so I had to click my own link. LOLL
convolution said:
LOL I wiped my laptop cause it had viruses and I forgot how to install ADB so I had to click my own link. LOLL
Click to expand...
Click to collapse
hahaha
Broman400 said:
How do I install a Radio with this?
Click to expand...
Click to collapse
K I got it. You can only flash a radio if you have S-off.
Download the zip file for the radio. Put it into your SD card. Boot up in recovery. Choose flash zip file. Choose radio zip file. Done.
No adb required.
Gee, thanks past me! I would have forgotten how to get it if it weren't for my own sig!
From: Present Me.
convolution said:
No ADB knowledge needed. Just follow instructions.
1. Download mini-adb Here
2. Extract that and put it on your desktop.
3. Go download HTC sync Official Page or HTC sync Direct Download and install it. If you are NOT HTC, then download whatever you need to get the drivers needed for your phone onto your PC (like samsung Kies)
4. Plug your phone into your computer and make sure debugging mode is on.
5. Now go to your mini-adb folder on your desktop and double click RunMe.bat
6. When the black command prompt window pops up, type the following:
adb devices
7. If it lists your Device, then you did it!
8. To push any file, make sure you place it in the same folder as your RunMe.bat, and the command will be
adb push WHATEVERTHEFILENAMEIS /WHEREEVERYOUWANTITTOGO
For example, to push a file called libSwypeCore.so into /system/lib/
Adb remount
adb push libSwypeCore.so /system/lib/
+1 Thanks if this worked for you!
P.S. Technically you have installed ADB by step 5. Step 5 and onwards just tells you how to use it.=P Title doesn't lie.
Click to expand...
Click to collapse
This archive has some kind of weird ".exe" file. What is this, some kind of balmervirus?
This is an older thread but I'm hoping someone can help me. I had adb installed on my old win7 pc and I had the my nexus drivers installed and everything was good. A month ago I got a new pc that is running win8 and I've had nothing but trouble ever since. I cannot find nexus drivers that will install on windows 8. Is anybody else out there running windows 8 that can help me? The VZW driver exe file would not even install for me and I ran it as an administrator.
ba_hamilton said:
This is an older thread but I'm hoping someone can help me. I had adb installed on my old win7 pc and I had the my nexus drivers installed and everything was good. A month ago I got a new pc that is running win8 and I've had nothing but trouble ever since. I cannot find nexus drivers that will install on windows 8. Is anybody else out there running windows 8 that can help me? The VZW driver exe file would not even install for me and I ran it as an administrator.
Click to expand...
Click to collapse
Yeah... I also gave win8 a try...
I reverted back to win 7. Sorry, can't help you there bro. Have you tried downloading the nexus toolkit and installing gnex drivers using that toolkit?
AW: [GUIDE] Install Portable ADB In 5 Easy Steps
Try this: In Windows 8 install the drivers with Windows 7 Compatibility checked. This did the trick for me while testing adb and rooting a samsung galaxy tab on my windows 8 x64.
I found this tip on only one forum after trying many other tips and drivers around for more than one day and it worked. So all credits to this poster.
Sent from my HTC Desire Z using xda app-developers app

adb

how can i use adb if i cant install drivers to windows 7..maybe linux??
sorry for being a complete noob
ADB is working in Ubuntu without any drivers needed.
davebugyi said:
ADB is working in Ubuntu without any drivers needed.
Click to expand...
Click to collapse
can you give me a thread about that?i want to know more!
In these tutorials the android SDK is outdated - Download it from the official site, to get the latest version.
I used the first method to set it up on Ubuntu 11.04 Natty. I can confirm it works.
http://forum.xda-developers.com/showthread.php?t=537508
http://forum.cyanogenmod.com/topic/116-tutorial-ubuntu-android-sdkadbfastboot-updated/
orsidoc said:
how can i use adb if i cant install drivers to windows 7..maybe linux??
sorry for being a complete noob
Click to expand...
Click to collapse
ADB works fine in Windows 7, even on x64. Download the latest HTC Sync, run the setup file then cancel it after the first stage (driver install) if you only want the drivers. Then go to your adb directory via command prompt and type adb remount (make sure the phone is plugged in and turned on, doesn't need to be unlocked or set to Disk drive though)

[HOWTO] simple. window usb driver with adb shell without android sdk.

hi just found another method to install the adb driver for SGW. because i encounter problem for not detecting SGW even after installing samsung kies. If you encounter the same problem as me feel free to follow my steps.
1. Download the driver from below links.
a. x86 google Samsung-Galaxy-S-USB-Driver-for-Windows-x86-Download-96692 click http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x86-Download-96692.html
b. x64 google Galaxy-S-USB-Driver-for-Windows-x64-Download-96693 click http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x64-Download-96693.html
2. unzip the downloaded file to you designated folder.
3. go to device manager in window system
4. select properties on samsung_android device
5. click on update once you received a prompt select browse manually for driver.
6. point it to the extracted folder.
7. there are 3 things you need to install. just point all the unrecognized device to update from the extracted folder.
8. you should have all the driver need to connect SGW to windows.
For the adb shell you can use google (android commander) http://androidcommander.com/ just download it and install. Run the program and you will notice shell command on the tab.
I've tested and it work on my SGW. If it does not work on you please dont complain.
Thanks your sharing
Sent from my GT-I8150 using xda premium
andynroid said:
Dude your link is unaccessible
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x64-Download-96693.html
http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x86-Download-96692.html
Hi!
Just a noob question, which should i download for a windows7 32bit machine? my processor is an intel i3, which i know supports 64bit, so i got confused with the x64 and x86 designation.
Thanks!
Sent from my GT-I8150 using XDA App
Your Win is 32 bit..so that would be x86
Sent from my GT-I8150 using xda premium
Hi, on the subject of adb, fastboot, and drivers, here is a pretty good tutorial, with pics, and fully illustrated.
I used it, on Windows 7, and it works very well.
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Thanks to Ashraf from dotTech

[Q] Need driver help for my KF - ADB is not detecting the device when in TWRP Mode

My KF is having some problems. I followed the tutorial from Cyanogen for the installation, and I got to the point where I finished flashing the recovery (twrp (don't know which version, it's from this site). I have a bootable device that will go into recovery, but when booting into standard Kindle OS, the device is unable to boot, and gets stuck on the KF logo. I am unable to use ADB to push the rom onto the device for flashing, and I cannot copy it manually because I cannot boot. My fastboot drivers are working, but when I go into Device Manager on Win7, my kindle shows up with the triangle + exclamation point. I can't update this driver as nothing works, and I've literally tried every possible solution on the internet.
thanks in advance
shameless self bump
Have you tried the drivers in my signature? You right click the device and hit update drivers and point it to where my drivers where extracted to use them.
I have tried your drivers - I tried that before coming here. When I extracted the driver files and pointed the install to the directory, it didn't give any install. It said drivers were not found and that's where I got stuck. Does the mounting of the internal storage not work in TWRP?
No it does not, you have to adb push them or adb side load them. If you tell me the vid and pid listed in the devices hardware id's on the details tab of its properties in the device manager maybe I can update my drivers to help you.
okay let me see:
do you want the pid and hid in TWRP mode or fastboot mode
in the hardware IDs these are listed:
USB\VID_1949&PID_0008&REV_0216&MI_00
USB\VID_1949&PID_0008&MI_00
Those are the two when booted into TWRP. If you need anything else like fastboot hid then I'll provide those as well.
shadowblade2652 said:
I have tried your drivers - I tried that before coming here. When I extracted the driver files and pointed the install to the directory, it didn't give any install. It said drivers were not found and that's where I got stuck. Does the mounting of the internal storage not work in TWRP?
Click to expand...
Click to collapse
You may be having a driver install problem. Windows 8/7 64bit must disable security enforcement. This is for Windows 7.
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers the next time you restart your computer. Follow steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Now restart your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
You may be having a driver install problem. Windows 8/7 64bit must disable security enforcement. This is for Windows 7.
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers the next time you restart your computer. Follow steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Now restart your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply but
I don't have drivers installed at all The kindle fire in the device manager shows with a little yellow triangle and exclamation and it says no compatible driver found. Fastboot still works though. Can anyone link me to the stock kfOS for me to reflash back to stock kindle fire?
shadowblade2652 said:
Thanks for the reply but
I don't have drivers installed at all The kindle fire in the device manager shows with a little yellow triangle and exclamation and it says no compatible driver found. Fastboot still works though. Can anyone link me to the stock kfOS for me to reflash back to stock kindle fire?
Click to expand...
Click to collapse
Fastboot is not gonna work if you don't have your usb drivers set up and your tablet recognized. Your tablet has to be recognized and that yellow triangle says it's not.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Fastboot is not gonna work if you don't have your usb drivers set up and your tablet recognized. Your tablet has to be recognized and that yellow triangle says it's not.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
nonononono it's quite weird
In fastboot mode, the device is easily recognized by the computer. i can flash and have no problems whatsoever. When I try to use TWRP to copy the image to the device, that's where I get the issue.
shadowblade2652 said:
nonononono it's quite weird
In fastboot mode, the device is easily recognized by the computer. i can flash and have no problems whatsoever. When I try to use TWRP to copy the image to the device, that's where I get the issue.
Click to expand...
Click to collapse
If you want, copy and paste your environment path here. Let's check and make sure it looks good.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
If you want, copy and paste your environment path here. Let's check and make sure it looks good.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
And what do you mean by that? What is the environment path?
I know it can be flashed in fastboot as the computer recognizes it and fastboot detects it as a device. It's just that in twrp the computer is unable to find any drivers for it.
shadowblade2652 said:
And what do you mean by that? What is the environment path?
I know it can be flashed in fastboot as the computer recognizes it and fastboot detects it as a device. It's just that in twrp the computer is unable to find any drivers for it.
Click to expand...
Click to collapse
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
m8 I have no idea what you are talking about.
I started the cyanogen mod tutorial that they have on the wiki, and I got to flashing the custom bootloader and the twrp recovery mode. After that, the device wasn't recognized during TWRP mounting so I wasn't able to mount and copy over the CM image for installation. That's why I am stuck now. Could you please link me to or attach the kindleOS stock rom so I can flash it and go back to stock kindleOS. Right now I have an expensive brick and it's seriously bugging me.
LinearEquation said:
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Do you mean the windows path? If you do, I used the installer I found on this website along with the kindle fastboot drivers found from amazon and it was already added to the path.
another shameless self bump.
bump?
im facing the same problem here, i restored my kf hd 8.9 back to stock using this thread: http://forum.xda-developers.com/showthread.php?t=2468988
however, i just cant connect to the device via adb. fastboot is working, so the drivers are fine. adb has been enabled on the device's settings panel.
i need adb to root the device and reinstall the 2nd bootloader for custom roms.
It might actually be a driver problem, switching between twrp, fastboot, and a android os have caused issues for me before where I NAD to uninstall the driver and reinstall it, and sometimes it would have a USB composite USB device I'd have to remove to fix it(had a bird of 1949 so I new it was the kindle).
surprisingly restoring back to stock and then doing it again worked. I'm now running 4.4.4
Thanks for the help stunts, sjj, and linear

Cant get fastboot to work!

I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Digital signature of the driver or wrong drivers is the problem
joedoctor said:
I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Click to expand...
Click to collapse
u are not saying mutch about how u are trying to enter fastboot
u do know the phone must be turn into fastboot right ?
...
same here, done everything i can...
mockneygeeza said:
same here, done everything i can...
Click to expand...
Click to collapse
to get fastboot to work u need to reboot the phone into fastboot
-fluffy- said:
to get fastboot to work u need to reboot the phone into fastboot
Click to expand...
Click to collapse
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
I'm going to try the above, it's never too late ?
moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
-fluffy- said:
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
Click to expand...
Click to collapse
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
moeq123 said:
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
Click to expand...
Click to collapse
im on windows 10 also an my adb devices also show nothing but i can still flash recovery an all

Categories

Resources