Yesterday i've rooted my Tab S with AiO tool. Everything went fine, i've also install some tweaks and mods with this tool. But today i cant get ADB connection working with my tab s and i dont know why. I think this is something with gscripts lite, because i've install some SD card tweaks and when i check or uncheck some scripts in the gscripts menu, computer shows Tab S on the list, but i cant reinstall drivers.
The other problem is that i reinstall gscripts lite and there are no scripts on the list. Can somebody know how i can get those scripts on the list back? Or just a command to write on the list?
Related
Mods, if this belongs elsewhere, feel free to move it.
I read many many threads about people's problems with adb on the vibrant and while there were no individual threads that matched exactly, little pieces from many helped me in my situation; in case someone else experiences what I had, this is what I did to fix it.
Environment:
Win7 Professional N x64
Vibrant (SGH-T959:2.1-update1/ECLAIR/UVJI) (this was the leaked ROM mid Sept)
Samsung x64 drivers from TGA_Gunnman's thread (forum.xda-developers.com/showthread.php?t=728929)
USB Debugging enabled
Problem:
I was able to get all the components of the phone recognized in device mgr & I was able to mount both the internal SD and my 8gb external SD cards, read & write to them with ease; I was even able to flash the leaked ROM via ODIN. I was NOT able to get adb to connect to my device.
C:\vibrant\adb devices
List of devices attached
T9596f3efa91 offline
I tried in recovery mode, no dice.
I had tried Droid Explorer, it was unable to find my device as well.
I had read somewhere that it was a driver problem, although dev mgr wasn't complaining and everything else appeared to be working just fine. One person noted they were able to use the Samsung Moment drivers from JuneFabric's website. I tried to install those drivers and was met with an error during the installation that said windows was unable to locate the file. Uninstalling, rebooting, reinstall (as many times as I had...) had no effect.
I grabbed USBDeview (thanks to masr1979's post in forum.xda-developers.com/showthread.php?t=735534&highlight=masr1979) and uninstalled every android related driver. Rebooted and when prompted for the drivers, tried the moment drivers only to face the same "unable to locate file" error. I got fed up and tried going back to the drivers from TGA_Gunnman's thread which brought
me back to the start. Atleast I was able to mount my sd cards.
Solution:
Not satisifed with this, I went to Samsung's website and found drivers for XP/Vista... i can't for the life of me re-navigate to that download page, but I have uploaded the drivers here.
After running USBDeview to nuke everythign samsung/android related (again) and rebooting, I plugged my phone back in - pointed it to the extracted folder for the attached drivers, ignored the "unsigned drivers!" error for all three devices and re-tested DroidExplorer. SUCCESS! Droid Explorer found my phone and adb (console) also shows my device attached! Everything is golden.
Summary
Random-assed drivers found on Samsung's site for XP/Vista (attached) matched what my Vibrant wanted on Win7x64 in order to get data and debugging connectivity.
Thanks
(edited for the attachment which didn't stick? & stupid 5min wait to post )
Hello;
This was my first time installing a Rom. I was fed up with my phone responding slowly and in time jams.
1-The first thing I did was install cwm recovery v6.0.2.7.
2-Then use the S3 tool kit available in xda to make a backup of all except system apps and internal storage data and it was stored in a .bak file. So that games and other apps keep their info as it is a hassle to start from the beginning.
3-Installed CM 10.1 nightly used in the instructions provided here.
All is okay up to here.
4-Tried to restore apps and app data through S3 tool kit but it won't display the data in the phone. I did enable the usb debugging on the cm10.1 (by pressing 7 times on the build name to enable the developers option and enabling usb debugging). I had the same problem when trying to do the backup in step 2, but it connected through the adb mode. This problem is that when ever I connect a device via usb windows installs the driver so every time I connect my phone windows installs the drivers.
5- When step 4 did not work I tried to restore using Holo Backup but no use no able to connect through to adb mode.
I can access the phone storage but I believe the appropriate drivers are not running when using the restore programs even though they are installed.
So the questions are:
1- Is there a way to fix the connection to be able to use S3 unified tool kit or if any one has dealt with the same problem?
2- Is there a way to restore the .bak file via cwm recovery?
3-For future use; An app or program that can be stored in the phone to avoid the use of a PC. The app or program would back-up contacts, sms text, apps and app data into the virtual sd or cloud to avoid deletion when "wipe data/ factory reset" after installing a rom.
I look forward to your replies.
Thank you.
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
wststreet said:
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
Click to expand...
Click to collapse
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
sub-80 said:
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
Click to expand...
Click to collapse
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
sub-80 said:
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
Click to expand...
Click to collapse
Tried ADB wifi but no success the pc says that there are no adb devices.
Also tried PDANet+ to install the drivers but software does not see the s3.
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
JJEgan said:
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
Click to expand...
Click to collapse
removed the .bak extension and placed it in the download folder of my virtual sd folder and pressed restore on cwm but nothing happened.
Could be because the backup is password protected?
Also tried to restore the file via titanium backup through the extract simple adb with and without the extension but only says analyzing file and remains that way for hours.
**New** Root Access is Now Required!
Download:
- G900T_OF6_Batch_Debloater_&_App_Freezer
Instructions:
1. Extract the G900T_OF6_Batch_DeBloater & App Freezer folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click DeBloater.bat to launch the program.
4. Select "Light," "Medium," "Extreme", or "Freeze Apps"**and press "Enter."
5. Grant Root Access if prompted by your device and press "Enter" to begin.
6. Once complete press "Enter" to return to the Main Menu and select ***"Reboot Device."
7. Last, select "Exit" from the Main Menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use notepad++ or other text editor to view/edit the lists of affected apps in the debloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
muniz_ri said:
Download:
- G900T_OF6_Batch_DeBloater
Instructions:
1. Extract the G900T_OF6_Batch_DeBloater folder onto your desktop.
2. Boot into *TWRP, Press "Mount" and make certain that "system" is checked.
3. Connect your phone to your **PC while still in TWRP and double click on the DeBloater.bat file.
4. Select "Light," "Medium," or "Extreme" debloating (see DeBloater.bat file for list of removed apps).
*I used TWRP 2.8.6.0 (could not get TWRP 2.8.7.0 to connect to PC).
** Make certain that you have Samsung Drivers installed.
Click to expand...
Click to collapse
The Tmobile my account app shows up in my installed apps but no where to be found in system/app or priv_app any ideas ?
Sent from my SM-G900T using XDA Free mobile app
dzhowandai said:
The Tmobile my account app shows up in my installed apps but no where to be found in system/app or priv_app any ideas ?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Its likely under a different name. I used the extreme option and its no longer installed.
It's a no go fir me with same result. Is your rom deodexed or does it make any difference?
Sent from my SM-G900T using XDA Free mobile app
dzhowandai said:
It's a no go fir me with same result. Is your rom deodexed or does it make any difference?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Not deodexed.
Not working for me either:
I just get:
" rm: can't remove '/system/app/xxxx': No such file or directory"
poncespr said:
Not working for me either:
I just get:
" rm: can't remove '/system/app/xxxx': No such file or directory"
Click to expand...
Click to collapse
To clarify does the PC recognize the device while in twrp and the tool runs successfully? But you get one or a few of the above error msg's or an extensive list of apps that it cannot remove? Are you on a completely stock rom that is not already debloated?
muniz_ri said:
To clarify does the PC recognize the device while in twrp and the tool runs successfully? But you get one or a few of the above error msg's or an extensive list of apps that it cannot remove? Are you on a completely stock rom that is not already debloated?
Click to expand...
Click to collapse
I went to far as to reinstall samsung drivers, google drivers.
I can check adb devices and see it is there.
Also, this is without any modification to your batch file.
poncespr said:
I went to far as to reinstall samsung drivers, google drivers.
I can check adb devices and see it is there.
Also, this is without any modification to your batch file.
Click to expand...
Click to collapse
Did the tool delete any apps? The extreme option includes over 90 apps. How many "could not find" msgs did you see? Also, which twrp version did you use?
muniz_ri said:
Did the tool delete any apps? The extreme option includes over 90 apps. How many "could not find" msgs did you see? Also, which twrp version did you use?
Click to expand...
Click to collapse
I chose extreme debloat and could not see any app succesfully removed.
I ended up using a debloater for the G900F via recovery, but it does not remove the Tmo bloat.
Anyway, I thank you for sharing your work.
poncespr said:
I chose extreme debloat and could not see any app succesfully removed.
I ended up using a debloater for the G900F via recovery, but it does not remove the Tmo bloat.
Anyway, I thank you for sharing your work.
Click to expand...
Click to collapse
The tool will not show successfully removed apps only failed apps.
Glad you found another method. I am just trying to understand why it works for me but not for you and another user so that I can either modify the tool or provide additional instructions.
muniz_ri said:
The tool will not show successfully removed apps only failed apps.
Glad you found another method. I am just trying to understand why it works for me but not for you and another user so that I can either modify the tool or provide additional instructions.
Click to expand...
Click to collapse
I tried quite a few times. Installed TWRP 2.8.6.0.. I re-downloaded drivers. I did a system restore on my windows 7 64 PC to make sure no other programs were conflicting.
Might give it a try again later on. I really want to get rid of Tmobiles useless app.
Edit:
Reinstalled drivers once more, used a different USB port, and selected minimal debloating (since I already removed most of the stuff I did not want)
and it finally worked. No more Tmobile branded bloat on my GS5.
Thank you again.
poncespr said:
I tried quite a few times. Installed TWRP 2.8.6.0.. I re-downloaded drivers. I did a system restore on my windows 7 64 PC to make sure no other programs were conflicting.
Might give it a try again later on. I really want to get rid of Tmobiles useless app.
Edit:
Reinstalled drivers once more, used a different USB port, and selected minimal debloating (since I already removed most of the stuff I did not want)
and it finally worked. No more Tmobile branded bloat on my GS5.
Thank you again.
Click to expand...
Click to collapse
I suspected that was the case so I have modified the tool to not run unless the device is recognized by the PC.
I can use "adb devices" to get adb to recognize my device when it's booted normally and usb debugging is checked (also checked always allow authorization), but when it booted to TWRP 2.8.6.0 and Mount system adb cannot recognize it ("adb devices" returns empty list) and thus the script cannot run (stops at the "waiting for device" part) . Any help?
Im having an issue with MTP not installing on Windows 7, tried many fixes and nothing is working. Really want to use this thing! Has anyone had this issue and know a possible fix?
Master619 said:
I can use "adb devices" to get adb to recognize my device when it's booted normally and usb debugging is checked (also checked always allow authorization), but when it booted to TWRP 2.8.6.0 and Mount system adb cannot recognize it ("adb devices" returns empty list) and thus the script cannot run (stops at the "waiting for device" part) . Any help?
Click to expand...
Click to collapse
Only thing that comes to mind are samsung drivers, try install or reinstall.
Edit: played around with it....connect your phone while in recovery to your PC and run Windows Update. It should give you the option of installing Android ADB Driver.
MortTheBeast said:
Im having an issue with MTP not installing on Windows 7, tried many fixes and nothing is working. Really want to use this thing! Has anyone had this issue and know a possible fix?
Click to expand...
Click to collapse
What I did is I disabled MTP in TWRP.
You disabled in TWRP and windows installed MTP? Because I tried that and windows won't even attempt to install MTP and phone doesn't get recognized.
MortTheBeast said:
You disabled in TWRP and windows installed MTP? Because I tried that and windows won't even attempt to install MTP and phone doesn't get recognized.
Click to expand...
Click to collapse
I tried Samsung drivers first, then used Google drivers. Still after a coulple of seconds I would always get an error 10 saying "This device could not start".
Tried downloading MTP drivers from microsoft somewhere, and that did not work either so finally decided to disable MTP on TWRP.
But, the ABD device was still recognized after disabling ATP.
poncespr said:
I tried Samsung drivers first, then used Google drivers. Still after a coulple of seconds I would always get an error 10 saying "This device could not start".
Tried downloading MTP drivers from microsoft somewhere, and that did not work either so finally decided to disable MTP on TWRP.
But, the ABD device was still recognized after disabling ATP.
Click to expand...
Click to collapse
I got nothing... here's crossing my fingers that someone is working on a root method, or else I will have to dump 5.1.1 and go with 5.0. :good:
I've searched online and found a few articles. I've tried following them but the steps say to change the USB setting from charging the device to transfer files (MTP) but I've unplugged and replugged my phone twice and there's no option for file transfer.
I've also downloaded Minimal ADB and FastBoot and the sites say to extract it into the root C drive but it didn't come in a zipped folder and when I opened it it showed up as the command prompt window. Typing in the command it says after you've installed it, it said it couldn't find what I was looking for.
So I deleted it and installed another one this one came in a zipped folder so I extracted it to the C drive and then the site said to open command prompt in the folder but I clicked on empty space and a few of the files and applications in there but no option to open command prompt came up.
I know I'm probably doing something wrong so I am looking for assistance.
After Package disabler Pro disappeared I really need another disabler app to get rid of Facebook and Chrome and others from my phone.
Thanks.
check out my old thread. There is a more or less a batch script, wich was for S7,
here:
https://forum.xda-developers.com/galaxy-s7/how-to/debloat-galaxy-s7-services-safe-to-t3432967
fromt there you might come up with your own way, that you can post here.
Also I may do something similar on my S10 now.
Aroma installer helps a little, but I don't need those 100 other small spy & bloat apps.
Basically you need a list of all apps installed.
And sort them out.
If you have it rooted, there are multiple apps to remove system apps.
Wait, so you can uninstall apps installed on the system volume without having root? or were these apps that were not installed on the system drive?
Sent from my SM-G973U using Tapatalk
My pc using w10x64, it wont recognize my s10+ exynos. For some strange reason. When i type in adb devices, its not showing my s10+. I did installed samsung usb driver.
Package disabler pro is on playstore now
Hi
Just got my A3. I'm unable to connect with adb to restore my backup. I enabled Dev options and USB debugging and when plugged into USB I get P notification icon and USB debugging connected message in notification. However
adb devices
shows nothing is connected. I notice there is no pop up asking if I want to authorize this computer which is iirc normally what happens.
adb can see my blu g6 phone so that's working. When I connect the A3 as a storage device, with no USB debugging, I can transfer files ok, so USB is working. I have a fresh Android studio install which should have the right sdk. I tried
adb connect <ipaddress>
and got "no connection could be made because target machine actively refused it" I did not refuse, because nothing popped up.
Have rebooted both phone and PC (windows 7)
Any idea what's going on? Thanks
Sent from my G6 using Tapatalk
Follow up: okay I figured out I need to install adb driver because A3 shows up in yellow in device manager. But I can't find a driver that works. I googled xiaomi A3 adb driver and downloaded like five of them from different sites and none worked. When I point windows to the folder where I extracted the driver it says could not find driver for your device.
I'm going nuts. Can someone point to a working driver for Windows 7?
Sent from my G6 using Tapatalk
These always worked for me. If they are not automatically installed for the device, follow the instructions in the video.
https://forum.xda-developers.com/showthread.php?t=2588979
Thanks. I figured out where I went wrong.
Instead of using the "browser file on my computer" and point it to where the driver is, I have to choose "let me select from a list" then "all devices", then select the Android composite adb driver. At least this works on Windows 7.
---
So I restored my back up, I got the pop up to confirm restore my data, and it seemed to run through the restore and took a while, but nothing changed. None of my app data was restored. All apps are still in newly installed state.
It did restore the data in SD storage, so my download folder etc got restored, which I could've done just copying to and from my PC.
What I really want is all the app data restored so I don't have to log back into all the different services and do all the settings again.
I did the back up with
adb backup -all -apk -shared -f allbackup.ab
Shouldn't that have worked?
Sent from my G6 using Tapatalk
From what I remember adb restore does not install *.apk back. It only writes back system and data files. So if you wanna all the app data restored - reinstall all apps manually before and then do adb restore.
On Windows you can sort of semi-automate that process in command prompt:
for %f in (C:\<your pak folder location>\*.apk) do adb install "%f"
Make sure though apk don't have spaces in their names or adb will complain.
qwertysmerty said:
From what I remember adb restore does not install *.apk back. It only writes back system and data files. So if you wanna all the app data restored - reinstall all apps manually before and then do adb restore.
On Windows you can sort of semi-automate that process in command prompt:
for %f in (C:\<your pak folder location>\*.apk) do adb install "%f"
Make sure though apk don't have spaces in their names or adb will complain.
Click to expand...
Click to collapse
I looked at adb logcat and there were a bunch of errors. Looks like it did try to restore app data but failed. Google back up already installed the apks back (except for the ones I side loaded) so that wasn't the problem. It's the app data (settings, etc) that I was hoping to get back
Oh well I just spent an hour setting my apps up again. I hear Google has already deprecated adb backup. Android needs a good non root desktop back up solution, not the cloud backup where you're at the mercy of Google and the individual apps to decide what get backed up.