Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,807,597 Members 51,940 Now Online
XDA Developers Android and Mobile Development Forum

How exactly do I uninstall and reinstall my adb drivers?

Tip us?
 
Astralogic
Old
#1  
Member - OP
Thanks Meter 0
Posts: 82
Join Date: Mar 2012
Question How exactly do I uninstall and reinstall my adb drivers?

I'm trying to fix the "daemon started successfully" problem, but I don't think I'm uninstalling and re-installing the driver correctly, I just uninstall the device from device manager, then plug the phone back in and let it install.


That must be wrong because it's not working. The program I'm trying to use is xUltiamte2.4 to deodex my phone.
 
Astralogic
Old
#2  
Member - OP
Thanks Meter 0
Posts: 82
Join Date: Mar 2012
Quote:
Originally Posted by Astralogic View Post
I'm trying to fix the "daemon started successfully" problem, but I don't think I'm uninstalling and re-installing the driver correctly, I just uninstall the device from device manager, then plug the phone back in and let it install.


That must be wrong because it's not working. The program I'm trying to use is xUltiamte2.4 to deodex my phone.
If anyone has had this problem and fixed can you please tell me how you did it?
 
Antiga Prime
Old
#3  
Senior Member
Thanks Meter 545
Posts: 814
Join Date: Sep 2012
Quote:
Originally Posted by Astralogic View Post
I'm trying to fix the "daemon started successfully" problem, but I don't think I'm uninstalling and re-installing the driver correctly, I just uninstall the device from device manager, then plug the phone back in and let it install.
Why is that a problem? You want the "daemon" to start successfully, ADB won't work if it doesn't... If it stays stuck on that, maybe you have some program interfering/using ADB. Maybe you have some other ADB program open (flashtool) or maybe you use Bluestacks; check your running processes for a running "adb.exe" process and kill it, then try again.

Removing the drivers should should work as you're doing it already, but before connecting your phone, you should reinstall the drivers first. Or, once it's installed, manually update the drivers through the Windows "Device Manager", by locating the "sa0105adb.inf" file manually.

It can be extracted from the drivers installer (the one that comes with Flashtool) with 7zip, or you might find it still in your temp folder.
MB525 - Bayer Camera - Slim-mb526-4.4.2.beta.2.4-UNOFFICIAL-20140120-1830
Sony Xperia TX LT29i - CARBON-KK-UNOFFICIAL_Hayabusa_build7
 
Astralogic
Old
(Last edited by Astralogic; 19th August 2014 at 08:41 AM.)
#4  
Member - OP
Thanks Meter 0
Posts: 82
Join Date: Mar 2012
Quote:
Originally Posted by Antiga Prime View Post
Why is that a problem? You want the "daemon" to start successfully, ADB won't work if it doesn't... If it stays stuck on that, maybe you have some program interfering/using ADB. Maybe you have some other ADB program open (flashtool) or maybe you use Bluestacks; check your running processes for a running "adb.exe" process and kill it, then try again.

Removing the drivers should should work as you're doing it already, but before connecting your phone, you should reinstall the drivers first. Or, once it's installed, manually update the drivers through the Windows "Device Manager", by locating the "sa0105adb.inf" file manually.

It can be extracted from the drivers installer (the one that comes with Flashtool) with 7zip, or you might find it still in your temp folder.
Nothing works, isn't there a better way of deodexing then using this stupid program?

Edit: I have a better question. The only reason I want to deodex is so that I can debloat using this guide, that thread already gives me the list of bloatware, isn't there a way I can just go in and manually delete the bloat? Without have to worry about deodexing in order to get the debloat script to run?
 
WhiteNeo
Old
#5  
WhiteNeo's Avatar
Senior Member
Thanks Meter 597
Posts: 961
Join Date: Feb 2013

 
DONATE TO ME
Quote:
Originally Posted by Astralogic View Post
Nothing works, isn't there a better way of deodexing then using this stupid program?

Edit: I have a better question. The only reason I want to deodex is so that I can debloat using this guide, that thread already gives me the list of bloatware, isn't there a way I can just go in and manually delete the bloat? Without have to worry about deodexing in order to get the debloat script to run?
Actually you can also debloat your rom while its odexed. At least as long as the framework is not changed.

Just do a backup, then get a root file manager and delete the safe to remove apps and their odex files. Reboot afterwards.

The only reason why the debloat script doesn't support odexed roms ia that the odex files are not deleted during the script. (However, it would be easily possible to add these lines)
My work:
  • NeoWave - A fully Z3 themed custom rom for the Sony Xperia V (Link) and Xperia T (Link)
 
Astralogic
Old
#6  
Member - OP
Thanks Meter 0
Posts: 82
Join Date: Mar 2012
Quote:
Originally Posted by WhiteNeo View Post
Actually you can also debloat your rom while its odexed. At least as long as the framework is not changed.

Just do a backup, then get a root file manager and delete the safe to remove apps and their odex files. Reboot afterwards.

The only reason why the debloat script doesn't support odexed roms ia that the odex files are not deleted during the script. (However, it would be easily possible to add these lines)
Could you tell me what folder those files are in that I should delete?
 
Antiga Prime
Old
#7  
Senior Member
Thanks Meter 545
Posts: 814
Join Date: Sep 2012
Quote:
Originally Posted by Astralogic View Post
Could you tell me what folder those files are in that I should delete?
Well, if you were following that guide you would have seen that practically everything it's deleting is in /system/app:

Quote:
delete("/system/app/FBCalendarSync.apk"
The odex files are in the same folder, and have the same name aside from the .odex extension.

Then again, that program sometimes has issues; you could always copy the files from /system/app and /system/framework manually without using ADB to the corresponding folders, after starting the program open the Windows Task Manager and kill of the "adb.exe", and the program will continue running and let you deodex the files. Then you'd just have to figure out how to copy them back which is not hard.

Or you could also try a different deodexing program such as Universal Deodexer V4. I've never used any of those since I've deodexed my ROM with dsixda's Rom Kitchen, for which you'd just need to follow the instructions and then copy the resulting files manually (as you'd have to do in the above mentioned example anyway).
MB525 - Bayer Camera - Slim-mb526-4.4.2.beta.2.4-UNOFFICIAL-20140120-1830
Sony Xperia TX LT29i - CARBON-KK-UNOFFICIAL_Hayabusa_build7
 
Astralogic
Old
#8  
Member - OP
Thanks Meter 0
Posts: 82
Join Date: Mar 2012
Quote:
Originally Posted by Antiga Prime View Post
Well, if you were following that guide you would have seen that practically everything it's deleting is in /system/app:



The odex files are in the same folder, and have the same name aside from the .odex extension.

Then again, that program sometimes has issues; you could always copy the files from /system/app and /system/framework manually without using ADB to the corresponding folders, after starting the program open the Windows Task Manager and kill of the "adb.exe", and the program will continue running and let you deodex the files. Then you'd just have to figure out how to copy them back which is not hard.

Or you could also try a different deodexing program such as Universal Deodexer V4. I've never used any of those since I've deodexed my ROM with dsixda's Rom Kitchen, for which you'd just need to follow the instructions and then copy the resulting files manually (as you'd have to do in the above mentioned example anyway).
I don't mean I want to manually deodex, I mean I want to manually debloat, deleting the appropriate APK and ODEX file from /system/app seems easy enough, but what would I delete (if anything) from the /system/framework folder?
 
Antiga Prime
Old
#9  
Senior Member
Thanks Meter 545
Posts: 814
Join Date: Sep 2012
Quote:
Originally Posted by Astralogic View Post
I don't mean I want to manually deodex, I mean I want to manually debloat, deleting the appropriate APK and ODEX file from /system/app seems easy enough, but what would I delete (if anything) from the /system/framework folder?
I know, I'm just giving you a solution since that program you're using has always given me issues, and even now, knowing that ADB works, it still get's stuck on that "starting ADB daemon" message.

I'm not trying to be rude, but if you're following the guide you'd have noticed that nothing gets deleted from the framework folder. All it tells you are which apps are safe to remove; whichever apps you do end up removing are up to you. I think the Google Talk app is garbage, but someone else might use it, so debloating is also subjective.

Also, you could just as easily do this with Titanium Backup and actually just freeze the app first in case you're not sure about deleting it.
MB525 - Bayer Camera - Slim-mb526-4.4.2.beta.2.4-UNOFFICIAL-20140120-1830
Sony Xperia TX LT29i - CARBON-KK-UNOFFICIAL_Hayabusa_build7
 
WhiteNeo
Old
#10  
WhiteNeo's Avatar
Senior Member
Thanks Meter 597
Posts: 961
Join Date: Feb 2013

 
DONATE TO ME
Quote:
Originally Posted by Astralogic View Post
I don't mean I want to manually deodex, I mean I want to manually debloat, deleting the appropriate APK and ODEX file from /system/app seems easy enough, but what would I delete (if anything) from the /system/framework folder?
I know, manually deodexing that way would cause a bootloop because of missing classes.dex files in every system app.

Some people that dont like the preinstalled Sony apps prefer getting rid of all the bloat and remove SemcGenericUXPRes.apk from framework folder.. And some (or most) of the framework jar files beginning with "com.sony..."
This will of course bring noticeable smoothness increases, but is very likely to cause bugs when not done by experienced users.
And it could cause a bootloop on odexed builds as the odex files in system/app do no longer fit to the framework.
Just for information.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes