Well as I'm sure most of you know we released CM7 alpha for the NT on Sunday and it was very warmly received, even after a major bug was found it was still downloaded almost 2000 times by the time I eventually removed the files form download server yesterday (links were removed form thread at about 1200 downloads lol). The feedback is still extremely encouraging and people are itching for the next release.
We’ve been working hard on fixing everything so that the next version we release has a lot less bugs, we’ve fixed the main bug of formatting the xloader and we've fixed a handful over other things causing issue too.
The issues we are having now which we are struggling with are usb sync for media as well as sdcard to a computer (in another thread) and a more important one of market not being able to install larger games / programs if there is an sdcard in. For instance one that I use for testing is Zombie bash, if you have an sdcard in it just won't install.. We've looked up the error online and all the errors point towards deleting a certain file but the problem is that we don't actually have that file so it would appear we have a different issue!
So the time has come for Goncezilla and I to reach out and ask for help, somebody out there probably knows or can debug and find out what the issue is. We're stumped and we don't want to release the next version until that’s fixed!
So please, if anybody can help, drop me a Pm or say something on here and lets get CM7 next alpha version sorted and released !
Is there any way to get an error log of this issue? I am using an app called LogThis and nothing is shown in Logcat.
Probably totally unrelated but on the stock ROM I grabbed a couple of Amazon Freebies the weighed in over 50Meg's each. I wasn't even really interested in them so I carried on about my business and a couple of days later noticed that they never installed. After digging around the "error" was that I DIDN'T have an SD card installed. This struck me as weird because the 1GB user and 12GB B&N partitions should have certainly been enough.
Either way once I popped in an SD card the downloads automatically started and off I went.
Like I said .... probably useless information but I figured I would throw it out there.
arclite00 said:
Is there any way to get an error log of this issue? I am using an app called LogThis and nothing is shown in Logcat.
Click to expand...
Click to collapse
Good point, HERE is the logcat.
Mainly it would appear the errors showing are
E/Vold ( 1168): Error opening devmapper (No such file or directory)
E/Vold ( 1168): ASEC device mapping failed (No such file or directory)
and then a few lines on
E/PackageHelper( 2146): Failed to create secure container smdl2tmp1
E/DefContainer( 2146): Failed to create container smdl2tmp1
any help to anybody ?
I'm not too versed in the world of Android development, however this might be useful. LINK 1 LINK 2
Perhaps the permissions to the folders referenced in these articles are incorrect...
scsione889 said:
I'm not too versed in the world of Android development, however this might be useful. LINK 1 LINK 2
Perhaps the permissions to the folders referenced in these articles are incorrect...
Click to expand...
Click to collapse
Thanks for trying, that's one of the articles we found but unfortunately we couldn’t get anywhere with it
From the log it appears as though it is unable to create the smdl2tmp1 temp file. So wouldn't it make sense that it would either be permissions of the folder it's going in, or an issue with whatever is trying to create that temp file?
Have we tried not pre-packaging gapps with the ROM to see if that helps?
Quick question, is there a specific file size where the install fails\hangs? Ex installs are okay up to 9 meg files, but anything over, and it fails?
I want to try and download something and replicate the issue.
Disregard...
I had no problem installing Google Earth and other large apps (over 8MB) today, but cannot install Zombie Dash (only 4 and some change) moments ago. Not sure what relavence the size of the app might be having with the install issue...
Sent from my BNTV250 using xda premium
I found that the "/mnt/sdcard/.android_secure" folder has 000 permissions. The other folder mentioned in the links I posted (/mnt/secure/asec) has 075 permissions.
I compared this to my phone with fully functional market and found "/mnt/sdcard/.android_secure" has 000 permissions. The asec folder has 175 permissions. Perhaps the execute permissions is the problem? I am unable to change permissions in root explorer to test. I get the "some file systems (e.g. SD card) do not allow permission changes" message.
You considered posting on the Android development section? They may have some more info or guidance with this.
Sent from my Nexus S using Tapatalk
I'm not thinking it's permissions I think we've messed up and something isn't tuned on in kernel like driver mapper or asec.
Just been unable to find it. Although I'm speaking to somebody now and I think he may have hit on the cure
Okay...
"Size of container 7 MB 5392635 bytes"
I am assuming based on that, that the app is 7 meg?
D/Vold ( 1168): DEVPATH='/devices/virtual/block/loop0'
D/Vold ( 1168): DEVTYPE='disk'
D/Vold ( 1168): MAJOR='7'
D/Vold ( 1168): MINOR='0'
E/PackageHelper( 2146): Failed to create secure container smdl2tmp1
Okay, sp if you eject the SD card, the download works and installs. So that means when you go to download the app, it creates a temp file (same as when you download a file in windows via your web browser), and then once the download completes, the temp file is removed and you have an apk which is automagically installed via android app handler or whatever. IF the SD card is inserted, it tries to create the file on the SD card instead of internal memory. So the issues lies with the SD card itself possibly(?). Have you tried running checkdisk or some disk checking tool on your card? I have had issues in the past where my sd card got corrupted (once after running the partitioning tool in cwm) and I couldn't install large market apps. I ran checkdisk and found errors (i cant remember the exact msgs), but I repartitioned the card and all was well. It is possible with all the partitioning etc you have done to your cards, they have gotten a bit screwy, have you tried swapping out the SD card for a different one?
I just installed gun bros which is a 12meg app, with my sd inserted and mounted, with no issues...I tried to view it in logcat as soon as I hit download, but I didn't see anything pertaining to the market download and install =(
I already re-partitioned my card and went out and bought a new card to try. It's not that.
CWS - Glad to hear you're making some potential progress.
Well, I've done my best to collect info on the error, so based on what others have found, this seems to be what I've learned so far, including the obvious.
-The error we're seeing is "Couldn't install on USB storage or SD card."
-This error seems to have been most often encountered by people using Android 2.2 (Froyo) and derivatives because that version was related to reading a temporary file called "smdl2tmp1.asec." The user workaround in 2.2 was to browse your SD card using ES File Explorer (so that you can see .folders, which are normally hidden), finding the file in either:
/sdcard/.android_secure/smdl2tmp1.asec
OR:
/mnt/secure/asec/smdl2tmp1.asec
and deleting it.
-This apparently has been fixed in 2.3 (Gingerbread). Because Cyanogenmod 7 uses 2.3.4 as a base, it's odd that we're still having this problem then.
So in my exploration of this stuff, here's what I found:
/sdcard/.android_secure has ZERO FILES in it. Ditto for /mnt/secure/asec. On my HTC Hero, both contain plenty of files with .asec extensions. I have no idea what these files are for, but I'm getting the impression that the reason why these .asec files are not appearing has to do with how the current ROM is treating the SD card.
Also, the error doesn't seem to have anything to do with install size. I've tried to install Minecraft Pocket Edition before, it's only 1.57 MB but it will get the error regardless.
Keep in mind that I'm not a programmer, but this is all I've been able to gather.
---------- Post added at 05:52 AM ---------- Previous post was at 05:49 AM ----------
[/COLOR]
Mike_IronFist said:
Well, I've done my best to collect info on the error, so based on what others have found, this seems to be what we know so far, including the obvious:
-The error we're seeing is "Couldn't install on USB storage or SD card."
-This error seems to have been most often encountered by people using Android 2.2 (Froyo) and derivatives because that version was related to reading a temporary file called "smdl2tmp1.asec." The user workaround in 2.2 was to browse your SD card using ES File Explorer (so that you can see .folders, which are normally hidden), finding the file in either:
/sdcard/.android_secure/smdl2tmp1.asec
OR:
/mnt/secure/asec/smdl2tmp1.asec
and deleting it.
-This apparently has been fixed in 2.3 (Gingerbread). Because Cyanogenmod 7 uses 2.3.4 as a base, it's odd that we're still having this problem then.
So in my exploration of this stuff, here's what I found:
/sdcard/.android_secure has ZERO FILES in it. Ditto for /mnt/secure/asec. On my HTC Hero, both contain plenty of files with .asec extensions. I have no idea what these files are for, but I'm getting the impression that the reason why these .asec files are not appearing has to do with how the current ROM is treating the SD card.
Also, the error doesn't seem to have anything to do with install size. I've tried to install Minecraft Pocket Edition before, it's only 1.57 MB but it will get the error regardless. Of course, ejecting my SD card or unmounting it temporarily allows me to install the app, but that doesn't fix the bug, does it?
Click to expand...
Click to collapse
You think some apps check for those .asec files, and since they don't find them, it fails some kind of authentication and bombs out the installation?
Actually, I just checked my shift, and those folders are all blank as well. Hopefully whomever Celtic is talking to knows what's up.
stealthfx said:
You think some apps check for those .asec files, and since they don't find them, it fails some kind of authentication and bombs out the installation?
Click to expand...
Click to collapse
Yeah, essentially like that. Further down that rabbit hole is what Celtic mentioned:
CelticWebSolutions said:
I think we've messed up and something isn't tuned on in kernel like driver mapper or asec.
Click to expand...
Click to collapse
Apps don't seem to be creating .asec files anywhere, and it seems like some apps need .asec files to validate certain information. It seems to have less to do with the size of the app and more with whether or not the app needs to check an .asec file to install or function.
Mike_IronFist said:
Yeah, essentially like that. Further down that rabbit hole is what Celtic mentioned:
Apps don't seem to be creating .asec files anywhere, and it seems like some apps need .asec files to validate certain information. It seems to have less to do with the size of the app and more with whether or not the app needs to check an .asec file to install or function.
Click to expand...
Click to collapse
/dev/block/vold/179:17 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
sould be
/dev/block/vold/179:10 (< Check on that) /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
also im looking into the fact that /device/virtual/block/loop0 does not exist.
stealthfx said:
Quick question, is there a specific file size where the install fails\hangs? Ex installs are okay up to 9 meg files, but anything over, and it fails?
I want to try and download something and replicate the issue.
Click to expand...
Click to collapse
I think the filesize problem is a red herring. It looks to be apps that have "'android:installLocation="preferExternal" in their apk manifest file.
Obviously this is probably used on larger apps more often so it looks like it is tied to the filesize. I have some small apps that give the same error.
Checkout http ://developer.android.com/guide/appendix/install-location.html for more info.
This doesn't necessarily help with the original problem but it might help limit the scope of troubleshooting.
Related
"Originally Posted by msierra519
i get an error too..i didnt catch the message tho..but it said aborted"
"You guys can unzip the file and push it to the system/etc folder until I have time to look at the zip"
I've had my g-Tab all of a week. I got it through Circuit City. The "application crashes" I learned are called "Force Close." Through the forum I found the solutions. I'd learned I needed the updated ROM and wanted Honeycomb. So this ROM seemed the best. I like the ROM as I've used it most of the day. I agree with the comment about soft keys because in the dark it's hard to see the keys on the bezel. The bugs I encounter are frustrating but, I've found solutions here in the forum. I'm new to Android on so many levels. This is my first Android device. So now I'm stuck.
All I wanted to do was transfer the files I have on my HTC Touchpro to my Tab. (For the 3rd Time.)(I've been through Stock ROM's and Mods several times over.) In reading I know I can't set an Adhoc WiFi tether. I also know I need the right App to transfer a file from the PC to the Tab via bluetooth or something.
So now I tried the USB file transfer. Of course it went into Debug mode. I tried some of the solutions for getting transfer mode operating but, that wasn't successful. I figured the SDCardFix solves this problem. So Tjohnsonjr says to push the file into the system/etc. folder. How would this be done?
You mean copy onto an SDcard Ext from the PC and then mount onto the gTab?
For some reason I can't even get my card to be read by the PC (I formatted it using the G-Tab command. Now when I put in my PC the explore window hangs.)
Use a bluetooth transfer? All I get is my Tab trying to use my PC as a headset. I can push a file from the Tab to the PC but, I' haven't figured the reverse.
BTW I thought I might have "bricked" the tab twice. I used CWMod to wipe cache, data, system and set the new partition. Since all of the files were on the internal SDcard the partition wiped the update.zip and command files. The reboot eventually started functioning and it pulled up "something...dirty....3388"
So obviously somewhere in the system there is still an OM android system ROM. (I think I'd like to hang onto that.)
BTW: the error reads:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/update.zip
(Status 0)
Installation aborted.
Well I hope tjohnsonjr gets this. He's put a lot of work into this ROM. But since the xda-developers won't let me post into the Developer's forum he probably won't. (Too much of a noob).
PS I know some have critiqued the gTab because of it's size. Well for a man who can't see too well that's great. The biggest problem I have with my HTC Touchpro right now is the screen is too small to read the fine print without reading glasses. If I ever figure out how to get the wifi tether working between these two devices. I'd have the perfect solution to several of my problems.
UPdate.zip=SDcardFix.zip
I changed the file name to see if that would make a difference. I was desperate.
try going back to stock rom and then installing. I had a similar problem, and I used nvFlash to go back to stock, then reinstall cwm and repartitioned, cleared data/cache etc.
Installed after doing all that and it worked like a charm.
[Q] [ROM-AOSP]G-Harmony Gingerbread 2.3.3 with Honeycomb elements(UPDATED 4/17)
TJ posted an update to his ROM. The fix to the USB works by renaming the EMMC to the external SDcard per the posts seen on this website. So if you backed up apps and data to the ext SDcard it is now listed under the emmc directory. The SDcard is the internal memory. Not sure how that's going to work when pushing apps and data to the external card. (See forum posts discussing this workaround for the situation for all ROM's.) The USB connection now works for transferring files onto the GTab. Use a file manager for pushing from internal memory to the external SDCard.
The Adhoc Wifi connection seems to work. Meaning I got my cellphone and gTab to connect to one another however, I was unable to get the gTab to connect to the internet via the cellphone. (I'm using an HTC Touchpro on Sprint. I've never gotten the wifi hotspot to function properly but, I'm experimenting with WMWIFIRouter.)
Thanks to TJ for all of the hardwork on this ROM.
I've got the Telstra RHOD110 and I've tried to install every Android build since about the first stable Froyo release. Every single one of them hangs during the Linux boot sequence.
It seems to be memory related, but past that I've got no clue - I'm an IT professional, but I'm in operations, not development so I'm a little out of my depth with this stuff.
I have NOT done HardSPL yet, but I was under the impression this wasn't necessary for the SD card method (which I wanted to test out before potentially bricking a ~$1000 phone). In theory it's just the standard Telstra WinMo 6.5 ROM...
It's getting a bit frustrating after years of trying this and seeing everyone else talking about how easy it is. I'm using F22's rootfs and TotalCommander isn't showing up any *.csv files in the \windows directory, so I can't even try the GBX0C (2.3.7) test build. Anyone know why my phone seems to be different?
Hi Nukkels lets focus on getting GBX0C running since
Nukkels said:
I have NOT done HardSPL yet,
Click to expand...
Click to collapse
First things first: Format the MicroSD you plan to use using the HP USB Disk Storage Format Tool. Just use google to find it. I use version 2.1.8. Perform a FULL format, FAT32.
Now download the package from here: http://files.xdandroid.com/GBX0C_Full_Bundle_2012.04.24.zip and extract all of the files to the root of your SD card
Nukkels said:
I've got the Telstra RHOD110
Click to expand...
Click to collapse
This device is identical to the RHOD100_UK so pull the startup.txt out of the STARTUPS\RHOD\RHOD100\ and place it on the root of your storage card.
Nukkels said:
I'm using F22's rootfs
Click to expand...
Click to collapse
I think I understand why you are trying to use that rootfs since it has some stuff tailor made for Rhod110/Telstra but I don't think it is necessary. Just leave the existing rootfs.img from the GBX0C package, it should work for you.
Nukkels said:
TotalCommander isn't showing up any *.csv files in the \windows directory
Click to expand...
Click to collapse
I haven't used TotalCommander for a while, but it seems to me that there is an option like "Hide Files in ROM" or "Show Hidden Files" or something like that which is probably preventing you from seeing the .csv's in /Windows/. So find that option and find those files and copy them to the root of your storage card.
If you can't find them I think that GBX0C should still boot as I have booted without any .csv's, there was just no sound in the build. But at least you can see that it is working. In case you absolutely cannot find them, here are my .csv's from rhod100uk: View attachment RHOD100_CSV.zip, unzip to your storage card, which hopefully will get you going.
Okay, now all you need is a touch screen calibration file. If you do not have one here is mine:View attachment ts-calibration.zip
Unzip it to the storage card.
Now you have everything in place on the card, please at this point do not try to edit the startup.txt or anything in /conf/. Lets just get this baby working.
Before you run anything I would set WM to airplane mode, set your backlight control to any level but auto (ie low), and make sure that you are not overclocking your processor in WM.
Now run HaRET.exe from the root of the storage card and cross your fingers mate!
Be patient, first boot can take ~10 minutes sometimes.
EDIT: Also there is a fairly good chance that your thread will get moved to the Android section... if it does and you aren't able to post in it anymore you can PM me.
I just wrote up a huge post and lost it all :crying:
Basically I followed your sintructions step by step and it worked!
I'd never done a FULL format before - that takes hours! I'm guessing this might have been the main issue.
I'll play around over the next few days with F22s rootfs and rhod110 startup parameter, Airplane mode turned on, etc to see if any of that had an impact. I never thought to set backlight to manual or use Airplane mode.
Hopefully I can help find the crucial step I missed, so it can be included in the installation instructions (or at the very least someone might stumble on this thread).
Anyway thanks a tonne for your help, it got me up and running!:good:
Thread moved to the appropriate section.
I genuinely hope you didn't pay ~$1000 for this phone... wow.
Caldair said:
Hi Nukkels lets focus on getting GBX0C running since
First things first: Format the MicroSD you plan to use using the HP USB Disk Storage Format Tool. Just use google to find it. I use version 2.1.8. Perform a FULL format, FAT32.
Now download the package from here: http://files.xdandroid.com/GBX0C_Full_Bundle_2012.04.24.zip and extract all of the files to the root of your SD card
This device is identical to the RHOD100_UK so pull the startup.txt out of the STARTUPS\RHOD\RHOD100\ and place it on the root of your storage card.
I think I understand why you are trying to use that rootfs since it has some stuff tailor made for Rhod110/Telstra but I don't think it is necessary. Just leave the existing rootfs.img from the GBX0C package, it should work for you.
I haven't used TotalCommander for a while, but it seems to me that there is an option like "Hide Files in ROM" or "Show Hidden Files" or something like that which is probably preventing you from seeing the .csv's in /Windows/. So find that option and find those files and copy them to the root of your storage card.
If you can't find them I think that GBX0C should still boot as I have booted without any .csv's, there was just no sound in the build. But at least you can see that it is working. In case you absolutely cannot find them, here are my .csv's from rhod100uk: View attachment 1184798, unzip to your storage card, which hopefully will get you going.
Okay, now all you need is a touch screen calibration file. If you do not have one here is mine:View attachment 1184808
Unzip it to the storage card.
Now you have everything in place on the card, please at this point do not try to edit the startup.txt or anything in /conf/. Lets just get this baby working.
Before you run anything I would set WM to airplane mode, set your backlight control to any level but auto (ie low), and make sure that you are not overclocking your processor in WM.
Now run HaRET.exe from the root of the storage card and cross your fingers mate!
Be patient, first boot can take ~10 minutes sometimes.
EDIT: Also there is a fairly good chance that your thread will get moved to the Android section... if it does and you aren't able to post in it anymore you can PM me.
Click to expand...
Click to collapse
I tired this on my TILT 2 it wouldnt work...
tru209 said:
I tired this on my TILT 2 it wouldnt work...
Click to expand...
Click to collapse
So... what's broken with it? Where does it stop?
Edit - basically, you've gotta give us more to go on. We can't help you with "wouldn't work" - it's simply not enough info. Provide as much as you can - what did you try, what happens when it boots, did anything semi-work, etc etc. Details!
tru209 said:
I tired this on my TILT 2 it wouldnt work...
Click to expand...
Click to collapse
Did you bite your tounge just right while dancing backwards to the wizard of OZ soundtrack? That always does it for me when it 'wouldnt work'.
My experience was that the full format using the HP tool is a crucial step. I did a full format using other tools but I had no joy until I did it with the HP tool.
Hello,
Earlier today I got an OTA upgrade of my Samsung Galaxy S4 to Jellybean 4.3.
Everything is working great except for some reason my external SD card (A 64 GB SanDisk MicroSD) is read only. The only thing I can do with it is to format it. Otherwise all write operations to it fail.
I have tried two different cards and several different apps (Terminal, Astro File Manager for instance) and none of them can write to the device.
Is anybody else experiencing this issue or does anybody have any tip for how to solve it?
I am almost thinking it is a matter of a missing new permission but I can't find anything in the SDK docs about it (If this is the case that is fine because my main use of the card is a home made music player that I've written).
I have the same issue after updating to 4.3 yesterday - external SD card is mounted as Read Only after the update.
I have not seen it mentioned before, but It is quite possible that it is just part of the new "Google Experience" - Google has for a long time advocated having a single SD card and several of the tablet devices already had their external SD card mounted as read only in the past.
You can still write to it using MTP from a PC, but it is mounted as ReadOnly for the accounts that Android apps run on the device.
Of course it is possible that it is just a strange side effect (bug) in the upgrade process that is affecting only some devices.
pirin said:
I have the same issue after updating to 4.3 yesterday - external SD card is mounted as Read Only after the update.
I have not seen it mentioned before, but It is quite possible that it is just part of the new "Google Experience" - Google has for a long time advocated having a single SD card and several of the tablet devices already had their external SD card mounted as read only in the past.
You can still write to it using MTP from a PC, but it is mounted as ReadOnly for the accounts that Android apps run on the device.
Of course it is possible that it is just a strange side effect (bug) in the upgrade process that is affecting only some devices.
Click to expand...
Click to collapse
Well, in some way I'm comforted that I am not going insane here.
I will be calling customer support but in a perfect storm for some reason yesterday my Google Wallet account was "suspended pending validation" and it supposedly takes 2-3 days for Google to verify it and you can't get to the support number for Nexus and Google Experience devices without access to your wallet account .
If I learn something I will be letting you know.
same thing happened to me when I updated my s4 to 4.3 made the external SD card into read only cannot modify it using android only if I connect it with my PC. I called Google today they told me that they have not heard of this issue before but they forward the info to there technical people and they will respond back eventually for an email and hopefully a fix. but I am glad to see I am not the only one dealing with this. hopefully Google will get this issue fixed.
ES File Explorer works, so its not impossible for other apps to get updated to work.
I've been looking into this, trying to work around the issue in my own apps. Regrettably don't have a GS4 GPE, but working with users and searching have so far discovered the following:
The underlying problem is that in Android 4.3 (at least on the GS4 G.P. Edition), an application's UNIX user id needs to be part of the group "media_rw" in order to write to the removable "external" SD card.
The "WRITE_EXTERNAL_STORAGE" permission that almost every app out there uses is inadequate. That will get your app uid added to the group "sdcard_rw", which in the case of Android 4.3+GS4 G.P.E. is only good enough to write to the built-in storage.
The "WRITE_MEDIA_STORAGE" permission is required in order to have your app uid added to the group "media_rw". The problem is that this is a system protected permission. You can put this permission in your manifest, but you won't actually be granted it unless you're a system app. (Even tested this modification to FX File Explorer to make sure, and it still fails).
There does appear to be one solution available if you have root: modify the /system/etc/permissions/platform.xml file and grant the WRITE_EXTERNAL_STORAGE permission access to the group "media_rw". Source of this is here: http://forums.androidcentral.com/samsung-galaxy-s4-google-edition/303764-4-3-sd-write-access.html I have not personally tried this.
Issues with external SD
tliebeck said:
There does appear to be one solution available if you have root: modify the /system/etc/permissions/platform.xml file and grant the WRITE_EXTERNAL_STORAGE permission access to the group "media_rw". Source of this is here: http://forums.androidcentral.com/samsung-galaxy-s4-google-edition/303764-4-3-sd-write-access.html I have not personally tried this.
Click to expand...
Click to collapse
Hi!
I have the very same problem: some apps can access the external SD, some others do not.
I tried mount/unmount and root access in ES Explorer... but no way.
The freshly downloaded "Root Explorer" does have WRITE access to the ExtSD, but TBackup doesn't...
I am running Jamal 4.3 AOSP Rom on a EU i9505.
Any help is welcome!
Help! Got the same problem here
64gb samsung micro sd card. Always write protected and no other way to re-format it.
ivanslh said:
Help! Got the same problem here
64gb samsung micro sd card. Always write protected and no other way to re-format it.
Click to expand...
Click to collapse
This solution here helped me: http://forum.xda-developers.com/showpost.php?p=48702336&postcount=13
"I was having the very same problem. I finally went into the computer management, and was about to throw phone across room....when I tried to format one last time. This time I unchecked the quick format. It is taking longer, but seems to be working...I am keeping fingers crossed.
Full Format has finished and card is saved! Hope this helps anyone in the future."
tliebeck said:
There does appear to be one solution available if you have root: modify the /system/etc/permissions/platform.xml file and grant the WRITE_EXTERNAL_STORAGE permission access to the group "media_rw". Source of this is here: http://forums.androidcentral.com/samsung-galaxy-s4-google-edition/303764-4-3-sd-write-access.html I have not personally tried this.
Click to expand...
Click to collapse
I know this is almost 1 year old but... I was struggling with this issue for some days until I tried this and: :laugh:This is the solution!
Hi
"Invalid download uri" is a bad ass error that is the biggest flaw (IMHO) You can encounter. Solutions are (as far as I can tell):
- cache clear
- factory reset
But for those, who did this and still have the same problem (or don't wanna try the factory reset) there might be some hope. (I was searching for solutions and found none like this, so I hope I don't duplicate someone's ideas)
I was fighting with this for a longer time and I guess I finally managed to fix it. I tried to clear cache, Google Store and Services, I even removed and reinstalled Google Play. But as logcat said, there was still problem with access to the file that was downloaded (something about JaveException:FileAccessInvalid - or something similar).
So, to make the long story short:
- connect phone
- adb shell
- cd /data/data/com.android.providers.downloads
- ls -al
There should be 4 directories:
- one of them (install) is a link (not visible in CM File Manager, but visible in shell)
- app_sslcache, cache, databases
Those three should have similar attributes (drwxrwx--x), in my case, cache had ony drwx--x--x.
So an easy fix: chmod 771 cache (You should be root) and voila, everything works (You don't need reboot or to stop google play or anything) and no more "invalid download uri".
Please, if You have this problem try this fix and if it works for You, let others know (maybe even in the comment section below)...
PS: It's not dangerous, but anyway... You do this at Your own risk.
It WORKED!
What a life saver, I was able to change the permissions through FX Root Explorer.
Thank YOU.
Thanks!!!
Old thread but throwing a thank you out there. Was having this issue after rooting my VZW M8 and this solved the problem. Thanks! I also shared this link over on AndroidForums.com as I found a similar thread with no solution while googling this issue.
So thanks!
Thank you, for the inspiration, by looking at the logs, it was some permission pbl in com.android.vending and after some try, it was com.android.vending itself that was with bad permission.
771 on com.android.vending fix it for me!
Hi, was reading your suggestion how to fix problem"invalid dowload url' problem, followed your guide but no luck.
You wrote:
There should be 4 directories:
- one of them (install) is a link (not visible in CM File Manager, but visible in shell)
- app_sslcache, cache, databases
I have galaxy S5, rooted, using root explorer(everything visible) and within data/data/androidproviders.downloads I have only 3 files.
cache,databeses and lib.
but in another directory data/data/com.android.vending I do have files you mentioned and some more.
All of my files as well directories have same set of permissions, which is
rwxrwx-x
I know you mentioned we should have drwxrwx--x and I don't know how to change it(if my permissions are wrong).
IF you can help pls I would appreciate.
sweetmango said:
Hi, was reading your suggestion how to fix problem"invalid dowload url' problem, followed your guide but no luck.
You wrote:
There should be 4 directories:
- one of them (install) is a link (not visible in CM File Manager, but visible in shell)
- app_sslcache, cache, databases
I have galaxy S5, rooted, using root explorer(everything visible) and within data/data/androidproviders.downloads I have only 3 files.
cache,databeses and lib.
but in another directory data/data/com.android.vending I do have files you mentioned and some more.
All of my files as well directories have same set of permissions, which is
rwxrwx-x
I know you mentioned we should have drwxrwx--x and I don't know how to change it(if my permissions are wrong).
IF you can help pls I would appreciate.
Click to expand...
Click to collapse
Must be the "new" Android version... I don't have enough info to help You. the pesmissions are correct. That "d" in the beginning says it's a directory. After that there are rwx (means: Read, Write, eXecute) three times. These permissions are for Owner, Group and Others. That means the owner (the app that created this directory/file) should have full rights:rwx. He can read, write and execute the file/directory. Group is just a group of owners that can share some data. Like, You can put pictures into a directory and have all apps in group "viewers" access them. And then Others. Others are all other apps that are there. So basically drwxrwxrwx means anyone can do anything with that file/directory. drwx------ means only the owner has full access, all others cannot do anything. That's the permission system in linux/android in a really really fast lesson.
Now what You need to do is to find where S5 puts the things it downloads from App Store. Maybe You are missing that folder I have found. Dunno. Try to google it out and maybe someone can help You better. Or try to find it Yourself.
What I would do is to connect S5 with a cable to a PC, run adb shell logcat and then I would try to install something from the App Store. You will see all that crap that's going on and if there will be an error, You can see it, read it, think about it and solve it
Ot put it here and I will think for You
"invalid dowload url' problem
Thank you very much for super fast response. BTW, besides this post about 'invalid dowload url' problem there is nothing on the net, not one single word. I resolved my issue with reseting my phone and everything is fine now(it was easy since I have back up of everything). Will re search more and let you know if find any answers. Anyway, was looking at permissions in same folder after reseting my phone and everything is same as before but works. Thank you again, for your effort.
ntn_labs said:
Must be the "new" Android version... I don't have enough info to help You. the pesmissions are correct. That "d" in the beginning says it's a directory. After that there are rwx (means: Read, Write, eXecute) three times. These permissions are for Owner, Group and Others. That means the owner (the app that created this directory/file) should have full rights:rwx. He can read, write and execute the file/directory. Group is just a group of owners that can share some data. Like, You can put pictures into a directory and have all apps in group "viewers" access them. And then Others. Others are all other apps that are there. So basically drwxrwxrwx means anyone can do anything with that file/directory. drwx------ means only the owner has full access, all others cannot do anything. That's the permission system in linux/android in a really really fast lesson.
Now what You need to do is to find where S5 puts the things it downloads from App Store. Maybe You are missing that folder I have found. Dunno. Try to google it out and maybe someone can help You better. Or try to find it Yourself.
What I would do is to connect S5 with a cable to a PC, run adb shell logcat and then I would try to install something from the App Store. You will see all that crap that's going on and if there will be an error, You can see it, read it, think about it and solve it
Ot put it here and I will think for You
Click to expand...
Click to collapse
Try without an SD card in your device.
I don't have install in either place (com.android.provides.downloads or com.android.vending) on my PadFone X and keep running into this issue
EDIT: In my case it won't download the whole app.
EDIT: Downgrading Play Store fixed it!
Thanks, it worked
I didn't try changing permissions but just cleared the Download Manager data and it did work
Did this with Root Explorer, just want to mention, permission 771 should be granted not only for cache folder, but to every sub-folder.
Anyway thanx, this is really working solution.
Just a quick note: Noticed this error after installing the Xposed Module "Root Cloak". Since this error only showed up for root apps I figured that was the problem. Was able to update (TiBU and Greenify) by disabling Root Cloak - rebooting - updating - re-enabling Root Cloak.
Not sure what item I added to Root Cloak that is causing this issue, but for now this "solved" the problem for me.
Merman1983 said:
Just a quick note: Noticed this error after installing the Xposed Module "Root Cloak". Since this error only showed up for root apps I figured that was the problem. Was able to update (TiBU and Greenify) by disabling Root Cloak - rebooting - updating - re-enabling Root Cloak.
Not sure what item I added to Root Cloak that is causing this issue, but for now this "solved" the problem for me.
Click to expand...
Click to collapse
Dead or not I have ran into the exact same thing twice. First time was right after root cloak, and this time its been a while. That and a bad memory had me end up here. Root Cloak or not a simple fix permissions in something as old as ROM Manager or just do it in custom recovery fixed it for me. Android 4.3. Galaxy Note 10.1 2014 rooted stock with multi user. I note multi user because it has also caused me some grief due to knox magically appearing in the second user even though completely removed from ROM and also must enable multi user root in supersu. Thanks for making me chase permissions instead of go after the old sd card mount issues.
Fixing permissions worked for me thanks!
Solution to "Invalid download URI."
After some time of troubleshooting this issue, and performing all the previously recommended steps, we believe we found a really easy solution. In fact, I feel really frustrated that I didn't do this to begin with, but hey, live and learn.
This solution will typically work for folks who are getting this on almost every app, with a few exceptions. You may notice that some apps will install while others throw this "Invalid download URI." When an app is downloaded, the installer will then look to see where the app wants to install. Most of the time, these apps request to use the "SD Card" mount point. On most Android devices, even if you do not have a SD card installed, you will still have a SD Card mount point, which simply points to another location within the phones storage. It turns out that in this case, the S4 we were working on, had a SD card installed, but it was defective. So the installer would attempt to perform the installation step, but since the SD card wasn't responding appropriately, we would get this "Invalid download URI" error. After the card was removed, the Play store began functioning normally and apps would install without any issues.
Hopefully this helps everyone who had no success with the cache clearing and permission change solutions.
I wanna bump this to say thanks to the op and xda in general I been fighting with the aopen Opensign tablet10s that uses some hacked apon version of ics trying to get gapps working this thread was the final piece of the puzzle
THANK YOU
Hi people, I have looked around and haven't found anything to do with adb not letting any editing to the extSdCard whatsoever (without root)
I want to be able to use
Code:
adb push "C:\whatever.txt" /storage/extSdCard/
and actually work. everytime I do this it gives me:
Code:
failed to copy 'C:\whatever.txt /storage/extSdCard/whatever.txt': Permission denied
I have not got superuser privileges and made this thread for those who do not have it. PLEASE do NOT post anything to do with busybox or su, your efforts will be in vain.
Thanks in advance
for those coming here as reference, this is probably due to the changes to file permissions in KitKat
The Jinxer said:
for those coming here as reference, this is probably due to the changes to file permissions in KitKat
Click to expand...
Click to collapse
No, it's not. The Kit Kat SD card deal is only for 3rd party apps on the phone for writing to the SD card. http://www.androidcentral.com/kitkat-sdcard-changes . Has nothing to do with adb.
There are tons of people through the past few years that have this "trouble" for various phones and many versions of android. Often times it does just not work. Are you certain that the external is at /storage/extSDcard? Sometimes you have to do this as well:
adb push somefile.zip /storage/extSDcard/somefile.zip
What phone do you have? Why to the external and not internal and then just use a file manager to swap it over? Or use an external card reader. Or wifi file transfer.
es0tericcha0s said:
No, it's not. The Kit Kat SD card deal is only for 3rd party apps on the phone for writing to the SD card. http://www.androidcentral.com/kitkat-sdcard-changes . Has nothing to do with adb.
There are tons of people through the past few years that have this "trouble" for various phones and many versions of android. Often times it does just not work. Are you certain that the external is at /storage/extSDcard? Sometimes you have to do this as well:
adb push somefile.zip /storage/extSDcard/somefile.zip
What phone do you have? Why to the external and not internal and then just use a file manager to swap it over? Or use an external card reader. Or wifi file transfer.
Click to expand...
Click to collapse
my phone's details are in my signature.
I do push to the internal since i cant push to external. my external is called sdcard1 by the system. The reason for pushing to external is that it is 16GB compared to 8GB internal (5GB usuable)
Why can't you just transfer via MTP or wifi file transfer?
es0tericcha0s said:
Why can't you just transfer via MTP or wifi file transfer?
Click to expand...
Click to collapse
I have an automatic script which moves files to the phone/installs them if apk file etc. MTP sucks big time and wifi can be slow/not available
The Jinxer said:
I have an automatic script which moves files to the phone/installs them if apk file etc. MTP sucks big time and wifi can be slow/not available
Click to expand...
Click to collapse
Never really had issues with MTP. I work on phones for a living and have owned many (see list in sig) and use 3 different PCs - Win XP, Win 7, and Win 8.1 and MTP works right 99% of time for me on - you name it - HTC, Samsung, Sony, LG, etc etc. Have rooted/modded/upgraded/fixed 100s of devices and pretty much all of them I have to use MTP these days. *shrug*
If you have the ability to wifi tether, you can tether to your device and send files that way too. It's as fast/reliable as your data connection at that point though. I'm lucky enough to live in an area where I have a good signal almost always and have unlimited data so this option works great for me too. Your results may vary.
i forgot to mention i am in a no signal zone. so wifi is not an option. i dont mean mtp does not work, but i feel it is sluggish and has flaws, while my script has none. do you want my script?
basically it is a drag and drop batch file, and if the dropped file is an apk, it installs it. if the file is a mp3, video etc it moves it to a corresponding folder, and if the extension is not recognised, it offers to move the file to downloads. only flaw it has is that it needs editing to work on a phone that names the internal sd something else, which can be changed with an easy find/replace