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
Related
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?
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
Consider one day you upset the devil and your phone is bricked by him, lets try to revive the phone from hell (at your own risk) :
Link to the OTA firmware's :
Click here for the links page
Important tools links:
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Stage 1
Download from here everything you need for the procedure - Download Folder Link
I am testing it on my BND-L21 firmware from BND-AL10
Downloading firmware (from topic). Full firmware must be more than 1.5Gb, all smaller is just
OTA Updates to the system.
After that we must download Huawei-MultiTool (future MT) version 8.x.x (link topic)
and downloading custom recovery. We will use TWRP for Honor7x (link topic)
Last we must prepare OTG Cable, SD Card more than 4Gb. On first stage that's all.
Stage 2
Go to MT and reboot phone to Fastboot mode (while phone off, hold "Volume -" and power)
If you did all correctly, you will see in the down right side your number and "Fastboot".
Now go in MT to the Bootloader and check the status. If you have already unlocked, skip this.
If you have locked phone, you must have IMEI and Huawei account. (if not please unlock your bootloader via the Huawei site)
After that, go to Recovery menu and choose our TWRP image in "Custom recovery" section and
type "Recovery". IMPORTANT!!! DON'T FLASH ERECOVERY, I DON'T HAVE THIS IMAGE!!!
After flashing recovery, we must turn off our phone.
Now we must to prepare base system image. In archive we have UPDATE.ZIP file. extract this
file to custom folder and open "Unbrick" in MT and choose "extractor". Open our file in extractor
and click right mouse key on empty space, choose extract all... and choose custom folder to
extracting.
Go to the folder and copy file VENDOR.IMG to the SD-Card (or USB with OTG). Turn on your
device in Recovery mode (Volume + and power), choose Wipe and Wipe ALL partitions! After
doing this, go to Install and choose "Install img", go to the SD-Card, and install VENDOR.img to
VENDOR folder (Important!)
After installing reboot phone again to Fastboot mode and connect to PC.
Now we must download .zip update to your region. We need this for using LTE (4G) in your country + Localization.
After downloading open .zip archive with our CUST file. archive must be called update_BND-
YOUR-NUMBER_hw_YOUR- COUNTRY.zip
From this archive we must extract .img file from root folder. It can be called cust.img CUST.img
version.img etc.
if name different from CUST.img rename it and put to the extracted UPDATE.app folder.
Last Stage 3
In MT go to Unbrick, choose our unpacked system with our CUST file and we must have at least
4/5 checkbox. And just type "UNBRICK" and wait. NOTICE: at moment of extracting system.img
it will be about 10-15 minutes. It's not a freezing of PC)
After good installing in log you will see like "All ok" Just reboot phone and you will see low level
factory reset, or something else like formatting. After formatting phone will reboot to the system.
That's all
Flashing Gapps method coming soon...
Password - 4pda for the update_full_bnd-AL10... Zip
Special Thanks to Kallibr44 my friend who helped me decipher everything. :highfive:
HIT THANKS IF I HELPED YOU IT MAKES ME HAPPY
We need a Full Firmware Package for L21,this is only Ota Updates.
letschky said:
We need a Full Firmware Package for L21,this is only Ota Updates.
Click to expand...
Click to collapse
there is a procedure used by EU users to completely revive the phone using the OTA but the procedure is too long which i haven't tried yet and is completely for users who have dead phones for now and yes obviously there is no official firmware available for Honor 7x but the user from an EU forum revived his phone so it is possible from the images.
though i made this thread for users who want to update their firmwares and not the procedure to flash a stock firmware since there is not one available yet but i can point to the thread where this user posted the procedure if someone wants to try. PM me
sid21 said:
i can point to the thread where this user posted the procedure if someone wants to try. PM me
Click to expand...
Click to collapse
Yes please....
fmotta said:
Yes please....
Click to expand...
Click to collapse
Sent reply.
There are teams who have unlocked a lot of stuff like flashing international FW,
flashing gapps on chinese fw, Automatic Call Recording, restoring the phone.
so i am in contact with them to make our phone better. lets keep our fingers crossed. :fingers-crossed:
i am waiting for firmware flashing to get it translated from one of the users.
This is the full recovery package right? Atleast for the Indian version?
TheDj408 said:
This is the full recovery package right? Atleast for the Indian version?
Click to expand...
Click to collapse
They arent recovery packages. they are full OTA which can be flashed for updating.
but there is a process to compile them into making them stock firmware packages but due to the long procedure i didnt post it here. rather wait for official stock firmware package.
sid21 said:
Hello Honor 7X Users, turns out there is firmware available for flashing for the AL10 and L21 variants
but i haven't tried them out and can post the procedure if someone needs it but all credit goes to PRO-TEAMMT for releasing them for us so now if we mess up we got official firmware's latest available to go back to.
I personally haven't tested any but i soon will.
Link to the firmware's :
Click here for the links page
Important tools :
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Steps : (Considering you have unlocked bootloader and flashed twrp)
1. Download the appropriate firmware as per your model (Link to the website given)
2. Clear Cache
3. Flash the firmware file
(Wait for the complete process to flash a firmware from scratch so that i can do it and confirm myself but if anybody tests before me let me know)
Refer to the thread by inside!out for any help till them if you want to try out
Click to expand...
Click to collapse
Hi
I am a New in Android world
I have honor 7x BND L21c185b101
And i rooted
Know exactly do this?
Step 3 how?
And the multi tool For what?
sid21 said:
there is a procedure used by EU users to completely revive the phone using the OTA but the procedure is too long which i haven't tried yet and is completely for users who have dead phones for now and yes obviously there is no official firmware available for Honor 7x but the user from an EU forum revived his phone so it is possible from the images.
though i made this thread for users who want to update their firmwares and not the procedure to flash a stock firmware since there is not one available yet but i can point to the thread where this user posted the procedure if someone wants to try. PM me
Click to expand...
Click to collapse
Can I have the procedure link?
I ordered a 7X from AliExpress.
I also own an Honor 5X & errrmmmm.. I'm not a developer rather still a learning buildbot ? still I want to take part in bringing up LOS or AOSP for Honor 7X. So we can work on it together if you want. ?
Cheers!
P.S. Belated Merry Christmas.
tootysa said:
Hi
I am a New in Android world
I have honor 7x BND L21c185b101
And i rooted
Know exactly do this?
Step 3 how?
And the multi tool For what?
Click to expand...
Click to collapse
exactly what you want to do?
this is to update to the latest firmware. if you have the latest firmware you dont need it.
the multi tool is used to flash stock with a procedure which is only needed to return to stock or else theres no need for it for the most part..
mumith3 said:
Can I have the procedure link?
I ordered a 7X from AliExpress.
I also own an Honor 5X & errrmmmm.. I'm not a developer rather still a learning buildbot ? still I want to take part in bringing up LOS or AOSP for Honor 7X. So we can work on it together if you want.
Cheers!
P.S. Belated Merry Christmas.
Click to expand...
Click to collapse
PM Sent kindly check.
sid21 said:
Hello Honor 7X Users, turns out there is firmware available for flashing for the AL10 and L21 variants
but i haven't tried them out and can post the procedure if someone needs it but all credit goes to PRO-TEAMMT for releasing them for us so now if we mess up we got official firmware's latest available to go back to.
I personally haven't tested any but i soon will.
Link to the firmware's :
Click here for the links page
Important tools :
[TOOL] Huawei Multi-Tool v8 by Team MT by inside!out
TWRP Honor 7X img
Steps : (Considering you have unlocked bootloader and flashed twrp)
1. Download the appropriate firmware as per your model (Link to the website given)
2. Clear Cache
3. Flash the firmware file
(Wait for the complete process to flash a firmware from scratch so that i can do it and confirm myself but if anybody tests before me let me know)
Refer to the thread by inside!out for any help till them if you want to try out
Click to expand...
Click to collapse
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english?)
PLEASE HELP ME??
Thanks
Lambo™ said:
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english?)
PLEASE HELP ME??
Thanks
Click to expand...
Click to collapse
1) ???
2) Not sure there is always a chance of bricking
3) Yes, if you don't know what you're doing. No if you're not going to be flashing anything.
4) You should be able to and also refer to #1.
5) None available
6) None available
7) You can't, no stock image released = no procedures to unbrick
Soapy! said:
1) ???
2) Not sure there is always a chance of bricking
3) Yes, if you don't know what you're doing. No if you're not going to be flashing anything.
4) You should be able to.
5) None available
6) None available
7) You can't, no stock image released = no procedures to unrbcik
Click to expand...
Click to collapse
1- can i upgrade the system at every update (when the device is rooted) with Firmware finder many times even if I don't recive the notification on the phone of the update (or if the device updater cannot find it)?
2-ok but if do all right steps you cannot brick the phone, no?
3-ok i only wanna unlock bootloader, flash twrp and root the phone. If I do all right steps there are no risks, no?
4-i don't understand it (in hisuite there s the option that says "Update device". With the device rooted can I update the phone with this software?)
5-ok but can I do one with a custom recovery, no?
6-ok so we just have to wait, no?
7-ok. Same thing of the - 6 (we have to wait for the UPDATE.APP for the 7x to be able to UNBRICK the phone in case it could happen, no?)
Sorry for my bad English and thanks for the answers?
Lambo™ said:
HI I wanna know many things:
1-if I can constantly update the 7x with the application (or the software on PC, is the same) "Firmware Finder" even if I don't recive the official OTAs (because I want to root my device)
2-if its possible upgrade the system via OTA (or Firmware finder etc...) when the device is rooted
3-is dangerous root the Honor 7x?
4-if I can upgrade the system when the device Is rooted via the software HiSuite
5- how/where can I do/find and restore a Nandroid Backup for my phone
6-where I can find a local/manual update (UPDATE. APP) for the 7x (in case a brick the phone)
7-how can i UNBRICK my phone I case of brick
(sorry for my bad english)
PLEASE HELP ME
Thanks
Click to expand...
Click to collapse
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
sid21 said:
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone [emoji14] since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
Click to expand...
Click to collapse
Thanks lol [emoji23]
Sent from my BND-L24 using Tapatalk
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
GC95 said:
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
Click to expand...
Click to collapse
I have a TWRP backup not sure if it'll work, https://drive.google.com/file/d/1EntdgNwcJSOTZizqt_W-yWfkd3-YVmCm/view?usp=drivesdk
It's a zip file with 2 backup folder, one with boot and system and one with vendor
Edit: pls thank if it worked, so I have an indicator of the effectiveness
GC95 said:
I rooted my 7X(Al10) version successfully but while performing the reset, deleted the system file also by mistake. There is no TWRP backup. Is there any way to get the stock OS files again to flash in TWRP ? Or does anyone have a backup file they made that they can share? I tried Huawei e-recovery too, but that gets stuck at 'unable to get package info'. The people at the service centre can't think of any other method to restore the phone, except changing the motherboard. When is the official stock file expected to be available?
Click to expand...
Click to collapse
I am waitinig for the official stock file since two weeks now, because I deleted accidently the OS from my phone -_-
I think we can wait several weeks again...
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
Jan.Pul said:
I have a TWRP backup not sure if it'll work, https://drive.google.com/file/d/1EntdgNwcJSOTZizqt_W-yWfkd3-YVmCm/view?usp=drivesdk
It's a zip file with 2 backup folder, one with boot and system and one with vendor
Click to expand...
Click to collapse
Thanks! I will try on my bricked phone
sid21 said:
1. yes you can if the app supported honor 7x with their firmware but it doesn't yet, use twrp
2. yes you can upgrade via flashing it in twrp
3. unlocking bootloader itself is dangerous let alone rooting since your waranty is gone since there is still no sign of official stock firmware
4. same as no. 1 ans
5. if u flashed twrp you can do your nandroid backup which can be later restored anytime so it will be obv on the phone at that time
6. manual or local update? in the op main post i guess? by opening the link?
7. Still no official firmware and the procedure i am aware of consists of turning the official chinese firmware into normal by changing settings and stuff which is a long procedure so probably if u brick, u r stuck until honor decides to release stock firmware
by the looks i guess you have no clue about phone flashing, its better you dont try anything until there are guides properly made for newbies. :silly:
Click to expand...
Click to collapse
1. In the app firmware finder there are firmwares for the phone but how can I flash a official firmware (OTA I mean) if there are no one (or how can I flash a firmware finder Update)?
2. Same thing in -1 (I mean)
3. Ok. Now we have to wait the official stock firmware, no? (i don't understand this answer, please write it in another way)
4. I don't understand it
5. Okok (obv? Sorry I'm Italian hahaha)
6. It's not the same thing local or manual? Write it in another way please hahaha google translate doesnt help me?
7. Okok, So if I don't use your method I only have to wait that honor release the official stock firmware (UPDATE. APP). And for greater security it's better wait it before to root and unlock bootloader etc, no?
Anyway, I have an idea of what flashing is, in fact every device I have (they are all Samsung, so that's why I'm disoriented) is completely modified. The fact is that I dont have much experience (I'm 14 years old) with non-Samsung devices, in fact my honor 7x I received for Christmas and for the hurry and the want to modify it, I would like to know all these things.
Thank you
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
k0pernicus said:
I am waitinig for the official stock file since two weeks now, because I deleted accidently the OS from my phone -_-
I think we can wait several weeks again...
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
Thanks! I will try on my bricked phone
Click to expand...
Click to collapse
OK thanks I'll keep it aside in case of brick
I would recommend everyone to not do experiments over your phone to try and root and flash random stuff..
they only have official chinese firmware for flashing so its better to wait for the official firmware for non chinese version.
the method which i know of to flash on the phone is for people with flashing knowledge cz the procedure is not simple and secondly even i have been flashing my phone for many years on various devices yet i havent got the guts to root this first honor device cz their partitions are different and somewhat secured so dont play with it.
wait for the official firmware for your respective devices. maybe they will straightaway launch the oreo firmware.
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your … .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?
Hi everyone,
I recently bought a Tencent edition of the ROG Phone 2, and was a bit annoyed to see that automatic system updates no longer worked after converting it to a WW ROM. I did some digging and found out that ASUS uses the IMEI of the device to track what updates the device is entitled to, including the region. So a CN IMEI would only be entitled to CN firmware updates.
That's what led me to write this app that interacts directly with the ASUS servers to look for updates, but using a spoofed IMEI that makes the server think it's WW. It was a bit of work to figure out how it all works, but I have managed it, and it seems to work as it should - I successfully upgraded from .44 to .64 just a short while ago using the app.
Download
v1.0.4:
- Allow input of custom IMEI
- Fix issues on Android 10 beta
- Other fixes
https://github.com/HomerSp/AsusUpdater/releases/download/v1.0.4/AsusUpdater-v1.0.4.apk
v1.0.3:
- Enable downloading updates via mobile data
- Several UI fixes
https://github.com/HomerSp/AsusUpdater/releases/download/v1.0.3/AsusUpdater-v1.0.3.apk
v1.0.2:
- Fix updates not working when on CN fingerprint (for real this time)
https://drive.google.com/open?id=1IgDM9T6u4z4LLLudHYIg3hb6OPw7Qz29
v1.0.1:
- Fix updates not working when on CN fingerprint
https://drive.google.com/open?id=1_hYwPi3Q_8tW6gaBnQvNmohWR4Q4wP2o
v1.0:
- Initial release
https://drive.google.com/file/d/1KVh8OmgMxMg-jQfpF2LmIW4cqBDKXtyz/view?usp=sharing
Instructions
The app is very basic, but it does what it should. It will check for updates every hour, and send you a notification if it has found an update - or you can force a check by opening the app and pressing the button.
Once the update is downloaded (the updater will notify you when it's done), you will need to restart the device, and upon booting again you will be notified by the system that a system update has been found and be asked if you want to apply it or not.
That's really it, the system will handle the updating from there.
Note 1:
You need to be on completely stock firmware for the update to apply properly. The bootloader can be unlocked, but you can't be rooted or such.
Note 2:
For the updater to work correctly you'll have to allow it to auto-start by going to System settings -> Battery -> PowerMaster -> Auto-start manager and make sure ASUS updater is ticked. Not doing this means you will have to run the app once each boot for notification to work correctly.
Note 3:
If the update fails (after rebooting and starting the update), I will need a log to be able to figure out what's wrong. The relevant tag is UpdateLauncher.
Source code:
AsusUpdater - Github
Do let me know if it's working for you, or if you can think of any improvements I can make.
Wow great work mate I will download the app when the next update will be available.
I wish you can develop something for volte and vowifi.
avivv said:
Wow great work mate I will download the app when the next update will be available.
I wish you can develop something for volte and vowifi.
Click to expand...
Click to collapse
+1 for VOWIFI
Sent from my ASUS_I001DE using Tapatalk
---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------
Hope you can get some more app for our lovely ROG 2 like this. Keep it up...
Sent from my ASUS_I001DE using Tapatalk
This is awesome and quite helpful! I appreciate your time and effort in making this!
HomerSp said:
Hi everyone,
I recently bought a Tencent edition of the ROG Phone 2, and was a bit annoyed to see that automatic system updates no longer worked after converting it to a WW ROM. I did some digging and found out that ASUS uses the IMEI of the device to track what updates the device is entitled to, including the region. So a CN IMEI would only be entitled to CN firmware updates.
That's what led me to write this app that interacts directly with the ASUS servers to look for updates, but using a spoofed IMEI that makes the server think it's WW. It was a bit of work to figure out how it all works, but I have managed it, and it seems to work as it should - I successfully upgraded from .44 to .64 just a short while ago using the app.
Download
https://drive.google.com/file/d/1KVh8OmgMxMg-jQfpF2LmIW4cqBDKXtyz/view?usp=sharing
Instructions
The app is very basic, but it does what it should. It will check for updates every hour, and send you a notification if it has found an update - or you can force a check by opening the app and pressing the button.
Once the update is downloaded (the updater will notify you when it's done), you will need to restart the device, and upon booting again you will be notified by the system that a system update has been found and be asked if you want to apply it or not.
That's really it, the system will handle the updating from there.
Note 1:
You need to be on completely stock firmware for the update to apply properly. The bootloader can be unlocked, but you can't be rooted or such.
Note 2:
For the updater to work correctly you'll have to allow it to auto-start by going to System settings -> Battery -> PowerMaster -> Auto-start manager and make sure ASUS updater is ticked. Not doing this means you will have to run the app once each boot for notification to work correctly.
Do let me know if it's working for you, or if you can think of any improvements I can make.
Click to expand...
Click to collapse
Hats off for you Senior.
I'm on WW_ZS660KL-16.0622.1906.19-0, was never able to update this phone that I imported from China to EU, and your tool doesn't find new updates available to install either. Could it be that I'm on ww firmware but cn fingerprint? (seller's doing, not mine). I'm 100% on stock everything (meaning, I haven't tinkered with the software one bit). Would appreciate some clarification, thank you.
Juraviel said:
I'm on WW_ZS660KL-16.0622.1906.19-0, was never able to update this phone that I imported from China to EU, and your tool doesn't find new updates available to install either. Could it be that I'm on ww firmware but cn fingerprint? (seller's doing, not mine). I'm 100% on stock everything (meaning, I haven't tinkered with the software one bit). Would appreciate some clarification, thank you.
Click to expand...
Click to collapse
As it turns out, the CN fingerprint does affect it; I didn't think it would, but one of the props that the app uses to send to the server actually changes based on the fingerprint.
I've fixed it, so please try this, and let me know if it works:
https://drive.google.com/open?id=1_hYwPi3Q_8tW6gaBnQvNmohWR4Q4wP2o
For me it's the same, unfortunately. Not sure what I could be doing wrong.
Juraviel said:
For me it's the same, unfortunately. Not sure what I could be doing wrong.
Click to expand...
Click to collapse
Sorry, I had completely missed another reference to the CN fingerprint. Try this latest one (tested and working for me with fingerprint changed to CN):
https://drive.google.com/open?id=1IgDM9T6u4z4LLLudHYIg3hb6OPw7Qz29
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Just change the fingerprint to WW, having a WW rom with CN fingerprint will cause more issues.
Juraviel said:
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Click to expand...
Click to collapse
A log would say what's wrong, most likely one of the partitions isn't completely stock - they probably botched something when they flashed the WW ROM on it. Feel free to send me a log and I can have a look.
avivv said:
Just change the fingerprint to WW, having a WW rom with CN fingerprint will cause more issues.
Click to expand...
Click to collapse
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Juraviel said:
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Click to expand...
Click to collapse
Juraviel said:
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Click to expand...
Click to collapse
Sure you can, it's easy just follow this guide, no need to root or to wipe and it takes 5 minutes
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
Juraviel said:
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Click to expand...
Click to collapse
I would indeed recommend changing the fingerprint to WW as having a CN fingerprint causes a whole bunch of issues, although that most likely won't fix your upgrade issue. The EDL method is really easy, and can be done in a couple of minutes - and does not require rooting.
As for the log, have you used adb and such? I just need a logcat. There are plenty of guides on how to do that, so I won't go into that here.
You were right it was fairly easy, although the original tutorial should have a warning that entering in edl mode causes the screen to go black and the phone completely unresponsive! Other than that it went smooth. You did an amazing job.
Edit: well, actually, it still fails I'll keep at it
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
---------- Post added at 10:41 PM ---------- Previous post was at 09:45 PM ----------
kashif31 said:
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
Click to expand...
Click to collapse
Nvm there was an error with the file which was downloaded by your app .. i download the file again n it worked
kashif31 said:
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
---------- Post added at 10:41 PM ---------- Previous post was at 09:45 PM ----------
Nvm there was an error with the file which was downloaded by your app .. i download the file again n it worked
Click to expand...
Click to collapse
If you get this again I would need a logcat to be able to help you. The update dialog you see on reboot isn't from my app, but it's a system app that I have no control over - so there's no way of telling what's causing it to fail, except for a log.
HomerSp said:
If you get this again I would need a logcat to be able to help you. The update dialog you see on reboot isn't from my app, but it's a system app that I have no control over - so there's no way of telling what's causing it to fail, except for a log.
Click to expand...
Click to collapse
How to open logcat
Thanks so much for this app, I was thinking I would just need to apply the updates manually as they came out. It doesn't seem to be downloading the update when I tap the button though, my data usage stays in the KB/s range or lower. Anything I might be doing wrong?