Related
Ho there, Im sure this has been posted a thousand times before. The best post I could find was s0be's fix but the instructions are not in regular English. Basically, I am unable to download any new apps/any app updates for no apparent reason. I have tried every solution under the sun except this one. Usually you guys know what your talking about so I have confidence in it.
http://forum.xda-developers.com/showpost.php?p=11055157&postcount=4647
can anyone translate? would be much appreciated.
We can forgo any contemptuousness by simply acknowledging my n00byness now.
Thanks
dburg84 said:
1. adb shell
This starts an interactive shell with the device. Every command from now on will run on the device and not on the computer.
2. su
su = Super User = the highest level of clearance. Once this is called you are running as root and have access to every little thing in the OS. You are now the boss. You need "root" to get access to this command.
3. mkdir /cache/download
mkdir = Make Directory = Create a new folder/directory with the name "download" in the path "/cache/".
"/" being the master/root path for all paths.
4. chown system:cache /cache/download
chown = Change owner = Change the persons who are recognized by the OS as being the owners of that particular directory.
system:cache = the user is "system" and the group is "cache".
Every file and directory on the OS always has 3 person categories attached. User (the owner), Group(the group), All (everyone else). You can change permissions for every one of those 3 as seen below.
5. chmod ug+rwx /cache/download
chmod = Change Mode = change the permissions for a specific file.
ug = both the User and the Group.
+rwx = Add (the +) Read, Write and eXecute permissions.
ug+rwx /cache/download = Add Read, Write and eXecute permissions to the user and group for the directory "/cache/download".
6. chmod a+x /cache/download
As above, but here you giving everybody else eXecute permission only.
Click to expand...
Click to collapse
I have edited the post you referred to.
My comments are in bold.
Good luck
http://en.wikipedia.org/wiki/Chmod
http://en.wikipedia.org/wiki/Chown
http://en.wikipedia.org/wiki/Mkdir
Thanks!
Thanks for clarifying!
/sacrifice lamb to the XDA gods
I had the same problem some days ago and i tried almost everything i found on the web, but nothing worked.
At least i solved the problem replacing the market app (vendor.apk) with a most recent one.
To do this you need a working vendor.apk (i grabbed from a most recent rom) and a file explorer who can use root to copy file in /system/app (like ES File Explorer or Root Explorer).
Now simply replace vendor.apk.
This worked for me
Or you could just re-install it.
Use my APK installer tool and check the "re-install" box.
This will overwrite the apk file but not mess with the configuration...
Just like what you suggested :0)
yes sure, nice tool mate
Thanks for all your help!
Thanks for all the help! I did what you suggested and tried to replace the android market with a newer version. I couldn't do a direct install with a new APK, someone said you have to uninstall the old APK. I decided to try just flashing a new gapps; I got the files from this thread http://forum.xda-developers.com/showthread.php?t=909067
It worked. The new market was able to update my apps successfully.
You guys rock!!! Thanks again!
no problem mate, i got crazy for the same problem last weeke so i'm happy to share the solution
Would it work if i do the same for "download unsuccessful. please try again" problem ?
the "please try again" problem should be a connection problem I suggest to check your wi-fi or apn settings
I made it just a minute ago.
-- Unmount SD Card. (Settings - Sd& Phone Storage)
-- Install any app from Market. (It will install without any error.)
-- Mount SD card back. And ta-daaa! You can install any app from market now.
Thanks anyway
jamiescott23 said:
I made it just a minute ago.
-- Unmount SD Card. (Settings - Sd& Phone Storage)
-- Install any app from Market. (It will install without any error.)
-- Mount SD card back. And ta-daaa! You can install any app from market now.
Thanks anyway
Click to expand...
Click to collapse
i having this issue atm i have tried this and it didn't work...
you can also try to clear data from "download manager" in the app manager
ok got a fix to this with rom manger i DL and install new gapps Im useing CM6 so i used 20101020 mdpi-tiny i let it back up and wipe all data and it worked but i wish i would have tried it with out wipe 1st but it works now...
Hello,
Just got my new TF and thanks to XDA I've already rooted it and installed rom Prime 1.4 to get a rooted 3.1 android version.
Everything goes fine except for mapping network shares. Mounting network shares with cifs manager is ok except that I'm French so some directories in my network got unicode characters and I can't mount them.
Does anyone know how to bypass this limitation ?
On my understanding, I should install a cifs.ko module compiled for the TF and the 3.1 Android version in /system/lib/modules but I don't know where to find such module.
Thanks in advance
Try es strongs file explorer. It allows you to add network shares.
Sent from my Transformer TF101 using XDA Premium App
Thanks, but I've already done it without success.
The issue is not to map a share, this is working. The real issue is that share with unicode characters (like é, è, à...) are not working.
Thanks anyway
Im also rooted with prime 1.4 buf cant get any shared volume to mount via cifs manager. What am i missing here?
Have you tried adding 'iocharset=utf8' to the mount point options?
Don't know if this can help you or not, but my 1st mistake with cifs manager when I tried it fist time was that I haven't put anything on mount point.
What you need on the fields of cifs manager is:
Share Path: The path to your share ==> ex: 192.168.1.5/share (this is the shared dir on your server)
Mount point: The name of the "false" directory that will simulate that your share is on your tablet ==> ex: /sdcard/cifs/share (this is up to you but keep close to this)
Plus of course username and password (I thinks that anonymous connection is not allowed anyway)
Hope this help
Tortel1210 said:
Have you tried adding 'iocharset=utf8' to the mount point options?
Click to expand...
Click to collapse
I don't know how I can do that. Is it an argument to parse in a field of cifs manager ? If so how should I do that ?
Can you help me with this please.
XPNect said:
I don't know how I can do that. Is it an argument to parse in a field of cifs manager ? If so how should I do that ?
Can you help me with this please.
Click to expand...
Click to collapse
If you edit the settings for a mount point (Long press on it, then choose edit), there is an options text field at the bottom. Put it in there, save, and try mounting it.
XPNect said:
Don't know if this can help you or not, but my 1st mistake with cifs manager when I tried it fist time was that I haven't put anything on mount point.
What you need on the fields of cifs manager is:
Share Path: The path to your share ==> ex: 192.168.1.5/share (this is the shared dir on your server)
Mount point: The name of the "false" directory that will simulate that your share is on your tablet ==> ex: /sdcard/cifs/share (this is up to you but keep close to this)
Plus of course username and password (I thinks that anonymous connection is not allowed anyway)
Hope this help
Click to expand...
Click to collapse
Thanks!!! Dont know how or why but now it works!
Tortel1210 said:
If you edit the settings for a mount point (Long press on it, then choose edit), there is an options text field at the bottom. Put it in there, save, and try mounting it.
Click to expand...
Click to collapse
It works fine a big thanks.
I've been abused by the comment and I was thinking that this box was only for a domain name... feel stupid sometime
I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?
yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.
ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.
This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.
be careful, backup buid.prop and restore it after creating Box account.
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
I am having no luck finding a way to get root access from a computer.
deleted post
user error
The tumbleweeds are big around here
There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
But is there an app to copy my file over from my computer?
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.
jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...
its taking forever to install SDK
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.
yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?
Me and my best friend both have Kindle Fires now. I rooted & flashed the latest MIUI onto both of them successfully over the past week, so we're running the latest version available. What we've found is that when we both try to attach to his wireless router, they seem to disrupt each other or confused the router and eventually our wifi goes bye-bye on our Kindles. When just one of us is trying to attach to his router, it goes through fine & seems to stay connected well without any issue.
Can anyone offer any recommendations on how to perhaps customize the wifi connection on either the Fire or the wifi router to try and resolve this issue?
Thanks much for your help in advance! Please ask any questions if I left out any details that could help : ]
Does MIUI have the MAC address problem? That'd be the first place I'd check. THen I'd check the router and see exactly what they're trying to do. My thoughts:
Either they have the same MAC, same name, or are vying for the same IP.
http://forum.xda-developers.com/showthread.php?t=1406845
Thanks for the feedback, guys! And thank for that related thread link! I reviewed that post and I have to admit, I'm a lil lost with where to start or what to do with that. I have a feeling both devices may be running the same MAC address, but I'm in the process of confirming that today. I also tried forcing a static IP on the Fire when connecting, but that didn't seem to resolve the problem.
Anyone have any, dare I say, more simple instructions for how I might go about altering my devices MAC address with MIUI? I'm not sure that the information in that post is fully applicable to the MIUI rom, so I'm hesitant to begin trying to give it a go, and plus, I might need something a little more noob-friendly... I could use a little more handle-holding with this, as I'm fairly fresh to rooting & flashing ROMs (but fairly computer literate).
look at post #24 in the linked thread - seems to be a easier solution
Oh, thanks! ... That does look much more manageable Now to just figure out where to get the file from the stock ROM and replace it. I did a backup of my stock stuff via TWRP prior to flashing MIUI, so does anyone know where I can locate this file from the stock amazon ROM after I've completed a backup of stock via TWRP?
I then assume that after locating the stock version of the file, that I would just replace the file in the root directory/system/bin right on the Kindle when it's attached to my PC via USB.
Yah.. I'm a noob, but trying! : \
Stock file I need to find: /system/bin/wlan_loader
there is one attached 2 or 3 posts after #24 - that should do it for your needs
Great! Thanks again!!!
This part of the post gets me a little lost. I assume I need to purchase & download Root Explorer ($3.99 in Market). As for performing the same thing this person did, I'm not quite sure how to go about doing that. One question I have is: Is Root Explorer absolutely necessary to perform this file replacement? It seems a little more involved than just simply replacing the file on the device while it is plugged in to my PC via USB.
I used root explorer, mounted as r/w, made a copy of the original JIC, overwrote the existing file within /system/bin and modified the permissions to appear as the original (rwxr-xr-x) rebooted leaving the system as r/w
Sure enough mac address is the same as when I was in 6.1 Kindle Fire OS.
Click to expand...
Click to collapse
Specifically, here are the things I'm not 100% clear on:
1) 'mounted as r/w' - I assume this means mounting as read/write; is this performed via Root Explorer?
2) 'made a copy of the original JIC' - I do not understand what is meant by 'JIC'
3) Can file permission changes as described above be performed in Root Explorer?
I greatly appreciate any insight! This appears to be the solution to my problem, not it's just a matter of execution on my part. Thanks, guys!
would use file explorer from the market - no cost and does the same
if you activate "root explorer" and "mount as root" in the settings all at the bottom
here the link:
https://market.android.com/details?id=com.estrongs.android.pop&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5lc3Ryb25ncy5hbmRyb2lkLnBvcCJd
1) 'mounted as r/w' - I assume this means mounting as read/write; is this performed via Root Explorer?
Click to expand...
Click to collapse
file explorer does this with the above settings automatically
2) 'made a copy of the original JIC' - I do not understand what is meant by 'JIC'
Click to expand...
Click to collapse
would mean he means the file to exchange
3) Can file permission changes as described above be performed in Root Explorer?
Click to expand...
Click to collapse
you can also do with file explorer - long tap on file - properties - change permission
Awesome - b63 - you're excellent
Ummmm... But I have to ask a really stupid question. I can't seem to find the /system directory on my Fire. I already had ES File Explorer... and I'm in it now, and I can only look around on my SD card it seems... Is the /system directory on the main internal storage of the device, or on the 'SD card?' Any help in finding this directory on my device would be appreciated! Sorry for the nooby questions n such
are the root settings made in the settings of es ?
then you can set your start directory to / somewhere in the settings
or simply go one directory up
when you are on / then you see the system directory like all the others (sdcard also)
OK... I'M SO CLOSE!
I got up to the root directory ( / ) and found the /system/bin directory... I have the new (well, old stock version) wlan_loader file from the linked thread that I downloaded on my Kindle on the SDCard ready to overwrite the existing file.
I definitely have Root Explorer on in ES File Explorer - it prompted me to allow and I did every time it asked. I then tried to copy the stock version of the file over my current version in /system/bin, but it said that the copy failed. I then went and tried to delete the existing file in /system/bin, but it said something like 'this file cannot be deleted' I'm not sure what is keeping the file locked. Do I need to modify the permissions of the file to be writable or something?
I hard-pressed on the file and tried to play around with it, but the only close option I have is 'Properties,' which didn't seem to allow me to change anything about the file though. So, I'm stuck : \ Help!?
OK, I got it! I didn't flip the 'Mount /, /system as writable option after switching on Root Explorer :\ My bad! But I was able to overlay the file now Let's test my MAC address now after rebooting.
looks promising ...
GET-R-DONE!
Yahoo! I got it!
I rebooted and everything seems to be functioning just fine - I'm connected to Wifi like normal, no big deal... AND, my MAC address is totally different than what it was before, so I think this did the trick!
Now to test it concurrently with my best friend's Kindle to ensure we can sit on the same network / router together. If it doesn't work, then I'll look to replace his wlan_loader file as well
Thanks for all your persistent assistance b63! I really appreciate it : ]
Was fun, and I learned a lot : ]
but take care if you change his one as well not to end up with the same mac again ...
and as allways - glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Hi everybody,
I want to share with you all what I've found to fix my problem :
MY PROBLEM : I had to repair my phone with Bluetooth devices (carkit/headset) EVERY times Bluetooth was reboot (phone reboot or bluetooth off/on)
What I was thinking was an Android 4.3 problem (thanks to Google to confort poeple on what they think ).
The reality : I formated /persist /firmware and there is a folder inside usefull to remeber bluetooth pairs (New feature from CWM --> Who did not tried it and got bootloop??? )
So here is the solution :
THIS IS NOT MY SOLUTION --> I FOUND IT HERE --> DON'T FORGET TO THANKS THE RIGHT GUY (A BIG BIG THANKS TO Gigadroid FOR HIS POST)
Original post
So, here is what you have to do to fix Bluetooth pairing memory,
Using your fingers and an explorer (with root):
- In /persist directory : Create a directory callled "bluetooth".
- Inside this directory, create a new file named .bdaddr (don't miss the dot!)
- Edit the file and put 6 random characters in it. Even better, if you can do this in a hex editor and put 6 random bytes, not just printable characters.
- Set permissions :
1) Set "execute" and "read" for everybody on /persist/bluetooth directory
2) Change owner of .bdaddr to bluetooth:bluetooth (owner:group) and permission to Read / Write for owner and group (and nothing else).
Using command line : (I never use it, so not tested)
chown root:root /persist/bluetooth
chmod 755 /persist/bluetooth
chown bluetooth:bluetooth /persist/bluetooth/.bdaddr
chmod 660 /persist/bluetooth/.bdaddr
After that, your Bluetooth device won't be forgotten (if i can call it like that) by your android device (for the last time or until next ROM flash )
Where is /persist?
Err0r-4o4 said:
The reality : I formated /persist /firmware and there is a folder inside usefull to remeber bluetooth pairs (New feature from CWM --> Who did not tried it and got bootloop??? )[/INDENT]
Click to expand...
Click to collapse
Where is this /persist folder? I have searched my whole phone with "find / -name persist" in a terminal as root and nothing is found?
TheRealLifeboy said:
Where is this /persist folder? I have searched my whole phone with "find / -name persist" in a terminal as root and nothing is found?
Click to expand...
Click to collapse
Soz for late answer, I hope you've find answer by youself.
If not, just use a Root explorer (I'm using ES explorer with root rights and it works well)
Go in Explorer --> Go in root folder (named " / ")
Then you'll find the "persist" folder inside, go in and create the new folder said in OP.
In case where there where not this "persist" folder in "/" folder, just create it
I recommend doing all this from phone (and not from windows), especialy for create the ".bdaddr" file.
Hope you'll use BT again in peace^^
Regards
What if /persist doesn't survive a reboot?
Err0r-4o4 said:
Hope you'll use BT again in peace^^
Click to expand...
Click to collapse
I have created the directory now and set the permissions and ownership, but when I restart Android, the directory is gone. Any idea how I can make the change stick and survive the reboot?
Thanks again!
TheRealLifeboy said:
I have created the directory now and set the permissions and ownership, but when I restart Android, the directory is gone. Any idea how I can make the change stick and survive the reboot?
Thanks again!
Click to expand...
Click to collapse
Hey. Its surely late (f**** quote not seen )
All I van say is that you maybe forgot to give your explorer all root rights.
Btw, be more explicit, which folder tour created?
DehoXeD said:
Hey. Its surely late (f**** quote not seen )
All I van say is that you maybe forgot to give your explorer all root rights.
Btw, be more explicit, which folder tour created?
Click to expand...
Click to collapse
This is what I did: (as you wrote up above)
Go in Explorer --> Go in root folder (named " / ")
Then you'll find the "persist" folder inside, go in and create the new folder said in OP.
In case where there where not this "persist" folder in "/" folder, just create it
I recommend doing all this from phone (and not from windows), especialy for create the ".bdaddr" file.
I didn't have a /persist folder so I created it. My phone is rooted, so I did it as root.
Fortunately I don't even have "windows"; did it all from my phone.
The directory is there, but when I reboot, it's gone
And what is your phone?
And your problem is that your BT devices arent memorized by your phone?
DehoXeD said:
And what is your phone?
And your problem is that your BT devices arent memorized by your phone?
Click to expand...
Click to collapse
Samsung Galaxy Tab 7" (P1000) running Cyanogenmod 11 M12.
Not just that, they disconnect pretty soon after receiving of making a call. Then it's hard to get them to connect again. The headset (Hybrid BT) works fine on a Blackberry and Galaxy SII.
TheRealLifeboy said:
Samsung Galaxy Tab 7" (P1000) running Cyanogenmod 11 M12.
Not just that, they disconnect pretty soon after receiving of making a call. Then it's hard to get them to connect again. The headset (Hybrid BT) works fine on a Blackberry and Galaxy SII.
Click to expand...
Click to collapse
Hmm, sounds different from what was my initial bug.
The problem was that when I disconnected my BT device from my phone, when I was trying to connect it back (by clicking on the list of BT devices), the phone had to launch "paring" whenever the device was already known.
Btw, I had Zero prob when they were connected as you have.
So it's not the same problem.
I think your problem is CM11 related (As samsung hasn't release official 4.4, it may stay drivers bugs...)
hi. I have this desire 310 dual with cm13 (lineage by swoopae)
can anyone tell me how can I fix pairing with bluetooth headphone?
bt turns on, recognises devices and sends and receives files, even pairs with bt headphone (after some time pending, fake pairing) but no sound
I flashed some mtk bt-fix, didnt do it
changed bluetooth MAC number
swapped files with lollipop that works fine but bt crashes