Just got an update (225mb) on my Tab 10.1. Still Nougat (7.0), with December security patch and new kernel. Not sure if anything else is new. Adoptable storage appears to have still survived on my stock, unrooted tablet.
How do you have Adoptable Storage in this tablet with nougat? (I supose that A6 10.1 is T580 [wifi] and T585 [with lte])
I used ADB, following a guide I found to enable it for (I think) the S8. I did it when I first got the tablet, so it was running Marshmallow, but it has survived the update to Nougat.
Thank you for the answer. Is interesting because one possiblitiy for other people (like me) is go to flash a marashmallow image, enable with ADB the adoptable storage, and then update again (actually this tablet is sold with Nougat, so is not possible to enable Adoptable Storage without flashing a Marshmallow image)
I got the s8 weather widgets from this update
And i have managed to install latest samsung experience launcher without root whereas I couldn't before and it has full Flipboard briefing support
Related
I've got a Nexus 6 with Verizon Wireless. It is purely stock: I have never rooted or modified the phone in any way other than accepting the standard OTA updates pushed out by Google/Verizon.
I've been patiently waiting for the OTA update to upgrade my phone to Nougat, but I haven't seen any updates in over a month. My phone is currently running MOB31H (6.0.1) which, according to the Google Factory Images page is the security update from October 2016. However, according to the same page there have been two security updates in November (MMB31C and MOB31K), and there have been two versions of Nougat released since then (NBD90Z and NBD91P). My phone has not seen any of these updates, despite repeatedly checking for updates via the settings menu.
I've got a few questions along these lines:
1) I've seen rumors about trouble with Nougat, which suggests maybe Verizon/Google have been delaying a widespread roll-out. However, I have not seen anything posted recently about this (latest reports are from early October), and what I did see seemed focused on other phones (not the Nexus 6). Are there any known issues with Nougat running on the Nexus 6 that would make me want to delay upgrading manually?
2) Is it unusual for my Nexus 6 to still be running 6.0.1 with the October security update? Shouldn't it have at least received the November security updates? Have others experienced this issue?
3) If I download the OTA directly from Google and sideload the update, will this disable the automatic OTA updates in the future? I'd like to at least apply the November 6.0.1 security updates to keep my phone secure.
4) If I want to update my phone to Nougat manually, can I simply download the OTA for Nougat and follow the instructions Google includes for sideloading the OTA update? Or do I have to download the entire 7.0 factory image and install that image? I have experience installing the factory images (I have a Nexus 10 that I've had rooted for a while, so I've gotten good at installing the factory images whenever a new image is released) but it is still a bit of a pain and I would prefer the OTA updates for my phone if I can.
4a) If I can update via the OTA, can I pick the latest OTA (NBD91P), or do I have to go incrementally (install NBD90Z first then update to NBD91P)?
5) Only tangentially related question: I've noticed that Google has included the month and year on more recent factory images, but is there any way to determine the exact date that an image was released? For example: I see there are two November OTA updates for Nexus 6, how can I tell if MOB31K was released this morning vs. November 2? If it was released this morning that may explain why I haven't seen the update yet, but if it was released November 2 I would be surprised I haven't seen the update yet.
Thanks in advance for any help.
1. Verizon has no control over updates on this device. That said, no major issues with the stock ROM.
2. Not unusual at all. When I received my N6 earlier this year it stopped updating after the latest Android 5.0.1 update. I had to flash an Android 6.0.1 image manually.
3. No.
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
5. No way to tell outside of paying attention here, since someone will inevitably announce the release of the latest version. Of course, once you've installed the latest image, OTA updates should continue as usual if you don't modify the firmware like most of us do.
Thanks for the helpful reply! One quick follow-up:
Strephon Alkhalikoi said:
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
Click to expand...
Click to collapse
I will likely follow your advice regarding updating from the full factory image instead of the OTA. My main limitation is my two-factor authentication. Because I haven't rooted, it is a pain to transfer some of that from one device to another (in some cases it requires disabling two-factor authentication and re-enabling it on each site, and I have at least 12 website that are using two-factor authentication on my device). I need to make sure that I don't accidentally lose the authentication tokens.
If I get lazy, or just want to "risk" using the OTA: Can I use either OTA image (the one from October or November) to upgrade from 6.0.1 to 7.0? Or does the one from October apply a full update and the November is just an incremental update intended to by applied to an existing 7.0 build?
Both are full updates. I'm not sure as to how well your current data will transition over to Android 7.
I would look into finding a means of backing up your authenticator.
Just got the Nougat OTA update from ATT on the S6 Active.
First time I got my update on the Active before my wife got hers for the G920A?
S6 Active AT&T How to Force Updates to Android 7 Nougat & Rooted ROM?
After seeing "No Update Current Version" while on a 2016 Security patch with corresponding Build # and 2016's Android v. 6.0.1, I found that by Turning On AT&T Mobile Network Data, and Turning Off Wifi, then Clearing the Google Framework App Data in Settings > Application Manager. Restart, Settings > About Device > Software Update > Check for Updates, I finally get "Software Update", and have repeated the process 4x in 4 days starting with a Security Patch of March 2016 and currently at January 2017. Apparently a 24-hour "Settle Time" period (literally 24-hours, it will show "No Update" at 23h 55m) between updates is incorporated into the process. I just did this with my son's S6 (Standard) and was able to update 5 consecutive Security Updates and then a 1.9GB Android Update followed which brought his S6 to a Security Patch of September 2017, and Android v. 7 Nougat. I am currently, after the 4 Security Patch Updates (over 4 days), at January 2017, and Android v. 6.0.1. I believe there are 2 more Security updates, then the very lengthy (1 hour) 1.9GB Nougat Update.
How can I Unlock this Bootloader?
How can I Root my S6 Active?
Is there a way to flash a pre-Rooted lean ROM (there are 270 Apps stock on this device. AT&T, Samsung, and Google seem to be having a Who can install more useless **** on a device war?) through ODIN, ADB Sideload, or Recovery Download for this specific device? All I find here at XDA are standard S6 catagories, No S6 Active image under "Choose Device", and a myriad "No Root Possible" in a S6 Active sub-catagories.
RCALL said:
After seeing "No Update Current Version" while on a 2016 Security patch with corresponding Build # and 2016's Android v. 6.0.1, I found that by Turning On AT&T Mobile Network Data, and Turning Off Wifi, then Clearing the Google Framework App Data in Settings > Application Manager. Restart, Settings > About Device > Software Update > Check for Updates, I finally get "Software Update", and have repeated the process 4x in 4 days starting with a Security Patch of March 2016 and currently at January 2017. Apparently a 24-hour "Settle Time" period (literally 24-hours, it will show "No Update" at 23h 55m) between updates is incorporated into the process. I just did this with my son's S6 (Standard) and was able to update 5 consecutive Security Updates and then a 1.9GB Android Update followed which brought his S6 to a Security Patch of September 2017, and Android v. 7 Nougat. I am currently, after the 4 Security Patch Updates (over 4 days), at January 2017, and Android v. 6.0.1. I believe there are 2 more Security updates, then the very lengthy (1 hour) 1.9GB Nougat Update.
How can I Unlock this Bootloader?
How can I Root my S6 Active?
Is there a way to flash a pre-Rooted lean ROM (there are 270 Apps stock on this device. AT&T, Samsung, and Google seem to be having a Who can install more useless **** on a device war?) through ODIN, ADB Sideload, or Recovery Download for this specific device? All I find here at XDA are standard S6 catagories, No S6 Active image under "Choose Device", and a myriad "No Root Possible" in a S6 Active sub-catagories.
Click to expand...
Click to collapse
Haven't been following closely on S6 active, but typically unlocking bootloader on ATT branded devices is not going to happen.
As far as the 24 hour delay between checking for updates, I believe you can manually set the date forward on the device to work around the delay.
S6 Active AT&T Nougat Android v.7
txwho said:
Just got the Nougat OTA update from ATT on the S6 Active.
Click to expand...
Click to collapse
I ended up Live Chatting w/ a most excellent Samsung Customer Care Specialist, she accessed my AT&T account, then forwarded the OTA update to Android 7.0 Nougat directly to my S6 Active.
Hi all
Been out of the ROM flashing game for a long time but a friend of mine has the P8 lite 2017 and is fed up with it, he doesn't have enough storage for the Huawei updates and phone is lagging... I already cleaned up his phone a couple of times in the past, even uninstalling a couple of apps he actually wanted to keep. Doing this I was able to install a few updates but now it's practically game over.
He doesn't want to buy a new phone so he told me I could fiddle with it and try to give him a working phone without storage issues. He doesn't mind if it's not updated to the latest security patches, he doesn't do mobile banking etc on it and he says he "has nothing to hide"
So I remembered the days where I rooted and installed ROM's and got fluid working devices out of it
Yesterday evening I managed to unlock the bootloader and install TWRP and now I am to the point on deciding what ROM to flash but here I'm a bit too long out of the game and I would appreciate some advice from people who have been around the P8 lite 2017 a bit longer then I have
Criteria:
doesn't have to be the latest stuff out there but everything should work (incl fingerprint scanner) + sd card can be used as adoptable storage
preferably something "light" like stock android but functionality and no bugs win so if that means huawei rom so be it
Extra info
model PRA-LX1
Build PRA-LX1C432B212
EMUI 5.0.3
Android 7
Any advise?
Or should I just root it, disable updates and try to get the adoptable storage working?
Thx!
B
Okay... Adoptable Storage on Huawei... Seems somewhat pointless actually since you can set the SD Card as the default storage in the storage settings/files app... Helps if the SD is larger than the internal storage.... That's Option 1...
Now, for option 2... Update to EMUI8.... I suggest wiping the phone, and just doing system updates until you get to EMUI8... Give EMUI8 a spin...
If not your(friend's) cuppa tea, there's option 3! Check some of the custom ROMs... SiriuZ ROM if you're looking for a Stock(-ish) EMUI8 ROM plus some minor customisation, and MorfuZ ROM for a EMUI8 ROM with more customisation and stuff...
Lastly, there's GSIs... (Go read up on Treble, GSIs, DSSIs and the AIO Guide here in the P8 Lite 2017 Development Forums)
As a sidenote, make sure to be on STOCK EMUI8... (None of the ROMs mentioned option 3 apply)
You'll have to be on EMUI8 first to run GSIs... I would recommend you check the Treble-Enabled Device Forums for GSIs. If you'd like something more device specific, in the P8 Lite 2017 development forums you'll also find some DSSIs which is somewhat better and a little bit less of a hassle if you want a all in one solution... PixysOS is pretty solid for the P8 Lite 2017... Also, although not in the P8 Lite 2017 forum, Descendant is another great option, not device specific to the P8L, but might just as well be... If running Descendant, be sure to flash the Labyrinth Kernel.
Last week I bought the Galaxy A90 5G (SM-A9080, China version), and immediately searched for ways of Magisk installation.
Indeed there are multiple articles from Google showning the methods. I tried most of them and regretfully all failed.
Even I followed the instruction from this forum, however, I still failed.
This is because of my current model? Because the current version of Magisk is not updated enough? Because of the mechanism of Samsung's Android 9 OS?
I also got the Galaxy Note8 running Android 9, and the way of Magisk installation on Android 8 and previous ones does not work on Android 9.
I do need Root/Magisk due to my requirement, but there is likely a huge barrier preventing me from the Root.
Thus, there is no possible solution?
jasonc417 said:
Last week I bought the Galaxy A90 5G (SM-A9080, China version), and immediately searched for ways of Magisk installation.
Indeed there are multiple articles from Google showning the methods. I tried most of them and regretfully all failed.
Even I followed the instruction from this forum, however, I still failed.
This is because of my current model? Because the current version of Magisk is not updated enough? Because of the mechanism of Samsung's Android 9 OS?
I also got the Galaxy Note8 running Android 9, and the way of Magisk installation on Android 8 and previous ones does not work on Android 9.
I do need Root/Magisk due to my requirement, but there is likely a huge barrier preventing me from the Root.
Thus, there is no possible solution?
Click to expand...
Click to collapse
I own a A908B (German Version) and I'm on Android 10 running Magisk on Stock OS. This is the tutorial i followed and it works. Since there is no Custom Recovery yet the only thing we can do right now is patch the AP-Image of every single update we get... And be prepared to backup everything you have because it's going tor require a full data wipe
Thanks for your advice.
Last night I upgraded my SM-A9080 to Android 10 and managed to get the phone rooted via Odin3.
yomama163 said:
I own a A908B (German Version) and I'm on Android 10 running Magisk on Stock OS. This is the tutorial i followed and it works. Since there is no Custom Recovery yet the only thing we can do right now is patch the AP-Image of every single update we get... And be prepared to backup everything you have because it's going tor require a full data wipe
Click to expand...
Click to collapse
Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”
There are many sites offing Step-by-Step guides.
I used
https://wiki.lineageos.org/devices/gts28vewifi/install and/or
https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-16-0-t3903286
(SEE BELOW for what’s missing from the instructions)
I have a 2016 Samsung Galaxy Tab S2 8.0 that seemed to be on its last legs. After all, it is the 4th quarter of 2020 as I write this. The current version of Android is 10. This poor old, much loved, tablet runs either Android 5, 6 or 7. Ancient, right!
I upgraded to Lineage 16.0 (17.0 was still “unofficial” in late summer 2020) – Android 9. All I can say is WOW!! A whole new tablet, or at least that is the way it behaves.
The process took me two days. It should have been about 2 hours. I’m writing this to save others those 46 hours of frustration.
I absolutely hate it when those that create the “How to” guides assume …
Don’t get me wrong I greatly appreciate and respect the intent and effort involved. Heck I’m doing a “how to” myself right now! But skipping info because “everyone” knows or because of an “assumed configuration” is unfortunate and causes major frustrations for others.
So things that didn’t work for me installing Lineage 16.0 on my Samsung Galaxy Tab S2 , SM-T713 region XAR.
Things they DON’T tell you:
• Let us start right at the end of that last sentence “region XAR.”
Look at any list of regions Samsung Firmware is released for that you can find. Canada is listed, United Kingdom is listed. Is USA, United States, or America listed? Nope! Somehow we are supposed to know that “Cellular south” is the correct firmware to use?
• The Tab S2 needs to have the Android Nougat 7.0 firmware. That makes sense. But would you presume that the latest 2019 Samsung Update, T713XXS2BSG1_T713XAR2BSB1, would not work?
It turns out that the latest (as of this writing) Lineage, lineage-16.0-20200928-nightly-gts28vewifi, requires a SPECIFIC Samsung Firmware Update -> T713XXU2BRB2_T713XAR2BRB2, dated March of 2018.
Repeated Error 7 from TWRP: Unzip the Lineage file. Look in META-INF\com\google\android and open the updater-script with notepad (Notepad++ is even better) find the “Target:” statement. It will tell you which Samsung firmware update the Lineage was built for.
• Odin won’t recognize the Tab S2:
and/or
Heimdall returns ERROR: “Failed to access device. libusb error: -12”:
Samsung firmware update requires Odin. Changing recovery to TWRP uses Heimdall. It appears these two Flash Softwares use different Windows 10 Drivers to communicate with the SM-T713
o After using Heimdall (and zadig-2.4.exe to install its drivers) you need to use SAMSUNG_USB_Driver_for_Mobile_Phones.exe to reinstall the Samsung Drivers if you want to use Odin3
o After using Odin3 and the required Samsung Drivers you need to use zadig-2.4.exe to reinstall the drivers used by Heimdall
• Tab S2 stuck on Samsung at boot after Samsung firmware upgrade:
Use recovery or TWRP, either one, to Wipe the Cache Partition
NOTE: I didn’t fix this boot loop issue after Flashing T713XXU2BRB2 and TWRP installed lineage-16.0-20200928 just fine . And lineage booted up A-OK.
There are things I haven’t told you that aren’t in the instructions either:
When you boot into stock recovery you’ll get “no instruction” – just wait it out
Flashing Lineage from your MicroCD is much easier than “adb sideload”
Odin takes a long time to load the Samsung Firmware before you can proceed
If Odin3 fails or especially partially fails, just do it again from the beginning
Boot into Recovery – Home + Power + Volume Up works best
Download mode - Home + Power + Volume Up works best
If you screw something up and can’t shut down – Power + Volume Down
Then IMMEDIATELY at black screen Home + Power + Volume Up – you can power off from there
Before Lineage install in TWRP
Wipe – Format
Wipe – Advanced - Cache & System
(Some instructions wipe more, DON’T)
If the Lineage install fails, you’ll have no OS and will need to reinstall a Samsung Firmware via Odin3
And more I’m sure
bardell3600 said:
Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”
There are many sites offing Step-by-Step guides.
I used
https://wiki.lineageos.org/devices/gts28vewifi/install and/or
https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-16-0-t3903286
(SEE BELOW for what’s missing from the instructions)
I have a 2016 Samsung Galaxy Tab S2 8.0 that seemed to be on its last legs. After all, it is the 4th quarter of 2020 as I write this. The current version of Android is 10. This poor old, much loved, tablet runs either Android 5, 6 or 7. Ancient, right!
I upgraded to Lineage 16.0 (17.0 was still “unofficial” in late summer 2020) – Android 9. All I can say is WOW!! A whole new tablet, or at least that is the way it behaves.
The process took me two days. It should have been about 2 hours. I’m writing this to save others those 46 hours of frustration.
I absolutely hate it when those that create the “How to” guides assume …
Don’t get me wrong I greatly appreciate and respect the intent and effort involved. Heck I’m doing a “how to” myself right now! But skipping info because “everyone” knows or because of an “assumed configuration” is unfortunate and causes major frustrations for others.
So things that didn’t work for me installing Lineage 16.0 on my Samsung Galaxy Tab S2 , SM-T713 region XAR.
Things they DON’T tell you:
• Let us start right at the end of that last sentence “region XAR.”
Look at any list of regions Samsung Firmware is released for that you can find. Canada is listed, United Kingdom is listed. Is USA, United States, or America listed? Nope! Somehow we are supposed to know that “Cellular south” is the correct firmware to use?
• The Tab S2 needs to have the Android Nougat 7.0 firmware. That makes sense. But would you presume that the latest 2019 Samsung Update, T713XXS2BSG1_T713XAR2BSB1, would not work?
It turns out that the latest (as of this writing) Lineage, lineage-16.0-20200928-nightly-gts28vewifi, requires a SPECIFIC Samsung Firmware Update -> T713XXU2BRB2_T713XAR2BRB2, dated March of 2018.
Repeated Error 7 from TWRP: Unzip the Lineage file. Look in META-INF\com\google\android and open the updater-script with notepad (Notepad++ is even better) find the “Target:” statement. It will tell you which Samsung firmware update the Lineage was built for.
• Odin won’t recognize the Tab S2:
and/or
Heimdall returns ERROR: “Failed to access device. libusb error: -12”:
Samsung firmware update requires Odin. Changing recovery to TWRP uses Heimdall. It appears these two Flash Softwares use different Windows 10 Drivers to communicate with the SM-T713
o After using Heimdall (and zadig-2.4.exe to install its drivers) you need to use SAMSUNG_USB_Driver_for_Mobile_Phones.exe to reinstall the Samsung Drivers if you want to use Odin3
o After using Odin3 and the required Samsung Drivers you need to use zadig-2.4.exe to reinstall the drivers used by Heimdall
• Tab S2 stuck on Samsung at boot after Samsung firmware upgrade:
Use recovery or TWRP, either one, to Wipe the Cache Partition
NOTE: I didn’t fix this boot loop issue after Flashing T713XXU2BRB2 and TWRP installed lineage-16.0-20200928 just fine . And lineage booted up A-OK.
There are things I haven’t told you that aren’t in the instructions either:
When you boot into stock recovery you’ll get “no instruction” – just wait it out
Flashing Lineage from your MicroCD is much easier than “adb sideload”
Odin takes a long time to load the Samsung Firmware before you can proceed
If Odin3 fails or especially partially fails, just do it again from the beginning
Boot into Recovery – Home + Power + Volume Up works best
Download mode - Home + Power + Volume Up works best
If you screw something up and can’t shut down – Power + Volume Down
Then IMMEDIATELY at black screen Home + Power + Volume Up – you can power off from there
Before Lineage install in TWRP
Wipe – Format
Wipe – Advanced - Cache & System
(Some instructions wipe more, DON’T)
If the Lineage install fails, you’ll have no OS and will need to reinstall a Samsung Firmware via Odin3
And more I’m sure
Click to expand...
Click to collapse
Thanks for this,
I am looking to breath some life into my wife's S2 8.0. Where did you get the March 18 firmware? I looked on Sam Mobile and I cannot download it as I am not a premium member. Her tablet is already on the July 2019 version which is what I downloaded this morning just to have on hand ( I am also in Canada)
**Update - I found a link to the firmware you mentioned and downloaded it**
Do you mind sharing the link to the download? thanx
RJC_68 said:
**Update - I found a link to the firmware you mentioned and downloaded it**
Click to expand...
Click to collapse
Hello there, do you mind sharing where you downloaded the right firmware?
Thanks a lot
pas7771 said:
Hello there, do you mind sharing where you downloaded the right firmware?
Thanks a lot
Click to expand...
Click to collapse
It may have been this site
Galaxy Firmware - Samsung Galaxy Tab S2 8.0 (SM-T713)
Samsung Galaxy Tab S2 8.0 Android tablet. Announced Jul 2015. Features 8.0″ Super AMOLED display, Exynos 5433 chipset, 8 MP primary camera, 2.1 MP front camera, 4000 mAh battery, 64 GB storage, 3 GB RAM.
galaxyfirmware.com
We have sold all our android devices and gone back to Apple so I cannot be 100% sure.
Hope this helps