Hello, my name as you can probably guess is Krutonium.
I do a lot of work over at leshcatlabs (Can't post a link yet, if a mod could edit that would be great!) and I was wondering if this community would be interested in my little project (Story about Why first, or look about 5 inches down).
So I recently got this little Android Tablet as a Gift, and I wanted to root it so I could play around with some less normal features like overclocking and such. So I go and get the ADB Drivers from Google, and quickly discover that I have to re-install the driver every time I reboot my tablet. This quickly got annoying, so I took a look at the actual inf (Over at leshcatlabs, we modify Video Card Drivers, so this was pretty much the norm for me, though it has a much cleaner layout than AMD's inf's) and decided to add my Tablets ID's into the driver. This of course worked, and it stayed installed.
I am willing to make a Massive INF File with your DEV_ID's, if you are interested.
I will sign it with a Driver Certificate, so that it will install on Windows Vista, 7, 8, 8.1, and the upcoming 9, without having to disable Signing Enforcement, and enabling you not not have any issues like having to constantly re-install the driver.
Any Questions? Are you interested? Please reply to let me know!
Hi krutonium i use unifl since years thanks for your work! I'm glad to see you on xda too good luck with your new project! :highfive:
Hi there!
I'm Tito & I've recently joined the Android USB UnifL team - the initiative as told by @Krutonium. Lot of improvements are made already!
Website: http://leshcatlabs.net/2014/09/28/android_adb-usb_unifl_drivers/
Discussion forum: http://leshcatlabs.net/forums/viewforum.php?f=15
Download: http://leshcatlabs.net/downloads_usb_unifl/
In a nutshell:
We provide digitally signed drivers for ADB & Fastboot (if available) interfaces.
Some other interfaces, such as Sony's Flashmode, Samsung's Download mode, Xiaomi's MDB are also supported.
No need to turn off Driver Signature Enforcement in Windows x64 to install these drivers.
Windows XP, Vista, 7, 8, 8.1 (& in future 10) are fully supported.
New devices from OEMs & generic/clone devices can easily be added in the supported list.
Automatic update check in installer.
Rapid development cycle.
List of supported OEMs & devices :
Coolpad
Dell
Google
HTC
Huawei
Intel SoC based devices
LG
MediaTek SoC based devices
Motorola
NVIDIA
OnePlus
Rockchip SoC based devices
Samsung
Sony
Sony Ericsson
Trekstor
Xiaomi
YU
To do:
There are already number of similar efforts exist, like Koush's Universal ADB Driver & @1wayjonny's Universal Naked Driver, but they aren't updated & actively maintained.
We always try our best to swipe out the errors & add more devices in the supported list. But to do so, we need active support from the users.
If your device from mentioned list doesn't work or you have a new device that isn't present in the list, please do the following:
1. Make sure USB Debugging in on in the Android device. Connect it with the PC.
2. Press Win key + R to open the Run dialogue box, type "devmgmt.msc" (without the quotes) & press Enter - Device Manager will be opened.
3. Go to the device that is unrecognized - the name should have something to do with your device, for example:
{
"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"
}
4. Double click on the device, go to Details tab and from the dropdown menu, select "Hardware Ids".
5. Take a screenshot or copy the texts. You need to post like this:
Please add my Tablet/Phone:
(OEM) PROSCAN
(Model) PLT7044K-B
(Dev_ID for ADB)
USB\VID_2207&PID_0010&REV_0222&MI_01
USB\VID_2207&PID_0010&MI_01
Click to expand...
Click to collapse
6. Similarly do for Fastboot interface if your device supports it.
7. Last but not the least, due to increasing number of cloned/generic devices, it is really helpful for us if you also link the official driver pack/sync tool/phone manager application of your OEM.
[Screenshots are created by @Krutonium ]
It would be better to join our forum regarding issues & support but we're also active in XDA too.
:good::highfive:
Related
Pdanet, a tethering tool which allows you to connect your PC/laptop to internet using your Android smartphone, also specialises in something else: You can install the drivers for any Android device using the PC end of Pdanet. While most of the popular devices come with official drivers or are easily available on the internet, some of the cheper and less popular models, like the ones sold by local Indian manufacturers, don't have any official drivers, so it's really a pain to find drivers for them.
{
"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"
}
Pdanet comes to the rescue here. I have tried it with a plethora of devices :fingers-crossed:, and it installs drivers for all of them. I have written a full fledged guide, targeted especially at newbies, to help everyone install drivers for their device and proceed with rooting/ using ADB or fastboot. I have even included snapshots to help you get through the process swiftly.
THe process is quite easy. I'm posting a summary here:
Download and install pdanet on your pc. It is available here: http://www.junefabrics.com
During the installation process, select device manufacturer accordingly.
Attach the device to your pc using usb only when the setup asks you to do so.
That's it.
Don't forget to exit pdanet before trying to connect to adb etc.
Here is the guide: http://www.droidiser.com/2012/11/how-to-install-drivers-for-any-android.html
These days, during the process of rooting, installing the drivers is one of the toughest steps for many, as one click root tools are available on xda, once drivers are installed successfully.
droidiser said:
Pdanet, a tethering tool which allows you to connect your PC/laptop to internet using your Android smartphone, also specialises in something else: You can install the drivers for any Android device using the PC end of Pdanet. While most of the popular devices come with official drivers or are easily available on the internet, some of the cheper and less popular models, like the ones sold by local Indian manufacturers, don't have any official drivers, so it's really a pain to find drivers for them.
Pdanet comes to the rescue here. I have tried it with a plethora of devices :fingers-crossed:, and it installs drivers for all of them. I have written a full fledged guide, targeted especially at newbies, to help everyone install drivers for their device and proceed with rooting/ using ADB or fastboot. I have even included snapshots to help you get through the process swiftly.
THe process is quite easy. I'm posting a summary here:
Download and install pdanet on your pc. It is available here: http://www.junefabrics.com
During the installation process, select device manufacturer accordingly.
Attach the device to your pc using usb only when the setup asks you to do so.
That's it.
Don't forget to exit pdanet before trying to connect to adb etc.
Here is the guide: http://www.droidiser.com/2012/11/how-to-install-drivers-for-any-android.html
These days, during the process of rooting, installing the drivers is one of the toughest steps for many, as one click root tools are available on xda, once drivers are installed successfully.
Click to expand...
Click to collapse
Thanks bro I'll try it
Hmm,
I finally caved and threw a win7 partition on here..
Ive had this going for about 20 minutes and I seem to be 'stuck' here...
Doesnt seem to be doing anything..
what's up? lol
(I'm essentially a windows noob again, so please bare with me)
HELP!
I tried rooting my Lenovo A1000-F --- followed the instructions, installed PDANet and ran Kingo, which said the root was complete. When I clicked FINISH the screen on the tab went blank and now I can't get anything!
Here's what I'm seeing after plugging the USB back into the tab, which I hope isn't bricked.
Link To Main Thread
{
"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"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved
Reserved.
schweet !
I will d/l and check this puppy out, sounds like a cool program.
: this is above my pay grade and thanks : ) .
has anyone confirmed this working? also is it still usable on 6.0.1 ?
Good stuff mate
I installed the tool but it doesnt recognize my X5.
Keeps saying offline.
Thanks!
WinDroid Toolkit v3.0 Is Now Out!
WinDroid Toolkit v3.0 has been released! It's a huge update with a material redesign, major recode and support for 43 new devices!
You can out more specific changes in the changelog here.
You can download the new update here.
All versions before v3.0 will not have their files updated anymore since I've moved from hosting on BasketBuild to Amazon S3. Please update to v3.0 to ensure you're getting the latest recovery and root files!
On the toolkit gui, when I tried to unlock the bootloader, it just stuck on "reboot device" screen while my phone, nexus 5x, has already in bootloader mode. What should I do now ? I did put my phone on "debug" mode, enable "OEM unlock", disable MTP.
system windows 10 drivers are installed and good for the nexus 5x. Device manager list it as good. Start the unlock process by clicking "unlock" the oem unlock is checked. usb debugging is checked. the tools says everything good and when it gets to bootloader says "fastboot device not found"
I check device manager and now says drivers for device not found and the yellow triangle. as soon as i reboot the phone when fully booted it has it listed in device manager as good but in bootloader it as the yellow triangle. please help to unlock it. thank you
Help. Thank you.
EDIT:
the drivers for nexus do not work for the bootloader fastboot mode. Windows lists it as android with the triangle in device manager when in fastboot and i had to allow windows to search for the drivers for it. When found it is listed as something like Marshall Bootloader in win device manager not nexus after the phone is fully booted up.
Guys I am getting desperate here. I hate crying in the forums for help, but that's why they are here. I am sorry but here I am to whine about the problem that I am facing whole day.
I tried with OP, Samsung, Xiaomi, Google USB drivers. Nothing so far works. I tried many options but I can' make the Windows to recognize the phone after getting into BL. Windows 11, tried all my USB ports (I have only 3), no success. Pushed even Googles driver files manualy from the Device manager and I chose the BL option of the driver, that didn't work, then I tried the rest of the 3 options of the driver, that didn't work either.
I followed this metod as well - https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
The only thing that has left as an option is the lack of USB 2.0. If this is the problem I am gonna throw up...
Any help or suggestion would be highly appreciated.
{
"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"
}
mrpeev said:
Guys I am getting desperate here. I hate crying in the forums for help, but that's why they are here. I am sorry but here I am to whine about the problem that I am facing whole day.
I tried with OP, Samsung, Xiaomi, Google USB drivers. Nothing so far works. I tried many options but I can' make the Windows to recognize the phone after getting into BL. Windows 11, tried all my USB ports (I have only 3), no success. Pushed even Googles driver files manualy from the Device manager and I chose the BL option of the driver, that didn't work, then I tried the rest of the 3 options of the driver, that didn't work either.
I followed this metod as well - https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/
The only thing that has left as an option is the lack of USB 2.0. If this is the problem I am gonna throw up...
Any help or suggestion would be highly appreciated.
View attachment 5603673
Click to expand...
Click to collapse
i could be way off base here but your in fastboot so the CMD should be "fastboot devices". Your screen looks no dif then mine
Are the drivers installed correctly, ie with admin rights, and if so, is the help in the link that works, but requires more time and effort. With that guide, I will install the win 11 and win 10 drivers myself.
How to Disable Driver Signature Verification on 64-Bit Windows 8 or 10 (So That You Can Install Unsigned Drivers)
64-bit versions of Windows 10 and 8 include a “driver signature enforcement” feature. They’ll only load drivers that have been signed by Microsoft. To install less-than-official drivers, old unsigned drivers, or drivers you’re developing yourself, you’ll need to disable driver signature enforcement.
www.howtogeek.com
hammered58 said:
i could be way off base here but your in fastboot so the CMD should be "fastboot devices". Your screen looks no dif then mine
Click to expand...
Click to collapse
that was correct, now the fastboot finds the device while in BL, thank you!
Title: Online ADB Installer - Fast and Easy ADB Installation with Automatic Driver Downloads
Hello XDA community!
Today, I'd like to introduce you to the Online ADB Installer project which provides a fast and easy ADB installation for your Android devices. With this project, you can easily install ADB and Fastboot tools and use other necessary tools to develop your Android devices.
Online ADB Installer is designed specifically for Windows users and brings together all necessary files in a single interface to speed up the installation process. It also automatically downloads and installs the latest ADB drivers and Google USB drivers from Google servers, ensuring that you have the most up-to-date drivers for your Android device.
It's very simple to use: just run the program, connect your device to your PC with a USB cable, and complete the installation process. That's it!
You can access the project's source code from our Github page: https://github.com/celalizolu/Online-ADB-Installer
Online ADB Installer features:
- Fast and easy ADB installation
- Brings together all necessary files in a single interface
- Automatically downloads and installs the latest ADB drivers and Google USB drivers from Google servers
- Designed specifically for Windows users
- Easy to use
We would be happy if the project is supported by the XDA developer community. If you have any questions or feedback, we would be grateful for your support and please write to our discussion section.
Thank you for your interest in Online ADB Installer!
AFAIK those installers exist like sand on the sea. Also published here at XDA.
Worst mistake is you simply download and install ADB driver provided by Google WHAT ARE MEANT TO BE USED ON GOOGLE BRANDED PHONES ONLY.
Take note that all OEMs provide a specific ADB driver suitable to their phones.
jwoegerbauer said:
AFAIK those installers exist like sand on the sea. Also published here at XDA.
Worst mistake is you simply download and install ADB driver provided by Google WHAT ARE MEANT TO BE USED ON GOOGLE BRANDED PHONES ONLY.
Take note that all OEMs provide a specific ADB driver suitable to their phones.
Click to expand...
Click to collapse
Hello,
Thank you for your message. I understand that there are many types of ADB driver installers available and they are published on sites like XDA. However, what sets my script apart from other installers is that it automatically retrieves and installs the latest version of ADB drivers from Google servers, thus ensuring that they remain up-to-date. Additionally, it downloads and installs the latest Google USB drivers from Google servers, which simplifies the process of Windows devices recognizing your device. My script is minimalist and supports many Android devices.
Nevertheless, in some cases, you may need to download and install the original drivers for your device. Therefore, it is important for users to follow the necessary steps to ensure they install the correct drivers and recognize their devices.
Best regards,
{
"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"
}
Latest generic ADB / Fastboot drivers can be fetched from here
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
and not from Google servers.
Madam, we obtain the latest drivers from the website that you have mentioned. As Android is owned by Google, the description referred to Google servers. Therefore, there is no problem.
Android isn't owned by Google, and never was. Android is OPEN SOURCE!
jwoegerbauer said:
Android isn't owned by Google, and never was. Android is OPEN SOURCE!
Click to expand...
Click to collapse
https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip
This above is the download link offered by your link in post #5.
Looks like a Google Server, doesn't it?
Android is Open Source and managed by the Open Handset Alliance, which is led by Google. So, the statement "Android is owned by Google" is an indirect correct answer.
WoKoschekk said:
https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip
This above is the download link offered by your link in post #5.
Looks like a Google Server, doesn't it?
Click to expand...
Click to collapse
Indeed,
dl.google.com is host for these
ns1.google.com
216.239.32.10
ns2.google.com
216.239.34.10
ns3.google.com
216.239.36.10
ns4.google.com
216.239.38.10
Thor Flash UtilityThis is a flash utility for Samsung devices, made from scratch in C#.
To run this, you must have .NET 7 runtime installed on your computer.
Latest release can be found on GitHub - https://github.com/Samsung-Loki/Thor
This tool was tested and works flawlessly, I'm open for any bug reports.
List of platforms1) Linux (USB DevFS method)
2) Windows (not implemented)
3) Mac OS (not implemented)
How's it different from Heimdall?Fun fact: Official Odin for Linux works using DevFS, and people report it working when Heimdall didn't.
1) Is able to do NAND Erase All (aka erase userdata) and erase any partition, given the length.
2) Ability to shutdown and reboot into Odin mode (not supported on every device)
3) Not using a USB transfer library and doing it natively for best results
4) Extended the PIT parser with new information being discovered
5) Can flash directly from an Odin .tar / .tar.md5 archive
6) Works with .lz4 files directly without manual extraction
7) Implemented EFS Clear and Bootloader Update options in Odin
8) Is able to change the sales code of the device
Support meIf you would like to support me and my team, donate here.
We're a team of teens (at age of 14-15) making random projects for fun.
Current list of commandsThe up-to-date list of commands can be found here.
Usage guideA comprehensive usage guide can be found here.
What devices were tested?1) SM-M205FN/DS from 2019 0x00030000 (Unknown1: 0, Unknown2: 0, Version: 3)
2) SM-G355H/DS from 2014 0x00020000 (Unknown1: 0, Unknown2: 0, Version: 2)
Frequently Asked Questions1) A fatal error occurred. The required library something could not be found.
This is a Linux Package Mixup, use this as reference.
2) What happened to original Thor (or Hreidmar)
This is a rewrite of Thor written from scratch, so I could implement the native USB communication.
Also, the old codebase was severely flawed in my opinion. I archived it here.
CreditsTheAirBlow for Thor Flash Utility
Benjamin-Dobell for documenting much of the Odin protocol
[reserved]
real
Bro finally revived good old Thor/Hreidmar
@TheAirBlow Thx.
Didn't test it yet but just a hint:
{
"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"
}
Link leeds to wrong version acc to your post #1, or doesn't it?
bmwdroid said:
@TheAirBlow Thx.
Didn't test it yet but just a hint:
View attachment 5938745
Link leeds to wrong version acc to your post #1, or doesn't it?
Click to expand...
Click to collapse
Yeah, that was an accident. It is indeed .NET 7
hello, please help me flash and revive the Samsung a12 (125FN) device.
the fact is that I don 't have a pc (
I only have an arm7 phone )
Heimdall-frontend does not work in Linux Deploy in my device, it cannot flash the super partition.. tell me what else can be done in my situation!??)
ilshatiko1988 said:
hello, please help me flash and revive the Samsung a12 (125FN) device.
the fact is that I don 't have a pc (
I only have an arm7 phone )
Heimdall-frontend does not work in Linux Deploy in my device, it cannot flash the super partition.. tell me what else can be done in my situation!??)
Click to expand...
Click to collapse
This tool could probably be used in Termux or in a root shell if you somehow could install .NET 7 Runtime. But, it does require the phone to be rooted for Thor to be able to access the USB devices connected. And additionally, you need a (first phones USB) to (second phone's USB) cable to connect, or have some adapter to make it work.