I have a Tab S4, so I'm posting this question here, but it really is a general android question, so if anyone knows a better forum to post at please let me know....
So I use otg dual drives to copy files back and forth between my phone, tablet and PC. I've had errors galore including scrambled data and a fried thumb drive issues started on my Tab S2 and seem worse on my Tab S4. Both my primary drives were SanDisk. For the S2 it was an Ultra Dual USB / micro drive for the S4 it was the Dual ultra with adaptor to USB C as well as a USB C to USB 3.1 dual drive. They are both formatted exFat32.
I always eject from windows. On the tablet, I usually use ES File Explorer, and use the eject button therein.
On the PC, it almost always pops up with the warning "your drive has problems, click to scan for errors" and scanning lead to scrambled files.
On ES File Explorer, it usually is detected initially as both an sd card and a USB drive; the card designation disappears after you select the drive. Usually you hit eject and the drive drops off the list, but sometimes it reappears as an SD card. Then I can't eject it, even through Android settings, and files always are scrambled when I disconnect. In the worst case, the USB Ultra drive was locked read-only and had to be exchanged by RMA.
So what is causing all the problems? Is there a safe way to transfer files with a flash drive? Or do I need to figure every third or fourth time I'm going to lose all the files on the drive?
Thanks
Joe
I know I'm bumping an old thread, but I would like to point out, ES File Explorer is to be avoided! The app was great many years ago, but then they introduced so much bloatware.
I use FX File Explorer. Developers are US based. They provide error handling on file transfer corruption. If I am doing a large file transfer I will use copy/paste, which is safer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, since I originally posted this thread, ES File Explorer has been pulled from the Play Store. I've since switch primarily to Solid Explorer. Granted they are Eastern European., still not American. There are features I miss from ES File Explorer, but I haven't had any problems with my USB storage devices since I made the switch. I think the eject function in ES File Explorer was the culprit. In Solid Explorer, "eject" takes you to the Android storage settings where you dismount the memory stick. It isn't as convenient as an eject button within the explorer app, but it seems to be much more reliable. Not only have the file scrambles gone away, but I no longer get the message that the stick needs to be error checked.
Thanks
Joe
drjoe1 said:
Yes, since I originally posted this thread, ES File Explorer has been pulled from the Play Store. I've since switch primarily to Solid Explorer. Granted they are Eastern European., still not American. There are features I miss from ES File Explorer, but I haven't had any problems with my USB storage devices since I made the switch. I think the eject function in ES File Explorer was the culprit. In Solid Explorer, "eject" takes you to the Android storage settings where you dismount the memory stick. It isn't as convenient as an eject button within the explorer app, but it seems to be much more reliable. Not only have the file scrambles gone away, but I no longer get the message that the stick needs to be error checked.
Thanks
Joe
Click to expand...
Click to collapse
do you why it was pulled?
Sent from my SM-G975U using Tapatalk
The Chinese publisher had all their software pulled for violating Google Play Store policies including not identifying the real publisher names, and fraudulent ad-click behavior.
See
https://www.androidpolice.com/2019/...lay-store-possibly-part-of-do-global-scandal/
Or do a Google search.
Joe
ilabstudios said:
I know I'm bumping an old thread, but I would like to point out, ES File Explorer is to be avoided! The app was great many years ago, but then they introduced so much bloatware.
I use FX File Explorer. Developers are US based. They provide error handling on file transfer corruption. If I am doing a large file transfer I will use copy/paste, which is safer.
Click to expand...
Click to collapse
The free version is garbage The Old Pro version is amazing. I still use it today I keep the old version of the file on an SD card in anytime I get a new device I just load that up
My Tab S4 cant copy files back to OTG Flash drive !!!!!!!
Ok I have a Sandisk dual drive and m using it on my Tab S4. it copies data from the Pen Drive to the internal and Micro SD card but when I try to copy anything from the Tab onto the Flash drive it shows "Operation not Possible"............ Weird Issue. Any Solutions guys???
So a number of the stupid questions that always need to be asked :
Is the drive formatted for exFat 32? If not reformat it.
Do you always properly eject the drive from Windows and unmount it from Android? If not, it may need to be reformatted.
What file manager are you using?
Does it work using a USB 3.0 hub or a USB 3.0 to USB C adaptor?
I find I get the best results by installing and removing the drive systematically:
1) Insert the drive
2) Wait for the tablet to recognize the drive. In the upper left status bar you'll see the USB icon and if you swipe down it will say "SanDisk USB Drive, Tap here to transfer media files" Don't bother tapping to transfer, just move on to #3.
3) Open your file manager and copy to / from the drive. I like Solid Explorer because it opens two locations side by side. Choose internal memory or SD Card for one side and the USB drive for the other.
4) Close the file manager
5) Swipe down and press the down arrow next to "SanDisk USB Drive" "settings" and unmount the drive
6) Wait until the pop-up says unmounted before you unplug the drive
I sometimes get read errors if I skip step #2 above. You can scramble the drive if you fail to dismount it (or manually eject it from Windows)
Good luck,
Joe
This is old, but I'll update it. I've had the USB notification on the status bar disappear from my Tab S4 and S10 Edge. It reappeared on my Tab S4 after the Android 10 update. Ot sure why it went away or why it came back. While it is gone you have to go to Android settings, device care, storage, advanced, and unmount the USB drive. Your file manager may have a shortcut - Solid Explorer does; press the three dots next to the drive name in the drive list and press unmount and it takes you directly to the Android settings screen.
Joe
Related
Droid Explorer and Android Commander are cool little programs run through Windows that let you batch install/uninstall apps, contacts, and a ton of other features such as screen shots and moving files around etc.
Droid Explorer Direct Download http://www.mediafire.com/?zjjmwtgimtz
Site: http://de.codeplex.com/
To get Screen Cast (interactive PC/Phone control which you can record as a video or tutorial) to work properly on some systems, dl this.
View attachment androidscreencast.zip
http://forum.xda-developers.com/attachment.php?attachmentid=329993&d=1274450154
Thanks to dianeofarcadia for the link
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
Multiple Device Support
Copy and auto-apply update.zip
Copy local files to device
Auto detection of connected/disconnected device
APK file icon and extended information
Device command shell window
Reboot device
Reboot device in to recovery mode
Open files for viewing / execution locally with the default file type executable
Drag & Drop file copy from Explorer
Flash Recovery Image
Package Manager (Install & Uninstall)
No need to mount SD card to access files from computer
Access files in other directories besides SD card
Copy files from device to local clipboard
Paste files from local clipboard to device
Open files on local machine
Display open with dialog to specify what to open a file with
Right click APK and Uninstall
Right click APK and Install
Delete files from device
Take a Screen Shot (landscape or portrait)
Plugins can register as a component to open files
Open from within Computer
Should now work with more ROMs as long as they are Rooted and have busybox
Device "Friendly Name" instead of device serial number.
Android Screencast Plugin - Control your android device with your mouse and keyboard
Install/Uninstall APK files right from explorer
Standalone plugin runner (will mainly be used for windows 7 jump lists and the apk installer but can be used to run any plugin.
Better Hero Support
Backup the "Google Experience" applications and creates an update.zip containing the applications
Android Commander Direct Download Link http://www.mediafire.com/?zzzymtiyezy
Site: http://androidcommander.cyf.pl
Features
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- update
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more…
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off phone
- screenshots (beta)
- tools…
Download link to my folder @ MediaFire
http://www.mediafire.com/?sharekey=27287fde074a5250e62ea590dc5e5dbbdc566628acb63ad8d6f20ee4ff677d52
Just wanted to share because it seems not a lot of people know these are out there. Enjoy!
MUST HAVE ROOT... probably...
seems promising
will have to check out Android Commander.
Droid Explorer runs pretty good, a bit laggy at times but it is promising. Hope it is ok to attach this jnlp to go with Droid Explorer in case anyone needs it. It was the only way to get screen cast to work properly. Just un zip, and toss the folder on the desk top. It helps start up the screen cast mode for Droid Explorer, in case anyone has trouble getting the one inside DE to work. Hope this helps.
dianeofarcadia said:
will have to check out Android Commander.
Droid Explorer runs pretty good, a bit laggy at times but it is promising. Hope it is ok to attach this jnlp to go with Droid Explorer in case anyone needs it. It was the only way to get screen cast to work properly. Just un zip, and toss the folder on the desk top. It helps start up the screen cast mode for Droid Explorer, in case anyone has trouble getting the one inside DE to work. Hope this helps.
Click to expand...
Click to collapse
Thank you for that. It already worked for me but I'm sure it will help others. I'll update the post and give you credit if you dont mind.
LexusBrian400 said:
Thank you for that. It already worked for me but I'm sure it will help others. I'll update the post and give you credit if you dont mind.
Click to expand...
Click to collapse
(I should look and find who wrote it, I found it somewhere here digging while troubleshooting). Glad it worked for you, now I need to know what is wrong on mine. lol.
the driod explorer says i am trying to install on the wrong platform? i have 64bit vista.. any ideas?
android commander says it cant find the sdk, i have it but i cant make this thing work for nothing, any ideas?
j-stang said:
the driod explorer says i am trying to install on the wrong platform? i have 64bit vista.. any ideas?
android commander says it cant find the sdk, i have it but i cant make this thing work for nothing, any ideas?
Click to expand...
Click to collapse
Go to the main site links. These links are for Win-7 32 bit. They should have a 64 bit on the main sites.
Will check it out thanks!
I got android commader to work.
-------------------------------------
Sent via the XDA Tapatalk App
This is really cool, thanks.
So the wife has been asking for a solution on watching videos hulu.com on the tablet, but afaik it doesn't work on any current browser. After putting my mad Google skill to work, found a paid app for $.99 called Flash Video Browser (buy it on Amazon cause Google market will show not compatible) which does the job.
http://www.amazon.com/Daniel-Lockard-Flash-Video-Browser/dp/B006IHK9PK
I even tried it on my Iconia A500 and it works there too.
deboyz1014 said:
So the wife has been asking for a solution on watching videos hulu.com on the tablet, but afaik it doesn't work on any current browser. After putting my mad Google skill to work, found a paid app for $.99 called Flash Video Browser (buy it on Amazon cause Google market will show not compatible) which does the job.
http://www.amazon.com/Daniel-Lockard-Flash-Video-Browser/dp/B006IHK9PK
I even tried it on my Iconia A500 and it works there too.
Click to expand...
Click to collapse
I watch stuff on Hulu.com all the time (about once or twice a day) with the stock browser from CyanogenMod 7.1.0.1 and the latest Flash from the Market (with a modified libflashplayer.so file which tells Hulu it's a Windows PC you're coming from and not an Android device) and changing the UserAgent setting in the browser to tell Hulu.com that you're coming from a desktop web browser (as a lot of their videos are not licensed for mobile viewing).
Just replace the libflashplayer.so file found in your data/data/com.adobe.flashplayer/lib folder with the one I've attached as a zip file to this post and you should be good to go.
Also, for the best viewing experience, I've got my streaming settings in Hulu.com to stream at 288p and it streams nicely without any issues and the picture looks great.
Awesome info, wished I would have known about this before but the app itself isn't too bad. This should help others who are looking to do the same thing.
thanks! this is great
Also, just an FYI...
Several television networks have full episodes of popular shows and current episodes on their websites. With my current browser and Flash setup I watch Person of Interest and C.S.I. on CBS.com, the current season of Downton Abbey on PBS.org and Fox.com has a bunch of shows (some are also on Hulu but some are not).
sjmoreno said:
I watch stuff on Hulu.com all the time (about once or twice a day) with the stock browser from CyanogenMod 7.1.0.1 and the latest Flash from the Market (with a modified libflashplayer.so file which tells Hulu it's a Windows PC you're coming from and not an Android device) and changing the UserAgent setting in the browser to tell Hulu.com that you're coming from a desktop web browser (as a lot of their videos are not licensed for mobile viewing).
Just replace the libflashplayer.so file found in your data/data/com.adobe.flashplayer/lib folder with the one I've attached as a zip file to this post and you should be good to go.
Also, for the best viewing experience, I've got my streaming settings in Hulu.com to stream at 288p and it streams nicely without any issues and the picture looks great.
Click to expand...
Click to collapse
i am not finding the right data folder. what is the full path?
gregh77 said:
i am not finding the right data folder. what is the full path?
Click to expand...
Click to collapse
That is the correct file path name and I can confirm that this works.
After I set my user agent to Mac desktop I had to wipe the cache, but wiped the history, cookies just incase before it would recognize that I had flash player and that I wasn't on android device.
gregh77 said:
i am not finding the right data folder. what is the full path?
Click to expand...
Click to collapse
The path I posted before is the correct full path. Perhaps you are using a file explorer that can only see the SD card and not the root of the file structure? I use Root Explorer which can see all of the files/folders but I've heard some people have used ES File Explorer (free) and that it can also see all of the folders and files.
I'm using ES File Explorer and Astro but can't find the path you mentioned on both the eMMC and SD card.
sjmoreno said:
The path I posted before is the correct full path. Perhaps you are using a file explorer that can only see the SD card and not the root of the file structure? I use Root Explorer which can see all of the files/folders but I've heard some people have used ES File Explorer (free) and that it can also see all of the folders and files.
Click to expand...
Click to collapse
i am running off SD card with CM7 if that may be affecting the structure. i can get to the system files like build.prop and things like that.
gregh77 said:
i am running off SD card with CM7 if that may be affecting the structure. i can get to the system files like build.prop and things like that.
Click to expand...
Click to collapse
I can't tell you why you don't see the data folder but here are some screenshots of my directory structure. I've highlighted the folders and file in question on my NC.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The guy that sits next to me at work has his NC running CyanogenMod 7.1 off of his micro SD card and he can see the data folder on his NC as well. The only thing I can say to try is to get to the root folder of whatever file explorer you're using until you can see the data file. If you're at the root level you should see folders like the ones in my first screenshot.
Can you get a screenshot of your file structure and post it? If you don't know it already CM 7 has that feature built in. Just hold down the power button for a second and when the power menu pops up one of the choices is "screenshot".
sjmoreno said:
I can't tell you why you don't see the data folder but here are some screenshots of my directory structure. I've highlighted the folders and file in question on my NC.
The guy that sits next to me at work has his NC running CyanogenMod 7.1 off of his micro SD card and he can see the data folder on his NC as well. The only thing I can say to try is to get to the root folder of whatever file explorer you're using until you can see the data file. If you're at the root level you should see folders like the ones in my first screenshot.
Can you get a screenshot of your file structure and post it? If you don't know it already CM 7 has that feature built in. Just hold down the power button for a second and when the power menu pops up one of the choices is "screenshot".
Click to expand...
Click to collapse
thx for the help your screenshots helped. i didnt drill down pass the data folder. it didnt say to go into the adobe flashplayer folder on the original posting of where to go. i guess it was assumed. thx for the help !
using Ghost Commander (free) from the Market I was able to find the listed path and it worked great. make sure you don't have auto-update enabled with the Flash player else it will over-ride the file. If so just copy it again. Thanks
Update: I have just created a V2. Why, because i plugged back my awox striimstick and found it very slow and outdated. So I created a V2 with a new launcher, and remove a lot of crap and freed up memory.
To sum up, if you need to get close to stock ROM use V1, (there is some draw back and some modification to do to get back the internal SDcard (Modify /etc/vold.fstab and find the line: "dev_mount sdcard /mnt/sdcard auto /devices/virtual/block/nandk" replace nandk or whatever by nandj then do a mkfs.vfat /dev/block/nandj to format, then reboot)
OR, use the V2, access to everything and very fast rom (fast considering the very old CPU and the 512 Mb of ram). This rom V2 is very usable;
Hi all,.
This is an awox striimstick, hdmi stick.
Please see the recovery method below after download link...
Long story short, a fw restore using allwinnera10 tools went wrong and now i have no way to recover it.
I have no power button or volume key, only a reset button on the back (like the mk802)
If i keep pressing this button while pluggin the usb cable to my computer i should be able to go to the bootloader, but it never works... It only reset all my settings.
For restoring the striimstick:
Link for Firmware V1 (file 460mb) and Firmware V2 (file 607 mb) and tools (Livesuite and phoenix carad writer)
Link: https://drive.google.com/drive/folders/0BwJDxBRQ92xcbU5RWkQ2WXV1UFE?usp=sharing
and the instruction:
- Download and use phoenix card writer to write the output.img or outputv2.img to a micro sd (1Gb microsd should be enough)
- plug micro SD card to the stiimstick (do not plug HDMI, just a Usb cable to your computer)
- Power on (You should see a green light blinking close to the red light)
- Wait 1 real minute
- 1- Remove microSD, 2- unplug the usb cable from your computer
- Plug it back into your computer (Make sure your computer's sound is on so you will here windows saying it is detecting new hardware)
- The stick Should now be in bootloader mode, Windows will detect the hardware and will ask for driver, use the driver from live suite folder\Usb driver
- Use livesuite to flash the file output.img or outputv2.img file (If flashing says 0% and do not start after 1 minute, unplug and plug back the stick one more time, do not touch anything on the computer, the flashing should start automatically in the next 30 seconds)
Unplug the stick and plug the HDMI cable to your TV, Plug back power cable, it should be working
Again this is not super easy, if you do it anyway, do it at your own risk
Fyi (On v1), on this image there is the playstore already installed and it is rooted. This is not the official image as nobody has it. I made this image from a nandroid backup i did previously
Fyi (On v2), on this image there is no google services installed but the rom is rooted and has aptoid lite, facebook lite, cleanMaster and ES File explorer already installed out of the box.
Please hit the thanks button if you donwload the file.
Cheers
Note for V2:
Use the same Recovery method using the SDCARD then Livesuite.
After reboot, use ES file explorer, activate "root"option in it THEN to go to /system/app and reinstall android terminal by clicking on jackpal.androidterm-1.apk (Yon can also use adb shell and type "su" and go to next step).
then Open Android term type su, wait for superSu to popup and autorise it. then type: mkfs.vfat /dev/block/nandj (It will format the internal SDCARD not the MicroSD call EXT-SD) then type reboot.
You will now have the internal SD card accessible in /SDCARD. Your MicroSD card is accessible through /mnt/extsd
Also, as this stick have a little amount of ram, I recommand to use the android Widget "CleanMaster (White theme)" already installed from the laucher (This is the widget below my kid's picture on the launcher). Everytime before starting an app I'm cleaning the RAM using this button from the launcher (See the launcher screenshot below)
I removed everything included google services and google market (Was present in V1) because it uses too much ram and CPU. I replaced it with Aptoid lite, replaced chrome by opera mini, and facebook by facebook lite..
Regarding remote control, if you dont like the hardware remote provided by awox, you can download from google play store on your phone the Awox remote app (striimstick Remote) and use it to remote control your android stick (emulating mouse and keyboard).
The stick is also able to receive DLNA request and it is working pretty well (I send DLNA from my galaxy S6 using bubbleUpnP and it is working well with movies and series.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here another screenshot with the application I used and works well with this stick:
pierrottls31 said:
Hi all, i need help with my device.
This is an awox striimstick, hdmi stick.
Long story short, a fw restore using allwinnera10 tools went wrong and now i have no way to recover it.
I have no power button or volume key, only a reset button on the back (like the mk802)
If i keep pressing this button while pluggin the usb cable to my computer i should be able to go to the bootloader, but it never works... It only reset all my settings.
Im suspecting vendor had setup a different way for recovering this device, like using the usb port or the micro sd port. Any idea of a procédure and the type of file i should use?
To sum up whatever i do, nothing is detected by usb so. I cannot use livesuite or other software to reflash the firmware
Any help/pointers will be greatly appreciated
Cheers
Click to expand...
Click to collapse
All I was able to get back the Livesuite USB device, but any firmware Im flashing is failling and the stick will not boot up.
I made a backup using all winnertool but i have only boot.img, bootloader.img, recovery.img and system.img
but livesuite want only one big firmware image. Any idea how I can gather all those files together in order to fully restore the device?
thank you
pierrottls31 said:
All I was able to get back the Livesuite USB device, but any firmware Im flashing is failling and the stick will not boot up.
I made a backup using all winnertool but i have only boot.img, bootloader.img, recovery.img and system.img
but livesuite want only one big firmware image. Any idea how I can gather all those files together in order to fully restore the device?
thank you
Click to expand...
Click to collapse
1st, I had to do all this because Awox will not release original firmware, so if your device is fu..ed then you need to get the firmware to reflash the device. (You cannot even test alternate firmware as if the stick is not booting, you will not be able to put the stick in bootloader mode, there is no USB connection detected)
Finally found a way to restore the original firmware I did backed up the device using Uberizer and a Phoenix card writer.
Use uberizer to unpack any A13 device image 4.0.1 you can donwload and wait untill it finish.
Take the backup you have made using allwinner tools.exe when the device was still working.
copy the 3 img file to uberizer rom input folder, rename your .img file to .fex file, the from uberizer menu "i" use Repack image.
Then take any 2gb min Microsd card, and using Phoenix card writer, write the uberizer output.img on the sdcard.
Turn off your striimstick, plug the MicroSD Card and plug the power cable on the device.
You should see a blinkin green light close to the red light. When it stop blinking, remove sdcard and Unplug, plug back in the power cable. It should be restored.
If you need I can create and send you a recovery image, just send me a private message.
Hope this will help.
Cheers
Hi Guys,
Is there someone kind enough to send me the original firmware please? I'm having issue with a Flickering HDMi, I would like to reinstall original firmware to make sure this is not software related.
Also if I get the original firmware I will be able to cook a better rom (My rom backup is already messed up). I want to try to go for 4.2 rom , in this case, the stick should be faster.
You can use the application Nandroid backup or any other tool you want.
Your help will be greatly appreciated.
Thanks you
I really need some assistance in understand this issue that i'm experiencing on my new XZU phone (not even 2 weeks old!).
I seem to be getting some odd file system issues wherein certain files which are supposed to be in a certain location (OBB folder) suddenly disappear. I've been researching and the general idea is that this is an Android KitKat issue but I posted here on the hopes finding a solution to this problem.
Some pointers regarding on what happened (note: phone is not ROOTED):
1. Installed game like Plants vs Zombies 2 (legit) and the OBB files were correctly placed on the OBB directory.
2. I also purchased Comic Rack full edition which seems to have created a Storage/Emulated directory on the root of my internal drive when creating a comic folder.
-- Initially i made the mistake of deleting this folder which deleted my whole file system (both internal and external sds). I already did a factory reset after this issue, but the obb movement issue as mentioned above still happened.
---- I noticed that some of the Comic files added by Comic rack through wifi syncing are added on the directory in the emulated section i.e (Storage/Emulated/SDCARD/0/Comics/) instead of just Comics/ . However using the android file explorer and the desktop windows explorer shows different files/locations.
------- I'm mentioning the Comic Rack issue because i suspect this might be related to the missing obb due to the folder linking/mirroring system for android (i only read about it so please don't quote me on this)
3. Uninstalling PVZ2 removes the game from the apps list but the files are still accounted for in the storage. Using clean master does not detect these missing files and using other File explorers doesn't show any other directories that may have these files.
4. I read on google that the files might be on Root/Media/SDcard/something but i can't access this directory due to file permission (unrooted)
5. Redownloading the PVZ2 data files, simply puts back the missing files and makes the game work again. However i am not sure until when the issue can or will happen again.
Would anyone be able to explain this issue? or better, if there is a solution? Thanks
How the fudge did you modify the system files and folders in / direction if you are not rooted????
App data are and can be located in these directories
/data/data/
/data/dalvik-cache/
/storage/emulated/android/obb/
/storage/emulated/android/data/
=== if you have an memory card inserted ===
/storage/sdcard1/android/obb/
/storage/sdcard1/android/data/
=== if you have an memory card inserted ===
If you have root permissions. Look in these folders for traces of the app you have issues with and delete any related files. Reboot.
Other common methods is also to reboot in to recovery and clear cache and clear dalvik cache then reboot to system.
But without root permissions or a recovery I don't see many options for you than do than flash a .ftf file which includes the whole stock rom. If that works on locked bootloader...can't remember by now.
SÜPERUSER said:
How the fudge did you modify the system files and folders in / direction if you are not rooted????
App data are and can be located in these directories
/data/data/
/data/dalvik-cache/
/storage/emulated/android/obb/
/storage/emulated/android/data/
=== if you have an memory card inserted ===
/storage/sdcard1/android/obb/
/storage/sdcard1/android/data/
=== if you have an memory card inserted ===
If you have root permissions. Look in these folders for traces of the app you have issues with and delete any related files. Reboot.
Other common methods is also to reboot in to recovery and clear cache and clear dalvik cache then reboot to system.
But without root permissions or a recovery I don't see many options for you than do than flash a .ftf file which includes the whole stock rom. If that works on locked bootloader...can't remember by now.
Click to expand...
Click to collapse
I'm also not sure how those files were modified because i dont have root permission. Comic Rack was somehow able to make the Storage/Emulated folder visible on windows and somehow messed up my file system (just a guess). I already looked at those directories (through windows) and they are empty. Those folders are not visible through android based file explorers on my phone
ckenni2000 said:
I'm also not sure how those files were modified because i dont have root permission. Comic Rack was somehow able to make the Storage/Emulated folder visible on windows and somehow messed up my file system (just a guess). I already looked at those directories (through windows) and they are empty. Those folders are not visible through android based file explorers on my phone
Click to expand...
Click to collapse
You can not look in to these folders with a computer as android nowadays use MTP protocol to communicate with usb. You need to use ADB or a local file manager on your device like https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
To write files in sdcard1 without root permissions you need to mount the sdcard manually in a pc. Android has these functions disabled since not so long ago.
Remove the sdcard from the phone. Insert sdcard in a sdcard reader connected to your computer and open the folder.
If you are only read and write files in /storage/emulated/ you do not need root permissions as this is your personal storage space and you can use an app like this https://play.google.com/store/apps/details?id=com.estrongs.android.pop
Install this app and look in
/storage/emulated/android/obb/
/storage/emulated/android/data/
When you install es file explorer by standard the app starts in /storage/emulated/ directory so you only need to locate a folder called "android"
Screenshot on my device with ES file explorer started
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think i figured out the issue somehow. Just as a reference, if you guys used the Disk Usage APP, does your System Data show more than 4GB? Mine does and i assume these are the files that were previously on my OBB folder that were somehow transferred to the Root or System/Data of the phone that i am unable to access/delete.
Would there be a way to delete these files aside from rooting/factory reset
ckenni2000 said:
I think i figured out the issue somehow. Just as a reference, if you guys used the Disk Usage APP, does your System Data show more than 4GB? Mine does and i assume these are the files that were previously on my OBB folder that were somehow transferred to the Root or System/Data of the phone that i am unable to access/delete.
Would there be a way to delete these files aside from rooting/factory reset
Click to expand...
Click to collapse
I don't know what that app is.
Apps installed in /data/app can not be moved to /system/app without root permissions unless it is a bloat app from either google or the manufacture ie samsung/SONY/LG etc
However app data and cache files can remain if there was an error with uninstallation or some error in the system.
Your only option if you don't have root permissions to access those folders is to do a factory reset or a reinstallation by flashing a stock .ftf rom
Hey there folks,
I've been using adoptable storage on my Moto X pure with great success.
I'm hoping that someone has more experience with adoptable storage than me that can help.
I am currently using a 32 gigabyte SD card and want to swap it with a new 64 gigabyte SD card. Can I just copy the contents from my old 32 gigabyte card to my new 64 gigabyte card and put the new 64 gigabyte card in the phone and expect it to work as before?
Thanks for any insight.
bumpbump
I have the same problem with a S5 (cm13). Used a 32gb card initially. Now bought a 128gb card and I want to upgrade it moving everything from the old card to the new one.
I found no documentation on internet so if no one has a better suggestion I think I'll go for the "raw" way.
I'll turn off phone, take out old card, attach it to a linux box along with the new one and "sudo dd if=/dev/oldcard of=/dev/newcard"
Once data is copied I'll try to insert the "new" card in the phone and see what happens. If the device works normally I'll power it off again, connect to the linux box again and create a new entry in the partition table to use the "remaining" empty space as an external "portable" SD.
I hope this will lead to the same "resulting" configuration when you use the command "sm partition disk:XXX mixed yy"
I wish the best, I ended up needing to update my rom so I just wiped everything and started fresh with the new Microsd. However I'm still curious if your method will work for future reference.
Thanks. If I succeed I'll post a tutorial on how to do that. Maybe someone finds it useful.
It works.
So...How to do that?
turn off phone (wait for it to be really off).
extract microsd.
insert into microsd reader (it's faster if you have TWO microsd readers, usb3. I had just one and times were longer)
boot ubuntu (or any other linux)
copy the image of the old sd card on the disk.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
once done take out the microsd reader from usb port, swap card with the new one and plug it again in usb port.
(optional) verify that your microsd reader works good with the new card.
Good! device contains only one partition (a big exfat one).
ensure that the system DOESN'T mount automatically the card. if it does "eject" (unmount) it.
copy back the data onto the new sdcard.
once done we got to tell the kernel to refresh the partition table.
the error just means the disk is bigger than what the partition table knows. We got to fix that and another problem. GPT has a backup partition table at the end of the disk (which on the new disk isn't "at the end" any more 'cause it's located at the end of the "source" disk)
check the partprobe result on dmesg. we should see that the kernel saw the new partitions and complains about the backup. let's fix it.
(optional) take out the reader from the usb port, put card in the phone, boot up, let it settle, check everything works fine (it should work exactly as before, no extra space yet).
turn off phone again (let it turn off completely), extract sd, put sd in reader, put reader in USB port (i plugged it in another usb port and the device became sdb...but it's just the same card)
let's create the "portable" space with the unused space. I used parted, you can use whatever you like.
and create the filesystem... (I did also a check on the new FS to see it is everything ok)
do not forget to set the partition type you just created as type 0700 (windows).
when you first create the "unformatted" partition entry in the partition table, by default, it gets "Linux filesystem" type. before putting the card back into the phone you gotta change the type to windows or android won't see it.
put card back in the phone...et voilà, the system says "hey, you inserted a new card, what do you want to do?" choose portable to leave the partition AS IS (I don't want to convert the new one to adopted storage too).
when you connect the phone through MTP you will see both the storage spaces
it's worth to note that this "raw copy" method creates problems if you try to read the card on windows 7 or earlier. why?
windows sucks (we all know it) and requires that the "portable" partition is the first in the gpt disk. (it is not, we added it at the end of the disk)
on windows 10 microsoft realized the world isn't all about windows and corrected this bug so you can just plug the sdcard on the port to read/write data.
Clarify please
LinoX said:
So...How to do that?
turn off phone (wait for it to be really off).
extract microsd.
insert into microsd reader (it's faster if you have TWO microsd readers, usb3. I had just one and times were longer)
boot ubuntu (or any other linux)
copy the image of the old sd card on the disk.
once done take out the microsd reader from usb port, swap card with the new one and plug it again in usb port.
(optional) verify that your microsd reader works good with the new card.
Good! device contains only one partition (a big exfat one).
ensure that the system DOESN'T mount automatically the card. if it does "eject" (unmount) it.
copy back the data onto the new sdcard.
once done we got to tell the kernel to refresh the partition table.
the error just means the disk is bigger than what the partition table knows. We got to fix that and another problem. GPT has a backup partition table at the end of the disk (which on the new disk isn't "at the end" any more 'cause it's located at the end of the "source" disk)
check the partprobe result on dmesg. we should see that the kernel saw the new partitions and complains about the backup. let's fix it.
(optional) take out the reader from the usb port, put card in the phone, boot up, let it settle, check everything works fine (it should work exactly as before, no extra space yet).
turn off phone again (let it turn off completely), extract sd, put sd in reader, put reader in USB port (i plugged it in another usb port and the device became sdb...but it's just the same card)
let's create the "portable" space with the unused space. I used parted, you can use whatever you like.
and create the filesystem... (I did also a check on the new FS to see it is everything ok)
do not forget to set the partition type you just created as type 0700 (windows).
when you first create the "unformatted" partition entry in the partition table, by default, it gets "Linux filesystem" type. before putting the card back into the phone you gotta change the type to windows or android won't see it.
put card back in the phone...et voilà, the system says "hey, you inserted a new card, what do you want to do?" choose portable to leave the partition AS IS (I don't want to convert the new one to adopted storage too).
when you connect the phone through MTP you will see both the storage spaces
it's worth to note that this "raw copy" method creates problems if you try to read the card on windows 7 or earlier. why?
windows sucks (we all know it) and requires that the "portable" partition is the first in the gpt disk. (it is not, we added it at the end of the disk)
on windows 10 microsoft realized the world isn't all about windows and corrected this bug so you can just plug the sdcard on the port to read/write data.
Click to expand...
Click to collapse
SO for clarity if we are using the exact same size and brand of storage, just faster, and want everything exactly the same we stop at step 10? Correct? I will use a usb c reader if I want removable storage. The primary thing for me is identical to original.
EDIT I meant step 9.
nooneelsesdroid said:
SO for clarity if we are using the exact same size and brand of storage, just faster, and want everything exactly the same we stop at step 10? Correct? I will use a usb c reader if I want removable storage. The primary thing for me is identical to original.
EDIT I meant step 9.
Click to expand...
Click to collapse
if you don't need the extra space yes, you just "dd" the "disks" (it's like a 1-1 copy of the card)...but nowadays it's kinda pointless and good quality, huge cards are very cheap...
Well shoot I tried it and it yelled at me to put back in the other card. My bad was they are in fact different brands, I think you need to stick with the same brand. I was coming from a Samsung Evo Plus Grade 3, Class 10, A1 and went to a SanDisk Extreme Grade 3, Class 10, A2, v30. I even dd'd the whole thing /dev/sdb. It knew new the brand... bummer.