Solution:
How to enable USB mass storage on Android 4.0 ICS Samsung Galaxy S2?
1.Bring up Settings.
2.Click More… (under Wireless and network).
3.Then select USB utilities ~ Set USB cable connection mode.
4.Select Connect storage to PC then.
5.Connect USB cable from phone to PC.
6.Select Turn on USB storage.
7.That’s all.
I was confused as to why my apps wouldn't install... Now i know why. Thanks dude
eheh it's quite different from gingerbred, yes.
I have found it just yesterday!!
rizxda said:
eheh it's quite different from gingerbred, yes.
I have found it just yesterday!!
Click to expand...
Click to collapse
It isn't really that different at all, it has always been under Network>USB utilities or something under GB. It's just that most of us used the pull-down notification.
its working with my usbStick but dosent work with the camera!?
Thanks, dude.
Was getting desperate because couldn't read my storage, on Bezke's ROM.
Cheers.
thank you very much...
OR, if you hate going through the menus everytime, you can do like I did and enable the USB mass storage by default (instead of that MTP which doesn't work on Mac OS).
Solution A - put this in your init script (if you have a kernel which supports init scripts, currently only CF-Root works on ICS).
Code:
setprop persist.sys.usb.config "mass_storage,adb"
Solution B - add/change the same settings in build.prop (you probably have now "persist.sys.usb.config=mtp,adb".
Code:
persist.sys.usb.config=mass_storage,adb
And reboot. When you connect your cable, it will default to USB mass storage mode just like it did on Gingerbread.
Solution C: JKay or any other ROM maker, add a button to the Message bar.
Sent from my GT-I9100 using XDA
VAXXi said:
OR, if you hate going through the menus everytime, you can do like I did and enable the USB mass storage by default (instead of that MTP which doesn't work on Mac OS).
Solution A - put this in your init script (if you have a kernel which supports init scripts, currently only CF-Root works on ICS).
Code:
setprop persist.sys.usb.config "mass_storage,adb"
Solution B - add/change the same settings in build.prop (you probably have now "persist.sys.usb.config=mtp,adb".
Code:
persist.sys.usb.config=mass_storage,adb
And reboot. When you connect your cable, it will default to USB mass storage mode just like it did on Gingerbread.
Click to expand...
Click to collapse
I have "persist.sys.storage_preload=1"
Danielfr said:
I have "persist.sys.storage_preload=1"
Click to expand...
Click to collapse
Got the same here.
Nice solution above but I just really wish it could be handled like my old HTC on GB with the dropdown notification.
Sometimes I just want to charge, sometimes mtp will do but more often mass storage.
i rly need this feature...i use it everyday to connect my gs2 to my car stereo....there'sno app capable a the moment?
That has nothing to do with what I wrote; as these are computers, even one letter makes a big difference, nevermind one entire word
I've checked the default build.prop files on XXLPQ and ZSLPE and they don't seem to include this setting by default, so you probably have to add it manually; either remount /system as r/w and edit through vi in ADB, either use build.prop Editor from the market.
@Elemetrix: changing the system property mentioned before gives you the old style setting instead of MTP.
VAXXi said:
That has nothing to do with what I wrote; as these are computers, even one letter makes a big difference, nevermind one entire word
I've checked the default build.prop files on XXLPQ and ZSLPE and they don't seem to include this setting by default, so you probably have to add it manually; either remount /system as r/w and edit through vi in ADB, either use build.prop Editor from the market.
@Elemetrix: changing the system property mentioned before gives you the old style setting instead of MTP.
Click to expand...
Click to collapse
editing build.rpop..didnt work
What exactly didn't work ? is it still going to MTP, is it not working at all anymore ?
Easiest way to check is to do a
Code:
getprop | grep usb
in Terminal Emulator and see if the values have changed.
VAXXi said:
What exactly didn't work ? is it still going to MTP, is it not working at all anymore ?
Easiest way to check is to do a
Code:
getprop | grep usb
in Terminal Emulator and see if the values have changed.
Click to expand...
Click to collapse
it is still picking as mtp,adb when i grep it. but i have confirmed i changed it in build.prop.. found under systems
can u make pls a detailed guide to us poor newbies? XD
xinfinityoO said:
it is still picking as mtp,adb when i grep it. but i have confirmed i changed it in build.prop.. found under systems
Click to expand...
Click to collapse
Was the build.prop saved ? can you grep the property name in build.prop and check it's still there after rebooting the phone ?
The
Code:
getprop | grep usb
should give you two more properties: sys.usb.config and sys.usb.state. They should have the same mass_storage,adb value.
VAXXi said:
Was the build.prop saved ? can you grep the property name in build.prop and check it's still there after rebooting the phone ?
The
Code:
getprop | grep usb
should give you two more properties: sys.usb.config and sys.usb.state. They should have the same mass_storage,adb value.
Click to expand...
Click to collapse
yes it was saved.. i even checked with root explorer.. and the rest of properties also states the same mtp,adb. can you attach your buildprop for me to test..
thanks
Related
After switching to linux, my phone no longer recognizes my computer and doesnt give the option to go to disc mode, sorry if its a dumb question but could someone tell me what i need to do to get it working again? Im not familiar with the os yet so im clueless.
you can't use mass storage mode?
it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in
Justjusten said:
it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in
Click to expand...
Click to collapse
Do you have debug turned on on the phone?
Thats because Linux doesnt see your phone. You need to setup UDEV to recognize your Hero. Follow this tutorial. And when I say "Follow" I MEAN FOLLOW. No skipping.
http://forum.xda-developers.com/showthread.php?t=537508
do i have to reinstall linux to do this ?
Justjusten said:
do i have to reinstall linux to do this ?
Click to expand...
Click to collapse
What flavor do you have?
im using mint i think its based on ubuntu
So, did you follow directions? Should work with any flavor of Linux.
im trying but i dont have a .bashrc file so i made one and when i put this code (sudo /etc/init.d/udev restart) into the terminal i get
(Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service udev restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart udev
udev start/running, process 2427)
Justjusten said:
do i have to reinstall linux to do this ?
Click to expand...
Click to collapse
No, you don't have to reinstall Linux.
Justjusten said:
im using mint i think its based on ubuntu
Click to expand...
Click to collapse
Mint is a derivative of Ubuntu, so yes, it's based off of it.
Justjusten said:
im trying but i dont have a .bashrc file so i made one and when i put this code (sudo /etc/init.d/udev restart) into the terminal i get
(Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service udev restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart udev
udev start/running, process 2427)
Click to expand...
Click to collapse
You don't need to create the .bashrc file... it's already there. The period in front of the bashrc indicates that the file is hidden.
To see hidden files, run this command:
Code:
[B]ls -a[/B]
This will show you hidden files, any files with a period in front of it, will always be hidden.
Or navigate to the folder that it says that it is in and press ctrl + h
This will show you all the hidden files inside of the folder. Without having to use the terminal.
Justjusten said:
it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in
Click to expand...
Click to collapse
Did you try pulling down the status bar and clicking on Charge Only to set it to disk mode?
If all else fails you can reboot to recovery and USB-MS toggle. If that doesn't work then something is messed up in your distro. Test if mounting works while in recovery and report your results.
I already did the control + h to show hidden folders and there isnt a .bashrc there is one under etc except it is bash.bashrc and i cant edit it , and i already tried the usb-ms toggle in recovery and nothing happened. Thanks for all the help so far guys, and if there is something wrong with my distro i dont mind getting a new one, does anyone have and suggestions on what to go with though?
Justjusten said:
I already did the control + h to show hidden folders and there isnt a .bashrc there is one under etc except it is bash.bashrc and i cant edit it , and i already tried the usb-ms toggle in recovery and nothing happened. Thanks for all the help so far guys, and if there is something wrong with my distro i dont mind getting a new one, does anyone have and suggestions on what to go with though?
Click to expand...
Click to collapse
There shouldnt be anything wrong with your Distro. Mint is built off Ubuntu so in essence it should work. Maybe download Ubuntu.
i think ill make a live disc of ubuntu and see if my phone is recognized at that point and if not then i wont install it
You cant edit it because you have to have root access. You should try typing in terminal sudo chmod permissions to give you root access. Im definitely not that good at linux but i figured out a majority of it.
make a file in /etc/udev/rules.d/ called 51-android.rules
here is mine.
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666" , GROUP="plugdev"
Make sure you belong to the plugdev group, you probably already are. I can execute adb commands without being root user.
Justjusten said:
i think ill make a live disc of ubuntu and see if my phone is recognized at that point and if not then i wont install it
Click to expand...
Click to collapse
just stick to what works and that's windows 7, i hate linux on a pc.
fixxxer2008 said:
just stick to what works and that's windows 7, i hate linux on a pc.
Click to expand...
Click to collapse
Well that is a debate topic for another place. For me I've formatted the drive on my last 4 new laptops and have not looked back.
I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?
yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.
ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.
This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.
be careful, backup buid.prop and restore it after creating Box account.
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
I am having no luck finding a way to get root access from a computer.
deleted post
user error
The tumbleweeds are big around here
There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
But is there an app to copy my file over from my computer?
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.
jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...
its taking forever to install SDK
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.
yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?
Ok so i finaly got hold of a otg micro to female usb adapter, they should really give you one with the nexus.
updated to 4.2.1 this morning and now ive found plugging anything into the otg cable does nothing , usb stick, android phone, mp3 player,.. nothing.
was hoping to use an old android as a external hard drive/usb storage/micro sd reader
any idea's?
Yes, as has been posted in countless threads, Stickmount will not work until it is updated to work with 4.2. Please do some reading. Someone posted that an app called 'Usb OTG Helper' does work after the update, but I don't have the update yet so I can't test. It also works under 4.1.2.
Groid said:
Yes, as has been posted in countless threads, Stickmount will not work until it is updated to work with 4.2. Please do some reading. Someone posted that an app called 'Usb OTG Helper' does work after the update, but I don't have the update yet so I can't test. It also works under 4.1.2.
Click to expand...
Click to collapse
Didn't work for me
darkuni said:
Didn't work for me
Click to expand...
Click to collapse
I've tried OTG Helper, USB Mass Storage Watcher, and Stickmount after updating my Nexus 7 to 4.2.
They all behave the same...will mount and unmount the drive, but the folder reports no files.
Groid said:
Yes, as has been posted in countless threads, Stickmount will not work until it is updated to work with 4.2. Please do some reading. Someone posted that an app called 'Usb OTG Helper' does work after the update, but I don't have the update yet so I can't test. It also works under 4.1.2.
Click to expand...
Click to collapse
my friend i suggest you begin reading as none of my post mentions the app "stickmount" if you took the time to read my post instead of flagrantly firing off any old answer you would probably see i only just got the nexus and have no real clue as to how connect anything too it.... please dont pigeon hole the next guy so bad eh?
limpet said:
I've tried OTG Helper, USB Mass Storage Watcher, and Stickmount after updating my Nexus 7 to 4.2.
They all behave the same...will mount and unmount the drive, but the folder reports no files.
Click to expand...
Click to collapse
darkuni said:
Didn't work for me
Click to expand...
Click to collapse
If you feel adventurous, you can try the ntfs-3g binary that makes OTG Helper work, and try to manually mount your drive.
First though adb/terminal emulate this command, 5 or + seconds [however long it takes to initialize the drive] after plugging it in through OTG:
Code:
ls /dev/block/sd?1
If it lists it, then you're good to go!
If however, you have more than 1 partition, you will need to change the 1 to a 2 [or 3, or 4] depending on the partitioning.
Download ntfs-3g compiled by shardul_seth, I pulled the binary and uploaded here: http://www.mediafire.com/?1z117pj3g57okab
with adb [or if you prefer, root browser]:
Code:
adb push ntfs-3g /system/xbin/
chmod +x /system/xbin/ntfs-3g
Now in adb/terminal:
Code:
su
mkdir /mnt/usbdisk
ntfs-3g /dev/block/sd?1 /storage/usbdisk
If you do not get an error, congratulations, your disk is now mounted!
To unmount,
Code:
su
umount /mnt/usbdisk
If you get an error saying device is busy, close file managers. If it still says device busy, type
Code:
su
pkill mediaserv
If it is still busy after that:
Code:
su
lsof | grep usbdisk
If any app has a file open on the disk it will show it here with its PID, and I think the name of it too. if you have the PID:
Code:
kill $PID
where $PID is the actual number.
If this works for you, and the other apps aren't updated for 4.2 soon, you can use Scripter to make mount and umount scripts to make it a little easier.
:victory: gl
Thanks. At least there is some work around. Next up? CIFS ....
Sent from my Galaxy Nexus using Tapatalk 2
darkuni said:
Thanks. At least there is some work around. Next up? CIFS ....
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah actually I forgot and assumed the drive was NTFS :S
If it's fat32 or probably even ext2/3/4, instead of ntfs-3g binary, just use regular mount. :victory:
the reason for the ntfs-3g is because it supports R/W, instead of just R/O in the stock mount command. [ntfs-3g is the driver they use in Ubuntu and such for mounting windows ntfs drives]
If you need the OTG only for media files Nexus Media Importer still works fine with 4.2, and doesn't even need root.
I was looking for this and I just found it. It just disables the USB Debugging notification without disabling USB Debugging.
I put it here just in case someone needs it:
root phone
backup /system/build.prop to your sdcard
edit & add the line below to /system/build.prop
Code:
persist.adb.notify=0
source
carlosmg2 said:
I was looking for this and I just found it. It just disables the USB Debugging notification without disabling USB Debugging.
I put it here just in case someone needs it:
root phone
backup /system/build.prop to your sdcard
edit & add the line below to /system/build.prop
Code:
persist.adb.notify=0
source
Click to expand...
Click to collapse
Nice!
You should put this in the Android development section of this forum.
You should just link to this thread, it has them all there (I've used this for years when needed)
http://forum.xda-developers.com/showthread.php?t=1246748
Thank you so much!!!!
Thanks man was looking for this :good:
After editing my build.prop and adding this line, the device no longer boots. Soft brick... (Nexus 5)
eladnava,you must edit that line,not add it.
Any non-rooted solution? You can (on Lollipop and above) longpress the notification and hide all from Android System, but that seems like a VERY bad idea.
thanks!!
good code ,thenks man
Modern method that works with Magisk (root):
Connect over adb, then do:
su
resetprop persist.adb.notify 0
Hi Guys,
First off sorry if this isn't the correct place for this, if it isn't would somebody be good enough to move it to the right place.
I've got a rooted (via NookManager) Nook Simple Touch, the problem is I need to turn on USB Debugging but can't find any way to do so. What am I missing?
Thanks
-S
Sanukk said:
What am I missing?
Click to expand...
Click to collapse
You are not "lurking" hard enough.
Use 'NookColor Tools' to turn on USB debugging.
http://forum.xda-developers.com/showthread.php?t=868366
To run 'NookColor Tools' put the 'apk' in /system/app/ folder using any filemanager that has the ability to mount /system partition in write mode (ex. 'Rhytm software File Manager', 'Es File explorer')
After that there are 2 choices.
1. Use 'ABD Wireless' or 'ADB Konnekt' to connect to your PC via WIFI (the easiest way)
2. Configure Android Udev Rules on your linux machine. You can find the correct values in
a) any search engine ( look for 'android udev rules adb')
b) check out the list of my posts. I posted the correct values somewhere.
c) http://forum.xda-developers.com/showthread.php?p=18418152
http://www.joescat.com/linux/android_rules.html
If you can find one site or post that contains the correct instructions for Linux and Windows paste them in this thread. Make this thread useful.
EDIT :
Wireless solutions should work out of the box, without the need of using NookColorTools.
osowiecki said:
You are not "lurking" hard enough.
Use 'NookColor Tools' to turn on USB debugging.
http://forum.xda-developers.com/showthread.php?t=868366
Click to expand...
Click to collapse
NookColor Tools did appear in in a few search results, but as I have a Touch Simple rather than a Nook Colour, I just ignored it. I'll try it tonight after I get home. Thanks.
~S