[SOLVED] Help about new update - Moto G5 Plus Questions & Answers

Hey,
I just bought new moto G5 plus from flipcart and its model no is XT1686
and it is running NPJ25.137-15 Android version (Running January 1 Security patch)
and now I got OTA for updating to NPJ25.137-67(no security update info given) and I don't know which is safe or not Because I had slimier issue with my moto G4 plus and it got hardbricked and I had to wait a long time for the appropriate blank-flash. So guys anyone can tell me should I update or not? or should I flash stock ROM using Fastboot? Bootloader is locked but Stock firmware doesn't requires unlocked bootloader, right?? PLEASE TELL ME

This is just fine. No reason to suspect Motorola would break your stock phone with a stock update....

siddhesh9146 said:
Hey,
I just bought new moto G5 plus from flipcart and its model no is XT1686
and it is running NPJ25.137-15 Android version (Running January 1 Security patch)
and now I got OTA for updating to NPJ25.137-67(no security update info given) and I don't know which is safe or not Because I had slimier issue with my moto G4 plus and it got hardbricked and I had to wait a long time for the appropriate blank-flash. So guys anyone can tell me should I update or not? or should I flash stock ROM using Fastboot? Bootloader is locked but Stock firmware doesn't requires unlocked bootloader, right?? PLEASE TELL ME
Click to expand...
Click to collapse
buddy dont worry update ur phone it have march security patch along with some bugfixes for the OS!
i have already updated mine safely,just charge your battery to 50%

love4chat said:
buddy dont worry update ur phone it have march security patch along with some bugfixes for the OS!
i have already updated mine safely,just charge your battery to 50%
Click to expand...
Click to collapse
Ok I am taking risk the update is about 214 MB in size. I am really worried because Motorola broke my phone(g4 plus) when I installed june security patch when I had January patch ( the march one was missing) so it hardbicked my phone.
I am really worried right now. Is this gonna work?:crying:

siddhesh9146 said:
Ok I am taking risk the update is about 214 MB in size. I am really worried because Motorola broke my phone(g4 plus) when I installed june security patch when I had January patch ( the march one was missing) so it hardbicked my phone.
I am really worried right now. Is this gonna work?:crying:
Click to expand...
Click to collapse
it will be totally fine dont worry amigo!

siddhesh9146 said:
Ok I am taking risk the update is about 214 MB in size. I am really worried because Motorola broke my phone(g4 plus) when I installed june security patch when I had January patch ( the march one was missing) so it hardbicked my phone.
I am really worried right now. Is this gonna work?:crying:
Click to expand...
Click to collapse
You've got a new device, so the chances of your hard bricking are very low, since your bootloader is locked and never been unlocked. Additionally, as others have mentioned, the NPN25.137-67 update is the currently available update for Indian devices. So your device should be unmodified and downloading the recommended update.
But yeah, provided you do not downgrade, you should be okay to receive and flash OTA updates. I still don't quite understand how you bricked your device with the June update, did you downgrade your G4 plus to the December update? I'm confused as to how you flashed the June 2017 OTA update without taking the March patch first...

SOLVED
@Karlinski @love4chat @echo92 Thanks for the info
I've updated my phone and the update was successfully installed :laugh:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and @echo92 my moto g4 plus was bricked because of downgrading. what happened actually my phone was running june security patch and everything was fine but then all of a sudden I installed some custom ROMs on it. after 2 days I wanted switched back to the stock android, so I flashed the Stock ROM from fastboot and I accidentally flashed the older rom from there. I got the OTA for installing June Patch and I installed it (I didn't aware of one last patch was missing) I connected my phone to charging, The update was downloaded and started installing, once loading bar reached 75% it went blank. I tried to open boot-loader but it didn't opened, it was worst nightmare. This is why I get worried when Motorola release new update

Duplicate

siddhesh9146 said:
@Karlinski @love4chat @echo92 Thanks for the info
I've updated my phone and the update was successfully installed :laugh:
and @echo92 my moto g4 plus was bricked because of downgrading. what happened actually my phone was running june security patch and everything was fine but then all of a sudden I installed some custom ROMs on it. after 2 days I wanted switched back to the stock android, so I flashed the Stock ROM from fastboot and I accidentally flashed the older rom from there. I got the OTA for installing June Patch and I installed it (I didn't aware of one last patch was missing) I connected my phone to charging, The update was downloaded and started installing, once loading bar reached 75% it went blank. I tried to open boot-loader but it didn't opened, it was worst nightmare. This is why I get worried when Motorola release new update
Click to expand...
Click to collapse
Yeah, that's what happened with most users with the June 2017 update on Moto G4 devices (and lessons may well apply to G5 users too). If you took the June 2017 update (or for Moto G5 users, the May security patch or newer), then downgraded with an older stock ROM, the OTA would install thinking your device bootloader was on the same patch level as your system (which in this case it wasn't). Thus, the OTA would have corrupted your newer bootloader, leading to a hard brick. You mentioned being on the December/January update, so you'd likely have obtained the March 2017 OTA, which corrupted your June 2017 OTA - else, if it were the same patch level, the OTA would likely have been okay.
In other words, don't downgrade your device and take OTAs, regardless of whether you're on a G4/G5.... Besides, you've still got your warranty with a new G5, so you might as well wait for the next OTA update after 137-67 - hopefully it's soon, as EU - and likely US users - are on the NPNS25.137-33-11 (August 2017 security patch) and other US users are on the May 2017 update (NPNS25.137-35-5)...

Related

Moto X AT&T 2016-04-01 update ready

Tonight i receive new update on my moto x xt1058 AT&T carrier
The system version is 222.201.1
Build number LPAS23.12-21.7-1
I installed it some performance bugs was cleared and battery was also optimised as i assumed
Phone was now faster than before
Now another thing there is no root the developers have another challenge to patch this firmware also
Because AT&T have locked bootloader
Anyone who install this update
please share your experience also
Here is snaps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Br
Shahzaib Jahangir
Shabby The Dev said:
Now another thing there is no root the developers have another challenge to patch this firmware also
Because AT&T have locked bootloader
Anyone who install this update
please share your experience also
Click to expand...
Click to collapse
I wonder if this root security patch affects those of us with unlocked bootloaders? (Probably not)
Also I hope the full image is released soon...
squaremoogle said:
I wonder if this root security patch affects those of us with unlocked bootloaders? (Probably not)
Also I hope the full image is released soon...
Click to expand...
Click to collapse
I got the same update notification and installed it. Motorola support has NO CLUE what this update is about. What is it?
I just got the notification too. I'm running a Chilean provider (Movistar) ROM, but the update just says 'en.CL'. I unlocked my bootloader a long time ago though via Motorola code IIRC, and to tell the truth I don't remember what precautions to take when receiving an OTA.
Moto X AT&T 2016-04-01 update ready
Not found any changelog for this update
Anyone found the changelog so please share it
Corsario_Negro said:
I just got the notification too. I'm running a Chilean provider (Movistar) ROM, but the update just says 'en.CL'. I unlocked my bootloader a long time ago though via Motorola code IIRC, and to tell the truth I don't remember what precautions to take when receiving an OTA.
Click to expand...
Click to collapse
My moto x xt1058 has also unlocked bootloader and i install this update without any issues
Shabby The Dev said:
Not found any changelog for this update
Anyone found the changelog so please share it
My moto x xt1058 has also unlocked bootloader and i install this update without any issues
Click to expand...
Click to collapse
Did you lose root after updating? Did you have to 'put bloatware back in' like the sticky says?
No my phone was not rooted
Anyway if bootloader was unlocked so you also can easily downgrade your moto x with 21.7 firmware
But be carefully
Backup your data first
I don't backup any data even contacts and update it [emoji2] and i m lucky
Br
Shahzaib Jahangir
Shabby The Dev said:
Not found any changelog for this update
Anyone found the changelog so please share it
My moto x xt1058 has also unlocked bootloader and i install this update without any issues
Click to expand...
Click to collapse
I don't follow... How is it that your bootloader is unlocked, but you are unable to root?
You can still flash a system app and root that way, correct?
I am updating from 222.26.7.ghost_att.ATT.en.US and the zip includes several system library updates and a new modem firmware.
I have an unlocked bootloader and a rooted phone, so to install:
* Boot to recovery (TWRP) and make a backup copy of update zip (/cache/Blur_Version.222.26.7.ghost_att.ATT.en.US.zip) at /sdcard (aka /data/media/0).
* Flash system and recovery to stock firmware in bootloader
* Install the update using stock recovery
* Reflash TWRP and reinstall SuperSU and Xposed
squaremoogle said:
Shabby The Dev said:
Corsario_Negro said:
Did you lose root after updating? Did you have to 'put bloatware back in' like the sticky says?
Click to expand...
Click to collapse
No my phone was not rooted
Click to expand...
Click to collapse
I don't follow... How is it that your bootloader is unlocked, but you are unable to root?
You can still flash a system app and root that way, correct?
Click to expand...
Click to collapse
Shabby means his phone was not rooted prior to applying the update, not he lost root or was unable to root.
I would happily take it if it means better battery life root is useless in its current state.
Just got the update notification on the XT1060.
I'm trying to learn how to root this thing, as I've never done so on an Android device. Should I hold off on updating this until after I've rooted?
My brother's wife got this update and now her phone is not connecting to their wifi network, even after several resets and different configurations.
Hopefully the old root methods will be adapted to this update.
Please chime in if you have a similar problem or a solution.
---------- Post added at 05:26 PM ---------- Previous post was at 05:21 PM ----------
MortimerR said:
Just got the update notification on the XT1060.
I'm trying to learn how to root this thing, as I've never done so on an Android device. Should I hold off on updating this until after I've rooted?
Click to expand...
Click to collapse
Definitely consider rooting/unlocking your bootloader as an alternative to official releases. You just have so many more options once you've made custom roms available to yourself.
Installed in on my dev edition and haven't noticed any difference.. Probably not a significant update.
cipsaz said:
Installed in on my dev edition and haven't noticed any difference.. Probably not a significant update.
Click to expand...
Click to collapse
Did you use this OTA on a rooted device? If so, did it impact your root?
bobo-the-drunk said:
Did you use this OTA on a rooted device? If so, did it impact your root?
Click to expand...
Click to collapse
The device is not rooted.
Does anybody have the stock zip for this update or know where they're usually located? I've been researching the method CrashXXL used to add root/Xposed/remove bloat, but then Moto dropped this update and I have to start from scratch.
lpjunior999 said:
Does anybody have the stock zip for this update or know where they're usually located? I've been researching the method CrashXXL used to add root/Xposed/remove bloat, but then Moto dropped this update and I have to start from scratch.
Click to expand...
Click to collapse
@iscaela posted the instructions to get update.zip file in the first page read but for this you need rooted phone
Don't Ever update your rooted moto X to the latest firmware via OTA specially verizon xt1060
My friend update a rooted xt1060 via OTA to the latest firmware and now his phone doesn't booted anymore Stuck on fastboot with an error of system failure
Now no firmware available right also fail to downgrade waiting for new update firmware
another thing this update have only SECURITY PATCH not any changing but i think patched the root privileges
Shabby The Dev said:
@iscaela posted the instructions to get update.zip file in the first page read but for this you need rooted phone
Click to expand...
Click to collapse
You also need an unlocked bootloader, which I don't have.

Security patch

Just got new OTA today for Osprey 2GB 1540 got January 1 2017 security patch. I was shocked this is the first OTA I have gotten on my wifes phone since we did the initial OTA update when we bought it to get 6.0. Did anyone else get it? Build # MPIS24.65-25.1-14
https://motorola-global-portal.cust...prod_answer_detail/a_id/116348/p/30,6720,9390
orvon.freeman said:
Just got new OTA today for Osprey 2GB 1540 got January 1 2017 security patch. I was shocked this is the first OTA I have gotten on my wifes phone since we did the initial OTA update when we bought it to get 6.0. Did anyone else get it? Build # MPIS24.65-25.1-14
Click to expand...
Click to collapse
I was prompted with a Jan 2017 patch update this morning as well. Osprey, 2GB, 1540 model. Update Version: 24.211.14.en.US (from the system update notice)
I haven't accepted it yet.
I am using XT1541 1GB model and I went back to stock ROM with stock Recovery few weeks ago . I recieved two security updates one after another which I acceptede an disntalled succesfully . However I am not sure if you have a custom recovery and whether they will be compatible with customer recovery . One of them was security update an dsecodn one included support for security+ unicode 8 support in text messages or something like that
usually they wont work with custom recovery. Nice to see they are at least giving us security patches, since we wont get 7.0 officially. (as of now anyway)
Well, just over a year of phone uptime, haha. I was seeing how long it would go before crapping out, and now Motorola wants to give us security updates from the past year and 3 months.
I'm not sure I'll give this phone another year of use to try again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
orvon.freeman said:
Just got new OTA today for Osprey 2GB 1540 got January 1 2017 security patch. I was shocked this is the first OTA I have gotten on my wifes phone since we did the initial OTA update when we bought it to get 6.0. Did anyone else get it? Build # MPIS24.65-25.1-14
https://motorola-global-portal.cust...prod_answer_detail/a_id/116348/p/30,6720,9390
Click to expand...
Click to collapse
I received it as well for my XT 1540. See this. Still have not updated; waiting to find enough time time to restore pre-rooted ROM and rebuild. I am interested in others (with a rooted stock ROM) experience in flashing latest OTA.
Can anyone provide flashable zip of this update?
rajatkumar2910 said:
Can anyone provide flashable zip of this update?
Click to expand...
Click to collapse
There is no such thing.
I received the security patch, switched to stock recovery before trying to install, but was unsuccessful, I have root/xposed so it seems you need to have an unmodified system partition to work
anyone knows a way to apply the ota successfully without flashing stock system first, or at least a way to get rid of the annoying notification, prompting for the update?
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
I received the security patch, switched to stock recovery before trying to install, but was unsuccessful, I have root/xposed so it seems you need to have an unmodified system partition to work
anyone knows a way to apply the ota successfully without flashing stock system first, or at least a way to get rid of the annoying notification, prompting for the update?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was successful updating my rooted stock ROM. But I did have to flash a pre-rooted ROM first. See this.
Hello guys!
I updated my moto g TE (xt1556), to january security patch, but I'm having problem to install xposed, after install stuck on warning bootloader, anyone more having this issue? or any idea how can I fix that?
I've installed the update on my XT1541 (non-rooted), but I'm not too happy about it. Had twice issues with network connectivity and it generates a bugreport every 2 hours or so. Haven't had the time to look at a report to see what crashes...

V20 in the UK - What SW Version are You On?

I have just bought a V20 from an Ebay seller.
It comes with Android 7.0 and it says that there are no newer versions to download.
However, my security patch level seems quite old being December last year.
The SW version details are as follows:
Android Version - 7.0
Android Security Patch Level - 1 December 2016
Kernel Version - 3.18.31
Build Number - NRD90M
Software Version - V10c-TWN-XX
Does anyone else in the UK with a V20 have more up to date software and if so how did you get it?
GadgetObsessive said:
I have just bought a V20 from an Ebay seller.
It comes with Android 7.0 and it says that there are no newer versions to download.
However, my security patch level seems quite old being December last year.
The SW version details are as follows:
Android Version - 7.0
Android Security Patch Level - 1 December 2016
Kernel Version - 3.18.31
Build Number - NRD90M
Software Version - V10c-TWN-XX
Does anyone else in the UK with a V20 have more up to date software and if so how did you get it?
Click to expand...
Click to collapse
I see you have the TWN variant. Idk why but it haven't received the latest security patch.
AbrahamW08 said:
I see you have the TWN variant. Idk why but it haven't received the latest security patch.
Click to expand...
Click to collapse
So do all TWN phones have a security patch from December 2016?
Do other variants of the phone have later patches?
Go here -
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
Download the following firmware -
H990ds10e_OPEN_SG_DS_OP_0314.kdz
Follow instructions in OP and when in LGUP select Update.
You'll have newer firmware with security patch at 1 March 2017.
And use search function, this has been answered already.
GadgetObsessive said:
So do all TWN phones have a security patch from December 2016?
Do other variants of the phone have later patches?
Click to expand...
Click to collapse
I think so... At least mine still in December.
Yes, the majority of the other variants are in April/March security patch
rubiicon59 said:
Go here -
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
Download the following firmware -
H990ds10e_OPEN_SG_DS_OP_0314.kdz
Follow instructions in OP and when in LGUP select Update.
You'll have newer firmware with security patch at 1 March 2017.
And use search function, this has been answered already.
Click to expand...
Click to collapse
Thanks for that.
I had seen that link but I had no idea if that would install a later version of software than I already have.
Just so I understand - why does my phone say that it is up-to-date if there is a later version of the firmware on LGs web site? (Where does the V20 check for firmware revisions?)
You're welcome. I was also supplied the link by another user, that's one of the great things about XDA and the members here.
Because a lot of us TWN variant owners don't live in the region the phone was released in we won't get OTA updates.
That's just how LG operates. I find it ridiculous that they release variants for different regions with different specs, hardware etc..
How do they come to the conclusion that the V20 will not be released in the UK and Europe?
People of some countries prefer 64GB but others will be happy with 32GB????
Wireless charging only for some?
Then there's the bootloader unlock farce........
This phone is really awesome and root would make it even more the perfect phone for me. But I knew what the situation was before I got it, and I'm still happy I own it.
GadgetObsessive said:
Thanks for that.
I had seen that link but I had no idea if that would install a later version of software than I already have.
Just so I understand - why does my phone say that it is up-to-date if there is a later version of the firmware on LGs web site? (Where does the V20 check for firmware revisions?)
Click to expand...
Click to collapse
Because the updated firmware is NOT meant for your branded TWN V20. It will work but you will not get any upcoming updates anymore. You will have to that maually.
Hi Pierre.
You're absolutely correct, but updating to where we are now is better than no update at all don't ya think?
And it's easy now to check for and install future updates :good:
rubiicon59 said:
Hi Pierre.
You're absolutely correct, but updating to where we are now is better than no update at all don't ya think?
And it's easy now to check for and install future updates :good:
Click to expand...
Click to collapse
Hi, you are absolutely right about that. And I think it's pretty safe to switch firmware. it's quite easy with LGUP. But maybe LG will surprise us the coming weeks with a fresh new TWN update
And a bootloader unlock too?
That would be awesome, I'm already missing all the stuff I was able to accomplish on my Z2.
H990DS can be flashed to same model firmware of other regions. My TWN H990ds had flashed to Philippines V10g and working without any problem , only two pop-up message after every system restart , but it didn't affect to any function..
Base on the hardware of H990ds is similar to H990n (HongKong) , I tried to flash to V10h(H990n) and it is working as well.
Both version's performance are better than TWN-V10c , i think it's worth to upgrade.
V10H-HongKong
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
V10G-Philippines

T-Mobile released(or about to release) new firmware G950USQU1AQHD

Looks like new T-Mobile firmware is coming.
Changelog:
IMS Roaming enhancements
Various system improvements
https://support.t-mobile.com/docs/DOC-34292
Nice, I want to update this later.
Update is live 414.96MB TMobile Los Angeles. :good:
picachux said:
Update is live 414.96MB TMobile Los Angeles. :good:
Click to expand...
Click to collapse
Same here in Northern Indiana had to manually search for it on the phone but downloading now:good::highfive::good:
Yep, got it and updated already. Salem, Oregon USA.
updating now.
So what's changed in the update? Any new features or any taken away?
Sent from my SM-G950U using Tapatalk
Aug security patches
Sent from my SM-G950U using Tapatalk
Does updating to this impact Adhell2 installs? Will it re-enable all of the bloat that I've disabled already?
I installed this update this morning and I received "Android. System. UI has stopped working" every time my phone tried to boot.
I thought that Substratum StatusBar Icons for Samsung was causing the issue. I was able to boot into safe mode one time and uninstalled Substratum StatusBar Icons, thinking that this would fix my boot issue. My issue was not fixed and I was not able to boot into Safe Mode again without receiving the "Android. System. UI has stopped working" error every time.
I installed Samsung Galaxy S8+US Unlocked Firmware XAA Version Live!!! (https://forum.xda-developers.com/tmobile-galaxy-s8+/how-to/galaxy-s8-xaa-version-live-t3613013) so that i can get my phone working again.
Can anyone point me in the right direction on re-installing the updated T-Mo firmware?
Baxbag said:
I installed this update this morning and I received "Android. System. UI has stopped working" every time my phone tried to boot.
I thought that Substratum StatusBar Icons for Samsung was causing the issue. I was able to boot into safe mode one time and uninstalled Substratum StatusBar Icons, thinking that this would fix my boot issue. My issue was not fixed and I was not able to boot into Safe Mode again without receiving the "Android. System. UI has stopped working" error every time.
I installed Samsung Galaxy S8+US Unlocked Firmware XAA Version Live!!! (https://forum.xda-developers.com/tmobile-galaxy-s8+/how-to/galaxy-s8-xaa-version-live-t3613013) so that i can get my phone working again.
Can anyone point me in the right direction on re-installing the updated T-Mo firmware?
Click to expand...
Click to collapse
This thread will have link to firmware and instructions that you may need: https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
I don't get it, why we didn't receive September patch, especially if it is the end of the month and T-Mobile had enough time to do it. It is possible that they are planning to release 7.1.1 update soon as Note 8 has...
Charkatak said:
I don't get it, why we didn't receive September patch, especially if it is the end of the month and T-Mobile had enough time to do it. It is possible that they are planning to release 7.1.1 update soon as Note 8 has...
Click to expand...
Click to collapse
yea im surprised we didn't just get the september update. maybe there will be another update with 7.1.1? D: but its possible but i don't think samsung has released 7.1.1 for XAA models either yet so.
EDIT: are updates suppose to cause a dead pixel? after updating i got a dead pixel on my screen :\
Anyone know if this update I just got today will break root ability? When checking the site it says "security fixes". Here's a screenshot of update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Charkatak said:
I don't get it, why we didn't receive September patch, especially if it is the end of the month and T-Mobile had enough time to do it. It is possible that they are planning to release 7.1.1 update soon as Note 8 has...
Click to expand...
Click to collapse
I dont think we will see 7.1.x because Oreo is already under development and should be release in a month or 2.
https://www.sammobile.com/samsung-galaxy-android-8-o-update/
kdoweb1 said:
I dont think we will see 7.1.x because Oreo is already under development and should be release in a month or 2.
https://www.sammobile.com/samsung-galaxy-android-8-o-update/
Click to expand...
Click to collapse
In a month or so, there could be a beta program. I don't think that Samsung will be able to make Android 8 available globally earlier than late December or even in the new year. I personally do want to see the update sooner than later
Charkatak said:
In a month or so, there could be a beta program. I don't think that Samsung will be able to make Android 8 available globally earlier than late December or even in the new year. I personally do want to see the update sooner than later
Click to expand...
Click to collapse
couple weeks for beta man.
mweinbach said:
couple weeks for beta man.
Click to expand...
Click to collapse
If that is the case, even better!
tsh said:
Does updating to this impact Adhell2 installs? Will it re-enable all of the bloat that I've disabled already?
Click to expand...
Click to collapse
In case anyone was wondering, I just decided to test it myself. Before applying the update I re-enabled all of the packages because I read elsewhere that people had an issue if certain Samsung system apps were disabled. I did not uninstall AdHell2, just re-enabled all of the packages. The update went by without any problems and I then disabled all of the packages I want removed from the running system after the update.
The only thing I had to do to get back to my same modified config was re-run the ADB commands to restore the mobile data toggle.
ImaUseBT said:
yea im surprised we didn't just get the september update. maybe there will be another update with 7.1.1? D: but its possible but i don't think samsung has released 7.1.1 for XAA models either yet so.
EDIT: are updates suppose to cause a dead pixel? after updating i got a dead pixel on my screen :\
Click to expand...
Click to collapse
No there shouldn't be a dead pixel from the update.

V20 h990ds Taiwan variant got update

Today, h990ds taiwan variant got update. Anyone already update? Only few description with improve phone usability only. Mine still downloading with poor speed (around 100KBps). What happen with update server? Anyone suffer slow downloading speed like me?
Sent from my [device_name] using XDA-Developers Legacy app
hello yes mine is very slow 917 MB in size !!!!!!!!!!!!!!!!!!
Yes!!! Me too!!! very slowly download. The update came this morning around 08:00 am CET and still downloading, until now just download 10% so.... very poor speed.
One question, this update will be Oreo?? or just 7.1 or something like that???
Well count me in as one of those experiencing the slow downloads.
Same here. Downloading is very very slow. I am at 22 percent.
Iam also on 32% and ridiculous slow speed from server, unfortunatly it's not oreo nor 7.1 but security patch is at level 1 november 2017 with this update.
Too laggy for me [emoji852]
only November security patch update [emoji40][emoji40]
Sent from my [device_name] using XDA-Developers Legacy app
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my [device_name] using XDA-Developers Legacy app
Was laggy for the first few minutes but its settled in and its as speedy as before, not really sure why yours is so laggy maybe its a user problem and the apps you have installed.
Fantastic of LG to keep us inline with November security patch.
Just an FYI, when an update is that large and all it contains is the latest security update, you can almost be sure that they have incremented ARB. They have to send ALL of the firmware when they increment ARB since each piece is checked by the bootloader....
Just figured I would throw that out there in case anyone that is still downloading it wants to abort....
-- Brian
runningnak3d said:
Just an FYI, when an update is that large and all it contains is the latest security update, you can almost be sure that they have incremented ARB. They have to send ALL of the firmware when they increment ARB since each piece is checked by the bootloader....
Just figured I would throw that out there in case anyone that is still downloading it wants to abort....
-- Brian
Click to expand...
Click to collapse
do you recommend the update?
Enviado desde mi LG-H990 mediante Tapatalk
I don't have an H990, so all I can say is that if you are ARB 0, don't take it. If you are ARB 1 or greater, go ahead.
If you are rooted and you ever screw your phone up so bad that you have to flash the KDZ and you are ARB 0, you can get root back.
If you aren't rooted, and ever want to root, you need to be ARB 0.
ARB 1 or greater, or don't ever want to root, then it wouldn't matter.
runningnak3d said:
I don't have an H990, so all I can say is that if you are ARB 0, don't take it. If you are ARB 1 or greater, go ahead.
If you are rooted and you ever screw your phone up so bad that you have to flash the KDZ and you are ARB 0, you can get root back.
If you aren't rooted, and ever want to root, you need to be ARB 0.
ARB 1 or greater, or don't ever want to root, then it wouldn't matter.
Click to expand...
Click to collapse
According to sources this update is still ARB = 0.
this worked for me, I used LG-Bridge it was way quicker than the OTA. Use LG-Bridge on your PCs
To ones using miracast, do not update to v10h-TWN-XX since it has problems...see dedicated thread in this section
popo72 said:
To ones using miracast, do not update to v10h-TWN-XX since it has problems...see dedicated thread in this section
Click to expand...
Click to collapse
So sad, i just read your comment. I already installed the update. And as you said, i cannot miracast now i hope LG will fix it asap
Crazy stuff happening (depending on what you call crazy)
No sooner have I installed v10h - popular opinion is that it's arb =0 / it actually d/l pretty fast thru the phone on wifi <45mins.
Just started playing with the phone and I went to about phone to check out the version and I see that there is a software update notification. It seems like there is a v10i update in the system as of right now.
Has anyone else noticed this?
The only thing that it says is "security update from Google" 61.12mb. So it's relatively small update.
I haven't been able to find any information here or anywhere else on this update.
Just FWIW.
I just installed the update and it bumps the Android security patch level to 6 November 2017, and Software version is V10i.
I would say that this is pretty good.
/J
Tim3tripp3r said:
Crazy stuff happening (depending on what you call crazy)
No sooner have I installed v10h - popular opinion is that it's arb =0 / it actually d/l pretty fast thru the phone on wifi <45mins.
Just started playing with the phone and I went to about phone to check out the version and I see that there is a software update notification. It seems like there is a v10i update in the system as of right now.
Has anyone else noticed this?
The only thing that it says is "security update from Google" 61.12mb. So it's relatively small update.
I haven't been able to find any information here or anywhere else on this update.
Just FWIW.
Click to expand...
Click to collapse
The latest 61MB security update fixes the KRACK WiFi vulnerability affecting anything that can use WiFi worldwide.
What carrier do you have to be on to get the update on 900ds?

Categories

Resources