hey guy's ... this trick ll help you to get rid from MTP when u plug ur device with usb and it asks for MTP media share...
after this trick u ll directly get the USB MASS STORAGE or USB MOUNTING access
STEP 1: Download/install Android Terminal Emulator, open it and type: su (to grant superuser permission)
then type setprop persist.sys.usb.config mass_storage,adb and execute the command
Step2: and Reboot phone typing reboot
It also works on ICS tested on ICS UCLE2
original link: samsung tweaks
Nice. I used the command line you gave but just used ADB WiFi and the entered it this way:
Code:
adb connect xxx.xxx.xxx.xxx
adb shell
su
setprop persist.sys.usb.config mass_storage,adb
reboot
I just go into USB Utilities in Settings on Gingerbread, or download Android File Transfer for ICS lol (on Mac OS X), but thanks I'll make sure to use this if I go back to GB.
Good One!
Thanks A lot. No need to go settings for USB mass storage.
Texantx said:
Good One!
Thanks A lot. No need to go settings for USB mass storage.
Click to expand...
Click to collapse
yeahh...
can you tell me how to undo this tweak? thanks...
I have Galaxy Note with stock kernel and stock everything but rooted and after I click disconnect storage (when android picture is yellow) there is a pop up asking me whether I want to restart MTP. Since I am too lazy right now to see about this matter on google and about mtp and what happens when I disconnect or connect I am asking you, would I choose to restart MTP or not to (it actually asks for mtp restart because he is mounting sd card again) and is there a command that can make it an automatic process like this one you have given to us.
Thank you.
rsage said:
can you tell me how to undo this tweak? thanks...
Click to expand...
Click to collapse
Sorry, just seen this thread, figured I'd answer your question;
It depends what it was already set to on your phone setprop sets a property. On my HTC One X, it was set to adb, so to restore the previous setting:
Code:
setprop persist.sys.usb.config adb
Hope that helps!
Just thought I'd chime in for Mac users. If you go to www.android.com/filetransfer there is an application that allows you to connect to Android phones via MTP and do transfers. No need for any adb stuff.
chrispy_212 said:
It depends what it was already set to on your phone setprop sets a property. On my HTC One X, it was set to adb, so to restore the previous setting:
Code:
setprop persist.sys.usb.config adb
Click to expand...
Click to collapse
On my Samsung SGS3, to return it to 'original' you would use:
Code:
setprop persist.sys.usb.config mtp,adb
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
Stupifier said:
Just thought I'd chime in for Mac users. If you go to www.android.com/filetransfer there is an application that allows you to connect to Android phones via MTP and do transfers. No need for any adb stuff.
Click to expand...
Click to collapse
You're missing the point.
For me it's so I can mount the 2 storages onto my mac, so I can back them up using rsync in a script, from the command line. MUCH faster than crappy drag/drop using android file transfer.
Please Help!!
I've just did what you said, but I forgot to execute the "su" command. When I realized it, I redo the whole operation but typing the "su"command the terminal says he didn't find the command.
Still doesn't work...
raman21raman said:
hey guy's ... this trick ll help you to get rid from MTP when u plug ur device with usb and it asks for MTP media share...
after this trick u ll directly get the USB MASS STORAGE or USB MOUNTING access
STEP 1: Download/install Android Terminal Emulator, open it and type: su (to grant superuser permission)
then type setprop persist.sys.usb.config mass_storage,adb and execute the command
Step2: and Reboot phone typing reboot
It also works on ICS tested on ICS UCLE2
original link: samsung tweaks
Click to expand...
Click to collapse
I've tried as you said, but neither the Finder nor the Android Files Transfer see it. What can I do?
SimoPiersi said:
I've tried as you said, but neither the Finder nor the Android Files Transfer see it. What can I do?
Click to expand...
Click to collapse
try with usb debugging on from developer options
Already on...
raman21raman said:
try with usb debugging on from developer options
Click to expand...
Click to collapse
It was already on. Any ideas?
SimoPiersi said:
It was already on. Any ideas?
Click to expand...
Click to collapse
Im looking for an answer as well.
Related
The Barnes & Noble Nook uses adb over wifi. How can I setup my N1 to do the same? Ideally I would like to specify on the N1 to only allow connections over wifi, and if possible have some sort of password type security. Can this be done?
why not use ssh?
the dropbear-client is included in most custom roms.
edit: i mean dropbear-server of course
mikecyber said:
The Barnes & Noble Nook uses adb over wifi. How can I setup my N1 to do the same? Ideally I would like to specify on the N1 to only allow connections over wifi, and if possible have some sort of password type security. Can this be done?
Click to expand...
Click to collapse
+1 on this, but I would like it to be included within the ROM with a UI setting or maybe even an applicaion
Getting adbd to listen to tcpip in the phone is quite easy.
Example below:
Code:
[I]# detach adbd from usb and tell it to listen to port tcp 2222
[/I][email protected]$ adb tcpip 2222
restarting in TCP mode port: 2222
[I]# tell your local adb command to use ip:port to connect through instead of usb (192.168.0.151 is my N1 on Wifi)
[/I][email protected]$ adb connect 192.168.0.151:2222
connected to 192.168.0.151:2222
[I]# connect over ip
[/I][email protected]$ adb shell
# uname -a
Linux localhost 2.6.29.6-cyanogenmod #3 PREEMPT Wed Jan 27 07:21:12 EST 2010 armv7l GNU/Linux
# exit
[I]# tell adbd to go back to listen on usb
[/I][email protected]$ adb usb
restarting in USB mode
packetlss said:
Getting adbd to listen to tcpip in the phone is quite easy.
Click to expand...
Click to collapse
Thank you, your method works well.
With my nook all I need to do is "adb connect 192.168.1.x:5555" I don't have to put adb into tcpip mode or enter "uname -a" in shell.
I would love to see "Wireless Debugging" in Settings -> Applications -> Development, or really anywhere in Settings. I haven't voided my N1's warranty, so an app to add this functionality would be great.
mikecyber said:
Thank you, your method works well.
With my nook all I need to do is "adb connect 192.168.1.x:5555" I don't have to put adb into tcpip mode or enter "uname -a" in shell.
I would love to see "Wireless Debugging" in Settings -> Applications -> Development, or really anywhere in Settings. I haven't voided my N1's warranty, so an app to add this functionality would be great.
Click to expand...
Click to collapse
That's because the nook adbd is configured to listen to tcp by default, on most other platforms it just listens to USB by default.
The 'uname -a' was just to show that I actually was connected to the phone. Nothing to do with the actual adb stuff at all, I was just lazy and copied from my terminal
MoDaCo Custom ROMs generally run dropbear by default with a password that is randomly generated on first startup.
I don't mind making an addon update zip for Cyanogen's ROM with this functionality if you want it?
P
bump
Found this really useful as my USB driver causes BSODs. thanks packetlss
1. connect device via usb
2. adb tcpip 2222
3. connect over wifi. adb connect 192.168.3.5:2222
4. adb commands as normal
can the OP remove [request] as this is now a [tip] or [howto]
britoso said:
bump
Found this really useful as my USB driver causes BSODs. thanks packetlss
1. connect device via usb
2. adb tcpip 2222
3. connect over wifi. adb connect 192.168.3.5:2222
4. adb commands as normal
can the OP remove [request] as this is now a [tip] or [howto]
Click to expand...
Click to collapse
Does the USB have to be hooked up each time, or is it a 1 time then WIFI is good after that?
Nice howto!!
britoso said:
bump
Found this really useful as my USB driver causes BSODs. thanks packetlss
1. connect device via usb
2. adb tcpip 2222
3. connect over wifi. adb connect 192.168.3.5:2222
4. adb commands as normal
can the OP remove [request] as this is now a [tip] or [howto]
Click to expand...
Click to collapse
Gotta say that is slick as sh**!!! How to get it to stay on tcpip via terminal on phone??
britoso said:
bump
Found this really useful as my USB driver causes BSODs. thanks packetlss
1. connect device via usb
2. adb tcpip 2222
3. connect over wifi. adb connect 192.168.3.5:2222
4. adb commands as normal
can the OP remove [request] as this is now a [tip] or [howto]
Click to expand...
Click to collapse
interesseting... thanks!
i'll try that
EDIT: worked so good - thx!
tbirdguy said:
Does the USB have to be hooked up each time, or is it a 1 time then WIFI is good after that?
Click to expand...
Click to collapse
Do it once and it stays...perhaps till you reboot the phone.
If your IP address on wifi you will need to run the connect command again. Also set the wifi-sleep mode to 'never', possibly install the wifi-keepalive app.
Its awesome to be able to run stuff on your phone straight from eclipse, unplugged; or install/push/pull files
xkonni said:
why not use ssh?
the dropbear-client is included in most custom roms.
edit: i mean dropbear-server of course
Click to expand...
Click to collapse
Do you know what the default pw is for dropbear? when i try to ssh with my local ip and root, i get a connection refused on port 22. i'm using cm6, do i have to enable it somehow?
TCPIP mode without connecting usb
Is it possible to enable ADBD tcpip mode without connecting device to USB port and use adb command? I mean maybe a command we can run in a Terminal Emulator?
bohlool said:
Is it possible to enable ADBD tcpip mode without connecting device to USB port and use adb command? I mean maybe a command we can run in a Terminal Emulator?
Click to expand...
Click to collapse
re,it's there any possible that get adb work over TCP/IP ,on all android devices(include non-rooted devices)？
wobiu said:
re,it's there any possible that get adb work over TCP/IP ,on all android devices(include non-rooted devices)？
Click to expand...
Click to collapse
I know how to enable it, just connect it with usb to computer and enter "adb connect tcpip <port>" then disconnect usb and connect phone to wifi, find the ip of phone and on your computer type "adb connect <ip>:<port>"
my problem is how can I do the first step without usb cable, i.e. using a terminal emulator. I have root access.
bohlool said:
my problem is how can I do the first step without usb cable, i.e. using a terminal emulator. I have root access.
Click to expand...
Click to collapse
would love to see this as well, can anyone with expertise in the area let us know if this is at all possible?
# adbd
As root on the device returns
Cannot bind tcp 5037
Im not home so i cant test but maybe this could work over tcp port 5037...
Sent from my Nexus One
bohlool said:
I know how to enable it, just connect it with usb to computer and enter "adb connect tcpip <port>" then disconnect usb and connect phone to wifi, find the ip of phone and on your computer type "adb connect <ip>:<port>"
my problem is how can I do the first step without usb cable, i.e. using a terminal emulator. I have root access.
Click to expand...
Click to collapse
for rooted device。you can use"start adbd" command to start adb daemon ，instead of plug into usb.
What am i looking for is a way to use adb over wifi for all device including non-rooted.
wobiu said:
for rooted device。you can use"start adbd" command to start adb daemon ，instead of plug into usb.
What am i looking for is a way to use adb over wifi for all device including non-rooted.
Click to expand...
Click to collapse
What is the port number then? is it 5037? Can I set it somewhere? (for rooted devices of course)
i searched and cant seem to find anything on my problem....i connect via mass storage mode , it detects the phone, but for some reason it doesnt let me access the files on the card....in other words ,i cant open them...any help ????
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
I am using it just fine on Ubuntu 10.4
I connect my phone and it is mounted automagically, and I can move the files from/to the phone.
Do you have se_linux installed?
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
thanks, I'll give this a try, let you guys know tomorrow...
Gotta say it works on Ubuntu better then does on Windows XP. You may have some permissions fudged somewhere. Do as the guys above said and let us know.
the3dman said:
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
Click to expand...
Click to collapse
this is not working for me
aksoutherland said:
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
Click to expand...
Click to collapse
nothign when i enter command
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
lqaddict said:
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
Click to expand...
Click to collapse
nothing again.....i have it set to ask on connection, then i swithced to mass storage mode....... what else should i do?
error message : "could not display" "the file location is not a folder "
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.
lqaddict said:
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.[/QUOTE]
thanks, I appreciate the help, I will give this a try in the morning
Click to expand...
Click to collapse
Hi,
I have a Spice Mi-270 dual sim android 2.2 phone.Searching on the internet I came across an article where the procedure for installing the apps by default to sdcard is possible for non rooted phones.I tried it but when I type "adb devices" I get a blank list under list of devices attached.My phone came with the usb drivers, I have installed that.Tried installing Google USB driver package,revision 4.When the phone is plugged in get the message on the phone "USB Debugging started".Windows device manager shows "Android Phone" > Android Composite ADB Interface.Still my device is not detected with the "adb devices" command.I am using winxp pro sp3 32bit.Please Guide!
(If I have posted in the wrong section please inform me where to post)
I probably won't be helping. But on my un-rooted HTC Sensation i just have an app called app2sd. After i installed an app, if it's supported, i copy it to sd card.
Can't you just use that and save the hassle?
try this apps2sd
I have already installed the apps2sd but as said one can move the apps to sd if and only if supported by the app.Besides Android 2.2 by default provides the option to supported apps.How do I change the default install path to sd without rooting?
sounds like u need to root it and add the a2sd+ scripts OR root, install rom with a2sd+ and partition sd card accordingly.
do0b said:
sounds like u need to root it and add the a2sd+ scripts OR root, install rom with a2sd+ and partition sd card accordingly.
Click to expand...
Click to collapse
Sorry doOb but I am not looking at rooting my phone but use the option
adb shell pm setInstallLocation 2.
Why not root your phone? At the end or the day you still can unroot it. It's not like you flash to a different Rom and lost your stock Rom.
As far as I know your running froyo you already have move app to SD at the manage application in setting. There are free market app that can help you to move apps to SD with simple clicks without going to setting with the slow loading.
I'm afraid there are no default to app to SD unless you root your Rom and flash a2sd script like darktermor to make the whole process default. Better still, you also need to partition your card with an ext partition for it to work.
By the way... You should be able to adb shell your phone with a proper setup from your pc. You need to look for adb shell howto.
Sounds like your doing it from the wrong folder at cmd if your using windows. Try start cmd from the folder with adb.exe or set your system path to include the folder with adb.exe. I'm not with a pc now, I can't direct you. You have to look for it on what I mean.
By the way, can you also post the link for the article you found?
I have friends that can't root their phone. E.g HTC wildfire s
Sent from my HTC Legend using XDA App
darryl_co said:
Hi,
I have a Spice Mi-270 dual sim android 2.2 phone.Searching on the internet I came across an article where the procedure for installing the apps by default to sdcard is possible for non rooted phones.I tried it but when I type "adb devices" I get a blank list under list of devices attached.My phone came with the usb drivers, I have installed that.Tried installing Google USB driver package,revision 4.When the phone is plugged in get the message on the phone "USB Debugging started".Windows device manager shows "Android Phone" > Android Composite ADB Interface.Still my device is not detected with the "adb devices" command.I am using winxp pro sp3 32bit.Please Guide!
(If I have posted in the wrong section please inform me where to post)
Click to expand...
Click to collapse
Sounds like the original issue was the pc not seeing the device....I know this may be elementary, but do you have it in "charge only" mode and not in the disk drive mode?
"Sounds like your doing it from the wrong folder at cmd if your using windows. Try start cmd from the folder with adb.exe or set your system path to include the folder with adb.exe." - pysionx
I am starting cmd from the folder with adb.exe that laocated in platform-tools.If I was not doing so I would get the error " 'adb' is not recognized as an internal or external command operable program or batch file." and on typing adb devices in the cmd prompt I would not get the answer "list of devices"
pysionx - "By the way, can you also post the link for the article you found?"
Unfortunately no as this is my first post I am not allowed by the administrator to do so.Please Check out the attachment.Sorry for giving you the trouble to download attachment.
pfroyjr - "Sounds like the original issue was the pc not seeing the device"
If the pc does not see the device how do I get in Windows device manager showing "Android Phone" > Android Composite ADB Interface.
pfroyjr - "I know this may be elementary, but do you have it in "charge only" mode and not in the disk drive mode?"
I do not have it in "charge only" mode but in the disk drive mode, USB debugging started is the message received in the notification area.
But this causes hw to crash!
root_toor said:
But this causes hw to crash!
Click to expand...
Click to collapse
I sorry but I did not understand. what causes hardware to crash?
Google "Spice driver" I'll find a link if you can't. Windows is odd with its drivers sometimes. I remember the first time I ever used SDK I had to remove the default drivers and install the one from HTC but recently just installing the driver was good enough and I've only used adb and not the SDK. just a suggestion.
Sent from my HTC Glacier using xda premium
EDIT: I forgot which posting I was replying to, sorry....
I found THIS which sounds like it's an issue with the phone and maybe not the same Android OS that everyone else has....just what I read. Happy Googling my friend. Sounds like it's a cool device, just not quite up to par with adb.
I do have the drivers of my mobile Spice Mi-270 which was shipped along with the phone. The drivers files are of similar names with that of the google usb drivers for android except for the file versions.
Thanks pfroyjr for the link.It seems it is the problem with the phone itself as I am not the only one facing the problem with adb comand.
darryl_co said:
I do have the drivers of my mobile Spice Mi-270 which was shipped along with the phone. The drivers files are of similar names with that of the google usb drivers for android except for the file versions.
Thanks pfroyjr for the link.It seems it is the problem with the phone itself as I am not the only one facing the problem with adb comand.
Click to expand...
Click to collapse
Best advice is stay active searching for an answer...someone will eventually figure it out
I think it can be done with the help of adb .
Just run command from the folder having adb.exe file after connecting your phone in USB Debugging Mode.
"adb shell pm setInstallLocation 2"
YOu can change it to default by the following command.
"adb shell pm setInstallLocation 0"
Type the commands without quotes....
Hope it helps!!!
darryl_co said:
I have already installed the apps2sd but as said one can move the apps to sd if and only if supported by the app.Besides Android 2.2 by default provides the option to supported apps.How do I change the default install path to sd without rooting?
Click to expand...
Click to collapse
Hey try this adb command from the directory having adb.exe file after connecting your phone to your pc by enabling USB Debugging Mode on it.
adb shell pm setInstallLocation 2
You can change it back to default by this command ..
adb shell pm setInstallLocation 0
Hope it helps you ...
yagya said:
Hey try this adb command from the directory having adb.exe file after connecting your phone to your pc by enabling USB Debugging Mode on it.
adb shell pm setInstallLocation 2
You can change it back to default by this command ..
adb shell pm setInstallLocation 0
Hope it helps you ...
Click to expand...
Click to collapse
when I type "adb devices" I get a blank list under list of devices attached.When my phone is not listed how would the adb shell pm setInstallLocation command work ?
but The pc does see the device and I get in Windows device manager showing "Android Phone" > Android Composite ADB Interface.
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!
---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!
yagya said:
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!)
Click to expand...
Click to collapse
I installed universal androot and rooted the phone.
Instead of shell commander I installed Move2SD Enabler.The move2sd had three radio buttons Auto, Internal and External.Initially it displayed the radio button on Auto.I selected External and clicked apply.Now it shows External.Then I unrooted the phone.In Apps2SD I found many apps that were listed under phone only under movable apps.Few questions do arise
1.If I restore to factory defaults will the installation to external storage be resetted?
2.Whenever I Install new apps it gets installed in the phones internal storage and the I have to move to sd.Why is that so?
3.Even after moving to the sd some amount remains in the phone internal storage.why?
4.Can I check using shell commander if the install location has changed? what is the command? Do I have to root the phone again to use the command?
darryl_co said:
I installed universal androot and rooted the phone.
Instead of shell commander I installed Move2SD Enabler.The move2sd had three radio buttons Auto, Internal and External.Initially it displayed the radio button on Auto.I selected External and clicked apply.Now it shows External.Then I unrooted the phone.In Apps2SD I found many apps that were listed under phone only under movable apps.Few questions do arise
1.If I restore to factory defaults will the installation to external storage be resetted?
2.Whenever I Install new apps it gets installed in the phones internal storage and the I have to move to sd.Why is that so?
3.Even after moving to the sd some amount remains in the phone internal storage.why?
4.Can I check using shell commander if the install location has changed? what is the command? Do I have to root the phone again to use the command?
Click to expand...
Click to collapse
Restoring factory default settings will reset default install location to auto.
Since you used move to sd enabler it only makes all apps movable to sd but doesn't move them automatically.
System apps and Those apps that don't support app to sd by default can't be completely moved to sd card
Yes, you can check using shell commander but you need to riot you phone to use the command.
pm getInstallLocation
(returns default install location)
pm setInstallLocation 2
(installs app direct to external storage)
Sent from my GT-S5570 using XDA Premium App
Hello, I am using a Droid Razr Maxx CDMA (XT912). I have Android version 4.2.2. I am using Cyanogen mod 10.1.
I am having problems opening ADB. When I turn my USB Debugging on under my dev. options, connect my device in PTP mode using the terminal emulator commands:
su
setprop persist.sys.usb.config mass_storage
reboot
I run the ADB program and a window comes up for a brief moment then closes. I am unable to open ADB. I have Java.
Thank You!
ADB Troubles Cont'd.
nathanielhall929 said:
Hello, I am using a Droid Razr Maxx CDMA (XT912). I have Android version 4.2.2. I am using Cyanogen mod 10.1.
I am having problems opening ADB. When I turn my USB Debugging on under my dev. options, connect my device in PTP mode using the terminal emulator commands:
su
setprop persist.sys.usb.config mass_storage
reboot
I run the ADB program and a window comes up for a brief moment then closes. I am unable to open ADB. I have Java.
Thank You!
Click to expand...
Click to collapse
Did adb kill-server and adb start-server several times in cmd with no avail. The device serial number shows up under adb devices, but ADB Program will still not open. I've tried to open ADB up in cmd also.
I also tried typing in the terminal emulator:
su
setprop persist.sys.usb.config mass_storage, adb
reboot
Thanks again!
Can someone please help me with this?
I even tried installing the Universal naked drivers and that wouldn't go through.
nathanielhall929 said:
I even tried installing the Universal naked drivers and that wouldn't go through.
Click to expand...
Click to collapse
I copied your command and pasted here. setprop persist.sys.usb.config mass_storage, adb
And what I find is posted here. setprop persist.sys.usb.config mass_storage,adb
And reboot afterwards.
Notice the extra space in your command before adb?
I found this command structure several locations and only one that reports failed has the space.
For ICS it also shows adb shell as in
adb shell setprop persist.sys.usb.config mass_storage,adb
adb reboot
I hope this helps.
Tried it without the space and still not working
tobdaryl said:
I copied your command and pasted here. setprop persist.sys.usb.config mass_storage, adb
And what I find is posted here. setprop persist.sys.usb.config mass_storage,adb
And reboot afterwards.
Notice the extra space in your command before adb?
I found this command structure several locations and only one that reports failed has the space.
For ICS it also shows adb shell as in
adb shell setprop persist.sys.usb.config mass_storage,adb
adb reboot
I hope this helps.
Click to expand...
Click to collapse
I just tried it without the space, rebooted, and nothing
I don't get it
nathanielhall929 said:
I just tried it without the space, rebooted, and nothing
Click to expand...
Click to collapse
The ADB Program just won't open up on this computer. It opens for a second spewing command info then closes. Is it my Java program?
nathanielhall929 said:
I just tried it without the space, rebooted, and nothing
Click to expand...
Click to collapse
Are you getting an error?
This is the other method I see being used but I'll break the command as I believe it should be.
adb shell
su
setprop persist.sys.usb.config mtp,adb
exit
adb reboot
My problem is I know nothing about your unit and I don't know whether it should be mtp or mass_storage. I see people failing with mass_storage are being told to use mtp.
in terminal it shows
su
setprop persist.sys.usb.config mass_storage,adb
reboot
or
su
setprop persist.sys.usb.config mtp,adb
reboot
To retrieve this info I used the top search that says Search All Forums and typed in your command then hit search. You may need to do the same and only go to the threads that suit your situation.
---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------
nathanielhall929 said:
The ADB Program just won't open up on this computer. It opens for a second spewing command info then closes. Is it my Java program?
Click to expand...
Click to collapse
Are you opening cmd and going to the directory with adb and issue your commands or are you trying to click on adb and use it that way?
I'm trying to run it in cmd
I've been trying to fix this for two days now. I'll be back tomorrow.
Figured out
Ok, now I feel like I'm a real noob. I just realized that I was thinking too hard about all of this. Adb doesn't open up in a new window as a regular program would. I thought it did. Oops. Maybe I should have been more thourough in my research. I should have realized that I already opened adb by using the cmd prompt.
This is why my device was recognized under adb devices.
Maybe not...
I still can't figure out how to get this:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/attachment/path-adb/
window to come up.
This is what I'm tring to do
nathanielhall929 said:
I still can't figure out how to get this:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/attachment/path-adb/
window to come up.
Click to expand...
Click to collapse
This is what I am trying to do:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/
Figured out finally!!!
nathanielhall929 said:
This is what I am trying to do:
http://tricktactoe.com/howto/how-to-record-android-screen-without-screencast/
Click to expand...
Click to collapse
I finally figured this out!!!
I want to thank tobdaryl for his time.
Thank you for your time tobdaryl
nathanielhall929 said:
I finally figured this out!!!
I want to thank tobdaryl for his time.
Thank you for your time tobdaryl
Click to expand...
Click to collapse
You are welcome.
Can you help me?
Can you check out this thread.. Maybe you can help me.
http://forum.xda-developers.com/showthread.php?t=2260208
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices
12. At the command prompt, enter:
C:\Users\entropy> adb shell
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.