Help my fire tv 2 stuck on alexa screen - Fire TV Q&A, Help & Troubleshooting

Hi i need some help here with my fire tv2 i reset the device and with a first gen remote since i lost the original.now after reset is stuck on alexa screen and remote wont connect no matter what i do.the cec from the tv remote works because the white light blinks when i press a button i attached a pic where is stuck
Anyone can help me fix this.thanks in advance

If rooted.
You can try to move the apk in twrp to /sdcard.
By your own Risk!!!!
com.amazon.tv.oobe under priv-app
and delete under /data/data/com.amazon.tv.oobe
and delete under /data/app/com.amazon.tv.oobe
maybe.
To pair remote and mark Setup Wizard as completet.
adb shell settings put secure install_non_market_apps 1
adb shell settings put global adb_enabled 1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
adb shell am start -n com.amazon.tv.settings.v2/.tv.controllers_bluetooth_devices.ControllersAndBl uetoothActivity

0815hoffi said:
If rooted.
You can try to move the apk in twrp to /sdcard.
By your own Risk!!!!
com.amazon.tv.oobe under priv-app
and delete under /data/data/com.amazon.tv.oobe
and delete under /data/app/com.amazon.tv.oobe
maybe.
To pair remote and mark Setup Wizard as completet.
adb shell settings put secure install_non_market_apps 1
adb shell settings put global adb_enabled 1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
adb shell am start -n com.amazon.tv.settings.v2/.tv.controllers_bluetooth_devices.ControllersAndBl uetoothActivity
Click to expand...
Click to collapse
Thanks for the advice but the box is not rooted any other way or at least root the box on the state it is now?

brigantti said:
Thanks for the advice but the box is not rooted any other way or at least root the box on the state it is now?
Click to expand...
Click to collapse
Hi there,
If it's the FTV2 (not stick) codenamed sloane you could try this https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
Regards!

Rortiz2 said:
Hi there,
If it's the FTV2 (not stick) codenamed sloane you could try this https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
Regards!
Click to expand...
Click to collapse
Try that no go only worked once throw ans error about serial something and never wanted to connect again with pc. I should trash this thing or theres any other option to try.thanks for your help

Related

Fire TV 2 Boot to white Amazon Logo and Stück. what to Do?

I Have a Fire TV BOX Gen 2.
As i install with twrp the Xposed the Power cut down.
After that i only come to the white Amazon Logo and stuck.
I dont come in the recovery.
A adb connection is there.
What can i Do to install the OS and Start it?
Bellany said:
I Have a Fire TV BOX Gen 2.
As i install with twrp the Xposed the Power cut down.
After that i only come to the white Amazon Logo and stuck.
I dont come in the recovery.
A adb connection is there.
What can i Do to install the OS and Start it?
Click to expand...
Click to collapse
adb shell am start -n com.amazon.tv.settings/.tv.FactoryResetActivity
Mmh that give me that answer
"- exec /system/bin/Sh failed: No such file or directory (2) -
Using Port 5555
Bellany said:
Mmh that give me that answer
"- exec /system/bin/Sh failed: No such file or directory (2) -
Using Port 5555
Click to expand...
Click to collapse
Then you can buy a new box now :good:
Is there no way to push the needed files on the Box.
I can Boot in the recovery but Display is Black and LED shrine Orange.
After a while it restart.
I Use the unbrick Tool from the forum here and it work through an but in the white Logo.
I Have feared that i can buy a New fire tv Box.
When i Have a Backup is it possible to install and Start it without shell?
Bellany said:
When i Have a Backup is it possible to install and Start it without shell?
Click to expand...
Click to collapse
If you find someone who provides you with a backup of system and data partitions via TWRP, you can also import it again via TWRP (all you have to do is change the folder name).
But it must be the same Fire TV device such as yours.

1st Gen Fire Tv Stick (Montoya) Blacklisted

Hi, do you guys know if it's possible to bypass amazon account login screen on a blacklisted fire tv stick?
I've managed to skip the update screen using Fire Tv Remote app but now it's stucked asking to login to an amazon account, but it fails when I try.
There is a way to maybe install a custom rom on this stick to make it usable?
Goku.95 said:
Hi, do you guys know if it's possible to bypass amazon account login screen on a blacklisted fire tv stick?
I've managed to skip the update screen using Fire Tv Remote app but now it's stucked asking to login to an amazon account, but it fails when I try.
There is a way to maybe install a custom rom on this stick to make it usable?
Click to expand...
Click to collapse
Unlock it first, then disable obbe and install custom launcher.
https://forum.xda-developers.com/fir...antis-t3978459
After rooting do the following
From recovery shell
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
adb shell settings put secure install_non_market_apps 1
adb shell settings put global adb_enabled 1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
pm disable com.amazon.tv.oobe
adb install anyTVLauncher.apk
ranjeet choudhary said:
Unlock it first, then disable obbe and install custom launcher.
https://forum.xda-developers.com/fir...antis-t3978459
After rooting do the following
From recovery shell
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
adb shell settings put secure install_non_market_apps 1
adb shell settings put global adb_enabled 1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
pm disable com.amazon.tv.oobe
adb install anyTVLauncher.apk
Click to expand...
Click to collapse
Thanks for reply. This guide you linked is for unlocking the 4K version of the stick, mine is the 1st gen. I've take it apart and took a photo of the board. I see some difference between my board and the one present in the guide.
Can I use that guide to unlock my 1st gen stick?
https://imgur.com/0c02HFU
Goku.95 said:
Thanks for reply. This guide you linked is for unlocking the 4K version of the stick, mine is the 1st gen. I've take it apart and took a photo of the board. I see some difference between my board and the one present in the guide.
Can I use that guide to unlock my 1st gen stick?
https://imgur.com/0c02HFU
Click to expand...
Click to collapse
No, you can't.
But your picture shows a 'tank' device (i.e. the 2gen stick), not the old 1gen montoya stick...
You can use that guide to root/unlock it. :good:

[ADB][GUIDE]Swap back/contextual menu keys for gesture nav bar

For those wanting to have the back button on the right side (where it naturally belongs ), it's simple with ADB:
Like stock spacing:
Code:
adb shell settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
or
adb shell settings put secure sysui_nav_bar 'space[0.25WC],contextual;home;back,space[0.25WC]'
More comfy:
Code:
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
or
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
To return back to stock:
Code:
adb shell settings delete secure sysui_nav_bar
If i try this command
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
this is the output. How i can solve it?
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
P.S. Now it works. The solution is to use this command:
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
" to '
Thanks.
bruceas said:
If i try this command
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
this is the output. How i can solve it?
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
P.S. Now it works. The solution is to use this command:
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
" to '
Thanks.
Click to expand...
Click to collapse
Thanks for the update, it seems to be related to the Windows regional settings on a PC (?). On my personal PC it works with double quotes ", on my work PC with single '. I've update the instructions.
Edit: if you split command into two, it works with double quotes as well
1. adb shell
2. settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
_mysiak_ said:
For those wanting to have the back button on the right side (where it naturally belongs ), it's simple with ADB:
Like stock spacing:
Code:
adb shell settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
or
adb shell settings put secure sysui_nav_bar 'space[0.25WC],contextual;home;back,space[0.25WC]'
More comfy:
Code:
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
or
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
To return back to stock:
Code:
adb shell settings delete secure sysui_nav_bar
Click to expand...
Click to collapse
hello, sorry for this "stupid question" but, how to use ADB? where can i find it to enter those commands?
i've installed the usb driver, unlocked oem, and activated usb debug on the phone. but i don't know what to do after...
arjo656 said:
hello, sorry for this "stupid question" but, how to use ADB? where can i find it to enter those commands?
i've installed the usb driver, unlocked oem, and activated usb debug on the phone. but i don't know what to do after...
Click to expand...
Click to collapse
https://www.xda-developers.com/quickly-install-adb/
https://www.xda-developers.com/what-is-adb/
i followed the tuto, but when i enter "adb devices" it says " the term adb is not know as a .exe ......."
arjo656 said:
i followed the tuto, but when i enter "adb devices" it says " the term adb is not know as a .exe ......."
Click to expand...
Click to collapse
Either put adb.exe to Windows PATH, or you must change directory before running adb (for example "cd c:/platform-tools").
_mysiak_ said:
Either put adb.exe to Windows PATH, or you must change directory before running adb (for example "cd c:/platform-tools").
Click to expand...
Click to collapse
ok thanks, now it works with the .exe in win path, i've got the pop-up asking to allow usb debug, but when i enter any command , i've got this
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
i've tried the 4 differents lines normal and confy
arjo656 said:
ok thanks, now it works with the .exe in win path, i've got the pop-up asking to allow usb debug, but when i enter any command , i've got this
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
i've tried the 4 differents lines normal and confy
Click to expand...
Click to collapse
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
_mysiak_ said:
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
Click to expand...
Click to collapse
WORKS!!!!!! :good:
thanks!!
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
arjo656 said:
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
Click to expand...
Click to collapse
Dont kill app, they will use more power when relaunching them, they use almost no power when in background.
arjo656 said:
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
Click to expand...
Click to collapse
No idea, I wasn't even aware of this button. As antoine62 said, it's totally useless. If you need to kill an app, just swipe it away from recent menu (or click on details and "force stop" if the app works with background service).
Sorry, my translation may not have been clear, in french we have the "effacer tout" (clear all) button on the left of the recently used apps, i took a screenshot.
And as a right hand writer, i find it useless to swipe all the list to the left before accessing this button, i would like to put it directly on the right of the list so when i swipe up from the bottom, i Can clear the list immediatly.
arjo656 said:
Sorry, my translation may not have been clear, in french we have the "effacer tout" (clear all) button on the left of the recently used apps, i took a screenshot.
And as a right hand writer, i find it useless to swipe all the list to the left before accessing this button, i would like to put it directly on the right of the list so when i swipe up from the bottom, i Can clear the list immediatly.
Click to expand...
Click to collapse
That button should not be really used at all, it just kills all cached apps. Stock Android is pretty good at memory management. There is really no point in force killing all the apps manually.
_mysiak_ said:
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
Click to expand...
Click to collapse
hello mysiak, i updated to android 10 yesterday against my will (see other post), i tried to do the same procedure, but it doesn't work anymore, any idea?
i did
./adb shell
settings put secure sysui_nav_bar "space,contextual;home;back,space"
exit
arjo656 said:
hello mysiak, i updated to android 10 yesterday against my will (see other post), i tried to do the same procedure, but it doesn't work anymore, any idea?
i did
./adb shell
settings put secure sysui_nav_bar "space,contextual;home;back,space"
exit
Click to expand...
Click to collapse
I don't have Android 10 yet and it seems that Google killed this feature (why oh why). I found this app which might help, give it a try and let us know. https://play.google.com/store/apps/details?id=nu.nav.bar
Hi,
Today i updated my phone to android 10 and I have same problem as arjo656. I tried app that you posted here, but now I have app's buttons and aslo original android's buttons. It looks weird. Didn't you find any way how to change it by adb again?
Hi, I followed this guide https://forum.xda-developers.com/mi-a3/how-to/button-nav-hack-t3997527 to get back the three buttons (as in the previous versions of Android), and wanted to combine the two "hacks" to get back the 3 nav bar buttons but with the back button on the right, and the contextual on the left, but when I use your command via adb, the contextual button disappears, even tho in the command it's still there, I attach two pics to understand better
lowmanager said:
Hi,
Today i updated my phone to android 10 and I have same problem as arjo656. I tried app that you posted here, but now I have app's buttons and aslo original android's buttons. It looks weird. Didn't you find any way how to change it by adb again?
Click to expand...
Click to collapse
Nope, Google removed the interface for navbar customization in Android 10. I just keep stock 2 buttons navbar and use "Edge gestures" app for one hand operation (it's even on sale right now, grab it while you can).
Phil_gloves said:
Hi, I followed this guide https://forum.xda-developers.com/mi-a3/how-to/button-nav-hack-t3997527 to get back the three buttons (as in the previous versions of Android), and wanted to combine the two "hacks" to get back the 3 nav bar buttons but with the back button on the right, and the contextual on the left, but when I use your command via adb, the contextual button disappears, even tho in the command it's still there, I attach two pics to understand better
Click to expand...
Click to collapse
For 3 buttons navbar replace "contextual" with "recent". For example:
Code:
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
Edit: if you want to keep "contextual" button as well, this might work (can't test it as I'm on Android 10 already):
Code:
adb shell settings put secure sysui_nav_bar "contextual;space,recent;home;back,space"

ADB debugging not working on reboot

I am running lineageOS on a rooted firestick. I am using ADB on the Firestick to control it via Homeassistant. The problem is that the adb debugging does not automatically work on reboot. Everytime i reboot i have to manually go to the menu turn off the ADB debugging and then turn in back on. After doing this i am able to reconnect adb via network (i.e, on homeassistant).
I want to ask is there any way i can use a script to automatically do this on restart of firestick. I have tried creating a script in init.d with the following contents but it doesn't seem to work.
adb tcpip 5555
I have added the following line to build.prop but this doesn't seem to work too
service.adb.tcp.port=5555
On restart the adb debugging is on in the developer tools but somehow it doesn't connect (either to Homeassistant or to my laptop), what seems to make it work is toggling it off and then back on.
Have you tried persist, so that the setting sticks between reboots?
Code:
ADB shell setprop persist.adb.tcp.port 5555
Just tried it. Still not working after reboot.
I there any command i can use to toggle the adb debugging via a startup script or crontab?
symbiansucks said:
Just tried it. Still not working after reboot.
I there any command i can use to toggle the adb debugging via a startup script or crontab?
Click to expand...
Click to collapse
Be sure you are running the above command as root user. Type su at the shell prompt, then type whoami to confirm you are root.
I guess you could make a script to run the following on each boot if the above doesn't work:
Code:
settings put global adb_enabled 1
setprop service.adb.tcp.port 5555
stop adbd
start adbd
exit 0
But I don't think this should be necessary.
Finnzz said:
Be sure you are running the above command as root user. Type su at the shell prompt, then type whoami to confirm you are root.
I guess you could make a script to run the following on each boot if the above doesn't work:
Code:
settings put global adb_enabled 1
setprop service.adb.tcp.port 5555
stop adbd
start adbd
exit 0
But I don't think this should be necessary.
Click to expand...
Click to collapse
Thanks. yes the command was run as root. Can i ask you one more thing, whats the best place to put the startup scripts in? I have tried init.d/ directory but the scripts don't get loaded from there i believe?
I have set permissions to chmod 755 for the script.
You can follow this guide,
Android (LineageOS 16) Execute Script on Start Up | sqall's blog
but it seems like there should be a much easier way to make ADB tcpip persist between reboots. I don't want to steer you wrong. @Sus_i would know better, he uses your build of LineageOS, and may have a cleaner solution.

FireTV 2nd Generation looping on updating to latest software screen

Hi all,
Absolutely frustrated by my 2nd Gen FireTV 4K - just been stuck on the installing the latest software screen and gets to the end to loop to a white Amazon logo for about a second to back to installing. Been doing this for ages
1. Tried to ADB but can’t connect - the IP address only stays up for a while plus ADB debugging maybe off…
2. Tried the keyboard method, Alt I print screen, doesn’t work.
3. Changed HDMI cables and ports, no idea how that makes a difference
4. Restarted my router, again don’t know how that makes a difference
5. Held the various buttons on remote and that doesn’t work either.
Absolutely ruined my Sunday afternoon
Trying all this, anybody with an idea of what I could do next would be great as it just keeps getting stuck in this install, restarts itself and then repeats again!
Picture attached. Usually takes about 2-4 mins, then restarts for a short while to this again and starts again, freezes , then suddenly completes.
You could try unlocking it, and using TWRP to reflash it
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
If you don't want to go down that road, you can use the command adb wait-for-device to wait until ADB is ready and then automatically send a command. For example:
adb wait-for-device && adb logcat > logcat.txt
This will automatically dump logcat as soon as adb becomes available. Then you can look through the log for whatever is causing the problem etc.
I'm not sure if the Android factory reset works on FireTV, you can try
adb wait-for-device && adb shell "recovery --wipe_data"
Or
adb wait-for-device && adb shell "input keyevent KEYCODE_FACTORY_RESET"
Finnzz said:
You could try unlocking it, and using TWRP to reflash it
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
If you don't want to go down that road, you can use the command adb wait-for-device to wait until ADB is ready and then automatically send a command. For example:
adb wait-for-device && adb logcat > logcat.txt
This will automatically dump logcat as soon as adb becomes available. Then you can look through the log for whatever is causing the problem etc.
I'm not sure if the Android factory reset works on FireTV, you can try
adb wait-for-device && adb shell "recovery --wipe_data"
Or
adb wait-for-device && adb shell "input keyevent KEYCODE_FACTORY_RESET"
Click to expand...
Click to collapse
Hi Finzz,
Thanks for your reply, wasn’t expecting anyone to get back to me on this to be honest!
I tried sudo ADB connect with the ip address that shows up on ipconfig /getethaddr but didn’t work. It seems the continuous reboots also knocks out the connection.
I don’t think ADB was enabled on the firetv so I can’t ADB connect anyway…
I’ll check the guide you posted now, thanks
Regards,
Jesal
Finnzz said:
You could try unlocking it, and using TWRP to reflash it
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
If you don't want to go down that road, you can use the command adb wait-for-device to wait until ADB is ready and then automatically send a command. For example:
adb wait-for-device && adb logcat > logcat.txt
This will automatically dump logcat as soon as adb becomes available. Then you can look through the log for whatever is causing the problem etc.
I'm not sure if the Android factory reset works on FireTV, you can try
adb wait-for-device && adb shell "recovery --wipe_data"
Or
adb wait-for-device && adb shell "input keyevent KEYCODE_FACTORY_RESET"
Click to expand...
Click to collapse
I have standard firetv firmware, will
The TRWP work and unbrick work? Doubt I have a usb cable A-A too. Will USB C to
A work?
jespat88 said:
I have standard firetv firmware, will
The TRWP work and unbrick work? Doubt I have a usb cable A-A too. Will USB C to
A work?
Click to expand...
Click to collapse
Oh ok, I thought you might be using a USB cable to make your ADB connection attempt. The device must be getting pretty far in the boot process if it's even making a momentary WiFi connection.
I don't think the method used in that link can be blocked by Amazon. It's made possible by a simple hardware short.
You would be using this to load TWRP from a computer onto your device, to allow you to reflash it, and wipe data if needed. It would work with the stock Amazon firmware.
You will need to buy/obtain that USB A to USB A cable for your computer to communicate with the FireTV. They are a few bucks on Amazon:
https://www.amazon.com/USB3-0-VCZHS-Double-Enclosures-Laptop/dp/B089ZZW425/
You could probably even get one for cheaper if you search around on Amazon/eBay.

Categories

Resources