Hi all
A couple of weeks ago I upgraded my rooted gen 1 fire tv to os 5 software and used twrp (previously using clockwork mod as per guides online). Anyway, it worked but i dont think i blocked updates and have since updated to OS 5.2.1.0 and appear to have lost root. No biggie since i didnt use it anyway.
One thing which is really annoying though is that 1-2 times a day ill turn the tv on and the fire tv has reset and is on the twrp screen. I fix this by unplugging the power and the fire tv reboots to its normal homescreen. Im just wondering what is an easy fix for this? Can i get rid of twrp? Do i do a reset of some form? I dont want to lose all my apps and kodi if possible.
I assume it is doing this for a particular reason, maybe looking for updates or something? I havent blocked updates at my router and really dont care too much anymore and am happy to run stock.
Cheers
cbarre said:
Hi all
A couple of weeks ago I upgraded my rooted gen 1 fire tv to os 5 software and used twrp (previously using clockwork mod as per guides online). Anyway, it worked but i dont think i blocked updates and have since updated to OS 5.2.1.0 and appear to have lost root. No biggie since i didnt use it anyway.
One thing which is really annoying though is that 1-2 times a day ill turn the tv on and the fire tv has reset and is on the twrp screen. I fix this by unplugging the power and the fire tv reboots to its normal homescreen. Im just wondering what is an easy fix for this? Can i get rid of twrp? Do i do a reset of some form? I dont want to lose all my apps and kodi if possible.
I assume it is doing this for a particular reason, maybe looking for updates or something? I havent blocked updates at my router and really dont care too much anymore and am happy to run stock.
Cheers
Click to expand...
Click to collapse
The device shouldn't be restarting by itself at all, let alone that often. Maybe wipe and reflash the ROM?
I figured it was something to do with it looking for updates but was surprised that It kept happening even after upgrading to a non pre-rooted rom.
Can I still flash a rom even if I don't have root? Which rom do I do?what the fire TV currently has ? Is there any way of just removing twrp?
cbarre said:
I figured it was something to do with it looking for updates but was surprised that It kept happening even after upgrading to a non pre-rooted rom.
Can I still flash a rom even if I don't have root? Which rom do I do?what the fire TV currently has ? Is there any way of just removing twrp?
Click to expand...
Click to collapse
Sounds to me like it downloaded a stock update but never installed it. You're seeing it sitting on TWRP randomly because after downloading an OTA update, the Fire TV reboots into stock recovery to install the update. Since your stock recovery has been replaced by TWRP, the OTA update is rebooting into TWRP and just sitting there because rbox made it so TWRP wont install OTA updates.
If you want to have a rooted device, install the latest pre-rooted ROM (5.2.1.1) from within TWRP and block updates. You'll also want to follow the "If your device is rooted and still powered on" section of this guide to clear the pending OTA update that's causing the reboots.
If you want to unroot, remove TWRP, and go back to stock, then follow this guide.
I have tried to follow the guide to unroot as suggested at the bottom, but when i go to install in twrp it says "updater process ended with ERROR: 255" "Error installing zip file '/sdcad/sloane-5.0.4-rooted_r2.zip'
Any thoughts?
cbarre said:
I have tried to follow the guide to unroot as suggested at the bottom, but when i go to install in twrp it says "updater process ended with ERROR: 255" "Error installing zip file '/sdcad/sloane-5.0.4-rooted_r2.zip'
Any thoughts?
Click to expand...
Click to collapse
SOrry, but I'm not familiar with that error. The only things I can suggest are wiping everything except system from within TWRP and then trying again. Otherwise, maybe @rbox can help.
Could it be that gen2 roms don't work on gen1?
hmm, dont know. Is there a Gen 1 option?
Don't know as i don't have a gen1 device. If i was you i would just upgrade to the latest prerooted rom and follow AFTVnews guide to remove any pending ota.
Afterwards you can block future ota's by issuing following command as root:
Code:
pm disable com.amazon.device.software.ota
WheelchairArtist said:
Could it be that gen2 roms don't work on gen1?
Click to expand...
Click to collapse
cbarre said:
hmm, dont know. Is there a Gen 1 option?
Click to expand...
Click to collapse
Not quite sure what would happen if you tried installing a Gen 2 ROM on a Gen 1 Fire TV, but you definitely shouldn't be doing it.
Fire TV 1 pre-rooted ROMs are here.
Fire TV 2 pre-rooted ROMs are here.
It's odd that you say you installed an OTA update that removed root, yet you still have TWRP. OTA updates are incremental (partial) updates. Before installing, they check system and/or recovery to make sure everything is on the up-and-up. If the device is rooted, the check fails and the device will then download a full version of the latest update that includes stock recovery. So, going by everything I've observed, either you lose root and TWRP simultaneously, or the OTA update doesn't install. If you really did install an OTA update, lose root, and NOT lose TWRP, then it seems somehow you installed an incremental OTA update on a pre-rooted ROM. I don't know how to proceed from here because I've never heard of this happening and in theory it shouldn't ever happen.
WheelchairArtist said:
Could it be that gen2 roms don't work on gen1?
Click to expand...
Click to collapse
I should have put an /s in that post
My advice would be the same as the one from AFTVnews. Just don't try do install a gen2 rom even though it shouldn't work.
Edit: Forgot this one: "updater process ended with ERROR: 255" "Error installing zip file '/sdcad/sloane-5.0.4-rooted_r2.zip'
As you see it doesn't work anyway.
AFTVnews.com said:
If you really did install an OTA update, lose root, and NOT lose TWRP, then it seems somehow you installed an incremental OTA update on a pre-rooted ROM. I don't know how to proceed from here because I've never heard of this happening and in theory it shouldn't ever happen.
Click to expand...
Click to collapse
If this would be the case he could still install any prerooted rom since he still has trwp and so a working custom recovery. In the worst case he needs to wipe data/cache or something like that after flashing.
And so my advice would be: flash latest prerooted, keep root, follow your guide to clean pending ota or wipe data, block further ota's and profit.
I don't know how Rbox implemented this on gen1 but he could also try to install for example the first official full ota (not incremental) to android 5 manually in twrp to make sure the recovery returns to stock as well. But that is just off the top of my head, don't know if this works that way.
Someone has the recovery files for the Firetv Stick 4k, i need to remove twrp because i send it back to amazon
test10000001 said:
Someone has the recovery files for the Firetv Stick 4k, i need to remove twrp because i send it back to amazon
Click to expand...
Click to collapse
Just flash original boot.img from the stock rom.
Related
Ok I have packaged up the 6.2.1 update with only the files changed or modified from 6.2
Included in this is:
unsecure boot image
busybox
su binary
and su apk
This is for anyone with root and TWRP already installed and still on 6.2
this will not format system it will just update the need files.
So all added apps will remain and all data will be intact.
Install and wipe dalvik and cache, then reboot
Download
This had already been done in both secure an unsecure boot images. Wait, sorry, didn't see the modded from 6.2 part...
this is only to update 6.2 to 6.2.1 without wiping the system partition. There was no need to flash the entire update as large portion of the package was the same when compared.
This is also to save the hassel of having to reinstall / reconfig everthing.
Yeah, I figured that out after I posted. My appologies. This should make it a little easier.
Won't get to it for a week because of the holiday but this sounds great. But just to be sure. I'm on 6.2 only right now. I download and install this and I magically get 6.2.1 without being too worry over losing root or changes I made to the /system partition, correct? Does this also mean I don't have to worry about the OTA update coming along and messing things up?
Sent from my HTC Flyer P512 using Xparent Purple Tapatalk
yes you dont have to worry about anything that was added to or modiied on your 6.2 it will remain, as for the OTA update, I cant verify that it wont end up trying to install, but if it actually verifies the system first then you should be good to go.
I did my wifes kindle yesterday and it hasnt tried to update at this point.
Ok, this POS just bricked my Kindle Fire.
Do NOT INSTALL!!!!!
Installed via TWRP.
Rebooted.
Got stuck at the "Kindle Fire" boot logo.
Check the bootmode via the Kindle Fire Utility and tried to change it.
Now all I get is the FireFirefire logo and NOTHING ELSE!!!
No ADB and NO fastboot.
Edit: was able to get ADB and fastbook working thanks to this post (http://forum.xda-developers.com/showthread.php?p=20631342#post20631342), though something in this update destroyed my ability to get into TWRP. Still: Do NOT flash.
andTab said:
Ok, this POS just bricked my Kindle Fire.
Do NOT INSTALL!!!!!
Installed via TWRP.
Rebooted.
Got stuck at the "Kindle Fire" boot logo.
Check the bootmode via the Kindle Fire Utility and tried to change it.
Now all I get is the FireFirefire logo and NOTHING ELSE!!!
No ADB and NO fastboot.
Edit: was able to get ADB and fastbook working thanks to this post (http://forum.xda-developers.com/showthread.php?p=20631342#post20631342), though something in this update destroyed my ability to get into TWRP. Still: Do NOT flash.
Click to expand...
Click to collapse
Wow really this is only the software update has nothing to do with the bootmode. This will take a while to boot as the dalvik needs rebuilt but should boot within 5 minutes.
I tested this several (at least 20) times after restoring my system to the 6.2 backup everytime and never had an issue.
nfinitefx45 said:
Wow really this is only the software update has nothing to do with the bootmode. This will take a while to boot as the dalvik needs rebuilt but should boot within 5 minutes.
I tested this several (at least 20) times after restoring my system to the 6.2 backup everytime and never had an issue.
Click to expand...
Click to collapse
Sorry if I was a little harsh, but I was - hopefully understandably - quite upset.
This update did not work for me and bricked my fire installation.
I left it on for at least 20-30 minutes to give it a chance to boot. No dice.
Maybe you included something specific to your KF?
andTab said:
Sorry if I was a little harsh, but I was - hopefully understandably - quite upset.
This update did not work for me and bricked my fire installation.
I left it on for at least 20-30 minutes to give it a chance to boot. No dice.
Maybe you included something specific to your KF?
Click to expand...
Click to collapse
no nothing other then the updated files, busybox, SU, where added.
You did follow my instructions and ONLY wiped dalvic/cache correct?
this is not a full install it is only for updating/upgrading your current version.
By the way I am not new to android so I do know what I am doing and have run this now on 4 more devices for friends without issue.
I am sorry for your problems but I can not replicate this issue that you have seen.
THANKS!
I chanced it, installed per instructions, and it worked fine. I'd been holding off on 6.2.1 cause I didn't want to re-do all the work I'd done setting up my Fire with the Google services. This is exactly what I wanted -- a way to go to 6.2.1 without wiping. The only oddity is a few apps have lost their icons (like XDA Premium, PocketCloud, and one more). They now have a no-name icon with just little black squares. Easily remedied with a reinstall of the apps I'm sure.
jb0ne said:
I chanced it, installed per instructions, and it worked fine. I'd been holding off on 6.2.1 cause I didn't want to re-do all the work I'd done setting up my Fire with the Google services. This is exactly what I wanted -- a way to go to 6.2.1 without wiping. The only oddity is a few apps have lost their icons (like XDA Premium, PocketCloud, and one more). They now have a no-name icon with just little black squares. Easily remedied with a reinstall of the apps I'm sure.
Click to expand...
Click to collapse
Glad to hear it worked for you, and yes a reinstall or update install should correct the issue.
Sure did! Thanks a lot for putting this together for us. 6.2.1 is much snappier but I really didn't want to jockey this thing anymore, I wanted to use it. This took less than 10 minutes.
Sent from my Kindle Fire using xda premium
Would like you to know that my Kindle Fire installed the update and is now back to a stock state (need to re-root, and install firefirefire and TWRP).
pyrostic said:
Would like you to know that my Kindle Fire installed the update and is now back to a stock state (need to re-root, and install firefirefire and TWRP).
Click to expand...
Click to collapse
Sorry to hear that it got pushed onto you, still working fine on my wifes, hasnt updated since I installed this update, but you can never tell untill we get a way to bypass the FOTA updates
could you do the same for 6.2.2 please ?
6.2.2 update amazon:
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.2.2_D01E_3205220.bin
that would be greatly appreciated by so many users !!!
thank you very much !
Update for 6.2.2 released
nfinitefx45 said:
Update for 6.2.2 released
Click to expand...
Click to collapse
you'r incredible !!!
thank you !
So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
http://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
From the OP rbox:
"Starting with 51.1.4.1, these require FireTV Boot Menu. For the time being, you must update to 51.1.4.0 before updating to 51.1.4.1. Also, if you flashed 51.1.4.0, you must flash bootmenu afterwards. If you are already on 51.1.4.0, then you just need to flash bootmenu."
stutunaru said:
So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
Click to expand...
Click to collapse
You kinda lost me there...but here's what I know
I'm almost certain its not possible for you to have boot menu and cwm without fully functional root privs
[email protected] is what it should say (does it go straight to that after inputting shell? Do you get the # sign?) That means bootloader is fully unlocked.
Supersu on aftv doesn't open and allow you to configure but it works. Not sure why but that's the way its been for a long time.
I think you're all set but sort of skimmed your post. Maybe someone else has insights.
stutunaru said:
So, the other day i have started on rooting the AFTV of a friend of mine. i rooted mine a while ago and was comfortable enough to do it for someone else.
was following the AFTVnews.com guide (very well organized site and i would say a wiki for all aftv users). the initial version on the box was 51.1.0.1. have succesfuly rooted it, installed customer recovery, busybox, bootmenu, etc, all as per the guide. have upgraded it to 51.1.4.0_514006420 updated succesfuly as well again using aftvnews.com after which have installed the busybox again. now here the strange things happen. have decided to keep upgrading it to the latest version 51.1.5.0_515030720, according to the description i could upgrade straight to this version from 51.1.4.0_514006420. followed the same upgrade procedure and after the reboot in CWM i get the Amazon Fire TV logo and doesnt do anything, left it for about 10 min - nothing. power cycled it still the coloured logo. which means somehow it got software bricked.
started to google the ways of unbrick it and followed the procedure with the USB keyboard, it worked well for me. i got in to CWM recovery and did factory reset after which reboot. no luck, still showing the coloured logo.
got back in to recovery using the same USB keyboard method and did again factory reset after which decided to install the 51.1.4.0_514006420 updated custom ROM again which was already on my sdcard.
installed successfully, rebooted and started to configure the brand new aftv box - language, network, register, etc. after all this got on home screen, system to find out that it has the stock 51.1.4.0 version (51.1.4.0_user_514006420). what is interesting that the supersu is already there but without the option to launch it, only force stop, clear data and cash.
tried towelroot but obviously no luck, it sais your phone is not supported. so i guess that's it, no more root for me.
where the hell i missed it? i followed every step carefully.
and why in the first place after upgrade from 51.1.4.0_514006420 to 51.1.5.0_515030720 i got bricked?
please tell me there's still hope to root it.
Update: despite the fact that towelroot cant root my box anymore i was able to install busybox and kernel boot menu succesfuly and granted super user permissions. the adb shell shows as [email protected] something is not right, looks like a partial root to me.
please advise.
have attached below a few screen shots.
Click to expand...
Click to collapse
Sounds like you installed 51.1.4.0 AFTER installing the bootmenu. You're supposed to install 51.1.4.0 first, then the boot menu, then the latest ROM. It's a simple enough fix. Just follow the "Resetting with Recovery Mode" portion of my guide here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
AFTVnews.com said:
Sounds like you installed 51.1.4.0 AFTER installing the bootmenu. You're supposed to install 51.1.4.0 first, then the boot menu, then the latest ROM. It's a simple enough fix. Just follow the "Resetting with Recovery Mode" portion of my guide here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Click to expand...
Click to collapse
@AFTVnews.com here are two separate issues im trying to find explanation:
1. why after installing rooted 51.1.5.0 i got brisked even i was following the same guide as for 51.1.4.0. i think i haven’t missed anything in there.
2. during the recovery the only missed step was nr.2 (missed to wipe cash partition). the question is why as a result of flashing the rooted 51.1.4.0 i got the stock one? (51.1.4.0_user_514006420)?
and the bootmenu i have installed only after applied 51.1.4.0->BusyBox->bootloader.
all works as should except the towelroot and partially supersu. why partially supersu because it still does what should, grants permissions to application but i cant open it, cant remove it, cant update it.
should i go ahead and apply the last rooted release (51.1.5.0_515030720)?
KLit75 said:
You kinda lost me there...but here's what I know
I'm almost certain its not possible for you to have boot menu and cwm without fully functional root privs
[email protected] is what it should say (does it go straight to that after inputting shell? Do you get the # sign?) That means bootloader is fully unlocked.
Supersu on aftv doesn't open and allow you to configure but it works. Not sure why but that's the way its been for a long time.
I think you're all set but sort of skimmed your post. Maybe someone else has insights.
Click to expand...
Click to collapse
according to AFTVnews.com the verification of unlocked bootloader was the adb shell. right after it i get [email protected]:/ #
http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked/
cd2022 said:
http://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
From the OP rbox:
"Starting with 51.1.4.1, these require FireTV Boot Menu. For the time being, you must update to 51.1.4.0 before updating to 51.1.4.1. Also, if you flashed 51.1.4.0, you must flash bootmenu afterwards. If you are already on 51.1.4.0, then you just need to flash bootmenu."
Click to expand...
Click to collapse
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
stutunaru said:
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
Click to expand...
Click to collapse
The rbox ROMs and the stock ROMs are named identically, as far as I know. As far as I know
Towel root probably sees the preroot fw as unsupported because the same version of stock is most definetly unsupported. I never tried because I am rooted so there was never a need.
You are rooted
You have unlocked the bootloader
Supersu is working
You have cwm
When I said you lost me there...I meant from reading your op I can't see anything that indicates you screwed up. In fact, I accidentally tried to flash a stock ROM when I was going through that long process but it won't flash. Rbox designed it to fail so we won't brick. So as far as I know there is no way to be running stock with a custom recovery and to have custom recovery you must be rooted. I could be missing something but I don't see what?
Have you tried flashing a more recent update?
***but don't just try it without ensuring prerequisites are met. Like many others I do things like root and unlocknjust once. There's a definite order to this that can't be overlooked.
Just grab the seeder.apk and try to enable it.
If it enables successfully,then you have root access.
stutunaru said:
and i did flash the bootmenu after 51.1.4.0. the question is why after rooted 51.1.4.0 i got 51.1.4.0_user_514006420 which is stock ROM. also why if i have all tools mentioned for root on my aftv the towelroot says not supported?
is there anyway of starting allover again beeing on 51.1.4.0?
it's probably easier to do that then to troubleshoot why all these happened
Click to expand...
Click to collapse
The pre-rooted ROM and the stock software update report the exact same software version number when you look in the Fire TV's about section. Saying "i got 51.1.4.0_user_514006420 which is stock ROM" is silly since the pre-rooted ROM will also say 51.1.4.0_user_514006420. Also, SuperUser not launching is a known issue. It is that way for everyone using the SuperUser app that is included in the pre-rooted ROMs.
You bricked because you either did not install the boot menu or you messed up the boot menu installation. Simple as that.
If you're running 51.1.4.0 right now, then:
Install BusyBox
CAREFULLY install the boot menu
Test that the boot menu is working by restarting your Fire TV and using the boot menu to enter recovery
Then finally, install the latest pre-rooted ROM
AFTVnews.com said:
The pre-rooted ROM and the stock software update report the exact same software version number when you look in the Fire TV's about section. Saying "i got 51.1.4.0_user_514006420 which is stock ROM" is silly since the pre-rooted ROM will also say 51.1.4.0_user_514006420. Also, SuperUser not launching is a known issue. It is that way for everyone using the SuperUser app that is included in the pre-rooted ROMs.
You bricked because you either did not install the boot menu or you messed up the boot menu installation. Simple as that.
If you're running 51.1.4.0 right now, then:
Install BusyBox
CAREFULLY install the boot menu
Test that the boot menu is working by restarting your Fire TV and using the boot menu to enter recovery
Then finally, install the latest pre-rooted ROM
Click to expand...
Click to collapse
Might be. i might've overlooked something during the process.
last night have applied the latest pre-rooted ROM and so far so good.
appreciate all your help folks.
:good::good::good:
Hi Guys,
so this morning my SW3 told me there was a system update, cool, so i said yes to the update and let it do its thing.
on coming back, the os version was still the same (LDZ22D) which i thought was odd.
I then did a search and found that there was indeed a new version out (LCA43) and thought something sus was afoot.
I got the twrp from this post http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501 and booted from twrp
i then pushed the rom i downloaded form here http://www.xperiablog.net/2015/08/2...-update-lca43-intros-interactive-watch-faces/ and promptly tried to flash it like i would any custom rom i would normally flash on any of my other android devices.
I got an error, saying it was expecting "test keys" from a LAZ22D device or a LWX49K device, and that I had LRX22G test keys.
I also tried an ADB sideload which also didn't work.
Am i doing something wrong? Has anyone else ever encountered this?
Full disclosure, I also installed supersu a few months ago, but have had many factory resets since then (new roms on the paired fone) which i wouldn't have thought was an issue?
Cheers for any help you can give
That update only works on stock recovery. Go to my rollback thread and install the complete system of 5.0.1. I put links and directions to all the files. Then roll forward.
Thanks for that @lekofraggle, but I found an easier option, install Sony companion software, reflash "latest" firmware (apparently LAZ22D) then sideload the original update zip. Worked just fine. Just to clarify, I never flashed twrp, just hot booted from it, wondering if root did break ota...
Sent from my Nexus 7 WIFI using Tapatalk
Yes, root breaks most otas, but adb sideload usually works. Glad it was simpler than my doomsday thoughts.
I did this a while ago when development was really slow and flashing pre rooted roms was a hassle. I disabled updates via the "pm disable com.amazon.dcp" method while I had root. After a while the AFTV got sluggish and so I decided to sideload a stock image and lose root in order to stay up to date with the newest software. Well, I forgot to enable updates again before sideloading the stock rom and losing root. Now my device can't update, I can't sideload even stock images I don't believe, and I'm stuck on a version that is not rootable. Am I completely screwed because I did not "pm enable com.amazon.dcp" prior to flashing a stock image?
.Gibson. said:
I did this a while ago when development was really slow and flashing pre rooted roms was a hassle. I disabled updates via the "pm disable com.amazon.dcp" method while I had root. After a while the AFTV got sluggish and so I decided to sideload a stock image and lose root in order to stay up to date with the newest software. Well, I forgot to enable updates again before sideloading the stock rom and losing root. Now my device can't update, I can't sideload even stock images I don't believe, and I'm stuck on a version that is not rootable. Am I completely screwed because I did not "pm enable com.amazon.dcp" prior to flashing a stock image?
Click to expand...
Click to collapse
Do a factory reset.
I just posted something quite similar to this... I should've scrolled down a little bit before posting.
rbox, I'm in the same situation. I already did a factory reset before I ran the official updater, but the stock update never gets past the white fire logo after the reboot. If I hard boot it, I'm back to my old rom....
rbox said:
Do a factory reset.
Click to expand...
Click to collapse
Wow, after all these months and trying multiple solutions I never thought to factory reset. I feel silly. Thank you so much, it worked like a charm and I am able to update to the latest. Take care.
I have not been able to update my shield tv 2015 16gb device to 5.2.
The device is rooted with latest 3.1.1 TWRP recovery. Each time I select upgrade with the stock settings it will reboot into recovery and won't update.
Does anyone have a link to the latest ROM or know where Nvidia stores the OTA file? I would rather flash the image my self if I can find get the ROM.
I'm sure this we'll help a few other people I can't be the only one with this issue. Need the 5.2 image not the 5.0.2 which is the previous version of Shield experience update.
you should not flash TWRP to your device reflash original recovery and remove su then try update again
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
.)
Click to expand...
Click to collapse
i didnt know that :good:
but if he has TWRP installed couldnt he format data pation from TWRP thus saving hours of thumb twiddling
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Click to expand...
Click to collapse
Obviously thats a much longer and worse route.
afgok said:
you should not flash TWRP to your device reflash original recovery and remove su then try update again
Click to expand...
Click to collapse
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
On another thread looks like others are having this same issue with only this version 5.2.. ill just wait for the Dev Images to show up hopefully soon.
I unrooted but still got the same issue, it wont install. But I also have another issue, i can't restore my 2015 shield 16gb by using official recovery rom and official tutorials. It consistently fails to flash system.img and vendor.img by saying that the data is too large. The only way I got my system back was by flashing this file https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062 through twrp
Diehardshorty said:
Obviously thats a much longer and worse route.
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Ichijoe said:
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Click to expand...
Click to collapse
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
If you're rooted, the right answer is to wait for Nvidia to release the 5.2 image.
If you absolutely need 5.2 right now for some reason, several people said that doing a factory restore worked. Just unrooting and restoring stock recovery won't do it, you need to do a full restore.
Diehardshorty said:
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
Click to expand...
Click to collapse
The Dev images are quite a bit different, and are also on an entirely different timeline to either the Preview, (Which I'm on), or the most current version.
But, yeah I could see how those would work. Alas mores the pitty that the rooted asspects of those Dev Images, only go as far as ADB, and not say a full /system wide root. Than again... It's probably for the best that way.
But, that doesn't really change the answer if you want / need to update (From root), than you are going to have to bite the big One, and run a Factory Reset. Which again, on the Pro, means a 2h+ reformating (zeroing out), of the /data Partition.
16gb version doesn't take as long to format but I've always remember flashing SuperSU.zip after ROM just incase. Short response for now at work.
Diehardshorty said:
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Use to be here:
/data/data/com.nvidia.ota/app_download
You obviously need root to reach that folder...
If i have time i will upload later this small OTA update to MEGA.
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
sammarbella said:
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
Click to expand...
Click to collapse
Sweet thanks I'll give that a try from the sounds of it it might not work but I'll give a shot after work. Thanks
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Diehardshorty said:
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Cameron581 said:
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Click to expand...
Click to collapse
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Diehardshorty said:
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Click to expand...
Click to collapse
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Cameron581 said:
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Click to expand...
Click to collapse
Ahhhhh that missing point for "error 7".
So the new app bypass that problem!
Thanks for posting it. :good: