Hey All,
So I went to push an app from Eclipse to my XT910 (CM10.1, via Safestrap, Rom Slot 1), and found that it wasn't detected by Eclipse, or ADB. Debugging is enabled, and I have the official Motorola drivers installed
When rebooting into the Stock Rom, i was able to use ADB, and push the App to my phone. Is this Regular behavior, or am i missing Something?
There are even another method to push the apps to ya RAZR rather then pushing it from adb or eclipse
Thanks!!
Please hit the thanks button if i helped ya in anyways !!!
anurag.dj2u said:
There are even another method to push the apps to ya RAZR rather then pushing it from adb or eclipse
Thanks!!
Please hit the thanks button if i helped ya in anyways !!!
Click to expand...
Click to collapse
Sorry, let me clarify. I am writing an app in eclipse, so it's not an apk. What other method is there to push this app to the phone, and still allow me to debug via eclipse?
BarrelRolls said:
Sorry, let me clarify. I am writing an app in eclipse, so it's not an apk. What other method is there to push this app to the phone, and still allow me to debug via eclipse?
Click to expand...
Click to collapse
About the debugging i have no idea because i aint no dev but how ya can push apps to phone is just simple method
1- open root explorer or download from play store if ya don't have
2- then copy the apk from ya internal or external sd card
3- paste it into the data ( root ) and fix the permission
4- reboot
5- profit
Thanks!!
Please hit the thanks button if i helped ya in anyways !!!
anurag.dj2u said:
About the debugging i have no idea because i aint no dev but how ya can push apps to phone is just simple method
1- open root explorer or download from play store if ya don't have
2- then copy the apk from ya internal or external sd card
3- paste it into the data ( root ) and fix the permission
4- reboot
5- profit
Thanks!!
Please hit the thanks button if i helped ya in anyways !!!
Click to expand...
Click to collapse
Okay, so again, it's not an Apk. And it needs to run through adb for debugging purposes. (eclipse compiles, and data is sent 'back and forth' between device and eclipse)
Does it show in the notification that debugging is on.?
Also what CM10.1 build are you on?
I tried using and it didn't ran the first time. However I disabled & then enabled it back and it worked flawless this time.So thats not a bug.
Sent from my XT912 using Tapatalk 2
neo.ank said:
Does it show in the notification that debugging is on.?
Also what CM10.1 build are you on?
I tried using and it didn't ran the first time. However I disabled & then enabled it back and it worked flawless this time.So thats not a bug.
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I do get the notification, and it's the 05/07 nightly.
Yesterday I set up a vm running Ubuntu 12.04, and tested adb from there, and it worked, which would suggest a driver issue with windows, but seeing this happens with both my desktop and laptop, I'm not too sure.
BarrelRolls said:
Yeah, I do get the notification, and it's the 05/07 nightly.
Yesterday I set up a vm running Ubuntu 12.04, and tested adb from there, and it worked, which would suggest a driver issue with windows, but seeing this happens with both my desktop and laptop, I'm not too sure.
Click to expand...
Click to collapse
That might be cause you installed the drivers from the same place to both your machines. Since the notification turns on, it suggests nothing is wrong at the phone side.
Re-download the drivers and try re-installing.
neo.ank said:
That might be cause you installed the drivers from the same place to both your machines. Since the notification turns on, it suggests nothing is wrong at the phone side.
Re-download the drivers and try re-installing.
Click to expand...
Click to collapse
Already done. I've used both the official Motorola drivers, and the Google drivers. No luck there.
Related
Hello im trying to use my tbolt as a mas storage device but my computer wont recognize my phone but when i try using the htc sync it will work any ideas tried uninstalling htc sync and the drivers but no luck any ideas on how i can get my computer recognize my phone as a mass storage by the way im using xp sp 3.
No guarantees, but have you tried downloading the android sdk and choosing to install the usb drivers?
letzgostate said:
No guarantees, but have you tried downloading the android sdk and choosing to install the usb drivers?
Click to expand...
Click to collapse
i think i tried already but not sure ill try with the android sdk again.
Did you install all the drivers that are on the cdfs partition when you plugged in the phone?
Sent from my ADR6400L using XDA Premium App
You need to download the sync drivers.
http://www.htc.com/us/support/thunderbolt-verizon/downloads/
ScoobarSTI said:
You need to download the sync drivers.
Click to expand...
Click to collapse
Those are the sync drivers im using but no luck yet tried to uninstall and reinstall but no luck.
nerozehl said:
Did you install all the drivers that are on the cdfs partition when you plugged in the phone?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
On this one i think i installed all them the issue here is that when i plug my phone it let me know that new hardware has been found then it starts with the installation some will install but i think there is one or two the just sit searching but nothing happens and then i try to closed out but it freezes up on me and when i turn off debugging then it closes out but if i try to install them with debugging off nothing comes up.
another thing i used my phone with acomputer runnig windows 7 and it worked so im guessing its a prblem with xp
I think pdanet has the drivers when you install it if you don't know how to manually add them.
Sent from my Thunderbolt using XDA Premium App
I don't know if this will work for you, but it worked for me...
When you plug your phone in via a usb cable, you will see a Verizon Mobile drive pop up on under "My Computer"
If you open it, there is a folder in there called DRV. There is a file called something like WM_driver installer. I installed that.
Then I go to my phone chose to connect as a disk drive (I have mine set to charge only by default).
Then I click on my removable disk and I can see my phone's data then.
Dnakaman said:
I don't know if this will work for you, but it worked for me...
When you plug your phone in via a usb cable, you will see a Verizon Mobile drive pop up on under "My Computer"
If you open it, there is a folder in there called DRV. There is a file called something like WM_driver installer. I installed that.
Then I go to my phone chose to connect as a disk drive (I have mine set to charge only by default).
Then I click on my removable disk and I can see my phone's data then.
Click to expand...
Click to collapse
ill try it tonight lets see if it work
Alright, you need to be able to have the drivers setup and everything correctly because I'm not offering support on this. Sorry but I have alot of stuff to maintain so I can't always help. I'll try but I would prefer the community support each other too. (you also need tgps launcher already installed so if you havent rooted, I dont think you will be able to do this.)
Anyway: you need to get the .apk file you want to install and just put it into the directory and name it A.apk b.apk c.apk d.apk and so on. I will have it install up to 26 apps (all the way up to z) then you can remove and start over.
Script download:
here
I will probably update it eventually but right now it's supposed to be very basic.
Manual instructions:
All you need to do is use adb install appname.apk
Indirect said:
Alright, you need to be able to have the drivers setup and everything correctly because I'm not offering support on this. Sorry but I have alot of stuff to maintain so I can't always help. I'll try but I would prefer the community support each other too. (you also need tgps launcher already installed so if you havent rooted, I dont think you will be able to do this.)
Anyway: you need to get the .apk file you want to install and just put it into the directory and name it A.apk b.apk c.apk d.apk and so on. I will have it install up to 26 apps (all the way up to z) then you can remove and start over.
Script download:
here
I will probably update it eventually but right now it's supposed to be very basic.
Click to expand...
Click to collapse
Basically, for those a little familar with ADB, they didn't block adb install, so you should be able to adb install path\to\app.apk and it will load without an issue. If your not familiar with adb, using xIndirect's method is probably for the best for you.
so the android central sideload wonder machine should work.
In addition, they did not actually close the hole, they just covered it up better. If you sideload anycut, in theory, you can allow any other install. I am going to try it, and let you all know how it goes.
~Leko
gameman733 said:
Basically, for those a little familar with ADB, they didn't block adb install, so you should be able to adb install path\to\app.apk and it will load without an issue. If your not familiar with adb, using xIndirect's method is probably for the best for you.
Click to expand...
Click to collapse
They would have to maintain two versions of their software if they blocked adb install. How are they going to test the apps going into their market.
Sent from my BNTV250 using xda premium
xdahgary said:
so the android central sideload wonder machine should work.
Click to expand...
Click to collapse
Someone try this. You need the apk file of the app you want to install on your cimputer.
http://forums.androidcentral.com/an...-central-sideload-wonder-machine-v-1-2-a.html
Hey all, I cannot get his to work because I no longer have usb debugging. I should say I am on a Nook Color not tab. I just thought it would be nice to try non-rooted for a while. I guess I will just re root.
~Leko
lekofraggle said:
In addition, they did not actually close the hole, they just covered it up better. If you sideload anycut, in theory, you can allow any other install. I am going to try it, and let you all know how it goes.
Click to expand...
Click to collapse
I have AnyCut installed and created a shortcut to app settings. I reset the "Install from unknown sources" to be checked and then tried installing an app from the Amazon Market. When the package manager ran I got the new will not install dialog. Dang! So I launched the app settings again and noticed that the unknown sources box was unchecked. I checked it again, closed, and relaunched the settings window. The option is unchecked again. Grr....
Installing apps from the Android Market works just fine though, as it does not require the package installer to install an app.
Am I understanding this correctly? So even with un-rooted NT that has updated to 1.41 we can use this method to sideload? I so hope I am understanding this correctly. If so thank you so very much!!!!! If not thanks anyway for helping me learn!!!!!
I have been unable to clear and reset my drivers for the NOOK Tablet.
I've uninstalled and reinstalled but I must not have the right drivers.\
I'm running Win 7 64bit.
Any link would be appreciated.
GreenFuzzer said:
Am I understanding this correctly? So even with un-rooted NT that has updated to 1.41 we can use this method to sideload? I so hope I am understanding this correctly. If so thank you so very much!!!!! If not thanks anyway for helping me learn!!!!!
Click to expand...
Click to collapse
BUMP, as I was wondering this myself.
I understand how to use adb, but how do I get the Nook Tablet with 1.4.1 in debugging mode? I can't install the tgps launcher apk because it says it is not a Nook Store app. My Nook was previously 1.4.0 and rooted with android market and lots of apps installed. I have no problem with the new side loading method, but I need to figure out how to re-enter USB debugging mode.
Ugh, my Nook just updated to the dreaded 1.4.1 version. I tried the script from XDA and ran it with the command prompt, but it says "error no decide found", even though my Nook Tablet is plugged into my Windows XP Machine. Any ideas why this is happening?
I'd greatly appreciate it. Thanks!
Also, I got the script from here: http://forum.xda-developers.com/showthread.php?t=1407023 . I run the Sideload.bat file which usually doesn't run until an Android device has been found, and in MS Dos it says: C:\Sideload>adb wait-for-device . And yet when if I were to install an apk residing in the Sideload folder via Command Prompt, it says no device found.
szumlanski said:
I understand how to use adb, but how do I get the Nook Tablet with 1.4.1 in debugging mode? I can't install the tgps launcher apk because it says it is not a Nook Store app. My Nook was previously 1.4.0 and rooted with android market and lots of apps installed. I have no problem with the new side loading method, but I need to figure out how to re-enter USB debugging mode.
Click to expand...
Click to collapse
Scrap that. I thought I had to re-download the apk file. I realized that it is installed as a device app. Once I entered debugging mode I was able to sideload apps onto 1.4.1 using the instructions.
Now I would love to get Android Market working again...
Indirect said:
Script download:
Click to expand...
Click to collapse
Is there something available for Mac users? I don't have access to any Windows system for over a week.
Also, I was wondering if anyone out there has had success access the Android Market after using this new script? Hopefully some of the root teams/specialists out there can find use a better answer that going by to sideloading.
szumlanski said:
Scrap that. I thought I had to re-download the apk file. I realized that it is installed as a device app. Once I entered debugging mode I was able to sideload apps onto 1.4.1 using the instructions.
Now I would love to get Android Market working again...
Click to expand...
Click to collapse
Ok, so how DID you get it into debugging mode?
geonjay said:
Ok, so how DID you get it into debugging mode?
Click to expand...
Click to collapse
If you rooted 1.4.0, you would have used tgps launcher downloaded over the air. Once you run (install) the tgps launcher, it remains in your android apps installed on the Nook tablet after the 1.4.1 is installed by B&N. Just unplug your USB cable, run tgps launcher, go into te development settings, enable two debugging options, disable auto mount. Then when you plug in USB it should pop up a notification that you are in debugging mode.
Do "adb devices" from a command prompt. If your device is found, you can adb install apps.
so this won't work for unrooted? got my mom this for xmas, we had 1.4.0 and started sideloading apps...then outta nowhere today, the OTA came through and now i can't do anything. when i try this method, it tells me device not found. it doesn't show up under adb devices, either.
jayochs said:
so this won't work for unrooted? got my mom this for xmas, we had 1.4.0 and started sideloading apps...then outta nowhere today, the OTA came through and now i can't do anything. when i try this method, it tells me device not found. it doesn't show up under adb devices, either.
Click to expand...
Click to collapse
Looks like your only option will be to manually downgrade to 1.4.0 and load all the apps you want. You can also prevent OTA update to 1.4.1. Search the forums for the instructions. That sucks.
Alternatively, wait and see if a 1.4.1 root comes out.
xdahgary said:
Someone try this. You need the apk file of the app you want to install on your cimputer.
http://forums.androidcentral.com/an...-central-sideload-wonder-machine-v-1-2-a.html
Click to expand...
Click to collapse
Thanks, this works great. I know there is a way to root and install google apps on 1.4.1 now, but I'm fine with this since I don't have to go through the process of losing and then restoring all the apps and books I have loaded.
Just like another person mentioned, all one has to do is have NT Hidden Settings or tgps_launcher installed prior to the upgrade to be able to enable USB debugging.
OK, I screwed the pooch on this one and if I'm correct, I'll have to undo everything and start over. I used DeanGibson's directions for rooting to 1.4.1. I could never get sideloading to work, so in a moment of dumb, I uninstalled NThiddensettings so I could reinstall a newer version. When I did that, I guess I lost USB debugging and enabled automount. So now, all Windows will do is add Nook Tablet as a device. If I'm correct, since I can't sideload, the only thing I can do to get it back USB debugging is undo everything and start over. Of course, I could wait until NThiddensettings is on Android Market, but that will probably never happen.
I feel for ya Tel.
I may find myself in your shoes before all is said & done.
Sent from my BNTV250 using Tapatalk
Just go to http://li362-167.members.linode.com/...s_launcher.apk in your browser and install. You will be able to activate usb debugging at that point.
rodorr
rodorr said:
Just go to http://li362-167.members.linode.com/...s_launcher.apk in your browser and install. You will be able to activate usb debugging at that point.
rodorr
Click to expand...
Click to collapse
I'm was blocked from sideloading anything since I couldn't enable USB debugging. I have just fixed it though. I looked in my Apps and saw an app titled AppMenu. That let me get to my development settings and turn off auto mount and enable usb debugging. I still can't get NThiddensettings to let me install from unknown sources like it should, but at least I can sideload now.
I'm glad you got it working, although downloading from a link on a web page does not require side loading, as does downloading from another local computer using a usb connection.
rodorr
rodorr said:
I'm glad you got it working, although downloading from a link on a web page does not require side loading, as does downloading from another local computer using a usb connection.
rodorr
Click to expand...
Click to collapse
Oh, I can download all I want, but without being able to enable usb debugging and disabling automount, I couldn't install anything. In fact, I'm still being blocked from installing any apps directly, they have to be installed via adb or Sideload Wonder Machine. I can live without that now that I've gotten usb debugging enabled again.
I guess I'm missing something. Which program enables the ability to install an apk file? I thought an apk file was self installing.
rodorr
rodorr said:
I guess I'm missing something. Which program enables the ability to install an apk file? I thought an apk file was self installing.
rodorr
Click to expand...
Click to collapse
Just because you download an .apk file, doesn't mean it will self install.
Sent from my HTC Inspire "4G" using XDA Premium App
Yeah, but doesn't the "tgps_launcher1.0.apk" file self install?
rodorr
rodorr said:
Yeah, but doesn't the "tgps_launcher1.0.apk" file self install?
rodorr
Click to expand...
Click to collapse
Only apps downloaded through the Google Market will self install.
Well all I know is that the "tgps_launcher 1.0 apk" file I downloaded form the "How to root your Nook Tablet" link installed no problem. Maybe it was from the Google Market, I don't remember.
rodorr
If, like me, you're one of those persons who used S.onyTablet.S v3.4 [ALLinONE] to update your firmware to a pre-rooted ICS 4.0.3 and lost ADB support afterwards, but are tired of the nagging notification telling you there's an update, do the following:
Use your favorite file explorer app to navigate to /system/app/ and simply rename "Automagic.apk" to something like "Automagic.apk.bak". This will disable those notifications and give you the option of undoing it later-on (remove the ".bak" you placed on the name) WITHOUT using ADB.
Gotta thank condi for the solution to my problem 'cause i actually took the fix right out of his tool's coding, so thanks man!
...and now... to figure-out why my ADB drivers stopped working out of the blue...
The Poetic Vampire said:
...and now... to figure-out why my ADB drivers stopped working out of the blue...
Click to expand...
Click to collapse
If you installed and used Condi's UMS inSD and UMS exSD scripts, that may be your problem. After using the USB Mass Storage scripts, I lost use of ADB. I solved the problem by turning on USB debugging, connecting my tablet to my computer via USB, then selecting "Connect as Media Device (MTP)" found at Settings > Storage. I have to do this each time I use the scripts. It appears the UMS scripts interfere with the computer's or ADB's ability to detect devices.
I lost ADB support to...
EDIT: problem solved.
I have just reinstalled the driver manually.
Cat McGowan said:
If you installed and used Condi's UMS inSD and UMS exSD scripts, that may be your problem. After using the USB Mass Storage scripts, I lost use of ADB. I solved the problem by turning on USB debugging, connecting my tablet to my computer via USB, then selecting "Connect as Media Device (MTP)" found at Settings > Storage. I have to do this each time I use the scripts. It appears the UMS scripts interfere with the computer's or ADB's ability to detect devices.
Click to expand...
Click to collapse
I actually haven't used them. The problem is that before ICS, device manager only recognized "Sony tablet S", but now there's also a "Sony_tablet" that has no drivers associated with it and if i try to install the same drivers i used originally... ERROR... so yeah, i've had to manage myself without adb... THE PAAAAAAAIN!!!!!!!!!!!!
scorpio_77 said:
I lost ADB support to...
EDIT: problem solved.
I have just reinstalled the driver manually.
Click to expand...
Click to collapse
In my case, it just reinstalled the same drivers and stayed with the same problem; sad thing is that the costumer took the tablet already so i can't keep testing possibilities.
I lost ADB support also, I also used the tool supplied with Condis program for mounting internal or external memory, I left the wrong one mounted and this stopped the ADB working, I was connecting via USB but I nothing showed.. I eventually after changing the storage mounting option back it worked.
PS to Condi: A little note when connecting to AIO tool to remind people to put the storage into the correct mode would help dzięki za twoją pomoc! :-D
Sent from my Sony Tablet S using xda premium
The Poetic Vampire said:
If, like me, you're one of those persons who used S.onyTablet.S v3.4 [ALLinONE] to update your firmware to a pre-rooted ICS 4.0.3 and lost ADB support afterwards, but are tired of the nagging notification telling you there's an update, do the following:
Use your favorite file explorer app to navigate to /system/app/ and simply rename "Automagic.apk" to something like "Automagic.apk.bak". This will disable those notifications and give you the option of undoing it later-on (remove the ".bak" you placed on the name) WITHOUT using ADB.
Gotta thank condi for the solution to my problem 'cause i actually took the fix right out of his tool's coding, so thanks man!
...and now... to figure-out why my ADB drivers stopped working out of the blue...
Click to expand...
Click to collapse
I actually have a non rooted ICS that says update available. Even after factory reset. But thanks for the info maybe ICS will let me disable it under apps.
Sent from my Sony Tablet S using xda app-developers app
OCedHrt said:
I actually have a non rooted ICS that says update available. Even after factory reset. But thanks for the info maybe ICS will let me disable it under apps.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Then why not install? It could be rev2 I kniw italy and germany have had an ics revision allready
Chur
**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: