Full easy instructions for running os remix off usb stick without errors - Supported Devices

This is a working usb install media creator method for os remix installation circumventing all known errors made for noobs including USING full drive internal storage space etc.
You will be able to use this usb stick for future creation of other usb install media
you will have the choice to also install to hard drive
you will need 2 x usb drives and require drive write speed to be higher than 10 mb/s
the first drive will be the installer drive and the second will be the actual usb drive used to run remix os.
For first drive basic fat 32 install you will need rufus 2.9 usb boot media creator
after creation of the installer drive keep it safe i reccommend you use a 4gb drive $4/£2 off ebay but get something thats got a write speed higher than 10 mb/s or else install will fail!
Format the second drive to your liking ext 4 for example on your pc with minitool partition or acronis disk manager (make sure the drive is formatted as primary and set to active flag)
1. Create fat 32 usb boot disk with first usb drive and rufus 2.9 and the remix os iso
2.make sure after creation you boot up the usb drive and enter remix os
3.make sure you dont boot up the ufi version of the boot up, only use the legacy version (it will have ufi next to boot drive in bios usb boot up list)
4.after you enter remix os go to settings and download the update (ota) (this is the main fix)(if this update fails you cannot proceed further with instructions)
5. After ota update reboot and enter remix os again and let android upgrade
6.after this stage is complete your fat32 remix os usb bootable drive is ready to create a usb drive that runs remix os from the drive itself.
7.insert the second drive in a usb hub and boot up the computer with both drives in the computer and boot from the first drive (the usb remix os installer drive)
8.boot up and at the grub boot menu (it should look blue with yellow writing not the black ufi version) press tab and type: INSTALL=1
9. then press enter then you will enter you will enter usb media creation menu select scan usb drives and select the second drive (the remix os running drive)
10. It will ask you what you want to format the drive as so select do not format option (becus you already formatted it)
11.then it will ask you to install first grub boot menu say yes
12. Then it will ask you to install second boot grub efi menu say yes
13. Next it will ask you if you want to format the boot partition or something like that say *** no ***
14. Then it will ask you if you want read/write privelage say yes
15. It will proceed to write the remix os onto the drive
16. When finished it will ask to restart (at this point i just switch the pc off by holding power button then restart and boot off the new second drive to run the os from it already upgraded too)
note: If wanting ntfs version of remix os then its a little complicated than this and you will need to use imgtools to increase the data.img file on the ntfs drive after creation with the first usb media creator drive.
The remix os ota update addresses the boot media creation errors. After the ota update all drives created with the grub menu installer boot up as they should but only ufi boot up option hangs!
Hope this helps hit the thanks dont forget so i know how many people were helped by this and if thats high i will continue helping happily! enjoy.
I have the ative pc pro xe700t1c the uk version with intel core i5 quad core and its also a convertible tablet with msata ssd as hdd drive and as you all probbaly know android was created for fast flash memory and linux format os so the best combination is an ssd and ext4 linux file format. I have a 64gb 544 mb/s msata drive in a usb 3.0 enclosure which i use to boot remix os and run it off it. Its perfectly smooth and fast enough and the ativ pc pro convertible laptop/tablet is fully compatible hadware software wise, no problems at all.

Related

I have bricked my SD Card!

I have bricked my 16G SD card
Anyone any idea how to get the stuff back off the card? I have tried putting it into a Desktop computer but the XP operating system just cant see it in File Explorer
Anyone any ideas?
Pete
Heh... Funny use of the word "bricked".
Originally, it was used to describe a phone that was broken in such a way that it could not be used as anything other than a brick.
Guess that's the way the language evolves..
Anyway, File Explorer can only read the device if the partition is ok.
If you've somehow corrupted the filetable, File Explorer won't see it.
Try this;
Right-click "My Computer"
Select "Manage"
Select "Disk management"
If you can see it as Disk# (where # is a number), you can probably delete the existing partition and create a new one.
Or if you can't see any partition data, just try to create a new one.
Good luck!
Bonzo said:
Heh... Funny use of the word "bricked".
Originally, it was used to describe a phone that was broken in such a way that it could not be used as anything other than a brick.
Guess that's the way the language evolves..
Anyway, File Explorer can only read the device if the partition is ok.
If you've somehow corrupted the filetable, File Explorer won't see it.
Try this;
Right-click "My Computer"
Select "Manage"
Select "Disk management"
If you can see it as Disk# (where # is a number), you can probably delete the existing partition and create a new one.
Or if you can't see any partition data, just try to create a new one.
Good luck!
Click to expand...
Click to collapse
whats up bonzo. i got the same problem. my 16gb that came with my hd2 is unreadable and unformatable within my device and cpu. in the disk management screen, i have the sd pluged in and it says that its disk 1 and "31 MB RAW" whatever that means. how would i go about patitioning the data to restore it? i dont care about the files because i backed them up and bought another 16gb. i wanted to see if i can get this unreadable 16gb back up. thanks in advance! just a side note, ive done no physical damage to it, all ive done is add media. the sd came with the phone so it is new. one day when i tried to access a movie and the sd didnt show in file explorer.
If you have a stuffed SD card, try plugging the card into a computer, and run TestDisk and PhotoRec. Hopefully you can get the data off it.
hi,the problem with my sd card is that my touchpro2 can read it but cannot write.I am using energyrom cdma May 23 on the fone.is it possible that having my 2gig transcend card in my fone during my upgrade could ve caused the problm.formatting with my hp laptop get to 90% but then says windows cant complete format.I can still see what I ve on the card but cant remove them or add anything on the card.Any help will be appreciated.thanx u all
wocko1 said:
If you have a stuffed SD card, try plugging the card into a computer, and run TestDisk and PhotoRec. Hopefully you can get the data off it.
Click to expand...
Click to collapse
Tried this but the computer can see the card as a drive - tried it in an USB stick adaptor and a hub ....no joy
Will try with windows 7 ..... possibly that better
Still stuck and dare not use my phone
PLeeeese ..... anyone any ideas ------ HELP
I'm also having problems with a 16GB SD card in my HTC Hero. My phone is rooted and I'm using the Amon-Ra 1.6.2 Recovery Image.
Booting into recovery mode I go to Partition SDCard, set 0MB for SWAP, 1024MB for EXT2 and the remainder for FAT32. Everything seems to go ok, but having installed some apps on my phone, my internal memory is lower than I would have expected. I've installed Quick System Info Pro and it tells me that it can't get any information for Apps2SD. I'm also having difficulties when copying data to the FAT32 partition, both when the card is in the phone and when it's plugged into a USB port on my computer.
Taking the advice to run testdisk, it reports the following:
Check FAT: unusual media descriptor (0xf0! = 0xf8)
Warning: Incorrect number of heads/cylinder 4 (FAT)! = 255 (HD)
Warning: Incorrect number of sectors per track 16 (FAT)! = 63 (HD)
1 P FAT32 LBS 0 0 2 1915 49 17 30767578
No EXT2, JFS, Reiser Cramfs or XFS Marker
2 P LINUX 1915 49 18 2039 181 62 2000421
2 P LINUX 1915 49 18 2039 181 62 2000421
No Partition is bootable
Can anyone help me decipher this? Am I right in thinking that the three warnings are simply because it's a memory card rather than a hard disk? Also, why is it showing that I've got 2 LINUX partitions?
Does anyone have any suggestions for getting it working? Is it worth making a live linux (Ubuntu?) CD and creating the partitions under that or can I do it while the card is in the phone using adb?
OR, is my SDCard busted?
Windows can't touch to removable (usb pendrive/SD) partition table, you need to use linux for remake it
Also, only one partition, Windows can see only one SD/USB partition
desmopro said:
Windows can't touch to removable (usb pendrive/SD) partition table, you need to use linux for remake it
Also, only one partition, Windows can see only one SD/USB partition
Click to expand...
Click to collapse
You mean it can only see one pen drive at a time?
he means it wont read more than 1 partition on a single drive, I re-wrote a usb key once for USB booting and somehow messed up the partitions, but HP USB Disk Storage Format Tool seemed to sort it
Well, I've since found a guide on here, written a few years back, to manually create partitions using adb shell and parted, and I've even resorted to downloading Ubuntu and using the LiveCD to boot my PC into Linux and then using the disk tools under that, and I'm STILL having issues.
I can create a FAT32 partition without any problems, the difficulties are coming when I then try to create an EXT2 partition; I get a read/write error.
So, all of this suggests to me that my SDCard is bricked and I need to send it back and get it replaced! Unless of course, anyone has any other suggestions?
enzydroid said:
Well, I've since found a guide on here, written a few years back to manually create partitions using adb shell and parted, and I've even resorted to downloading Ubuntu and using the LiveCD to boot my PC into Linux and then using the disk tools under that, and I'm STILL having issues.
I can create a FAT32 partition without any problems, the difficulties are coming when I then try to create an EXT2 partition; I get a read/write error.
So, all of this suggests to me that my SDCard is bricked and I need to send it back and get it replaced! Unless of course, anyone has any other suggestions?
Click to expand...
Click to collapse
are you using gparted in ubuntu? when i created mine for my hero, i had to tick one of the boot optiosn in gparted
also how is it connected to the pc?
Yes, I was using gparted in ubuntu, set to 'master boot record' I think it was. I've got a usb key with an adaptor for the micro sdcard.
enzydroid said:
Yes, I was using gparted in ubuntu, set to 'master boot record' I think it was. I've got a usb key with an adaptor for the micro sdcard.
Click to expand...
Click to collapse
keep on messing about with it, Its rare they die unless its been write to over 250,000 times of you have been trying to smoke it
I quit smoking nearly 3 months ago now!
Just to clarify, I create the FAT32 partition first, then the EXT2 partition. Am I right in setting it up with a master boot record (I think that's the option within gparted)?
Regarding the EXT2 partition, do I need to take ownership of it or just leave it for SU access only?
Cheers
may i know which partition you set as boot.?
i've tried to set fat32(boot),ext2,linux-swap still does not work. should i set all partition as boot. is there any limit on the size for ext2 and linux-swap partition?
how you partition the sdcard? connect to pc using usb card adapter or connect to pc using the phone?

[Q] phone does not connect to PC via USB

[SOLVED] : using dropbox now for file transfer...
After I installed the latest build of stock XDAndriod on my Rhodium, it does not connect to my PC (win-XP) using USB port. I have tried multiple times to reset my phone and re-flash my winmo with no help.
My computer does not detect a USB device at all when I connect my phone when in Android. When I plug in my phone, nothing happens. But my phone does begin charging from the USB port and does detect that is plugged in to a power source.
How do I get my PC to recognize my phone?
Phone details:
H/w : standard AT&T tilt2
Winmo : JackOS build Aug/19
XDAndroid version - [MJG]Rhod.2.2Froyo.083010.rar
Thanks,
Dhanvi
PS: I did check the thread here - http://forum.xda-developers.com/showthread.php?t=641444&highlight=USB+problems and that hasn't solved my problem.
If you read the port status, USB data connections are not currently supported. Only charging is supported via USB.
Thanks for that pience of info, but I do not see anything saying USB on the project development page. Is there some other page that I should be looking at too?
If that is indeed the case, then how do I transfer stuff over from my PC to my SD card when in andriod ? Is there any other method?
Thanks.
kapiladhanvi said:
Thanks for that pience of info, but I do not see anything saying USB on the project development page. Is there some other page that I should be looking at too?
If that is indeed the case, then how do I transfer stuff over from my PC to my SD card when in andriod ? Is there any other method?
Thanks.
Click to expand...
Click to collapse
Use dropbox. www.dropbox.com for you pc and download dropbox in the market.
Thanks for the tip!
Dhanvi
Great Idea but waiting for more help
Hey Fist post here about the xAndroid. I have to say this rocks!! First time I got it up I said to myself this is how a phone is supposed to run.
To the questions do any of you know if this USB connection is going to be fixed anytime soon sine I would really like to see if you can connect Google App Inventor to the phone while on this great mod.
Thanks
Lennyz1988 said:
Use dropbox. www.dropbox.com for you pc and download dropbox in the market.
Click to expand...
Click to collapse
By far the simplest way to get it done.
I went for installing ADB and droid explorer on my pc. It works, but I have much less hair now.
with the current way xdandroid is built, I can't see it being probable that usb mode will ever work (could be wrong, so feel free to correct me).
i.e. currently we have a FAT partition on the SD card and we loopback mount files on it to act as the android system and data file systems, and the fat can then act as a normal SD card.
because of this, it can't expose the FAT partition to anyone outside of the OS instance (i.e. 2 OS's will be writing to the FAT table (redundant I know) independently and can clobber each other.
On the other hand, I think the way the cyanogenmod port works, by partitioning the SD card into multiple partitions to hold the different sets of data (though not sure it takes it all the way), is an approach that could be made to work for usb access, if separate partitions would be made for the system and data file systems on the SD card and a third partition just used for the FAT FS. This way, android can unmount the FAT partition only (nothing else depending on it) and let it be accessed by whatever machine the device is attached to over usb.
there's a reason its not done this way currently as its much harder to manage and continuously update.
just my 2 cents.
Hm, does this also mean, you can not use tools like MyPhoneExplorer (Outlloksync via UBS with Android phones) due to absence of data over USB? Seems like a decent app, but it does not see my TYTN over USB, says no conenction. I also note, Windows XP is trying to install an 'Android Phone' driver when I connect the TYTN to the Laptop. Is this all somehow related?
Oddly, my phone decides to turn on USB after it's been sitting plugged in for a time, which exceeds an hour. It's like it checks for USB connectivity at some long interval.
thetoady said:
with the current way xdandroid is built, I can't see it being probable that usb mode will ever work (could be wrong, so feel free to correct me).
i.e. currently we have a FAT partition on the SD card and we loopback mount files on it to act as the android system and data file systems, and the fat can then act as a normal SD card.
because of this, it can't expose the FAT partition to anyone outside of the OS instance (i.e. 2 OS's will be writing to the FAT table (redundant I know) independently and can clobber each other..
Click to expand...
Click to collapse
With Android on my wife's HD2 (booting from Windows via Haret.exe) USB mass storage mode works fine, so it's definitely doable.
toadlife said:
With Android on my wife's HD2 (booting from Windows via Haret.exe) USB mass storage mode works fine, so it's definitely doable.
Click to expand...
Click to collapse
No clue how - when you're in WinMo, what happens when you plug in your phone and select to use it as a disk drive? It unmounts the SD in WinMo and mounts it on your PC. Same thing would happen in Android, but when the card can't be unmounted - as Android is running off of it.
arrrghhh said:
No clue how - when you're in WinMo, what happens when you plug in your phone and select to use it as a disk drive? It unmounts the SD in WinMo and mounts it on your PC. Same thing would happen in Android, but when the card can't be unmounted - as Android is running off of it.
Click to expand...
Click to collapse
Well I have no idea how it works. I just know that it works.
toadlife said:
Well I have no idea how it works. I just know that it works.
Click to expand...
Click to collapse
I've been told it's flaky on the HD2 and not recommended for use anyways. Still not sure how it works tho.
We won't have true SD card access (USB mass storage) until Android is flashed onto our devices. Until then, true USB mass storage will NOT work.
In the meantime, there's ADB. Perhaps the HD2 guys hacked something up based on ADB, who knows.

USB Mass storage mode - can't see drive in Windows.

Hi, I'm having trouble when using USB mass storage mode on my Kaiser TyTN II with Android Froyo.
When I connect the phone can't see the SD contents from the FAT32 partition.
I have flashed on my TyTN II the latest 2.6.32 kernel from here, and i'm using the Incubus26Jc's Super FroYo RLS16. I have partitioned my 4gb SDHC using GParted to 3 partitions, one of ~3gb in FAT32, next to one in ext2 of ~64mb, and the last one in ext2, of ~1gb for the system.
Strangely enough when using Ubuntu Linux, it sees ands mounts all three partitions without problems. And when inserting my SD to a card reader on windows, it sees the FAT32 partition and I can browse it, but I want to do this with the card on my phone and on windows.
What can be wrong?
You can't do nothing, actually Adb driver for our kaiser is not working on windows...
I'm testing now on my Windows XP laptop and it works... strange.
My home computer is running Windows 7 (and ubuntu) can't it be a problem of w7?
tOz666 said:
I'm testing now on my Windows XP laptop and it works... strange.
My home computer is running Windows 7 (and ubuntu) can't it be a problem of w7?
Click to expand...
Click to collapse
Oo are you serious?
ADB was fixed in the latest version of l1q1d's kernel, but is still incompatible with Windows 7. At least, in my case it doesn't work in Windows 7, causes my computer to freeze until I pull the plug on the phone.
2.6.25 kernel has nice compatibility for Dual Mount SD Widget, check if Super Froyo supports .25 kernels. For me Not So Super Froyo is doing the job on .25 kernel. Default USB Mass Storage mode never works. You can use Dual Mount SD Widget to do the job
For adb, I had no problem with it on .32 while I am using XP.
HUGE EDIT:
Now I understand
Windows can ONLY ONLY see the 1st primary partition on your Removable Flash drive. Plus, linux FS are not recognizable for windows. (you can use Partition Magic or a linux FS supported partition software to actually view them that they exist).
If you want to partition your SD Card in windows, just install HITACHI Microdrive Driver for your SD Card's removable storage and it will identify as a removable hard disk. (I actually did that to have 3 partitions on my 16GB Data Traveler )
dark_prince said:
Windows can ONLY ONLY see the 1st primary partition on your Removable Flash drive.
Click to expand...
Click to collapse
Well I already knew that, but I want to see at least the FAT32 partition for application install, loading mp3, and occasional data storage.
I'm only a couple of days in the android on kaiser world, what is ADB? I read that you need some drivers to make it work, and can be used to install apps etc. but when I connect the phone it doesn't request me drivers unless I select mass storage mode. On Windows 7 it sees it as a Disk in device manager but can't see the drives. On XP it has no problems, it can browse FAT32 part.
So if Android is exposing the phone as a mass storage drive why it doesn't work in 7?
tOz666 said:
Well I already knew that, but I want to see at least the FAT32 partition for application install, loading mp3, and occasional data storage.
I'm only a couple of days in the android on kaiser world, what is ADB? I read that you need some drivers to make it work, and can be used to install apps etc. but when I connect the phone it doesn't request me drivers unless I select mass storage mode. On Windows 7 it sees it as a Disk in device manager but can't see the drives. On XP it has no problems, it can browse FAT32 part.
So if Android is exposing the phone as a mass storage drive why it doesn't work in 7?
Click to expand...
Click to collapse
Because android's itself "Turn on USB Mass Storage" mode doesnt work. Use a Multi Mount SD Widget or Dual Mount SD Widget or SD-Share to do the job
ADB is: http://developer.android.com/guide/developing/tools/adb.html
Just a tool to remotely administer your android device from command prompt
Try installing Hitachi Microdrive Driver in Windows 7 and see if it does any better
http://www.uwe-sieber.de/usbtrouble_e.html
dark_prince said:
Because android's itself "Turn on USB Mass Storage" mode doesnt work. Use a Multi Mount SD Widget or Dual Mount SD Widget or SD-Share to do the job
ADB is: http://developer.android.com/guide/developing/tools/adb.html
Just a tool to remotely administer your android device from command prompt
Try installing Hitachi Microdrive Driver in Windows 7 and see if it does any better
http://www.uwe-sieber.de/usbtrouble_e.html
Click to expand...
Click to collapse
Thanks for the tips. Are you suggesting that installing the Hitachi Microdrive Driver (by the way, I noticed that it's intended for Windows XP) could help in mounting the device using Android's built-in mount option?
cerebralgenius said:
Thanks for the tips. Are you suggesting that installing the Hitachi Microdrive Driver (by the way, I noticed that it's intended for Windows XP) could help in mounting the device using Android's built-in mount option?
Click to expand...
Click to collapse
Hitachi microdrive driver is intended to identify your Flash Drive as USB Hard Drive to see all partitions correctly in windows and allows you to partition your USB flash drive
Nope it wont help, since .32 kernel has not supported USB driver which hinders the USB Mass storage functionality, even through Dual mount apps.
If you are using Kyle's FAT Free Froyo or Not So Super Froyo, install a .25 kernel and then use Dual Mount USB app. It will work for sure.
Another Work Around:
If you just want to move some files to SD Card and you connect your network connection through wifi, you can try ES File Explorer to view Windows Based File Shares, just like you are seeing shared folders from another PC I use it since I connect my mobile and my PC through a wifi router

Mobile Transfer Protocol (MTP) v.s. USB Mass Storage (UMS)

Hi,
i wonder why they dropped mass storage device mode on the Gen9 devices.
No problem in the Windows world though, but i'm frequently using linux on my host computers and i'm little annoyed about the new MTP mode.
What do you think, could this be reverted easily?
Did anyone checked this out by tweaking some code or using a custom kernel?
Any information would be nice!
EDIT: O.K. i did some research... there's a lot discussion about it already.
Anyway would be nice to read your opinion.
Regards,
scholbert
I still see the mass storage option in my 4GB 80 G9, though I prefer MTP mode because it allows access to internal storage as well as SD card.
Yeah sure...
AFAIK, if you got a MicroSD in the slot it is accessed as USB mass storage.
I related to the device itself...
Anyway this will clear things up a bit.
I'll install libmtd and stuff on my laptop running Debian and see if it works out like expected.
Thanks for your reply!
scholbert
Well, internal storage is "media" directory of /data partition and it would be too dangerous for Archos to export whole /data as mass storage.
The benefit of this is to get rid of the limit of installed apps versus storage, the downside is that they can't export it as a drive. Google is pushing for this model too afaik.
Don't forget that storage for both SD and HDD models is formatted as ext4- unreadable for Windoze (it's the only reasonable option- fat32 supports max 32GB partitions, NTFS is not linux-frielndly IMO)
BTW it seems to me that MTP is becomming more popular- Xperia Arc S offers both MTP and UMS (MTP is factory default)
I don't know how to use it under Ubuntu or Linux mint, any recommendations?
thanks in advance.
get things rollin' on linux
Hi,
i started to do some research how to activate/implement the MTP on my laptop running Linux Mint (in partitular LMDE). Process would be the same for Debian and similar for Ubuntu.
To fully support the Gen 9 series libmtd version 1.1.2 should be installed on your machine.
See the logs at http://sourceforge.net/tracker/?group_id=158745&atid=809061
To start you need some essential packages first.
Afterwards you'll be able to see the device. I'm still in the process of sorting out how to make it work pleasantly.
Right now it'S not working the way it should. Anyway here are some requirements...
If you're on Debian Wheezy, simply install libmtp and stuff using your package manager.
Older versions only support older versions, not matching for the Archos G9 series.
If you're on Linux Mint it is possible to install version 1.1.2 manually from console (to force a partial upgrade).
Unfortunately some tools are little behind in this distro (at least LMDE)
Grab at least four packages from Debian Wheezy repo (e.g. 64bit machine):
- libmtp-common_1.1.2-2_all.deb
- libmtp9_1.1.2-2_amd64.deb
- libmtp-runtime_1.1.2-2_amd64.deb
- mtp-tools_1.1.2-2_amd64.deb
Remark: Install these in the right order. See the command below.
I found it to be safe to upgrade these packages partially, no depends are broken afterwards.
Please do not update your repository sources to point at the wheezy tree.
This might definitely confuse your package manager.
Additionally needed for handling virtual drives (better use package manager for install):
- fuse
- mtpfs
On Linux Mint (LMDE) you might then simply enter a root console to force upgrade of native libmtp:
Code:
dpkg -i libmtp-common_1.1.2-2_all.deb libmtp9_1.1.2-2_amd64.deb libmtp-runtime_1.1.2-2_amd64.deb mtp-tools_1.1.2-2_amd64.deb
I am not using Ubuntu, but i found out that 1.1.2 has found its way in 12.04 (precise), which is yet to be released.
Remark for Ubuntu 11.10 (oneiric):
In this distro libmtp 1.1.0 is used, unfortunately no Archos G9 support natively.
You could try to force a partial update though.
Please check dependencies first!
After installing you should add your username to the group audio:
Code:
adduser your_username audio
This is because the Gen 9 devices enumerate as audio device in the USB device-tree.
If you leave this out, only root will have access to this device.
Though this might be considered as optional.
Now you'll be able to use the mtp-tools (as a user) to discover your device and do lowlevel stuff.
As already stated things are not done automatically.
I will investigate, maybe some things are missing... (e.g. install package mtpfs).
Maybe this is the reason, why i got no virtual drive.
After installing mtpfs you may mount the internal storage of your Archos device (as root):
Code:
# mkdir ~/g9-storage
# mtpfs -o allow_other ~/g9-storage
The internal storage is now accessable...
To unmount:
Code:
# fusermount -u ~/g9-storage
Even with some scripting this is far from automount (like known from USB mass storage devices), but it works.
I'll try to find an even more convenient way...
Stay tuned!
scholbert
Any way to enable USB Mass Storage mode?
On 4.0.28 (stock), I only have MTP and PTP. I would like it to work as a "Normal" USB mass storage device, like most Android devices.
If all I can see is the SD Card, that's fine. It's much more convenient that carrying around a USB Card reader, and having to remove the card.
--
AW: Mobile Transfer Protocol (MTP) v.s. USB Mass Storage (UMS)
Hi, you can use FTP over Wi-Fi. With root access you can export every file you like.
Sent from my ARCHOS 101G9 using xda app-developers app
AW: Mobile Transfer Protocol (MTP) v.s. USB Mass Storage (UMS)
Hi, you can use FTP over Wi-Fi. With root access you can export every file you like.
Click to expand...
Click to collapse
Several other options:
1. SD card reader - Some Micro SD cards come with a tiny USB reader.
2. SD card adapter - Some Micro SD cards come with an adapter that lets them be used in a full size SD slot.
3. ADB via command line. adb push and adb pull.
Best I have found:
4. Use the file manager in DDMS. DDMS includes a simple file manager. It's basically a GUI for adb push and adb pull. DDMS is part of the Android SDK.

OTG device corrupted after uprade

Hi all,
I'm using an LG Nexus 5X with a custom ROM (LineageOS 15.1)
Device Background (upgrade path etc)
I upgraded from LineageOS 14.x via recovery.
Appart from initial trouble with the wizard (couldn't switch apps via recents or get notifications until editing some properties manually), and an occaisional hang on the google screen between restarts (boot to recovery and reboot typically solves it), all is working well.
On Lineage 14 I had to perform some unantural acts to get OTG working. Whilst I could mount with root, the fusemounted sdcard (and SELinux I suspect) was preventing anything other than root writing (and even reading) the contents of my flash drive.
After a lot of fussing about, I got OTG working by simply running:
Code:
sm set-force-adoptable true
Note however that I was NOT using the device as internal storage. It was a simple NTFS system.
After the upgrade to Lineage 15, I can no longer use OTG (neither my NTFS drive or my Fat32 drive).
I've not modified the drive between last I used it on Lineage 14, but when I plug it in, I get a message saying the usb drive is "corrupted" - and the phone offers to format it. I don't want to format it to Fat32. exFAT is fine. Really extfs would be ideal, but I'm not going to limit my files to 4GB size just because of android.
I don't believe this is a Lineage issue. Android has historically been cagy about allowing external storage to be mounted, so my hunch is some new permissions/security model in oreo.
Posting mainly as all other posts on the net tell you to reformat. I know for a fact this is not necessary (because of working on Lineage 14).
EDIT: Please do let me know if you've figured how to have OTG devices connected correctly. MiExplorer etc work, but it's not the same. With OTG working properly, I don't need root and all apps (that support OTG of course) work.
EDIT2: so my drive was formatted to exFAT not NTFS. The moral of the story:
Format as NTFS if you want plug'n'play support on Android 8. Haven't tried extfs. exFAT definitely didn't work though.
exFAT is patent encumbered. Not all manufacturers have paid the patent fees to be able to use it.

Categories

Resources