ASUS ZF3U Nougat/Android 7.0 AUG-2017 Update Released [OTA and Manual Available] - Asus ZenFone 3 Ultra Guides, News, & Discussion

UPDATED TOPIC! 02.08.2017
ASUS has released the NEWEST Nougat Update for ZF3U:
Newest Release: Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
Previous Version: Version WW_14.1010.1705.49 Release Date: 21.06.2017
Here is the official Update for Manual Install. DIRECT from ASUS Servers. Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/UL-ASUS_A001-WW-14.1010.1706.50-user.zip
Via:
http://https://www.asus.com/Phone/ZenFone-3-Ultra-ZU680KL/HelpDesk_Download/
If the link is expired Get it from the Asus ZenFone 3 Ultra Support and Firmware Website under Drivers and Tools-ANDROID Section. It is for the WW Version:
UPDATE! :OTA Update Working ONLY with phones with LOCKED Bootloaders. The Manual Update will work with both LOCKED and UNLOCKED Bootloaders. I have tested the OTA Update and after I unlocked my ZF3U's bootloader, I can no longer get update notification (on my previous ZF3U-I am on my 2nd one). From what I have read, ASUS servers block any devices with unlocked bootloaders from accessing automatic system updates. My only option is to find a way to RELOCK the bootloader or use the Manual Update file.
Enjoy!
Changelog:
Android 7.0 Nougat comes with handful of features such as App Shortcuts, Multi Window support, restart setting to power menu, Launch the camera by pressing the power button twice, Image Keyboard support, 100 emoji added, GIF Support, Quick Reply via Notification, Notification Redesigned panel, Notifications prioritization, Enhanced Doze Mode, System UI Tuner, Customizable Quick Settings, Don Not Disturb, New Settings Panel Redesigned, Data Saver per App, seamless updates and New Emoji Support.
-----------------------------------------
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item:
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to:
TW:http://www.asus.com/zentalk/tw/ReleaseNotes
WW:http://www.asus.com/zentalk/ReleaseNotes
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, .
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number

AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse

ctorbaoglu said:
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
It may be because your Bootloader is unlocked. If it is you will not receive the update. My ZF3U's bootloader was locked when I received the update. However, when I unlocked the bootloader, rooted and then decided to wipe everything through TWRP to do a fresh install of everything to reinstall Android 7.0 the trouble started. Now, I cannot do firmware update using the system Update menu (notification of update availability is not there). This is because the bootloader is now unlocked and I don't know if it is possible to relock it. I guess I have to wait for the full manual package of Android 7 to become available or see if anyone can help me to relock the bootloader and then update from Android 6.0 original firmware. I was excited to be finally getting Android 7.0 but only managed to use it for 1 day. Oh well, you live and learn.:crying:
Click to expand...
Click to collapse

UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.

AWFRONT said:
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
Click to expand...
Click to collapse
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.

doctahjeph said:
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
Click to expand...
Click to collapse
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.

AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??

doctahjeph said:
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
Click to expand...
Click to collapse
I have tried your suggestion numerous times and;
-it appears that when I boot to Android M, I don't have any sound in calls, fingerprint and other issues fully remain.
-when I upgrade to Android N, then Iam able to hear call sounds but fingerprint scanner still does not register and other issues still remain.
I have a feeling that somewhere along the process my device has enabled some sort of encryption and this is preventing the device from enabling all the features. No matter how many times I install/reinstall/wipe using stock or TWRP no change.
Does anyome know how I could disable encryption either using some sort of google service or through root etc... In settings device reports that it is encrypted. Also when I first booted the device after firmware update encrypting device message was shown. Not sure whats going on with my device. Hope to find out/fix soon though.

ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!

AWFRONT said:
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Click to expand...
Click to collapse
???? Thank you!!!

ASUS has released the NEWEST Nougat Update for ZF3U.
Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item:
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to:
TW:http://www.asus.com/zentalk/tw/ReleaseNotes
WW:http://www.asus.com/zentalk/ReleaseNotes
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, .
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
Once again, I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!

Never mind.

AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
Hey @AWFRONT How did u manage to go back from android 7 to 6 ...i recently updated my phone to nougat and want to go back to mm. Could u help me out I have unlocked bootloader

Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?

AWFRONT said:
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
Click to expand...
Click to collapse
all of this from twrp or stock recovery

If you have TWRP installed then apply from it, if not you can use the stock recovery of Android 6.0 as posted in one of the topics of ZF3U forum sections and flash it using custom recovery and then flash the appropriate firmware file of Android MM version 6.0 and on completion wipe cache, factory data and reboot.
Due to lack of developer support for this device, I do not recommend that you rollback the firmware. When my 1st device failed I realised that ASUS devices don't have the software fixability ease of Samsung devices so I am using my 2nd ZF3U in its original factory state. I love the device as it is and don't want to mess with it and root is no longer important to me.

does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks

gubbilo144 said:
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
Click to expand...
Click to collapse
mine is

Malam

anybody updated to WW-14.1010.1711.62 is it still 7.0 or 7.1.1

Related

[GUIDE] How to sideload the Nougat soak test onto your G4. [TEXT TUTORIAL]

AMAZON VARIANT NOW SUPPORTED!
NO PC REQUIRED AT ALL FOR THIS TUTORIAL!
READ ME: I am not responsible for bricked/damaged devices from following this procedure. It should be safe, if done right on the supported models. This does not void your warranty, but it is soak test firmware, meaning that it is beta software, and might have bugs/issues. I haven't noticed any myself, however.
Alright, I am aware that there are already videos describing how to install Nougat, but this is a (fairly) easy to follow text tutorial.
Step 1: Make sure your running the latest Marshmallow.
Before you can install the Nougat update, you have to make sure that you are running the latest Marshmallow firmware for your device. If your phone is running the MPJ24.139-63 firmware, you are good to go. Anything lower, and you will have to update your firmware, either manually, or through the OTA checker.
HAVE A NEWER FIRMWARE? (OR AMAZON VARIANT)
I had a link to a Reddit user's guide to do this, but they have apparently deleted their account, so I'll link this guide from XDA: http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
UPDATE: Download this file and flash it in recovery the same way that you install Nougat, to update to the latest Marshmallow firmware, if you are on anything lower than MPJ24.139-63: https://docs.google.com/uc?export=download&confirm=mkUs&id=0BzpjDRtfDv8PdER0cml3VzRHZTA
Step 2: Download the Nougat OTA File.
Follow this link to download the Nougat OTA file: http://downloadmirror.co/Uq5/Blur_Version.24.31.64.athene.retail.en.US.zip
Step 3: Boot into Recovery.
You have to boot into recovery to sideload this OTA file. First, power off the device completely. When it is completely powered down, hold the Volume Down button, and then the power button, not letting go of either button, until an Android appears, with a bunch of text. You are now in Fastboot Mode. Press the Volume Down button until you see Recovery Mode, then hit the power button.
Step 4: Install.
Once you are in Recovery, you may see an Android logo again, with the text "No Command" below it. What you need to do here is hold the power button, and whilst holding the power button, press Volume Up, to access the menu. It is easy from here. You need to select the option to install update from SD Card, using the Volume buttons for navigation, and Power to select. From there, you find where you downloaded the BLUR_VERSION.24.31.64.ATHENE.RETAIL.EN.US.ZIP file, and select it. It will start installing the official Nougat OTA. Give it some time, upwards of 15 minutes to install. Once it has complete, simply select the Reboot system now option, and if all went well, you should see the "Android is upgrading" screen, and now you are running official Nougat soak test on your G4.
NOTES - The install may hang on the "Patching system image after verification." message. Give it around 5-10 minutes, it will eventually pass that stage.
I can't guarantee that this method will work on all G4 variants. I can confirm it works on a UK Retail XT1622, however.
This may make it harder to install the stable official Nougat when that releases worldwide, I am not sure yet if it affects the upgrade path to the stable firmware.
KNOWN ISSUES
I actually have not found any issues with this firmware yet, it appears VERY stable for a soak test build. If you have come across any, or need help, comment below.
COMPATIBLE MODELS
These models have said to have had success with this update.
XT1643 - Moto G4 Plus Dual-SIM (India)
XT1640 - Moto G4 Plus Dual-SIM (Brazil)
XT1642 - Moto G4 Plus
XT1622 - Moto G4
XT1626 - Moto G4 (India)
DOWNGRADE TO MM FOR OFFICIAL NOUGAT OTA WITHOUT BOOTLOADER UNLOCK
Follow this guide from the Moto G4 Plus XDA section to downgrade your G4 to Marshmallow to install the official Nougat OTA:
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Welp, can't apply the MPJ24.139-63 update on XT1621 lol
Does it work on the xt1625 non amazon, MPJ24.139-64 ?
traceable ? (sorry not good at this title thing)
Hey thanks for sharing this.
I just wanted to ask whether or not Motorola/their repair service will be able to tell if I applied this update (meaning if I roll back to older firmwear without unlocked bootloader), since I sent my Moto G4 in for a repair but apparently since it came back yesterday the issues came back.
So I just want to make sure whether I can try this without them blaming it on me "flashing unfinished software" once I'll send it back for a repair/replacement
Thanks in advance
Yoloswaggerboy69 said:
Hey thanks for sharing this.
I just wanted to ask whether or not Motorola/their repair service will be able to tell if I applied this update (meaning if I roll back to older firmwear without unlocked bootloader), since I sent my Moto G4 in for a repair but apparently since it came back yesterday the issues came back.
So I just want to make sure whether I can try this without them blaming it on me "flashing unfinished software" once I'll send it back for a repair/replacement
Thanks in advance
Click to expand...
Click to collapse
They dont seem to care, they just reflash and send it back.
Rempala said:
They dont seem to care, they just reflash and send it back.
Click to expand...
Click to collapse
Thanks a bunch
Cyberneticx said:
Does it work on the xt1625 non amazon, MPJ24.139-64 ?
Click to expand...
Click to collapse
It does not. It checks your current firmware version and that one is too NEW. I have the same. I got this: http://i.imgur.com/ggmBiMZ.jpg
Cyberneticx said:
Does it work on the xt1625 non amazon, MPJ24.139-64 ?
Click to expand...
Click to collapse
mattgoldey said:
It does not. It checks your current firmware version and that one is too NEW. I have the same. I got this: http://i.imgur.com/ggmBiMZ.jpg
Click to expand...
Click to collapse
I have added a way to downgrade your firmware to install the update.
LoopingCreeper said:
I have added a way to downgrade your firmware to install the update.
Click to expand...
Click to collapse
Do I have to root the phone to downgrade?
I went to the link and I think it was a different version.
I bought mine on the motorola store and it's a custom phone. It came as xt1625 but there is no amazon nor anyother thing on it
Cyberneticx said:
Do I have to root the phone to downgrade?
I went to the link and I think it was a different version.
I bought mine on the motorola store and it's a custom phone. It came as xt1625 but there is no amazon nor anyother thing on it
Click to expand...
Click to collapse
You don't have to root or unlock your bootloader or anything like that. I believe that G4 and G4+ ROMs are interchangeable.
LoopingCreeper said:
I have added a way to downgrade your firmware to install the update.
Click to expand...
Click to collapse
That reddit post is deleted and the person that posted it deleted their account. Not sure I'd be comfortable downgrading now.
Can anyone confirm XT1621? Would it be safe to bet that it'll work if XT1622 is working?
Thank You, i have MOTO G4 with Nougat,
no need to downgrade the bootloder because i was on MPJ24.139-63, this worked with XT1622 - Moto G4 bought from Romania.
"Patching system image after verification" was like 15 minutes and when i choose reboot the led in the bottom of phone was flashing,(strange, i was reading about this led on xda) i hope will function in Nougat .
this does not work in any way shape or form with the XT1625 retail or amazon variants.
If I were upgrading from stock marshmallow to stock nougat and not performing a factory reset I would completely understand why i need to be on the latest version. However, I'm coming from a cm based ROM and will have to do a factory reset anyways. The firmware file includes the most up to date bootloader, soooo why do I need to flash -63 before flashing -64? Is there something I'm missing here or am I correct?
(I'm on Retus XT1625, non Amazon prime variant with an unlocked bootloader)
Travisholt92 said:
If I were upgrading from stock marshmallow to stock nougat and not performing a factory reset I would completely understand why i need to be on the latest version. However, I'm coming from a cm based ROM and will have to do a factory reset anyways. The firmware file includes the most up to date bootloader, soooo why do I need to flash -63 before flashing -64? Is there something I'm missing here or am I correct?
(I'm on Retus XT1625, non Amazon prime variant with an unlocked bootloader)
Click to expand...
Click to collapse
short answer to your question: the nougat ROM looks for a -63 boot image, and also verifies against baseband versions.
it doesn't matter though, because the Nougat ROM linked herein will not work on a XT1625. i have spent hours trying to make it happen.
trevorcobb said:
it doesn't matter though, because the Nougat ROM linked herein will not work on a XT1625. i have spent hours trying to make it happen.
Click to expand...
Click to collapse
What error are you getting when you try and flash it? I tried, but my firmware version was newer than the expected version, so it refused to flash.
I tried this on a locked bootloader with XT1625 amazon prime phone.
I am getting the error This package expects the value "athene" for "ro.product.name" or "athene" for "ro.product.name" on the OEM partition; But the actual value are "athene_amz""athene_amz"
It'll probably work on the non-Amazon version, then.
I have Adoptable Storage and the ZIPs don't show up in the SD card. Is it safe to swap to another card temporary to do the update?

[FOTA][MM][DOWNLOAD] SM-G930A APJ4 Update File

Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Looking at the CSCVersion.txt File inside the ZIP shows that this is G930AATT4APJ4 for anyone wondering which version
elijahblake said:
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Click to expand...
Click to collapse
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
thelostsoul said:
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
Click to expand...
Click to collapse
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
KingOfTheNet said:
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
Click to expand...
Click to collapse
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
Most likely be Spring with AT&T and their release record.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
It's fine, I just flashed it to mine and it's just a security patch for MM. I will capture the official Nougat FOTA release once it comes out.
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Omar04 said:
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Click to expand...
Click to collapse
One issue with that... qa6 is feb update...
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Added screenshot
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Yeap it doesnt apply for Beta they are always ahead of time only official releases match. (There's always that one build that wants to break the rules, but only happen with unreleased builds mostly because they apply the security patch early for testing and compiler gives that build code.)
It always has been that way with Samsung since the OG Galaxy S.
Check my posts from several years ago on earlier galaxies and you'll notice.
KingOfTheNet said:
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
Click to expand...
Click to collapse
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
There was no compiling. You can flash the ota update files from stock recovery after renaming the file name extension from .cfg to .zip.
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
I didn't flash the update file itself, I had the ODIN files for it. They're the same thing.
When it comes to official updates, no signature modification should be necessary (Or possible, for that matter. I don't think there's a way to modify the signature. If there is, I don't know about it.). The only thing different between the 2 files is the file format.
Hope I answered your questions.
Cheers!
Can You Supply the Latest FOTA roms For.
G930AUCU4BQK2
G930AUCS4BQJ2
G930AUCS4BQH1
I have an Unlocked G930A (not really unlocked just using a cricket SIM) But I cannot Get the Software Updates For it because of AT&T. I have seen the information on reflashing it to the U software but i really dont want to have to restore everything to my phone unless i have to..
The Version currently running on my phone is vulnerable to the bluebourne exploit and im trying to get that patched. :/
On a side note. are you able to do a packet capture while scanning for the updates? There is one on the play store that will also let you perform a MITM on the application and you should be able to capture anything sent over SSL in plain text/hex/etc
I did Want to Ask you a quick question. How did you capture the FOTA package to begin with?
I wonder if it is possible to setup an Authoritative only dns server and then use it to spoof the location of the update servers. to create a DNS method that would allow the FOTA to be pushed to devices no longer on AT&T
Anywho if you can get those firmwares and get me full packet captures of just the update application while it is checking and downloading the update, i might be able to create a web application that is able to capture the headers sent by the phone that identify its model/fw version/etc and be able to push the firmware update Via the built in option in the settings, (although you may need to swap your dns settings for a moment and install a CA cert that allows validation of a connection. im not too sure if a CA cert will need to be installed because im not sure if they push the updates over a SSL/TLS connection. Using the data collected here may also pave the way to enable this to work with other models and carriers and manufacturers. (my hypothesis is that packet captures would be needed on any firmware updates "you" would want to push with this)
Basically Im thinking it might be possible to download those zip files along with the packet capture data to create a simple web application that is able to tell the phone there is a software update available. It would require using a 3rd party DNS server to "redirect" the connection to a server that doesnt care if your an at&t customer. It might also need a self signed CA cert installed into the device to Validate TLS/SSL. From there it might be possible to have the server 301 redirect the zipfile to another url that is behind a CDN to reduce the risk of ddos and keep the server(s) stable keeping the downloads reliable and fast.
Seeing how the Firmware update is already digitally signed by Samsung and/or AT&T it should probably install without an issue. I dont see the possibility of the wrong stock firmware being flashed on the wrong phone provided the manufactuer had a proper assert statement in place to verify the model and sw/hw versions, and im pretty sure a stock recovery wont accept a firmware signed by any key.
I might be Going off topic here, But one more question.
Do i actually need AT&T service to download the OTA updates from the Software update function in the phone settings.
What i mean by this is does the SIM card need to have an active plan on it? or can it just be provisioned to their network with out a phone plan and downloaded over wifi?
UPDATE: It Can Now be officially confirmed that Carriers and Samsung Deliberately block OTA updates when you unlock the device. there are thousands if not tens of thousands out there on a variety of devices as far back as the S4 that may not have been able to get updates. just because they used a Cricket Sim or unlocked the device. I also Spoke with AT&T customer support today and got told the blatant Lie that they push the same OTA updates through the cricket network to ensure that AT&T devices on it can be updates. I also went to samsung service center at bestbuy and they told me my phone was up to date when its not. Samsung Smart Switch Also Reports that my device is up to date when i know for a 900% fact it is not.
So it looks like Someone is going to have to write an app that Hijacks the Requests and replays a valid packet capture just to get the phone to update in its orignial intended built in method.
The sad part is the carriers would see this and just write a patch to prevent it rather then change their policies.
Basically The carrier has the right to deny you a software update because you left their network and leave you exposed to Critical Security Vulnerabilities.
That is their way of sticking up their Middle Finger at the FCC for mandating carriers unlock their devices and the end user who either met his/her contract obligation or outright paid for his/her device
[SARCASM] basically its like saying hey we know you paid for your device, but **** you, you left our network and even though the updates come from a samsung controlled server were going to ensure our middleware deliberately blocks your device from updating so you remain vulnerable and you information is stolen, That'l teach you for unlocking your device and leaving our network because we charge literally an arm and leg for service, how dare you as a customer go against our big monopoly that seeks to buy out every major ISP and cable provider in america but hey thats alright were still winning but because you left our network we will block these updates so we can further Sell your information and viewing browsing habits off to the NSA (Google TITANPOINTE tinfoil hatters!!!!) unless you want to send your phone off to one of our service centers where one of our butthurt technicians will see you rooted your phone and say it has damage and turn our free reflashing service into a paid repair and charge you through the ass for service, also did we mention were not going to update the software because our application is designed not to tell you there is an update available if you unlocked it or used our Subsidary cricket SIM in the device and didnt unlock it Or you can go on XDA and grab an odin package an potentially invalidate your warranty and then when your device comes to us for a cracked screen we can deny you the repair even though the modifcation wasnt a modifcation and has nothing to do with a cracked screen. [/SARCASM]
Anywho im going to Bite the Bullet and Grab an Assortment of AT&T contract Sims and Go Phone sims and Other Carriers, Im going to go to the local pawn shops and buy an assortment of devices and attempt to downgrade each and every single one of them back to their old original firmware versions, Dump all the FOTA updates and dump the packet captures and i guess i will have to research the possibility And be that asshole who gets sued for reverse engineering their software.

Feb Security Patch now out

The Feb 2018 Security Update is now available for our phones.
If you haven't gotten it already go to Settings->System updates and see if it's available there.
From [ZenFone 3] [180209] ZenFone 3 Zoom ZE553KL_ WW_V71.60.139.27
Update Google security patch
Enable Taiwan CHT VoWiFi functions.
Performance improved and bugs fixed.
Is there a .zip available for people with unlocked bootloaders?
kekley said:
Is there a .zip available for people with unlocked bootloaders?
Click to expand...
Click to collapse
Hi @kekley, mine is still locked so I don't have experience with that scenario here (have done with other phones but decided to leave this one stock).
The update (as zip) is here: Version WW-71.60.139.27 - ZE553KL
(Note the SKU)
This is a message from another user who has TWRP installed and still did a previous update: How to update firmware if you've already flashed TWRP
Hopefully that's enough to get you going.
koimr said:
Hi @kekley, mine is still locked so I don't have experience with that scenario here (have done with other phones but decided to leave this one stock).
The update (as zip) is here: Version WW-71.60.139.27 - ZE553KL
(Note the SKU)
This is a message from another user who has TWRP installed and still did a previous update: How to update firmware if you've already flashed TWRP
Hopefully that's enough to get you going.
Click to expand...
Click to collapse
I was referring more to the fact that the zip file for the update was not on the support page for the device until recently but thank you for going through the trouble to write this up. I'm sure it will be useful to someone. :good:
When I did a factory reset on the last firmware, MiniMovie app came back which had been removed on firmwares before. After the update to this firmware and factory reset again, MiniMovie was gone again but now they added BeautyLive. Just weird.

[OTA] Nokia 6.1 Plus (a.k.a Nokia X6, Codename DRG) Update DDLs

These update packages should work on global variant Nokia X6.
Usage:
Confirm your current version by dialing *#*#227#*#* before update.
Then download the package and rename to the specific filename I gave, place it to root directory of internal storage and dial *#*#874#*#* to update.
After the update procedure completed, update package will be deleted from your phone automatically.
Global Release:
Note: From DRG-250A build, it blocked current bootloader unlock method, be careful.
Click to expand...
Click to collapse
June 2018 to August 2018 (DRG-250A-0-00WW-B05-229D-0-00WW-B01-update.zip)
August 2018 to September 2018 (DRG-250B-0-00WW-B01-250A-0-00WW-B05-update.zip)
Android Pie November 2018 (DRG-330B-0-00WW-B01-update.zip)
Thanks for your work supporting our device!
Do you have boot image of 250A version?
izkyline said:
Do you have boot image of 250A version?
Click to expand...
Click to collapse
Yes that would be handy. I read that payload_dumper doesn't work on incremental updates. I'm still looking for ways to extract a boot.img
Hi bro I need to unlock the blltloader for my nonia 6.1 ta-1050 . If you could help me plzz
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
My nokia
DRG-250A-boot_patched.img patched with Magisk v17.1:
https://www111.zippyshare.com/v/12gKJE7u/file.html
how to update the path for x6
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
google play pretent CN OTA?
Boss,
After discuss with many other user, we think it is because I am using China version rom, but installed Google play, which pretent OTA update.
Do you think so? Could you give us a solution?
I bought the phone from ebay. I just need OTA.
yshgcs said:
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
Click to expand...
Click to collapse
Will this work on Android one varient i.e , Nokia 6.1 plus?
Do you have boot image of 250B version? I need root my device, boot September, help me
thaidaidong25 said:
Do you have boot image of 250B version? I need root my device, boot September, help me
Click to expand...
Click to collapse
Use the boot image from Nokia 7 Plus. They work. Just don't flash it, only boot it.
thanks for sharing, i just installed the pie version on my nokia 6.1 plus
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
xoxoJoelxoxo said:
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
Click to expand...
Click to collapse
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
DJBhardwaj said:
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
Click to expand...
Click to collapse
Well, that didn't do the trick, but I just simply clicked 'disable' after wiping the data and it gave me a message of "uninstalling app and installing factory camera app" which worked beautifully.
Now everything's working fine.
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
snowdance said:
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
Click to expand...
Click to collapse
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
hoatongoc said:
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
Click to expand...
Click to collapse
already installed it last night, and it work's !
thank's for the reply
Will I still receive OTA updates by HMD for my device when I check for it?
xoxoJoelxoxo said:
Will I still receive OTA updates by HMD for my device when I check for it?
Click to expand...
Click to collapse
you will, i already ask it with the support center from my country in indonesia

My phone didn't receive the Android 11 update.

According to the people on reddit it is because I have debloated my phone. I also tried to install the Pixel Experience Plus custom rom at one point but it didn't work, I did reinstall the stock recovery an relocked the bootloader after that.
I did factory reset it and even flashed it with an ozip file still no update.
also found an ofp file for the Android 11 update but relme flash tool wouldn't work with it.
Is there any other way to manually update it or force it to update?
Thanks in advance.
Do you really want it?
I think it's a bloatware dud.
The "security" is not needed and comes at a stiff price as you will see if you load it.
Scoped storage sucks.
Rule #1, if your OS is running fast, stable and fulfilling its mission... let it be.
You do make a good point.
But if it is possible and I don't like it I can always reverse to Android 10.
At this point I just want to try it out and try the Pixel Experience rom.
If it isn't, well both my phone and I will survive.
thephone.geek said:
You do make a good point.
But if it is possible and I don't like it I can always reverse to Android 10.
At this point I just want to try it out and try the Pixel Experience rom.
If it isn't, well both my phone and I will survive.
Click to expand...
Click to collapse
You can go back... as long as it doesn't update the boot loader version too.
As a Samsung user I'm all too aware of that trick.
I would investigate what advantages R has over Q that would benefit you. Scoped storage isn't fully implemented on Q apparently and seems to run as well maybe better than Pie. In Q it's scoped storage in all it's blazing cpu cycle sucking glory.
Is there anyway to do it using adb?
I got Realme 7 Pro from Amazon Warehouse with somehow broken security - figerprint scanner didn't work and the phone didn't want update itself thru OTA, even with relocked bootloader and when connected via VPN to Germany, Italy etc. It actually updated to Android 11 C23 using OTA when I changed phone's region to Singapore using the service code. Then I was still able to go back to Android 10 using OZIP file (like described in this guide), or it was also possible to flash individual img files from fastboot using adb as described here. But OTA updates and fingerprint scanner were still broken until I sent the phone to Realme service and they reflashed it completely within warranty - after that fingerprint sensor works properly and I got OTA update to Android 11 C26 right after connecting to Germany over VPN.

Categories

Resources