Related
Hello there,
I have recently installed TomTom 3.01 with GPS update 3.07 and now I cannot connect my BT headset Bluetrek G2 anymore. Before the TomTom install everything worked fine.
I can still pair the headset using the setup wizard, but when it comes to finally connect it I get the error message "Failed to connect".
After hard reset and restore of system before TomTom install all works fine again. Seems to me TomTom somehow blocks the headset-profile.
I spent days reading through all the posts here, but couldn't find any answers.
If there's anyone out there who can help, any tips would be greatly appreciated.
Thanx
[/b]
You could try installing bttools.
Thanx for replying. I have installed bttools from this link http://bluetooth.i-networx.de/index_e.html , but it doesn't seem to do anything. It just appears on the today screen, but none of the buttons has any function. My guess is it only works when the MS-Bluetooth stack is installed (like on the Himalaya), which by default isn't installed on the Blue-Angle. But thanks for trying...
Cheers
Has anyone sucessfully installed MS Voice Command 1.5 with the New ROM (Jasjar ROM 1.30.68 WWE, Radio 1.09.00, extROM 1.30.153)? It installs but when I run it I get an error message and it disables itself. Any suggestions?
Thanks,
Sven
I have VC working fine with the new ROM - installed and worked just the same as before, so does the reg hack to enable operation via BT headset...........maybe if you try it again (re-install?) it will work
works fine on mine.
@sbatxda I had the same issue, VC would just close itself...what worked was a simple soft reset, I only figured this out after pulling out all my nose hair but hey it's never to late to learn Just do a soft reset an it should work as normal.
sorry, i assumed a soft reset was a foregone obvious solution and would be done automatically by anybody that has any knowledge of any microsoft system.
if in doubt, reset
youmeus: it worked ok on the new ROM then? I'll try to upgrade soon I guess then..
V
MS Voice Command 1.5
Thanks for the suggestions. I have made the register modification to get it to work with my BT headset and I have made multiple soft resets. I have some issue with the Voice Command install in that I have to first install the 1.0 version and then the 1.5 version; if I go directly to 1.5 the install tells me that there is no previous version and stops. This may create some issue, but this is also how I did it with the previous ROM version. I'll try a re-install again.
Regard,
Sven
@vijay555, yes I tried it again and it works ok now...but this new rom has a few issues that I am not comfortable with so I am going back to old rom once I get home later
@sbatxda, the better way to install VC is vis the cab file...just look for the cab file on your desktop eg C:\Program Files\activesyne\voice command\...etc and drag the cab to your PPC.
MS Voice Command 1.5 installation
Thanks youmeus,
Installing the .cab worked better.
I'm now having difficulties installing the .cab file with my ISP settings. It will not install on my device or storage card. This worked fine with the old ROM.
Ideas anyone?
Regards,
Sven
BT hack reg
@adesonic
installed and worked just the same as before, so does the reg hack to enable operation via BT headset...
Click to expand...
Click to collapse
please tell me the issue about this or send a link in a thread. VC 1.5 doesn't work with my BT headset.
DTR - try this - copied from another thread on here
MS Voice Command activation from BT headset
Now this one is sweet and makes the JASJAR the daddy for voice commands.
Install Voice Command to the default location.
Fire up a registry editor
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
Now, when you press your BT headset connect button, MS Voice command will fire up and take commands through the headset. It's reponses will be played through the headset too.
regs
sonic
@adesonic
oh, thatone I shure did try. But, having a Magician, I obviously had no success.
Maybe the fault is with the i-tech headset, which probably doesn't support connection.
I also had no luck with streaming audio to that headset, which some posts in other threads say is possible.
Thanx neverteless for your fast reply.
regards
Why haven't MS upgraded this software to a proper WM5 version yet?
OR have they and I haven't been paying attention?
Question: Earlier I and others have had problems with showing of contacts displaying a blank page.. Are you guys able to show contacts using Voice Command properly?
@eman, you have to add one the files form the VGA hack in your windows folder for VC to display contacts...I can't remember the name of the file so do a search on the board!
Great to know there's a solution.
Installing VC now
with the previous ROM there was the issue where it didn't work in laptop mode with the lid closed. Does VC work in that mode now, or are you guys using it in portrait mode?
It would be great if it did.
the file needed is outres.96.dll
no VC doesnt work when the clam is closed.
even on the latest release.
Hi all. I have a HTC Desire rooted with unrevoked3. Phone runs sweet as except bluetooth. I can enable bluetooth graphically (the checkbox ticks and after some time the bluetooth logo appears on the status bar). However, if I cannot chance the device name, make the device discoverable or scan for devices. Nothing happens.
The kernel gives errors such as:
Code:
<3>[ 71.632263] hci_cmd_task: hci0 command tx timeout
I am currently running CyanogenMod 7.1 RC1, but this problem exists if I run other ROMs too. I've gone back to the HTC RUU to verify it's not hardware and bluetooth works fine there. So I dug about some more.
There are many posts relating to bluetooth problems on rooted Desires, but none appear to be line mine - Still, I tried some recommended solutions anyway. The issue of a 'USB brick' sounded a possible cause, but I followed through the solution (http://forum.xda-developers.com/showthread.php?t=691639) and got no further. I am sceptical as to if I modified the misc.img file correctly, as I don't know how to find my current ROM version (it's not under About The Phone).
I would really appreciate any help. I've been nosing about looking in '/sys/devices/virtual/bluetooth/hci0/' were the bluetooth stuff resides. See here: http://forum.cyanogenmod.com/topic/23500-bluetooth-lack-of-functionality/#entry217041 But this isn't just a Cyanogen problem. The only way I can restore bluetooth functionality is by letting HBOOT re-flash from PB99IMG.
I am not an expert in this, but I have read quite a lot and have a good idea of what's going on, but this has stumped me. I am very fluent in Linux. Any help you can give would be greatly received.
EDIT:
I notice that from the stock HTC ROM, I can root the device with unrevoked3 and Bluetooth still works. Then as soon as I do anything with ClockworkMod (version 2.5.0.7) it appears to break Bluetooth.
I dumped the misc partition from the stock HTC ROM while Bluetooth was working, and tried to reflash that to the misc partition once Bluetooth broke in Cyanogen - It didn't work: using flash_image on the rooted phone, it appears to work... it doesn't actively fail... it doesn't say anything, just returns (exit 0). Using fastboot flash misc mtd0.img results in checksum errors, etc and does actively fail.
Any advice would be greatly received please?!
Kind Regards,
George Smart.
If you are trying to use your OTG USB as music or video library in Marmshallow or Nougat, but your media player doesn't recognize the content of your usb, then follow these instructions.
Download the terminal from store in case you don't have one. Root is required. You only have to do this once:
Simply open terminal and type:
Code:
su
sm set-force-adoptable true
Now just insert OTG USB and it will be immediately recognized by music players and all other apps.
Additional info:
Do not safely eject the usb, in my case doing this I noticed some bugs, just directly unplug the otg.
My phone is LG G2 d802 and the rom is CM13 snapshot 20161220.
It Works, than you!
I tested in Lineage OS 14.
I want to try this, but I am using Nougat now. So, just in case it didn't work, how should I revert the code above? I am new to this thing actually. Thanks!
geraldalcos said:
I want to try this, but I am using Nougat now. So, just in case it didn't work, how should I revert the code above? I am new to this thing actually. Thanks!
Click to expand...
Click to collapse
Change "true" to "false".
I'm using jetAudio plus, everything works great, thanks!
(Nexus 5, 7.1.2)
I am not sure what happened or why, but this has suddenly stopped working for me. ?
Edit: Appears I might have been a bit hasty, looks to be working just fine now. Only thing is, there's no notification for the connected drive. It's a tiny little inconvenience, I know, but I prefer it was there. Any help would be much appreciated.
It's been a while since I thank you someone from Xda and all I can you are a genius!
I have been looking for a solution for days now for my nexus tablet car project. I bought a Tpms from China (I am about to return it actually) and it is not working due to some stock Rom external restrictions for Android 6.1 even I am rooted.
Again! Thanks to you Buddy!
Does the "sm set-force-adoptable true" setting change how sdcards are managed?
Do SD cards and USB sticks become readable only from the Android device?
Are SD cards and USB sticks formatted / deleted when connected to Android?
Sorry for the perhaps stupid questions, but until now I was sure that an adoptable memory was not readable by other devices.
Does this trick still work in Android 9?
I have this problem in Android 9, on a PX6 unit.
I cannot use external USB SSD disk, or USB stick for my MP3 archive.
Can anyone point to a solution for this that does not require rooting, or can anyone point to a very simple solution for rooting this device?
Very thankful if anyone knows.
I tried the command "sm set-force-adoptable true" and it will not work, it does not find the command SM.
Als the SU command will not run. I guess because i am not rooted.
Any suggestions here?
thanks!
/GF
Until yesterday I had a functional FTV stick, now paperweight.
I installed an application for watching TV. The application installed ok but, when launched, told me it needs the Google Play services.
So I went and installed the Google Play services, which also installed ok.
I relaunched the application, which this time just froze, and I could not back out of it. So I rebooted the FTV, with the result that now it starts booting, gets to the white Amazon logo with music and from there it boots again, and again in an infinite loop.
I tried powering it from an external supply - no change. I tried the Right button/Back button remote combination - no change. I did NOT unlock the bootloader (did not expect such a problem and was not aware that it is doable); I do not have ADB enabled.
I read that there is a way to unbrick using a USB keyboard combination but I only have one micro-USB port on the stick which is used for power supply, so I don't see how I can connect a keyboard.
Any suggestions how to proceed from here will be most welcome. Thanks in advance.
Hi there,
Same happened to me. I received a brand new 4k Stick.. it worked like a charm for 20 min, I installed a few thing, and then when I rebooted it started the loop with the amazon logo. youtube.com/watch?v=zK5a-2MILOU
I dont know what to do; my FireStick is not rooted so I cant fastboot or adb it; I cant enter anywhere!
I dont have any OTG to connect a keyboard, neither a keyboard. I have been traying to solve with a thousand of ways which i read on this forum, but nothing fixed it.
I have 2 options, and i dont know if they will work:
1.- Buy o make a fastboot cable. I dont know if it works for Firestick, and I dont know what to do if it works! Should I install a new rom? Which one?!
2.- Buy a OTG and a keyboard to try to enter to the recovery mode. But if I actually enter in there, would I be able to fix it?
What do you guys think?
Thanks!!
ddoouubbllee said:
Hi there,
Same happened to me. I received a brand new 4k Stick.. it worked like a charm for 20 min, I installed a few thing, and then when I rebooted it started the loop with the amazon logo. youtube.com/watch?v=zK5a-2MILOU
I dont know what to do; my FireStick is not rooted so I cant fastboot or adb it; I cant enter anywhere!
I dont have any OTG to connect a keyboard, neither a keyboard. I have been traying to solve with a thousand of ways which i read on this forum, but nothing fixed it.
I have 2 options, and i dont know if they will work:
1.- Buy o make a fastboot cable. I dont know if it works for Firestick, and I dont know what to do if it works! Should I install a new rom? Which one?!
2.- Buy a OTG and a keyboard to try to enter to the recovery mode. But if I actually enter in there, would I be able to fix it?
What do you guys think?
Thanks!!
Click to expand...
Click to collapse
I contacted Amazon customer support (via online chat) and told them the story. In spite of me not being able to offer any proof of purchase (all went to the bin as the FTV worked so well - until it didn't anymore) they offered me the choice between a 40% discount on a new unit, or a free replacement they could only ship to an US address. As I live in Europe I don't have such an address BUT - I found a company that will receive a shipment on my behalf at an US address and will forward it to my European address for the shipping cost plus a small fee. So I chose this option and I just got an email that the replacement was shipped to the US address.
So, bottom line, I will end up with a new unit (which first thing I will open up all the possible ways - unlock bootloader, enable ADB etc.) and, if ever I will succeed to salvage the old one, I will have a spare for free
Anyway, kudos to Amazon for a great customer support experience.
avidav said:
I contacted Amazon customer support (via online chat) and told them the story. In spite of me not being able to offer any proof of purchase (all went to the bin as the FTV worked so well - until it didn't anymore) they offered me the choice between a 40% discount on a new unit, or a free replacement they could only ship to an US address. As I live in Europe I don't have such an address BUT - I found a company that will receive a shipment on my behalf at an US address and will forward it to my European address for the shipping cost plus a small fee. So I chose this option and I just got an email that the replacement was shipped to the US address.
So, bottom line, I will end up with a new unit (which first thing I will open up all the possible ways - unlock bootloader, enable ADB etc.) and, if ever I will succeed to salvage the old one, I will have a spare for free
Anyway, kudos to Amazon for a great customer support experience.
Click to expand...
Click to collapse
Lucky you; i live in Chile and they dont want to send me anything. I need to fix the unit I have..
If anybody can help me ill be very gratefull!
Same with me, and i have fix as below video, please find fix description, i hope also you will fix it.
https://youtu.be/R7EA_VLDxZ4
erolmutlu said:
Same with me, and i have fix as below video, please find fix description, i hope also you will fix it.
https://youtu.be/R7EA_VLDxZ4
Click to expand...
Click to collapse
Does not work. ADB does not find any device attached.
Does anyone have any news on how to solve the problem? please help
avidav said:
Does not work. ADB does not find any device attached.
Click to expand...
Click to collapse
hi! I have tried to adb link my fire stick when I got the stick from amazon,but failed.Tried thousands times,then I found something that may help:
Unplug the usb port from the amazon charger,plug it directly into the usb hole on PC.
Open the adb window on PC,may be at this time the adb can find the device.
Maybe you could use the adb on PC connect another android phone at first,if it succeed so you will know the adb software on PC is all right.
I found there is something wrong with the last version of the adb software:"the port missing.....".You may try an old version of adb.
Good Luck!
I've tried USB Keyboard <ALT> + <Print> + <i> , also + <Shift> and + <Ctrl>, several combinations / orders.
Seems not to work anymore - keeps looping
After Looping about half a day 4K came up once.
You have to do a factory reset then, otherwise another half day on next boot up.
Network was USB-Hub - USB-Ethernet, don't know if important.
I have to admin that patient i the best way to solve that problem.
It helped me also. I wait for about 24h and it boot up to system and now i'm restored it to default and all works fine
abdel85 said:
I have to admin that patient i the best way to solve that problem.
It helped me also. I wait for about 24h and it boot up to system and now i'm restored it to default and all works fine
Click to expand...
Click to collapse
Did you keep your TV POWER ON during the bootloop process?
Fell into it and fixed it twice
Hey guys , I had this problem twice already because of trying to install google services on it and i was searching for hours and hours and i came to this thread and i had no choice but try the solution offered by @iwl in the first time ,because i had never authorised any computer to connect to this stick before, i didnt even knew about it, so i left the FireStick 4K connected to TV and its adapter normally and let it loop as much as it wanted, i actually went to bed and on the next day it was back on, i did a mistake a didnt reset it immediately so later on i had another half a day of bootlooping and when it was up again after a few hours i reset it and of course all apps were lost , not a big deal as long as my FS is back to life.
Now is the nice part that made any bootloop later on a piece of cake, i went immediately and connected the stick to to Minimal ADB via WIFI so i could authorise the computer to connect to it( it is a one time thing, there are some videos about how to do that from which i also learnt the method).
The second time i was prepared so i took the risk and wanted to install Play services in order to get some other app work and not for the sake of google, so i fell into the loop, disconnected the Stick from TV and connected it with the USB cable only to my computer which i authorised before on this specific stick, ran Minimal ADB and fastboot and ran the following commands in the shell (use commands between the " ")
"adb kill-server"
"adb start-server"
to make sure that i am connected to the stick "adb devices"
-you will get list of connected devices
Then unistall the nasty app , in my case it was google so it used these commands
"adb uninstall com.google.android.gms"
in case you have a problem with another app , you could check the app's name with the following command "adb shell pm list packages -f"
find it's and use it the abovementioned uninstall command.
Then in the end , disconnect the device properly with "adb disconnect" and then "adb kill-server"
Voila , back on , all apps were there and only the nasty app was gone
I hope i could be helpful to someone
Mine over 24 hrs still in bootloop. I hope you're telling the truth.
Thank you, I fixed my bootloop with this method.
For me the TV USB 1A didn't work (1st day) and the PC USB also didn't work (2nd day) , only when I plugged it to an USB (2A? 2.5A?) direct to a power outlet that it got able to boot after 8 hours.
Use the included USB Power Adapter and Cable. Especially many other USB Cables are weak and can't transport 1 Amp.
PC USB 2.0 provides only 0,5 Amps, 3.0 0,7 (or 0,8?) Amps but not 1.
Tried to repair it, but nothing helps. Anybody could check, which app could cause bootloop?
package:com.android.cts.priv.ctsshim
package:com.amazon.net.smartconnect
package:com.amazon.tv.resolutioncycler
package:com.google.android.athome.globalkeyinterceptor
package:com.amazon.recess
package:com.amazon.platform.fdrw
package:com.amazon.ssmsys
package:com.android.providers.calendar
package:com.amazon.tv.ime
package:com.amazon.whisperplay.contracts
package:com.android.providers.media
package:com.amazon.device.rdmapplication
package:com.amazon.dcp.contracts.library
package:com.android.wallpapercropper
package:com.amazon.metrics.api
package:com.amazon.vizzini
package:com.amazon.tv.devicecontrolsettings
package:com.amazon.bueller.notification
package:com.amazon.connectivitycontroller
package:com.ivona.orchestrator
package:com.amazon.device.sync
package:amazon.fireos
package:com.amazon.device.logmanager
package:com.android.documentsui
package:com.android.externalstorage
package:com.android.htmlviewer
package:com.amazon.ceviche
package:com.amazon.alta.h2clientservice
package:com.amazon.advertisingidsettings
package:com.android.providers.downloads
package:com.amazon.tv.parentalcontrols
package:com.android.providers.tv
package:com.amazon.whisperjoin.provisioner.middleware.controller
package:com.amazon.ftv.glorialist
package:com.amazon.dp.logger
package:com.amazon.ods.kindleconnect
package:com.android.defcontainer
package:com.android.providers.downloads.ui
package:com.android.pacprocessor
package:com.amazon.tv.intentsupport
package:com.amazon.sharingservice.android.client.proxy
package:com.amazon.webview
package:com.amazon.android.marketplace
package:com.android.certinstaller
package:com.android.carrierconfig
package:com.amazon.device.backup.sdk.internal.library
package:android
package:com.amazon.tifobserver
package:com.amazon.dialservice
package:com.amazon.client.metrics.api
package:com.amazon.aca
package:com.amazon.cpl
package:com.amazon.dcp
package:com.amazon.imp
package:com.amazon.ssm
package:com.amazon.sync.service
package:com.amazon.fireinputdevices
package:com.amazon.whisperjoin.provisioner.middleware.firetv
package:com.android.backupconfirm
package:com.amazon.logan
package:com.amazon.tahoe
package:com.amazon.tcomm
package:com.android.statementservice
package:com.amazon.naatyam
package:com.amazon.storm.lightning.tutorial
package:com.amazon.identity.auth.device.authorization
package:com.amazon.kindle.cms
package:com.android.providers.settings
package:com.amazon.kindleautomatictimezone
package:com.android.sharedstoragebackup
package:com.amazon.uxcontrollerservice
package:com.android.printspooler
package:com.fireos.arcus.proxy
package:com.amazon.tv.fw.metrics
package:com.android.dreams.basic
package:com.amazon.device.backup
package:com.amazon.firehomestarter
package:com.amazon.securitysyncclient
package:com.amazon.unifiedshare.actionchooser
package:com.amazon.firerestapiframework
package:com.amazon.tv.routing
package:com.amazon.device.messaging
package:com.amazon.device.bluetoothkeymaplib
package:com.amazon.device.metrics
package:com.amazon.device.messaging.sdk.internal.library
package:com.amazon.providers
package:com.amazon.tv.devicecontrol
package:com.amazon.tv.ottssocompanionapp
package:android.ext.shared
package:com.android.onetimeinitializer
package:com.android.keychain
package:com.amazon.device.sale.service
package:com.amazon.cardinal
package:android.ext.services
package:com.android.packageinstaller
package:com.svox.pico
package:com.amazon.tcomm.client
package:com.amazon.tv.forcedotaupdater.v2
package:com.amazon.client.metrics
package:com.amazon.device.settings.sdk.internal.library
package:com.android.proxyhandler
package:com.amazon.autopairservice
package:amazon.jackson19
package:com.android.managedprovisioning
package:com.amazon.tmm.tutorial
package:com.mediatek.atci.service
package:com.amazon.device.software.ota
package:com.amazon.wifilocker
package:com.amazon.dcp.contracts.framework.library
package:com.amazon.device.bluetoothdfu
package:com.amazon.storm.lightning.services
package:com.amazon.whisperlink.core.android
package:com.amazon.device.messaging.sdk.library
package:com.amazon.tv.notificationcenter
package:com.amazon.tv.support
package:com.amazon.tv.nimh
package:com.amazon.tv.oobe
package:com.amazon.sync.provider.ipc
package:com.amazon.tv.legal.notices
package:com.android.settings
package:com.amazon.tv.settings.core
package:com.amazon.firebat
package:android.amazon.perm
package:com.android.cts.ctsshim
package:com.amazon.tv.keypolicymanager
package:com.amazon.android.service.networkmonitor
package:com.amazon.providers.contentsupport
package:com.amazon.avl.ftv
package:com.android.vpndialogs
package:com.amazon.awvflingreceiver
package:com.amazon.device.crashmanager
package:com.amazon.application.compatibility.enforcer
package:com.amazon.whisperplay.service.install
package:com.ivona.tts.oem
package:com.android.shell
package:com.android.wallpaperbackup
package:com.amazon.uxnotification
package:com.android.providers.userdictionary
package:com.amazon.cast.sink
package:com.amazon.device.software.ota.override
package:com.android.location.fused
package:com.android.systemui
package:com.amazon.alexashopping
package:com.amazon.franktvinput
package:com.android.bluetoothmidiservice
package:com.amazon.aria
package:com.amazon.avod
package:com.amazon.communication.discovery
package:com.amazon.alexa.externalmediaplayer.fireos
package:com.amazon.tv.releasenotes
package:com.amazon.ssdpservice
package:com.amazon.device.settings
package:com.amazon.tv.livetv
package:com.amazon.device.sync.sdk.internal
package:com.amazon.connectivitydiag
package:com.android.bluetooth
package:com.amazon.device.lowstoragemanager
package:com.android.providers.contacts
package:com.amazon.providers.tv
package:com.amazon.webview.chromium
package:com.amazon.bueller.music
package:com.amazon.hedwig
package:com.amazon.kindle.devicecontrols
package:com.amazon.application.compatibility.enforcer.sdk.library
Problem solved!
What worked for me?
adb shell pm list packages -f
Then copy output to notepad and uninstall all listed apps. Every single one. After this fire tv restarted few times and i have it working again.
Took some time do do it, but it is working now.
I have waited for 5 days without success, but this worked.
Firestick 4k Boot loop issue solved using Y-OTG cable
Hello, I had the same problem. I did not have my fire stick 4k connected to my laptop adb before I installed Google play so I could not uninstall play store and play services using adb. I came across this link and followed exactly what mentioned, It let me boot in to safe mode then I uninstalled play store and play services then did a normal boot. It works well now. (This url is non-English so allow google translate to English)
I got y-otg cable from Amazon, I Kept holding ctrl+alt+menu+printscreen keys while another person assisted to plug in the fire stick power adapter. I kept hitting the "i" key. It started the regular white screen with orange amazon logo after few moments darkscreen+safemode in left bottom appeared then I got my screen. clicked "your applications" and uninstalled both culprits then power off and power on.
(Both blue tooth and usb key board supports to invoke the safe mode)
(add https www to the url)
android-hilfe.de/forum/amazon-fire-tv-stick.2146/google-apps-bootloop-praevention-und-infos-fuer-den-ernstfall-fire-tv-4k.918292.html
How to unbrick or factory reset...
avidav said:
Until yesterday I had a functional FTV stick, now paperweight.
I installed an application for watching TV. The application installed ok but, when launched, told me it needs the Google Play services.
So I went and installed the Google Play services, which also installed ok.
I relaunched the application, which this time just froze, and I could not back out of it. So I rebooted the FTV, with the result that now it starts booting, gets to the white Amazon logo with music and from there it boots again, and again in an infinite loop.
I tried powering it from an external supply - no change. I tried the Right button/Back button remote combination - no change. I did NOT unlock the bootloader (did not expect such a problem and was not aware that it is doable); I do not have ADB enabled.
I read that there is a way to unbrick using a USB keyboard combination but I only have one micro-USB port on the stick which is used for power supply, so I don't see how I can connect a keyboard.
Any suggestions how to proceed from here will be most welcome. Thanks in advance.
Click to expand...
Click to collapse
....
To unbrick or factory reset it, you will need an OTG cable with charger and USB conector to connect an logitech keyboard or another multimedia keyboard.
Then with the fire tv turning on ( in loop status ), push at the same time ( ctrl+alt+del ) and when it restart push ( FN key+ Option key -square with lines ) over and over again, until it enter in SAFE MODE. Then, go to my fire tv and push factory reset. ... Good luck. ( if you request the video i going to upload soon in youtube).