So instead of spamming the forums, I thought I would just make on consolidated post asking for help
Background: I have suffered from a visual disability for over 20 years. There are many facets to it but the one that is relevant here is that some displays trigger instant eye strain and migraines when I view them. I have been to over 27 specialists in 7 states over 2 decades and no one has been able to find out exactly what us causing it. All we know is the issue isn't really caused by the display, but what is driving the display, and seem to be related to colors somehow.
Anyway, I ordered a 4k Fire Stick on July 15, 2019. SO looking at https://forum.xda-developers.com/t/...is-prerooted-stock-images-6-2-8-0_r1.3983091/, it looks like my Fire Stick came with OS 6.2.6.5_r1. I do not recall it ever asking for updates before this, so I do not know if it ever updated to 6.2.7.7_r1 (which is the last update prior to the UI update). I would like to flash OS 6.2.6.5_r1 which is the closest ROM I can find to what was on the stick when I first bought it and it worked.
I also have an unopened 4k Fire Stick I purchased on Nov 29, 2019. This is still sitting new in the box and have never been opened or plugged into anything.
So here is where my questions start
General Questions
1. Are the sticks I ordered the "mantis" one? So I would look for "mantis" instructions for working with it? Can someone provide a stock Mantis 6.2.6.5 ROM, I really don't care too much about being rooted honestly.
Questions for upgraded stick (that I cannot use right now due to disability)
1. Is there any hope for this device? As I understand it there is an eFuse blown during the 6.8 upgrade preventing downgrades.
2. Is there any work going on that will allow that blown eFuse to be bypassed (like a modified 6.2.6.x ROM that doesn't check the eFuse status)?
Questions for unopened stick
1. Is there any way to block the updates while setting up the device (prevent auto update)?
- 1a: I know there is a "BlockUpdate.apk" that can be sideloaded and run, but to do that I would need to have the device up and running to enable ADB Debugging and connect to the device, so I would have had to go though the initial setup, which will update the device, making it to late to install the APK and block the update
- 1b: I know you can also install Remote ADB Shell on the stick and use the PM disable user commands to block OTA updates, but again, you can't get to the point where you can turn on ADB Debugging and install those apps before going though the initial setup, which will update the device, making it to late to block the updates
2. I saw there were some methods where people were using their routers to block access to certain Amazon and/or akamai servers so you could activate the stick but the update check would fail, but all those guides seem to be for Fire TV's, not Fire Sticks, and are all from 2016-ish. Do these still work?
Questions for Rooting device
1. I saw the aluminum foil trick, but all the guides I see seem to start after a point where the device has been activated, which would have forced the update and would be to late for me. Can you root BEFORE the device is activated?
2. How do you connect a Fire Stick to a PC to allow the Linux scripts to see it and root it? I can't connect to the TV and then to my wifi, cause once it connects to wifi, it auto updates, and we're stuck again.
So can anyone help me out? My end goal is to have my upgraded Fire Stick downgraded to the 6.2.6.5 version and will NEVER install a system update, and/or have my unopened FireStick activated and working and NEVER install an update. I don't really care about any enhanced "debloating" or anything after that.
Many thanks up front.
Yes, you can try the unlock infront of the setup, that is the way to go.
But I would test your ruined stick first, it doesn't harm anything... maybe big A. messed the efuse burning up, who knows. Short the stick and in case you can't see 'phone' mode in lsusb, the efuse is burned as expected.
Sus_i said:
Yes, you can try the unlock infront of the setup, that is the way to go.
But I would test your ruined stick first, it doesn't harm anything... maybe big A. messed the efuse burning up, who knows. Short the stick and in case you can't see 'phone' mode in lsusb, the efuse is burned as expected.
Click to expand...
Click to collapse
Thanks, how would I unlock the device and block the updates without having to go through through Fire Stick setup (which would force the update)
As I understand it, I could
1 - Boot up the modified Linux iso in a VM
2 - Open the Fire Stick and use the aluminum foil to short it
At that point, how do I connect the Fire Stick to my PC? If I plug it into my TV and connect it to my network, it's going to auto update.
Once the above quesiton is answered, I could then run the scripts and get root and get twrp via the scripts in the Linux iso. But at that point, what would I flash in TWRP to block the OTA updates? I would not be anle to get to any point that allows me to enable ADB debugging without going through the Fire Stick setup, which would force the OTA updates
The thing is really easy.
Older 4k sticks are vulnerable to the current kamakiri exploit, and newer sticks are not.
Amaz. fixed with 6.2.8.0 the bootrom feature used in kamakiri, so any kamakiri vulnerable stick gets fixed with that update... Only way to prevent this fix, is to unlock it first, then the OTA updates can't harm anything.
The unlock protects them. In this case the update is fine...
If you want to try the unlock, you need to follow the kamakiri OP.
You don't need a TV or a network connection for your stick.
You need the usb cable and some tinfoil.
No one knows if your stick is vulnerable or not.
You may check this in a terminal with the lsusb command, while shorted (see the unlock OP for details).
If you can keep the stick with the short in 'phone' mode (look in lsusb a few times instead of running the bootrom-step), you're lucky and the unlock may work.
Sus_i said:
The thing is really easy.
Older 4k sticks are vulnerable to the current kamakiri exploit, and newer sticks are not.
Amaz. fixed with 6.2.8.0 the bootrom feature used in kamakiri, so any kamakiri vulnerable stick gets fixed with that update... Only way to prevent this fix, is to unlock it first, then the OTA updates can't harm anything.
The unlock protects them. In this case the update is fine...
If you want to try the unlock, you need to follow the kamakiri OP.
You don't need a TV or a network connection for your stick.
You need the usb cable and some tinfoil.
No one knows if your stick is vulnerable or not.
You may check this in a terminal with the lsusb command, while shorted (see the unlock OP for details).
If you can keep the stick with the short in 'phone' mode (look in lsusb a few times instead of running the bootrom-step), you're lucky and the unlock may work.
Click to expand...
Click to collapse
I thought even if you were unlocked, once you were auto updated, the eFuse is blown and you can't downgrade?
FOr the old Fire Stick (that has never been upgraded so it should be fine) once I unlock the device and flash TWRP, what would I flash to prevent the OTA update from taking place during the setup of the device?
emkorial said:
I thought even if you were unlocked, once you were auto updated, the eFuse is blown and you can't downgrade?
FOr the old Fire Stick (that has never been upgraded so it should be fine) once I unlock the device and flash TWRP, what would I flash to prevent the OTA update from taking place during the setup of the device?
Click to expand...
Click to collapse
No, unlocked = safe.
There isn't a reason to mess with the initial update, as long as you've done the unlock successfully and TWRP is in place. Then you can downgrade anytime later to whatever OS version, if you like.
After you did the unlock, flash magisk, do the initial setup, enable adb, you can use adb shell commands to disable the OTA updates.
You don't need a TV or a network connection for your stick.
Click to expand...
Click to collapse
How do I interact with TWRP if it isn't plugged into the TV?? What do you see the TWRP screen on to navigate it??
See post two and three in the unlock thread...
Most people use always TWRP commandline via ADB.
Sus_i said:
See post two and three in the unlock thread...
Most people use always TWRP commandline via ADB.
Click to expand...
Click to collapse
So I am still very confused. If I have the Fire Stick only connected to my computer via USB cabl, there will be no Fire Stick display anywhere. So I will be unable to interact with TWRP. But step 1 of post 2 says I can use an OTG mouse to interact with TWRP. How can you use a mouse when the Stick isn't plugged in to a TV?? How do you even boot into TWRP when the stick isn't plugged in?
The second point says use a command line and use ADB, but I thought you need to have ADB permissions set on the device to allow that to work, and you can't get to those ADB permissions without activating the device, which will update it, which defeats the whole purpose
I really appreciate the help but I am totally confused. This is so very frustrating.
You can plug the hdmi into your TV, but that wont help you to interact, because you use TWRP commands via adb. Ofc you see the commands and the TWRP txt output in the terminal window...
If the unlock is done, you can unplug the usb and use OTG + mouse, if you like. Should work too, but you need an usb hub and a storage stick too, if you like to install a ROM or Magisk or whatever. TWRP commandline is easier, you can push files via adb and then just run a adb shell twrp install command...
If TWRP is up, adb is always enabled...
Only the fireOS wants a permission, if you want to use adb.
Sus_i said:
You can plug the hdmi into your TV, but that wont help you to interact, because you use TWRP commands via adb. Ofc you see the commands and the TWRP txt output in the terminal window...
If TWRP is up, adb is always enabled...
Only the fireOS wants a permission, if you want to use adb.
Click to expand...
Click to collapse
OK, that is helpful, so you are saying if I unlock the device, flash TWRP, and reboot into recovery, ADB will be enabled, there is no need to allow ADB Debugging and I can run those pm uninstall commands?
SO are you saying this is the process?
1 - Download linux iso and script to unlock
2 - boot linux iso
3 - plug Fire Stick into PC with supplied USB cable only. Do not plug the HDMI into anything
4 - run the script and do the tinfoil thing
5 - After the script is done type "./fastboot-step.sh" which will reboot the device into TWRP. I will have no idea if this is working because there is no display for me to look at, correct?
6 - I would I guess wait a few minutes for the device to reboot since I would have no display available I would have no idea when it is done rebooting, but at some point I would type "adb devices" and my device would appear in the list?
If that is all correct, then I know I can type "adb shell" at that point to get to a shell window where I can send adb commands. Could I then execute the pm disable commands? Or do I NEED to flash a new rooted ROM before I do that? I honestly don't care at all about being rooted, I just want to disable OTA
7 - And then after that, OTA would be disabled, I can unplug the Stick from my PC, plug it into my TV for the first time, and it would let me register and not auto update during the registration process and never bug me for updates again?
Also I have seen many different variants of the actual pm disable commands required to disable OTA, can you provide the actual correct ones?
Thanks again
emkorial said:
OK, that is helpful, so you are saying if I unlock the device, flash TWRP, and reboot into recovery, ADB will be enabled, there is no need to allow ADB Debugging and I can run those pm uninstall commands?
Click to expand...
Click to collapse
No, never said something like that
You cannot run pm uninstall commands in TWRP adb...
but you can run adb push/pull, adb shell, twrp install and all the other TWRP commands, in order to 'interact' with TWRP.
Maybe do some research, read a bit more about it. There are also some youtube guides out there.
emkorial said:
3 - plug Fire Stick into PC with supplied USB cable only. Do not plug the HDMI into anything
4 - run the script and do the tinfoil thing
Click to expand...
Click to collapse
It doesn't matter if hdmi is in or out.
But you need to follow the unlocks OP.
You need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Take your time, follow the OP
Maybe @Bertonumber1 answers some of your other questions, I've got no time to continue for now... sry.
Sus_i said:
No, never said something like that
Click to expand...
Click to collapse
Thats exactly what you said. You said "If TWRP is up, adb is always enabled..." So which is it, will I be able to run adb shell and then run the pm commands once it boots into twrp or not?
Sus_i said:
You cannot run pm uninstall commands in TWRP adb...
but you can run adb push/pull, adb shell, twrp install and all the other TWRP commands, in order to 'interact' with TWRP.
Click to expand...
Click to collapse
So you are saying I cannot run adb commands from TWRP, but you say I can run adb shell from twrp, which I can then run adb commands from. Which is it?
Sus_i said:
Maybe do some research, read a bit more about it. There are also some youtube guides out there.
Click to expand...
Click to collapse
I've read everything there is on the topic and it's very poorly documented from a step by step perspective. Can you answer the questions where you gave two opposite answers?
And the other questions no one has answers:
1 - Do I need to flash a rooted ROM before running the pm uninstall commands?
2 - Do I need Magisk installed? If so how do I install it?
I've been a remember of xda dev for years and years over many devices and I will never, ever understand how no one on this site ever seems capable of just giving simple step by step instructions and answering simple direct questions with simple direct answers.
At this point I am more confused than when I started so I feel it is still to risky to try this
Sus_i said:
It doesn't matter if hdmi is in or out.
But you need to follow the unlocks OP.
You need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Click to expand...
Click to collapse
I get that the HDMI does not need to be hooked up. Can you answer my quesiotn about how to know when the device is rebooted if I have no display? So I just keep checking adb devices until it shows up?
Sus_i said:
Take your time, follow the OP
Maybe @Bertonumber1 answers some of your other questions, I've got no time to continue for now... sry.
Click to expand...
Click to collapse
Can you just answer this, once I unlock, and reboot, if I wait and then my device shows up in adb devices, can I then run adb shell and run the pm uninstall commands?
emkorial said:
Thats exactly what you said. You said "If TWRP is up, adb is always enabled..." So which is it, will I be able to run adb shell and then run the pm commands once it boots into twrp or not?
So you are saying I cannot run adb commands from TWRP, but you say I can run adb shell from twrp, which I can then run adb commands from. Which is it?
Click to expand...
Click to collapse
lol. Its just like I said yesterday:
You can run adb push/pull, adb shell, twrp install and all the other commands, in order to 'interact' with TWRP.
Click to expand...
Click to collapse
You see, it isn't TWRP that searchs for updates
It is the fireOS that wants to keep the stick up-to-date.
If you want to disable this OTA update process inside the fireOS, you need to run the pm disable commands while fireOS is up and running.
Then I said yesterday:
It doesn't matter if hdmi is in or out.
But you need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Take your time, follow the OP
Click to expand...
Click to collapse
About four hours later, you ask the same question, in the same wrong order!??:
emkorial said:
I do not want to flash another firmware. I don't care about being rooted at all. I'm never going to install any silly add-on's or pointless extras. I have one goal and one goal only: Keep the OS version on the stick now and prevent it from ever updating.
Here is the process I have put together from scouring about 20 different threads and a half dozen conversations.
1 - Download the linux iso and the script to unlock the Fire Stick
2 - boot a PC with the linux iso
3 - plug Fire Stick into PC with supplied USB cable only. Do not plug the HDMI into anything
4 - Run the script and do the tinfoil thing
Click to expand...
Click to collapse
At this point It doesn't make sense, just to write it again and again, if you can't get the point.
emkorial said:
I've been a remember of xda dev for years and years over many devices and I will never, ever understand how no one on this site ever seems capable of just giving simple step by step instructions and answering simple direct questions with simple direct answers.
At this point I am more confused than when I started so I feel it is still to risky to try this
Click to expand...
Click to collapse
I'm sorry to hear that.
I've just realized that I can't help you at all, so I'm going to stop answering.
Wish you good luck. Have fun.
Sus_i said:
If you want to disable this OTA update process inside the fireOS, you need to run the pm disable commands while fireOS is up and running.
Click to expand...
Click to collapse
OK, that makes sense. But since Fire OS is up and running and sitting at the setup screen, USB Debugging has never been turned on. So how do you connect to the Fire Stick via ADB since you cant get to developer options?
UNLESS, does the pre rooted image you flash after unlocking have USB Debugging enabled by DEFAULT, so you DON'T have to turn it on via Settings? THAT would make this ALL make sense. Is that the case?
If so, then it would be
1 - Download iso and script
2 - boot iso and do foil trick and run script
3 - flash a rooted ROM (that will have USB Debugging enabled by default)
4 - boot Fire Stick and just sit at initial screen, don't go though setup
5 - Connect via ADB (which will work since USB Debugging is turned on by default)
6 - Run pm commands
7 - Continue with setup and OTA will be blocked
Is that correct?
Edit: I suppose I can just keep trying at each step until it works. Like this
Step 1 - Take the stick out of the box, plug it into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. If that doesn't work...
Step 2 - Unlock the device via the foil trick, plug the stick into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. If that doesn't work...
Step 3 - Flash a custom ROM, plug the stick into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. That should work as that mirrors the process in the guide.
Related
UPDATE: I added "solved" to the title since I am now unbricked. That said, I do hope someone will pop in and tell me how to run the shell scripts on a mac...
Click to expand...
Click to collapse
Hi there. I have spent several days searching xda forums, popping into the kindlefire irc channel, and searching google however have not yet figured this out, could use some help.
I have read: the Kindle Fire Beginners Guide, the Kindle Fire Unbrick thread, The Kindle Fire Utility thread (yup the whole thing), and more.
According to the Kindle Fire Beginner's Guide, only 1% of all brick situations are actually a brick, so I'm going to persevere and go ahead and ask for the help, because also according to the guide, if your fire can't be seen as a device then actually it's a brick. To quote: " unless something else was done to the device after the change in bootmode preventing access to adb or fastboot commands. Then it’s actually a brick at that point."
I can't be sure if anything else was done after the change in bootmode so I'll just explain how I got here and hopefully someone can help out.
I have a mac mini running Os x 10.6.8, and the Kindle Fire which was running stock version 6.2.2.
I used the kindlewater root method to install firefirefire and cwm recovery. Was able to boot into recovery by pressing on the power button for it to go orange and then load the recovery options.
Before doing anything at all (and in consultation with St3p_2 of this forum, one of the kindlewater developers), I decided to perform a backup in preparation for flashing a ROM.
so, I booted, went into recovery, navigated to "install a .zip" and chose "backup" at which point I got a message/nag/reminder that this was a permanent change, and I selected "ok". It did it's thing for a while, went into reboot, and I then had the firefirefire logo blinking in a very very slow loop.
It was recommended to me to perform a factory reset by holding the power button for 2 solid minutes, which should then have returned me to stock. Actually, the first time i did it for minutes I went from having a very slow blinking firefirefire to having a rather fast blinking firefirefire. Following a suggestion i then tried it with the kindlefire unplugged. This resulted in a plain black screen until the fire was plugged in again: no boot, no indication of response to use of the power button. Once plugged in, it has gone back to the rather fast blinking firefirefire logo.
I read through the Kindle Fire Utility thread, found the v0.9.2 version prepared for mac and linux, and downloaded it. Although I am not new to terminal, I am not familiar with what command language is necessary to perform the actions required by this tool. If I open the install_drivers.sh with terminal, i get this:
Reverie:~ apple$ /kindlefire/Kindle_Fire_Utility_MacLinux_0.9-1.2/install_drivers.sh ; exit;
This file will install the correct adb_usb.ini file for proper Kindle Fire detection.
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
so I tried running it in the console. I will spare you the output of the console as it appeared to be merely a printout of the actual code of the file and was quite long.
Trying to run the file runme.sh in terminal before running the install_drivers.sh in the console, I got error messages stating there is no such command, or no such file, depending on my command language.
After running the install_drivers.sh in the console, when I try to run runme.sh in terminal, i get this:
/kindlefire/runme.sh ; exit;
Reverie:~ apple$ /kindlefire/runme.sh ; exit;
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure adb is in your path
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue... --- STARTING ----
--- WAITING FOR DEVICE
Which I affirmed because all the requirements had indeed been set that way on the device before the bricking happened. After "starting" and "waiting for device" nothing happens even waiting indefinitely (more than half an hour) and then it never finds the device.
When I go into terminal and type: "adb devices" I get:
Last login: Sun Mar 18 17:08:38 on ttys001
Reverie:~ apple$ adb devices
List of devices attached
Reverie:~ apple$
This result is the same both before attempting to use the 0.9.2 mac utility and after.
I really am stuck at this point, as everything I find with instructions on how to "unbrick" does require that the machine recognize that your kindlefire is attached. Running any of the tools I find requires that basic bottom dollar, which I don't seem to have.
That said, the behavior of "nothing at all: blank screen" when unplugged, and the behavior of "blinking firefirefire logo" when plugged in would tend to indicate that at the very least the device knows it's plugged in and getting juice, and some process is happening when that's true.
Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?
nothing doing when unplugged seems like a dead battery
would try to charge it with the wall charger for some hours regardless if the orange light comes up - this can last a while
furthermore i don't know which version of kfu for mac you'r using but zergrush is'nt working any more since stock rom 0.6.1
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
for rooting use kindlewater:
http://forum.xda-developers.com/showthread.php?t=1443071
as far as i know the commands need to be entered with a ./ in front ie: ./install_drivers.sh
sisterdelirious said:
Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?
Click to expand...
Click to collapse
Thanks for reading my guide. I hope it helped you a bit.
Mac OS X is also my primary OS and I take my hat off to you for even trying things this way. I took the easy way out from the very beginning and just used Parallels Desktop to build Windows and Linux virtual machines. If things ultimately don't work out, you might want to try going that route as well. I believe Parallels offers a demo version if you want to see it in action. Regardless, I don't think that matters quite yet, because I tend to agree with b63 here. I think the biggest problem you have right now is a dead battery.
I've never had a dead battery, so I can't comment directly, but take a look at this thread, starting at post #226...
http://forum.xda-developers.com/showthread.php?t=1392693&page=23
There some back and forth for a couple of pages, but that user describes symptoms that sound very much like what you are seeing right now. I think you should try the wall charger first. Plug it in, force the Kindle Fire to turn off and just try to let it charge overnight or something. If you cannot get your KF charged with the stock wall charger, you might want to buy a factory cable. From what I gather, that user reported that his Kindle Fire booted into fastboot mode by using the factory cable even with a (nearly) dead battery. He was then able to flash the stock software, which is able to handle the dead battery situation better than some alternative ROM and have it go through the charge cycle.
Wow... so simple...
b63 said:
nothing doing when unplugged seems like a dead battery
would try to charge it with the wall charger for some hours regardless if the orange light comes up - this can last a while
Click to expand...
Click to collapse
This was the deal. When plugged in with the usb cord it didn't seem to be giving it power and being powerless could not be recognized by the computer. Plugged it into the wall charger and Voila! was able to start up just fine, still rooted via the kindlewater method, capable of being booted normally or booted into CWM recovery. Awesome!
I also did a quick double-check, and now that it's powered-up, running a terminal and typing "adb devices" actually returns a list with the kindle (serial number?) on it.
furthermore i don't know which version of kfu for mac you'r using but zergrush is'nt working any more since stock rom 0.6.1
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
Click to expand...
Click to collapse
I read through everything and the version of kfu that was modded for mac was 0.9.2 which I mentioned in my original post. Sounds like since I was on 6.2.2 that mac version is definitely not going to help me (both kfu out of date and stock version out of date on zergrush) if I were to want it for rooting purposes.
for rooting use kindlewater:
http://forum.xda-developers.com/showthread.php?t=1443071
Click to expand...
Click to collapse
that is the one i used. I was looking for a mac tool for post-root rescue methods...i had thought that the kfu mac version had valuable rescue/unbrick capabilities but at this point I don't remember.
as far as i know the commands need to be entered with a ./ in front ie: ./install_drivers.sh
Click to expand...
Click to collapse
[/QUOTE]
Thankfully, I don't need to try that. my kf got properly unbricked just by plugging it into the wall charger.
Great guide, it was the battery
kinfauns said:
Thanks for reading my guide. I hope it helped you a bit.
Mac OS X is also my primary OS and I take my hat off to you for even trying things this way. I took the easy way out from the very beginning and just used Parallels Desktop to build Windows and Linux virtual machines. If things ultimately don't work out, you might want to try going that route as well. I believe Parallels offers a demo version if you want to see it in action. Regardless, I don't think that matters quite yet, because I tend to agree with b63 here. I think the biggest problem you have right now is a dead battery.
Click to expand...
Click to collapse
Thank you for your guide. I thought it was extremely well written and very helpful. It definitely helped me relax a little stress-wise while looking for a solution.
That was it (dead battery). I did try meddling around a bit with virtualbox virtual machines: a windows 7 ultimate, and a linux box that I have that does not have internet access making doing anything realtime while reading suggestions just isnt easy/feasible right now. I found that the virtualbox vms did not have access to the usb devices (flash drives, external hard drives, ostensibly if it were visible to the computer the kindle) despite my installing some optional extension packs for that purpose. I didn't explore the vms further to linux or xp simply because of the time required to install and configure a vm. I also didn't rewire my home so net access went to the linux box for the same reason... ultimately both are possible but both more hassle than it seems to be worth before simply asking the question, can it be done on a mac?
I've never had a dead battery, so I can't comment directly, but take a look at this thread, starting at post #226...
http://forum.xda-developers.com/showthread.php?t=1392693&page=23
There some back and forth for a couple of pages, but that user describes symptoms that sound very much like what you are seeing right now. I think you should try the wall charger first. Plug it in, force the Kindle Fire to turn off and just try to let it charge overnight or something. If you cannot get your KF charged with the stock wall charger, you might want to buy a factory cable. From what I gather, that user reported that his Kindle Fire booted into fastboot mode by using the factory cable even with a (nearly) dead battery. He was then able to flash the stock software, which is able to handle the dead battery situation better than some alternative ROM and have it go through the charge cycle.
Click to expand...
Click to collapse
I'm just so glad this worked. Thank you for your help!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Similar issue
My KF is seeming to have a similar but distinctly different issue as the OP. Because I can turn on the KF without it being plugged in, I cannot imagine that it is a battery issue.
When I plug it in to a Windows machine, the FFF bootloader comes on, the KF seems to connect, be recognized, fail at driver installation (which I have done manually, with no success), and then disconnect. This prevents me from running any sort of commands.
When I connect to my Mac, I get the FFF bootloader and then no response whatsoever.
Trying to run commands from Terminal or the Command line or using KFU on my Windows machine all result in a "waiting for device" message.
Not sure what I should do from this point to get it back to accepting adb commands. I'm confident that once I do I'll be able to save it, but at this point I'm stuck.
Any ideas?
Ok. I've scoured the internet trying to find a solution to my issue and so far I've come up empty handed. Here's my issue:
- I bought this FTV1 on Craigslist knowing it was softbricked. I have no idea if it was unlocked or rooted or had any custom recovery installed.
- I do not have the remote as the owner wanted to keep it as a spare (I use my phone as a remote anyways).
- I've tried using the ALT+PRNT SCRN+I keys (I'm not sure I'm hitting them at the correct times) and have had no luck getting to the recovery screen.
- I ordered a USB cable to try fastboot and I had no luck there as well.
The only success I've seen is when connected to my computer via USB my computer recognizes the FTV1 via ADB. I can use ADB to reboot recovery but I only get to this screen (not my picture) and can't get anywhere from here.
Can anyone suggest something I haven't tried? Is there anyway to crack this thing open and somehow do a factory reset/stock flash? Any info would be appreciated!
Thanks in advance!
Try the PC version of Kingoroot, if the device has a rootable version of firmware you can unbrick it with Kingoroot.
Read the paragraph right after step 10 in this post:
https://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
I can confirm, it does work.
2WhlWzrd said:
Try the PC version of Kingoroot, if the device has a rootable version of firmware you can unbrick it with Kingoroot.
Read the paragraph right after step 10 in this post:
https://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
I can confirm, it does work.
Click to expand...
Click to collapse
Thanks! I'll be trying this asap!
Well, I was able to try this tonight and unfortunately it didn't work. After a few minutes I'd eventually get a "Root Fail" message on KingoRoot. It did look positive for a few minutes though!
Any other suggestions? Or am I just out the $15 I have in this thing? Like I said, I knew it was a risk when I bought it but I figured it was worth it for $15.
Thanks for any suggestions provided!
cabraswell said:
Well, I was able to try this tonight and unfortunately it didn't work. After a few minutes I'd eventually get a "Root Fail" message on KingoRoot. It did look positive for a few minutes though!
Any other suggestions? Or am I just out the $15 I have in this thing? Like I said, I knew it was a risk when I bought it but I figured it was worth it for $15.
Thanks for any suggestions provided!
Click to expand...
Click to collapse
Use adbLink to connect to the device and open "Uninstall APK" from the console, and look for APKs with instances of "king" in the name. If you see kingroot or kinguser those are related to Kingroot, not to be confused with Kingoroot. Sorry, I don't remember off hand what the one related to Kingoroot was called, other than it had "king" in the name. But if it was present on the device and "Root Failed", I uninstalled it and tried again, and the next time I would get "Root Successful".
Also, at the top of the console there is a "Reboot" feature which allows you to reboot into recovery that may be useful.
cabraswell said:
Ok. I've scoured the internet trying to find a solution to my issue and so far I've come up empty handed. Here's my issue:
- I bought this FTV1 on Craigslist knowing it was softbricked. I have no idea if it was unlocked or rooted or had any custom recovery installed.
- I do not have the remote as the owner wanted to keep it as a spare (I use my phone as a remote anyways).
- I've tried using the ALT+PRNT SCRN+I keys (I'm not sure I'm hitting them at the correct times) and have had no luck getting to the recovery screen.
- I ordered a USB cable to try fastboot and I had no luck there as well.
The only success I've seen is when connected to my computer via USB my computer recognizes the FTV1 via ADB. I can use ADB to reboot recovery but I only get to this screen (not my picture) and can't get anywhere from here.
Can anyone suggest something I haven't tried? Is there anyway to crack this thing open and somehow do a factory reset/stock flash? Any info would be appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Have you tried the windows version of KingoRoot Aswell?
I never got alot of luck with King Root but KingoRoot worked quite a few times for me.
If you manage to get root, even if you can't boot it fully up you will be able to recover.
sconnyuk said:
Have you tried the windows version of KingoRoot Aswell?
I never got alot of luck with King Root but KingoRoot worked quite a few times for me.
If you manage to get root, even if you can't boot it fully up you will be able to recover.
Click to expand...
Click to collapse
I did try KingoRoot (for Windows) and kept getting "Root Fail"
Gonna try adblink as suggested by 2WhlWzrd when I get home tonight. Hoping that works. Would love to get this thing working!
Some more information that will help move things along.
First, after getting adbLink installed and connected. Open "ADB Shell" from the console and run:
Code:
getprop ro.build.version.fireos
This will tell us what version of firmware the device has, and whether or not it is even rootable.
If it is, and happens to have been rooted with Kingoroot, the APK that I mentioned uninstalling before will be listed as "com.kingouser.com".
And if it's not rootable then getting in to recovery is going to be your best bet.
Good Luck!
2WhlWzrd said:
Some more information that will help move things along.
First, after getting adbLink installed and connected. Open "ADB Shell" from the console and run:
Code:
getprop
This will tell us what version of firmware the device has, and whether or not it is even rootable.
If it is, and happens to have been rooted with Kingoroot, the APK that I mentioned uninstalling before will be listed as "com.kingouser.com".
And if it's not rootable then getting in to recovery is going to be your best bet.
Good Luck!
Click to expand...
Click to collapse
Thanks again. I look forward to trying these steps tonight!
cabraswell said:
Thanks again. I look forward to trying these steps tonight!
Click to expand...
Click to collapse
Edited the code, just "getprop" gives alot of info, we're looking for something specific.
2WhlWzrd said:
Edited the code, just "getprop" gives alot of info, we're looking for something specific.
Click to expand...
Click to collapse
Software version 5.2.1.0 not rootable by software means (from what I can find).
Getting error "Could not access Package Manager" when I click Uninstall APK in adbLink.
cabraswell said:
Software version 5.2.1.0 not rootable by software means (from what I can find).
Click to expand...
Click to collapse
Correct. Looks like Recovery is the only option.
2WhlWzrd said:
Correct. Looks like Recovery is the only option.
Click to expand...
Click to collapse
The trouble is I can't get into recovery. I've tried a couple different keyboards even. I am starting to think I'm hosed =/
cabraswell said:
The trouble is I can't get into recovery. I've tried a couple different keyboards even. I am starting to think I'm hosed =/
Click to expand...
Click to collapse
Did you try the "Reboot Recovery" option from the "Reboot" menu at the top of adbLink console?
2WhlWzrd said:
Did you try the "Reboot Recovery" option from the "Reboot" menu at the top of adbLink console?
Click to expand...
Click to collapse
Yup. Same result as using adb reboot-recovery
cabraswell said:
Yup. Same result as using adb reboot-recovery
Click to expand...
Click to collapse
i think i went through quite similar ordeal few weeks back. can you try 'fastboot devices' command to see if firetv shows up with usb cable you ordered.
also, if it doesn't show up, make sure you try few combinations as below
- 1. make sure firetv is off and you don't have command prompt window running
2. turn on firetv, wait couple seconds and turn on command prompt but make sure you run as admin( i had to do this due to work laptop)
3. try fastboot devices, if it won't show up then keep take usb cable out from either of the side, restart fire tv and hook usb back quickly...
4. play around with combination of #3 above...
YoColdRain said:
i think i went through quite similar ordeal few weeks back. can you try 'fastboot devices' command to see if firetv shows up with usb cable you ordered.
also, if it doesn't show up, make sure you try few combinations as below
- 1. make sure firetv is off and you don't have command prompt window running
2. turn on firetv, wait couple seconds and turn on command prompt but make sure you run as admin( i had to do this due to work laptop)
3. try fastboot devices, if it won't show up then keep take usb cable out from either of the side, restart fire tv and hook usb back quickly...
4. play around with combination of #3 above...
Click to expand...
Click to collapse
So far I haven't had any luck getting fastboot to recognize it but I'll give this a try tonight. Thanks!
Well, I gave up tonight. I've tried everything I could find and everything mentioned here but recovery has eluded me. I called Amazon to talk to them and after trying a few troubleshooting options they gave me a 20% discount on a Fire TV. I ordered a refurbished 2nd gen Fire TV so I'll be ready when I get a 4K tv.
Thanks for all of your help guys. I wish we had gotten it done. Maybe next time!
Hello guys,
I am an unlocked LG G4 user running on Android 5.1 Lollipop.
I cant recieve updates through OTA as it always says "You have latest version of current OS". So I tried updating manually.
Since I am not very good with LG flash tools I was looking at unlocking bootloader and twrp.
The problem is :
My hardware info shows "LG H815"
Adb recognizes it as "LGF500L204da3d4 unauthorized"
A google search told me that F500L is Korean variant and now I am totally confused. Am I missing something here.
I have attached screenshots of device info.
Please guide.
The unauthorized thing comes from enabling ADB in the Developer Options. Once you do that, the very next time you connect the G4 to a computer and then run the "adb devices" command it starts the adb daemon and then tries to connect to the device, upon a connection the phone not the computer will pop up a box asking for permission to allow the connection based on an RSA fingerprint (aka the security aspect) and you have to allow that.
Without allowing that you'll never get ADB to work properly. You can try this process to get things working properly:
- Disconnect the G4 from the computer entirely
- Disconnect it from any charger too just so you're good to go
- Go into the Developer Options, revoke all using the "Revoke USB debugging permissions" and reboot the G4 right then and right there as soon as those permissions are revoked, do NOT do anything else, reboot immediately after you make that change
- Upon the reboot let the G4 boot completely and wait 2 minutes before swiping/unlocking the device back to the Home screen
- Plug in the USB cable and make sure you choose the MTP/file option, not charging
- Fire up the adb devices command on the computer and watch the phone carefully for that popup asking for permission to connect
- Choose OK to enable the connection and check the box to make it permanent for that specific computer
After that it should show you the device serial number and say "authorized." If not then you're missing something or there's some other problem, but that's how I've done this on a few hundred devices over the years and never had an issue. The other thing that could be affecting this are making sure you have the proper ADB drivers, sometimes that can be a complete pooch-screw to get working and I can't help on that front.
Pic below is what you're looking for and without granting this permission ADB will never see the device as authorized.
Good luck...
br0adband said:
The unauthorized thing comes from enabling ADB in the Developer Options. Once you do that, the very next time you connect the G4 to a computer and then run the "adb devices" command it starts the adb daemon and then tries to connect to the device, upon a connection the phone not the computer will pop up a box asking for permission to allow the connection based on an RSA fingerprint (aka the security aspect) and you have to allow that.
Without allowing that you'll never get ADB to work properly. You can try this process to get things working properly:
- Disconnect the G4 from the computer entirely
- Disconnect it from any charger too just so you're good to go
- Go into the Developer Options, revoke all using the "Revoke USB debugging permissions" and reboot the G4 right then and right there as soon as those permissions are revoked, do NOT do anything else, reboot immediately after you make that change
- Upon the reboot let the G4 boot completely and wait 2 minutes before swiping/unlocking the device back to the Home screen
- Plug in the USB cable and make sure you choose the MTP/file option, not charging
- Fire up the adb devices command on the computer and watch the phone carefully for that popup asking for permission to connect
- Choose OK to enable the connection and check the box to make it permanent for that specific computer
After that it should show you the device serial number and say "authorized." If not then you're missing something or there's some other problem, but that's how I've done this on a few hundred devices over the years and never had an issue. The other thing that could be affecting this are making sure you have the proper ADB drivers, sometimes that can be a complete pooch-screw to get working and I can't help on that front.
Pic below is what you're looking for and without granting this permission ADB will never see the device as authorized.
Good luck...
Click to expand...
Click to collapse
Ok..So I tried as per above instructions.
The only change is it's written as "device" in place of "unauthorized". The serial number is the same.
I thought it would be written as LGH815...etc etc for the H815 model. But here it's F500L...
Is this normal?
[email protected] said:
Ok..So I tried as per above instructions.
The only change is it's written as "device" in place of "unauthorized". The serial number is the same.
I thought it would be written as LGH815...etc etc for the H815 model. But here it's F500L...
Is this normal?
Click to expand...
Click to collapse
Update:
Found something interesting as well.
The phone doesn't boot into recovery using hardware keys.
I tried with adb and got into a screen showing "No command" with red exclamation.
It means you don't have a working recovery partition now so something got borked. Best case scenario: do a full factory reinstall of the stock ROM and go from there, maybe, using Odin or whatever tool you prefer, these days I have no idea what software there is to be honest.
I don't own a G4 anymore either, but if I find one in good shape for a good price, like $50 or less, I'll more than likely grab it.
br0adband said:
It means you don't have a working recovery partition now so something got borked. Best case scenario: do a full factory reinstall of the stock ROM and go from there, maybe, using Odin or whatever tool you prefer, these days I have no idea what software there is to be honest.
I don't own a G4 anymore either, but if I find one in good shape for a good price, like $50 or less, I'll more than likely grab it.
Click to expand...
Click to collapse
Maybe I should just keep it as it is coz I don't even know what rom to use and actually which model it is.
[email protected] said:
Maybe I should just keep it as it is coz I don't even know what rom to use and actually which model it is.
Click to expand...
Click to collapse
Used to believe HTC devices are tough nuts to crack but LG just blowed me away.
Basically I want to downgrade from rbox's pre-rooted version 5.2.7.2_r1 back to 5.2.6.3_r1.
I use ADB via Windows 10 with no problems, I've access to SU, FireTV is rooted and TWRP 3.0.0.7 is installed.
In the past I would just boot into TWRP recovery and select any of rbox' pre-rooted rom and hit install/upgrade and all went well since 2016.
This is the first time trying to downgrade, TWRP recovery went well 5.2.6.3_r1 got installed, but no way to login into my Amazon A/C (kept saying login/password combinations not correct, but they were 100% correct).
One thing interesting is before I could see my bootloader as fully unlocked as "[email protected]", but now I see its only partial unlocked ([email protected])?
Update:
It seems like I do have rooo#bueller? from this picture after typing adb shell and su?
Any help will be much appreciated!
In regards to your original post on the bueller thread - have you tried re-enabling updates? A few other members here found that disabling updates on their sloane (see here) stopped them from using particular apps on 5.2.7.2 until they re-enabled updates, allowed the Fire TV to download updated apk files & then disabled them again
If that doesn't work: I had a Fire TV recently that I thought it was blacklisted by Amazon (wouldn't log in with the correct details), but turns out it was just never registered as a AFTV on their end & was being refused a connection. This obviously won't be your case, but something similar could be happening, so I would suggest you remove the device from your account (here: https://www.amazon.co.uk/hz/mycd/myx#/home/devices/1) & then attempt to log in again - if this doesn't work, maybe talk to Amazon via their live chat, ask them to register your device to your account manually (they'll happily do it) & attempt login again after a hour or two (that worked for me).
edit: I've just seen your latest post about bricking - general rule of thumb (as far as I'm aware) is that anything after 5.2.6.8 shouldn't be rolled back to pre-5.2.6.8 due to changes within the partitions, therefore, if you do so, you essentially brick your device after reboot as the prerooted zip only flashes boot/preloader/LK, then at boot, the rpmb checks to see if all those files match & when they don't, sends the device into a bootloop. If this was a Fire TV 2, you'd be in luck, but unfortunately, there doesn't seem to be any way to unbrick a Fire TV 1 on the latest software yet?
If you're bootloader unlocked, you might be able to get into fastboot & fix it from there, but I'm not clued up on the Fire TV 1 bl unlock unfortunately.
DanielF50 said:
I've just seen your latest post about bricking - general rule of thumb (as far as I'm aware) is that anything after 5.2.6.8 shouldn't be rolled back to pre-5.2.6.8
Click to expand...
Click to collapse
Completely right for the second gen fireTV :good:
But the first gen fireTV isn't a MTK SOC device, the SOC is from broadcom with different booting stages. In case of a rooted box, you can up- & downgrade to any fireOS 5 version if you like.
DanielF50 said:
there doesn't seem to be any way to unbrick a Fire TV 1 on the latest software yet?
Click to expand...
Click to collapse
There is a way, but it requires hardware (low voltage emmc adapter, a special sdcard reader, small soldering iron) and at least some soldering skills.
DanielF50 said:
If you're bootloader unlocked, you might be able to get into fastboot & fix it from there, but I'm not clued up on the Fire TV 1 bl unlock unfortunately.[/B]
Click to expand...
Click to collapse
Some guys have tried it, it's all in the bueller prerooted rom thread.
Hi Daniel, thanks for taking the time to write.
Yes my bootloader is fully unlocked, and my unit is rooted with TWRP installed.
Hi Sus_i, where are you at? If you can try the "hardware (low voltage emmc adapter, a special sdcard reader, small soldering iron)" thing on my FireTV, I will compensate you for your time and ship the unit to you (I'm near the border, so US/CAN addresses are fine with me).
Ok, this is what happened in my case:
My FireTV 1 background - bought directly from Amazon, rooted back in 2015/2016, bootloader fully unlocked and TWRP installed in 2017.
1) Was running on rbox's pre-rooted 5.2.6.3_r1
2) Updated to rbox's 5.2.7.2_r1 and discovered that upon resuming/waking up from sleep the unit always return to the Home page instead of whatever page/Tab you left it as in 5.2.6.3_r1, also Alexa and few other APPS were automatically installed in 5.2.7.2_r1.
I only use 4 APPS on my FireTV, an APK from my IPTV (90 %), VLC to watch videos from my own local Network (5%), CX_File Explorer to move/transfer files (3%) and NewPipe (alternative to YouTube) (2%).
rbox’s pre-rooted 5.2.6.3_r1 is perfect for my needs above, as I NEVER need to see the Amazon Home screen or any ads. Only the 1st time after a power off/on that I would ever see the Home page and from there on I would navigate to the “Settings” Tab – “Applications” Tab – “Manage Applications” and I only see a few pre-installed APPS from Amazon and my 4 APPS above and going to sleep mode and waking up sleep mode always stays in the “Manage Applications” Tab and NOT Amazon Home page as in 5.2.7.2_r1.
3) Flashing back from 5.2.7.2_r1 to 5.2.6.3_r1/5.2.7.0_r1/5.2.6.9_r1 to no avail because I would always get an error stating Login ID/password combinations were in errors (Login ID/password were 100% dead correct), also the Developer Options would also no longer showing under My Device/My FireTV Tab. Amazon FireTV support would be quick to add the FireTV under my profile (because they could see I bought it directly from them back in 2014 and they also could see my serial numbers and all along I was the only one registered for this unit), but still no go, so I tried to de-register/re-register again during all the testing and Amazon must had added the FireTV to my profile at least 10 times and in the end it escalated to the point they credited my account $25.00 (this is usually the price of the FireTV Stick 4K during sales/promotions) and also at the same time sent out a FireTV Stick 4K to me FOC.
I’m not a FireTV expert, but just an ordinary user with some sys/programming backgrounds during my early years. I reckon Amazon must had implemented some sort of hard coded checks either on their side (registration) or in the firmware since 5.2.6.3_r1.
4) So now my unit is flashed with 5.2.6.3_r1 and couldn’t get passed the registration screen, what do I do? I re-flash it to 5.2.7.2_r1 and bingo, everything is back to normal again and don’t even need to register the unit. (For testing purposes, I removed my A/C from the unit and re-register again and this time Login ID/password got no errors).
5) Thinking that back from Windows 98SE/2000/XP Pro/W7 Pro and now Windows 10 Pro, no matter what kind of messed I created, I would just format the drive/write zeros and re-image (Ghost image Back-ups) and everything would be normal again. My fireTV is rooted, bootloader is fully unlocked and TWRP installed, I told myself what’s there to afraid of , so I tried to re-flash 5.2.7.2_r1 to 5.2.6.3_r1/5.2.7.0_r1 and it would always back to the registration error and now double icons under settings, lol.
6) I suspect during one of the re-flash I made a mistake of after clearing/wipe Cache/Dalvik, instead of the default reboot, I ESC back out and redo the install/re-flash thinking that might get rids of all the leftovers that cause the double icons under Settings.
7) Now I’m left with the white Amazon logo on my TV screen and white pulsing light on the unit itself. I like to think that the motherboard or the power unit are still alive, just that the software part of it got messed up by ME big time!
Matt_7 said:
Now I’m left with the white Amazon logo on my TV screen and white pulsing light on the unit itself
Click to expand...
Click to collapse
Like DanielF50 said, as a first step you may try to connect with fastboot, use an usb a-to-a cable and run: fastboot devices
Sus_i said:
Completely right for the second gen fireTV :good:
But the first gen fireTV isn't a MTK SOC device, the SOC is from broadcom with different booting stages. In case of a rooted box, you can up- & downgrade to any fireOS 5 version if you like.
There is a way, but it requires hardware (low voltage emmc adapter, a special sdcard reader, small soldering iron) and at least some soldering skills.
Some guys have tried it, it's all in the bueller prerooted rom thread.
Click to expand...
Click to collapse
Good information to know, thanks Sus_i :good:
Reading Matt's response, it looks hopeful that he should be able to fastboot into the device to recover it then.
Sus_i said:
Like DanielF50 said, as a first step you may try to connect with fastboot, use an usb a-to-a cable and run: fastboot devices
Click to expand...
Click to collapse
OK, I'll get the USB A to A cable, how does one run the fastboot?
Once I connect the FireTV to my PC using the USB A- A cable, what will happen? do I need to install anything on my Windows 10 to run fastboot?
Update:
OK, dfound out I already have fastboot in my platform-tools folder,
From AFTNews:
Enter the command:
fastboot devices
If your computer has correctly detected your Fire TV, you will see a series of numbers followed by the word “fastboot” after entering the above command.
Download the latest version of ClockworkMod custom recovery from AFTVnews.com/recovery
Rename the file you just downloaded to “recovery.img”
Enter the command:
fastboot flash recovery recovery.img
(Be sure to replacerecovery.img with the full path to the file you just renamed)
Enter the command:
fastboot boot recovery.img
(Be sure to replacerecovery.img with the full path to the file you just renamed)
Your Fire TV should now boot into ClockworkMod recovery. Proceed to follow the steps in the next section below labeled “Resetting with Recovery Mode”.
Resetting with Recovery Mode
If you can successfully enter ClockworkMod recovery, then follow the below steps to reset your Fire TV, regardless of what state it is in and what has been done to it. You can also follow these steps if, for example, you want to update your ROM but aren’t sure if you’ve unlocked your bootloader or aren’t sure if you’ve installed the boot menu.
[OPTIONAL] From within ClockworkMod, select the option to “wipe data/factory reset”. This will delete all of your settings and user data. It is an optional step, but is recommended.
From within ClockworkMod, select the option to “wipe cache partition”.
Follow my guide to install pre-rooted Stock ROM version 51.1.4.0_514006420 updated. Note, you are NOT installing the latest pre-rooted ROM on purpose. Do NOT skip ahead and install the latest pre-rooted ROM.
Restart your Fire TV. You should be able to boot normally.
Follow my guide to install BusyBox.
Follow my guide to unlock your bootloader.
Follow my guide to install the boot menu.
Follow my guide to install the latest pre-rooted ROM.
Do I need to redo all these? I already have TWRP. If I'm to do the above I would end up with both TWRP recovery and ClockworkMod custom recovery, right?
Once done, do I actually install the 51.1.4.0_514006420 updated or 5.2.6.3_r1?
Pardon my ignorance!
Matt_7 said:
OK, I'll get the USB A to A cable, how does one run the fastboot?
Once I connect the FireTV to my PC using the USB A- A cable, what will happen? do I need to install anything on my Windows 10 to run fastboot?
Click to expand...
Click to collapse
Yep, bundled with android-sdk so runs just like you'd use adb, but obviously has a different purpose/commands - I should think there would be info on the full bootloader unlock thread on how to use it to recover from a bootloop using fastboot?
Matt_7 said:
Do I need to redo all these? I already have TWRP. If I'm to do the above I would end up with both TWRP recovery and ClockworkMod custom recovery, right?
Once done, do I actually install the 51.1.4.0_514006420 updated or 5.2.6.3_r1?
Pardon my ignorance!
Click to expand...
Click to collapse
You can try to boot the recovery.img (boot... not flash!)
This means, grab the latest prerooted, extract the recovery.img into the fastboot/adb folder. Check/connect with fastboot devices and run: fastboot boot recovery.img
In case this fails, you may carefully follow the guide you've posted above.
Sus_i said:
You can try to boot the recovery.img (boot... not flash!)
This means, grab the latest prerooted, extract the recovery.img into the fastboot/adb folder. Check/connect with fastboot devices and run: fastboot boot recovery.img
In case this fails, you may carefully follow the guide you've posted above.
Click to expand...
Click to collapse
OK, will try and report back.
I actually made a copy of "bueller-twrp_3.0.0-7.img", "bootmenu.img" and "recovery.img" which I copied from the FireTV before flashing, I reckon I can use the "recovery.img"?
Matt_7 said:
OK, will try and report back.
I actually made a copy of "bueller-twrp_3.0.0-7.img", "bootmenu.img" and "recovery.img" which I copied from the FireTV before flashing, I reckon I can use the "recovery.img"?
Click to expand...
Click to collapse
I would try to boot bueller-twrp_3.0.0-7.img and recovery.img
Update 3:
Gosh, I got it to the point of checking for updates and unplugged the internet cable hoping to issue via adb to block OTA, and the FireTV detected no internet connection and asked to unplug the power for a few minutes and I did that, but now no whatsoever light on the FIreTV itself, don't tell me its now dead not because I bricked it the other day, but because of the power unit?
Tested the power adapter with a multimeter, got 6.18V (6.25 is printed on the power adapter), since 6.18V is close to 6.25V, its not the power adapter right?
Update 2:
OK, figured out I could remove the USB A to A cable and use the USB port on the FireTV to connect my Logitech K400 ! (see, I'm not a very smart person!)
- I deleted "Data"
- Tried to wipe cache and got a message "No OS installed"
- No choice but to select install option and install 5.2.7.2_r1
- Now at least I'm seeing the Colourful Amazon logo again, and now its doing the "Optimizing system storage and applications...", wish me luck!
Update 1:
Just received my USB A to A Male to Male (LOL) cable today.
Don't know to jump for joy or cry!
- When I typed "fastbbot devices", I got exactly from "AFTNews - If your computer has correctly detected your Fire TV, you will see a series of numbers followed by the word “fastboot” after entering the above command.", I got the screen showing me my device/serial number and the word fastboot, so I think its working!
- I then typed "fastboot boot bueller-twrp_3.0.0-7.img" and the white Amazon logo was gone I was back in TWRP screen, but I couldn't do anything, the USB port is already used by the USB A to A cable (USB splitter couldn't work either), I see the mouse pointer, but how to move it to reboot/wipe/install/advance etc?
Mayday, help!
Matt_7 said:
Update 1:
Click to expand...
Click to collapse
:good:
Matt_7 said:
Update 2:
Click to expand...
Click to collapse
:good:
Matt_7 said:
Update 3:
Click to expand...
Click to collapse
Pull all the plugs from the box + tv and try again...
6.xx v seems ok. Any voltage drops if you connect a device, light bulb or anything like that?
Sus_i said:
: Any voltage drops if you connect a device, light bulb or anything like that?
Click to expand...
Click to collapse
Thanks Sus_i.
How to connect the light bulb to test, and connect from where to where?
I couldn't believe what a stupid move I did by pulling the internet cable and now I want to beat myself so bad...
I've a few power adapters from router/modem etc lying around, will I damage the Fire TV if I'm to try them out?
Matt_7 said:
Thanks Sus_i.
How to connect the light bulb to test, and connect from where to where?
Click to expand...
Click to collapse
Have you tried to pull all plugs, reconnect only the power supply... what does the LED?
There is an ifixit guide on how to disassemble the fireTV. In case you open the box, measure the voltage IN inside the fireTV at power on. You can measure VDD 3.3v and VDDQ 1.8v too, next to the emmc, see the picture here.
Matt_7 said:
I couldn't believe what a stupid move I did by pulling the internet cable and now I want to beat myself so bad...
Click to expand...
Click to collapse
That shouldn'd harm anything. In case of a failure, the fireTv should blink yellow.
Matt_7 said:
I've a few power adapters from router/modem etc lying around, will I damage the Fire TV if I'm to try them out?
Click to expand...
Click to collapse
You can test other adapters, someone on this forum said that he used an 5v usb supply, but for a 'stable use' you need a big one... regards the amps...
I think a power supply between 7v to 5v works fine, probably no damages at all.
Sus_i said:
Have you tried to pull all plugs, reconnect only the power supply... what does the LED?
There is an ifixit guide on how to disassemble the fireTV. In case you open the box, measure the voltage IN inside the fireTV at power on. You can measure VDD 3.3v and VDDQ 1.8v too, next to the emmc, see the picture here.
That shouldn'd harm anything. In case of a failure, the fireTv should blink yellow.
You can test other adapters, someone on this forum said that he used an 5v usb supply, but for a 'stable use' you need a big one... regards the amps...
I think a power supply between 7v to 5v works fine, probably no damages at all.
Click to expand...
Click to collapse
OK, will try to open up the FireTV.
No light/LED when plugging only the power adapter to the FIreTV, already tried different power outlets throughout the house
Come to the worst, will this https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 help?
Thanks again.
Matt_7 said:
Come to the worst, will this https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 help?
Click to expand...
Click to collapse
Worst case is a broken fireTV.
Don't follow this guide, you lose your unlock... apart from that, the download link from the guide is dead
Sus_i said:
Worst case is a broken fireTV.
Don't follow this guide, you lose your unlock... apart from that, the download link from the guide is dead
Click to expand...
Click to collapse
OK, will forget about that!
Once I got the FireTV opened, will take some pixs and report back!
OK, here are the pixs.
Now that I look at the Multimeter, I'm not sure I'm using it correctly. Bought this few years ago (just in case I need to test my car's battery).
AT the bottom of the multimeter, there are 3 holes, one red on each side and black hole in the center, which two am I supposed to use?
I tested the power adapter again with multimeter using the center black and red on the right, and I'm reading 4.2V?
Sus_i said:
Worst case is a broken fireTV.
Click to expand...
Click to collapse
Would it be possible just by looking at the board if its kaput?
Hi
I installed the German App Sky Ticket, unfortunately the program started.
I read that it is upgraded to root, wanted to make root returning and have
Uninstalled Magisk.
Unfortunately, the wrong way I have been stupid.
The stick is now in the bootlop for 20 minutes and then comes the Amazon login window
But unfortunately, the Firestick no longer recognizes connected devices.
And I can not enter any entry by keyboard or mouse.
Is there any hope or not?
Akki67 said:
Is there any hope or not?
Click to expand...
Click to collapse
Log-in there or wipe data and use the sticks setup...
Thanks @Sus_i Unfortunately, the remote control stops responding and also with
I do not come to a USB keyboard in the column of the username
and password.
So I can not log in.
If I want to be the Firestick 4k with Kamakiri-Mantis-V2.0.1, he does not find the stick, is always just "waiting of device" there and the script does not start.
Akki67 said:
If I want to be the Firestick 4k with Kamakiri-Mantis-V2.0.1, he does not find the stick, is always just "waiting of device" there and the script does not start.
Click to expand...
Click to collapse
You said something that you've uninstalled magisk in the first place, so the stick is already unlocked and you can use/try the boot-recovery.sh script in order to boot into twrp. Run the script then connect the stick via an usb cable. If you reach twrp, wipe data via commandline.
Thank you very much for your answer @Sus_i, the problem is yes if I connect the FIRETV 4K only with the USB data cable, it becomes aware of the Ganicht more perennous, the USB cable is only used as a power source.
Something must have disabled the USB socket, since yes zero commands arrive
And the FIRETV4K is no longer found as a medium.
I suspect that an update is transferred when uninstalling Magisk Amazon
has made the stick unusable.
Before I uninstalled Magisk, these 3 stuff installed on the 4K:
6.2.8.1_r3_4054_patched.zip
Patch - 6.2.
TZ Update - (TWRP) .zip8.1 (No Fota) .zip
Through this stupid action of, I have confirmed the emissions.
Akki67 said:
Thank you very much for your answer @Sus_i, the problem is yes if I connect the FIRETV 4K only with the USB data cable, it becomes aware of the Ganicht more perennous, the USB cable is only used as a power source.
Something must have disabled the USB socket, since yes zero commands arrive
And the FIRETV4K is no longer found as a medium.
I suspect that an update is transferred when uninstalling Magisk Amazon
has made the stick unusable.
Before I uninstalled Magisk, these 3 stuff installed on the 4K:
6.2.8.1_r3_4054_patched.zip
Patch - 6.2.
TZ Update - (TWRP) .zip8.1 (No Fota) .zip
Through this stupid action of, I have confirmed the emissions.
Click to expand...
Click to collapse
How did you uninstall Magisk?
@SweenWolf
Immediately after the start of Magisk was at the bottom of a yellow bar and there was uninstall, there was no error message.
As a result, I have given my Firestick 4k the death shock of great mis
Page out. The USB connection was thereby still laid down as I already
described.
The stick even appears on the network with IP address, but I can not help it.
Akki67 said:
@SweenWolf
Immediately after the start of Magisk was at the bottom of a yellow bar and there was uninstall, there was no error message.
As a result, I have given my Firestick 4k the death shock of great mis
Page out. The USB connection was thereby still laid down as I already
described.
The stick even appears on the network with IP address, but I can not help it.
Click to expand...
Click to collapse
You do not update/uninstall Magisk from Magisk Manager (App), if you do then it will cause the stick to not boot (if there are modifications made on the system).
I am unsure about the state of your system.
I think you should
Open TWRP
clean system, data, cache, Dalvik cache
Install ROM and start fresh.
If you can connect the stick with IP address then you can use SCRCPY to access your stick.
If the device is saying "Unauthorized" and you had installed "Launcher Manager" on it, then you can download "ADB_C.zip" from Launcher Manager page (If you haven't reset the stick)
If your TV supports CEC then you can use your TV to navigate around.
Thanks again to all helping.
@SweenWolf (do you understand German?)
Thank you for the good explanation, unfortunately I come with the tool scrcpy via IP
Not on the box, since ADB is still activated?
I do not come to the TWRP, Ganicht is displayed when booting
thus no newflash possible.
The stick always starts according to the same
Pattern c. 15 min. Always repeats the boot logo, then the screen is white
And then there is automatic login, see picture above.
No entry with the TV remote control possible despite CEC, otherwise that was
where the stick was still in order.
The only option would be about the IP address. There is a possibility ADB via WLAN
to activate at the Firestick 4k?
Slowly, I think the ideas and thank you again.
Akki67 said:
I do not come to the TWRP
Click to expand...
Click to collapse
Get an USB OTG cable, then you get a bootmenu at power on and you can select twrp. Use it together with a mouse/keyboard.
If your stick isn't recognized with the fireISO, you can also try ubuntu together with the boot-recovery.sh script.
If that won't work, you may unbrick with the bootrom-step + fastboot-step. How did you unlock the stick, with or without shorting? Kamakiri 2.0.1 works also without a short.
@Sus_i
When I had rooted him then with Fireiso Image then closed with wire short and the two
Files Bootrom-Step.sh and Fastboot-step.sh executed.
Unfortunately, this does not work if I put the wire on the contact and the USB cable
Pure corner, does not start the scripts and there is only the message there "Waiting for Device"
But no reaction.
As if the USB connection is death
I will now install Ubuntu on my computer and test again
thanks, Take me again
The Fire TV 4K Stick must be clinically death, I tried Ubuntu after 1 hour in the terminal Femster
Waiting for Device I canceled.
If you live in Germany @Sus_i I send you the deaths Firestick 4k and can try
Whether you manage to bring him back to life.
Thank you again for your help and thanks to SweenWolf
Akki67 said:
The Fire TV 4K Stick must be clinically death
Click to expand...
Click to collapse
Trade it in at amazon and get a new one...
Amazon.de: Fire Trade-In: Trade-In
Online-Einkauf von Fire Trade-In mit großartigem Angebot im Trade-In Shop.
www.amazon.de
Thanks for the link But the Fire TV Stick 4K is not listed in the trade in the program.
Will dispose of him or place on Ebay.
Akki67 said:
Thanks for the link But the Fire TV Stick 4K is not listed in the trade in the program.
Click to expand...
Click to collapse
I know this, but if you click at the 2gen stick and trade it in (only stick), probably no one cares... Worst case is they ship it back to you.
Ebay is also ok, I guess someone will pick it up and try the unbrick solution
Akki67 said:
Thanks for the link But the Fire TV Stick 4K is not listed in the trade in the program.
Will dispose of him or place on Ebay.
Click to expand...
Click to collapse
Try lsusb with watch and then attach the stick to your PC, and check if its getting detected or not, you can try changing your USB cable and make sure you the cable has wires for DATA in it.
I do not know german so its getting a bit confusing.
If its taking long time to boot then it can be caused by system services not starting due to some reasons.
If on windows check in Device Manager if its visible in it, and check if plugging/unplugging the stick is causing the console to refresh or not.
@SweenWolf and @Sus_i
I have followed your advice and called the device manager in Win 10. When I connected the FIRETV 4K Stick to the USB cables, this new entry "MT65xxPreloader" under other devices was gone again for 3 seconds.
Can you do something with it, there is something to save?
After 15 minutes this entry appears MTP-USB device, that looks good right?
Which driver or how would I have to proceed?
After 15 minutes this entry appears MTP-USB device, that looks good right?
Which driver or how would I have to proceed?
Have it again with Ubuntu and the KamakiriMantis-V2.0.1.zip on the USB 2 port, but he will find the stick from this error message:
[email protected]:~/Schreibtisch/test/kamakiri-mantis-v1.2/kamakiri$ sudo ./bootrom-step.sh
[sudo] Passwort für akki:
[2022-04-24 23:33:48.695287] Waiting for bootrom
[2022-04-24 23:33:58.244631] Found port = /dev/ttyACM0
[2022-04-24 23:33:58.245259] Handshake
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 119, in <module>
main(dev)
File "main.py", line 24, in main
load_payload(dev)
File "/home/akki/Schreibtisch/test/kamakiri-mantis-v1.2/kamakiri/modules/load_payload.py", line 45, in load_payload
dev.handshake()
File "/home/akki/Schreibtisch/test/kamakiri-mantis-v1.2/kamakiri/modules/common.py", line 97, in handshake
c = self._writeb(b'\xa0')
File "/home/akki/Schreibtisch/test/kamakiri-mantis-v1.2/kamakiri/modules/common.py", line 92, in _writeb
return self.dev.read()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 509, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
Why could it be?
Thanks for your help you since top !!!
Akki67 said:
@SweenWolf and @Sus_i
I have followed your advice and called the device manager in Win 10. When I connected the FIRETV 4K Stick to the USB cables, this new entry "MT65xxPreloader" under other devices was gone again for 3 seconds.
Can you do something with it, there is something to save?
After 15 minutes this entry appears MTP-USB device, that looks good right?
Which driver or how would I have to proceed?
After 15 minutes this entry appears MTP-USB device, that looks good right?
Which driver or how would I have to proceed?
Regards
Click to expand...
Click to collapse
https://developer.samsung.com/sdp/file/17a610e4-ce96-4291-8757-37f2134fb37e
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Download these files and install (for Windows)
Reboot the Computer
Open "Terminal" or Command Prompt or PS
And type
Code:
adb devices
or
Code:
./adb devices
if running from PS
There should be a device, most likely unauthorized.
If you see "device" then you can use SCRCPY to control the device using ADB.
If you have used "Launcher Manager" and authorized its key then you can use
https://forum.xda-developers.com/attachments/adb_c-zip.5562577/
Simply extract and run the ADB_C.exe
And then run SCRCPY
After restarting the stick, the Bootsqenz ran for 20 minutes. Then stood down to the right is loaded And the Amazon Authoring Image Schrim came back.
In the device manager is re-available ontort portable devices MTP USB Device
But when I add ADB Devices no devices found, because before the Crash USB debugging
Not yet activated and I had not installed the Launcher Manager yet.
Scrcpy does not find anything.
The only way would be over Ubuntu, but there was this error message, what
Does that really say?
I think,
You have not enabled ADB debugging let alone authorized it.
When you uninstalled magisk it restored stock boot.img which restored the TWRP with stock one, so preloader exploit is gone now, and now because you have stock boot image with some system changes, (it should fail dm-verity) its not allowing system to boot.
You wrote you installed the Patch 6.2.8.1, in yhe post i wrote it requires a patched boot image, install magisk or flash my patched boot image, in this case i assume and am pretty sure you went with magisk only, which on installation caused this, you could have installed my patched boot.img then flash magisk on it.
In short:
Your TWRP is gone.
You cannot use OTG to fix your stick.
You may have cleared the /data and ADB is now turned off. So you will not be able to use ADB also.
If you efuse is intact then you WILL HAVE to follow unlock procedure to apply preloader exploit.