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.
Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Davy49 said:
Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Click to expand...
Click to collapse
Hi David!
Holy cow, you've installed the entire studio? That's way more than you need. Just get the Platform Tools here: https://developer.android.com/studio/releases/platform-tools
At a user level, all you'll ever need are ADB and fastboot. Then enable developer settings, enable USB debugging and use the command 'adb reboot recovery'. You sure power + volume down don't work? Or power + volume up for fastboot (to get custom recovery installed)? Note that I have made zero research on this device so it may deviate (I'm on mobile right now). If any of those steps seem difficult or you're unsure how to proceed, just let me know where exactly you're stuck.
Oh and when you send an adb command to your device for the first time (like 'adb devices') it will likely show a trust notification on your screen, asking you to allow this computer to send adb commands. Make sure the remember checkbox is on.
Good luck!
Wrapped with delicious Fajita [emoji896]
Hi Timmy,
Thanks for being nice and explaining the process to me, that sounds pretty easy. Today my biggest problem is getting vanced to install on my amazon fire 7 tablet (2019 Edition). I've had it running normally on there previously, but a couple of day's ago I started the vanced app and noticed that I wasn't signed into my google account anymore. And when I attempted to sign in I received the now famous notice that said google server's were busy, please try again later. But knowing I had it running before, motivates me to get it running again. In the interim, I'm using the Web Tube app.
David
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Davy49 said:
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Click to expand...
Click to collapse
Proper reboots in between? I don't see how web view would be related but it's always a good exercise to remove recent installations one by one, retrying Vanced in between. Be sure to share your findings if you encounter a potential culprit. It's important for the community to learn from that.
Hi Timmy (I guess it's okay to use this name),
I think before I do anything else, I'll go back and re-read the instructions on how to properly install it. Unless google has done something on their end, I should be able to get it functioning properly. It was installed previously, that's why I don't know what happened.
Thanks,
David
My firestick downloaded 5.2.7.4 and its broke my accessibility and adb commands. I looked on amazon to see latest versions for their devices and none of em are listed to have 5.2.7.4. Not sure if anyone else is having this problem or if they are rolling out another update and I just got unlucky and got some of the first roll outs of it. I also had ran some debloat commands and not sure if the stick just ran some updates after that. But it was after that it broke. But I have since factory reset and its still broke adb and accessibility. Just wanted to make people aware and see if anyone else has found a fix for this version or any info on a fix.
I having this problem too, cant set custom launcher.. anyone help us??
The 5-6 domains did not block this update either! This update made it through!
I also am wondering about this. Not even the app I used to prevent standby works anymore!
I have been looking all over for any info on the .4 update and no one seems to care as if this update doesn't exist. I have found no info on any existence of .4 except for a select few people sharing the same problem. this update has broke my adb as well as accessibility. Virus scanner wont work custom launcher will work if manually loaded. any app that requires any adb or accessibility are completely broke. sm commands come back as doesnt exists as will as i believe pm commands. only a select few non important commands will work. trying to give details in case it helps at all. but for now just letting developers do their thing and not trying to bother them to much. would love to help more but my 2nd gen tank cant be rooted. so i cant pull a backup or anything from it. not to mention if it was able to be rooted id be golden. Hopefully if someone figures out this whole .4 thing they will be kind enough to post something about it.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
Adb works without any Problems.
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
noremy said:
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
Click to expand...
Click to collapse
Try toggling unkown sources and debugging in settings? Maybe they got turned off?
Oh and just straight usb, 1 cable? Mine wont do tether adb with an otg cable.
Done all that. Unfortunately Im stuck. I dont what else to do with this thing. ADB will still connect but all the important commands come back as missing or invalid. such as sm commands and pm commands.
With 5.2.7.4 , you need root for this commands!!!
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
TimmyP said:
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Click to expand...
Click to collapse
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Sus_i said:
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Click to expand...
Click to collapse
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
TimmyP said:
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
Click to expand...
Click to collapse
:good:
You can fix this issue if you connect the FireISO system to the internet and run this, in order to update fb:
Code:
pacman -Sy
pacman -Sy fastboot
Ahh where were you a couple days ago!
noremy said:
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
Click to expand...
Click to collapse
So just to clarify, 5.2.7.4 OTA has taken custom launcher apart by blocking pm grant permissions in accessibility.
TechdoctorUK mentioned this too a couple of weeks back. It seems the devs at amazon have been all over him lately and have been quoting tutorials etc from his site.
I've been using the ftvlaunchx app wrote to system settings on a post Dec 2019 unrootable 2nd gen and thought I'd blocked 5.2.7.4 update but I came back in today and was fkin horrified it had updated to 5.2.7.4 (I nearly sh't myself) its still optimizing apps just now but I'm hoping, just hoping that due to the pm grant permission already being installed it maybe slip through the net. Wishful thinking I know.
Hurry up and arrive 4k firestick I NEED ROOT
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
noremy said:
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
Click to expand...
Click to collapse
Hi noremy, i just made a new thread there on 5.2.7.4, the cure is ftvlaunchx wrote to system settings, install atv launcher pro and set that as default launcher in the ftvlaunchx app, should work with any android tv launcher too.
Big thanks to the developers @github
Edit #### i rebooted and now the home button is not working at all
Only sending me back to amazon screen.
Regards
Sent from my SM-T580 using Tapatalk
Hi! Mine is a 2nd gen Firestick. After the 5.2.7.4 update, none of my apps are opening. It says "Amazon App Store is out of date. Please visit the Amazon website to install the latest version". When I click on the link, it says Appstore is installed & I am good to go. No matter what I do, same thing happens for each and every app. So I can't use any of the apps on my Firestick. Any suggestions on what this is? Thanks!
The only option I can think off would be to factory reset it. I know its a pain to put everything back on but not sure what else to try.
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