Fire TV Stick 2 (tank) Prerooted Stock Images [5.2.7.3_r1]

Search This thread

Sus_i

Senior Member
Apr 9, 2013
1,608
692
So the events that took place were

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.
 

vprasinos

Senior Member
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)
 

Sus_i

Senior Member
Apr 9, 2013
1,608
692
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...
 

vprasinos

Senior Member
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
 

Sus_i

Senior Member
Apr 9, 2013
1,608
692
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.

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).
 
  • Like
Reactions: dcarvil

0815hoffi

Senior Member
Dec 22, 2019
455
141
Munich
github.com
@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
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=adb
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

Not tested try at your own Risk
 

Attachments

  • TWRPtestDelALandOOBE.zip
    4.4 MB · Views: 65
Last edited:

vprasinos

Senior Member
@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

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
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
 

0815hoffi

Senior Member
Dec 22, 2019
455
141
Munich
github.com
🤷‍♂️ i dont know, maybe you can get it with.

# 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....
 
Last edited:

vprasinos

Senior Member
🤷‍♂️ i dont know, maybe you can get it with.

# 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...
 

0815hoffi

Senior Member
Dec 22, 2019
455
141
Munich
github.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/...
 

0815hoffi

Senior Member
Dec 22, 2019
455
141
Munich
github.com
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
  1. Press and hold the Home button. ...
  2. Release the Home button.
  3. Press the Menu button 9 times.
  4. Remove the batteries from your remote.
 
Last edited:
  • Like
Reactions: Sus_i

vprasinos

Senior Member
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
  1. Press and hold the Home button. ...
  2. Release the Home button.
  3. Press the Menu button 9 times.
  4. Remove the batteries from your remote.
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?
 

0815hoffi

Senior Member
Dec 22, 2019
455
141
Munich
github.com
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....
 
Last edited:

Sus_i

Senior Member
Apr 9, 2013
1,608
692
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

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:

Top Liked Posts