Hi,
I'm using Total Commander and the sftp plugin to download my music directly on the SD Card and then play it with the music player of Total Commander.
Since few days, I can't download anymore on the SD Card. Total Commander give me this error: "Error writing to target file!"
However I can download on the phone and then I've no issue to copy or move the file to the SD Card. It is boring to do the extra step...
This happened after an software update.
I've rooted my s4 and granted root access to Total Commander but I still have the same issue.
After rooting, I've uninstalled and reinstalled Total Commander sftp plugin but I still have the same issue.
I've tried to use Turbo Client that was also able to write on my SD Card before, and now it is throwing me an SftpException error
If I open a txt file from the SD card with gvim, I'm getting an error: "Unable to open swap file" (it tries to create a swap file .swp in the same folder but can't write)
Anybody have the same issue? Any idea why?
As I said, I'm still able to write on the Card from Total Commander but only to copy or move files...
Cheers.
Here is the detail of my phone:
Model number: GT-I9505
Baseband version: I9505XXUFNC4
Kernel: 3.4.0-481100
Build number: KOT49H.I9505XXUFNC4
Hum... after looking a bit more it seems that the issue comes from either KitKat and the version 4.4.2 of Android or just from Samsung and their version.
Can someone clarify this please?
If I install a customed rom, will I be able to use my SD Card properly?
Which rom will you advised? I've never looked at them yet. I've just rooted my phone today hoping it will fix the bug...
Sooo disappointed to have done the update, I'll definitely not let the automatic updates anymore... I don't understand how this can happen...
Now basically I can copy file to my SD but only files. Can't create a folder, can't extract a zip... that sucks!!!
Edit: I can copy a folder from the internal storage to the Sd Card using Samsung "My Files" horrible app.
Better than nothing but still really annoying. If this is a Samsung issue, I'll definitely go for a customed ROM.
ramislebob said:
Hum... after looking a bit more it seems that the issue comes from either KitKat and the version 4.4.2 of Android or just from Samsung and their version.
Can someone clarify this please?
If I install a customed rom, will I be able to use my SD Card properly?
Which rom will you advised? I've never looked at them yet. I've just rooted my phone today hoping it will fix the bug...
Sooo disappointed to have done the update, I'll definitely not let the automatic updates anymore... I don't understand how this can happen...
Now basically I can copy file to my SD but only files. Can't create a folder, can't extract a zip... that sucks!!!
Edit: I can copy a folder from the internal storage to the Sd Card using Samsung "My Files" horrible app.
Better than nothing but still really annoying. If this is a Samsung issue, I'll definitely go for a customed ROM.
Click to expand...
Click to collapse
Aways USE search button. First link....
spamtrash said:
Aways USE search button. First link....
Click to expand...
Click to collapse
Yep, but I wouldn't have imagine it could come from the last version of Android...
using the search engine I've found the soluce I guess: http://forum.xda-developers.com/showthread.php?t=2684188
cool, going to test this now.
sorry for the post... may help other android noobs
ramislebob said:
sorry for the post... may help other android noobs
Click to expand...
Click to collapse
Not a problem, for that this thread exists.:good:
Related
No matter what WMO ROM I am running or no matter what Android platform I try to run Android will not boot a 2nd time. on the Linux bootscreen it says:
"Failed
Failed to find rootfs on SD card. You need to unzip a rootfs/bin/sh: Can't access tty; Job control turned off"
What do I need to do?!?!
Please help me...
shubcraft has a fix for this in his thread, if that doesnt work shift the android files all tothe root of your SD card, I'd reccomend shubcrafts fix first though, hes deff more knowledgable than me.
You moron why would you double post when both topics are on the first page. Mods please close
Sent from my HTC HD2 using XDA App
Read the readme file that came with your build. It will probably say something like extract the android folder to your card. Sounds to me that you took all the files out of the android folder and put them on the root of your card.
Delete the Android/ folder in your SD root (or rename it if that makes you feel better). Will boot again after that. And yes, you will have to do that every time you want to boot Android.
Had the exact same problem yesterday.
this happen to me too then i took it off my sd and put it back on and i got this error message
The file 'CLRCAD' cannot be opened.Either it is not signed with a trusted certificate,or on of its compenents cannon be found.If the problem persists,try reinstalling or restoring this file
and
The file 'haret' cannot be opened.Either it is not signed with a trusted certificate,or on of its compenents cannon be found.If the problem persists,try reinstalling or restoring this file
any one knows how to fix this?
Issues with wanting to copy to extsdcard any new files/folders from my gdrive account...not specific to write or modify but a mix of both.
I am experiencing an issue with my 32gb sdhc card that baffles me. I use ES Explorer and create a folder on the extsdcard and it quickly shows creating the folder in asynch mode, I then refresh and it shows up. Ok odd, whatever, moving on... I then try to delete it and it says successfully deleted, hit refresh and it shows up. How is this?
Another test is use FolderSync and i set up the folder pair and then click sync. Status shows error in red, I click show to see errors and I see errors "could not create folder: <anyfolder> File transfer failed '<file>' open failed: EACCES (Permission denied)"
Anyone have issues like this? Any pointers? I have researched and cant find much other than 4.4 changed its extsdcard security.
Thanks
Robert
Kitkat is picky on third party apps writing files to the card. Call it Googles strive to be more like Apple with each release.
Google probably wants all users to be cloud loving lemmings they can data mine.
http://www.androidpolice.com/2014/0...at-and-even-samsung-may-be-implementing-them/
My main issue is I can't even delete a folder. ..
Sent from my SM-G900V using XDA Premium 4 mobile app
Dunno if it's just me.....I've had zero problems doing ....well....anything I want to ?!?
BTW, I used ES file explorer (file exploder?) on my Galaxy Nexus.....constant issues and crashes.
Never again.
On your S5 there is a app called "My Files", it seems to work almost exactly like ES is supposed to work.
It does everything I can think of....make folders, open and add to them, delete files and folders ???
Works perfectly on mine with a 32gb Pony class 10 micro SD, not a single problem ever.
Perhaps you have a problem SD card ?
<edit>
Err, it's a PNY sd card, just always seemed like calling it a Pony was the correct term ?
As soon as Verizon gets root run the app
SDFix
From the market, or you need to edit platform.xml and add in a permission, only takes a few seconds but you need to be rooted, it is an issue with kit kat
First off, HI ALL. Awesome community!! OK, so I am having the same can't write to SD issue as everyone else. I am rooted with TowelRoot and on KK 4.4.2. I have installed a few of the different "SD FIX" apps and upon looking at the platform.xml file the proper strings are there but I still cant write to or delete from EXT-SD. I have tried ES File Explorer and Root Explorer ( Donate vrs). Another thing that I noticed is that all the tutorials I have read say that there needs to be a space between the " /> at the end. My platform.xml doesnt have that, in fact, none of the strings have the space between the " and />. I tried to do it manually and got the massive force close of a lot of apps. Reverting back to the original didnt help. I had to do a factory reset. That stopped the FC issue but the paltform.xml file is the same with the added string and the nonexistant spaces. Any help would be greatly appreciated. Thanks in advance!!
what filesystem do you have on your card?
Either he has exFAT or FAT32. Can you tell us your exact device model? What ROM are you on?
Thanks for the reply. Model number is N900V and I'm on stock Rom rooted.
Considering that your platform.xml file is still stock, you might want to try this app: https://play.google.com/store/apps/details?id=nextapp.sdfix
This app will automatically detect whether you need the fix or not. If you do need it, it'll do it for you.
Gesendet von meinem SM-N9005 mit Tapatalk
I DL and ran app. Says not needed. Does anyone have the original file so I can start this process over? Or will that bork something? I'm a noob but I am a little tech savy. One anomaly that doesn't make sense to me is that in my xml file, none of the strings have a space between the " and />. Does that make a difference? I'm confused. lol
harmageddon4 said:
I DL and ran app. Says not needed. Does anyone have the original file so I can start this process over? Or will that bork something? I'm a noob but I am a little tech savy. One anomaly that doesn't make sense to me is that in my xml file, none of the strings have a space between the " and />. Does that make a difference? I'm confused. lol
Click to expand...
Click to collapse
Does it make a difference? ...make a backup of your platform.xml. Then put space in between " and >, save and reboot.
Sent from my SM-N9005 using Tapatalk
The whole xml is like that with no spaces. I originally used an SDFix app to do it. Never looked at it. It worked for a brief time then either I rebooted or something and it stopped. I added the space manually but noticed none of the strings had a space. Are they all supposed to have them or just to added/modified string? I did factory reset because I was getting the FC issue but that didn't reset the xml. Does anyone have the original so I can start the process over?
Try this. It already has the fix implemented. If everything else fails, you can still flash a stock rom and use the SD Fix app I posted before.
https://docs.google.com/file/d/0B9Yi7IW9DXQsdVF0aGl0Z3lJbGc/edit?usp=docslist_api
OK. I renamed the file to paltform.xml and renamed mine to bak. Moved it to the folder and did a reboot. So far so good, no FC. Upon using Root Explorer I still get the failed operation toast when trying to delete a file from EXT SD. If noone else has an idea I guess I will just have to flash a rom and try that. I'm going to del and reinstall Root Explorer and see if that does anything. I'll keep you posted. Thanks again for all the help.
OK so I dont know all what was messed up but here is what all I did. I went in to del the Root Explorer app and found that I had converted it to a sys app with TiBu. I undid that process, uninstall and reinstall. That didnt work, so I stuck SD in my puter and backed up files and then stuck card back into phone, robooted into recovery and did a wipe of the SD. Then I put a few test files back onto the card mounted by USB cable) and tried to make folder and del a diff file and it all seemed to work so all is good so far. As I am typing this I tried something else I couldnt do which was instll the XDA app. It kept saying something like it wouldnt write to the ext sd card. Well. I just installed it with no issues. Hooray!!!:laugh: So I dont really know what the issue was but it all seems to be going fine now. A BIG thank you to all that helped me in this. And Nitrous, I clicked the THANKS button on yours!! :good:
Hey everyone,
I'm trying to comply update to my device using the B32 firmware downloaded on ZTE USA Support site. The file is large, too large for FAT32, at 5.39GB.
I have tried copying it using android transfer on my mac, ejecting the microSD and using a regular SD adapter and copying it that way, and I have also tried just downloading right from the Software Update screen. The first two methods errored with (https://ibb.co/kjh4yG).
The software update fails with a message explaining that the firmware found and downloaded by the phone does not match the device...?
I have been on the old firmware for what feels like a year now. I'm hoping you all can shed some light on this.
Thanks
macboss said:
Hey everyone,
I'm trying to comply update to my device using the B32 firmware downloaded on ZTE USA Support site. The file is large, too large for FAT32, at 5.39GB.
I have tried copying it using android transfer on my mac, ejecting the microSD and using a regular SD adapter and copying it that way, and I have also tried just downloading right from the Software Update screen. The first two methods errored with (https://ibb.co/kjh4yG).
The software update fails with a message explaining that the firmware found and downloaded by the phone does not match the device...?
I have been on the old firmware for what feels like a year now. I'm hoping you all can shed some light on this.
Thanks
Click to expand...
Click to collapse
You have two ways to do this:
-If your internet is decent enough just forget about the SD card and download the update on your phone. Afterwards, download 'RAR' from the play store, find the downloaded file (in Downloads), and open the zip file. If you find a PDF and a file called 'update.zip' inside, simply select it and unzip it to the root of your sd card (put '/storage/emulated/0/ on the Destination path). So you will have an 'update.zip' file there. You don't need to unzip this one. Now go to Settings, Updates, then let it scan and it should find the file, update and voila
-Format your SD Card to exfat and pop the file right in
It's weird that the update file is that huge, since usually files for the A2017G are around 2.1 gigs
It worked my friend!!!
I installed RAR, then went inside the downloaded file, found update.zip and unzipped it to '/storage/emulated/0. Did not find any PDF file though, not sure what that would have been for..? Anyway, saw the MiFavor firmware update screen which meant we were on our way to finish line. After that it booted to a small tiny linux penguin symbol and black background. Tried rebooting by holding down the power button. Rebooted. Saw penguin again for like 5 seconds, then booted straight to the axon wavy weird startup sequence. I DID IT!! I really appreciate the help on this one. Great idea. And it worked flawlessly.
Thank you. Choose an username.. Your username might be strange but your solutions are a lifesaver.
Cheers!
macboss said:
It worked my friend!!!
I installed RAR, then went inside the downloaded file, found update.zip and unzipped it to '/storage/emulated/0. Did not find any PDF file though, not sure what that would have been for..? Anyway, saw the MiFavor firmware update screen which meant we were on our way to finish line. After that it booted to a small tiny linux penguin symbol and black background. Tried rebooting by holding down the power button. Rebooted. Saw penguin again for like 5 seconds, then booted straight to the axon wavy weird startup sequence. I DID IT!! I really appreciate the help on this one. Great idea. And it worked flawlessly.
Thank you. Choose an username.. Your username might be strange but your solutions are a lifesaver.
Cheers!
Click to expand...
Click to collapse
Lol. The signup dialog said 'Choose an username...', so i said, why not?
I think you downloaded directly the update.zip. Maybe the RAR part wasn't needed, I dunno. If there's a folder somewhere there called 'update' then just delete it, and the update.zip too
A larger than 5Gb update would have to be the file fully unzipped into a folder structure.
Update files are zipped and that's what the phone wants.
Choose an username... said:
Lol. The signup dialog said 'Choose an username...', so i said, why not?
I think you downloaded directly the update.zip. Maybe the RAR part wasn't needed, I dunno. If there's a folder somewhere there called 'update' then just delete it, and the update.zip too
Click to expand...
Click to collapse
I downloaded one of the two raw zips from the ZTE USA site that had a very long name.zip with all numbers. The "update.zip" was nestled inside after unzipping the file on the phone. I just picked that file and moved it to ther root and applied the update. It went through successfully. Did i not apply it correctly? Should i have just renamed that whole file to "update.zip" and moved the entire folder? A little confused. But i imagine if the update took and i saw the 32 in the current build of the device it took. But im not sure.
macboss said:
I downloaded one of the two raw zips from the ZTE USA site that had a very long name.zip with all numbers. The "update.zip" was nestled inside after unzipping the file on the phone. I just picked that file and moved it to ther root and applied the update. It went through successfully. Did i not apply it correctly? Should i have just renamed that whole file to "update.zip" and moved the entire folder? A little confused. But i imagine if the update took and i saw the 32 in the current build of the device it took. But im not sure.
Click to expand...
Click to collapse
Nah that's okay. I thought you downloaded the 'update.zip' directly. Happens sometimes
It’s weird the update was only about 2 GB. What do you think was the rest of the file?
Maybe in case it needed the full firmware. In this case it didn’t probably. Just a guess
macboss said:
Maybe in case it needed the full firmware. In this case it didn’t probably. Just a guess
Click to expand...
Click to collapse
No, that doesn't make sense. No idea really.
It couldn't have gone wrong so don't stress out. Your phone works. If it didn't work then yeah, something was wrong...
Hi all,
I can't seem to get my obb folder to behave. After installing anything which makes a file inside it, the folder changes to a file inside any file manager including with root access.
In twrp it shows as a normal folder and can be deleted or edited, but once back in android, it reverts to this weird uneditable file...
Any clues? I can't (or rather won't) format internal storage as I don't have a micro SD and currently have lots of files in my root folder which I need in case of emergency (i.e. my twrp backups and some downloaded . zip files).
Any help would be appreciated! It's not an emergency I'm just trying to get a game working. Oh also, if it helps, when I try to download the game after folder has gone weird, play store gets to 99% then fails with error 0 every time.
darkglobe87 said:
Any help would be appreciated! It's not an emergency I'm just trying to get a game working. Oh also, if it helps, when I try to download the game after folder has gone weird, play store gets to 99% then fails with error 0 every time.
Click to expand...
Click to collapse
You simply need to delete the obb folder from TWRP file manager.
If no success, connect your phone to pc and delete ithe folder from there. (or use some force delete software for your platform)
darkglobe87 said:
Hi all,
I can't seem to get my obb folder to behave. After installing anything which makes a file inside it, the folder changes to a file inside any file manager including with root access.
In twrp it shows as a normal folder and can be deleted or edited, but once back in android, it reverts to this weird uneditable file...
Any clues? I can't (or rather won't) format internal storage as I don't have a micro SD and currently have lots of files in my root folder which I need in case of emergency (i.e. my twrp backups and some downloaded . zip files).
Any help would be appreciated! It's not an emergency I'm just trying to get a game working. Oh also, if it helps, when I try to download the game after folder has gone weird, play store gets to 99% then fails with error 0 every time.
Click to expand...
Click to collapse
Hi,
I'm also facing same issue, did you find any solution ?
Please help me too..
Don't know if this means anything but if I go into file manager after a reboot it's fine for a minute or two then goes back to being weird. Can't put my finger on what causes it. I've uninstalled magisk, clean flashed my ROM, only thing left to do is format internal storage but can't do that until I get an SD card for my ROM files and backups to go on.
darkglobe87 said:
Don't know if this means anything but if I go into file manager after a reboot it's fine for a minute or two then goes back to being weird. Can't put my finger on what causes it. I've uninstalled magisk, clean flashed my ROM, only thing left to do is format internal storage but can't do that until I get an SD card for my ROM files and backups to go on.
Click to expand...
Click to collapse
I also had the same issue with pixel experience rom. My Suggestion is to install a nougat based custom rom until someone finds a solution for that.
Prince Jhamat said:
I also had the same issue with pixel experience rom. My Suggestion is to install a nougat based custom rom until someone finds a solution for that.
Click to expand...
Click to collapse
Thanks but that's not really a solution I want when it worked fine on previous builds.
Wow... You'll never guess...the issue is present in nougat ROMs too...
*facepalm*
i also faced the above problem in almost every oreo rom. But in the below rom it is normal.
https://forum.xda-developers.com/g5-plus/development/rom-cosmic-os-v3-1-universe-t3730547. i am using this rom as daily driver.
Hi All,
I deleted obb folder from going into root >> data >> media >> obb
Choose file manager like es file explorer or Aroma file manager.
But this is temporary solution not permanent after some time same issue will occur again.
Kindly follow this thread to solve obb data lost on Oreo custom Rom.
https://forum.xda-developers.com/g5-plus/how-to/guide-how-to-solve-obb-data-lost-t3744711
Thank you so much!! I don't have an SD card at the moment, however, but happy to know a solution. Does anyone know the cause??
Is there a solution for this without SD card??
EDIT: I've noticed something. The issue described in this thread seems only to happen after connecting to WiFi and downloading apps from the play store. It doesn't seem to happen before I will do that. Hope it helps.
darkglobe87 said:
Is there a solution for this without SD card??
EDIT: I've noticed something. The issue described in this thread seems only to happen after connecting to WiFi and downloading apps from the play store. It doesn't seem to happen before I will do that. Hope it helps.
Click to expand...
Click to collapse
Did u find any solution ?
My theory says obb folder turns into file cause system link from data/media/obb should be revoked but I'm not smart enough to know how to create system links
I noticed that when I install the pubg mobile game manually I do not lose the obb folder, just like the friend mentioned above only occurs when the game is installed directly from the play store
For those who don't have rooted devices use this method until we get a fix