Related
Turned my Fire TV on to an update notification. Updated hoping for more features, i.e.Prime Music use but to no avail. It also had the added (dis)benefit of disabling root and preventing towelroot from reenabling. Any thoughts?
One interesting thing I found out is that it is possible to enable installation from unknown sources with out editing the original settings.apk.
halftonehero said:
Turned my Fire TV on to an update notification. Updated hoping for more features, i.e.Prime Music use but to no avail. It also had the added (dis)benefit of disabling root and preventing towelroot from reenabling. Any thoughts?
One interesting thing I found out is that it is possible to enable installation from unknown sources with out editing the original settings.apk.
Click to expand...
Click to collapse
So you're the second person to claim to have gotten an update. I still haven't gotten it. I'd be curious to see if they've patched the bootloader. I'll have to wait until @AFTVnews.com or I get the update and get the URL to examine it. It's possible you'll be able to downgrade, but without knowing what was in the update I'm not going to encourage such an action. But if you want to try it out on your own, go right ahead. There are instructions and URLs in a few posts here. Just know if they updated the bootloader and turn on anti-downgrade flags, it might brick.
rbox said:
So you're the second person to claim to have gotten an update. I still haven't gotten it. I'd be curious to see if they've patched the bootloader. I'll have to wait until @AFTVnews.com or I get the update and get the URL to examine it. It's possible you'll be able to downgrade, but without knowing what was in the update I'm not going to encourage such an action. But if you want to try it out on your own, go right ahead. There are instructions and URLs in a few posts here. Just know if they updated the bootloader and turn on anti-downgrade flags, it might brick.
Click to expand...
Click to collapse
One of my Fire TV's tends to get updates early so hopefully it'll get updated tomorrow. I'll be sure to set it up to sniff out the update URL.
Thanks for the insight. I'll wait on downgrading at the moment with no know brick recovery method. I wonder if the other numerous one clicks used the same method as geohots?
halftonehero said:
Turned my Fire TV on to an update notification. Updated hoping for more features, i.e.Prime Music use but to no avail. It also had the added (dis)benefit of disabling root and preventing towelroot from reenabling. Any thoughts?
One interesting thing I found out is that it is possible to enable installation from unknown sources with out editing the original settings.apk.
Click to expand...
Click to collapse
Do you have a new version number you can provide us?
mcsephoenix said:
Do you have a new version number you can provide us?
Click to expand...
Click to collapse
51.1.2.0_user_512073320 according AFTV.com
Downgrade To Previous Firmware
Would downgrading to previous firmware update allow for the ability to root the Fire TV?
EDIT: Will be receiving a new Fire TV from Amazon tomorrow and if it comes with the new firmware update, I'll downgrade and report on whether it works or not. Nothing to lose on my part if it bricks as I will be able to return it to Amazon.
mjbxx said:
Would downgrading to previous firmware update allow for the ability to root the Fire TV?
EDIT: Will be receiving a new Fire TV from Amazon tomorrow and if it comes with the new firmware update, I'll downgrade and report on whether it works or not. Nothing to lose on my part if it bricks as I will be able to return it to Amazon.
Click to expand...
Click to collapse
Downgrading requires the FTV to be rooted in the first place to be able to push the update.zip to the proper location.
Edit: I noticed recovery mode (following steps here) has an option to "Update from ADB" (I assume this would use ADB sideload). However, since the FTV doesn't have an accessible USB client port, I'm not sure how or if this would work (unless they build network drivers into the recovery partition).
If this was figured out, that could be a possible method of downgrading.
elmerohueso said:
Downgrading requires the FTV to be rooted in the first place to be able to push the update.zip to the proper location.
Edit: I noticed recovery mode (following steps here) has an option to "Update from ADB" (I assume this would use ADB sideload). However, since the FTV doesn't have an accessible USB client port, I'm not sure how or if this would work (unless they build network drivers into the recovery partition).
If this was figured out, that could be a possible method of downgrading.
Click to expand...
Click to collapse
If network support was available in recovery... how would we know the ip address? I am wondering if there might USB support in recovery for ADB with male/male cable.... I don't happen to have one to test... anyone else?
I imagine the IP address would be the same but it would utilize a different port
tselling said:
If network support was available in recovery... how would we know the ip address?
Click to expand...
Click to collapse
Check the DHCP tables in your router to see which IPs have been leased to which device.
tselling said:
If network support was available in recovery... how would we know the ip address? I am wondering if there might USB support in recovery for ADB with male/male cable.... I don't happen to have one to test... anyone else?
Click to expand...
Click to collapse
I have tested this with no luck. Plugging in a male/male USB cable while on that recovery screen does nothing. The Fire TV is not seen by the PC.
I may be wrong about this, but the problem is that in order to get to that recovery screen, the Fire TV has to be in USB Host Mode. This is what allows it to recognize commands from a USB keyboard. In order to use ADB via USB and transfer the update package, the Fire TV needs to be in USB Accessory Mode. When "Update via USB" is selected, the Fire TV does not switch to USB Accessory Mode. It stays in USB Host Mode.
The only way I know of for the Fire TV to be in USB Accessory mode, is to connect the Fire TV to a PC via a male/male cable while it is powered off, and then power the Fire TV on. In this setup, it sees that it's connected to a PC and enables fastboot via USB with the USB set to Accessory Mode. In this state, plugging in a keyboard does nothing which means there is no way to get to recovery.
elmerohueso said:
Check the DHCP tables in your router to see which IPs have been leased to which device.
Click to expand...
Click to collapse
I do not believe that work if it uses a default IP address like many devices do for setup rather than dhcp.
tselling said:
I do not believe that work if it uses a default IP address like many devices do for setup rather than dhcp.
Click to expand...
Click to collapse
There is no networking code in the stock recovery. DHCP or explicit ip addresses.
rbox said:
There is no networking code in the stock recovery. DHCP or explicit ip addresses.
Click to expand...
Click to collapse
I wonder if there is a way to send our own update via network by somehow spoofing the update server that amazon uses.
tselling said:
I wonder if there is a way to send our own update via network by somehow spoofing the update server that amazon uses.
Click to expand...
Click to collapse
MITM'ing an update to the firetv is easy. But making the Fire TV download it is the hard part. When it checks for updates its a complicated encrypted exchange between the firetv and the amazon servers. I tried spoofing that and it was rejected because of the hashes. So if the firetv wants to already download an update, it would be possible for it to download something else. But that something else would still need to be a valid signed update. Can't make it download and update random code.
AFTVnews.com said:
...The only way I know of for the Fire TV to be in USB Accessory mode, is to connect the Fire TV to a PC via a male/male cable while it is powered off, and then power the Fire TV on. In this setup, it sees that it's connected to a PC and enables fastboot via USB with the USB set to Accessory Mode. In this state, plugging in a keyboard does nothing which means there is no way to get to recovery.
Click to expand...
Click to collapse
Hi,
because I'm new at the AFTV and it's just ordered (I prefer to have it at my hands when I post ideas ) BUT what will happen, if you use your described way to get it to connect to PC, but not using power off/on , but using 'adb reboot recovery' via network?
BTW: OT does 'Image Verification' will stop after a count of posts or do I have to do it always?
got this update today by auto update (got the box and tried blocking domains but doesn't work)
51.1.3.0_user_513011820
any chance to root or downgrade the box now or just replace it by amazon?
Hitchi said:
got this update today by auto update (got the box and tried blocking domains but doesn't work)
51.1.3.0_user_513011820
any chance to root or downgrade the box now or just replace it by amazon?
Click to expand...
Click to collapse
I feel sorry for you Bro, same here. Hope that towelroot or an other solution will come soon.
RA
Hitchi said:
got this update today by auto update (got the box and tried blocking domains but doesn't work)
51.1.3.0_user_513011820
any chance to root or downgrade the box now or just replace it by amazon?
Click to expand...
Click to collapse
Do you have a German Fire TV? I'm trying to determine if this new update is only being pushed to German Fire TVs.
So I have received a replacement FTV and I believe it to be rootable because it does not go to the German language in the beginning screen.
Problem I am having is I blocked the updates in my router and I can't complete the initial set up. It sends a lot of time on:
"We are trying to update your Amazon Fire TV but we cannot contact our services. We will keep trying. Please do not disconnect from the network or unplug the power cable."
Then it goes to a screen that says:
"Unable to update your Amazon Fire TV
Try disconnecting the power cable for a few seconds and then plugging it back in.
If that does not work, please try again later or contact us at www.amazon.com/firetvsupport."
Any idea how to get past this without the update?
Thanks for the help guys!
I got past it by using open dns to block the update urls instead of directly blocking on router. Then after I got past it, I switched back to blocking on router directly and disabled the update program on firetv itself.
I don't understand how opendns.com will work for this? If that works would privateinternetaccess.com also work? I normally am running pptp with them for added security as I browse or do whatever I do.
draky said:
So I have received a replacement FTV and I believe it to be rootable because it does not go to the German language in the beginning screen.
Problem I am having is I blocked the updates in my router and I can't complete the initial set up. It sends a lot of time on:
"We are trying to update your Amazon Fire TV but we cannot contact our services. We will keep trying. Please do not disconnect from the network or unplug the power cable."
Then it goes to a screen that says:
"Unable to update your Amazon Fire TV
Try disconnecting the power cable for a few seconds and then plugging it back in.
If that does not work, please try again later or contact us at www.amazon.com/firetvsupport."
Any idea how to get past this without the update?
Thanks for the help guys!
Click to expand...
Click to collapse
If you are blocking the update server and get this it 99% mean it's running 51.1.0 and the first update it will take is 51.1.0.2. Then it'll try to update to the latest. If that's the case, you need to unblock the servers, let it download the update, and then when it reboots to install it, reblock them.
rbox said:
If you are blocking the update server and get this it 99% mean it's running 51.1.0 and the first update it will take is 51.1.0.2. Then it'll try to update to the latest. If that's the case, you need to unblock the servers, let it download the update, and then when it reboots to install it, reblock them.
Click to expand...
Click to collapse
So I let the system download the first update, unplugged the ethernet line as it restarted. Then I blocked the updates sites and plugged it back in... Now I'm sitting at sw version 51.1.4.0. Guessing there's nothing I can do about it now...
draky said:
So I let the system download the first update, unplugged the ethernet line as it restarted. Then I blocked the updates sites and plugged it back in... Now I'm sitting at sw version 51.1.4.0. Guessing there's nothing I can do about it now...
Click to expand...
Click to collapse
Really, there is no way to bypass a forced update... but it finally looks like they've caught on to us. Doesn't seem like good news.
draky said:
Any idea how to get past this without the update?
Click to expand...
Click to collapse
Hi,
i have the same problem.
Trying to finish initial setup without updating firmware.
At first start, Network found and started downloading Update.
So i turned it off and blocked the updateserver at router.
But can´t pass setup this way...
There's a guide on AFTVNews on how to bypass the mandatory update. Does that guide no longer work?
I wiped and installed latest pre-rooted software and could not get past checking for updates using blocks on router. Switched to open dns and went right through. Then I switched back to router. Just my experience.
16Darknight said:
There's a guide on AFTVNews on how to bypass the mandatory update. Does that guide no longer work?
Click to expand...
Click to collapse
it still works,
thank you
I know this is too late for OP, but incase someone comes across this thread looking for an answer, here is my guide to bypass the forced update:
http://www.aftvnews.com/how-to-get-passed-a-forced-software-update-on-the-amazon-fire-tv/
AFTVnews.com said:
I know this is too late for OP, but incase someone comes across this thread looking for an answer, here is my guide to bypass the forced update:
http://www.aftvnews.com/how-to-get-passed-a-forced-software-update-on-the-amazon-fire-tv/
Click to expand...
Click to collapse
And looks like I may get lucky... After it was funny loaded up I immediately preformed a master reset on the device just to see if everything took or if I happened to get lucky and something didn't load right and I was right. I go in, choose my language, put in my amazon account (it knows when I put in the wrong account) and then tries to register the device and while it's doing that it's flashing back and forth with a screen that says it doesn't have network connectivity but the box still has the white light.
I plug in my old box, lights up and connects just fine. I let it sit tonight for 20 minutes and still didn't work right so I'll be calling them tomorrow to see about replacing this one. Looks like the software update maybe didn't get loaded right.
I got through the initial setup following AFTVnews guide. Unluckily my Gernan FTV was on 5.1.3.0 from the start on, so i can't root and use the update blocking tool. Still having the update servers blocked the FireTV is almost unusable since it complains about not having a network connection. XBMC works fine but i can't use Amazon instant video. I blocked amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
via router. any advice what i can change to continue blocking updates, but still access Amazon content?
Gesendet von meinem SM-N9005 mit Tapatalk
{ParanoiA} said:
I wiped and installed latest pre-rooted software ...
Click to expand...
Click to collapse
Beginning with which version, please?
Was on whatever came before 51.1.4.0 and did full wipe and then installed 51.1.4.0 and that's when I had to use opendns. After that I just flashed 51.1.4.1 over top of it because of the requirements.
{ParanoiA} said:
Was on whatever came before 51.1.4.0 and did full wipe and then installed 51.1.4.0 and that's when I had to use opendns. After that I just flashed 51.1.4.1 over top of it because of the requirements.
Click to expand...
Click to collapse
Bummer. It was 51.1.1.0 or earlier.
Wishful thinking...
What I've discovered is in the serial number range of the units themselves. If the unit has a serial of 7090020141....anything after that from 0 to 4 will not root....it will automatically jump to the "your unit requires an update" screen...no way around it. If the serial is 7090020141.....5 and above it will root.
I have rooted almost 100 units in the past 2 weeks and it is the same every time.... Perhaps I'm wrong....but I think not.
At this point I can look at the serial and tell you if it will root or not.
I have 3 rooted Fire TVs (4K and standard).
I believe they recently tried to take an update (though I thought I had it blocked).
At any rate, they all are falling back to TWRP no matter what I try to do. They also all fail to mount cache. If I try to do anything in TWRP from wiping to anything I get mounting errors. I can flash a new image but on system reboot they always fail to launch. I've tried a couple of things I've seen online about ext4 and changing file system and same errors. They were all running the latest rbox pre-rooted images (july release)
Any suggestions on recoverying these Ftvs?
Thanks
Endosmok said:
I have 3 rooted Fire TVs (4K and standard).
I believe they recently tried to take an update (though I thought I had it blocked).
At any rate, they all are falling back to TWRP no matter what I try to do. They also all fail to mount cache. If I try to do anything in TWRP from wiping to anything I get mounting errors. I can flash a new image but on system reboot they always fail to launch. I've tried a couple of things I've seen online about ext4 and changing file system and same errors. They were all running the latest rbox pre-rooted images (july release)
Any suggestions on recoverying these Ftvs?
Thanks
Click to expand...
Click to collapse
No suggestions on how to fix, but my Fire TV 1 is doing the same thing. I'm rooted with rbox 5.2.4.1 and it is trying to update to 5.2.6.0. I wondered why i kept checking box and it was in TWRP.
dk1keith said:
No suggestions on how to fix, but my Fire TV 1 is doing the same thing. I'm rooted with rbox 5.2.4.1 and it is trying to update to 5.2.6.0. I wondered why i kept checking box and it was in TWRP.
Click to expand...
Click to collapse
still not sure what has caused it but used this method 1 http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/ to re-block updates. it survived a reboot also.
Thanks... I tried but without success... I seemed to have lost root but still have TWRP. Any adb shell command kicks me back to not found. Did you still have root when you tried or?
dk1keith said:
still not sure what has caused it but used this method 1 http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/ to re-block updates. it survived a reboot also.
Click to expand...
Click to collapse
Endosmok said:
Thanks... I tried but without success... I seemed to have lost root but still have TWRP. Any adb shell command kicks me back to not found. Did you still have root when you tried or?
Click to expand...
Click to collapse
I still had root. To disable updates I had to adb shell and su to execute the disable.
I’m having same issue on my 1st gen ftv, I was able to disable the ota, hope this fixes the reboot.
Thanks
justdoit2552 said:
I’m having same issue on my 1st gen ftv, I was able to disable the ota, hope this fixes the reboot.
Thanks
Click to expand...
Click to collapse
Update,disabling the update helped solve this issue.
Or you could just update to the latest rooted version.
My friend has a fire tv 2 box sloane.
we've tried everything to update including contacting Amazon support for remote assistance and factory resetting multiple times.
We can't use YouTube TV without updating.
I'm good with Android and kkow how to use adb.
Can I force flash the stock firmware to update past 5.2.6.0? If so how?
dovedescent7 said:
My friend has a fire tv 2 box sloane.
we've tried everything to update including contacting Amazon support for remote assistance and factory resetting multiple times.
We can't use YouTube TV without updating.
I'm good with Android and kkow how to use adb.
Can I force flash the stock firmware to update past 5.2.6.0? If so how?
Click to expand...
Click to collapse
I had a box the other week that was on 5.2.7.3 so the issue isn't if it only updates to your current version.
There may be a corrupted ota update apk in your build, have you made sure that ota updates are enabled in >settings>my firetv and tried the adb commands to make sure they are actually enabled?
Sent from my SM-G935F using Tapatalk
I haven't run adb commands on it yet nor any fire device only android phones. I don't physically get the box in my possesion again until this weekend.
That's why I'm asking though...
Can I simply flash firmware in the stock recovery? Like via USB?
Whats the gist of recovering this aftv besides factory reset in settings?
dovedescent7 said:
I haven't run adb commands on it yet nor any fire device only android phones. I don't physically get the box in my possesion again until this weekend.
That's why I'm asking though...
Can I simply flash firmware in the stock recovery? Like via USB?
Whats the gist of recovering this aftv besides factory reset in settings?
Click to expand...
Click to collapse
Sorry to hear the factory reset process didn't work for you, I suspect there may be a problem with the update protocol (either system or the ota apk). Maybe someone can correct me if I'm wrong?
Please Note :This method requires a Linux installation either on a pc or live USB.
To flash firmware to your device you will have to unlock it first as per OP unlock instructions.
Here:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
This will unlock your box bootloader and install TWRP.
After TWRP is installed you can then choose what ever firmware(s) pre rooted you want for the box.
The general unlocking process is quite simple. If your friend is game for it being opened, shorted and unlocked that is.
You will first have to get acquainted with adb and boot your pc from a Linux installation or Linux distro Live USB to complete the amonet script process.
(This is the amazing program that flashes the TWRP custom recovery to your device)
All of this may sound quite daunting and bewildering but this box is easy to unlock.
It is totally upto you but this is the only way I can see for you to gain control over your friends box and upgrade the firmware.
The guys here will be there should you need help at anytime.
Regards
R.
Sent from my SM-G935F using Tapatalk
Bertonumber1 said:
Sorry to hear the factory reset process didn't work for you, I suspect there may be a problem with the update protocol (either system or the ota apk). Maybe someone can correct me if I'm wrong?
Please Note :This method requires a Linux installation either on a pc or live USB.
To flash firmware to your device you will have to unlock it first as per OP unlock instructions.
Here:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
This will unlock your box bootloader and install TWRP.
After TWRP is installed you can then choose what ever firmware(s) pre rooted you want for the box.
The general unlocking process is quite simple. If your friend is game for it being opened, shorted and unlocked that is.
You will first have to get acquainted with adb and boot your pc from a Linux installation or Linux distro Live USB to complete the amonet script process.
(This is the amazing program that flashes the TWRP custom recovery to your device)
All of this may sound quite daunting and bewildering but this box is easy to unlock.
It is totally upto you but this is the only way I can see for you to gain control over your friends box and upgrade the firmware.
The guys here will be there should you need help at anytime.
Regards
R.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Bummer, so the new methods referenced here in below link dont work then ?
AFTVnews is saying that i can root with new method?
Is this fake news? lol
https://www.aftvnews.com/amazon-fire-tv-2-box-running-latest-software-version-has-been-rooted/
.
.
.
.
dovedescent7 said:
Bummer, so the new methods referenced here in below link dont work then ?
AFTVnews is saying that i can root with new method?
Is this fake news? lol
https://www.aftvnews.com/amazon-fire-tv-2-box-running-latest-software-version-has-been-rooted/
.
.
.
.
Click to expand...
Click to collapse
No, it works up to 5.2.6.9
Sus_i said:
No, it works up to 5.2.6.9
Click to expand...
Click to collapse
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
Click to expand...
Click to collapse
As stated by @Sus_i the diplomatic mediatek exploit will only work upto version 5.2.6.9. Any higher version of fireos then you will have to use the hardware root, twrp method from the thread I posted above.
Good you are familiar with Ubuntu/Linux as the commands for the script will be run through terminal with the downloadable amonet script in the thread.
After you've installed/updated adb+fastboot py serial through command line of your Linux install. You're ready to open up your device, and refer to the dat0 located in the photo of OP
Sent from my SM-G935F using Tapatalk
Bertonumber1 said:
As stated by @Sus_i the diplomatic mediatek exploit will only work upto version 5.2.6.9. Any higher version of fireos then you will have to use the hardware root, twrp method from the thread I posted above.
Good you are familiar with Ubuntu/Linux as the commands for the script will be run through terminal with the downloadable amonet script in the the thread.
After you've installed/updated adb+fastboot py serial through command line of your Linux install. You're ready to open up your device, and refer to the dat0 located in the photo of OP
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thank you. I get a little confused on version numbers with this thing. Does fire tv sw/fw go up like normal fw? Like does it go 5.2.6.0 then 5.2.6.1 and so on?
I have:
5.2.6.0 so this one can be done with software method?
5.2.7.4 this one has to be done by shorting internal stuff+linux right?
dovedescent7 said:
Thank you. I get a little confused on version numbers with this thing. Does fire tv sw/fw go up like normal fw? Like does it go 5.2.6.0 then 5.2.6.1 and so on?
I have:
5.2.6.0 so this one can be done with software method?
5.2.7.4 this one has to be done by shorting internal stuff+linux right?
Click to expand...
Click to collapse
Yes I had to edit the post there as i got confused myself, I had wrote 5.2.7.0 lol.
So just to clarify 5.2.6.9 and under you can use mediatek software root.
5.2.7.0 and over requires the hardware short method.
Sent from my SM-G935F using Tapatalk
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
Click to expand...
Click to collapse
Lets say, it 'should' work :good:
I don't know if someone tested it on your OS version, because it's much older than the exploit itself.
The most current OS version back then was 5.2.6.8, the mtk root method came up and everybody was happy, finally a new root method for the second gen box
Big A patched it with 5.2.7.0.
Needless to say that most people tested it on 5.2.6.8 and .9.
It may be that the exploit isn't adapted to your OS version, but who knows.
Let us know what happens.
Good luck
Perfect thank you for the clarification.
One last question?
I messed up, I factory reset ftv 2 box using my tvs remote and now cannot set it up because my ftv remote is broken/or this particular ftv2 box doesn't pair with Amazon remotes.
Is it possible to somehow setup fire tv (from setup screen after factory reset) without a fire tv remote?
dovedescent7 said:
Perfect thank you for the clarification.
One last question?
I messed up, I factory reset ftv 2 box using my tvs remote and now cannot set it up because my ftv remote is broken/or this particular ftv2 box doesn't pair with Amazon remotes.
Is it possible to somehow setup fire tv (from setup screen after factory reset) without a fire tv remote?
Click to expand...
Click to collapse
Ok, I see. You could try it this way:
-remove the batteries, then press 30 seconds the home button.
-Put new fresh batterys back in.
-Try to pair the remote again, but keep pressing the home button for at least 30 seconds.Do that again and again...
Could be that it takes some time (and attempts), until the remote connects.
If it won't work and you don't know someone with a remote near to you, take a look for a guide with a usb keyboard or so at www.aftvnews.com or xda forums search.
Sus_i said:
Ok, I see. You could try it this way:
-remove the batteries, then press 30 seconds the home button.
-Put new fresh batterys back in.
-Try to pair the remote again, but keep pressing the home button for at least 30 seconds.Do that again and again...
Could be that it takes some time (and attempts), until the remote connects.
If it won't work and you don't know someone with a remote near to you, take a look for a guide with a usb keyboard or so at www.aftvnews.com or xda forums search.
Click to expand...
Click to collapse
THANKS!
NOW I NEED URGENT HELP
Rooted ftv 2 with short method now stuck at twrp.
Can i simply now install prerooted rom from within TWRP via rom on SD card?
edit
so I rooted aftv 2 box with shorting method then got into twrp. Then flashed prerooted fire tv image but when I rebooted it gets stuck on amazon fire tv splash screen and won't move.
I tried clearing cache 1x in TWRP afterwards, then reboot but still hangs at Amazon boot.
What am I missing?
dovedescent7 said:
edit
so I rooted aftv 2 box with shorting method then got into twrp. Then flashed prerooted fire tv image but when I rebooted it gets stuck on amazon fire tv splash screen and won't move.
I tried clearing cache 1x in TWRP afterwards, then reboot but still hangs at Amazon boot.
What am I missing?
Click to expand...
Click to collapse
Have you flashed this way, first the 5.2.6.7_v2 and then a later 5.2.7.x one? It's mentioned in the prerooted thread.
Wipe cache and dalvik before you reboot.
If it won't boot, you probably need to wipe data and internalsd too. Best is to use the 'format' data tab in TWRPs wipe section.
After that, the box should boot, but you need to log on at the setup, pair the remote and so on...
dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
Click to expand...
Click to collapse
I just did this on a used device I purchased that came with 5.2.6.7 and it worked perfectly. Follow the instructions and you'll have no issues and none of that jumper stuff.
Bought an older stick from some guy and it couldn't get updates or register (even entering amazon user/pass showed error saying credentials are not correct).
It had TWRP so I thought maybe just needs to be restocked. I first updated the firmware to 6.2.8.9 (still wouldn't work, still same issues) so I decided to get rid of TWRP as well and flashed the boot image. OK TWRP is gone but the issues are still there even after multiple factory resets.
Have I messed it up for good? Any chance to fix it? I since got another 4K stick, brand new, and that one worked like a charm, of course; also my older Fire Cube works fine. So it's not some issue with my network.
primusmagestri said:
Bought an older stick from some guy and it couldn't get updates or register (even entering amazon user/pass showed error saying credentials are not correct).
It had TWRP so I thought maybe just needs to be restocked. I first updated the firmware to 6.2.8.9 (still wouldn't work, still same issues) so I decided to get rid of TWRP as well and flashed the boot image. OK TWRP is gone but the issues are still there even after multiple factory resets.
Have I messed it up for good? Any chance to fix it? I since got another 4K stick, brand new, and that one worked like a charm, of course; also my older Fire Cube works fine. So it's not some issue with my network.
Click to expand...
Click to collapse
you should not remove twrp. Your Firestick is soft bricked
primusmagestri said:
Bought an older stick from some guy and it couldn't get updates or register (even entering amazon user/pass showed error saying credentials are not correct).
It had TWRP so I thought maybe just needs to be restocked. I first updated the firmware to 6.2.8.9 (still wouldn't work, still same issues) so I decided to get rid of TWRP as well and flashed the boot image. OK TWRP is gone but the issues are still there even after multiple factory resets.
Have I messed it up for good? Any chance to fix it? I since got another 4K stick, brand new, and that one worked like a charm, of course; also my older Fire Cube works fine. So it's not some issue with my network.
Click to expand...
Click to collapse
The stick is most likely blacklisted, common reason is if the device gets reported as stolen... lost on shipping or something like that.
You can still use the unlocked stick, somewhere in the forums is a posting about this. If I recall right, you would need to disable OOBE, set the props for adb enabled, device registered / setup completed. Then the stick boots straight into the fireOS launcher, now you can install a custom launcher...
Sus_i said:
The stick is most likely blacklisted, common reason is if the device gets reported as stolen... lost on shipping or something like that.
You can still use the unlocked stick, somewhere in the forums is a posting about this. If I recall right, you would need to disable OOBE, set the props for adb enabled, device registered / setup completed. Then the stick boots straight into the fireOS launcher, now you can install a custom launcher...
Click to expand...
Click to collapse
he removed twrp and he have 6.2.8.9. He cant install jailbreak now
anphabvn said:
he removed twrp and he have 6.2.8.9. He cant install jailbreak now
Click to expand...
Click to collapse
That is not true.
He installed 6.2.8.9 via TWRP and a boot.img, so the efuse for shorting may be gone (if he flashed a TZ image update at some point too, which we don't know).
Anyways. TWRP will block flashing preloader/LK and TZ images from the stock rom, so the old vulnerable preloader is still on his stick installed, therefore he CAN install the jailbreak again, that's for sure
In order to block the expoit, he need to do at least one update with the stock recovery (which will flash the new preloader). Only that will block the latest kamakiri 2.0.1.
anphabvn said:
you should not remove twrp. Your Firestick is soft bricked
Click to expand...
Click to collapse
Sus_i said:
The stick is most likely blacklisted, common reason is if the device gets reported as stolen... lost on shipping or something like that.
You can still use the unlocked stick, somewhere in the forums is a posting about this. If I recall right, you would need to disable OOBE, set the props for adb enabled, device registered / setup completed. Then the stick boots straight into the fireOS launcher, now you can install a custom launcher...
Click to expand...
Click to collapse
I've had some few crazy months and went away so I haven't checked the replies. I appreciate your responses and I'll try to see if I can resurrect the damned thing, just as a hobby since it didn't cost that much.
mmmk, fireiso burnt to usb, boot it up, been futzing with a ALU foil trying to find the sweet spot but no device seen by the script I'd guess that's what happens when it's FUBAR
primusmagestri said:
mmmk, fireiso burnt to usb, boot it up, been futzing with a ALU foil trying to find the sweet spot but no device seen by the script I'd guess that's what happens when it's FUBAR
Click to expand...
Click to collapse
If you see no device in lsusb while shorted, try the 'new' method (run bootrom-step with sudo and connect the stick without a short).
You can also use this OPs guide together with the latest mantis kamakiri:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)
Read this whole guide before starting. This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon). NOTE: FireOS < 7.2.7.3 required NOTE: This process does not require you to open your device. What you need: A Linux...
forum.xda-developers.com