I was using wugs toolkit and this brought adb, fastboot and drivers. Now I would like to use adb and fastboot independent from the toolkit. I guess drivers stay the same, but what is the best way to install fastboot and adb systemwide, without having to install the full sdk?
Lownita said:
I was using wugs toolkit and this brought adb, fastboot and drivers. Now I would like to use adb and fastboot independent from the toolkit. I guess drivers stay the same, but what is the best way to install fastboot and adb systemwide, without having to install the full sdk?
Click to expand...
Click to collapse
I, personally, would use the SDK to get everything on your PC. At least then you've got all the files
After that, follow this guide:
http://forum.xda-developers.com/showthread.php?t=1161776
After that, you can use adb/fastboot from any location
Please go to my "adb and fastboot" thread which you can get to via "guides and info threads" link in my signature. This will give you naked drivers and 15 second adb and fastboot installer. Quickest and easiest method IMHO
rootSU said:
Please go to my "adb and fastboot" thread which you can get to via "guides and info threads" link in my signature. This will give you naked drivers and 15 second adb and fastboot installer. Quickest and easiest method IMHO
Click to expand...
Click to collapse
Hey mate, I tried the tool, but it doesn't work:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Lownita just use it for adb and fastboot. In my thread there is a separate link for drivera
@rootSU I'll try! Well, does the device have to be connected to the PC while installing any of those? I guess not? (Ofc drivers install themselves when phones gets connected afterwards).
Lownita said:
@rootSU I'll try! Well, does the device have to be connected to the PC while installing any of those? I guess not? (Ofc drivers install themselves when phones gets connected afterwards).
Click to expand...
Click to collapse
Yeah needs to be connected because you need to right click the device in device manager. Just connect it in recovery or bootloader depending which one you're most likely to use most.
Related
So basically i am trying to put the ROM zip file to the phone via ADB..
I have TWRP, so i start ADB SIDELOAD
connect phone to computer
and run adb devices
but i have never managed to find the phone...
I even tried to install adb drivers but:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P.S
HTC drivers are installed
phone is unlocked
I have dualboot Windows 8 & Ubuntu 14.04
if that helps in anyway
citybong said:
So basically i am trying to put the ROM zip file to the phone via ADB..
I have TWRP, so i start ADB SIDELOAD
connect phone to computer
and run adb devices
but i have never managed to find the phone...
I even tried to install adb drivers but:
P.S
HTC drivers are installed
phone is unlocked
I have dualboot Windows 8 & Ubuntu 14.04
if that helps in anyway
Click to expand...
Click to collapse
have you tried Ubuntu??
windows sometimes has a lot of problem.
If you've got a driver installed that works fine you can use Device Manager in Windows. Connect your phone, find it in the list, choose update driver, and the option that lets you choose a driver from the list. Select the driver that works (mine is called MyHTC) and it should install. You need to repeat this for eachc of the three states (adb in Android, fastboot, and adb in Recovery)
@SidDev said:
have you tried Ubuntu??
windows sometimes has a lot of problem.
Click to expand...
Click to collapse
Yes made it work with ubuntu!
i just had to download adb sdk and install lib32stdc++6
and adb was ready!
citybong said:
Yes made it work with ubuntu!
Click to expand...
Click to collapse
happy I was able to help
you could have pressed the thanks BTW
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the device manager I get a yellow flag on the ADB interface:
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Seleuco said:
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
?
In the device manager I get a yellow flag on the ADB interface:
In the device manager I get a yellow flag on the ADB interface:
?
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Click to expand...
Click to collapse
Honestly you don't need adb portion working to do this. Have you tried seeing if your computer recognizes your opo in fastboot mode?
Turn your phone off hold volume up and power button it will boot into fastboot. Then plug your phone into your computer let it install drivers then open command prompt where your fastboot file is and type fastboot devices if it shows something your good to go follow the rest of the guide unlock bootloader and install a custom recovery and SuperSU to root.
Also if its me I would install twrp recovery.
you sure you got the right drivers?
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
giaur said:
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
Click to expand...
Click to collapse
Honestly I don't even know at this point, I tried deleting and installing them a dozen times from different sources, but it doesn't recognize them. Do you know any idiot-proow way of installing the drivers?
wulsic said:
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
Click to expand...
Click to collapse
Thanks, but I actually took the screenshots right after running that program
Seleuco said:
Thanks, but I actually took the screenshots right after running that program
Click to expand...
Click to collapse
Did you also tried to install the driver manually in device manager?
See this link how you can do that:
http://www.technobuzz.net/install-nexus-5-driver-adb-fastboot-unlock-bootloader/
If these drivers don't work and or can't install then just extract Snoop05's adb installer and use those drivers :good: hope this would work now,
the issue is probably that there are so many drivers installed that they are conflicting with each other and windows is just deciding which one is better, so manually overriding it should fix it and else I guess you have to remove the old adb drivers with an program but first try these easy methods
Hello All
I have had to reinstall stock(sm-g930f) due to an own stupid(again) mistake.
The OS is reinstalled and working and now I would like to flash Magisk through ADB. ADB recognises the phone by "adb devices" when in normal mode. When in fastboot (download mode) it does not recognise the phone. All it states is: List of devices attached
Can someone help me to overcome this, or if you have another suggestion to flash Magisk?
Edit:
after searching for a long time I read somewhere:
Do not put phone in download(fastboot) mode, only in charging mode when connected to the PC's motherboard USB port. Works flawless since, with having the relevant ADB drivers installed.
Adb is adb.
Fastboot is fastboot.
For adb, you need adb binaries.
For fastboot, you need fastboot binaries.
I have downloaded these and and haven't had any luck. Is there a detail how-to somewhere?
kiwigi said:
I have downloaded these and and haven't had any luck. Is there a detail how-to somewhere?
Click to expand...
Click to collapse
Try this:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
d
VD171 said:
Try this:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Click to expand...
Click to collapse
Thanks
Done that. PC is not recognising phone in download mode(fastboot)
kiwigi said:
d
Thanks
Done that. PC is not recognising phone in download mode(fastboot)
Click to expand...
Click to collapse
Probably because you didn't have drivers installed.
You need to find the specific drivers for your device model and install it.
Good luck.
VD171 said:
....
You need to find the specific drivers for your device model and install it.
..
Click to expand...
Click to collapse
I have searched for hours and all I have found seems not to be compatible with S7 sm-g930f. I have also followed this https://androidadbdriver.com/ specific to my mobile.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you really try to find ?
Here is the download for samsung usb drivers: https://developer.samsung.com/mobile/android-usb-driver.html
Install it and reboot.
If it doesn't work, probably you have any problem in your device manager.
I'm an user linux and I hate windows.
Good luck google'ing it.
Im having the same problem. i don't want to use the adb setup thing becuase its a virus so yeah.
kiwigi said:
Hello All
I have had to reinstall stock(sm-g930f) due to an own stupid(again) mistake.
The OS is reinstalled and working and now I would like to flash Magisk through ADB. ADB recognises the phone by "adb devices" when in normal mode. When in fastboot (download mode) it does not recognise the phone. All it states is: List of devices attached
Can someone help me to overcome this, or if you have another suggestion to flash Magisk?
Edit:
after searching for a long time I read somewhere:
Do not put phone in download(fastboot) mode, only in charging mode when connected to the PC's motherboard USB port. Works flawless since, with having the relevant ADB drivers installed.
Click to expand...
Click to collapse
THANK YOU!!! From a fellow Kiwi. I followed a tutorial for my Nokia G20 and they left this part out! Faaaaar out. You're my hero
Hello everyone, I have a big problem with my device, it happens that the system started to fail and after that it turned off, when I turned on it stayed in a bootloop and I can only access the fastboot, the question is that my device does not have the OEM and I never did any modifications so it doesn't have recovery either.
So far I have tried to install for fastboot the boot.img and system.img from the original firmware but I get the error "remote: not allowed in locked state" because the bootloader is locked
Any recommendation?
Reflash original Stock ROM by means of ADB Sideload method
jwoegerbauer said:
Reflash original Stock ROM by means of ADB Sideload method
Click to expand...
Click to collapse
but I can't use recovery and it doesn't have TWRP installed either.
The truth is that I am quite new to this subject but it would help me a lot if you guide me through that process.
In addition, the stock rom offered by ulefone is in .tar.gz format
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
jwoegerbauer said:
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
Click to expand...
Click to collapse
How about, I was trying to access with ADB, however when I put adb devices, the device does not appear, perhaps because I did not have the USB debugging before the bootloop, I was trying with different commands and nothing happens, but it does appear in the device manager. I'm sure I have the correct drivers because I tried another device with USB debugging enabled and it works fine.
Attached image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should be obvious to you that ADB can't work as expected if USB debug option isn't got enabled on Android.
how can the bootloop be solved if only fastboot is available?
And the manufacturer flashing tool doesn't recognize the phone?
I cannot reflash the phone.