Related
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.
Recently got a Fujitsu T-01D and want to know if there is a way to root this phone. Found unlockroot.exe but it seemed to have virus.
Also, on screen capture (not available on this phone), already tried No Root Screenshot It app from Market but it does not work, because the computer does not detect the phone:
http://www.fmworld.net/product/phone/usb/t-01d/download.html
Already installed this official USB driver on the computer, but when the phone is plugged into the comp (via USB debugging mode), the comp still does not detect the phone.
Seems like the computer has problem detecting the phone (both Wins and Mac)
Even the developer of the screenshot app cannot solve the problem
Does anyone know?
P.S. tried another method but still failed:
installed PDAnet on the computer, and then installed PDAnet app from Market to the phone, but the computer still could not detect the phone.
have u press the "turn on USB storage" in the notification bar?
What's the status now? Can you share the unlockroot file for us?
well,you must uninstall the mass storage device in the device manager.
and then the comp will find a unknown device called t-01d,update driver for t-01d.
now comp can detect my t-01d,but i don't find any root tools which really work.
HaoyuWen said:
well,you must uninstall the mass storage device in the device manager.
and then the comp will find a unknown device called t-01d,update driver for t-01d.
now comp can detect my t-01d,but i don't find any root tools which really work.
Click to expand...
Click to collapse
I uninstalled the usb device manager and re-plugged the phone back to the computer and the computer re-installed the driver itself, but the computer still cannot see the phone.
I tested it with the SDK kit ddms tool, it cannot detect the phone
225001gkh said:
I uninstalled the usb device manager and re-plugged the phone back to the computer and the computer re-installed the driver itself, but the computer still cannot see the phone.
I tested it with the SDK kit ddms tool, it cannot detect the phone
Click to expand...
Click to collapse
now i know how to make it work!!!!
open folder .android
【Windows XP】
C:\Documents and Settings\＜login user＞\.android\
【Windows Vista, 7】
C:\Users\＜login user＞\.android\
creat a new txt file under folder .android,write 0x04C5 in the txt file,and then save file as adb_usb.ini.
now comp can detect my phone with ddms tool,and also root tools.
you may download incorrect driver for phone,this is the ADB driver for T-01D.
spf.fmworld.net/oss/usb_driver/t-01d/data/download.html
HaoyuWen said:
now i know how to make it work!!!!
open folder .android
【Windows XP】
C:\Documents and Settings\＜login user＞\.android\
【Windows Vista, 7】
C:\Users\＜login user＞\.android\
creat a new txt file under folder .android,write 0x04C5 in the txt file,and then save file as adb_usb.ini.
now comp can detect my phone with ddms tool,and also root tools.
you may download incorrect driver for phone,this is the ADB driver for T-01D.
spf.fmworld.net/oss/usb_driver/t-01d/data/download.html
Click to expand...
Click to collapse
Thanks! Now my comp can detect the phone. I tried the No Root Screenshot It App from Market:
http://www.lindylabs.com/screenshot_it/
When I plugged the phone to the computer, and launched the enabler software, it went ok because the computer could see the phone.
But after I enabled it from the computer and tried the phone's no root screenshot app to capture the screen, it would capture but the file would not save. I heard the capture sound, but when I looked at the folder there was nothing.
Any way to fix?
well,I tried the no root screen shot it and it didn't work.
i do not know how to fix it.but the screen shot ux trail work on my T-01D.
this is blog link.
liveov.blogspot.com
HaoyuWen said:
well,I tried the no root screen shot it and it didn't work.
i do not know how to fix it.but the screen shot ux trail work on my T-01D.
this is blog link.
liveov.blogspot.com
Click to expand...
Click to collapse
Do you know a solution to make the wifi tethering work on this phone? Most carriers do not seem to able to connect (the 3G signal will disappear when tethering is activated)
225001gkh said:
Thanks! Now my comp can detect the phone. I tried the No Root Screenshot It App from Market:
http://www.lindylabs.com/screenshot_it/
When I plugged the phone to the computer, and launched the enabler software, it went ok because the computer could see the phone.
But after I enabled it from the computer and tried the phone's no root screenshot app to capture the screen, it would capture but the file would not save. I heard the capture sound, but when I looked at the folder there was nothing.
Any way to fix?
Click to expand...
Click to collapse
Hi,
I'm the developer of the "no root screenshot it" application. Please make sure that the phone is DISCONNECTED from the computer when you take the screenshot. If you still have problems, please do the following:
1) start the app
2) goto the 3rd tutorial screen
3) press the menu button
4) send me the error log.
Thanks!
Edward
225001gkh said:
Do you know a solution to make the wifi tethering work on this phone? Most carriers do not seem to able to connect (the 3G signal will disappear when tethering is activated)
Click to expand...
Click to collapse
Unfortunately,wifi tether is a japan only feature for no root devices.
You can find this tip 'A subscription to sp-mode is required to use tethering.'
on the docomo official website:
goo.gl/yCk4g
and docomo don't provide Hong Kong Service.
So waiting for root.
Finally,i am sorry for my English.It may confused you,and i always forget capital letters.
HaoyuWen said:
Unfortunately,wifi tether is a japan only feature for no root devices.
You can find this tip 'A subscription to sp-mode is required to use tethering.'
on the docomo official website:
goo.gl/yCk4g
and docomo don't provide Hong Kong Service.
So waiting for root.
Finally,i am sorry for my English.It may confused you,and i always forget capital letters.
Click to expand...
Click to collapse
Got mine rooted using superoneclick 2.3.1!!!
Is that true?
I always face the false on the step 7. waiting for device and the superoneclick not responding.
What's the model(type) of your phone?
airngkeye said:
Got mine rooted using superoneclick 2.3.1!!!
Click to expand...
Click to collapse
You rooted the T-01d? Can you provide detail steps? many thanks
225001gkh said:
You rooted the T-01d? Can you provide detail steps? many thanks
Click to expand...
Click to collapse
Greeting!~
I rooted my T-01D with this method.
forum.xda-developers.com/showthread.php?t=1461475
Hava a try!
Great! Many thanks. Can somebody post a guide for updating this phone outside Japan after rooting?
Hi.
Anyone managed to get wifi tethering working after rooting?
Hey there,
Here is a list of what I have before I get started.
Samsung Galaxy Tab 10.1 Wifi (P7510)
Android Version - 3.2
Kernel Version - [email protected]#1
Build Number - INFAMOUS TAB 0.1 P7510UEKMM
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
I bought this tablet from a friend who rooted and flashed with the INFAMOUS mod.
I have searched all over the web for an answer and cant find something for this case specifically.
Each time I plug in my tab, my PC tells me that the Hardware ID is missing.
I can see the tablet in my Devices and Printers (displayed as SAMSUNG_android) as well as in my Device Manager. In device manager it says the drivers are up to date and functioning.
What have I tried?
USB Debugging (On and Off)
Clearing cache via recovery mode
Updating drivers via W7 and KIES via Samsung
I have tried following a few threads on installing the KIES software without internet connectivity. However I would rather not use the KIES Software anyway as it is kind of garbage.
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Can anyone point me in the direction of help and me being able to enjoy this tablet?
I hope I have provided enough information. I am a pretty techy person and I understand how to do all of this but it seems like I am missing something really big.
Something to take note of, whenever the tab is plugged in (PC or Wall) there is a red x over the battery symbol and the tab charges very slowly.
Cheers
B
Snugglebutt said:
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
...
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Click to expand...
Click to collapse
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
hope this help
FIXED
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Click to expand...
Click to collapse
Ahhh ha! As soon as I uninstalled the driver that windows found and used the Google Driver that came along with the Android SDK, the tablet was recognized. Alas, I can finally use this tablet.
In the end it was as simple as a driver error, I spent a very long time searching last night and now I just feel silly.
The tablet still shows the red X over the battery symbol, whether I have MTP with USB Debugging on or off. I guess this can be avoided with certain ROMS. Anybody know of a ROM that avoids this?
Thank you all for your immediate responses!
B
Tid bit of info
H. Ess said:
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
Click to expand...
Click to collapse
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
Click to expand...
Click to collapse
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Snugglebutt said:
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Click to expand...
Click to collapse
For honeycomb and many others, debugging is always there. Under the storage option, you have an Additional Settings button usually and it should be present in there. I was always running3.2 until like a couple days ago so surprised its not there. Oh well problem solved lol
I'm having a similar problem with my tab not being recognised by my pc (win7 64) or in kies. It was originally an M380W (Korean) model, which I updated to a P7510. That all went fine, and the tablet works perfectly, except for the fact that my pc no longer sees it when it's plugged in. I tried uninstalling and reinstalling the drivers, but no dice. I'm going to see if adb works.
Just wanted to share some tips to those who wanted to re-enable the Mass Storage Mode on their Android 4.2.2
1. Connect your phone to a computer (The device will be connected in MTP mode as default)
2. Reboot your phone while connected to the computer
3. Wait until you see the USB icon on your Notification Bar
4. You will now have an option to select Mass Storage henceforth
:cyclops:
I'd appreciate a "THANKS" if this helps you.
reply
SoloRazr said:
Just wanted to share some tips to those who wanted to re-enable the Mass Storage Mode on their Android 4.2.2
I'd appreciate a "THANKS" if this helps you.
Click to expand...
Click to collapse
well, u can also go to settings --> storage --> [press menu] and select connectivity mode or sth, there u can choose mass storage, usb otg and the stock mtp mode
but thanks anyway (pressed thanks )...
peace bejunk
SoloRazr said:
Just wanted to share some tips to those who wanted to re-enable the Mass Storage Mode on their Android 4.2.2
1. Connect your phone to a computer (The device will be connected in MTP mode as default)
2. Reboot your phone while connected to the computer
3. Wait until you see the USB icon on your Notification Bar
4. You will now have an option to select Mass Storage henceforth
:cyclops:
I'd appreciate a "THANKS" if this helps you.
Click to expand...
Click to collapse
Doesn't work.
So far I have tried everything. It seems mass storage is completely disabled.
vdub12 said:
Doesn't work.
So far I have tried everything. It seems mass storage is completely disabled.
Click to expand...
Click to collapse
no WAY !!
did u tried it my ''solution'' ?! also u can add this to ur build.prop / in sysctl OR make a init.d for..
persist.sys.usb.config=mass_storage,adb (if alredy there change it AND '',adb'' is NOT importrant, it only activates it btw...)
but what for a rom are using???
thanks
thanks
SoloRazr said:
Just wanted to share some tips to those who wanted to re-enable the Mass Storage Mode on their Android 4.2.2
1. Connect your phone to a computer (The device will be connected in MTP mode as default)
2. Reboot your phone while connected to the computer
3. Wait until you see the USB icon on your Notification Bar
4. You will now have an option to select Mass Storage henceforth
:cyclops:
I'd appreciate a "THANKS" if this helps you.
Click to expand...
Click to collapse
Thanks!!! Confirmed working on Legacy Xperia JB 4.3 :highfive:
Nope this does not work as advertised in the OP. Neither is there a "USB mass storage" option anywhere in the device's settings. Thanks anyhow.
Update: still no. I rebooted several times. No joy. I tried rebooting into recovery mode-- disabled if it's connected to a PC. Still no.
SoloRazr said:
Just wanted to share some tips to those who wanted to re-enable the Mass Storage Mode on their Android 4.2.2
1. Connect your phone to a computer (The device will be connected in MTP mode as default)
2. Reboot your phone while connected to the computer
3. Wait until you see the USB icon on your Notification Bar
4. You will now have an option to select Mass Storage henceforth
:cyclops:
I'd appreciate a "THANKS" if this helps you.
Click to expand...
Click to collapse
Will this option work for jelly bean 4.2.1?
No joy. This either never worked or this trick is obsolete. I have plain stock kitkat 4.4 on my phone (htc one google play ed) and mass storage appears to be completely removed now. stuck with sh!tty MTP/PTP that does not permit transfer of non "media" files. Best solution I can see is getting an SFTP client and xfer over wifi. Why oh why is Google turning evil and doing hacker-hostile and becoming as annoying as Apple?
SoloRazr said:
Just wanted to share some tips to those who wanted to re-enable the Mass Storage Mode on their Android 4.2.2
1. Connect your phone to a computer (The device will be connected in MTP mode as default)
2. Reboot your phone while connected to the computer
3. Wait until you see the USB icon on your Notification Bar
4. You will now have an option to select Mass Storage henceforth
:cyclops:
I'd appreciate a "THANKS" if this helps you.
Click to expand...
Click to collapse
MSHYYC said:
No joy. This either never worked or this trick is obsolete. I have plain stock kitkat 4.4 on my phone (htc one google play ed) and mass storage appears to be completely removed now. stuck with sh!tty MTP/PTP that does not permit transfer of non "media" files. Best solution I can see is getting an SFTP client and xfer over wifi. Why oh why is Google turning evil and doing hacker-hostile and becoming as annoying as Apple?
Click to expand...
Click to collapse
I feel you. I stopped using anything i[whatever] for any reason because of the stupidity of the storage and transfer software. Now google is doing it. Must join google+ to give feedback on an app? Seriously? Can't access content on my SD card unless the file type meets an arbitrary set of criteria? I'm just waiting for Ubuntu Touch to be ready for an SGH-T989 and I'll dump google next. Either that, or I go back to a damn flip phone and leave all this crap behind.
@bejunk
thanks for the build.prop suggestion, although i cant get the option "MTP, PTP, UMS" in Storage setting, at least i can use UMS...
here's what my opinion;
using MTP;
-faster data transfer
-less reliable; prone to get "cant copy file, phone not responding"
-and if delete file while in phone, connect to PC the file is still there
using UMS;
-slower data transfer
-more reliable than MTP, in my case its secure, no error unless youre "massaging" your phone (blame cable)
-if delete a file while in phone, connect to PC the file is deleted (which is good, no evidence )
UMS is better than MTP in my case
btw, im GT-i9100G SlimKat 4.4.2 (yes, i know this is Sony section)
nope
not working on asus transformer TF701T , thanks anyway
VannM said:
@bejunk
thanks for the build.prop suggestion, although i cant get the option "MTP, PTP, UMS" in Storage setting, at least i can use UMS...
here's what my opinion;
using MTP;
-faster data transfer
-less reliable; prone to get "cant copy file, phone not responding"
-and if delete file while in phone, connect to PC the file is still there
using UMS;
-slower data transfer
-more reliable than MTP, in my case its secure, no error unless youre "massaging" your phone (blame cable)
-if delete a file while in phone, connect to PC the file is deleted (which is good, no evidence )
UMS is better than MTP in my case
btw, im GT-i9100G SlimKat 4.4.2 (yes, i know this is Sony section)
Click to expand...
Click to collapse
exactly what i mean, sorry i thought MTP = UMS. sorry my fault
spatchy said:
not working on asus transformer TF701T , thanks anyway
Click to expand...
Click to collapse
add this to build.prop or change if allready there. just try
''persist.sys.usb.config=mass_storage,adb'' (if alredy there change it AND '',adb'' is NOT importrant, it only activates it btw...)
bejunk said:
exactly what i mean, sorry i thought MTP = UMS. sorry my fault
add this to build.prop or change if allready there. just try
''persist.sys.usb.config=mass_storage,adb'' (if alredy there change it AND '',adb'' is NOT importrant, it only activates it btw...)
Click to expand...
Click to collapse
I do not yet have root on my trasformer pad, until last night I thought that UMS was required to get root. I just need to install the fastboot drivers which I thought I had already done. I will update if it turns out I'm wrong (again), all this stuff with the ADB's, fastboot and cmd is confusing me; I have had to root, unroot, wipe, flash etc. loads of times on my galaxy ace but all that had could be done from the phones recovery almost instantly. geuss i'll just have to sort of evolve and get used to it being harder to root and install a recoveries now!
This one worked on my lenovo a369i:
Type these on your Terminal Emulator app:
su
setprop persist.sys.usb.config mass_storage,adb
reboot
Hope this works on yours too.
imanskoi said:
This one worked on my lenovo a369i:
Type these on your Terminal Emulator app:
su
setprop persist.sys.usb.config mass_storage,adb
reboot
Hope this works on yours too.
Click to expand...
Click to collapse
OMG!! After I input the above commands in terminal emulator, my Lenovo K1 doesn't detect USB anymore No USB is detected Because of this, I can't do USB tethering anymore
I am on kaschemme's latest [JB 4.2.2] [CM10.1] ROM. How do I undo the above command ?
Please help me out.
Edit: Nevermind, I did some research and found out, you can put this command to set it back...
su
setprop persist.sys.usb.config mtp,adb
reboot
MTP working
bejunk said:
no WAY !!
did u tried it my ''solution'' ?! also u can add this to ur build.prop / in sysctl OR make a init.d for..
persist.sys.usb.config=mass_storage,adb (if alredy there change it AND '',adb'' is NOT importrant, it only activates it btw...)
but what for a rom are using???
Click to expand...
Click to collapse
Thanks.. a lot .. had a lot of struggle before finding this
Didn't work..
SoloRazr said:
Just wanted to share some tips to those who wanted to re-enable the Mass Storage Mode on their Android 4.2.2
1. Connect your phone to a computer (The device will be connected in MTP mode as default)
2. Reboot your phone while connected to the computer
3. Wait until you see the USB icon on your Notification Bar
4. You will now have an option to select Mass Storage henceforth
:cyclops:
I'd appreciate a "THANKS" if this helps you.
Click to expand...
Click to collapse
Your tip didn't work on my Galaxy Grand Duos, I-9082 running stock rom 4.2.2..
Ahmadhassan92 said:
Your tip didn't work on my Galaxy Grand Duos, I-9082 running stock rom 4.2.2..
Click to expand...
Click to collapse
try to put in the above command in terminal emulator, it seems to work on stock roms...
USB mass storage
Phone Galaxy S4 9505 Android 4.2.2
I use USB mass storage enabler (Mohammad Abu-Garbeyyeh)
Its great thanks!
Works on a PC (Win7)
However I can't see me mounted devices on any set top boxes (Ie: Freebox V5 [ free.fr ] )
It seems something is wrong or not standard...
Any idea???
Or other better app?
Thanks
Dominique
**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: