Hi,
We have not been able to replicate the battery drain and random reboot issue that several users have reported after the ICS update and subsequent firmware updates.
As such we are looking for a few volunteers here to run a custom logging problem and report back their results. The system needs to have either the random reboot or battery drain issue and cannot be rooted.
If you are willing to run this logging problem (very much appreciated) then please PM with the following information.
Name
Email Contact Information
Serial Number
Problem Description
Sincerely,
Gary
Update -
I will start sending out the logging file and instructions to the test group tomorrow.
The logging tool simply captures low level OS routines that might lead us to the source problem.
3/21/2012 Update -
The logging tool was delivered to the first control group tonight. I will send the tool to the second control group tomorrow. Thank you for your assistance and replies.
3/26/2012 Update -
Thank you for your assistance and log reports. R&D is working on them feverishly right now. I will send out the tool to a third control group shortly.
4/2/2012 Update -
First off, thank you for your assistance and log reports. We are still investigating root causes for some of the problems. As such, personnel from the three control groups might be contacted directly for a system replacement so we can further investigate the lockup problem. I will have an update later this week.
4/9/2012 Update -
Thank you for the continued log reports. We are working through all the data now within R&D and at NVIDIA/Google. As soon as I have word on a Firmware update I will post it here.
4/18/2012 Update -
We sent out a beta Firmware release to a few users for testing. So far, it has solved the problems these users have experienced but I am still waiting on a couple of test updates. We also received back a unit that had the random lockup and screen corruption problem and so far after 22 hours of testing no problems. If the balance of the test updates are positive, we will get this build qualified and releases ASAP.
4/24/2012 Update -
9.2.1.21 will roll out today in North America. This release addresses several of the random reboot and lock problems reported by a few users after upgrading to ICS. It also provides new functionality with WiFi-Direct, Unzip in File Manager, Restore Tab function in the Browser, and general performance/stability tweaks. Although we had a high success rate in the beta testing phase in solving the random reboots, there were a couple of users who still experienced it during deep sleep mode. We are having those systems returned to us for further analysis and regression testing with their particular setups.
5/3/2012 Update -
We will release 9.2.1.24 into beta testing shortly. This firmware contains new NV code based upon the beta test group who still had issues with .21. I will provide updates once the firmware goes out to the beta group but it did fix returned units that experienced random lockups after .21.
5/9/2012 Update -
I have been out with pneumonia but will have messages forwarded to the Customer Care Team. The .24 release is in final qualification testing and will be released shortly.
5/10/2012 Update -
The .24 release is approved and will be released in the near future.
5/14/2012 Update -
The .24 release should go to FOTA later today or early tomorrow. Please shutdown and perform a cold boot after updating.
5/15/2012 Update -
Bad news, Google has changed their CTS qualification requirements on firmware so the .24 release is delayed for a couple of days. We have asked for an exception to release earlier, especially since it already passed qualification testing.
5/16/2012 Update -
The .24 release should go to FOTA very shortly.
5/22/2012 Update -
Sorry for the delay, tried not to die from pneumonia last week after a relapse. I will start answering general questions again today and forwarding CSR events to the Service Team. Good news is that we have hired a full time employee to assist our Tablet owners in the Android centric forums. His name is Tien Phan and he is available here under the user name Asus_USA. He is part of our new Customer Loyalty Group and will be taking over forum coverage and assisting our valued customers. I will still be around, especially to handle technical problems and coordinate with Engineering until Tien is completely up to speed. However, as always, if you run into a problem that is not solved by our Service Group please feel free to contact me.
5/31/2012 Update -
We are working on another release with updated code from NV/Google. I will be in Taiwan next week to discuss this version and once a beta is available we will release it to a small group of testers. So far, this updated code based has worked extremely well on the TF201/TF300 in beta testing. As soon as I have an update it will be posted.
6/11/2012 Update -
We received additional code enhancements from NV/Google while I was in Taiwan last week. We will create a beta update shortly for testing and hopefully the next firmware update will occur in the next two weeks. I/O and Thread priority changes are the top two items and will address ANR and Sleep issues, however, still testing various application loads as some applications do not want to play nice with thread overrides.
7/4/2012 Update -
New .27 Firmware is released and addresses browser and ANR problems among other items. As always, after the update is complete, clear browser and system caches, shutdown and then power up.
I just checked your previous postings since I wasn't sure that you are who you claim to be. Judging by your previous postings I'd say that you are an Asus rep.
Now to the point.
What exactly does this logging of yours entail?
I am willing to help you out. Please answer in this thread if possible.
I sent a PM to Gary volunteering to participate
PM sent. Hope to hear soon.
Great! Been waiting to see some official movement on this. Will PM requested info.
Thiesen said:
I just checked your previous postings since I wasn't sure that you are who you claim to be. Judging by your previous postings I'd say that you are an Asus rep.
Now to the point.
What exactly does this logging of yours entail?
I am willing to help you out. Please answer in this thread if possible.
Click to expand...
Click to collapse
he is an ASUS Technical Marketing Manager
I will also PM you Gary, when I arive home and can send you my serial.
(pff never heard anything from Gary!)
I hope this goes better than the "No Serial Number" issue with the Prime, in which emails were never answered (including mine), and the promised fix that was "coming soon" in January, never came.
PM sent too.
Has anyone actually received a response form this yet? I believe that I was one of the first to PM this guy, but haven't heard anything back...
Thanks!
@jtrosky: Gary updated his post one hour ago with this
Update -
I will start sending out the logging file and instructions to the test group tomorrow.
The logging tool simply captures low level OS routines that might lead us to the source problem.
Click to expand...
Click to collapse
PM sent.
Thanks Gary for the doing this.
testing if this is a PM
PM sent from me as well. I would love to help out if it leads to my Transformer working as it did under Honeycomb. It used to be a rock of stability. Not so much with the 2 ICS updates.
I sent a PM. I would love to help test.
PM'd - Will happily run this tool if it will cure my list of bugs
Thanks Gary,
I also sent a PM.
I've definitely had all the random reboots, stuck in boot loop, battery drain, unresponsive touch screen issues since the ICS update. Everything was fine before that.
Hi Gary: Major kudos to you for reaching out to the community. This harks back to Asus' great efforts when the TF101 first came out, and I'm glad to see you've not forgotten us.
I'll be dropping you a PM; I have two TF101s and both suffer this problem at least once or twice per day, so it should be quite easy to get you a log.
PM'd, hopefully we can help. A bit frustrated with my transformer at the moment.
PM'd.. hopefully not too late!
Just got an email from Asus and installed the log program.
Amazon has released yesterday a New software update 5.2.1.0, for all the FireTV units:
http://www.aftvnews.com/fire-tv-software-update-5-2-1-0-is-now-rolling-out/
Some FireTV users, are already complaining that some APPs like "HBO GO/HBO NOW" (if you have Kodi/SPMC installed), "Mouse-Toggle 1.04", "Wukong Remote 1.9.0EN" and "Firestopper" now do not work at all...
Fo Realz, has mentioned on www.aftvnews.com, that after the update he can’t use "HBO NOW", unless he uninstall Kodi... Because he always get the following message:
“For security reasons the following apps must be uninstalled to use this app: Kodi”
Luckily, KODI and SPMC are still working flawlessly!!
Others users, have noticed that it looks like Amazon has changed the FireOS Font, that now it looks a bit like “Trebuchet”... And that the Remote-Control, the Wifi-Direct version, got a new update too…
It is not known yet whether this 5.2.1.0 update is Rootable or not!
Someone who has received this 5.2.1.0 update, has noticed something new or any improvements?
I just got the update yesterday as well. Netflix doesn't load properly anymore, gets stuck at 99%. Amazon videos don't play they load the video and I just see like a screenshot of the video and it doesn't play. I've lost all audio. Tried resetting, clearing cache, data, reinstalling Netflix etc.
ulises.rodriguez said:
Amazon has released yesterday a New software update 5.2.1.0, for all the FireTV units:
http://www.aftvnews.com/fire-tv-software-update-5-2-1-0-is-now-rolling-out/
Some FireTV users, are already complaining that some APPs like "HBO GO/HBO NOW" (if you have Kodi/SPMC installed), "Mouse-Toggle 1.04", "Wukong Remote 1.9.0EN" and "Firestopper" now do not work at all...
Fo Realz, has mentioned on www.aftvnews.com, that after the update he can’t use "HBO NOW", unless he uninstall Kodi... Because he always get the following message:
“For security reasons the following apps must be uninstalled to use this app: Kodi”
Luckily, KODI and SPMC are still working flawlessly!!
Others users, have noticed that it looks like Amazon has changed the FireOS Font, that now it looks a bit like “Trebuchet”... And that the Remote-Control, the Wifi-Direct version, got a new update too…
It is not known yet whether this 5.2.1.0 update is Rootable or not!
Someone who has received this 5.2.1.0 update, has noticed something new or any improvements?
Click to expand...
Click to collapse
Did you get a chance to grab the URL for this? I can start tearing apart the update to see what changed.
I'm very sceptical about the comment on my site claiming that HBO Now won't work with Kodi installed. I have not received the update myself yet, but a reader I trust has received the 5.2.1.0 update on his Fire TV 1 and says he can launch HBO Now with Kodi installed and with Kodi running in the background. He does not have an HBO Now subscription, so it's possible the message only appears when you try to play content, but he said he does not receive a message when launching the app and going to the login screen.
Wukong Mouse mode is dead on Firestick after latest OS update
Xfinity TV does not allow clicking after the update. Mouse mode is DOA. Maybe something to do with the prompt that comes up stating . "You don't have a controller" when you bring up the TVGo app. BTW I have not 'rooted' my FireStick.
Surprised you took it seriously in the first place. Obvious troll is obvious.
There's also a comment that ADBFire doesn't work. Not believing that either.
AFTVnews.com said:
I'm very sceptical about the comment on my site claiming that HBO Now won't work with Kodi installed. I have not received the update myself yet, but a reader I trust has received the 5.2.1.0 update on his Fire TV 1 and says he can launch HBO Now with Kodi installed and with Kodi running in the background. He does not have an HBO Now subscription, so it's possible the message only appears when you try to play content, but he said he does not receive a message when launching the app and going to the login screen.
Click to expand...
Click to collapse
Claude Koch said:
Surprised you took it seriously in the first place. Obvious troll is obvious.
There's also a comment that ADBFire doesn't work. Not believing that either.
Click to expand...
Click to collapse
Well you never know. When the first couple comments started rolling in that 5.0.5.1 was removing FireStarter, my initial reaction was to assume it was a troll. I'm not going to go posting about something based on a comment or two, but I've learned my lesson to not dismiss anything entirely.
I'm curious... In theory, if I were to repack/recompile the Kodi APK into a different name and then installed on my Fire TV, would I survive an Amazon Kodi block if it were to happen? Is it really that simple to avoid a software block?
AFTVnews.com said:
Well you never know. When the first couple comments started rolling in that 5.0.5.1 was removing FireStarter, my initial reaction was to assume it was a troll. I'm not going to go posting about something based on a comment or two, but I've learned my lesson to not dismiss anything entirely.
Click to expand...
Click to collapse
Elias, I understand your point of view and that is precipitated taken as certain some news only based on one or two comments... But, there are many users complaining about Adb-Fire problems (that not allows applications sideloading anymore) and also problems with the Mouse-Toggle1.04 and Wukong-Remote1.9.0EN APPs, that Amazon might have changed something in this new 5.2.1.0 update.
Maybe as you already said in aftvnews.com, the issues trying to run HBO-GO or HBO-Now, with Kodi installed or running, could be "a troll comment meant to stir up concern with a false statement", however I am very worried because I'm starting to see more complaints about Netflix and Amazon Video, that are not working well after installing this update:
1 - When I watch a movie with Netflix, it don't load completely and gets stuck on 99%.
With Amazon-Videos, movie loads, but the video does not play, and does not have audio"
2 - "I am having amazon issues, and Netflix Issues stuck 99% and no audio"
3 - “Netflix doesn’t load properly anymore, gets stuck at 99%.
Amazon videos don’t play they load the video and I just see like a screenshot of the video and it doesn’t play.
I’ve lost all audio”
Since I still have not received this new 5.2.1.0 update, I would appreciate if you could contact some users who have received it, to ask if they have experienced these strange behaviors with Netflix/Amazon-Videos, and to also confirm issues with adbfire and the sideload of apps.
Thank you Elias, for your Excellent comments, your Great AFTVnews site and always help with all our requests!!
ulises.rodriguez said:
... But, there are many users complaining about Adb-Fire problems
Click to expand...
Click to collapse
adbFire worked for me on 5.2.1.0
trek70000 said:
I'm curious... In theory, if I were to repack/recompile the Kodi APK into a different name and then installed on my Fire TV, would I survive an Amazon Kodi block if it were to happen? Is it really that simple to avoid a software block?
Click to expand...
Click to collapse
Yes, currently Amazon is only blacklisting apps by package name. FireStarter and FiredTV are the only two apps on the list as of the 5.0.5.1 updated. I haven't received the 5.2.1.0 update yet, so I don't know if the list has changed, but several people have said Kodi installs/runs fine on 5.2.1.0
---------- Post added at 11:13 AM ---------- Previous post was at 11:09 AM ----------
ulises.rodriguez said:
Elias, I understand your point of view and that is precipitated taken as certain some news only based on one or two comments... But, there are many users complaining about Adb-Fire problems (that not allows applications sideloading anymore) and also problems with the Mouse-Toggle1.04 and Wukong-Remote1.9.0EN APPs, that Amazon might have changed something in this new 5.2.1.0 update.
Maybe as you already said in aftvnews.com, the issues trying to run HBO-GO or HBO-Now, with Kodi installed or running, could be "a troll comment meant to stir up concern with a false statement", however I am very worried because I'm starting to see more complaints about Netflix and Amazon Video, that are not working well after installing this update:
1 - When I watch a movie with Netflix, it don't load completely and gets stuck on 99%.
With Amazon-Videos, movie loads, but the video does not play, and does not have audio"
2 - "I am having amazon issues, and Netflix Issues stuck 99% and no audio"
3 - “Netflix doesn’t load properly anymore, gets stuck at 99%.
Amazon videos don’t play they load the video and I just see like a screenshot of the video and it doesn’t play.
I’ve lost all audio”
Since I still have not received this new 5.2.1.0 update, I would appreciate if you could contact some users who have received it, to ask if they have experienced these strange behaviors with Netflix/Amazon-Videos, and to also confirm issues with adbfire and the sideload of apps.
Thank you Elias, for your Excellent comments, your Great AFTVnews site and always help with all our requests!!
Click to expand...
Click to collapse
It's very tedious and slow to check/verify update changes by contacting people who have already received the update. I just keep a list of all the issues I've heard about and check them myself once I receive the update. I'd rather be a few days late with postings than be inaccurate because information is being relayed to me.
AFTVnews.com said:
Yes, currently Amazon is only blacklisting apps by package name. FireStarter and FiredTV are the only two apps on the list as of the 5.0.5.1 updated. I haven't received the 5.2.1.0 update yet, so I don't know if the list has changed, but several people have said Kodi installs/runs fine on 5.2.1.0
---------- Post added at 11:13 AM ---------- Previous post was at 11:09 AM ----------
It's very tedious and slow to check/verify update changes by contacting people who have already received the update. I just keep a list of all the issues I've heard about and check them myself once I receive the update. I'd rather be a few days late with postings than be inaccurate because information is being relayed to me.
Click to expand...
Click to collapse
I totally agree, it is very tedious and time consuming too, trying to contact users who already have received this 5.2.1.0.update.
I meant to get in contact with only known and trusted users, that have received the new update, as you already did with the user who confirmed that he had not received any safety message launching HBO-NOW, with Kodi installed or running.
However, maybe you're right, it is better to keep a list of all problems reported and once you receive the update, check to see if they are true or not...
I really hope that in a couple of days after receiving this update, you will have the time to write a full review in AFTVnews.com, about the negative things and also the new features of this 5.2.1.0 update.
Deleted post
I'm from Germany and I received the 5.2.1.0 update on my Fire TV Generation 1. After this Update the aftvnews.com Update blocking methode 2 isn't working anymore. No Feedback from adb when I send the command. My 2nd device, a Fire Stick hasn't got the update to 5.2.1.0, and there the blocking Methode works I think, because adb shows a Feedback after sending the command.
Gesendet von meinem E6653 mit Tapatalk
harlekinade said:
@aftvnews: Just as a small critique (well - thats how it started out, anyways... ) - when people looked at you in the past to provide context, this is what they got as first responses in return.
Click to expand...
Click to collapse
First off, thank you for posting this long and detailed criticism. Feedback, even negative feedback, is always welcome. I'll respond inline.
- When Firestarter first stopped working - it was pronounced by you "probably just an incompatibility issue".
Click to expand...
Click to collapse
I did not say "probably." I said "one theory is." There's a distinct difference. At that point nobody knew why FireStarter wasn't working yet. I hadn't even received the software update yet (which I pointed out), but thought people would like to know sooner rather than later that the update was causing some unknown issue with FireStarter. I'd love to have weeks with an update to fully dissect it before posting anything about it, but by then it would be too late for many people to avoid the update if they suddenly want to.
- When Amazon started blacklisting apps and banning Firestarter you first repeated the same notion, then celebrated Amazon for providing "their own launcher" and therefore "making it easier for most people". And only afterwarts wrote about the issues it created, also for the company itself (reputation damage).
Click to expand...
Click to collapse
The first thing I wrote about the 5.0.5.1 update was that sideloaded apps were added to the home screen and there was a quicker way to get to apps. That's what Amazon told us about the update so that's what I reported. Nobody had any idea apps were blacklisted at that point. I didn't first write about app banning and "then celebrate Amazon" like you say.
- When people asked you why to root Fire TVs, you "couldnt tell them, because everyone is different" - nfts support (circumventing the 4GB filesize limit), running a smb server, using VPN services (currently also possible without - but generally speaking), blocking software updates, using open APIs or a web interface to control the device -- are all usecases I'd argue most people should know about that are possible by now - even though Amazon put in extra effort to specifically take them out of base Android one by one. So by glancing over those - you actually follow Amazons product politics once more -
Click to expand...
Click to collapse
I assume you're referring to when people ask about why they should root in the Q&A portion of my podcast. That question comes up nearly every week and if I listed all the reasons why someone would root in every episode it would not be interesting to the listeners. Heck, if I listed and talked about just the things you mention above, which is still just a small portion of the reasons to root, it would take up the entire time I allocate to Q&A. If you want to compile a full list of all the reasons to root and keep it up to date with links to guides, I'd love to point people to it every single time this question comes up. But nobody, including myself, has created such a list because it would be very time consuming to create and maintain.
- to put it out in the open, I have a problem with you having become the gatekeeper of most information in the Fire TV ecosystem.
Is saw german mainstream technology outlets copying your first statements on issues verbetum - even if they turned out to be beside the point (as in the blacklist issue case)
Click to expand...
Click to collapse
Other websites not covering the Fire TV more or not doing their own research is out of my control.
and I ultimately hold you personally responsible for Amazon being able to --
Put blacklist routines into Android, uninstalling apps from their users devices - which they dont like because of anti competitive reasons - and allowing them to spin this feat to be just something thats "easier for the user".
Click to expand...
Click to collapse
Holding me personally responsible for that is just plain stupid.
You maybe single handedly prevented the "Amazon uninstalls its users Apps" headline and made it a "Great new feature" story.
Click to expand...
Click to collapse
You over estimate how much influence I have over other tech blogs. Every time Amazon does something negative to Fire TV owners, I contact numerous tech blogs to let them know. They simply don't care. It's not newsworthy to them. The issue isn't that the headlines were "Great new feature," it's that there were no headlines at all outside of my site.
I also hold you responsible for maintaining an atmosphere where every slight new feature, change, or tidbit Amazon "creates" gets received with unfiltered optimism first ("cheerleading"). Even down to overly detailed changelog analyses that are made to be seen as newsworthy - just because they are something new to report on. Something of general interest to your audience.
Click to expand...
Click to collapse
I'm sorry everything I write about isn't newsworthy to you. I write about what I find interesting. It's not that I think everything Amazon does is worth cheering about, it's that I don't write about things I don't think are interesting. It might be a shock to you, but a headline like "Amazon did a thing that you shouldn't care about" is not at the top of my list of articles to write.
When you made them care more about ES File explorer (by pronouncing it "the easiest way") than if adb (which was first limited, then got puposely rewritten (?)) actually remains usable for things not predetermined by Amazon - you did this entire community a disservice.
Click to expand...
Click to collapse
I didn't "make" anyone do anything. My sideloading guide lists 7 methods. The ES File Explorer method is by the the preferred method by most for obvious reasons. The fact is ADB is confusing to many people. A GUI, even if limited, is usually preferred by most. Hence the popularity of utilities like adbFire before ES File Explorer was even an option.
When you let tutorials regularly get pushed off of the front page of your blog by 12 times the "Amazon echo appreciation messages" - something important changed - combining the "how to tinker with the device" angle with the actual product messaging of the manufacturer - created a hybrid that I'd argue actually resembles a frankensteins monster that produced more harm than good.
Click to expand...
Click to collapse
If you're saying I deliberately push guides off the front page, that's just stupid. I cannot control when something newsworthy happens. If something happens that results in a bunch of posts right after I release a guide, that's out of my control. I'm not going to hold back news just because I wrote a guide.
You managed to commercialize most aspects of device hacking, for - and mostly in the name of the company that produced the device - while Amazon itself promoted a purely anti right to modifications message at the same time. You tried to moderate this conflict - and somehow it never quite worked.
Click to expand...
Click to collapse
If I didn't make money from the website through ads, it wouldn't exist. Not in the same capacity at least. The same way XDA wouldn't exists if it didn't have ads to make money off of device hacking. If you have an issue with me turning my hobby of tinkering into a means to support my family, then so be it.
When Amazon put the blacklist into the Fire TV firmwares - you werent the person that first discovered the database entries - they were reported (In here or on your comments section) and you picked it up - but now you are promoting yourself to be the person we should look at for a confirmation if Amazon has added new entries to their blacklist, or if they didn't.
Click to expand...
Click to collapse
I never took credit for discovering the blacklist. I said "XDA forum member jkchr1s has discovered that FireStarter is being explicitly disabled by name" in my post and linked to his XDA post. jkchr1s and I were going back and forth via XDA private messages trying to locate the, at the time, theoretical blacklist. He explicitly asked me to not credit him with certain things, so I left some things vague.
I am not "promoting" myself to be "the person we should look at" for anything. It's simply a fact that I'm in a position to be the first one to know if the blacklist has been updated, since I know where to look and I have several Fire TVs and Fire TV Sticks dedicated for the sole purpose of capturing the update package to pass along to rbox.
Something about all of this just feels wrong. You were more a Steward of public opinion towards your cause (a world where a advertising message can stand eye to eye to a "how to intall Kodi" tutorial - ) and at least created an information silo - that kept out certain aspects of what is possible, or what happened in the past, and overemphasized others (I see ES File Explorer use as a real problem to people learning better ways of interacting with their devices, f.e.) at least I don't agree with.
Click to expand...
Click to collapse
I agree that learning ADB is far superior to any GUI like ES File Explorer. The only guides where ES File Explorer comes up is when I write "no pc needed" guides for rooting and sideloading, since those two topics are the most popular types of guides. But for every "no pc needed" guide I have ever written, there was always first an equivalent guide posted that did everything with just ADB.
Now that the hype is mostly over, Firestarter is no more and we are gossiping whos next on Amazons in Android blacklist - where do we actually stand considering discoverability of methods or tutorials, do we understand the actions Amazon has taken, do we promote best practices - and do you - for example know - why not letting Amazon blacklist Kodi is actually important?
Click to expand...
Click to collapse
Despite what you think, I don't control the future of FireStarter, the actions Amazon has or will take, or where the Fire TV community stands.
You take both sides on this issue as well - why? And when you, a few months from know - write your article about how it was actually necessary and beneficial to the average user - will you still be part of this community? Or do you just want to feature its work? And tell your readers to mostly use Alexa ("the service economy"), just because it is there by default.
Hey - and buy an "order from Amazon" WiFi button for 20USD while you are at it, because maybe one day you will be able to launch an App on the Fire TV with it. Great pitch.
Click to expand...
Click to collapse
I don't "take both sides on an issue", but I do try to explain both sides of an issue. When Amazon does something the community thinks is negative, I don't blindly defend their actions. I do give my opinion on why I think they chose to do what they did, regardless of whether I agree or disagree with it. There is a distinct difference.
I've hid my reply to the comments that were deleted to help clean up this thread.
@harlekinade
So your old account was banned? And you decided to come right back in here with your obvious rants now directed at the main person who keeps this community going? Good job dude.
Biggest question (for us "pros") is actually: Is root (and downgrade) still possible on the fire tv 4ks that ship with that firmware?!
harlekinade said:
I'm glad to see that the posting got some kind of of recognition, I'll take some time reading through the responses and give another rebuttal in the following days.
Click to expand...
Click to collapse
If you do reply, I encourage you to do it in a new thread and link to the posts in this thread as reference because discussions of your opinion of me and my site do not belong in a thread about a Fire TV software update. This is potentially an important thread (depending on what is discovered in the update), so it should not be cluttered with off-topic conversations. I absolutely will no longer reply to you in this thread regarding myself or my website.
zroice said:
Biggest question (for us "pros") is actually: Is root (and downgrade) still possible on the fire tv 4ks that ship with that firmware?!
Click to expand...
Click to collapse
I don't know if anyone whos gotten it yet has confirmed if the preloader hack is still active.
harlekinade said:
@aftvnews:
.
Click to expand...
Click to collapse
Dude, quit it. No one's reading your responses, you're acting like a sorry little git. If the mods bothered to read these, expect your second ban real soon. Quit starting fights and leave everyone alone.