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
Have a strange one I don't know how to fix. Purchased a Pyle PTBL102BCD tablet for the Mrs. to use basically as an ebook reader (according to About, running 4.2.2). When it came in I started sideloading apps to prepare it for her (I do not have a Google account), and searched on the Net about rooting the device. Found a one-click that worked with a different Pyle tablet, so I gave it a shot.
Now I have root access _only_ through the adb shell. None of the apps (including Superuser.apk itself as tested by updating /system/bin/su) can get root access, yet I have no problem running root through an adb shell - remounted file systems, even performed an su which is the only instance Superuser.apk's log shows. Root access in the shell remains between reboots, so it's not a temporary root.
If the adb shell has root, I _should_ be able to use it to grant access to everything else, and I've followed a few different "manual" root instructions (having different permission settings for su and busybox), with no joy. So long as I connect with a USB cable and type on the Windows machine, I'm god. On the tablet itself...not so much.
I hope that someone with a more intimate knowledge of Android internals can point me in the right direction for achieving root completely. Currently have Titanium Backup and ConnectBot (long java errors when I attempt to su there) installed to test root, Superuser v3.1.3 and su v3.1.1. Permissions on su are -rwsr-sr-x. And the human is confused.
Did you get anywhere with this? I have the same problem. What one-click did you use?
mfurlend said:
Did you get anywhere with this? I have the same problem. What one-click did you use?
Click to expand...
Click to collapse
Side note; REALLY hate the new forum software. With all the untrusted Google and Amazon javascript (which my company firewalls), it's a pain for me to even log in let alone post replies. (And I wonder if I'm the only person in the world sick to death of all the unnecessary ajax garbage...)
Anywho, used Kingo, rooted and unrooted a few times, until I finally acquired complete root on the thing. Once I did, I could run Samba, and once that worked, I could more easily transfer files and apks to the tablet.
Still don't understand why it was left in such a...weird...state - having root by default in adb is just a scary thing!
thanks for the information. I tried doing that but I encountered various problems. Eventually, after trying to do it manually, I totally screwed up the device. Now it won't boot.. I still have access to adb. I need to flash this thing. Do you know what the stock ROM is?
mfurlend said:
Do you know what the stock ROM is?
Click to expand...
Click to collapse
No...I can give you the Kernel version info (3.0.36+ [email protected] #48) and build number (rk3168_k11_4.2.2_v20131230), but other than that no clue.
Hello, i just inherit my moms Android 4.1.1 Tablet Ematic 7" EM63 purchased from walmart, a 70 dlls tablet. but with an issue, The tablet shows 0.00 HDD space available if no external SD card is plugged in, and its unable to download data or install APKs, The tablet works fine for browsing or playing files from sd card. but if the user restart the device it shows the factory reset screen after boot. The user needs to set up the wifi, google account, etc. Everytime a soft reset is done.
i've been told that not unusual activity was performed (no rooting, installing apks or messing up with files) before the issue happen. The tablet does not have Root privilege installed yet.
after a pair of hours doing research on internet i saw that it was a common (?) issue on generic brand tablets with 4.1.1 and the "busybox" application update (as im aware, no one updated the application on my moms EM63 tablet). According to "Dejan" from another forum this is the obvious fix for my issue.
Iregistered since i needed to thank you for your help, also i have some tips to add!
I had the same problem with all files wiped out and not enough space to instal new apps..
here is how i solved it.
1. Download root explorer here
2. Copy it to your memory card, and instal it (don't worry you will not have memory instal problem while installing it)
3. Run root explorer, and go to preferences and thick option "show hidden files"
4. Go back and inside root explorer there is an option "search", click on it and type in word "busybox", hit enter, after few seconds while he locate busybox location (mine was in /system/Xbin/busybox ) just copy it to /system/bin.
after that just reboot tablet..TAAADAAAM all your apps and everything is back to normal.
hope this helps and thank you again.
Dejan from Bosnia
Click to expand...
Click to collapse
After trying to fix the tablet by my own following this instructions i noticed that the tablet has indeed the buxybox file in the path /system/Xbin/busybox instead the path /system/bin.
Now, here goes the question:
As stated before, i dont have Root Permisions so i cannot move the busybox to the correct path in order to complete that fix, Is it possible to fix this issue without having to root my device? Im not exactly sure how and if its possible to root my "new" EM63 tablet since there is no Hard drive disk space available.
Is there a "easier" way to fix this issue?
Thanks in advance for any help regarding this issue
Att:
Roberto Villa
as a side note, the HDD can be "read" by the pc.
Noobs!
Hi everyone !
I've come to a problem involving quite a few (regretably stupid) steps.
I first tried to root my tablet with the kingo root app thingy, with a relative success. I was indeed able to get super-user access in an adb shell, but not grant acces to the apps that needs it when opening them. I may have been able to work around it, but here is not the problem.
My main goal was to delete some stock apps, and since i wasn't able to do it with another app i decided to do it manually.
steps involved :
adb shell
su
cd /system/app
and now my masterpiece :
rm Asus*
rm SetupWizard.*
and rm others less important
But unfortunatly the settings apk was hidden inside the Asus* crap (Probably AsusSettings.apk)
Until now, i was still able to use my tablet. Just unable to go to settings or anything, but obviously I found it quite anoying.
So there came my second masterpiece :
I booted into recovery, and did a factory reset.
Now, if i boot my tablet, i'm stuck at the language setup, and i can't go any further because when i want to continue it says that the setup wizard has stopped working. I can't connect the tablet with adb because I did this factory reset and I can't access the settings anymore.
I don't have a custom recovery, nor custom rom.
I anyone has a brilliant idea to solve my brilliant problem, he is more than welcome !
Cheers,
Guitou0
Reply
I found out how to resolve it.
From the begin I was trying to use the recovery to replace the entire firmware by its original (found on the Asus website).
For some reasons it didn't work, but what did work was flashing the system.img found inside the firmware package with fastboot.
fastboot oem unlock (not sure that it was necessary)
fastboot flash system (path to system image)/system.img
After some time, (230sec approximatly) i got an error message, but when i rebooted the tablet the missings apks where back.
I recently rooted my device. ( my first time, go figure) After many errors and even a bricked device, I finally managed to root the device and unbrick it. I believe the opperating system was deleted in the process along the way and I had to flash a stock ROM onto the device, resulting in a downgrade from 6.0 to 5.1.1. I still had TWRP on the device and was able to put the needed superuser zip files on the SD card when in TWRP mode because that's the only time the pc recognized the phone. After install in the Superuser files in Twrp the device rebooted up and I ran a root checker and it says that superuser was installed correctly and I have root access. Now here's the issue, I went to go and turn on unknown sources and when I click on fingerprints and securiry, I'm met with an error message saying com.android.settings has stopped . this happens In a few other areas of the settings but not all. I also had downloaded another app (NT Hidden Settings) that I was hoping would allow for me to turn on unknown sources and when I click on the option to turn on unknown sources, I get anmessage saying system/bin/su missing. I now am lost and have no idea what to do. I tried copying a file named su from the xbin folder thinking that may fix the issue but it didnt. Any tips or ideas? If I have to unroot the device and reroot I have no problem doing so (although I'd probably need a concise tutorial because I had very poor luck getting as far as I did..)