Root Fire 7"- 5th Gen-2015 FireOS 5.1.3, 5.1.4 (New Shipments Summer, Fall 2016)
I bought my Fire 7" shortly after it came out. Not too many weeks went by and folks had posted instructions to get rid of the ads, load Google Play Store, get rid of Amazon's horrible home screen(s) (a.k.a Launcher) and a month or so later how to root it.
A friend of mine just ordered one on my recommendation. And boy have things changed! It would appear that as folks came up with ways to do the things mentioned above, Amazon simply issues OS updates to stop them. Everything I am about to write about is, I'm sure, found somewhere else here on XDA. My intent is to save you the time it took me to figure this out this past afternoon.
FIRST - DON'T LET YOUR NEW FIRE TABLET UPDATE! What I'm going to explain applies to FireOS 5.1.3, 5.1.4 (and 5.1.2.1)
Right now today, early Oct 2016, it appears that there isn't a root tool for FireOS numbered above 5.1.2. But you easily downgrade the ones shipping today (FireOS 5.1.3, 5.1.4 and 5.1.2.1) to FireOS 5.1.2. And then existing tools work.
You'll need to download and extract:
AmazonFire5thGenSuperTool.zip
Firmware-Downgrade-to-Fire-OS-5.1.2-Supertool.zip
Steps:
Run the Firmware-Downgrade-Supertool, you don't need to start adb or anything first, just double-click the "1-Start-Firmware-Downgrade-to-5.1.2.bat"
NOTE1: You'll need to allow unknown sources (In the Security Settings) and allow adb (In Developer Options. You add Developer Options by tapping Serial Number 7 times (In Device Options) see Developer Options
NOTE2: Watch the Fire Screen closely. There will be multiple popup screens/boxes. You'll need to approve adb several times. Just tap "OK"
NOTE3: When I ran it the text in the Windows cmd.exe box said it failed. But wait and a menu will appear on the fire's screen. Use the volume keys to select the 2nd item listed "from ADB" and the on/off/power button to select it. Go back to the Windows cmd.exe box and hit any key. Then the bin file for the downgrade will start transfering
When it completes, run the AmazonFire5thGenSupertool. It has a menu that will let you do everything I listed in my opening paragraph
In the AmazonFire5thGenSupertool menu pay attention to those selections that require root first. In FireOS 5.1.2 it will intall a rooting app. PAY ATTENTION to the NOTE in the cmd.exe screen that says if it fails to root you may need to shut the Fire all the way down and run tha app again. For me it was running it again after a full shutdown that completed the root.
You've just spent a good amount of time downgrading to 5.1.2 so you could get rid of the Amazon crud. IT SHOULD GO WITHOUT SAYING, but I'll say it anyway. In the AmazonFire5thGenSupertool be sure to shut off updates!
MANY, MANY THANKS to RootJunky for the tools!!!
I used this method, but when you restart the tablet does not appear among the options to update the firmware, it appears only option (I forget the name) and select not let.
Got myself a Fire tablet 16gb, which came with ver 5.1.3 and auto updated to 5.1.4 (which i didn't want it to), used this guide and followed the steps. Kingroot took maybe 6-7 tries, but it finally worked. Achieved root, got rid of of lockscreen ads, uninstalled FireOS launcher, and installed nova launcher. Now it feels like stock android (also got playstore) while keeping the FireOS features (useful for my 2 yr old son who loves the shows on the Amazon firestick). Win-Win. Thank you OP
mstrakt said:
Got myself a Fire tablet 16gb, which came with ver 5.1.3 and auto updated to 5.1.4 (which i didn't want it to), used this guide and followed the steps. Kingroot took maybe 6-7 tries, but it finally worked. Achieved root, got rid of of lockscreen ads, uninstalled FireOS launcher, and installed nova launcher. Now it feels like stock android (also got playstore) while keeping the FireOS features (useful for my 2 yr old son who loves the shows on the Amazon firestick). Win-Win. Thank you OP
Click to expand...
Click to collapse
Don't forget to disable OTA updates. If you used an automated method make sure system\priv-app\DeviceSoftwareOTA.apk got renamed.
Davey126 said:
Don't forget to disable OTA updates. If you used an automated method make sure system\priv-app\DeviceSoftwareOTA.apk got renamed.
Click to expand...
Click to collapse
Yup did that too. It hasn't bugged me to update since, so I'm guessing it worked! Thanks.
mstrakt said:
Got myself a Fire tablet 16gb, which came with ver 5.1.3 and auto updated to 5.1.4 (which i didn't want it to), used this guide and followed the steps. Kingroot took maybe 6-7 tries, but it finally worked. Achieved root, got rid of of lockscreen ads, uninstalled FireOS launcher, and installed nova launcher. Now it feels like stock android (also got playstore) while keeping the FireOS features (useful for my 2 yr old son who loves the shows on the Amazon firestick). Win-Win. Thank you OP
Click to expand...
Click to collapse
I had rooted my kindle out of the box and turned off auto updates. However overnight it updated..... I am having a heck of a time getting access to the kindle again even after authorizing USB debugging. I have tried the downgrade supertool, I've tried command window method, the main supertool and everything else I can think of.
When I get to the point to load the firmware via adb sideload <filename> it says it cannot find the device. I have authorized debugging and allowed unknown source app downloading.
Please tell me how you were able to get back out of 5.1.4. Thank you in advance.
Dano
So ... received a 5.1.3 device (5th gen, with special offers) yesterday. Successfully downgraded to 5.1.2 using the method on this thread. Before even connecting to Wifi - downgraded straight out of the box.
However, the kingroot method from this thread just fails (using 4.9.2 apk version) with the supertool method. Tried several times, even reflashing 5.1.2. gets stuck at Verify Root Status (left it there for several hours).
Decided to manually install kingroot 3.5 to PC (from XDA thread). That fails too. Says Failed to Root. Root request recieved. KFFOWI Android 5.1.1.
So now, I got a 5.1.2 device that cannot be rooted using the methods at my disposal.
Hope something comes up soon.
siftekhar said:
So ... received a 5.1.3 device (5th gen, with special offers) yesterday. Successfully downgraded to 5.1.2 using the method on this thread. Before even connecting to Wifi - downgraded straight out of the box.
However, the kingroot method from this thread just fails (using 4.9.2 apk version) with the supertool method. Tried several times, even reflashing 5.1.2. gets stuck at Verify Root Status (left it there for several hours).
Decided to manually install kingroot 3.5 to PC (from XDA thread). That fails too. Says Failed to Root. Root request recieved. KFFOWI Android 5.1.1.
So now, I got a 5.1.2 device that cannot be rooted using the methods at my disposal.
Hope something comes up soon.
Click to expand...
Click to collapse
Keep trying; KingRoot can be stubborn as countless others before you have learned. Try a factory reset; don't register device w/Amazon on restart. WiFi must be enabled during first 30-60 sec of KingRoot run; otherwise failure is certain.
---------- Post added at 04:09 PM ---------- Previous post was at 04:07 PM ----------
AkDano said:
I had rooted my kindle out of the box and turned off auto updates. However overnight it updated..... I am having a heck of a time getting access to the kindle again even after authorizing USB debugging. I have tried the downgrade supertool, I've tried command window method, the main supertool and everything else I can think of.
When I get to the point to load the firmware via adb sideload <filename> it says it cannot find the device. I have authorized debugging and allowed unknown source app downloading.
Please tell me how you were able to get back out of 5.1.4. Thank you in advance.
Dano
Click to expand...
Click to collapse
Updated to what? KingRoot is now capable of rooting all builds of FireOS 5.1.x. No downgrade needed if on 5.1.4.
Related
Hello everyone :laugh:
I'm new here in this forum and as on android user as well so go soft on me
I have a problem regardless the root and unroot device, my nexus 7 in rooted (I dunno if it is rooted by manufacture or not)
I installed some online games like Iruna online and avabel problem is I always got the same error screen "Authentication Failed"
I heard it got something to do with rooted devices, so I tried some programs that un-root the device for certain apps but it failed too.
any suggestion or this error is duo to something else
Ps:Google play is restricted in my country so I'm using hotspot
Do you want to hide the root or unroot the device.
No Nexus 7's are sent rooted from the manufacturer if it is rooted then this has been done by a user. Wugfresh nexus toolkit has an option to unroot but this involves flashing an unrooted stock ROM and will wipe the device. I'm not aware of any other way to unroot the tablet. Some apps say that they can hide the su binary from other apps. For more info on what "root access" actually is see XDA university for a pretty concise explanation. Try hide my root by amphoras if you can't get that on hotspot PM me and I will send you the .apk file.
Sent from one of my 47 iPads running android C3P0
I tried multiple apps that hide root but all failed, I will try the one you mention,
and I'm asking about the error too "Authentication failed" is it because of root or else ?
Edit: I just tried the app and the same error
SheepRaider said:
Hello everyone :laugh:
I'm new here in this forum and as on android user as well so go soft on me
I have a problem regardless the root and unroot device, my nexus 7 in rooted (I dunno if it is rooted by manufacture or not)
I installed some online games like Iruna online and avabel problem is I always got the same error screen "Authentication Failed"
I heard it got something to do with rooted devices, so I tried some programs that un-root the device for certain apps but it failed too.
any suggestion or this error is duo to something else
Ps:Google play is restricted in my country so I'm using hotspot
Click to expand...
Click to collapse
Hi, SheepRaider...
If your Nexus 7 is rooted with Chainfire, then unrooting it should be relatively straightforward...
------------------------------------------------------------
** Go into the App Drawer and locate the SuperSU app. By default, the icon should be a YELLOW triangle with a RED hash (#) overlayed on top of it. However, this may have been changed by whoever originally rooted the device. See the first thumbnail at the bottom of this post for the alternative icons. If it's been made invisible (hidden from launcher), then things become a little more technically challenging. See this post for more details on this.
** Once you have located the SuperSU app, run it and tap on the SETTINGS tab.
** Scroll down to the option, Full unroot - Cleanup for permanent unroot, tap on this and follow the on screen instructions.
** Reboot your Nexus 7... you should now be unrooted.
------------------------------------------------------------
Take a look at my attached thumbnail images for the sort of things you should expect to see.
Hope this helps... and good luck.
Rgrds,
Ged.
04/17/2015 Update to this posting; -24A OTA rooted 1st time using Stump after dozens of Brute Force fails on 23A-
Can anyone else confirm Stump Root working for 24A on their own devices?
Original Stump Thread; http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
New OTA software update VK81024A just released this week. From what I've read and VZW's PDF, the only thing that was changed was 4G LTE coverage. In my experience with Verizon, they only release updates for this device to patch root methods and add bloat. This would have been my 3rd update to my GPad (had I accepted) without measurable positive impact. I personally cannot believe that they spent the time and money to fix LTE coverage that, in my experience, had no noticeable issue to begin with.
I would still be waiting for Lollipop on my VZ G3, if I didn't go ahead and root/ROM just last month. With the Lollipop ROM being available to the Korean G3 as early as November of LAST YEAR, my faith in Verizon getting us the updates we want and deserve (I purchased a flagship phone, and a popular tablet) is nonexistent.
Okay, I'm done ranting (for now) about the "Great Satan" that is VZW...the only carrier with good coverage here in my area of NY. Does anyone have any experience with this update? Anyone try rooting it (maybe Stumproot will start working again)? I am tempted to accept it if I could assist the community by doing so. Please tell me your thoughts.
VK810 OTA update from 23A to 24A keeps root
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf
Just got mine this morning. Hadn't been using the tablet for a few days. Would not take OTA. Downloaded the file but kept kicking an error. Ended up hooking it up USB and using the upgrade assistant. Paranoia got the better of me and I "unrooted" first. Brute force stump (climbed to 6800 I think) did the trick just like before. Must say I was disappointed. I had not read what the "upgrade" consisted off but figured since they jumped from 23A to 24A it would be something substantial. I notice some minor cosmetic changes but that's about it. The 4gLTE "Update: or "Upgrade" isn't going to make much difference in my neck of the woods. 3G is about the best you can hope for here in this little town for the time being.
DeanGibson said:
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf
Click to expand...
Click to collapse
Did the same thing as you, OTA installed and still rooted
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
On every Android device, if you want to take an OTA, you have to either be 100% stock, or at least have stock recovery, kernel, bootloader, and other partitions, and only have done minor things with the system partition - not have debloated at all.
Sent from my VK810 4G
Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
If the LG Mobile Support Tool factory restores the whole phone (recovery included) then this may be the best option till someone posts the KDZ with rooted 24A. This was my root method and it may work for you.
After searching through forums for weeks looking for viable root options (rollback and Purplerake or Towelroot, ADB scripting, and all others) and running Stump as often as I remembered (probably 30 times on 23A) I finally have it! I didn't see any up to date threads on rooting the VK810 and all the old threads had too many broken links to actually perform the steps.
Here's how it went down;
1.) Installed the latest LG USB drivers from LG's site ( http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427 ).
2.) Download LG Mobile support tool ( https://docs.google.com/file/d/0B687...p2NlhhalU/edit ).
3.) Run the LG Mobile Support Tool program.
4.) Switched tablet USB mode to "Internet Connection / Ethernet" and after a few moments the LG Tool recognized my VK810.
5.) In LG Tool, click on "Options -> Upgrade Recovery" on the upright corner.
6.) It should start downloading stock firmware right away, if it says "Downloading" but there is no file size or progress, then you need to disable firewall.
7.) After the download, it will start "Upgrading".
8.) When the tablet rebooted I was on the latest VZW VK81024A which shocked me because I thought it was going to put the factory image (JB 4.2), but not to give up hope, I retried Stump...1st time rooted the thing!
9.) Followed Stump Root's directions (Reboot after app tells you to, Install SuperSU APK from market, Uninstall StumpRoot) and poof!
10.) Enjoy rooted 24A KitKat
It is very possible that 24A broke the fix VZW had for 23A (even though many people had success with 23A) and one need only take 24A OTA to Stumproot if they were not able to prior, but this is how my experience went down.
MANY thanks to @roirraW "edor" ehT, @jcase, & @jim380 for producing the threads and software that led to my rooting.
Root MethodAmazon has just released a new firmware update, blocking the fastboot commands necessary for root/custom ROMs (fastboot boot). We need more information about this update. If people could update their tablet to this latest version without getting it stuck in the botloop, we could see the information regarding the update and get root out for this ROM ASAP. Thanks to anyone who sacrifices root/ROMs for development.
List of things you can't do:
Downgrade to an earlier release
Boot a .img from Fastboot
List of things you can do:
Install and use the Google Play Framework and Services
Root
Install Custom ROMS via FlashFire
Remove Lockscreen Ads
Remove Amazon Bloatware
Feel free to comments things that worked/didn't work on your device.
ANYONE WHO IS ON 5.0.x AND WANTS TO GO TO 5.1.1 WITHOUT ANY COMPLICATIONS AND KEEPING TWRP, GO TO THIS LINK: http://forum.xda-developers.com/showthread.php?t=3265594
Can anyone test if the Google Framework Install tutorial works on this update?
It does.
However, DON'T TRY TO DOWNGRADE BACK TO THE 5.0.1 FIRMWARE. IT WILL BRICK YOUR DEVICE. I found that out the hard way. It's stuck in a preloader reboot-loop.
Added list of what you are able to do on the update.
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
You have to go through the setup, but originally I just skipped that part, even though I was next to a Starbucks, and it didn't connect.
Doesn't Starbucks wifi require you to click to agree to their terms of use before you can freely browse or download? So Internet would not actually be available initially to the update script.
Pretty much, I trust amazon on this issue, as far as I can throw them. I don't want to presume that a OTA proccess won't silently connect, while the Fire otherwise appears to be waiting for the ok to connect to wifi.
Bloat removal
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
craigs23 said:
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
Click to expand...
Click to collapse
Thanks, added.
This is bullsh!t. the ENTIRE reason about 5,000 people bought this tab last week is because of root, fastboot and CM. If I get my tab soon I can offer any assistance you need. I'm not sure if it will be possible to dump any part of the system, boot, etc. without fastboot or twrp, but I'm sure we could figure something out.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
When I setup mine it asked to turn on wifi I skipped it and said later.
Sent from my SM-N910T3 using Tapatalk
Has anyone tried kingroot on 5.1.1?
Experts please take a look at this
What was changed in OS 5.1.1?
If anyone can get the frimware update or capture it id like to test it out
running 5.1.1 & all I could manage to load was Google Account manager. The rest (Framework Services, etc) says something like "App not installed" & nothing else, every time I try.
scratch that..... found found a couple that did load for me.
Damn! I did this (tried to downgrade, got bricked) a day before you posted this. I should probably replace mine...
My unrooted Fire upgraded to 5.1.1 last night before I had any idea it was coming. I'm willing to try whatever is needed to assist with further research if I could be of any help.
unlikely it would work, but did anyone on 5.1.1 try
Code:
fastboot -i 0x1949 boot twrpfilename
Sent from my KFFOWI using Tapatalk
5.1.1 update file
Here is the 5.1.1 update file
snap42.com/update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip
Brand New Firestick, I blocked the first update and it wont start, since at soon It connect it want to update and of Course failed telling me to contact customer support and consequently cannot access the menu - settings - system – developer, in order to load kingroot
I blocked the update with open DNS
1. amzdigital-a.akamaihd.net
2. amzdigitaldownloads.edgesuite.net
3. softwareupdates.amazon.com
4. updates.amazon.com
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/?
is there a way to start and prevent update at least up to 5.05 and root?
guliver365 said:
Brand New Firestick, I blocked the first update and it wont start, since at soon It connect it want to update and of Course failed telling me to contact customer support and consequently cannot access the menu - settings - system – developer, in order to load kingroot
I blocked the update with open DNS
1. amzdigital-a.akamaihd.net
2. amzdigitaldownloads.edgesuite.net
3. softwareupdates.amazon.com
4. updates.amazon.com
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/?
is there a way to start and prevent update at least up to 5.05 and root?
Click to expand...
Click to collapse
Follow these instructions to get through the initial setup without updating:
http://www.aftvnews.com/how-to-complete-the-fire-tv-initial-setup-without-updating/
Then you can briefly unblock updates just long enough to see which one it's going to try to download. If it's 5.0.5 (537174420) then let it through, but if it's 5.0.5.1 (537175520) kill the power. There's no way to force it to take 5.0.5 if it tries to download 5.0.5.1. If it tries to download 5.0.5.1, all you can do is hope that rbox is able to release TWRP for the Stick and hope he releases a 5.0.5 ROM.
I am in it system 5.0.5 (537174420) but not sure why the 5.0.5.1 (537175520 has been downloaded but not installed yet waiting for the stick to be not in use, so I need a step by step to delete the download file in the cache before It got installed!
guliver365 said:
I am in it system 5.0.5 (537174420) but not sure why the 5.0.5.1 (537175520 has been downloaded but not installed yet waiting for the stick to be not in use, so I need a step by step to delete the download file in the cache before It got installed!
Click to expand...
Click to collapse
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
AFTVnews.com said:
Follow these instructions to get through the initial setup without updating:
http://www.aftvnews.com/how-to-complete-the-fire-tv-initial-setup-without-updating/
Then you can briefly unblock updates just long enough to see which one it's going to try to download. If it's 5.0.5 (537174420) then let it through, but if it's 5.0.5.1 (537175520) kill the power. There's no way to force it to take 5.0.5 if it tries to download 5.0.5.1. If it tries to download 5.0.5.1, all you can do is hope that rbox is able to release TWRP for the Stick and hope he releases a 5.0.5 ROM.
Click to expand...
Click to collapse
that guide and video are ancient, have you ever even attempted this specifically on a fire tv stick anytime in the past 2 years or even remotly recently? the video is from 2014 , i think it needs to be updated because it does not work at all any more
my fire TV stick says manufactured in mid march 2016 according to the serial #
also in the wifi password menu screen the cancel, advanced ,connect buttons are at the bottom not at the top like in the video
the guide doesn't work , the fire tv stick will not go past the error screen and get to the registration screen, there is no way to get to the registration screen using that guide
i do everything the guide says exactly, when it says connection successful i pull the ethernet cable from the back of my router going to my modem and before it gets to the checking for updates screen
then it just hangs at checking for updates for like an hour and finally goes back to the error message screen, i hit the back button like you said,i re enter the wifi information like you said and hit connect again , pull the cable once it says connection successful and before checking for updates
same thing happens every time, one giant loop
hangs at checking for updates, goes to error screen ,hit back , re enter wifi settings ,hit connect, pull cable at connection successful ,hangs at checking for updates , goes back to error screen ,hit back, infinity
your guide is old and doesn't work any more
obviously it has not been tested anytime recently and they changed something hardware of software wise in the mean time
your guide says it was "updated" but what does that even mean? yeah you update your guides but do you actually retest them with new hardware for all 3 products 1 ,2 and stick?, i highly doubt it
i highly doubt that this guide was ever re tested recently with a fire stick ,one manufactured recently with a new fw like the one before the latest or whatever fw they were shipping with in mid march
go take a ride down to best buy and pick up a new fire stick and retest it then return it see if it still works, check the SN to see if it's made in 2016 ,i bet it won't work
The way I did it :
you cannot register the stick without the update downloading, at this point you are still in 5.05 make sure you do not restart the device I was not able to find the bin file with ES so I put King root in there with adbfire succeed to root it although it start to say fail but before I start the rooting again it says root so from this I used the regular adb guide from http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/#root method 1 even after restart still at 5.05. I checked system update it give me error not still blocked by the open Dns I do not dare to remove it yet, firestarter is installing Kodi so I guess I am in business the only minor problem with fire starter the regular amazon home menu is truncated 3/4 of the screen maybe because of 4k TV and I do not have this issue with the rest of the links like your videos tv shows etc !
Hey guys! Been running fRomFuture build 201 on my VKY-L09 and haven't updated in like one year.
Right now the phone is on the june 2018 security patch and I cannot update. I would like to go back to stock.
I have tried like a dozen methods last night: HWOTA, HURUpdater, HiSuite, FunkyHuawei's unbrick tool etc. I think I am missing something here.
FH's unbrick tool does not go past the "wait 5 minutes" step, it just hangs.
The HWOTA... Well I changed the script a bunch of times for it to work properly but it seems that it flashes TWRP, then boots to it and waits for ADB and hangs. If I interfere with ADB and kill-server and start-server, the daemon cannot start any more. I tried like 3 separate twrp versions because of that and think it might actually be my adb to blame.
Saw a bunch of guys explaining how to do the dload method, but didn't manage to actually try it out.
The secret menu code method just does not see the UPDATE.APP file.
I am lost and desperate.
Can anyone please let me know what I am missing? Am I using the right build? Or is there a specific build I should be flashing to replace this old rom I am stuck on? FirmwareFinder said that most of the ones I tried were approved for install. For instance B185
P.s. the DNS method fails because my router is PPPoE and has the upstream WAN settings all greyed out. The FH Connectify method is utter crap and won't work. Traffic gets routet to a dead end if I change any dns settings.
Also HiSuite says that it can't fix my phonr lmao.
Phone can boot in fromfuture, I can install twrp on it, I just dunno how to get back to stock.
Solved with HWOTA.