Related
I thought I read that it will prevent them.
Or is it just a custom recovery (CWM) that will prevent them?
I just wanted to make sure I get 4.2 on day one one is released.
That is one of the greatest mysteries of the Common Era, especially since there at least 50 past threads on this subject, and yet it is impossible to find an answer (apparently)...
BTW - you do realize that with a rooted phone and custom recovery you can actually flash what the hell you like, and don't have to wait for someone to push it to you...?
Yes, I realize that you can flash broken or preview builds of new releases...or nightlies with broken features.
I'm interested in stable builds only.
That's why I'm asking.
With the Galaxy Nexus, the dev teams usually have the OTA available to flash within a day of it hitting. You will typically get it from devs before your device will let you OTA.
Root users (especially on nexus devices) always get it first!
Another good thing about Nexus is that its gonna be a stable release.
Rooting doesn't prevent OTAs. Now a custom recovery on the other hand will stop automatic install but it will still download and try.
Root itself doesn't stop an OTA. Custom recovery, different radios, and changed/modified/removed system apps/files do.
Ruggerxpunk said:
I thought I read that it will prevent them.
Or is it just a custom recovery (CWM) that will prevent them?
I just wanted to make sure I get 4.2 on day one one is released.
Click to expand...
Click to collapse
I also agree that it's CWM that prevents the OTA update from being written to your Nexus. Yesterday I was in the same situation as you (unlocked bootloader and rooted) with stock Jelly Bean 4.1.1. I downloaded the new 4.1.2 file from google and followed these excellent instructions:
(had to remove link....not enough posts...go figure)
The mistake I made yesterday, even though I had an existing BU made by Titatium Pro, I didn't copy that BU to my PC so I didn't get my apps data updated (messed up a game, email configuration, groove ip, google voice)....learned on that one:>)
martonikaj said:
Root itself doesn't stop an OTA. Custom recovery, different radios, and changed/modified/removed system apps/files do.
Click to expand...
Click to collapse
This.
If you root and remove system apks like Google plus or currents, any ota update will fail to install, even on stock recovery with locked boot loader.
Sent from my Galaxy Nexus using xda premium
More accurately, it's the update script that stops the install of OTA's.
OTA's are typically a patched update, rather than a full update (meaning they only update parts of the OS). The OTA's are typically designed and tested to update X to Y, and are not designed for U, V or W to Y. In order to make sure that the update is actually updating X, and not U, V or W, the install script makes certain hash tab type checks on items such as Recovery, specific system apps, and even the Bootloader. Files that get added to the system, such as su and SuperSu, busybox, etc, are not typically checked for their presence during the install process.
Not every OTA is the same, and not not every install script is the same. Past experience shows that Recovery, system apps, and sometimes Bootloader need to be un-modified for the script to pass its checks and balances, but there's no guarantee that this will be the case for the next update. On the Nexus One, it threw everyone for a loop when the updates started checking the Bootloader for the first time, especially since a lot of people were deliberately trying to avoid updating to a particularly restrictive Bootloader (which was probably restrictive for a reason, hence the check to make sure it was being used). I used to modify the updates to remove certain checks; when I wanted to use an alternate Recovery for example. Removing the checks would allow the update to install, regardless of the changes - of course, you had to know the risks.
The real answer is that you never know what an update is going to check, and hence you will never know what will make it fail.
I recommend pulling apart an update to see what it is doing, and then there will be less guesswork and speculation...
No offence to adrynalyne, martonikaj, etc - who I know know their shizzle
Well, I was speaking more on behalf of the updater function rebooting but not able to get a 3rd party recovery to actually install the update package; I am guessing because the command it sends to recovery is invalid for the custom recovery. But you can reboot to the custom recovery and manually install it.
I've never investigated past that.
And definitely no offense taken. I am always open for being corrected or learning new things
adrynalyne said:
I am guessing because the command it sends to recovery is invalid for the custom recovery. But you can reboot to the custom recovery and manually install it.
Click to expand...
Click to collapse
I'm glad you mentioned that. A lot of people either assume or are given the impression that a custom recovery actually prevents an OTA update, when it really just prevents the update from happening automatically. It's an important distinction to someone who wants to learn and understand the process. I've seen people flash back to stock recovery so they could get an OTA update, then flash back to their custom recovery... instead of just booting into their custom recovery and choosing the update zip.
phazerorg said:
I'm glad you mentioned that. A lot of people either assume or are given the impression that a custom recovery actually prevents an OTA update, when it really just prevents the update from happening automatically. It's an important distinction to someone who wants to learn and understand the process. I've seen people flash back to stock recovery so they could get an OTA update, then flash back to their custom recovery... instead of just booting into their custom recovery and choosing the update zip.
Click to expand...
Click to collapse
+1
Another important distinction.
danger-rat said:
+1
Another important distinction.
Click to expand...
Click to collapse
Great info in this thread....thanks to all!
I can cofirm receiving OTAs on rooted devices (not the GNex though), and the only issue I ran into was frozen apps. As long as I unfroze them before flashing, and had the stock recovery. I had not issue (LG Ally and Asus TF201)
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!
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.
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:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
XDAnonymous said:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
Click to expand...
Click to collapse
Wow thank you so much I thought it was me having issues. I have a 410vk and as you said nothing was one click. I hope to continue to try and get root on the G Pad. Still an awesome device.
Sent from my LG-H932 using Tapatalk
XDAnonymous said:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
Click to expand...
Click to collapse
Can you link where you got the ROM? Is anyone actively working on it? Really too bad the vk810 never got much love, great little device. Been awhile since I've done anything with it, it's my dad's so I got it rooted on 5.0.2 and just kinda left it alone. What prompted me to come back to this forum is screen mirroring won't work. The tablet sees TV and vice versa, it tries to connect but never completes the connection, just kicks back to satellite TV after a couple of seconds of black screen. Don't suppose you tried casting on that lineage build?
AirForceOnes0010 said:
Can you link where you got the ROM? Is anyone actively working on it? Really too bad the vk810 never got much love, great little device. Been awhile since I've done anything with it, it's my dad's so I got it rooted on 5.0.2 and just kinda left it alone. What prompted me to come back to this forum is screen mirroring won't work. The tablet sees TV and vice versa, it tries to connect but never completes the connection, just kicks back to satellite TV after a couple of seconds of black screen. Don't suppose you tried casting on that lineage build?
Click to expand...
Click to collapse
I got the ROM from the Invisiblek ROMS site under /roms/lineage-14.1/vk810/ (Can't post the link as I'm currently under 10 posts)
It's definitely a start. There is screen glitching, and no LTE service (Wi-Fi only), so it definitely limits the tablet. I have not done much with it as it was a hassle just to get the root within the OS to work correctly. Some apps aren't detecting root when the OS is trying to give it to them.
XDAnonymous said:
I got the ROM from the Invisiblek ROMS site under /roms/lineage-14.1/vk810/ (Can't post the link as I'm currently under 10 posts)
It's definitely a start. There is screen glitching, and no LTE service (Wi-Fi only), so it definitely limits the tablet. I have not done much with it as it was a hassle just to get the root within the OS to work correctly. Some apps aren't detecting root when the OS is trying to give it to them.
Click to expand...
Click to collapse
It'll have to wait until/if LTE is ever functional then, my parents don't have internet other 4g out in the sticks lol. Google took me right to it, thanks. Will keep it bookmarked just in case
I'd like to write about my experience too as it took me some time to finally get the device up and running.
I will describe what I wanted to do, what mistakes I've made and what should've been the correct way.
The device itself is LG G Pad 8.3, Verizon LTE variant aka vk810
Initally I received it in a bricked state, on launching it showed the "Secure booting error" message and that's it.
1) Unbricking
The goal was to install an official LG system image and restore the tablet to a working state.
Basically, I did everything according to the steps outlined here: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-4g-reliable-to-root-install-t3283027
Installed LG drivers
Downloaded the LG Flash Tool 2104
Downloaded a KDZ image
Plugged the device in the download mode into the PC and installed the KDZ using the flash tool
At that point I got a fancy idea to install a non-stock Android on this tablet.
2) Lineage OS
I chose this OS for my tablet, because it seems to be the current standard for non-stock Android installations.
I followed these installation instructions: https://wiki.lineageos.org/devices/v500/install
BEWARE: that page is for v500, so it won't work for vk810.
Lineage doesn't support vk810 officially. A mistake I've made was assuming that I can just roll along with a v500 installation. Actually, you kinda can, but for me it resulted in Wi-Fi not working and my device's MAC address being 02:00:00:00:00:00.
3) Rooting
I was quite confused here too: there are different rooting methods, and some of them can be applied in different ways.
Ultimately I found Stump to be the most comfortable for me: https://forum.xda-developers.com/lg...root-stump-root-lg-g3-sprint-verizon-t2850906
It works fine on this device and uses a very straightforward process: download APK to your PC, connect the tablet to the PC, "adb install <filename>.apk", then launch the app and that's it. It had to go through the bruteforce process to root, which took several minutes.
4) TWRP
I don't remember what exact TWRP I installed initially, but it was a 3.x version, and I encountered an issue where it couldn't mount any of the tablet's partitions. That was quite a pain in the ass.
For a while I resorted to using an older version, 2.7.x, and it worked fine.
Ultimately what I'm the most happy with is this: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-twrp-3-1-1-0-unofficial-t3691551
The lesson learned here is that, again, you need to make sure stuff you install is compatible with your device.
Ultimately, after making mistakes at each step of the process, I figured out everything, and just followed the installation instructions on the Lineage page I linked earlier.
* Flash stock rom
* Root using Stump
* Enable USB debugging on the tablet, install Stump via adb and root the device
* Install vk810 variant of TWRP 3.2.1-0 via adb
* Reboot to recovery (turn off the tablet -> hold Volume Down + Power -> you should get a factory reset menu after the LG logo -> select factory reset, then confirm it and you'll be booted into TWRP. That factory reset is fake after you have TWRP installed)
* Wipe everything
* adb push the lineage / lineage's su / opengapps onto the device
* Install lineage, then su and opengapps and you're good to go
Main lesson learned: it is CRUCIAL to make sure stuff you install is compatible with your particular device. Do not assume that you can use another version, even if it is made for a device of the same family.
Just to provide an update here, this is where the ROM that I used came from: https://updater.invisiblek.org/vk810
The latest version at this time seems to be this: lineage-17.1-20200329-UNOFFICIAL-vk810.zip
XDAnonymous said:
Just to provide an update here, this is where the ROM that I used came from: https://updater.invisiblek.org/vk810
The latest version at this time seems to be this: lineage-17.1-20200329-UNOFFICIAL-vk810.zip
Click to expand...
Click to collapse
Thanks for all the great information, but I have the VK810 that has usb connection problems. It will connect, but it keeps dropping (it cannot be trusted with usb cord). I have wanted to root, twrp, magisk and other things just to play around to see what it can do or how far I can go with it. I am not afraid to trash it. Have you or anyone else had this problem? I have reset it, wiped it out, factory settings, but nothing seems to help that usb port. I was thinking that reflashing the rom might help. Any advice is appreciated.