Related
I used to use "Root Explorer" on my hero to delete system apps before..doesn't seem to work anymore..
solution??
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
did you mount /system in rw mode? (it's ro by default)
U dont have write access to system partition in normal use if i read the tutorial right. U have to do it with an update.zip (editing the update script) or with adb both u have to do in recovery menu from modaco i think. Tell me if i am wrong.
Sry for my bad english
@cezarL yes I did
@xtcislove I wish u were wrong..seems like pain.. anyway to do it without a pc?
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Damn, you're right. Previously, I had deleted an .apk just to check if it's working, then reinstalled the app right away.
But I just tested now, it looks like after a reboot, the .apk magically reappears, and the application is running as usual
Damn, you're right. Previously, I had deleted an .apk just to check if it's working, then reinstalled the app right away.
But I just tested now, it looks like after a reboot, the .apk magically reappears, and the application is running as usual
Click to expand...
Click to collapse
ye..I'm sure it has something to do with the root limitations Paul mentioned in his rooting guide. hope it'll be fixed soon.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Try this: Boot in recovery menu and try the following commands:
adb remount
adb shell rm /system/app/APP.apk
adb shell rm /data/app/APP.apk
where APP.apk is the filename of the apk with the .apk extention, remember case-sensitive!
for example:
adb remount
adb shell rm /system/app/FriendStream.apk
adb shell rm /system/app/FriendStream.odex
take a look before if your app has a odex or try this: (here u need only one command)
adb remount
adb shell rm /system/app/*FriendStream*
Good luck and have fun =)
Edit: Just find a topic =)
hxxp://android.modaco.com/content/htc-hero-hero-modaco-com/297207/removal-of-apps-via-adb/#entry1124362
(replace hxxp with http)
I'm trying to do these things in windows at the moment. No issues getting in the recovery with the windows scripts. But when I try to open a ADB Shell after I've gone to recovery I can't really do anything with it and the recovery hangs (not controllable with the track pad).
Anyone can tell me what I'm doing wrong?
You're not doing anything wrong, from what I've seen opening a new adb instance on Windows will kill the server created by the .bat file used for recovery... which means the connection to the device is lost. I haven't looked into it further, but it might be fixeable somehow.
Ah I see, so basicly you undo the patched recovery by opening a new session. It does work properly under Linux then? I run ubuntu on my netbook so It's not a big issue anyway. Thanks for the tip, gonna try under linux now!
I'm having the same problems as:
http://android.modaco.com/content/h...co-com/307401/removing-sys-apps/#entry1256015
I removed a load of HTC widgets but I get strange entries on the widget menu. Anyone know how to get rid of these?
Also, I removed Stocks (.apk and .odex), now I get a force close on 'Accounts & sync'. Anyone know how to remove Stocks properly?
Cheers.
After running the bat file to get into recovery, start a new cmd prompt in windows and use again adb-nilezon for shell commands instead of ordinary adb, and it wont be killed.
This has worked for me atleast
blackadder1000 said:
Anyone know how to remove Stocks properly?
Click to expand...
Click to collapse
The best, foolproof, failsafe way is to remove them from the rom before installing it... and remember that some services are still required, weather you use them or not.
But, if a system app is already installed you need to remove:
the apk from /system/app
the data from /data/data/appname
the cache from /cache/dalvik-cache
Do not remove Accounts & Sync...
Thanks for the answer.
I guess now is a good time to bake my own ROM!
blackadder1000 said:
Thanks for the answer.
I guess now is a good time to bake my own ROM!
Click to expand...
Click to collapse
Yep, that's what I do... see my sig...
I've tried reading through the thread many times already.... Renaming the file, moving it to different locations, going through the terminal. Yet I'm still not able to install the 1.8 recovery. I have no idea how to use the abd shell or what ever it is, I don't even think I have it. Could someone upload a flashable zip with it? Or maybe give me some step by step for it cause I'm lost here and want to flash Vael's rom.
1) Put the recovery image on the root of your sdcard
2) Open a terminal emulator on your phone
3) Type "su" and hit enter
4) Type flash_image recovery /sdcard/<name_of_the_recovery_image>.img and hit enter
Voila! You just updated your recovery image
even easier..
download rom manager from the market, you must be rooted to use, hit flash recovery, then it will flash clockwork recovery, once thats done, scroll to the bottom on the main page of rom manager, then select flash alternate recovery, and it will flash amon 1.8.0. This is the easiest way to do it
It says I don't have permission everytime I try the terminal.
On the plus side the Rom Manager solution was simple and effective. Though I would still like to know why I don't have permission through the terminal and a little more about the problem I was having. It would be nice know what exactly is going on and how to fix these little problems.
crimeslunk said:
It says I don't have permission everytime I try the terminal.
Click to expand...
Click to collapse
Try re-installing the SU app from the market. I've had trouble with it being bundled in roms before, reinstalling it has always fixed my su permission issues.
Reboot your phone after you get the SU app reinstalled.
Maybe this could help for you:
http://forum.xda-developers.com/showthread.php?t=764062&highlight=amon_RA
Followed all the instructions on team venum's page but cannot get this to work, after searching i found a bunch of fixes which none worked. I placed in system/bin folder and after getting su permission i enter "superfreeze" and it gives me a "superfreeze: Permission denied" same with superdefrost. I tried entering the PM commands myself but at the end i get a "df: /mnt/.lfs: Function not implemented" & "df: /mnt/secure/asec: Permission denied" "[1] killed pm disable com.samsung"
Under the hood:
Calk's 2.8.1 rom
Rouge "hitman" 1.5.0 kernel w/ -75mv
v6 supercharger 1000hp option
for me i manually place all the files where they need to go in my rom the bin files in the bin folder and the system files in the system folder and then i run the superfreeze commane in terminal emulator...which it sounds like u have tried...
what i have noticed is i get permission denied on the things my rom doesnt have and the only one that actually goes through is system update
from my understanding...you really dont need superfreeze...not with calk's rom because everything that it freezes is not included in the rom... calk already removed drm, media hub, social hub, and i believe sns...the only thing im not sure he disabled is system updates...i am currently on a different rom which is why i still get system notification updates...and why this script freezes it...
with all that being said i would assume that the reason this is not working is because there is nothing for it to freeze...calk already removed it...you dont need this script not with calk's rom
Disable Updates
If you just want to disable updates go into terminal emulator and type "su" hit enter, this command gives you super user access. then type "noupdates" this should disable all updates. to enable again just type "update". I hope this helps!
K Ron Hubbard said:
If you just want to disable updates go into terminal emulator and type "su" hit enter, this command gives you super user access. then type "noupdates" this should disable all updates. to enable again just type "update". I hope this helps!
Click to expand...
Click to collapse
sweet dude i hope this works because i just noticed that even though i have updates frozen like i can visually see its frozen....i still get update notifications
after running noupdates
Oh, btw if after running no updates you get the ota update message click accept and then let it try to update. It won't be able to so just reboot your phone and you'll never get that message again.
K Ron Hubbard said:
Oh, btw if after running no updates you get the ota update message click accept and then let it try to update. It won't be able to so just reboot your phone and you'll never get that message again.
Click to expand...
Click to collapse
i tried running the noupdates and it errored out said the file didnt exist any suggestions
can i click on the system update message when system updates are frozen...will that make it go away?
That's strange, when I do it it reads "updates from com.Samsung disabled"
And yes once updates are disabled accept the update it will try to install and then fail.after that you just reboot and you'll never receive the update again.
Sent from my SPH-D710 using XDA App
I am using Sandvold's ROM but, starting from some days ago, I encountered a big problem: during startup, my Desire freezes and cannot terminate the boot sequence. Even a nandroid restore is not able to fix it: I have to factory reset the device and, after that, restore works. I haven't changed anything, I don't know what could cause this problem, which is very annoying.
I use the latest version, 0.18.2.1.
What could I do?
I'm using the same version of the ROM and for a while now it has been randomly freezing up and I have to physically remove the battery to be able to restart it, after which it resets the date back to January 1980.
Today it froze up and it is also stuck in a boot loop. Tried wiping the dalvik cache and that didn't work so I'll do the factory reset like you suggest. I don't really want to have to switch back to a GB ROM though as I really like ICS.
Same problem here, the problem started when I rebooted today. Running sandvold 0.18.1.
After some digging I could identify a rough source of the problem, but I'm not Android guru, so it will take somebody more experienced than me to figure this out. Essentially, what happens, is that the system_server goes into a loop and keeps on crashing and getting restarted. I've attached the logcat for the gurus.
I'll try reinstalling and possibly wiping to see if that helps.
Just a quick followup, I had to do a full wipe to get back to working order. Attached is a comparison logcat. I don't really understand how Android boots, so I would kindly ask the more knowledgeable devs to have a quick look. Thanks!
After setting the phone up and rebooting, the problem is back again. Seems like there is a time/date-related bomb in sandvold 0.18.
The same problem at 0.18.2.1.
As much as I found it works (is able to survive reboot) until any soft from Google Play was installed.
After that it has a bootloop on reboot.
Actually I didn't try to install anything from .apk so it can be related to the installation process itself.
Also the same problem has 0.17.1.1 (I don't сheck all versions, just the last ones of majors).
---------- Post added at 09:47 AM ---------- Previous post was at 09:20 AM ----------
0.16.1 - the same problem.
Steps to reproduce:
1. Wipe and install ICS
2. Add google account (at that point the phone still survives a reboot nicely)
3. Install any soft from Play
4. Reboot and enjoy the bootloop
Add: update of an existing soft from Play still causes a bootloop.
dietwice said:
The same problem at 0.18.2.1.
As much as I found it works (is able to survive reboot) until any soft from Google Play was installed.
After that it has a bootloop on reboot.
Click to expand...
Click to collapse
Someone with posting privileges should report this problem in the developer's forum...
roberto.zanasi said:
Someone with posting privileges should report this problem in the developer's forum...
Click to expand...
Click to collapse
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Briefly:
0. Make sure you have adb and phone drivers so you can connect to the phone from computer via "adb shell"
1. Google for Vending-3.8.15.noupdate.norestrictions.apk, download it, rename to Vending.apk, place to sd card
2. Reboot into Recovery mode, use menu to mount "system" and "sdcard"
3. Run "adb shell" on computer
# cd /system/app
# ls
You should see Vending.apk somewhere in the list
This will delete the broken Play Store app
# rm Vending.apk
# rm -r com.android.vending
# rm -r com.android.vending.updater
Settle the correct Play Store app (assuming you placed the downloaded Vending.apk to the root folder of sd card)
# cp /sdcard/Vending.apk /system/app/
4. Clear Dalvik cache
5. Profit!
Now reboot and enjoy the regular booting.
Also you can use the Play Store to install applications.
dietwice said:
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Click to expand...
Click to collapse
Thank you!
I was trying to see if the same method could be performed with the terminal emulator (I haven't installed the sdk, so I don't have adb), when I realized that the superuser app is broken, too. The "su" command in terminal isn't working, as the superuser app stops.
roberto.zanasi said:
Thank you!
I was trying to see if the same method could be performed with the terminal emulator (I haven't installed the sdk, so I don't have adb), when I realized that the superuser app is broken, too. The "su" command in terminal isn't working, as the superuser app stops.
Click to expand...
Click to collapse
I also tried to do this via Terminal, and my "su" is ok.
But it doesn't work.
It looks like commands are being executed successfully, but it in fact they aren't.
Same problem for me...I'll try to fix it following your help!!! I let you know!!
It work, but I'm not able to "install" the edit Play Store downloaded!!! Reboot work, but no Play Store present among my applications!!!
I find com.process.vending in my application list, but it's a grey icon whit the small sd symbol!
I'll try again to uninstall it!
I have the same problem but, when I tried to use the dietwice's method, I found only the Vending.apk on /system/app folder. So I removed it, replaced with the Vending.apk file downloaded and I continued to follow the method and then I rebooted the phone.
The boot loop is present also after this, so I'd like to know if the fact that I didn't found com.android.vending and com.android.vending.updater is a signal that something was wrong even before applying the dietwice's method.
Someone can answer to my question, please?
I have the same problem as freakymonkey. Any Ideas?
gartenriese said:
I have the same problem as freakymonkey. Any Ideas?
Click to expand...
Click to collapse
I have flashed the ROM again from ClockworkMod recovery and, first to make the reboot, I used the dietwice's method and everything went OK! :good:
On the first boot something went wrong with synchronization with my gmail account, but after a reboot (without boot loop) everything worked fine.
I restored everything but sd-ext and it (re)booted fine, so it has something to do with that. Maybe some Google Play Store data is still on there? How can I get rid of these?
EDIT: Ok, I found some files, will try to delete them tomorrow.
Following the main Sandvold discussion, I've FIXED it!!!!
At the end of the procedure, I needed to do "adb uninstall com.android.vending" and then reboot.
I've Play Store back! )))
dietwice said:
SOLVED there:
http://forum.xda-developers.com/showthread.php?t=1355660&page=1661
Briefly:
0. Make sure you have adb and phone drivers so you can connect to the phone from computer via "adb shell"
1. Google for Vending-3.8.15.noupdate.norestrictions.apk, download it, rename to Vending.apk, place to sd card
2. Reboot into Recovery mode, use menu to mount "system" and "sdcard"
3. Run "adb shell" on computer
# cd /system/app
# ls
You should see Vending.apk somewhere in the list
This will delete the broken Play Store app
# rm Vending.apk
# rm -r com.android.vending
# rm -r com.android.vending.updater
Settle the correct Play Store app (assuming you placed the downloaded Vending.apk to the root folder of sd card)
# cp /sdcard/Vending.apk /system/app/
4. Clear Dalvik cache
5. Profit!
Now reboot and enjoy the regular booting.
Also you can use the Play Store to install applications.
Click to expand...
Click to collapse
matteo.rek said:
Following the main Sandvold discussion, I've FIXED it!!!!
At the end of the procedure, I needed to do "adb uninstall com.android.vending" and then reboot.
I've Play Store back! )))
Click to expand...
Click to collapse
I have been unable to get the Play Store back on my HTC Desire. I have followed the above steps exactly but no shortcut appears on the applications screen.
I have tried wiping the dalvik cache, even did a fresh install of ICS Sandvold Rom but no luck.
Could it be because of the default a2sd?
Any assistance much appreciated guys
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