Related
Hey guys!
I was at a concert last night and took some photos/videos with my ZL. But when I tried to transfer them to my computer, I got some problems. All I did was:
> Connected my ZL to PC via usb in MTP mode
> Created a new folder in my computer
> Opened the desired folder (in this case, Internal Strorage > DCIM > 100ANDRO)
> Then, I simply dragged the 100ANDRO folder to the new one I created
But after doing this, some trouble: the 100ANDRO disappeared from my phone internal storage and appeared EMPTY inside the folder I created before. Result: I've lost all the photos and videos.
I don't even know if I'm posting on the right area, but all I want is to recover the disappeared files. Tried to google a solution. I even found it, but for that I have to root my phone, and I don't want to do this 'cause it's in warranty period yet.
Questions: Can I have my photos/videos back without rooting my phone? If I really have to root it to have my photos/videos back, what I have to do? Do someone knows what happened? PLEASE HELP MEEEE :crying:
@EDIT
Okay, I realized that the only way is rooting my phone. Can anyone explain step-to-step or indicate a thread that a noob can understand?
C6503, KitKat 4.4.2 running on 10.5.A.0.230 with unlocked bootloader
leonardohideki said:
Hey guys!
I was at a concert last night and took some photos/videos with my ZL. But when I tried to transfer them to my computer, I got some problems. All I did was:
> Connected my ZL to PC via usb in MTP mode
> Created a new folder in my computer
> Opened the desired folder (in this case, Internal Strorage > DCIM > 100ANDRO)
> Then, I simply dragged the 100ANDRO folder to the new one I created
But after doing this, some trouble: the 100ANDRO disappeared from my phone internal storage and appeared EMPTY inside the folder I created before. Result: I've lost all the photos and videos.
I don't even know if I'm posting on the right area, but all I want is to recover the disappeared files. Tried to google a solution. I even found it, but for that I have to root my phone, and I don't want to do this 'cause it's in warranty period yet.
Questions: Can I have my photos/videos back without rooting my phone? If I really have to root it to have my photos/videos back, what I have to do? Do someone knows what happened? PLEASE HELP MEEEE :crying:
Click to expand...
Click to collapse
Well maybe you accidentally put it somewhere...
Are you using 4.3 or 4.4?
AndreIrawan97 said:
Well maybe you accidentally put it somewhere...
Are you using 4.3 or 4.4?
Click to expand...
Click to collapse
I'm using 4.4, with 10.5.A.0.230.
you removed device without close usb conection.
It's normal lose data when do this way.
that things were on SD, i think you'll see nomore. Or, use another ZL and copy the original files.
Adilson Casula said:
you removed device without close usb conection.
It's normal lose data when do this way.
that things were on SD, i think you'll see nomore. Or, use another ZL and copy the original files.
Click to expand...
Click to collapse
I didn't remove the device before I realized the trouble I was in. By the way, I've done this process so many times before and never had a problem like this, always safely removing my device.
The photos and videos were on Internal Storage. If them were on the SD card, I think I could recover the files; but since I can't connect my ZL in USB Mass Storage mode, pc applications can't scan it to try to recover the files.
I found some ways to try to recover the files w/ an application named DiskDigger, for Android. But in order to use it, I have to root my device first. Anyone ever used this app? Does it really works? What's the best, safely or simply way to root my device for a noob like me? I'm using a C6503 running 4.4 on 10.5.A.0.230 with unlocked bootloader.
why can't connect in MSC?
Adilson Casula said:
why can't connect in MSC?
Click to expand...
Click to collapse
According to some information I found over the internet, Google disabled Mass Storage mode in newer Android versions.
settings / Xperia conectivity / usb xonectivity / USB connection mode
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
is that you're talking?
Adilson Casula said:
settings / Xperia conectivity / usb xonectivity / USB connection mode
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
is that you're talking?
Click to expand...
Click to collapse
Yep. But the Internal Storage isn't available in Mass Storage mode, only the SD card. Since the photos I want to recover were on the internal storage, it don't works for me.
Can you indicate me the best/easier way to root my phone?
leonardohideki said:
Yep. But the Internal Storage isn't available in Mass Storage mode, only the SD card. Since the photos I want to recover were on the internal storage, it don't works for me.
Can you indicate me the best/easier way to root my phone?
Click to expand...
Click to collapse
try it
http://forum.xda-developers.com/showpost.php?p=52850196&postcount=7
leonardohideki said:
I didn't remove the device before I realized the trouble I was in. By the way, I've done this process so many times before and never had a problem like this, always safely removing my device.
The photos and videos were on Internal Storage. If them were on the SD card, I think I could recover the files; but since I can't connect my ZL in USB Mass Storage mode, pc applications can't scan it to try to recover the files.
I found some ways to try to recover the files w/ an application named DiskDigger, for Android. But in order to use it, I have to root my device first. Anyone ever used this app? Does it really works? What's the best, safely or simply way to root my device for a noob like me? I'm using a C6503 running 4.4 on 10.5.A.0.230 with unlocked bootloader.
Click to expand...
Click to collapse
After a heavy data loss I managed to recover all my photos with DiskDigger.
Works from both, internal and external storage, it is a great app :good:
Adilson Casula said:
try it
http://forum.xda-developers.com/showpost.php?p=52850196&postcount=7
Click to expand...
Click to collapse
I tried to follow the instructions in the link you posted, but I have problems with the second step. It redirects me to this thread, but since I don't have recovery and can't flash the kernel that is disponibilized, I got an error that says that it cant write the boot 'cause remote command is not allowed or something like this. So, I can't flash the kernel with recovery and can't root. Some tips about this?
you must have a unlocked bootloader.
i think your is locked.
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
Adilson Casula said:
you must have a unlocked bootloader.
i think your is locked.
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
Click to expand...
Click to collapse
Ok, so my device allows me to unlock my bootloader... I read in somewhere here in xda that having my bootloader unlocked cause the loss of the Bravia Engine 2. Is it really true? Or it's a risk that may occur?
I have rooted and have disabled most of the recommendations listed here: http://forum.xda-developers.com/galaxy-tab-s/help/debloating-t2805503
I now find myself unable to create a folder (using ES or ASTRO) in any directory?
Very confused
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
UpInTheAir said:
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)? I checked out that thread, downloaded the "SDFix: KitKat Writable MicroSD", rebooted and still does not work. I am attempting the wanam xposed fix but whenever I attempt to use the xposed installer, it can't extract (due too inability to write to disk). Is there a way to install xposed via odin?
Thank you for the response. I am new to rooting and Android in general, but I am trying!
lordnorth4 said:
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)?
Click to expand...
Click to collapse
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Freakstyler said:
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Click to expand...
Click to collapse
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
same issue
lordnorth4 said:
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
Click to expand...
Click to collapse
I have the same exact issue. I can add folders through the Samsung My Files; the ES File explorer gives me 'Sorry, operation failed' also. I have reformatted, and re-rooted, but same issue.
Im no expert mind you, but i had this exact same issue, pretty sure its a kernel issue, specifically i think selinux and its two modes passive and enforce.........first i tried an app on the store thats suppose to change this mode upon reboot, before i realised newly installed apps were now also having issue with internal storage........anyways, long story short, i checked out the lone kernel in the dev thread, paraphrasing, selinux disabled, or some such, and bingo bango, everythings back the way it was
If you have recovery, might be worth backing up and flashing kernel, see if that works, report if it does for the benifit of others that might find themselves with internal storage issues
Edit
T700/T705 version
http://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-skyhigh-tw-kernel-t2806563
"SELinux PERMISSIVE" - turns out kernel is permissive by default, not disabled
T800/T805 version
http://forum.xda-developers.com/gal...ent/kernel-skyhigh-tw-kernel-synapse-t2854933
Hopefully thats usefull
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
UpInTheAir said:
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
Click to expand...
Click to collapse
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
banderos101 said:
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
Click to expand...
Click to collapse
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
UpInTheAir said:
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
Click to expand...
Click to collapse
Thanks by the way, for your kernel, and its rescue of my device .........and not least of all, the work you've done with our devices:highfive:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
Worked fine until i started rooting and flashing the recovery, pretty sure during that process something triggered this issue
UpInTheAir said:
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
Click to expand...
Click to collapse
Yup, first post in the Samsung threads and I messed up. Now I have to find a proper thread to get an answer....
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
banderos101 said:
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
Click to expand...
Click to collapse
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
UpInTheAir said:
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
Click to expand...
Click to collapse
Okay, i could have sworn that i was experiencing the same issue on the external, aswell as the internal, infact im certain, i remember trying the external fixes first, assuming i had the kitkat external storage issue, untill i noticed it was also happening to the internal storage.......this was the first and only thread i found concerning internal issues, maybe i had both issues, but then again, the kitkat fixes didnt fix the external issues, your kernel seemed to fix both, at least in my specific situation
Edit
Okay, i see maybe you were answering my question from a more knowledgeble perpective, it just seemed that whatever affected the internal, was also affecting the external, otherwise, wouldnt the sdfix and/or root file managers like es file explorer with a kitkat/sd workaround, worked, both of which i tried.......seems like whatever was affecting my internal was also affecting external..........one way to find out is if folks who find themselves with the internal issues could confirm if they also have external issues, and whether the external fixes work or not
Edit
Ive just come to realise the fact that i was having internal storage permission issues might have caused the external storage fixes not to function properly, and that maybe i did indeed have two seperate issues, and that whatever was affecting my internal storage was a different issue to the kitkat/external sd card issue, so maybe you are right in saying that this only fixes the internal storage issue, which in turn allowed the external storage fixes to work.........hopefully time will tell, and hopefully, some of that makes sense
Since updating to Kitkat 4.4 I've lost the ability to sync files and folders on my MicroSD card.
There is a work around provided by the dropsync developers where you put your files in the /Android/data/com.ttxapps.dropsync/files folder on your microSD card and you're supposed to be able to sync there. However I don't have the 'com.ttxapps.dropsync/files' folder in my microSD card. In fact there is nothing in there that appears to be associated with dropsync. I even tried uninstalling and reinstalling dropsync to see if those folders would be generated but they were not.
So I tried creating those folders in there myself and dropping my folders and files to be synced in there as well. When I tried to set the sync settings through dropsync it says that those folders cannot be two-way synced.
Does anyone have some advice for me? I really don't want to root because I don't want to void my warranty, but if there is absolutely no other way of resolving this issue that I may end up doing so.
Does anyone think android will change their minds about this and let apps write to the microSD card in a later update?
gina$zanboti said:
Since updating to Kitkat 4.4 I've lost the ability to sync files and folders on my MicroSD card.
There is a work around provided by the dropsync developers where you put your files in the /Android/data/com.ttxapps.dropsync/files folder on your microSD card and you're supposed to be able to sync there. However I don't have the 'com.ttxapps.dropsync/files' folder in my microSD card. In fact there is nothing in there that appears to be associated with dropsync. I even tried uninstalling and reinstalling dropsync to see if those folders would be generated but they were not.
So I tried creating those folders in there myself and dropping my folders and files to be synced in there as well. When I tried to set the sync settings through dropsync it says that those folders cannot be two-way synced.
Does anyone have some advice for me? I really don't want to root because I don't want to void my warranty, but if there is absolutely no other way of resolving this issue that I may end up doing so.
Does anyone think android will change their minds about this and let apps write to the microSD card in a later update?
Click to expand...
Click to collapse
Did you used a system file manager app to create the folder (file manager app build in with the O/S)? you can't create with a third party file manager. Give it a try. If that's not working then you need....ROOT!!!
buhohitr said:
Did you used a system file manager app to create the folder (file manager app build in with the O/S)? you can't create with a third party file manager. Give it a try. If that's not working then you need....ROOT!!!
Click to expand...
Click to collapse
I used the "My Files" app which was already installed on the device. I'm pretty sure it's androids thing.
gina$zanboti said:
I used the "My Files" app which was already installed on the device. I'm pretty sure it's androids thing.
Click to expand...
Click to collapse
yep that's the system file manager. Tell you the truth, if your sync app already installed before you upgrade then you may have a chance, but if you install the app after the 4.4 upgrade then, most likely it's not going to work...just my observation.
buhohitr said:
yep that's the system file manager. Tell you the truth, if your sync app already installed before you upgrade then you may have a chance, but if you install the app after the 4.4 upgrade then, most likely it's not going to work...just my observation.
Click to expand...
Click to collapse
It was installed and set up to sync all my files before the upgrade. It was working perfectly until I updated to Kitkat. Now it's all gone to hell and I'm about ready to root. This irritates me so much.
gina$zanboti said:
It was installed and set up to sync all my files before the upgrade. It was working perfectly until I updated to Kitkat. Now it's all gone to hell and I'm about ready to root. This irritates me so much.
Click to expand...
Click to collapse
BTW, what model of your device?
buhohitr said:
BTW, what model of your device?
Click to expand...
Click to collapse
SM-P600. It's the 16gb wifi.
Would downgrading my firmware void my warranty?
gina$zanboti said:
Would downgrading my firmware void my warranty?
Click to expand...
Click to collapse
With the p600, your warranty will be voided if you try to root and you can't not downgrade.
buhohitr said:
With the p600, your warranty will be voided if you try to root and you can't not downgrade.
Click to expand...
Click to collapse
Ugh... I'm completely updated with the stock firmware (installed the 103mb update earlier today). Will this tutorial still work for it?
gina$zanboti said:
Ugh... I'm completely updated with the stock firmware (installed the 103mb update earlier today). Will this tutorial still work for it?
Click to expand...
Click to collapse
Yes the link is good, but the files are not up to date here is mine;
1) Download this file https://dl.dropboxusercontent.com/u/...ixx-smp600.zip then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here https://goo.im/devs/OpenRecovery/lt03wifiue/
That's all!
Title basically says it all. This should be a simple task but for the life of me I cannot find how to change the default download location to external storage. Honestly it should be as simple as changing storage options but LG in their infinite wisdom decided to make it either convoluted as hell or something that isn't even possible.
Okay, I've tried the download2sd xposed module and it seemed to be fairly simple and straightforward to change where I wanted my downloaded files to go... BUT when I download files that sound like orrents (XD) my file downloader of choice says I cannot locate the file. So obviously download2sd needs a certain path structure that LG doesn't use.
Can anyone shed some light on any possible solution? I've searched the threads and there are people asking about other issues but not this specific issue. Yes I CAN just manually move the files to my sd card after downloading them but that kind of defeats the purpose of not using the internal drive for this process anymore. The fact we can't just change preferred download location to external storage is derp as hell.
The only way I know of is by using the default browser--> Settings--> Advanced--> "Select download storage", and change it to the SD card.
I actually just downloaded a different downloader client and it had the option to change the path built into the app itself. I had to download the SDFix apk to allow me to even save to external storage since google removed that option in Kit Kat. Good to go now. Thanks for trying to help though
thank you
redduc900 said:
The only way I know of is by using the default browser--> Settings--> Advanced--> "Select download storage", and change it to the SD card.
Click to expand...
Click to collapse
Thank you so much. This problem has vexed me since the day I got my LG 8.3, and it was driving me crazy. Your suggestion resolved the situation. Thank you again.
finally!
redduc900 said:
The only way I know of is by using the default browser--> Settings--> Advanced--> "Select download storage", and change it to the SD card.
Click to expand...
Click to collapse
awesome! spent the day trying to figure this out - what a stupid place for it! It's not even an option on Chrome!
Sorted now - thanks
I did that
DomnnallO said:
Thank you so much. This problem has vexed me since the day I got my LG 8.3, and it was driving me crazy. Your suggestion resolved the situation. Thank you again.
Click to expand...
Click to collapse
I did that and it is STILL sending stuff to the "Downloads" folder and there is no way to get it to the SD Drive from there.
I have to send it to the Cloud and I don't want to send it to the cloud. I don't want anything to go there.
I am referring specifically to a PDF I tried to download as an experiment. It was about 12 MG and it reduced the internal storage but not the external storage amount.
It's making me absolutely crazy and I will not be able to do anything else until I figure this out.
works on my LG Stylo thanx for the tip
BreakingVZW said:
I actually just downloaded a different downloader client and it had the option to change the path built into the app itself. I had to download the SDFix apk to allow me to even save to external storage since google removed that option in Kit Kat. Good to go now. Thanks for trying to help though
Click to expand...
Click to collapse
Does this need me to root the phone?
I tried following the steps for the S7 to convert my SD card to internal storage, but when I get to the part where I'm supposed to type in "sm partition disk:179,32 private" it doesn't do anything. It just loads up the shell prompt again. I know the S7 and the Galaxy Tab S are different, but I assumed these steps would be the same. I was apparently wrong, or did something wrong. Anyone tried this and got it to work?
ADB Shell > sm list-disks > sm partition disk:179,32 private
Yes I tried it but no luck
Sent from my SM-T815 using Tapatalk
Porox009 said:
I tried following the steps for the S7 to convert my SD card to internal storage, but when I get to the part where I'm supposed to type in "sm partition disk:179,32 private" it doesn't do anything. It just loads up the shell prompt again. I know the S7 and the Galaxy Tab S are different, but I assumed these steps would be the same. I was apparently wrong, or did something wrong. Anyone tried this and got it to work?
ADB Shell > sm list-disks > sm partition disk:179,32 private
Click to expand...
Click to collapse
Tried with ":" instead ","?
Yeah tried it both ways, no luck
Try with root essential app on play store, there's a specific option to re enable adoptable storage. Try it and report back.
Does not appear to work, does not format external, both internal and external still show as separate, keep wifi on while running or you get advert block notice that freezes the program.
EDIT: It askes you to select external disk, it only shows 1 and size seems wrong far too small, so maybe it formatting the wrong drive?
John
zooster said:
Try with root essential app on play store, there's a specific option to re enable adoptable storage. Try it and report back.
Click to expand...
Click to collapse
I don't have yet MM on tab S so I can't try but something is fishy here, pheraps Samsung completely removed the module.
Hello,
I also tried with ADB with no results. I will try to root mine today night, and give you feedback about Root Essentials.
BR
I just installed the latest SuperSU with TWRP and i am now rooted on MM 6.0 NZ.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
John.
riwaly said:
Hello,
I also tried with ADB with no results. I will try to root mine today night, and give you feedback about Root Essentials.
BR
Click to expand...
Click to collapse
Tinderbox (UK) said:
I just installed the latest SuperSU with TWRP and i am now rooted on MM 6.0 NZ.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
John.
Click to expand...
Click to collapse
Thanks!
Are you sure Root Essentials does not work for you? I have been looking for any other option, and there is not. ADB method has been disabled by Samsung for sure, and I was hopeful Root Essential with Root permission would work.
I have used ADB on the ASOP MM and it looks different, it showed one drive when connected to my notebook, when using RE it showed 2 drives, and i installed it twice, though it has setting, auto, internal, external storage, i left it on auto for where downloaded files go, I downloaded a couple of files and they went to the internal storage, why a choose if the internal and internal are now one, seems fake to me, and it was supposed to format my external 128gb micro sd, and it did not do even that.
John.
riwaly said:
Thanks!
Are you sure Root Essentials does not work for you? I have been looking for any other option, and there is not. ADB method has been disabled by Samsung for sure, and I was hopeful Root Essential with Root permission would work.
Click to expand...
Click to collapse
Tinderbox (UK) said:
I have used ADB on the ASOP MM and it looks different, it showed one drive when connected to my notebook, when using RE it showed 2 drives, and i installed it twice, though it has setting, auto, internal, external storage, i left it on auto for where downloaded files go, I downloaded a couple of files and they went to the internal storage, why a choose if the internal and internal are now one, seems fake to me, and it was supposed to format my external 128gb micro sd, and it did not do even that.
John.
Click to expand...
Click to collapse
Can you send a snapshot of Settings/Storage screen. In the web pages where ADB process was explained, it was told that storage information was not accurate, although adoptable storage was working. In my view, if after enable adoptable storage option in Root Essential, there is any change in Settings/Storage info, it will seem to work. Otherwise not.
I remove RE, cats asleep in front of my keyboard so not easy to type at the moment, we need another member to try RE ADB and see if they think it is working, I think ABE should work like RAID in computers, 2 drives in to 1, seemless.
John.
Tinderbox (UK) said:
I just installed the latest SuperSU with TWRP and i am now rooted on MM 6.0 NZ.
Click to expand...
Click to collapse
So did I. I installed TWRP and Supersu from the links you provided in another topic. My main reason for looking forward to MM on my Tab S is adaptive storage. 16gb of internal storage is ridiculous. I have a S7 Edge I'm but not using adaptive storage on the S7 yet because 34gb at this point suffices. It's nice to know I have that option with the S7 if needed. I just hope the Dev's find a way to enable it on our tablets.
You can use the Vanilla version of 6.0 MM, there is no TouchWiz but it has Adoptable Storage, I installed it myself and it works, but i like TouchWiz
http://forum.xda-developers.com/gal...android-6-marshmallow-tab-s-10-5-lte-t3219759
John.
Eddie Hicks said:
So did I. I installed TWRP and Supersu from the links you provided in another topic. My main reason for looking forward to MM on my Tab S is adaptive storage. 16gb of internal storage is ridiculous. I have a S7 Edge I'm but not using adaptive storage on the S7 yet because 34gb at this point suffices. It's nice to know I have that option with the S7 if needed. I just hope the Dev's find a way to enable it on our tablets.
Click to expand...
Click to collapse
---------- Post added at 05:58 PM ---------- Previous post was at 05:15 PM ----------
I wonder what owners of the Tab S2 are doing, do they have an AS fix, and will it work on the S1
John.
Tinderbox (UK) said:
You can use the Vanilla version of 6.0 MM, there is no TouchWiz but it has Adoptable Storage, I installed it myself and it works, but i like TouchWiz.
Click to expand...
Click to collapse
I could take or leave TouchWiz, either way is OK. I checked into that version. It appears some people are having issues with it. Maybe now that an official T800 firmware is out the Dev can work out any bugs. I'll pass for now. Thanks
If you have a problem with Google Play crashing, a member has posted an alternative OpenGApps later in the thread, and that one works fine.
Also there an an ASOP Vanilla version of Android 7.0 Nougat, but i think it`s a bit buggy, so i have not tried it, though others says it fine.
John.
Eddie Hicks said:
I could take or leave TouchWiz, either way is OK. I checked into that version. It appears some people are having issues with it. Maybe now that an official T800 firmware is out the Dev can work out any bugs. I'll pass for now. Thanks
Click to expand...
Click to collapse
Tab S with official MM Rom with custom recovery and Rooted following given instructions!! Thx!! These are the good news. Bad news are that Root Essential seems to do the same thing as ADB procedure but automatically, so it does not work either. We hope Dev's community will find a solution soon. It seems that Samsung was not interested in giving us easily more internal storage, in order to be potential clients of a new Tablet in a future!!! Samsung, do not count on me for sure!!
It's highly likely Samsung have removed the necessary framework for this to even work due to the S7 hack.
I should imagine all future updates for all devices will be the same including the S7.
Unless someone convinces Samsung to reinstate it or is able to patch the rom with the necessities it's just not going to work any more.
ashyx said:
It's highly likely Samsung have removed the necessary framework for this to even work due to the S7 hack.
I should imagine all future updates for all devices will be the same including the S7.
Unless someone convinces Samsung to reinstate it or is able to patch the rom with the necessities it's just not going to work any more.
Click to expand...
Click to collapse
I know that's not out of the realm of possibilities, but it just doesn't make sense to me. I totally get that Samsung is worried about receiving support calls from people that don't understand what adoptable storage is and that may have turned it on by mistake. Though turning it on via the shell on its own demonstrates that the user knows exactly what they're doing. Nobody is going to stumble into that. So, what would be the value in blocking that? I sincerely hope that someone finds a workaround.