Database Users

[Q] Sideloading/accessing folders in SD

I have built an SD bootable CM7 card as described by verygreen, but when I try to create folders on that drive from my PC (filled with APK files) I can't see them on the Nook. I have no problem doing this on my rooted emmc Nook, but when I boot to an SD card (that I am setting up for my daughter's Nook) I can't access any other folders/files.
What am I doing wrong? (The box is checked allowing Unknown Sources and I am currently running 177).

Are you connecting the nook via USB or putting the SD card in your computer directly?
Sent from my NookColor using Tapatalk

The card is placed in a usb card reader (or a usd card reader), either one sees the files on the PC, but it will not find it on the nook. Even when I create a folder on the nook and move the disk over and copy a file into the new folder I can't see it on the nook.

You need to connect through the nook
Sent from my LG Optimus V using Tapatalk

Littlewhat said:
The card is placed in a usb card reader (or a usd card reader), either one sees the files on the PC, but it will not find it on the nook. Even when I create a folder on the nook and move the disk over and copy a file into the new folder I can't see it on the nook.
Click to expand...
Click to collapse
This is because the partition the computer sees is the boot partition... to access it in the nook... either in terminal or adb shell:
1. mkdir /sdcard/boot
2. mount /dev/block/mmcblk1p1 /sdcard/boot/
the items on the boot partition of the SD (including the folders and apks you put there) will be visible as /sdcard/boot
Pretty sure you'd have found it in the VG SASD thread and a few others... since I have posted this several times.

Thanks for the response. I'm not real familiar with ADB so I tried it with terminal and was able to create a directory but mounting gave me a 'permission denied' message.
(Sorry if this is old info, I've spent the morning combing the SASD thread and haven't found it yet, just too much info, thanks for taking the time to help some of us who are slower learners!)
Edit: learning slowly, used su to get into superuser (#) and made directory, but when I try to mount it says not found.

Littlewhat said:
I have built an SD bootable CM7 card as described by verygreen, but when I try to create folders on that drive from my PC (filled with APK files) I can't see them on the Nook. I have no problem doing this on my rooted emmc Nook, but when I boot to an SD card (that I am setting up for my daughter's Nook) I can't access any other folders/files.
What am I doing wrong? (The box is checked allowing Unknown Sources and I am currently running 177).
Click to expand...
Click to collapse
If you asked this question 2 weeks ago, I might able to give you the exact answer but since I wiped out the uSD CM7, I can't remember correctly what would happen.
However, based on my experience (+/- my memory loss), what you describe is all correct and that's what it is. Odd? Maybe, but don't panic.
Let's go slowly
when I try to create folders on that drive from my PC
Click to expand...
Click to collapse
you meant you created a folder in the "boot" partition on the uSD card?
a. if so, it's not recommended. Using the left over FAT32 partition instead
b. if so, try to use Root Folder app (it's a paid app) to access root folder (boot partition) directly on the NOOK. If you see the folder you created earlier, move it to the eMMC storage.
c. if not, pls tell us more

Yes, the SD card was accessed on my PC thru a USB adapter and a folder called 'APKs' was created in the boot sector. (I have also tried just adding the files into one of the other folders, but anything I add is invisible to the Nook).
So if I need to create a folder in other than the boot sector, I would need to use something like Easeus Partition Master to make that sector active and then create the folder and add appropriate files? (When I rooted my Nook directly to emmc it sure seemed a lot easier to access folders created by my PC.)
(Thanks again for all your help.)

That's much clearer, m8
Now, I think it's easier to get straighten.
1. From PC, using SD slot or usb-sd adapter, move (remove) the "APKs" folder off your NC to your PC, save it there, then eject the uSD off PC.
2. Insert the uSD into the NC and turn it on, make sure it boots into CM7 properly.
3. Wait until it completely load. Now using usb cable to connect the NC and the PC.
4. Watch the notification status bar on the NC, tap on it then turn on usb mass storage.
5. PC should recognize the NC and ready for use.
6. Move your "APKs" folder from PC into your uSD (it would probably named as CM7SDCARD)
Update: on item 6, I prefer to move the folder to the eMMC storage. I'm not 110% sure if the NC see "it" (it means the left-over FAT32 partition on the uSD card) or not, but I do believe, 99% it will.

Deleted folder on SD card (from PC) and verified reboot ok.
Connected USB cable to PC then to Nook, no notification bar comes up, but battery icon shows charging as well as the lighted n on the cable.
Tried to use Nook Tweaks to begin USB connection (both boxes checked).
Still no recognition from the PC that anything is connected.
Edit: I am using my rooted Nook to build this SD card for my daughter's new unrooted Nook and when I plug the rooted Nook into the PC I don't get any verification from the PC on it either. No change on the Nook either, just the charging light and icon indicator.

Tried to use Nook Tweaks to begin USB connection (both boxes checked).
Click to expand...
Click to collapse
I don't have the NC with me now so I don't know what "both boxes" are and need to be checked or not.

The USB Settings from Nook Tweaks has a "USB Host Mode" (to enable host mode to connect peripherals) and an "External VBus" (to allow charging and hosting).
Both boxes were checked.
I've read that some of these issues can be caused by a faulty cable. If so, are there other alternatives to connecting thru the cable to open this up.
I have also tried the MiniTool partition program but I have not been successful in getting the active partition to 'stick' . (It immediately reverts back to the root being active after I apply the changes.)

You definitely have to UNCHECK the "USB Host Mode".
I'm not so sure with the "External VBus" status but suggest leave it by default.

With nothing checked in the Nook Tweaks section, USB cable connected to the Nook and then the PC, there is no recognition or acknowledgment that the Nook is there from the PC. (This is true whether I use my rooted version or try after booting to the sd card.)
If it is a cable problem, I will need to replace that, but aren't there other ways to make the sd card usable?
I've tried making the 4th partition action using Minitool and also Easeus but it didn't work. (Minitool just reverts back to boot partition active immediately after I apply the changes.)

Slow down, MiniTool and partitioning have nothing to do with this. Don't make more mess.
a. when plugging NC to PC, do you see any indication on the NC's status bar? like usb debugging?
b. when plugging NC to PC, do you see any indication on the PC (running Windows)? like removable drive?

There is no indication on the PC of any new connection.
The only indication on the Nook is the lighted n at the end of the cable and the recharging icon in the status bar.
Edit: the reason I was providing info on the MiniTools experience I was having is because my original question was how to access a folder (and files) created on my sd-bootable disk on my PC but the Nook can't see it. One way to accomplish this is to write the folder/apks directly to the Nook thru the USB cable. Other alternatives are to use windows to access it on my PC but I need to be able to access the 4th partition (if my reading of the various posts is correct). MiniTools and Easeus are two options that allow you to activate the 4th partition but it has not worked for my yet.
The USB cable connection problem appears to be there whether I boot to emmc or to sd.
Edit: I was able to find a non-nook cable (for my Blackberry) and using it my Nook recognizes when I connect to the PC and executes the USB Mass Storage Utility which allows me to turn USB storage on/off. Unfortunately the PC doesn't add any new logical drives in My Computer. The device manager shows 2 B&N Ereader Disk USB devices but with the yellow ! by them.

The 4th partition you mentioned about should be taken care during the installation, using verygreen's instructions, if you do correctly. There is ABSOLUTELY no need to mess around with MiniTool or the a-like.
Another question, have you turn on the USB Debugging feature? (I don't remember where, NC not with me now). If it not, check it box, try to plug in PC using usb cable again. I expect at least the usb debugging indicator will lit up.

I checked the debug feature (part of settings/applications/development/) and it was not checked. I checked it and now I get the robot icon (USB debugging conntected) and the USB icon to toggle storage on/off. Still nothing in My Computer and the drives shown in device manager are still yellow ! .
The device manager says "This device cannot start. (Code 10)"

I know it would be too early to say but I gonna to say anyway "congratulation".
When you see those icons on the NC status bar, it's 99% that it would work.
Now, back to the reality.
1. Connect usb cable between NC and PC running Windows
2. As you can see those icons, tap on the status bar to bring up then tap on "USB Mass Storage" (or something like "connect to computer for file/folder transfer, NOT the debugging). Read the warning then tap to enable USB connection
3. Now, pay attention on the PC, if it goes smoothly as expect, by now, you now can access both storages (eMMC and left-over of the uSD card) from PC. If so, move your "APKs" folder over.
I wish you luck

1- cable connected, icons on nook show up
2- tapping on status bar gives access to USB Mass Storage utility and option to turn on/off USB storage - with USB storage set to 'on' there is no recognition on the PC
Device manager shows two entries under disk drives for B&N Ebook Disk USB device but both are tagged with yellow ! (which a right click shows "This device cannot start. Code 10")
Is there something I need to do to download a usable driver for this?
(OBTW thank you for your help and patience)
Edit: within device manager I uninstalled the two drives (while the nook was still connected and USB active) and then had it search for new hardware. This time it loaded the drivers and NO yellow ! . At that point the PC recognized the drives and I have been able to create a folder that is accessible by the Nook and the PC. Thank you for help in this.
I have also contacted B&N and have a replacement cable on the way (which seemed to be a large part of my problems). Thanks Votinh for sticking with me while I got this resolved.

[Q] Transfer FROM Tablet TO USB Drive

Hi guys,
I'm getting tired of not being able to transfer files from my Nexus 7 [rooted] to a USB flash drive. I have Nexus Media Importer software installed, but it will only allow me to transfer files from the FlashDrive to the Tablet but not the other way...it's just plain dumb.
I usually download stuff via torrent to my Tablet and then distribute it to my friends, but when the files are over 4gb, bluetooth is way to slow and forget about the PC option, I don't have any PC to use...so don't tell me to transfer to a PC and then to the flash drive...
Any ideas?
EDIT: Also tried Stick Mount y USB Host Controller :/ NO LUCK!

Perhaps dumb questions, but since you didn't mention these details, everybody who reads your post is forced to guess.
1) Did you check the mount points (in each case) to see whether they were read-write (rw) or read-only (ro) ?
2) Should we assume that the USB stick only has a single partition, and that it is formatted in a FAT32 fashion? Or something else? What device/OS did you use to format the USB key to begin with?
If you are using any file system excepting FATx, the kernel you are using is also important - and you also failed to mention that.
BTW, I have successfully written large-ish files TO a FAT32 USB key on a OTG cable mounted via StickMount with a lightly-rooted stock N7 (essentially a stock ROM and stock kernel). "Large-ish" in this case is about 2.5 GB. (FAT filesystems are not capable of writing individual files larger than 4GB)
cheers

bftb0 said:
Perhaps dumb questions, but since you didn't mention these details, everybody who reads your post is forced to guess.
1) Did you check the mount points (in each case) to see whether they were read-write (rw) or read-only (ro) ?
2) Should we assume that the USB stick only has a single partition, and that it is formatted in a FAT32 fashion? Or something else? What device/OS did you use to format the USB key to begin with?
If you are using any file system excepting FATx, the kernel you are using is also important - and you also failed to mention that.
BTW, I have successfully written large-ish files TO a FAT32 USB key on a OTG cable mounted via StickMount with a lightly-rooted stock N7 (essentially a stock ROM and stock kernel). "Large-ish" in this case is about 2.5 GB. (FAT filesystems are not capable of writing individual files larger than 4GB)
cheers
Click to expand...
Click to collapse
No dumb questions at all, I just started this thread really quick because I am at work and can't be 'on the internet' for too long.
1) I just checked and Nexus Media Importer says 'read only', I haven't seen that :/ (that's dumb)
2) The owner of the USB Stick tells me he formatted it with Windows 7 but never changed the format, it's FAT32 since he bought it. The file I attempt to transfer is 4.1Gb...
About the kernel and ROM, both stock and ROOTED.
The owner of the USB Stick tells me that he recently used it to boot Win7 and install it on a friend's PC and maybe that's why it is on 'read only'. I've checked for the usual 'lock' switch but it doesn't have one...so that must be why. Don't you think?
Also, I could never use StickMount..it just times out attempting to mount :/
EDIT: One more thing, I downloaded 'USB Host Controller' (http://forum.xda-developers.com/showthread.php?t=1468531). I attempted to mount at /mnt/sdext and many other points but none of them worked...I'm using ES file explorer to look for the mount point but it doesn't exist.

Nanopane said:
1) I just checked and Nexus Media Importer says 'read only', I haven't seen that :/ (that's dumb)
Click to expand...
Click to collapse
Well, the name of the app includes the word "importer". That seems to imply only one direction, but I've never used the app so I don't know.
Nanopane said:
2) The file I attempt to transfer is 4.1Gb...
Click to expand...
Click to collapse
No matter how you mount a FAT32 filesystem, you will not be able to write a file to it which is greater than 4,294,967,295 bytes in length (2^32 - 1).
Apparently there is something called "exFAT" that is intended for large flash devices, but it seems to be not ready for prime time with Android yet. (Search titles here on XDA for "exFAT"). Also, the Wikipedia page for exFAT says that it is patent-encumbered. That's a deal-breaker for Android I suspect.
Nanopane said:
The owner of the USB Stick tells me that he recently used it to boot Win7 and install it on a friend's PC and maybe that's why it is on 'read only'.
Click to expand...
Click to collapse
Hard to say. Re-format it in windows and try again.

Thanks a lot Mr!
I'm gonna use some other app just to try to get it done, with a 'smaller' file. And regarding the USB Stick, let's just leave that behind...I can mount NTFS systems and give my friend the files in a Ext-HDD
Luckily there is always another option

[Q] External USB drives (HDD/SSD) And Mounting

[Q] External USB drives (HDD/SSD) and mounting
How does the SATV decide what directory it will mount an external USB drive to?
/mnt/media_rw/usbdrive
/mnt/media_rw/usbdrive2
/mnt/media_rw/usbdrive3
I keep noticing mine will change from one to another each time I reboot. This is really messing with Foldermount. Does it matter what other devices are plugged in? How can I force it to a certain one? I am rooted so if this can be done from terminal, I assume it's *NIX like, I'm all ears
thanks

Mine is mounting the same every time. Make sure you are connecting to the usb port every time obviously.

I personally use stickmount to mount inside the sdcard directly.

In my situation I have a SSD in an external USB 3.0 chassis that is always plugged in, same port. I just allow the OS itself to perform the mounting and have never had an issue where it didn't mount, it just intermittently changes the mount location it is using.
The big problem here is when it switches it screws up any app that previously had the drive noted at the last known mount folder. Foldermount being the main app but others like emulators lose the last folder used too.
Is the mounting process on an Android device similar to Linux? Will I find some config file that I can edit to force the mount location every time? Although I'm not sure why it changes sometimes, not all the time, on restarts of the device. For now I've been trying to not restart unless really, really needed.

I also use the same setup minus the fact that I use stickmount also. The system will still do what you are discribing, but it will also mount within the SD card in the same place every time for me.

Can't backup Nexus 4 using TWRP Mako 3.0.2.0

Hello,
I'm new to much of this. I want to flash Android M to my Nexus 4 but I am heeding many people's warnings to backup my device. However, nothing I've tried has allowed me to do so. In my searches, I discovered this thread that enables OTG flash drive support for Nexus 4 phones:
http://forum.xda-developers.com/showpost.php?p=66226991&postcount=48
But when I installed it over the stock TWRP 3.0.2.0, it showed an external slot with 0MB and would not allow me to select it. I've tried various flash drives, all formatted to FAT 32, I've tried a powered external USB 3.0 drive enclosure (NTFS formatted) - nothing works. The cable I'm using is not a "Y" cable, which is why I tried using my external backup drive, which is powered but NTFS. Is that the issue?
Finally I decided, to heck with it, I'll just create a nandroid backup to my phone's storage and then drag it onto my PC, but it only has 4.5GB free space left. I could go and uninstall most of my apps, but what is the point of backing it up then? I need almost 9GB of space on a device that has just 16GB.
This crap is so frustrating. I expect installing Marshmallow would be hard, but I did not expect a backup, which should be a simple operation, to be so challenging Any help would be greatly appreciated.

Did you try twrp 2.8.7?

audit13 said:
Did you try twrp 2.8.7?
Click to expand...
Click to collapse
Thanks for the suggestion - I just tried it. Using all the methods listed in my post (using straight non-Y cable) I get not OTG option when specifying storage location - just internal storage. I've ordered a OTG Y cable and will post back here if that helps.
Also, I purchased the "Live" option, thinking that would back my phone up to the cloud. After reading a bit, it appears that premium feature allows you to create a nandroid backup without booting to recovery mode. It's just about useless though because it requires selinux to be set to permissive - AFAICT, selinux is always set to something else and the process to get it set to permissive is pretty advanced and looks like a PITA. I guess the live option would be really cool for you advanced users...

dalewb said:
Hello,
I'm new to much of this. I want to flash Android M to my Nexus 4 but I am heeding many people's warnings to backup my device. However, nothing I've tried has allowed me to do so. In my searches, I discovered this thread that enables OTG flash drive support for Nexus 4 phones:
http://forum.xda-developers.com/showpost.php?p=66226991&postcount=48
But when I installed it over the stock TWRP 3.0.2.0, it showed an external slot with 0MB and would not allow me to select it. I've tried various flash drives, all formatted to FAT 32, I've tried a powered external USB 3.0 drive enclosure (NTFS formatted) - nothing works. The cable I'm using is not a "Y" cable, which is why I tried using my external backup drive, which is powered but NTFS. Is that the issue?
Finally I decided, to heck with it, I'll just create a nandroid backup to my phone's storage and then drag it onto my PC, but it only has 4.5GB free space left. I could go and uninstall most of my apps, but what is the point of backing it up then? I need almost 9GB of space on a device that has just 16GB.
This crap is so frustrating. I expect installing Marshmallow would be hard, but I did not expect a backup, which should be a simple operation, to be so challenging Any help would be greatly appreciated.
Click to expand...
Click to collapse
- Have you tried turning on compression and ignoring the disk space in TWRP?
- If that still fails, you can backup one partition at a time, then transfer it by adb before backing up the next partition, etc.

Thanks and solution
Thanks to those of you who suggested different things. The solution ended up being a combination of things - needed the Y cable (that allows power and USB flash drive to be plugged into phone at same time) and the TWRP build for Nexus 4 with OTG support. Once those two things were in place, I was able to select my flash storage device. The backup was right at 9GB - pretty big!

Requirements to format a USB drive so Shield TV & TWRP and access it's files?

I'm trying to find out the Android requirements to properly format a USB drive from either a Windows or macOS computer (Linux if required) so (A) I can mount it on Shield TV 2017 (16GB) and (B) TWRP 3.2.3.0 Recovery Project can actually read the files on it.
What are the exact requirements to format the USB drive so Android doesn't have to modify or update anything?
FAT32/NTFS/XFAT/Other ? from what I've read FAT32 seems to be the most preferable.
MBR/GDP/Other ?
Primary/Logical ?
What tool is the best to format this so there's no issues?
I've tried Gparted, Windows Format, Acronis, Disk Utility, MiniTool Partition Wizard, and a few others.
Are their any requirements to copy data (i.e. boot.img, boot.zip, readme.txt, etc...) files from Windows/macOS/Linux onto the USB drive so it's readable?
These may sound like primitive or stupid questions, however I've spent several hours trying to boot my Shield TV (usb keyboard holding keys A and B) to then launch TWRP 3.2.3.0 Recovery to then mount the USB and read its files to Install them. So far I've tried just about everything I've learned from the internet and nothing seems to work. I've even formatted the USB drive using a Sony Android (7.0) TV however when I attempt to insert that onto either a PC or Mac both require the drive to be initialized. When my Shield TV was still working any USB drive I inserted required it be formatted or updated in some way so it could read it.
Currently if I format the USB drive can be detected by Shield TV and mounted by TWRP however none of the files I've copied onto it can be viewed by TWRP. I understand that TWRP filters files so if one needs to load an *.img file one needs to press the correct button to "view" and "access" those file types.
I'm starting to believe it's not the USB it's TWRP but I can't tell for certain.

Does one need to create Android-x86 (android-x86_64-8.1-rc2.iso) in VMware to accomplish this task? It's mind boggling that this is seems to be so difficult when it should be rather straight forward.

whiteak said:
You have tried mounting the USB I take it? I would try a different USB Stick if you have one for sure, it doesn't have to be any special format at all, just a simple fat32 format through Windows is all it needs. Without actually physically seeing what is going on, I can't really say what is going on, power is actually getting to the USB, eg, can you see any lights flashing etc?
Click to expand...
Click to collapse
Hello whiteak, Shield TV sees the USB drive, TWRP is able to mount it, navigate to it and list folders but no files are displayed either through Install (to see boot.img, readme.txt or boot.zip) even when toggling the IMG or ZIP button. I've also attempted to use TWRP's File Manager to review this data, no success. In an alternate test to prove that TWRP can see any *.img file I navigated to the Downloads folder (internal storage) and it can see recovery.img just fine. Using TWRP's File Manager I've attempted to change the file permissions (chmod 755, 777, etc...) to the usb-otg but that didn't change anything either.
At this point I'm unsure what to think? Is it the way the USB drive is formatted? Is it file/folder permissions on the USB drive? Is it TWRP limiting things that are actually there but refuses to read them for security or some other reasons? Hard to tell...

SOLVED
I solved the problem. I'll post the exact steps later but in short, create a Virtual Machine, install Android 8.1, insert the USB drive, format it and quit. Once this is done PROPERLY I later copied the necessary files using macOS TERMINAL from macOS to the USB drive. Now TWRP sees everything. What a pain in the @$$ to do such a simple task.

nadia p. said:
I solved the problem. I'll post the exact steps later but in short, create a Virtual Machine, install Android 8.1, insert the USB drive, format it and quit. Once this is done PROPERLY I later copied the necessary files using macOS TERMINAL from macOS to the USB drive. Now TWRP sees everything. What a pain in the @$$ to do such a simple task.
Click to expand...
Click to collapse
i havent used twrp on my shield tv before but i typically prefer to use twrp's adb terminal for that type of stuff..
it sounds like u had something formatted wrong or maybe even some type of encryption on the usb so it couldnt see the files... u def. shouldnt have to do all that lol

elliwigy said:
i havent used twrp on my shield tv before but i typically prefer to use twrp's adb terminal for that type of stuff..
it sounds like u had something formatted wrong or maybe even some type of encryption on the usb so it couldnt see the files... u def. shouldnt have to do all that lol
Click to expand...
Click to collapse
Hello elliwigy, I'm quite new at all this so I didn't know how to format a USB drive using ADB, I didn't even know this was possible. I'll have to look into this next time. My workaround installing Android in VMware worked out well.