Related
So I just installed Ubuntu 10.10 on my PC and I'm really digging it. But when I try to mount my sdcard from the phone, it doesn't show up under my places menu. I'm running GSB 1.8.1. I don't have a problem mounting it under windows XP, and also have no problem using the wired tether function. Is there anything I can change on the phone or in Ubuntu to fix this?
I am running Ubuntu 10.04 LTS - inside a Virtual Machine - and I can mount the drive from inside the VM. (Believe me, that's even trickier than what you are trying).
But, 10.10 might have had some changes, and I wouldn't be surprised if your result depended on which desktop you are running; so maybe you need to mount the thing manually.
Try this:
With the phone unplugged, type
$ sudo /bin/bash
# tail -f /var/log/messages
This will continue to show you various kernel messages as they appear. Next, plug in the phone.
Hopefully, you will see some lines scroll by that mention USB.
Next, mount the SD to the PC from the phone. If all goes well, you should now see some mention of "SCSI" devices /dev/sdX, where X is probably "a", "b" "c" "d". Probably you will also see mention of the first partition on the device, such as "/dev/sdb1". Make a note of this drive device name.
Cancel the "tail" command (Ctrl-C) and do a
# mount | grep sdb1
( note device name "sdb1" ; use whatever you saw previously )
This will show you if the device is already mounted somewhere.
If the device has not been mounted, you can manually mount it, as in:
# mkdir -p /mnt/Eris_SD
# mount -o rw /dev/sdb1 /mnt/Eris_SD
( Again, note device name "sdb1" - use whatever you saw previously. If it doesn't recognize the file system, use "mount -o rw -t vfat /dev/sdb1 /mnt/Eris_SD" )
Hopefully that will do it. Don't forget to "umount /mnt/Eris_SD" when you are done.
If the device never shows up in the /var/log/messages file, then you have some other problems.
If you don't see anything in the log file indicating USB activity, well - you ought to investigate what is going on at the USB port.
Right now my phone is booted into Amon_RA; if I issue the "lsusb" command, I see:
Code:
Bus 001 Device 031: ID 0bb4:0c98 High Tech Computer Corp.
BTW, on my VM, it seems like I need to unplug the USB cable after I dismount the drive, or the next time I export the SD card to the PC, the kernel recognizes it, but the automounter doesn't automatically mount it.
Another thing that you might try to make things more automatic is the instructions in "Step #5" of this XDA post. This is meant for allowing an unprivileged user on your Ubuntu box to use ADB or fastboot without needing to "sudo" to root. I did this on my VM - I don't think that's the reason that the phone automounts into the SD drive, but perhaps it is related - the same "Vendor_ID" is in use when the phone is in "Composite ADB mode".
When you get to the part in these instructions about restarting the "udev" subsystem, unplug your USB cable first - and then see what you get when you plug it in and fire up the SD export from the phone.
hope that helps.
bftb0 said:
BTW, on my VM, it seems like I need to unplug the USB cable after I dismount the drive, or the next time I export the SD card to the PC, the kernel recognizes it, but the automounter doesn't automatically mount it.
Click to expand...
Click to collapse
I noticed this on my desktop with a full install of Ubuntu. I knew it was connected because the charge led was lit, but I would have to unplug the usb and plug it back in almost every time just to get it to mount or connect to the internet with wired tether. I never messed with it BUT it did seem to fix itself once I started doing the system updates on Ubuntu.
bftb0 said:
$ sudo /bin/bash
# tail -f /var/log/messages
This will continue to show you various kernel messages as they appear. Next, plug in the phone.
Hopefully, you will see some lines scroll by that mention USB.
Next, mount the SD to the PC from the phone. If all goes well, you should now see some mention of "SCSI" devices /dev/sdX, where X is probably "a", "b" "c" "d". Probably you will also see mention of the first partition on the device, such as "/dev/sdb1". Make a note of this drive device name.
Click to expand...
Click to collapse
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
prsguitaruser said:
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
In case this helps, GSB mounts the SD card through USB just fine with Windows. Don't take my comment as a Windows versus Ubuntu, thing, however. Just for whatever it's worth.
prsguitaruser said:
I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
Glad to here you got this fixed
prsguitaruser said:
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
Great news! I don't know how I missed your edit since I quoted it in my last response. I must've had this thread open in my browser from before, and went to respond to it after your edit.
OK, so I went back to GSB and had the problem again. I found out that ADB works and the sdcard mounts until I turn on wired tether, then if I turn wired tethering off, my sdcard still won't mount, nor will ADB recognize my phone, until I reboot the phone. Every time I've tried to mount the sdcard, I've made sure to turn tethering off. But it seems like tethering is what kills it.
prsguitaruser said:
OK, so I went back to GSB and had the problem again. I found out that ADB works and the sdcard mounts until I turn on wired tether, then if I turn wired tethering off, my sdcard still won't mount, nor will ADB recognize my phone, until I reboot the phone. Every time I've tried to mount the sdcard, I've made sure to turn tethering off. But it seems like tethering is what kills it.
Click to expand...
Click to collapse
Are you using the tethering abilities built into CM7 (for wired you have to use the Tether Widget from the market, but that's it), or are you using the "for root" apps? IMHO, the "for root" apps are redundant and don't work as well as the native tethering in CM6 and CM7.
roirraW "edor" ehT said:
IMHO, the "for root" apps are redundant and don't work as well as the native tethering in CM6 and CM7.
Click to expand...
Click to collapse
Really? Because I have never been able to get "native" tethering to work. They appear to be working but there not allowing data to pass through.
Also I only use the ones posted on Google's source page.
I believe there may be an issue here that isn't faulted by the phone or the tethering apps. I think it has something to do with the way Ubuntu reacts to the change between allowing data inbound and when it goes back to remounting the phone and its SD card. Honestly if you can I would say allow your Ubuntu to do its system updates then see what happens.
@ roirraW "edor" ehT, no harm intended at the top of my post. Just my personal observation of how these things generally work out for me. Heh.
Powered by: GSB CM7
wildstang83 said:
Really? Because I have never been able to get "native" tethering to work. They appear to be working but there not allowing data to pass through.
Also I only use the ones posted on Google's source page.
I believe there may be an issue here that isn't faulted by the phone or the tethering apps. I think it has something to do with the way Ubuntu reacts to the change between allowing data inbound and when it goes back to remounting the phone and its SD card. Honestly if you can I would say allow your Ubuntu to do its system updates then see what happens.
@ roirraW "edor" ehT, no harm intended at the top of my post. Just my personal observation of how these things generally work out for me. Heh.
Powered by: GSB CM7
Click to expand...
Click to collapse
Just curious, did you have the opportunity to try the native tethering under Froyo/CM6 as well, or did you only try it under CM7? I haven't needed the tethering since before I started to try CM7, so I actually don't know from personal experience if Cyanogen has made the tethering work correctly under it yet. I didn't have any trouble with it under CM6, besides the usual occasional semi-random tethering failures.
My ubuntu 10.10 install handles native tethering just fine. However, that stupid bug where the Eris loses data connection randomly. while natively tethered kicks in.
The only solution I've found is to use AziLink (seems to solve the random disconnect as well as pdanet does.)
Sent from my Eris using XDA App
adaneshade said:
My ubuntu 10.10 install handles native tethering just fine. However, that stupid bug where the Eris loses data connection randomly. while natively tethered kicks in.
The only solution I've found is to use AziLink (seems to solve the random disconnect as well as pdanet does.)
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Thanks, I'll keep them both in mind. I tried PDANet a long time ago and it didn't keep the tethering from failing, but maybe they improved it.
I am using Neo V official build 4.1.B.0.431 (ICS 4.0.4), rooted, unlocked bootloader (doesn't seem to matter)
I've downloaded the kernel source code, compiled the `usb-storage.ko` module, and placed it on `/system/lib/modules/drivers/usb/storage/`.
I've also changed `/system/etc/vold.fstab`, added this line:
Code:
dev_mount usb /mnt/usbstor auto /devices/platform/msm_hsusb_host.0
Then I restarted the phone.
After that, I typed the commands (using root) in shell:
Code:
mount -o remount,rw /
insmod /system/lib/modules/drivers/usb/storage/usb-storage.ko
cd /mnt
mkdir usbstor
Then I plugged in the OTG cable with a USB Flash Drive.
The storage is successfully mounted (by vold, I think), as I can verify in Root Explorer. I don't have photos so can't verify whether media scanner can detect it.
But in Settings->Storage it didn't appear. Seems that the Settings app don't support. I cannot unmount it using GUI, so when I remove the storage it warns me about that.
Are there any ways to get the Settings app to show my USB storage so that I can unmount via GUI?
Also how to automatically `insmod` and create `/mnt/usbstor` when startup? I won't bother editing ramdisk, but anything under `/system` is fine. I saw a few shell scripts under `/system`, are they fine to use?
Download USB otg from market. It's for both, arc s & neo/ neo v.
Use it with caution it may burn your motherboard....
Sent from my MT11i using xda app-developers app
Fine. I didn't use any piece of compiled binary anywhere else, but I've done the following:
1. insmod and create mountpoint using `/system/etc/pre_hw_config.sh`
2. edited `res/xml/storage_list.xml` in `framework-res.apk`.
Now the USB storage shows up in system storage settings. The name showed "USB storage" though it still shows "mount USB". I can normally use it now.
It seems to be better than using 3rd-party applications.
alvinhochun said:
I am using Neo V official build 4.1.B.0.431 (ICS 4.0.4), rooted, unlocked bootloader (doesn't seem to matter)
I've downloaded the kernel source code, compiled the `usb-storage.ko` module, and placed it on `/system/lib/modules/drivers/usb/storage/`.
I've also changed `/system/etc/vold.fstab`, added this line:
Code:
dev_mount usb /mnt/usbstor auto /devices/platform/msm_hsusb_host.0
Then I restarted the phone.
After that, I typed the commands (using root) in shell:
Code:
mount -o remount,rw /
insmod /system/lib/modules/drivers/usb/storage/usb-storage.ko
cd /mnt
mkdir usbstor
Then I plugged in the OTG cable with a USB Flash Drive.
The storage is successfully mounted (by vold, I think), as I can verify in Root Explorer. I don't have photos so can't verify whether media scanner can detect it.
But in Settings->Storage it didn't appear. Seems that the Settings app don't support. I cannot unmount it using GUI, so when I remove the storage it warns me about that.
Are there any ways to get the Settings app to show my USB storage so that I can unmount via GUI?
Also how to automatically `insmod` and create `/mnt/usbstor` when startup? I won't bother editing ramdisk, but anything under `/system` is fine. I saw a few shell scripts under `/system`, are they fine to use?
Click to expand...
Click to collapse
Hi Alvin,
I´m having big issues with enabling USB Host mode as well (phone does not find any usb devices such as usb mouse or a pendrive), so I would greatly appreciate your help in finding the root of this problem. Here are the details and what I tried so far:
1. Im running on a rooted GT-i8530, leaked 4.1.2 rom with busybox installed
2. android.hardware.usb.host.xml permissions xml file exists in etc/permissions and just mentiones the apache license
3. Running USB host diagnostics I got:
Android API
Claims support yes
classes found yes
device detected no
Rooted API
Claims support N/A
Device detected N/A
Kernel
Claims support Yes
Device detected No
Verdict OS support No
3rd party apps No
4. I tried 3 different USB cables (original samsung one with female to female connector), another original micro usb to female plug, and a no name one,
5. No mouse nor usb sticks (fat32) seem to be recognized (below 200 ma)
6. Had a look into the storage folder and I can see a folder for external sd, sdcard and UsbA-UsbF. These Usb folders have no permissions set ( like rwx). Looking into the mnt folder I can see the same but in there the Usb folders have rwx permissions set.
7. I was thinking to manually mount the pendrive but when type into terminal as su: ls /dev/block there are no devices (like sda, sdb, sdc) or partitions ( sda1...) mentioned. So I didnt even try commands such as mount -t vfat /dev/block/sda1 /mnt/sdcard/usb...Only mmccblk, loop, dm, ram, vold, param is mentioned on dev/block
8. In vold.fstab all usb(a-f) folders including paths are visible
Now I read your post regarding the usb-storage.ko module and I guess thats whats missing for the phone in order to recognize any usb devices. Reason why I think that is because once I connect a usb device I cant even see any sda´s or sda1´s...In system/lib/modules the folder driver is non existent but I found in sys/module/usb_storage/drivers a usb-storage file but its not a .ko What do you think? I would appreciate your thoughts on that one..
Today my Tablet (Hyundai A7HD) with CM9 started behaving very strange.
It doesnt recognize my sd card, nor its own internal nand storage anymore.
I dont know what to do, since i cant even flash an update through CWM anymore without a functioning storage medium.
the sd card works fine on my pc and i cant format the internal storage through my tablet.
what else can i do to fix this?
I could really use some help, if someone knows a way to do it.
IndigoHD said:
I could really use some help, if someone knows a way to do it.
Click to expand...
Click to collapse
Supply more information. How do you know it's not detecting the internal storage? What are the symptoms? In my point of view, the device would be bricked in this case. Can it boot at all? Or is it fastboot complaining , trying to flash it? The internal memory, is it a MTD for /system plus an MMC for /data, or only an MTD? Only one MMC? Does the devices still exists or not? The partitions..?
Give us some more information, and we'll see if someone here can come with an intelligent suggestion.
Thank you for your reply!
The Device is an Hyundai A7HD and it says that what it calls "sdcard" but actually is its internal storage is damaged. Formatting doesnt work.
It still boots fine but cant access the internal storage, so nothing can be downloaded onto the device and such.
It has a special partition where applications are installed, but nothing can be saved there.
im guessing that something is wrong with the OS, and maybe i could fix it using ADB (if someone could explain to me how)?
Ok, so no /sdcard and /sdcard is supposed to be the phones internal memory, no /data partition, hence not able to download new apps, but the phone boots and so, i.e. system partitions works fine.
This sounds quite like this (confusing) thread to me. In summary, we are talking about three devices, the internal MTD device with /system, boot image, cache etc, the internal MMC device with /sdcard and /data plus an external sdcard named something like /sdcard/external_sd. The internal MMC broken beyond repair (hardware failure).
Still it may be something else only reassembling this.
If you believe your problem is due to some problem with your ROM I suggest you try to reinstall stock ROM using the vendors standard flash tools.
If this doesn't work, we can see if a solution similar to the one in the thread above may be applicable to you.
When i use Astro file manager to look at my phones storage the internal memory calls itself "sdcard" and my ACTUAL micro-sdhc calls itself "extsd" in a folder called "mnt".
the original flash tool doesnt seem to function anymore since i would normally hold down the "menu"-button, then plug the cable into my pc and while STILL holding menu id press power 7 to 10 times and then flashing would start automatically. but ever since installing cwm and a cm9 custom-rom, this doesnt seem to function anymore.
EDIT: in Clockwordmod recovery its called "emmc" for internal memory and "sdcard" for my actual sdcard.
Ok, this is consistent. Can you do a couple of shell commands?
# mount
and
# ls -l /dev/block
... and paste in the result here. As root or as shell user (or any other user) doesn't really matter.
when i plug the device into usb it says debugging enabled. so i open adb and type in "adb devices" and it starts listing devices. But no device is recognized.
EDIT: it recognizes my phone tho.
IndigoHD said:
when i plug the device into usb it says debugging enabled. so i open adb and type in "adb devices" and it starts listing devices. But no device is recognized.
Click to expand...
Click to collapse
Tricky. And not possible to install apps, so no ConnectBot or similar ...
Do you have a link to the CM9 you are using?
kuisma said:
Tricky. And not possible to install apps, so no ConnectBot or similar ...
Do you have a link to the CM9 you are using?
Click to expand...
Click to collapse
wait! i CAN install apps from the market!
and yes, one second.
http://www.slatedroid.com/topic/33373-rom-cm9-nightlies/
im using version 20120711
EDIT: Its an Allwinner A10 Device.
IndigoHD said:
wait! i CAN install apps from the market!
Click to expand...
Click to collapse
That makes all the difference!
So, what does "mount" say?
when i type "adb mount" it just gives me a long list of commands and explanations.
EDIT: there are many versions of connectbot. which one do we need?
IndigoHD said:
when i type "adb mount" it just gives me a long list of commands and explanations.
Click to expand...
Click to collapse
No, run mount from the command line using ConnectBot. ADB didn't work, you told me before.
$ mount
Click to expand...
Click to collapse
but which connectbot on the market is the right one? There are so many.
IndigoHD said:
but which connectbot on the market is the right one? There are so many.
Click to expand...
Click to collapse
Please. Show a little more effort.
https://play.google.com/store/apps/details?id=org.connectbot
i installed it and started it.
now it asks me to connect to a host.
i honestly dont know what im doing here.
IndigoHD said:
i installed it and started it.
now it asks me to connect to a host.
i honestly dont know what im doing here.
Click to expand...
Click to collapse
Select "local", give the session some name of you choice and connect. Now you are running a local shell in the same way as using "adb shell". You are familiar with "adb shell"..?
kuisma said:
Select "local", give the session some name of you choice and connect. Now you are running a local shell in the same way as using "adb shell". You are familiar with "adb shell"..?
Click to expand...
Click to collapse
isnt adb shell a terminal that accepts commands either locally or by usb connection?
EDIT: What should i do now on connectbot?
Can anyone help me, perhaps?
The screen is black and doesn't operate when you touch it.
I know you can get into the files using the recovery ...but I don't know how many volume ups and downs you need to get into it?
I am running the 5.0 JB CM10 recovery.
Volume up + volume down + power button if froyo bootloader
Volume down + power button if gingerbread bootloader
Sent from my SGH-T959 using xda app-developers app
What he is asking is, since he can't see the screen, he needs to know exactly the number of up or down spaces to get to.....
And this brings my question, where are you trying to get to in recovery?
I approve this message.
samsgun357 said:
What he is asking is, since he can't see the screen, he needs to know exactly the number of up or down spaces to get to.....
And this brings my question, where are you trying to get to in recovery?
I approve this message.
Click to expand...
Click to collapse
The option to mount USB storage....I don't think it has it anymore...I don't have It on my gs3
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
If its the same as the recovery in PA, semaphore
Its down 6, power
Up 2
I approve this message.
If you want to copy all your files from the internal storage using ADB: Reboot into CWM and connect it to your PC. In the command prompt, type:
adb shell
mount /dev/block/mmcblk0p1
(that's the partition of the internal storage in my vibrant)
exit
adb pull /sdcard C:\backup
(make sure you create the C:\backup folder first, it will begin to copy everything from your phone's storage to your harddrive)
-----
Optional: Once you are in adb shell, you can type this:
cat /etc/fstab (it will tell you the location of each partition that you can mount)
cd /sdcard (go to /sdcard partition)
ls -la (display all files in current directory)
Just remember to use 'adb pull' or 'adb push' you need to exit adb shell first.
Or just:
1. Pull battery
2. Attempt to get into recovery by guessing.
3. Adb shell Into device.
3.b if adb can't find device, go back to 1
4. Adb pull /storage/sdcard0/ or adb pull /sdcard/
It will be in the folder containing the adb file.
Sent from my GT-I9000 using xda premium
that /storage directory is new thing in Jelly Bean, I guess it does make things easier for people, instead of /sdcard and /emmc. It's a symbolic link, I don't even see it in adb shell.
The CWM doesn't auto mount the internal storage, so you still have to mount it first.
VeryCoolAlan said:
The option to mount USB storage....I don't think it has it anymore...I don't have It on my gs3
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
Maybe your GS3 uses MTP rather than mass storage.
Try: Up, Up, Down, Down, Left, Right, Left, Right, B, A, B, A
Sorry couldnt resist :laugh:
Lol, forgot select start!
I approve this message.
FaultException said:
Maybe your GS3 uses MTP rather than mass storage.
Click to expand...
Click to collapse
Probably.... I'm on CM10 .
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
I was experiencing the wifi+bluetooth ship failure that I fixed once, twice, ..., but the fix didn't last
My last attemp to fix that resulted in a flex cable ribbon damage (bad move)
Power button and touch screen are now broken
Sounds like it's time to change phone :crying: I'm not willing to repair this time
I'm trying to access internal storage but I am stuck:
I can:
- access bootloader options (buy plug-in power or usb cable)
- go into recovery, but I can't validate my selection (no power button)
- go into fastboot, but it seems that mounting is not a fastboot possibility
- go into rom (fastboot reboot), but I need to touch screen to activate usb mount
Any idea ?
cailloup said:
I was experiencing the wifi+bluetooth ship failure that I fixed once, twice, ..., but the fix didn't last
My last attemp to fix that resulted in a flex cable ribbon damage (bad move)
Power button and touch screen are now broken
Sounds like it's time to change phone :crying: I'm not willing to repair this time
I'm trying to access internal storage but I am stuck:
I can:
- access bootloader options (buy plug-in power or usb cable)
- go into recovery, but I can't validate my selection (no power button)
- go into fastboot, but it seems that mounting is not a fastboot possibility
- go into rom (fastboot reboot), but I need to touch screen to activate usb mount
Any idea ?
Click to expand...
Click to collapse
Try this http://droid-at-screen.ribomation.com/installation/
Use a desktop window to access your phone. A long time back when my screen went off, i used this to access my phone.
guruzen said:
Try this http://droid-at-screen.ribomation.com/installation/
Use a desktop window to access your phone. A long time back when my screen went off, i used this to access my phone.
Click to expand...
Click to collapse
Thanks, one problem: USB debugging is not activated (what a noob I am not to have USB debugging check lol)
Do you have a custom recovery? If so, you should be able to access the shell through adb and USB while in recovery.
cailloup said:
Thanks, one problem: USB debugging is not activated (what a noob I am not to have USB debugging check lol)
Click to expand...
Click to collapse
If ravilov method works, write an android program that registers for onBootReceiver. In onReceive() have this code
Settings.Secure.putInt(context.getContentResolver(), Settings.Secure.ADB_ENABLED, 1)
Put the apk under /system/app and change the permission to rw-r-r
Restart your phone, the above app must run onBoot and u will have usb debugging enabled.
Lets see how things go.
ravilov said:
Do you have a custom recovery? If so, you should be able to access the shell through adb and USB while in recovery.
Click to expand...
Click to collapse
I have big part recovery V3 from Zn7mkUKzN1r8aCIV
So accessing shell would let me mount storage ?
How do I use adb from recovery ?
guruzen said:
If ravilov method works, write an android program that registers for onBootReceiver. In onReceive() have this code
Settings.Secure.putInt(context.getContentResolver(), Settings.Secure.ADB_ENABLED, 1)
Put the apk under /system/app and change the permission to rw-r-r
Restart your phone, the above app must run onBoot and u will have usb debugging enabled.
Lets see how things go.
Click to expand...
Click to collapse
So I won't be able to mount storage from shell, but I can write lines that will enable usb debugging so that I can use your first post ?
I
cailloup said:
I have big part recovery V3 from Zn7mkUKzN1r8aCIV
So accessing shell would let me mount storage ?
How do I use adb from recovery ?
So I won't be able to mount storage from shell, but I can write lines that will enable usb debugging so that I can use your first post ?
I
Click to expand...
Click to collapse
Looks like u cannot mount sdcard. I found something about adb enabling in init.rc that u can retrieve. Put your phone in recovery and connect to the system and do adb shell
You must be in # prompt. Pull out init.rc using the command "adb pull /init.rc ."
I am attaching my init.rc. diff it and you should find differences wrt to adb. Try replacing the adb differences and ensure the chmod is done for init.rc (initial permissions)
guruzen said:
Looks like u cannot mount sdcard. I found something about adb enabling in init.rc that u can retrieve. Put your phone in recovery and connect to the system and do adb shell
You must be in # prompt. Pull out init.rc using the command "adb pull /init.rc ."
I am attaching my init.rc. diff it and you should find differences wrt to adb. Try replacing the adb differences and ensure the chmod is done for init.rc (initial permissions)
Click to expand...
Click to collapse
adb device is ok
I got the init.rc with adb pull, it is exactly the same as yours
I tried adb pull emmc
pull sdcard
pull scard0
pull scard1
pull storage
etc
Some don't work, some work but I got only files from "sys" folder
I tried this
http://forum.xda-developers.com/showthread.php?t=2339530
Same folder issue
I tried adb shell su mount but I don't know what to do with it ^^
Since our init.rc are similar, I also tried [email protected] but I have nothing in the device list (while phone is on)
If you enabled root for adb inside the rom, you can use the following command in adb to mount the internal storage:
echo /dev/block/vold/179:97 > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun0/file
That will mount internal storage as usb storage and you will be able to access the files from a computer.
Edit: I just read that you don't have it enabled >.< Another way would be to use "input tap x y" which does not require root but as you don't have it enable, something has to be done through recovery.
Second edit: Try this inside recovery:
adb shell
mkdir sdcard0
mount /dev/block/mmcblk0p18 sdcard0
Now that the internal storage is mounted on sdcard0, exit adb shell and use the following command:
adb pull /sdcard0 sdcard
This should copy all the files from the internal storage to a new folder called sdcard in your computer.
Reiki21 said:
Second edit: Try this inside recovery:
adb shell
mkdir sdcard0
mount /dev/block/mmcblk0p18 sdcard0
Now that the internal storage is mounted on sdcard0, exit adb shell and use the following command:
adb pull /sdcard0 sdcard
This should copy all the files from the internal storage to a new folder called sdcard in your computer.
Click to expand...
Click to collapse
Yeah that worked!
currently pulling everything, it's going to be long
Thanks all for help
Problem solved