Related
Every time i get a picture and try to open it, it gives me a force close. then i go back and click on it and it wont let me open the pic at all....any ideas?????
nard_23 said:
Every time i get a picture and try to open it, it gives me a force close. then i go back and click on it and it wont let me open the pic at all....any ideas?????
Click to expand...
Click to collapse
Might be something wrong with your permissions! Does this happen with other apps or just the gallery?
Try one of these....
1. Bring up the Terminal APP....Type
su
fix_permissions
If you don't have the terminal app and want to do it via ADB
type this in via ADB
adb shell fix_permissions
From Recovery
In Amon_Ra's recovery, the fix_permissions script is run by selecting the 'other' menu then selecting 'Fix apk UID mismatch' .
In CM-1.4 recovery, it must be run manually from console (alt+x on G1) or adb shell, as above from terminal except 'su' is not needed.
Once you get done fixing permissions do a reboot and you should be golden!!
2. Boot into recovery, wipe and re-flash the MIUI rom again and that should fix your problem!
3. Post this same exact question in this forum and see if someone running the same exact rom you got can duplicate your problem and fix it!
http://forum.xda-developers.com/showthread.php?t=915527
GOOD LUCK DUDE!!
Hello!
I'm new to this forum so i hope I'm putting my question in the right place on this forum.
I own a HTC Desire that is rooted with Cyanogenmod 7.1.0.-Desire ROM (S-ON) and i can't get AdFree to work - ads and banners in apps are not blocked at all. In Adfree app's Options i pot a 'tick' on all options, including on "Use /data/data/hosts symlink" and the one below that one.
I also tried to make a host file through adb ("cp /sdcard/hosts /data/data/hosts") but i get the message "cp: can't stat 'sdcard/hosts': No such file or directory".
I tried installing AdAway app, but that doesn't work either since the phone has to be S-Off if I'm not mistaking...
So has someone here had similar experience with Desire on Cyanogen and AdFree? Haw can I get it to work? Is the only solution S-Off?
Thanks for help!!
Hi,
did you restart the device? Also you must press the "Download & Install Hosts" button so the hosts file is edited.
I personally have the first two options checked (Check for updates and Autoupdate). Always after tapping the button I get noticed that I may need to restart the device to clear DNS cache. Everything works perfectly for me, no ads at all. But I use Sense ROM.
Yes i did restart several times after tapping "download and install hosts" but after restart nothing changes that's why I'm asking what to do next...
I think there is no "hosts" file on the SD card. Could that be a part of the problem?
With S-ON, Adfree is not working.
Only 2 possibilities
1. Either make S-OFF and retry Adfree
2. Do manual symlink for hosts from system to etc via adb in fastboot mode
2. Do manual symlink for hosts from system to etc via adb in fastboot mode
Click to expand...
Click to collapse
Thanks for the reply. I'll try the 2nd option first. Actually i did try it and i got the error message in cmd: "cp: can't stat 'sdcard/hosts': No such file or directory", as i described in post #1. Why do i get that message?
I followed a guide from a forum where they described the process for AdFree on HTC incredible but to clarify my steps:
I downloaded Adfree from the market, tapped to download and install... then got the message to reboot because i need to clear my DNS cache. Powered down the phone, powered up by holding volume down button, got into clockwork recovery, mounted /system, /data, /sdcard
connected phone via usb, got cmd up, got into adb shell and typed in the command but got the error message...
Am i doing something wrong?
Can someone guide me through the process? thanks!
acimer said:
Thanks for the reply. I'll try the 2nd option first. Actually i did try it and i got the error message in cmd: "cp: can't stat 'sdcard/hosts': No such file or directory", as i described in post #1. Why do i get that message?
I followed a guide from a forum where they described the process for AdFree on HTC incredible but to clarify my steps:
I downloaded Adfree from the market, tapped to download and install... then got the message to reboot because i need to clear my DNS cache. Powered down the phone, powered up by holding volume down button, got into clockwork recovery, mounted /system, /data, /sdcard
connected phone via usb, got cmd up, got into adb shell and typed in the command but got the error message...
Am i doing something wrong?
Can someone guide me through the process? thanks!
Click to expand...
Click to collapse
via adb, copy the hosts file from /system/etc/ to /sdcard.
Then use symlink option.
or you can get the hosts file from the below link
http://forum.xda-developers.com/showthread.php?t=696084
You can see the below thread for more help.
http://forum.xda-developers.com/showpost.php?p=9609932&postcount=10
May be this app help you:
http://adfree.bigtincan.com/adfree.apk
I rooted my KFHD 8.9, installed the Play Market, Go Launcher HD, and a few other things. Everything went smoothly...until I decided to install TSF Shell 3d. I moved it to system/app, changed permissions, and rebooted. Now, TSF is stuck in a loop and I can't access ES File Explorer long enough to delete it from the device. When I try using Android Commander, it shows "No Root" and I'm not very experienced at ADB. Is there some way to get this off my device so it's usable again?
When I boot up, it boots normally, then before I can unlock the lockscreen, I get "TSF Shell has Stopped" with a button below it to ok the message. When I tap it, it goes away for a split second, then comes right back...over and over.
Any tips or advice would be greatly appreciated. Thanks.
(I posted this here because I did not see a Q and A or Help section that was KFHD 8.9 specific. If it needs to be moved, feel free and I apologize.)
couple of things to try. if you can access the pull down menu go to more settings, applications then find tsf shell and clear defaults. reboot.
if that doesn't work reboot to recovery and do a factory reset.
adb reboot recovery.
I will try the adb reboot recovery option. I can't get into anything on the device itself long enough to do anything. Also, I didn't even set TSF as default home. I'm thinking (the way adb is acting), that I don't have full root privileges. When I try to delete the file using adb, I get a permission denied error.
slim6596 said:
I will try the adb reboot recovery option. I can't get into anything on the device itself long enough to do anything. Also, I didn't even set TSF as default home. I'm thinking (the way adb is acting), that I don't have full root privileges. When I try to delete the file using adb, I get a permission denied error.
Click to expand...
Click to collapse
Have you tried:
Code:
adb shell su -c "rm /path/to/TSF.apk"
...replacing "/path/to/TSF.apk" with the actual path to the actual name of the TSF app you want deleted? Just be sure to leave the quotes around the command or it may not work.
soupmagnet said:
Have you tried:
Code:
adb shell su -c "rm /path/to/TSF.apk"
...replacing "/path/to/TSF.apk" with the actual path to the actual name of the TSF app you want deleted? Just be sure to leave the quotes around the command or it may not work.
Click to expand...
Click to collapse
I tried adb shell su -c rm/system/app/TSF Shell 3D
"permission denied" and then "device not found" when I tried editing the pathname. What am I missing? The path to the Kindle?
slim6596 said:
I tried adb shell su -c rm/system/app/TSF Shell 3D
"permission denied" and then "device not found" when I tried editing the pathname. What am I missing? The path to the Kindle?
Click to expand...
Click to collapse
There is a space between the 'rm' command and the path. Also you need to get the exact name of the file you want removed...
Code:
adb shell su -c "ls /system/app"
And again, don't forget the quotes...meaning leave them there.
"Is" or "rm"?
........and thanks for trying to help me out. I really appreciate it.
slim6596 said:
"Is" or "rm"?
........and thanks for trying to help me out. I really appreciate it.
Click to expand...
Click to collapse
'ls' is the list command. Use it to list the contents of either the '/system/app' directory or the '/data/app' directory to find the exact name of the 'apk' that is causing problems, then use the 'rm' (remove) command to get rid of it.
I got it to work. TSF is gone (yahoo!). So now I get to start over. What I finally did was to do a total restore using KFFirstAide. Thanks you guys for pitching in and helping a newb. I appreciate it to no end.
Hi, i installed Rbox's custom recovery earlier. When running the initial coomand from the adb shell i had to run it as su or i received a permission error. After running the reboot recovery command, the device rebooted, displayed the white Amazon logo, and then went to the Amazon update failed screen... after a minute or two it started up fine. Am i doing something wrong. Thanks!
It seems when you did the dd commands it didn't write the recovery. So you either typed the command wrong, or don't have root access which is needed for permission to write to the partition. Did your cursor change from an $ to # after running su?
Luxferro said:
It seems when you did the dd commands it didn't write the recovery. So you either typed the command wrong, or don't have root access which is needed for permission to write to the partition. Did your cursor change from an $ to # after running su?
Click to expand...
Click to collapse
i didn't notice to be honest, but i did get a message on the FireTV saying su access had been granted, and then the text in the shell (after i copied and pasted the command from the thread in) looked as if it worked... no errors. And yes, i had named my file the same as the example and had put it in the same location. Once i ran the reboot recovery command was where i got the Amazon updated unsuccessful screen. i had thought it would just reboot into the recovery menu. Thanks.
tavery said:
i didn't notice to be honest, but i did get a message on the FireTV saying su access had been granted, and then the text in the shell (after i copied and pasted the command from the thread in) looked as if it worked... no errors. And yes, i had named my file the same as the example and had put it in the same location. Once i ran the reboot recovery command was where i got the Amazon updated unsuccessful screen. i had thought it would just reboot into the recovery menu. Thanks.
Click to expand...
Click to collapse
What you saw was the stock FireTV recovery. I'd give it another try and make sure it switches to root access (#).
I started over as suggested and it worked as it was supposed to this time. I obviously must have missed something or had a typo the last time. Thanks for your help!
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
LastDeuS said:
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
rbox said:
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
Click to expand...
Click to collapse
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
LastDeuS said:
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
Click to expand...
Click to collapse
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
rbox said:
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
Click to expand...
Click to collapse
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
LastDeuS said:
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
Click to expand...
Click to collapse
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
rbox said:
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
Click to expand...
Click to collapse
I can bring a keyboard from work tomorrow if that would help us troubleshoot cuz right now my keyboard is wireless
I know I've been asking a lot this last hour but can you please point me in the right direction so tomorrow I can Try something else using an usb keyboard?
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
roligov said:
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
Click to expand...
Click to collapse
Well yesterday I couldn't bring the keyboard but now I have it in front of me but I haven't been able to reproduce the recovery mode with the keyboard combination.
I know it works because the firetv reboots but sometimes goes to the initial amazon logo and sometimes just the same updating android logo
So any suggestions now that we have the keyboard here???
OK I finally figured it out.
All started when I ran the command "echo --update_package=/cache/update.zip > command" to update to a stock ROM but was never able to PUSH the actual file... kept getting error "cannot stat ‘update.zip’: no such file or directory"
THEN
I successfully installed Clockworkmod Recovery (luckily) and when rebooted to recovery I was presented with Clockwmod Recovery asking if sure to install the NON PRESENT "rom.zip"
BUT i didn't have a keyboard with me at that moment and didn't know the "control recovery" command either... SO I thought to find a different way to PUSH the file....
So I used push file function in adbfire to get the file into /sdcard/ and the the mv command to get it to /cache
SO I got my problem right there wich I was able to reproduce today: When you connect to adb during recovery or booting the FireTV you will get this error for most commands including su ----> "/sbin/sh: not found"
NOW if you try to push a file it will say it got pushed but only half of it or some shortcut of it I'm not sure
The thing is with that half pushed file the system now obeys "echo --update_package=/cache/update.zip > command" and starts updating and shuts down reboots and update again, whatever you do it keeps on booting again to the same state(trust me nothing works)
What I did basically with the few seconds I got between reboots I ran "rm -f /cache/*.bin" and rm -f /cache/*.zip to erase all cache folder and then I was again asked to install the file (not there again) and disabled recovery flash
Anyways thanks for all the replys I got really appreciated all your help and keep up the good work ppl I hope this helps someone out there besides me.
I'm now running the latest prerooted rom from rbox thanks again for that
have a good one
question: Is there an actual gui windows app to transfer files to FireTV???
2: Do I need to block updates for this custom rom also or that's already implemented?
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
schneid said:
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
Click to expand...
Click to collapse
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
rbox said:
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
Click to expand...
Click to collapse
TiBU shows mine "frozen". Did I do that previously with something else?
schneid said:
TiBU shows mine "frozen". Did I do that previously with something else?
Click to expand...
Click to collapse
Either you froze it with titanium previously or you did the pm disable command.
rbox said:
Either you froze it with titanium previously or you did the pm disable command.
Click to expand...
Click to collapse
I did do the PM disable thing but thought your rooted ROM would undo it. Guess not. Anyway, I'm happy. Thanks.
Think I bricked mine
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Note3usr said:
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Click to expand...
Click to collapse
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
rbox said:
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
Click to expand...
Click to collapse
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
I am in a similar boat. I tried to install "rom.zip" per the instructions here http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
but it would not install it from CWM. It would abort the installation instantly. I read another thread where someone wasn't able to do something through ADB Shell because of SU permissions. I tried to uninstalled it and sideloaded SuperSU again. When I accessed it instead of clicking on "Normal" I chose the other option. Well, it's not stuck in the same loop as mentioned here.
I see the Amazon logo briefly, then it shows the android logo and reboots. It disconnects for a few seconds with the TV saying there is no HDMI connection and then shows the amazon logo shortly after again. I can no longer ADB into it.
Please help.
Note3usr said:
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
Click to expand...
Click to collapse
Hey your problem is really similar to mine and what I did was connect to adb in between the loops and erase all cache
try searching on your router or do a scan on your network and find the correct ip address for the firetv
also don't worry about not being able to SU just erase cache using "rm -f /cache/*.bin" and "rm -f /cache/*.zip"
then it will ask for the actual file and just choose "not to install" then "disable recovery flash"
pd: Don't try to enter recovery by keyboard combinations it's useless trust me I tried A LOT