Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.hardware > #2236 > unrolled thread

Can't mount LG A341 phone

Back to article view | Back to comp.os.linux.hardware

Contents

  Can't mount LG A341 phone "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> - 2014-02-05 13:26 -0800
    Re: Can't mount LG A341 phone Michael Black <et472@ncf.ca> - 2014-02-06 00:40 -0500
    Re: Can't mount LG A341 phone Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2014-02-06 06:52 +0000
      Re: Can't mount LG A341 phone "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> - 2014-02-06 08:11 -0800
    Re: Can't mount LG A341 phone Eric Pozharski <whynot@pozharski.name> - 2014-02-06 09:49 +0200
      Re: Can't mount LG A341 phone Harold Stevens <wookie@limbo.localdomain> - 2014-02-06 05:24 -0600
        Re: Can't mount LG A341 phone Aragorn <thorongil@telenet.be.invalid> - 2014-02-07 01:34 +0100
          Re: Can't mount LG A341 phone Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2014-02-06 22:52 -0700
            Re: Can't mount LG A341 phone David Brown <david.brown@hesbynett.no> - 2014-02-07 09:16 +0100
              Re: Can't mount LG A341 phone JEDIDIAH <jedi@nomad.mishnet> - 2014-02-07 09:50 -0600
    Re: Can't mount LG A341 phone Doug Laidlaw <laidlaws@hotkey.net.au> - 2014-02-07 04:29 +1100
      Re: Can't mount LG A341 phone Eric Pozharski <whynot@pozharski.name> - 2014-02-07 10:03 +0200
    Re: Can't mount LG A341 phone buck <buck@private.mil> - 2014-02-06 17:55 +0000

#2236 — Can't mount LG A341 phone

I'm trying to access photos on my LG A341 cell phone, but I can't
seem to mount it.  When I plug in the USB cable, dmesg shows the
following lines:

[3292084.980030] usb 1-7: new high speed USB device using ehci_hcd and address
57
[3292085.097781] usb 1-7: New USB device found, idVendor=1004, idProduct=f000
[3292085.097786] usb 1-7: New USB device strings: Mfr=3, Product=2,
SerialNumber=4
[3292085.097788] usb 1-7: Product: LG Mobile USB Modem
[3292085.097790] usb 1-7: Manufacturer: LG Electronics, Inc
[3292085.097792] usb 1-7: SerialNumber: <serialno>
[3292085.099716] scsi59 : usb-storage 1-7:1.0
[3292086.100581] scsi 59:0:0:0: Direct-Access     LGE      MMC Storage     
2.31 PQ: 0 ANSI: 2
[3292086.100849] sd 59:0:0:0: Attached scsi generic sg7 type 0
[3292086.105834] sd 59:0:0:0: [sdf] Attached SCSI removable disk

$ ls -l /dev/sdf*
brw-rw---- 1 root plugdev 8, 80 Feb  5 13:12 /dev/sdf

$ sudo mount /dev/sdf /mnt/backup
mount: no medium found on /dev/sdf

Can anyone help?  I'd really hate to have to depend on some
Windows program to access files on my phone.

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  HTML will DEFINITELY be ignored.  Join the ASCII ribbon campaign!

[toc] | [next] | [standalone]

#2237

On Wed, 5 Feb 2014, Charlie Gibbs wrote:

> I'm trying to access photos on my LG A341 cell phone, but I can't
> seem to mount it.  When I plug in the USB cable, dmesg shows the
> following lines:
>
> [3292084.980030] usb 1-7: new high speed USB device using ehci_hcd and address
> 57
> [3292085.097781] usb 1-7: New USB device found, idVendor=1004, idProduct=f000
> [3292085.097786] usb 1-7: New USB device strings: Mfr=3, Product=2,
> SerialNumber=4
> [3292085.097788] usb 1-7: Product: LG Mobile USB Modem
> [3292085.097790] usb 1-7: Manufacturer: LG Electronics, Inc
> [3292085.097792] usb 1-7: SerialNumber: <serialno>
> [3292085.099716] scsi59 : usb-storage 1-7:1.0
> [3292086.100581] scsi 59:0:0:0: Direct-Access     LGE      MMC Storage
> 2.31 PQ: 0 ANSI: 2
> [3292086.100849] sd 59:0:0:0: Attached scsi generic sg7 type 0
> [3292086.105834] sd 59:0:0:0: [sdf] Attached SCSI removable disk
>
> $ ls -l /dev/sdf*
> brw-rw---- 1 root plugdev 8, 80 Feb  5 13:12 /dev/sdf
>
> $ sudo mount /dev/sdf /mnt/backup
> mount: no medium found on /dev/sdf
>
> Can anyone help?  I'd really hate to have to depend on some
> Windows program to access files on my phone.
>
No, I can't help.

But two things.  One is, I'm pretty sure I've seen Linux able to tell me 
what I've just plugged in, but unable to get a driver for it.  I recall 
that happening with my first cardreader, I never did get it going until I 
moved to a later release.

Also, some devices look just like memory, others don't. My Sansa Fuze MP3 
player has both MTP and MSC modes, I had to set it to the latter in order 
to mount it under Linux.  My Canon camera does only MTP, so I can't simply 
mount it, I'd have to use one of those special camera programs.  I don't 
know whether this is your problem or not.

  Michael

[toc] | [prev] | [next] | [standalone]

#2238

On Wed, 05 Feb 2014 13:26:11 -0800, Charlie Gibbs wrote:
> I'm trying to access photos on my LG A341 cell phone, but I can't seem
> to mount it. 

I'm not familiar with that particular phone, but on my own HTC G1 Android 
phone I need to use the drop down menu to activate USB storage on the 
phone before its disks can be seen from the PC. Then after mounting, 
using, and unmounting the disk(s) I also need to turn off USB storage 
from the drop down menu on the phone.

The file system on the flash is no cluster file system, the phone has to 
umount the filesystem itself before it can allow the host computer to 
mount it. Once the host computer is done, the phone can mount the file 
system again. This is what it looks like from the host computers point of 
view:

-8<---------------------------
Feb  5 20:15:15 minotaur kernel: scsi 23:0:0:0: Direct-Access     
HTC      Android Phone    0100 PQ: 0 ANSI: 2
Feb  5 20:15:15 minotaur kernel: sd 23:0:0:0: Attached scsi generic sg2 
type 0
Feb  5 20:15:15 minotaur kernel: sd 23:0:0:0: [sdb] Attached SCSI 
removable disk
Feb  5 20:15:24 minotaur kernel: sd 23:0:0:0: [sdb] 15954944 512-byte 
logical blocks: (8.16 GB/7.60 GiB)
Feb  5 20:15:24 minotaur kernel:  sdb: sdb1 sdb2
Feb  5 20:15:29 minotaur hald: mounted /dev/sdb1 on behalf of uid 406
Feb  5 20:16:27 minotaur hald: unmounted /dev/sdb1 from '/media/disk' on 
behalf of uid 406
-8<---------------------------

Note the time of 9 seconds gap between 20:15:15 and 20:15:24, that was 
the time it took me to use the drop down menu on the phone to give the 
storage to the host computer.

Do _NOT_ forget to umount the media on the host computer before giving 
the storeage back to the phone or unplugging the phone. Forgetting to do 
so might give a broken file system.

regards Henrik
-- 
The address in the header is only to prevent spam. My real address is:
hc351(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost

[toc] | [prev] | [next] | [standalone]

#2241

In article <52f33142$0$295$14726298@news.sunsite.dk>,
Henrik.Carlqvist@deadspam.com (Henrik Carlqvist) writes:

> On Wed, 05 Feb 2014 13:26:11 -0800, Charlie Gibbs wrote:
>
>> I'm trying to access photos on my LG A341 cell phone, but I can't
>> seem to mount it.
>
> I'm not familiar with that particular phone, but on my own HTC G1
> Android phone I need to use the drop down menu to activate USB storage
> on the phone before its disks can be seen from the PC. Then after
> mounting, using, and unmounting the disk(s) I also need to turn off
> USB storage from the drop down menu on the phone.

<HomerSimpson>
D'oh!
</HomerSimpson>

I rememer having to do this on my Sansa C200 MP3 player (RIP),
except that I could leave it in MSC mode.  My latest MP3 player
defaults to MSC, so I believed that my fantasy was coming true
and we were getting free of all this MTP/PTP crap.  I should
have known better... <sigh>

Alas, I can find no menu setting on my phone to set it to
MSC mode.  However, I now recall being in a similar situation
with my wife's phone (same make and model), where I hacked
around it by putting in an SD card and telling the phone to
copy the files there; then I could remove the card and read
it on a computer without going to the time and trouble (and
expense!) of e-mailing the files from the phone.

Thanks for your help, folks.

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  HTML will DEFINITELY be ignored.  Join the ASCII ribbon campaign!

[toc] | [prev] | [next] | [standalone]

#2239

with <1324.184T587T8063576@kltpzyxm.invalid> Charlie Gibbs wrote:
*SKIP*

> $ sudo mount /dev/sdf /mnt/backup
> mount: no medium found on /dev/sdf

AFAIU, there're two options (those aren't solutions, so far):

[*] Modern kernels have to be told that there's something.  There're
    "helpers" for common cases.  Probably, it's not common case.

[*] There's nothing to mount.  Or not yet.  Because,

> Can anyone help?  I'd really hate to have to depend on some Windows
> program to access files on my phone.

If there's block special for windopws, probably, "windopws drivers" spit
somet special magic into phone, and phone obeys.  Just like with that
Zeor-CD thing.

-- 
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom

[toc] | [prev] | [next] | [standalone]

#2240

In <slrnlf6fjh.rld.whynot@orphan.zombinet> Eric Pozharski:

[Snip...]

> "windopws drivers" spit somet special magic into phone, and phone obeys

IMO, this is likely FAT patent/licence skirmishing among Android phones
facing the Borg's rapacious tollroad business model based on an archaic
file system.

Whatever, I got fedup messing with mtpfs (etc.) workarounds. I resorted
to using Dropbox (2.5GB free cloud storage) for exchanges (I don't have
exceptional xfer volume, or security concerns).

Once again, Microsmut can kiss my nether regions. HTH, YMMV ...

-- 
Regards, Weird (Harold Stevens) * IMPORTANT EMAIL INFO FOLLOWS *
Pardon any bogus email addresses (wookie) in place for spambots.
Really, it's (wyrd) at airmail, dotted with net. DO NOT SPAM IT.
I toss GoogleGroup (http://twovoyagers.com/improve-usenet.org/).

[toc] | [prev] | [next] | [standalone]

#2244

On Thursday 06 February 2014 12:24, Harold Stevens conveyed the 
following to comp.os.linux.hardware...

> In <slrnlf6fjh.rld.whynot@orphan.zombinet> Eric Pozharski:
> 
> [Snip...]
> 
>> "windopws drivers" spit somet special magic into phone, and phone
>> obeys
> 
> IMO, this is likely FAT patent/licence skirmishing among Android
> phones facing the Borg's rapacious tollroad business model based on an
> archaic file system.

That depends on the Android version.  As of Android 2.3 onward, Android 
uses ext4 as its filesystem, and I think the new 4.x generation uses 
Samsung's special Flash-oriented filesystem - I forgot its name.  
Earlier versions of Android used FAT.

-- 
= Aragorn =

         http://www.linuxcounter.net - registrant #223157

[toc] | [prev] | [next] | [standalone]

#2245

Aragorn <thorongil@telenet.be.invalid> writes:

> On Thursday 06 February 2014 12:24, Harold Stevens conveyed the 
> following to comp.os.linux.hardware...
>
>> In <slrnlf6fjh.rld.whynot@orphan.zombinet> Eric Pozharski:
>> 
>> [Snip...]
>> 
>>> "windopws drivers" spit somet special magic into phone, and phone
>>> obeys
>> 
>> IMO, this is likely FAT patent/licence skirmishing among Android
>> phones facing the Borg's rapacious tollroad business model based on an
>> archaic file system.
>
> That depends on the Android version.  As of Android 2.3 onward, Android 
> uses ext4 as its filesystem, and I think the new 4.x generation uses 
> Samsung's special Flash-oriented filesystem - I forgot its name.  
> Earlier versions of Android used FAT.

That was my first guess, but according to
http://www.lg.com/ca_en/cell-phones/lg-A341
the A341 isn't an Android phone.  That page lists its OS as "LG OS (WISE)"
(whatever that is).

The problem with recent Android versions isn't the change in filesystem,
it's that Android no longer supports USB mass storage mode.  You now
have to use MTP (media transfer protocol).  I don't know why they did
this...

[toc] | [prev] | [next] | [standalone]

#2246

On 07/02/14 06:52, Joe Pfeiffer wrote:
> Aragorn <thorongil@telenet.be.invalid> writes:
> 
>> On Thursday 06 February 2014 12:24, Harold Stevens conveyed the 
>> following to comp.os.linux.hardware...
>>
>>> In <slrnlf6fjh.rld.whynot@orphan.zombinet> Eric Pozharski:
>>>
>>> [Snip...]
>>>
>>>> "windopws drivers" spit somet special magic into phone, and phone
>>>> obeys
>>>
>>> IMO, this is likely FAT patent/licence skirmishing among Android
>>> phones facing the Borg's rapacious tollroad business model based on an
>>> archaic file system.
>>
>> That depends on the Android version.  As of Android 2.3 onward, Android 
>> uses ext4 as its filesystem, and I think the new 4.x generation uses 
>> Samsung's special Flash-oriented filesystem - I forgot its name.  
>> Earlier versions of Android used FAT.
> 
> That was my first guess, but according to
> http://www.lg.com/ca_en/cell-phones/lg-A341
> the A341 isn't an Android phone.  That page lists its OS as "LG OS (WISE)"
> (whatever that is).
> 
> The problem with recent Android versions isn't the change in filesystem,
> it's that Android no longer supports USB mass storage mode.  You now
> have to use MTP (media transfer protocol).  I don't know why they did
> this...
> 

There were very good reasons for changing to MTP.  When using
block-oriented protocols (USB mass storage), then the filesystem can
only be mounted on one device at a time - if the computer has access to
it, then android device cannot access it.  Using MTP is more akin to
exporting the filesystem with NFS or SAMBA - the device /and/ the
computer can use the filesystem at the same time.  An additional
advantage is that the connected computer does not need to support the
filesystem type - thus they can use Samsung's FFS, or ext4, or whatever,
along with Linux, Windows and Mac hosts.

My old Fedora 14 system does not support MTP, so when I need to transfer
data with my telephone, I use a VirtualBox machine running a new Mint
version (a virtual "live cd" is fine) for accessing it.  Despite that
extra inconvenience, MTP is definitely a better choice than USB mass
storage device.

[toc] | [prev] | [next] | [standalone]

#2248

On 2014-02-07, David Brown <david.brown@hesbynett.no> wrote:
> On 07/02/14 06:52, Joe Pfeiffer wrote:
>> Aragorn <thorongil@telenet.be.invalid> writes:
>> 
>>> On Thursday 06 February 2014 12:24, Harold Stevens conveyed the 
>>> following to comp.os.linux.hardware...
>>>
>>>> In <slrnlf6fjh.rld.whynot@orphan.zombinet> Eric Pozharski:
>>>>
>>>> [Snip...]
>>>>
>>>>> "windopws drivers" spit somet special magic into phone, and phone
>>>>> obeys
>>>>
>>>> IMO, this is likely FAT patent/licence skirmishing among Android
>>>> phones facing the Borg's rapacious tollroad business model based on an
>>>> archaic file system.
>>>
>>> That depends on the Android version.  As of Android 2.3 onward, Android 
>>> uses ext4 as its filesystem, and I think the new 4.x generation uses 
>>> Samsung's special Flash-oriented filesystem - I forgot its name.  
>>> Earlier versions of Android used FAT.
>> 
>> That was my first guess, but according to
>> http://www.lg.com/ca_en/cell-phones/lg-A341
>> the A341 isn't an Android phone.  That page lists its OS as "LG OS (WISE)"
>> (whatever that is).
>> 
>> The problem with recent Android versions isn't the change in filesystem,
>> it's that Android no longer supports USB mass storage mode.  You now
>> have to use MTP (media transfer protocol).  I don't know why they did
>> this...
>> 
>
> There were very good reasons for changing to MTP.  When using
> block-oriented protocols (USB mass storage), then the filesystem can
> only be mounted on one device at a time - if the computer has access to

    Not a problem really. 

> it, then android device cannot access it.  Using MTP is more akin to
> exporting the filesystem with NFS or SAMBA - the device /and/ the

    ...except not nearly robust. This is even true on Windows.

> computer can use the filesystem at the same time.  An additional
> advantage is that the connected computer does not need to support the
> filesystem type - thus they can use Samsung's FFS, or ext4, or whatever,
> along with Linux, Windows and Mac hosts.

     Not that much of an advantage compared to the simplicity and thus
robustness of just mounting the mobile device in the simplest way 
possible. Even under Windows you end up with weird behavior because MTP 
doesn't behave like a real filesystem.

[deletia]

-- 
     Negligence will never equal intent, no matter how you 
attempt to distort reality to do so. This is what separates         |||
the real butchers from average Joes (or Fritzes) caught up in      / | \
events not in their control.

[toc] | [prev] | [next] | [standalone]

#2242

Charlie Gibbs wrote:

> I'm trying to access photos on my LG A341 cell phone, but I can't
> seem to mount it.  When I plug in the USB cable, dmesg shows the
> following lines:
> 
What is the cell phone's filesystem. Is it something that Linux can see?
Is it iOS or Android?

[toc] | [prev] | [next] | [standalone]

#2247

with <8ctcsa-f11.ln1@dougshost.douglaidlaw.net> Doug Laidlaw wrote:
> Charlie Gibbs wrote:
>
>> I'm trying to access photos on my LG A341 cell phone, but I can't
>> seem to mount it.  When I plug in the USB cable, dmesg shows the
>> following lines:
>> 
> What is the cell phone's filesystem. Is it something that Linux can
> see?  Is it iOS or Android?

May I remind that, in this particular case, mount doesn't complain about
filesystem being unidentifiable.  It complains about *media* being
missed.

-- 
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom

[toc] | [prev] | [next] | [standalone]

#2243

"Charlie Gibbs" <cgibbs@kltpzyxm.invalid> wrote in
news:1324.184T587T8063576@kltpzyxm.invalid: 

> I'm trying to access photos on my LG A341 cell phone, but I can't
> seem to mount it.  When I plug in the USB cable, dmesg shows the
> following lines:
> 
> 
> $ ls -l /dev/sdf*
> brw-rw---- 1 root plugdev 8, 80 Feb  5 13:12 /dev/sdf
> 
> $ sudo mount /dev/sdf /mnt/backup
> mount: no medium found on /dev/sdf
> 
> Can anyone help?  I'd really hate to have to depend on some
> Windows program to access files on my phone.

What does
  fdisk -l /dev/sdf
say?  I think you need to mount sdf1 not just sdf.
-- 
buck

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.hardware

csiph-web