Yes, I think IDME looks good.
Or what you think @Sus_i
Try to hold homebutton more than 1 minute to pair
Yeah, looks good
@vprasinos Edit or delete your serial out of the idme print...
Fire TV Stick 2 (tank) Prerooted Stock Images [5.2.7.3_r1]
- Thread starter rbox
- Start date
Yeah, looks good
@vprasinos Edit or delete your serial out of the idme print...
You're not alone, there are a few reports like this.
Pull the batterys out of the remote and let it alone for a while, over night or so.
Then put fresh batterys in and try to pair it again.
Press the button at least a minute, like hoffi said.
Yes but what I don't get is why my android tv could see the remote and pair with it in a second. So I don't think it's an issue with the remote.
Anyway I will try what you say although I've done it more or less (haven't tried with the batteries out overnight)
I know what you mean.
Someone reported here, that he tried about 100 times to pair the remote but nothing, then he took it to a second fireTVstick and it paired within a second. The remote of the second fireTVstick paired also within seconds with his stick. It's weird...
So I also tried 5.2.7.2. No dice. Tried holding the home button for more than 1 minute. No dice. Lineage or Stock no dice. I am starting to wonder whether flashing ROMs somehow screwed my Bluetooth chip since the whole situation indicates a hardware problem.
In favour of the hardware problem points me the issue that when in Lineage I plug in the OTG cable with a wireless remote that I can control the stick (no back button though but I think this is solvable) I keep getting a screen "Bluetooth service has stopped" and points me to press "ok". When in settings trying to turn bluetooth on, it tries and then nothing. I can't keep Lineage because this dialogue is annoying and pops up every 15 seconds or so.
So how can I check if bluetooth service is running in either lineage or stock? This can happen in Lineage while system is running since I can connect to wifi but not on stock since I must pair first before entering the system.
Thanks
In favour of the hardware problem points me the issue that when in Lineage I plug in the OTG cable with a wireless remote that I can control the stick (no back button though but I think this is solvable) I keep getting a screen "Bluetooth service has stopped" and points me to press "ok". When in settings trying to turn bluetooth on, it tries and then nothing. I can't keep Lineage because this dialogue is annoying and pops up every 15 seconds or so.
So how can I check if bluetooth service is running in either lineage or stock? This can happen in Lineage while system is running since I can connect to wifi but not on stock since I must pair first before entering the system.
Thanks
Maybe you see some errors in logcat, but you need to enable adb debugging for it. Since you cannot complete the setup, only way is via twrp and a build.prop edit.
Something like this worked for the Stock rom on 4k stick and I guess its the same for tank. You need to add/edit this lines in the build.prop file:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
@0815hoffi posted somewhere nice echo commands for use with twrp shell (ask him), but you can also adb pull/push the file and edit it in between...
On the 4k stick its possible to bypass the setup with that commands:
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
I guess that works too for tank, but I've never messed with that on tank. In case it works, you can use your phone / i.e. the fireTV app as a remote (workarround).
@vprasinos
You can try to Flash TWRPtestDelALandOOBE.zip in TWRP.
It will remove Amazon Launcher and install Wolf-Launcher.
It also remove Amazon OOBE to bypass initial setup and
writes
Use my Settings app to enable ADB and pair your remote ( needs root Access )
You can also try to use your TV remote to pair Amazon Remote .
( enable HDMI CEC on your TV and use TV Remote )
after that run:
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
You can try to Flash TWRPtestDelALandOOBE.zip in TWRP.
It will remove Amazon Launcher and install Wolf-Launcher.
It also remove Amazon OOBE to bypass initial setup and
writes
to build.prop.
Use my Settings app to enable ADB and pair your remote ( needs root Access )
You can also try to use your TV remote to pair Amazon Remote .
( enable HDMI CEC on your TV and use TV Remote )
after that run:
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
Last edited:
Thanks so much for this zip, my stick is almost usable again...
So as far as the remote pairing process still no dice. The wolf launcher shows though that bluetooth is enabled after boot (the bluetooth icon stays on next to the wifi icon then dissapears). It seems something else is going on. Could you please let me know where I can find the log file from the debuggable service?
I am using the HDMI CEC to control the stick and while this is a good alternative, when I connect the RKM wifi remote control with the OTG cable, I get no mouse appearing on the screen and no back button - also no home button. Where are the mappings I can configure? Have you done this before?
Thanks again for your efforts
# adb logcat
I think cec can't be remapped, but you can try with buttons remapper .
@Sus_i do you know the location of the logfile....
You got it wrong. I don't want to remap CEC, I want to remap a wifi tv remote control connected with OTG cable to tank. From my experience there should be a file with keymaps that needs to be created or changed.
Also adb logcat produces so much output at realtime that I cannot filter. It's like a 10-20 lines per second...
Logcat command-line tool | Android Developers
Logcat is a command-line tool that dumps a log of system messages, including stack traces when the device throws an error and messages that you have written from your app with the Log class.
developer.android.com
Logcat -c clean
Logcat -d
Buttons remapper should work.
You must edit one of the kl files under
/system/usr/keylayout/Generic.kl
Change the Numbers....
I think you can identify the Nummer by running Logcat and then press the Button on your remote.
But you must find the correct kl file for your remote under system/usr/keylayout/...
I would use constantly saving to PC as txt file
adb logcat > logcat.txt
and watch out with notepad++ during some pairing attempts...
Look like Amazon has released a new Fire OS 5.2.7.7 (662663920) for Tank.
update tank_full_tank 662663720 to 662663920
@vprasinos
I tested it today.
Then had the same Problem, after flash back from lineageos to fireos.
Not possible to pair remote.
This was my solution:
Reset Your Fire TV Remote
update tank_full_tank 662663720 to 662663920
@vprasinos
I tested it today.
Then had the same Problem, after flash back from lineageos to fireos.
Not possible to pair remote.
This was my solution:
Reset Your Fire TV Remote
- Press and hold the Home button. ...
- Release the Home button.
- Press the Menu button 9 times.
- Remove the batteries from your remote.
Last edited:
Hi Sus_i, I did but I got a file of 2,5MB in just 30 secs. I can't make anything out of it. Maybe you could have a look?
Thanks
I tried it with 5.2.7.2 but not successful. Do I need to upgrade to 5.2.7.7 first? Should the stick be unplugged when I perform this or on and looking for the remote?
My Stick was connected at initial pairing screen.
But i have not released the homebutton.
Hold homebutton, press menu 10 - 15 times then my remote was connected.
Strange, but it worked
But maybe you have a other Problem....
But i have not released the homebutton.
Hold homebutton, press menu 10 - 15 times then my remote was connected.
Strange, but it worked
But maybe you have a other Problem....
Last edited:
To reduce logcat you can try my debloat script
I think it comes from the skipped oobe, that you have so much output at logcat...
The output is normal/ok.
I guess the Stick trys always to pair via wifi... while the remote is in BT mode.
Whats about hoffis reset button combination? Works for you?
Last edited:
No it didn't. No combo works for me. How did you find out that my stick tries to pair via wifi?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
22As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
First, you must be unlocked. You can follow the instructions here for making that happen.
If you are first starting, you should first unlock, then install this ROM, and THEN install Magisk for root or any other addons. This rom uses addon.d to preserve Magisk and any other addons, but any system modifications like Magisk, gapps, etc, that you have installed prior to this ROM will NOT be preserved.
If you've already unlocked and installed Magisk, then after installing this ROM you need to reinstall Magisk in TWRP.
Beyond that, Magisk and any other addons will be preserved as you flash newer roms. Consequently, if you would like to remove root, you will need to wipe /system in TWRP prior to installing this ROM. That will prevent it from being restored when installing the ROM.
WARNINGS
- It is extremely important you never reboot after a failure. If recovery is hung, you can use adb shell to run
to restart itCode:
killall recovery - It is also extremely important to never reboot after wiping /system.
- If you wind up bricking, you will most likely have to follow the original unlock instructions again to get it recovered.
Thanks to @k4y0z, @xyz`, and @hwmod for the unlock.
Changelog and Downloads:
- July 4, 2020 - 5.2.7.3_r1 (md5sum: 14c6ccb4ffb26418a84ef7ad6322ab01)
- December 7, 2019 - 5.2.7.2_r3 (md5sum: c66d3128ab8b99f2f05aefed5ef7a527)
- November 10, 2019 - 5.2.7.2_r2 (md5sum: 975b85849203555b924dd7facc96056c)
- October 26, 2019 - 5.2.7.2_r1 (md5sum: f06045a91283f22ba5e2458e20036987)
- September 21, 2019 - 5.2.7.1_r1 (md5sum: dcb2ec970f0f2937ef53bf6f4c824c28)
- June 29, 2019 - 5.2.7.0_r1 (md5sum: ba6ca5312053628d4fc84d34b7c6cfd5)
- March 30, 2019 - 5.2.6.9_r1 (md5sum: ff7669e329244dfebee2968777a37fc7)
- March 17, 2019 - 5.2.6.8_r1 (md5sum: 8b68a96e4d6b908ddc9ee565d2ec2929)
3You can downgrade up to 5.2.6.3 for now on the Fire TV Stick 2 within TWRP. The update will say .bin at the end so in order for you to flash the file successfully, simply rename .bin (not the whole file name) to .zip. Thanks to the Amonet exploit, it patches the image files automatically so there's no need to patch the 5.2.6.8 image file. I'll give you a warning though. Before downgrading to this version, the new Fire TV Stick remote with the power button/volume buttons are incompatible since this is an older version before the new remote functionality even was announced.
Here's the .bin (rename the .bin to .zip)
https://drive.google.com/file/d/1kd0eBgebDUpKoKc8lvlZCFxqr4Gx_biz/view?usp=sharing
Don't worry about TWRP after flashing33 - It is extremely important you never reboot after a failure. If recovery is hung, you can use adb shell to run
