Develop Bugs

[Q] How exactly do I flash amon 1.8 recovery?

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

[help]rooting my mytouch slide

after i myroot in the cmd i type adb shell and i get a # instead of a $ and i tried to cd /sqlite_stmt_journals but to no avail and all the rest never seems to work its good until this point

Deion123 said:
after i myroot in the cmd i type adb shell and i get a # instead of a $ and i tried to cd /sqlite_stmt_journals but to no avail and all the rest never seems to work its good until this point
Click to expand...
Click to collapse
I don't know about your second issue, but if you type adb shell and you get a #, that means you are in shell as root. Meaning you have root permissions. $ means regular user, # means superuser, in linux. Are you sure you aren't rooted?

i just found out that im rooted but now i need help where are the google addons and where can i access the recovery menu im such a noob

Deion123 said:
i just found out that im rooted but now i need help where are the google addons and where can i access the recovery menu im such a noob
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/index.php?title=Latest_Version
That has everything you need for gapps/cm6,
to get to recovery, download ROM manager from the market, then tap flash clockworkmod recovery, then reboot into recovery. You can also just copy the update.zip for clockwork recovery to your sd card and then boot into the stock recovery by holding vol down + power and selecting reboot recovery, and then flash update.zip.

thank you for your help now is there anyway i can load music on it ormake a music file????

Deion123 said:
thank you for your help now is there anyway i can load music on it ormake a music file????
Click to expand...
Click to collapse
Yeah, just copy music from your computer to somewhere on your sd card, the build in music app should find it.

[Q] Custom Recovery Question

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!

Software Update Loop Bricked FireTV

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

Nexus 5x SuperSu Update Faliure

Sorry I have so many problems, but this forum has been successful at fixing them, so I need a little more help if that's fine.
When I try to update SuperSu normally, it says, "Installation failed ! Please reboot and try again" with no wording left out.
It also has this other option attempts to load me into TWRP or CWM depending on my device from this button (TWRP/CWM). It also asks me if I want to install files manually.
I will not do this part without specific instructions, but I've seen some very detailed forums so links will be good to.
Anything helps, and enjoy your day

Easiest way to install superuser is to download chainfires latest beta su 2.5.2
http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
than flash it from twrp (recovery)
Sent from my Nexus 5X using Tapatalk

The_Automator said:
Easiest way to install superuser is to download chainfires latest beta su 2.5.2
http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
than flash it from twrp (recovery)
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I saw that link before, but I need to know the steps. Can you lay them out like you did before if that's fine? . By the way you seem really talented at fixing phones and helping people with phone problems.

I believe it has been covered in a couple different locations previously but dont mind helping and ill assume you have already tried the search feature before starting a new thread.
1)You should already have enabled usb debugging and selected the box for oem unlocking in developer options this will allow you to flash the custom recovery.
2)By default the data partition of android is encrypted to disable this first go to wipe>Format Data> Type yes ***this will delete all of your data if you have pictures or something id save it to the cloud or pc first***
3)boot your phone reset up your google account and download su from the link above
4) Reboot into custom recovery (twrp)
5)Press install and navigate to your download folder and select the su 2.5.2 zip swipe across your screen and it should flash the zip
Reboot your phone and you should have su installed.

The_Automator said:
I believe it has been covered in a couple different locations previously but dont mind helping and ill assume you have already tried the search feature before starting a new thread.
1)You should already have enabled usb debugging and selected the box for oem unlocking in developer options this will allow you to flash the custom recovery.
2)By default the data partition of android is encrypted to disable this first go to wipe>Format Data> Type yes ***this will delete all of your data if you have pictures or something id save it to the cloud or pc first***
3)boot your phone reset up your google account and download su from the link above
4) Reboot into custom recovery (twrp)
5)Press install and navigate to your download folder and select the su 2.5.2 zip swipe across your screen and it should flash the zip
Reboot your phone and you should have su installed.
Click to expand...
Click to collapse
I indeed did use the search feature but there instructions were pretty much just giving you the files. Thanks for the help

RingPvP said:
I indeed did use the search feature but there instructions were pretty much just giving you the files. Thanks for the help
Click to expand...
Click to collapse
No problem happy to help you can also install zip files using adb sideload which is my go to method.
Download the zip on a computer place it in the same folder as your fastboot.exe and adb.exe
Reboot your phone into twrp click advanced and then sideload swipe across the bottom to start sideloading.
On your computer in the fasboot folder (platform-tools subdirectory of the sdk) press shift and right click the background of the folder select open command window here
In the command prompt type adb sideload superuser.zip or whatever zip you want to install.
Can be useful if you are changing roms or doing other stuff that will wipe your data partition
Sent from my Nexus 5X using Tapatalk

The_Automator said:
No problem happy to help you can also install zip files using adb sideload which is my go to method.
Download the zip on a computer place it in the same folder as your fastboot.exe and adb.exe
Reboot your phone into twrp click advanced and then sideload swipe across the bottom to start sideloading.
On your computer in the fasboot folder (platform-tools subdirectory of the sdk) press shift and right click the background of the folder select open command window here
In the command prompt type adb sideload superuser.zip or whatever zip you want to install.
Can be useful if you are changing roms or doing other stuff that will wipe your data partition
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks