Develop Bugs

can i root/rom with newest kfhd device version?

Anyone else here get the 8.4.5 update? I got it about 3-4 weeks ago and just a couple of days ago, got 8.4.6. Sent a message to Amazon to see what was fixed/added, but didn't get any information yet.
Wondering if it would effect rooting/installing CWM or CM mods.

try Bin4ry v31

hello friends,
There are already reports back whether rooten, playstore and 2nd Bootloader & TRWP with current software version 8.4.6 is still possible or has someone already tried successfully?
mfg
J-P

ver 8.46 has stolen root from my KFHD 8.9
I was running happily with ver 8.43 and had OTA blocked (?) but 8.46 got through and I can't get back to Root using any tools I've managed to find.

shibashi said:
I was running happily with ver 8.43 and had OTA blocked (?) but 8.46 got through and I can't get back to Root using any tools I've managed to find.
Click to expand...
Click to collapse
me too！
I was running 8.46，and I've searched everywhere about root！
Help me pls！

Facing the same issue!
Running 8.4.6 and the usual methods to rooting don't seem to work. Is there a work around to this?
tufeikai said:
me too！
I was running 8.46，and I've searched everywhere about root！
Help me pls！
Click to expand...
Click to collapse

lyndnpnto said:
Running 8.4.6 and the usual methods to rooting don't seem to work. Is there a work around to this?
Click to expand...
Click to collapse
I just used the method from this and it worked fine to get root.

"this" method worked for my Kindle too
Used the same method, first under Linux, which would not work, then fell back to Windows 7 which also failed saying "couldn't find specified paths".
Connected Kindle to PC before starting next run and all worked perfectly.....full ROOT and no data loss, all apps working again.
Thanks to all...

lizzord30 said:
I just used the method from this and it worked fine to get root.
Click to expand...
Click to collapse
Tried this one a few times, the computer pings the 4.2.2.2 address just fine, I installed the drivers and ran the software. when it asked me to plug the kindle in, I do so, and it continues its business , but the computer starts installing new drivers during this time.
The prompt window says that the kindle will reboot into recovery, it doesn't and in the end, it says that the kindle will reboot, but nothing happens...

[Q] New FTV ... Initial setup problem

So I have received a replacement FTV and I believe it to be rootable because it does not go to the German language in the beginning screen.
Problem I am having is I blocked the updates in my router and I can't complete the initial set up. It sends a lot of time on:
"We are trying to update your Amazon Fire TV but we cannot contact our services. We will keep trying. Please do not disconnect from the network or unplug the power cable."
Then it goes to a screen that says:
"Unable to update your Amazon Fire TV
Try disconnecting the power cable for a few seconds and then plugging it back in.
If that does not work, please try again later or contact us at www.amazon.com/firetvsupport."
Any idea how to get past this without the update?
Thanks for the help guys!

I got past it by using open dns to block the update urls instead of directly blocking on router. Then after I got past it, I switched back to blocking on router directly and disabled the update program on firetv itself.

I don't understand how opendns.com will work for this? If that works would privateinternetaccess.com also work? I normally am running pptp with them for added security as I browse or do whatever I do.

draky said:
So I have received a replacement FTV and I believe it to be rootable because it does not go to the German language in the beginning screen.
Problem I am having is I blocked the updates in my router and I can't complete the initial set up. It sends a lot of time on:
"We are trying to update your Amazon Fire TV but we cannot contact our services. We will keep trying. Please do not disconnect from the network or unplug the power cable."
Then it goes to a screen that says:
"Unable to update your Amazon Fire TV
Try disconnecting the power cable for a few seconds and then plugging it back in.
If that does not work, please try again later or contact us at www.amazon.com/firetvsupport."
Any idea how to get past this without the update?
Thanks for the help guys!
Click to expand...
Click to collapse
If you are blocking the update server and get this it 99% mean it's running 51.1.0 and the first update it will take is 51.1.0.2. Then it'll try to update to the latest. If that's the case, you need to unblock the servers, let it download the update, and then when it reboots to install it, reblock them.

rbox said:
If you are blocking the update server and get this it 99% mean it's running 51.1.0 and the first update it will take is 51.1.0.2. Then it'll try to update to the latest. If that's the case, you need to unblock the servers, let it download the update, and then when it reboots to install it, reblock them.
Click to expand...
Click to collapse
So I let the system download the first update, unplugged the ethernet line as it restarted. Then I blocked the updates sites and plugged it back in... Now I'm sitting at sw version 51.1.4.0. Guessing there's nothing I can do about it now...

draky said:
So I let the system download the first update, unplugged the ethernet line as it restarted. Then I blocked the updates sites and plugged it back in... Now I'm sitting at sw version 51.1.4.0. Guessing there's nothing I can do about it now...
Click to expand...
Click to collapse
Really, there is no way to bypass a forced update... but it finally looks like they've caught on to us. Doesn't seem like good news.

draky said:
Any idea how to get past this without the update?
Click to expand...
Click to collapse
Hi,
i have the same problem.
Trying to finish initial setup without updating firmware.
At first start, Network found and started downloading Update.
So i turned it off and blocked the updateserver at router.
But can´t pass setup this way...

There's a guide on AFTVNews on how to bypass the mandatory update. Does that guide no longer work?

I wiped and installed latest pre-rooted software and could not get past checking for updates using blocks on router. Switched to open dns and went right through. Then I switched back to router. Just my experience.

16Darknight said:
There's a guide on AFTVNews on how to bypass the mandatory update. Does that guide no longer work?
Click to expand...
Click to collapse
it still works,
thank you

I know this is too late for OP, but incase someone comes across this thread looking for an answer, here is my guide to bypass the forced update:
http://www.aftvnews.com/how-to-get-passed-a-forced-software-update-on-the-amazon-fire-tv/

AFTVnews.com said:
I know this is too late for OP, but incase someone comes across this thread looking for an answer, here is my guide to bypass the forced update:
http://www.aftvnews.com/how-to-get-passed-a-forced-software-update-on-the-amazon-fire-tv/
Click to expand...
Click to collapse
And looks like I may get lucky... After it was funny loaded up I immediately preformed a master reset on the device just to see if everything took or if I happened to get lucky and something didn't load right and I was right. I go in, choose my language, put in my amazon account (it knows when I put in the wrong account) and then tries to register the device and while it's doing that it's flashing back and forth with a screen that says it doesn't have network connectivity but the box still has the white light.
I plug in my old box, lights up and connects just fine. I let it sit tonight for 20 minutes and still didn't work right so I'll be calling them tomorrow to see about replacing this one. Looks like the software update maybe didn't get loaded right.

I got through the initial setup following AFTVnews guide. Unluckily my Gernan FTV was on 5.1.3.0 from the start on, so i can't root and use the update blocking tool. Still having the update servers blocked the FireTV is almost unusable since it complains about not having a network connection. XBMC works fine but i can't use Amazon instant video. I blocked amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
via router. any advice what i can change to continue blocking updates, but still access Amazon content?
Gesendet von meinem SM-N9005 mit Tapatalk

{ParanoiA} said:
I wiped and installed latest pre-rooted software ...
Click to expand...
Click to collapse
Beginning with which version, please?

Was on whatever came before 51.1.4.0 and did full wipe and then installed 51.1.4.0 and that's when I had to use opendns. After that I just flashed 51.1.4.1 over top of it because of the requirements.

{ParanoiA} said:
Was on whatever came before 51.1.4.0 and did full wipe and then installed 51.1.4.0 and that's when I had to use opendns. After that I just flashed 51.1.4.1 over top of it because of the requirements.
Click to expand...
Click to collapse
Bummer. It was 51.1.1.0 or earlier.
Wishful thinking...

What I've discovered is in the serial number range of the units themselves. If the unit has a serial of 7090020141....anything after that from 0 to 4 will not root....it will automatically jump to the "your unit requires an update" screen...no way around it. If the serial is 7090020141.....5 and above it will root.
I have rooted almost 100 units in the past 2 weeks and it is the same every time.... Perhaps I'm wrong....but I think not.
At this point I can look at the serial and tell you if it will root or not.

5.1.1 OTA update not working

My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.

traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.

Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.

traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.

traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!

I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937

traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....

Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.

traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous

Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....

traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.

Fire TV 1 and 2 both exhibiting same issues

I have 3 rooted Fire TVs (4K and standard).
I believe they recently tried to take an update (though I thought I had it blocked).
At any rate, they all are falling back to TWRP no matter what I try to do. They also all fail to mount cache. If I try to do anything in TWRP from wiping to anything I get mounting errors. I can flash a new image but on system reboot they always fail to launch. I've tried a couple of things I've seen online about ext4 and changing file system and same errors. They were all running the latest rbox pre-rooted images (july release)
Any suggestions on recoverying these Ftvs?
Thanks

Endosmok said:
I have 3 rooted Fire TVs (4K and standard).
I believe they recently tried to take an update (though I thought I had it blocked).
At any rate, they all are falling back to TWRP no matter what I try to do. They also all fail to mount cache. If I try to do anything in TWRP from wiping to anything I get mounting errors. I can flash a new image but on system reboot they always fail to launch. I've tried a couple of things I've seen online about ext4 and changing file system and same errors. They were all running the latest rbox pre-rooted images (july release)
Any suggestions on recoverying these Ftvs?
Thanks
Click to expand...
Click to collapse
No suggestions on how to fix, but my Fire TV 1 is doing the same thing. I'm rooted with rbox 5.2.4.1 and it is trying to update to 5.2.6.0. I wondered why i kept checking box and it was in TWRP.

dk1keith said:
No suggestions on how to fix, but my Fire TV 1 is doing the same thing. I'm rooted with rbox 5.2.4.1 and it is trying to update to 5.2.6.0. I wondered why i kept checking box and it was in TWRP.
Click to expand...
Click to collapse
still not sure what has caused it but used this method 1 http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/ to re-block updates. it survived a reboot also.

Thanks... I tried but without success... I seemed to have lost root but still have TWRP. Any adb shell command kicks me back to not found. Did you still have root when you tried or?
dk1keith said:
still not sure what has caused it but used this method 1 http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/ to re-block updates. it survived a reboot also.
Click to expand...
Click to collapse

Endosmok said:
Thanks... I tried but without success... I seemed to have lost root but still have TWRP. Any adb shell command kicks me back to not found. Did you still have root when you tried or?
Click to expand...
Click to collapse
I still had root. To disable updates I had to adb shell and su to execute the disable.

I’m having same issue on my 1st gen ftv, I was able to disable the ota, hope this fixes the reboot.
Thanks

justdoit2552 said:
I’m having same issue on my 1st gen ftv, I was able to disable the ota, hope this fixes the reboot.
Thanks
Click to expand...
Click to collapse
Update,disabling the update helped solve this issue.

Or you could just update to the latest rooted version.

1st Gen FireTV stuck an Amazon FireTV logo

I have a rooted 1st Gen with 5.0.5.1 on it
I used software ver 51.1.4.0
Now Im suck cant connect ADB

trickyrick said:
I have a rooted 1st Gen with 5.0.5.1 on it
I used software ver 51.1.4.0
Now Im suck cant connect ADB
Click to expand...
Click to collapse
Did you try clearing cache? Maybe you need to do a factory reset?

I only know how to do that when the firetv will boot. Using the remote will not work. Clearing cache also FTC needs to boot. I'm stuck on the logo
Thanks for the suggestions

trickyrick said:
I'm stuck on the logo
Click to expand...
Click to collapse
Why you flash a fireOS 3 version over a fireOS 5?
If the FireTV Boot Menu doesn't show up at boot, your box is probably dead.
Only way to recover is with a low voltage emmc adapter soldered to the EMMC, but this costs about the same as a new stick.

You may want to give the link below a try. I did the opposite by going from fireOS3 to fireOS5 without installing bueller_recovery_v2.zip first and has a similar issue. I was able to get my box working, however there are a few issues. ADB doesn't work, supersu is still running as a service. I'm stuck on software 5.2.6.3, prime video doesn't work and it tries to install os updates every time i rebooted the box.
I eventually got prime video working by installing a newer Video_com.amazon.avod.apk from one of my other box and i broken checking for updates by installing a newer DeviceSoftwareOTA_com.amazon.device.software.ota.apk and System Updates_com.amazon.device.software.ota.override.apk.
The box is running great except for os updates and adb.
https://forum.xda-developers.com/fi...ock-images-t2882337/post56987752#post56987752