Database Users

[FOUND] OTA Update Link!

Just got prompted for a new update here is the link
https://android.clients.google.com/packages/incrediblec/OTA_IncredibleC_Verizon_WWE_1.22.605.2_1.22.605.0_release_sign.a33bc3bf.zip

Instructions?

if you want to install this you just downlaod it put it on the root of your sd card, than rename it to update.zip than rebbot to rcovery than select apply update.zip.
Im not saying its ok to install this, as for me i am going to wait for a bot till i can look into more.

Mirror Here

Anybody without a corp account try flashing this yet?

i flashed it today and I do NOT have the CorpEmail account. I really hope this doesn't stop me from getting root.

Gimpeh said:
Anybody without a corp account try flashing this yet?
Click to expand...
Click to collapse
i have, no differences at all. battery life will tell in a day or two

So are we safe letting update go thru? Or should we hold off if we want root?

I wouldn't flash it yet. It contains a recovery image and I don't know if anyone knows for certain what's different about the image.

Would this have the correct test keys?

I flashed. Not noticing anything unexpected. Im getting my incredible replaced anyway. Sounds like I'm listening to people talk underwater.

I doubt you'd notice anything different; I'm just afraid that they've closed a useful hole.
Now if this thing would just stop asking me every 20-30 minutes ... grrrr.

The update fixes the email client for business users.
The meat of the update they don't tell you about, however, is there is a new recovery image in the updater. So yeah, maybe a hole was closed.

I held down volume down button and hit power, booted into the prompt, selected "recovery mode," and all I got was a red triangle and exclamation point.
I downloaded the zip, renamed it update.zip, and put it on /sdcard using Astro.
Am I doing something wrong?

I have the exact same problem.

dont do it

Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?

This whole subject was coverd in another thread.
http://forum.xda-developers.com/showthread.php?t=770091

swindelljd said:
Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?
Click to expand...
Click to collapse
read the other thread, you need to update to 1.22.605.2 first, easy and does not lose date.

Root and OTA
I have rooted with unrevoked 3.1 but still have stock 2.1. Do I need to unroot to install the OTA or will the OTA still be pushed to my phone while I am still rooted?

Kill the kill switch - "ST - yy"

< include generic disclaimer here >
TL;DR
Since update 3.1, Nvidia can force updates (such as the one that bricks your tablet) to be downloaded and installed silently. No guarantees, but:
If you're on stock, delete TegraOTA (/system/app/TegraOTA or /system/priv-app/TegraOTA if you're on 5.0 or newer, or /system/app/TegraOTA.apk if you're still on 4.4) before booting into Android (the attached ZIP file does this for you, but please check with the file manager in recovery before rebooting and let me know if it didn't work), then reboot
Note: you also will need to delete TegraOTA again if you ever install an OTA from Nvidia or a recovery image
If you're not on stock, you're probably safe
EDIT: The urgent OTA is currently not getting sent out to any devices anymore, not even to those who have been getting it before.
EDIT 2: The urgent OTA is now being delivered again, this time named "ST - yy"!
What if my tablet is already deactivated?
Unless you can still boot into fastboot mode (in which case your tablet isn't really deactivated yet), your tablet is probably gone for good. The only way to fix this would be through nvflash, and using it requires the SBK that is unique to each device and that only Nvidia knows, so it's pretty unlikely that we'll ever be able to fix these deactivated tablets.
What/why/how?
In the last OTA (Update 3.1), Nvidia has made some changes to their TegraOTA application. The most important/interesting/suspicious of which is the ability for them to mark OTAs as "urgent". What this means is that these updates will be downloaded without ever notifying the user, and they will be installed without asking the user for permission first. If this is how the kill switch is delivered, all users will see is the tablet randomly rebooting and installing an update, then the tablet would never boot again. As some of you might notice, this would match what has been happening to a few users already, both here and on reddit.
But that's not all. I've been connecting to the OTA servers using various serial numbers (both found and provided to me by a few people) in hopes of actually finding the update that bricks the device. The first serial number I've tried that wasn't mine was the serial number from the screenshot on the recall page. It revealed an interesting "urgent" OTA, named "SHIELD Tablet xx - LTE", which does nothing but flash a blob (which, among other things, contains the bootloader). Many more questions appear now, but the main one is: if this is nothing but a routine bootloader update, why is it marked urgent? And why is it not attached to any Android update? But this by itself is not enough to prove anything, as I could only obtain it with one serial number, so as far as I could have known, it might had just been an internal update or something similar. (update is linked and analysed in the second post below)
Today, however, one of the serial numbers I've been given by some of the people here (thanks for the help guys!) turned out to have the same update waiting for it the next time it connected to the Internet. This rules out the possibility of an internal update, so the next somewhat obvious possibility is that this is the kill switch. Mind you, I still have no direct way of proving this without flashing the ZIP to see what happens (which I'm not planning to do myself), but I will keep checking on the other serial numbers I've gotten to see if this update turns up for them too.
The same person who has given me this serial number has also tested running the old tablet on the latest stock Android version but with TegraOTA removed, and, as expected, the tablet is still working perfectly fine now. Your mileage may vary.
How can I know if the kill switch has been triggered for my tablet?
Go to http://shield.bogdacutu.me/ and enter the full serial number of your old tablet. If the next OTA returned is "SHIELD Tablet xx" "ST - yy", the kill switch has been triggered for your tablet.
Warning: the serial number from the box of the tablet and the one etched on the side of the tablet are not complete, as they only contain the first 13 characters of the full (20 characters) serial number. You can get the full serial number from Android (Settings -> About -> Status), from the bootloader (it will be on the screen when you boot into bootloader mode), or from your computer if the tablet is or (in some cases) if it was previously connected, using various tools such as USBDeview. Example: 0413714803249000a4cf (you can try this on the page and it will return that the kill switch is activated).
Why would I want to also do the fix on my new tablet too?
The update is signed by Nvidia, and communication with the OTA server does not use HTTPS, so, for example, a malicious WiFi network could MITM your connection and cause this update (as well as any other signed update) to be flashed to your new tablet without your permission, thus permanently disabling it too. If you have the stock recovery, only updates signed by Nvidia can run. The story might be slightly different if your recovery doesn't enforce signature verification (such as TWRP and CWM by default).
Can I still get updates from Nvidia after doing this?
Not directly, but people will post OTA download links here on xda when new updates get released. I'd personally recommend that you wait before flashing though until someone here checks the new update to confirm that there's no new way for Nvidia to kill your tablet.
Many hours of work have gone into investigating this. Even if it doesn't help your specific scenario, consider hitting that Thanks button, so that I can at least know it wasn't for nothing.
I'd also like to thank the people who have given me their serial numbers to use for testing again, this wouldn't have been possible without their help: @Beauenheim, @Jackill, and @runandhide05 (who has even volunteered to test removing TegraOTA with the latest update on his old tablet :highfive

Fragments of code from TegraOTA.apk
< screenshots temporarily removed >
Also, from what I've seen so far, the update isn't delivered instantly after activating the new tablet. I don't know exactly what the rule is, but out of the 4 serial numbers that I have, only 2 have this update waiting for them.
EDIT: One more serial number from the ones I have has gotten the xx update. Only one left...
EDIT 2: All the serial numbers I have have the urgent OTA waiting for them now.

"SHIELD Tablet xx" - Update Analysis
OTA URL: http://ota.nvidia.com/ota/data/post...wf-full_ota-32256_554.0168.20150624152335.zip
yy OTA URL: http://ota.nvidia.com/ota/data/posted-roms/uploaded/st---yy--092704233775---7294.20150819152732.zip (if you don't know what you're doing, DO NOT DOWNLOAD THIS, it's very likely that this will permanently brick your device upon flashing it!!!) - also attached to this post in case this link becomes invalid
updater-script is the first file we check:
Code:
getprop("ro.product.device") == "shieldtablet" || abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");
nv_copy_blob_file("blob", "/staging");
reboot_now("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "");
Suspiciously enough, this only flashes a blob to the staging partition. But what exactly does this blob do, you might ask? Well, the blob actually contains data for 9 partitions, which are automatically replaced during the next boot (before the bootloader does anything else at all, so once you've rebooted, there's no going back) with the contents present in this blob. The 9 partitions are as follows (also detailing comparison with files from update 3.1):
BCT (Boot Configuration Table) - stores some information that is needed for the device to find the bootloader stored on the other partitions, initialize the RAM and some other stuff
Status after update: probably corrupted - the previous OTAs have binary BCTs, but this update replaces it with a text file (which, while it does contain somewhat relevant information, is likely not a valid format). If this is corrupted, it's enough for the device not to be able to boot anymore.
BMP (boot logo) - intact
DTB - intact
EBT (part of the bootloader) - has a zeroed out region
NVC (part of the bootloader) - intact
RBL (part of the bootloader) - has a zeroed out region
RP4 (landscape boot logo) - intact
TOS (Trusted OS - probably part of the bootloader too) - has a zeroed out region
WB0 (related to the boot process, source file is named "nvbootwb0.bin") - has a zeroed out region
The update also contains a few other files, but those are not used at all (probably leftovers from the 5.1 AOSP update template that they are using).
DO NOT DOWNLOAD THE ATTACHMENT IF YOU DON'T KNOW WHAT YOU'RE DOING. THIS IS THE XX OTA, NOT THE ZIP THAT REMOVES TEGRAOTA!

Just as I suspected!!

Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.

tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
CWM and TWRP are both compatible with OTAs, so yes, it can. If you completely erase the recovery (fastboot erase recovery), the update can't get flashed, but the tablet will still reboot (which is at least annoying).
You can flash the provided ZIP through CWM or TWRP (but please check through the file manager if /system/app/TegraOTA still exists after installing it, the ZIP hasn't gone through a lot of testing so it might not work properly in all cases)

tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?

bluegizmo83 said:
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
Click to expand...
Click to collapse
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks

Bogdacutu said:
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Click to expand...
Click to collapse
Oh ok! Great explaination. Thanks for all your hard work on this! I'm flashing the zip now, i'll report back if it removes the file
Edit: Ok I flashed the zip, and TegraOTA is gone. Now I will finally turn on my new tablet and set it up!

So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?

Great post. Hopefully that's as far as Nvidia is going to go. I flashed a custom rom on my old tablet. I'm keeping my new one stock but deleting the system app per your post. Just in case Nvidia is spiteful when I don't return the old tablet. I don't want to leave them any option of nuking the new one.

fkofilee said:
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Click to expand...
Click to collapse
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings

Bogdacutu said:
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Click to expand...
Click to collapse
I know fella I appreciate it. Could you check my second point? 2 x Nvidia Shields would be awesome! One for Work, One For Home

fkofilee said:
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Click to expand...
Click to collapse
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.

Bogdacutu said:
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Click to expand...
Click to collapse
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?

fkofilee said:
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
Click to expand...
Click to collapse
As mentioned in the OP, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.

Bogdacutu said:
As mentioned in the first post, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Click to expand...
Click to collapse
Sorry fella missed that part, I will be donating some funds when i get paid later this month Mucho Gracias!

Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?

bluegizmo83 said:
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
Click to expand...
Click to collapse
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore

Bogdacutu said:
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Click to expand...
Click to collapse
AWESOME man, thank you!!

Asus Zenpad 10 (Z300M) Boot Loop after update

Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you

Same problem. When WiFi is ON.
When I put WiFi OFF - the tablet works fine.
Last firmware doesn't help, reset too. I think there is no solution at this moment, except maybe to flash an old firmware with Android 6.
I'll replace it in store. No idea about Asus control quality of their firmware... but this problem is pretty common.

???
Belnadifia said:
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Click to expand...
Click to collapse
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach

coolbeans2016 said:
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
Click to expand...
Click to collapse
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.

I'll give you that
diplomatic said:
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
Click to expand...
Click to collapse
The link on the Z380M is what threw a flag for me because that Asus tab isnt rootable. If this is some combo of slipups between tools & devices that lines up just right to get TWRP on its not described very well in the OP. Using the 5.132 (?) you can not readback with that option.ini file.... so what am I missing? The bootloader unlock app isn't written for this tablet is it? written for the zenphone 2 (3)?

Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.

Just want to mention for anyone else struggling with this issue, what fixed it for me:
I found the reboot would only happen when wifi was turned on, and even more weird, it would only happen when connected to specific wifi networks. After doing a factory reset I was able to set it up again by tethering to the wifi on my phone. I then found that I actually was able to connect to the problematic wifi network but only by setting a static IP! This has completely resolved the issue for me.

Thaniks
diplomatic said:
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Click to expand...
Click to collapse
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls

coolbeans2016 said:
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
Click to expand...
Click to collapse
Ohhh... ok. No problem man. Just please get your facts straight before posting next time. Good luck. BTW, I'm not sure if you saw this post on the TWRP thread from 2 weeks ago. You didn't reply.
diplomatic said:
What is the error that you got when trying to flash it? Can you post a screenshot of the Download tab along with the Help/About dialog box?
Click to expand...
Click to collapse

[OTA Update] [Oreo] Galaxy S7 Active Update to Android Oreo Guide

This Guide is one i wrote in a reply on another forum, I thought more people would see it if i posted it here as well. As usual, if you brick your phone while following this guide, it is your problem, and i take no repsonsibility for any bricked S7 Actives due to this guide. Its not likely, but in the event that it occurs, understand that it's your problem.
There is no s7 active oreo rom in ODIN flashable format available yet, but you can update by flashing nougat, and flashing two ota flashable zip files in stock recovery. If you go to this website, and click the blue download button, you can extract the downloaded file with 7zip, or winrar, and flash the md5 files in ODIN, and you will then be on stock android nougat. You can then copy this zip file to your phone's external micro sd card, without extracting it, and use stock recovery mode (turn off, then volume up + home + power) to "apply update from sd card", or if you don't have a micro sd card, click "apply update from adb" and look up "how to use adb sideload" on google. Once it's done updating, do the same thing with this zip file, using stock recovery and "apply update from sd card" or using "apply update from ADB", and you will be on android 8.0 oreo. you can always use the first file you downloaded to go back to stock nougat if you don't like oreo, but it's working great for me! Enjoy android Oreo on your S7 Active, hopefully we will see a root soon, as the nougat root just bricks my phone while it is on oreo. I do not recommend using a newer oreo OTA zip instead of the one i posted, as some of the other ones flash a newer bootloader, thus preventing a downgrade back to nougat in the event something catastrophic happens.
Reply and let me know if this worked for you, or if it didn't, tell me where the process failed.
remember to hit thanks, and if you want to support me, consider donating to me by clicking here!

Yay! Had trouble with the download stopping and varying speed download (mostly slow) but now that I've got it all went as normal.
Did seem to take a little longer than normal on the factory recovery updates but no problems to report there.
Up and running now but I've yet to play with it more than opening a few apps and testing features.
Now we need an unlocked bootloader!!! I miss having custom ROMs, debloat, and a real firewall...
Maybe someday. Maybe.

Hello
I recently installed the version G891AUCU2BQB2
Do I need to install all the files that appear in the link you gave?
Sorry about my English and sorry for the questions of a novice
Thank you

yossiv69 said:
Hello
I recently installed the version G891AUCU2BQB2
Do I need to install all the files that appear in the link you gave?
Sorry about my English and sorry for the questions of a novice
Thank you
Click to expand...
Click to collapse
I don't know what Jacob says about your doubt, but probably you can downgrade the build to the BQD4 and then install the updates until the BRB5. I did something similar, I downgrade the build BQF2 to BQD4 and then I installed the updates (the last was the build BRB5) to be able to install android oreo (build CRC7).
---------- Post added at 04:06 PM ---------- Previous post was at 03:59 PM ----------
jacoblong09 said:
This Guide is one i wrote in a reply on another forum, I thought more people would see it if i posted it here as well. As usual, if you brick your phone while following this guide, it is your problem, and i take no repsonsibility for any bricked S7 Actives due to this guide. Its not likely, but in the event that it occurs, understand that it's your problem.
There is no s7 active oreo rom in ODIN flashable format available yet, but you can update by flashing nougat, and flashing two ota flashable zip files in stock recovery. If you go to this website, and click the blue download button, you can extract the downloaded file with 7zip, or winrar, and flash the md5 files in ODIN, and you will then be on stock android nougat. You can then copy this zip file to your phone's external micro sd card, without extracting it, and use stock recovery mode (turn off, then volume up + home + power) to "apply update from sd card", or if you don't have a micro sd card, click "apply update from adb" and look up "how to use adb sideload" on google. Once it's done updating, do the same thing with this zip file, using stock recovery and "apply update from sd card" or using "apply update from ADB", and you will be on android 8.0 oreo. you can always use the first file you downloaded to go back to stock nougat if you don't like oreo, but it's working great for me! Enjoy android Oreo on your S7 Active, hopefully we will see a root soon, as the nougat root just bricks my phone while it is on oreo. I do not recommend using a newer oreo OTA zip instead of the one i posted, as some of the other ones flash a newer bootloader, thus preventing a downgrade back to nougat in the event something catastrophic happens.
Reply and let me know if this worked for you, or if it didn't, tell me where the process failed.
remember to hit thanks, and if you want to support me, consider donating to me by clicking here!
Click to expand...
Click to collapse
Hi Jacob, I have a doubt, do you have any problem with the HRM sensor? I can't use it. I could use it with nougat but with oreo it doesn't work (even if I test it in the *#0*# the sensor doesn't work). Thank you!!

Bro, I’m sorry, I can’t help, I accidentally bricked my s7 active last month, and it was hard bricked, I accidentally flashed the wrong boot loader, so I had to return it and I know how people feel about this, but there was a great deal on an iPhone 6s :/
???????????????

jacoblong09 said:
Bro, I’m sorry, I can’t help, I accidentally bricked my s7 active last month, and it was hard bricked, I accidentally flashed the wrong boot loader, so I had to return it and I know how people feel about this, but there was a great deal on an iPhone 6s :/
Click to expand...
Click to collapse
Haha. I'm thinking about getting a 6S as well. How's the standby battery life compared to the S7 Active?

Yeah, I can make it last a day, I got mine used, so my battery has 85% of its original health, I would think one with a newer battery in it would last longer, especially since this one lasts the whole day.... if you find one cheap, I recommend, but only the 6s/6s plus, not the 6/6 plus

Thanks, works great
Thanks so much, I was able to update my phone that has been off of any network for over a year. I update my S7 Active from BQH1 all the way through to CRD4, took a while having to manually update each OTA file. 6 updates later and I am running Android 8, so far no issues, no sim atm so can not tell if all functions are good, but seems to be so. Been 24 hours since and have not had a single issue. Even got it network unlocked and am running a T-Mobile sim, works like a charm.

jacoblong09 said:
Bro, I’m sorry, I can’t help, I accidentally bricked my s7 active last month, and it was hard bricked, I accidentally flashed the wrong boot loader, so I had to return it and I know how people feel about this, but there was a great deal on an iPhone 6s :/
Click to expand...
Click to collapse
Oh bro, don't worry, it's okay! Have a good life with your iPhone 6 :'v. Thank you bro!

When I try to install the BRA7 to BRB5 update, my phone gives this error.
Could someone that knows more than me interpret this for me and tell me what I need to do?
Installing update...
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: Permission denied
source: samsung/poseidonlteuc/poseidonlteatt:7.0/NRD90M/G891AUCS2BRA7:user/releasekeys
source: samsung/poseidonlteuc/poseidonlteatt:7.0/NRD90M/G891AUCU2BRB5:user/releasekeys
Build_number : QB16651846
Verifying current system...
e3005: "/system/SW_Configuration.xml" as unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
Successfully verify for dmverify hash tree
Installation aborted.

Trying to flash SM-G891A_G891AUCS2BRA7_USA_ATT_v7.0, but I keep getting a "md5 error! Binary is invalid" when trying to load the AP file in Odin3 v3.13. Is this legit?

what build are you on currently?

Traxxasman10 said:
When I try to install the BRA7 to BRB5 update, my phone gives this error.
Could someone that knows more than me interpret this for me and tell me what I need to do?
Installing update...
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: Permission denied
source: samsung/poseidonlteuc/poseidonlteatt:7.0/NRD90M/G891AUCS2BRA7:user/releasekeys
source: samsung/poseidonlteuc/poseidonlteatt:7.0/NRD90M/G891AUCU2BRB5:user/releasekeys
Build_number : QB16651846
Verifying current system...
e3005: "/system/SW_Configuration.xml" as unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
Successfully verify for dmverify hash tree
Installation aborted.
Click to expand...
Click to collapse
I am currently having this issue trying to update from S3BRD1 to U3CRE7. I was running CRD4 but downgraded so I could go up to CRE build, but no luck. Were you able to figure out what is causing this issue?

saintbump said:
I am currently having this issue trying to update from S3BRD1 to U3CRE7. I was running CRD4 but downgraded so I could go up to CRE build, but no luck. Were you able to figure out what is causing this issue?
Click to expand...
Click to collapse
Nope, still looking for an answer

Traxxasman10 said:
Nope, still looking for an answer
Click to expand...
Click to collapse
I gave up on trying to apply the CRE7 update and went ahead and settled with the CRE5 and it loaded just fine. Might have been a corrupt file, downloaded it 3 times. :silly:

Traxxasman10 said:
Nope, still looking for an answer
Click to expand...
Click to collapse
Just a thought, they recently uploaded a stock U3BRD1, which brings the bootloader to the newest (no root possible), then just OTA update from there.

Successfully flashed CRC7 on my S7 Active (I'm in Canada and can't get OTA updates).
However my Samsung Pay can no longer register my Canadian credit cards (it was working fine on Nougat build BRB5). Anyone in a similar situation?

Peace
Where can I find the file SS-G891AUCU2BQF2-to-S2BQG1-UP.zip
Thanks Yossi

yossiv69 said:
Peace
Where can I find the file SS-G891AUCU2BQF2-to-S2BQG1-UP.zip
Thanks Yossi
Click to expand...
Click to collapse
On my cloud folder there are all OTA updates. Here is SS-G891AUCU2BQF2-to-S2BQG1-UP.zip.
Russian post about all OTA updates on 4pda.ru for quick naviagation.

khaliullov said:
On my cloud folder there are all OTA updates. Here is SS-G891AUCU2BQF2-to-S2BQG1-UP.zip.
Russian post about all OTA updates on 4pda.ru for quick naviagation.
Click to expand...
Click to collapse
Thank you:good::good::good:

Issues with rooted S5e running Lineage 17.1

I rooted my S5e (SM-T720) using the method outlined here. Everything seemed to go well, but three annoying issues became apparent as soon as I started using it. I could use some help troubleshooting them.
Chrome hangs frequently, becoming entirely unresponsive. Removing it from the multitasking pane and then relaunching solves the problem, but It happens quite often, and since reading on the Internet is one of my primary uses for this tablet, this is quite frustrating. I often have to relaunch about every 10 minutes or so. I rarely have many other apps open, and I rarely have more than 5 or 6 tabs open.
Google Assistant doesn't recognize my voice. When I go into settings and turn on Voice Match, the button which is supposed to turn on "Hey Google" responds, and walks me through voice training. It retrieves my voice match settings from my account, and after it completes that process, the next screen says that "Hey Google is ready," and after I click "Continue," I am returned to the main Voice Match settings, the "Hey Google" button is turned off. I have tried the "Teach your assistant your voice again," to no avail.
Most disturbingly, the tablet's screen unfailingly powers itself on immediately after powering off. It does so whether I have powered off using the power button, using the magnetic auto on/off function, or by allowing the screen to timeout. Needless to say, this is not conducive to effective battery management, and I really need to find a fix.
I don't recall the tablet doing any of these things prior to rooting/ installing Lineage, although I confess that my memory isn't improving with age. Luckily, I'm getting better-looking, insofar as I can remember. All assistance will be greatly appreciated.
P.S. I just edited this post to fix a broken link, and to clarify that it is the tablet's screen which is powering back on, not the tablet itself.

Your root link doesn't work? How did you root? Are you running a current version of Lineage and current firmware?

lineage_gts4lvwifi-userdebug 10 QQ3A.200805.001 1c4e6536e3
OhioYJ said:
Your root link doesn't work? How did you root? Are you running a current version of Lineage and current firmware?
Click to expand...
Click to collapse
I fixed the link, and it now points to https://forum.xda-developers.com/t/galaxy-tab-s5e-sm-t720-root-instructions-release-1-0.3947806/.
I just edited my post to clarify that it is the tablet's screen which is powering back on, not the tablet itself.
I'm not quite sure how to answer your questions about the version of Lineage and the firmware. The build number identified in Settings/About tablet is lineage_gts4lvwifi-userdebug 10 QQ3A.200805.001 1c4e6536e3. The folder which was created when I unzipped the download of Lineage is named T720XXU1CTK1_T720OXM1CTK1_XAR. If this isn't the information you're looking for, can you please tell me where to find it?
Thank you for weighing in. I was beginning to think that no assistance would be forthcoming.

smilejack1 said:
lineage_gts4lvwifi-userdebug 10 QQ3A.200805.001 1c4e6536e3
I fixed the link, and it now points to https://forum.xda-developers.com/t/galaxy-tab-s5e-sm-t720-root-instructions-release-1-0.3947806/.
I just edited my post to clarify that it is the tablet's screen which is powering back on, not the tablet itself.
I'm not quite sure how to answer your questions about the version of Lineage and the firmware. The build number identified in Settings/About tablet is lineage_gts4lvwifi-userdebug 10 QQ3A.200805.001 1c4e6536e3. The folder which was created when I unzipped the download of Lineage is named T720XXU1CTK1_T720OXM1CTK1_XAR. If this isn't the information you're looking for, can you please tell me where to find it?
Thank you for weighing in. I was beginning to think that no assistance would be forthcoming.
Click to expand...
Click to collapse
You don't need to do all that to root. At least not in your case. For the moment we'll go on the assumption that if you're running a recent build of LOS, you're on the new firmware, as it should check. Since you went with a "non-traditional" root method, I think I would try a reflash of LOS, basically the update method to replace anything that could have gotten "borked". This shouldn't harm any data or apps, as this is normal. Backups are never a bad idea though.
So I would try (from TWRP): (<-- Not sure which TWRP you are using, but make sure you are using at least 3.4.0-5, 3.5.0_9-0 is the latest)
- Flash Lineage (even if it's the same build as you have currently)
- Flash Gapps (if you use them)
- Flash Magisk (Magisk GitHub Here.)
- Reboot. Is it better?
I just tested 21.3 (magisk) on mine, no issues. Although I am running LOS 18.1 now.

OhioYJ said:
You don't need to do all that to root. At least not in your case. For the moment we'll go on the assumption that if you're running a recent build of LOS, you're on the new firmware, as it should check. Since you went with a "non-traditional" root method, I think I would try a reflash of LOS, basically the update method to replace anything that could have gotten "borked". This shouldn't harm any data or apps, as this is normal. Backups are never a bad idea though.
So I would try (from TWRP): (<-- Not sure which TWRP you are using, but make sure you are using at least 3.4.0-5, 3.5.0_9-0 is the latest)
- Flash Lineage (even if it's the same build as you have currently)
- Flash Gapps (if you use them)
- Flash Magisk (Magisk GitHub Here.)
- Reboot. Is it better?
I just tested 21.3 (magisk) on mine, no issues. Although I am running LOS 18.1 now.
Click to expand...
Click to collapse
Thank you for your suggestions. In preparing to implement them, new information came to light which might require that they be altered.
I attempted to perform a Titanium Backup, but when I opened the app, it informed me that I didn't have root. This was puzzling, as I had verified root before, both according to the technique suggested in the rooting instructions I linked to above, and with Root Checker. When I do so now, Root Checker indicates that I don't have root, and the procedure in my rooting instructions results in my tablet booting to TWRP.
Also, Magisk seems to have entirely disappeared from the tablet. I'm thoroughly confused at this point. Should I continue with your suggestions, or pursue other options?

smilejack1 said:
Also, Magisk seems to have entirely disappeared from the tablet. I'm thoroughly confused at this point. Should I continue with your suggestions, or pursue other options?
Click to expand...
Click to collapse
I've had that happen before, typically after installing a new ROM. Usually just reflashing Magisk in TWRP fixes it. Then you can likely run Titanium Backup as planned.

Thanks for your further assistance. Unfortunately, the adventure continues; I can't flash Magisk!
When I attempt to do so from Main Storage, the Magisk zip file doesn't appear on the top level folder visible in TWRP, nor in any subfolder therein. When I attempt to do so from the SD card, I get an error message reading "Invalid zip file format! Error installing zip file '/external-sd/Magisk-21.4.zip'.
I have tried wiping the cache and Dalvik prior to installing Magisk, with the same outcome. I'm really at a loss.

Never
smilejack1 said:
Thanks for your further assistance. Unfortunately, the adventure continues; I can't flash Magisk!
When I attempt to do so from Main Storage, the Magisk zip file doesn't appear on the top level folder visible in TWRP, nor in any subfolder therein. When I attempt to do so from the SD card, I get an error message reading "Invalid zip file format! Error installing zip file '/external-sd/Magisk-21.4.zip'.
I have tried wiping the cache and Dalvik prior to installing Magisk, with the same outcome. I'm really at a loss.
Click to expand...
Click to collapse
I figured it out. I'm embarrassed to say what I did wrong, but thanks again for your help.

smilejack1 said:
I figured it out. I'm embarrassed to say what I did wrong, but thanks again for your help.
Click to expand...
Click to collapse
We've all been there...