[Solution] How to get system status : modified to official - Moto G5S Questions & Answers

This is the method how I fixed my mobile to get the system status: modified to official
1.Unlock the bootloader
2.download the ZUI from the link given below
https://mega.nz/#!OsRACb7J!-5mVSoCfkx053SMHd5UkpQ4hHULkLjanH_NiIe8PCoo
3.install this ROM the process for installation is given by @rssxda
Just remove bootloader.img command from the comands or from the extracted
folder of the ZUI rom
4.change the language from Chinese to English by the process given below
https://youtu.be/_YWulrud9A4
5.go to about phone and check for system updates and u should get an
update download The update and install it
6.after installation of the update u software status will be charged to official
NOTE:Until and unless u get a OTA and install it
Ur bootloader status doesn't change
(Note: The main reason it gets to modified is rooting ,if u root Ur mobile the software status is changed to modified
And my software status has been modified because of flashing stock ROM lite root)
That's it now u have successfully fixed Ur problem
If u have fixed it then appreciate my work
Thanks to. @mr_patel031
@xda developers
@Nicolas36
@lohanbarth
@bycabraljr

Talwar sridhar said:
This is the method how I fixed my mobile to get the system status: modified to official
1.download the ZUI from the link given below
http://corneey.com/wgCfW6
2.install this ROM the process for installation is given below
http://ceesty.com/wgKBUx
3.change the language from Chinese to English by the process given below
http://ceesty.com/wgKNGP
4.go to about phone and check for system updates and u should download
The update and install it
5.until and unless u get a OTA and install it
Ur bootloader status doesn't change
(Note: The main reason it gets to modified is rooting ,if u root Ur mobile the software status is changed to modified)
That's it now u have successfully fixed Ur problem
If u have fixed it then appreciate my work
Thanks to. @mr_patel031
@xda developers
@Nicolas36
@lohanbarth
@bycabraljr
Click to expand...
Click to collapse
Looks like this rom is out of date... the June patch stock I installed refuse to flash ZUI rom...

michael50310 said:
Looks like this rom is out of date... the June patch stock I installed refuse to flash ZUI rom...
Click to expand...
Click to collapse
It's out of date it should be updated

The main reason for system modified is flashing Montana lite root stock ROM it making system status to modified

michael50310 said:
Looks like this rom is out of date... the June patch stock I installed refuse to flash ZUI rom...
Click to expand...
Click to collapse
Even though it's out of date but it's working

How to instll this rom using adb or twrp
I want to try your rom

Related

Rom-Assaye-Rooted-14.1.G.2.257

Introducing
ROM-Assaye-V3.0.0
[Stock based-14.1.G.2.257] [C6903][Unlocked and Locked Bootloaders]
​
No claims, no nonsense, this is just a rom for people who want the latest stock rom with root and want a trusted source.
This is just made from dsixda's Android Kitchen and I hesitate to call it development. [MOD's, if you think it should be moved, feel free] Its just something I did and thought I should share​Feedback is actively encouraged​
Features
Based on [STOCK FIRMWARE][C6903]14.1.G.2.257-Vodafone-UK
Added SuperSU Credit Chainfire
All apk's zipaligned
Wishlist
Include dual recovery in ROM (CMW, TWRP and Philz recovery)
Deodex system
New bootanimation
New offline charging images
Installation for Locked Bootloader
Ensure you are on 14.1.G.1.534 firmware (Or another that can be rooted and have recovery installed)
Root it and install dual recovery
Enter CMW and factory reset, wipe cache and dalvik.
Flash the ROM. The .zip file from the download section. Or from here
DO NOT REBOOT
Flash supersu zip from here
DO NOT REBOOT
Goto advanced in recovery and choose power off.
Flash this file in flashtool. ENSURE YOU HAVE TICKED TO EXCLUDE SYSTEM
Reinstal recovery
Known Bugs and Fixes (If applicable)
Code:
How to Report Bugs
Answer these questions.
1. Which version of the ROM did you download? Please provide the download link.
2. Are you on a locked or unlocked bootloader?
3. Which kernel are you on?
4. Have you flashed anything else, or is the bug coming from a CLEAN install of this ROM?
5. What are the symtpons of the bug?
6. How can I reproduce the bug?
7. Can you provide a logcat?
8. Any other comments that might help me or others to help you.​
Credits
@[NUT] for dual recovery and always answering questions
@DooMLoRD for everything
@nvphuong for install instructions
XDA:DevDB Information
ROM-ASSAYE, a ROM for the Sony Xperia Z1
Contributors
gregbradley
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: 14.1.G.2.257
Version Information
Status: Stable
Stable Release Date: 2013-10-30
Created 2013-10-30
Last Updated 2013-10-31
Reserved
Reserved
Another one
Last one
Nice to see another ROM, ty.
tiunilohmu said:
Nice to see another ROM, ty.
Click to expand...
Click to collapse
Thanks,
File is now uploaded and in the download section
EDIT
There seems to be a problem ATM. There are links to the mega site where the .zip is in the instructions, but I will try and reupload to the xda server again later tonight
You messed something mate.
You said - flash ROM via CWM but you provided ftf file so I guess there's no need for that step or?!
It would mean we should flash ROM two times, from CWM and from flashtool....?
Sent from my C6903 using Tapatalk
---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------
Great idea, I really need stock, unchanged 257 firmware (rooted) but please, fix this or give us proper instructions.
Tnx
EDIT:
On PC download links are visible
tnx
Sent from my C6903 using Tapatalk
Thanks for the replies and the interest.
1) There is a link to the download in the download section at the top of the project. See the screen shot. However the .zip file can also be found here
2) The instructions are correct. You have to flash the .zip in recovery and root it using the superSU .zip. Then before rebooting flash the 257 ftf to install the 257 kernel etc. You exclude system because you want to keep the rooted system you just flashed in recovery. The ftf has to be flashed in flashtool.
3) Anyone can flash the ftf from any region. If you want to keep your basedand etc, then just exclude system and baseband in flashtool. If you want to flash a FTF of your region though you can flash any FTF and just exclude system.
4) I am currently uploading a direct link to the rom in the download section.
Recovery for locked bootloaders is not included to rom? I have to install recovery again after flashing?
POWER1FM said:
Recovery for locked bootloaders is not included to rom? I have to install recovery again after flashing?
Click to expand...
Click to collapse
Yes. I have made this as stock as possible for people. I will start including more in the next release.
But you can download dual recovery from here and reinstall it
OK, I have put a link in the instructions and also in the post a few above this one.
I will work on the download section as well.
gregbradley said:
OK, I have put a link in the instructions and also in the post a few above this one.
I will work on the download section as well.
Click to expand...
Click to collapse
Thank you for this good idea of rooted stock. I am on 6902 , How can I proceed please ? Are you preparing same for 6902 ? )
hovnovice said:
Thank you for this good idea of rooted stock. I am on 6902 , How can I proceed please ? Are you preparing same for 6902 ? )
Click to expand...
Click to collapse
I will see what I can do if you send me a link to a FTF for the C6902.
gregbradley said:
I will see what I can do if you send me a link to a FTF for the C6902.[/QUOTE
Thank you for trying , here is the link : https://mega.co.nz/#!6pBlCZLa!Jl4QLU9lHTUPeHJzqTuQt03-EGFSReLHVMivYJKobMA
Click to expand...
Click to collapse
Hi. This is based on a Vodafone ROM so will it have Voda stuff in it if I flash or will it be generic?
ozgadgetguy said:
Hi. This is based on a Vodafone ROM so will it have Voda stuff in it if I flash or will it be generic?
Click to expand...
Click to collapse
yes, but you will have rooted rom, so you can uninstall it.
I will provide a bloatfree rom soon, but ATM people are after a stock rom with root so that is what I have provided.
In a few days it will be deodexed, bloatware free, etc etc/..
Error
When I flashed it, I got a status 7 error of some sort, just after that, I re-flashed it and it worked perfectly fine until it came time to boot the phone, I followed the instructions given thoroughly multiple times and came out with the same error again and again.
ChrisFirerabbit said:
When I flashed it, I got a status 7 error of some sort, just after that, I re-flashed it and it worked perfectly fine until it came time to boot the phone, I followed the instructions given thoroughly multiple times and came out with the same error again and again.
Click to expand...
Click to collapse
strange, status 7 is to do with the updater script, but it worked fine for me. Also, what exactly happened when you came to reboot the phone?
Can I ask what version of recovery you have installed?
gregbradley said:
strange, status 7 is to do with the updater script, but it worked fine for me. Also, what exactly happened when you came to reboot the phone?
Can I ask what version of recovery you have installed?
Click to expand...
Click to collapse
Oh, sorry about that, forgot to finish that part, I was basically stuck in a bootloop, but I was able to fix it. Here is the recovery I used http://forum.xda-developers.com/showthread.php?t=2455959&page=9

[GUIDE] OTA Update Rootet(Magisk) H6X (Honor 6X)

I had trouble updating my Honor 6X (BLN-L21) after I rooted it, so I searched the whole xda to gain some information. Finally I made it, so I thought I could share this information with you guys, hope it helps, but I do not take responsibility if not, as you may have already heard, the Honor 6X (like every Kirin device) is very easy to brick.
- If everything is gone alright you should keep all of your data, apps and settings.
- If there is a big update, like from MM to N you maybe should backup all your stuff and relock the bootloader to update (big updates can relock frp so you can't unlock your bootloader then a rollback is the only way.
Successfully tried from:
B360 to B365
B365 to B367
Short Version (for expert users):
1. uninstall busybox bynaries and the Xposed Framework
2. uninstall magisk (inside the app)
3. flash stock recovery.img (of your actual firmware)
4. flash stock boot.img (of your actual firmware)
5. make OTA update (Reminder: safe update file)
6. flash twrp again and root
7. you are all done
Detailed Version:
#cmd commands#
1. backup your system over TWRP #adb reboot recovery# and do a backup there (for safety reasons)
2. #fastboot reboot#
3. uninstall busybox bynaries and the Xposed Framework(not just the app) (if you have it)
4. uninstall magisk (in app over "complete Uninstall button")
5. restart to bootloader #adb reboot bootloader#
6. flash stock recovery #fastboot flash recovery recovery.img# [use the recovery out of your actual firmware, how to extract is explained in the Forum I added at the end
7. flash stock boot #fastboot flash boot boot.img# [also use the extracted version of your actual package]
8. #fastboot reboot#
9. download update over OTA Update app (System update) in stock system. -> If the "System updater" app does not provide a Full version of the update package, the update could get stopped at 8% saying it could not verify the update, if so, just take the step to the error and reboot, if you then search for an update again, the "System updater" should now show you a Full version of the update package. like "BLN-L21C432B365-FULL"
10. you should safe that update files out of the HwOUC folder, so you can extract the recovery.img and boot.img later before you restart your device to do the update, because the system deletes these files after successful update
11. update over OTA Update app (System update) in stock system
12. restart to bootloader (#adb restart bootloader#)
13. flash twrp again #fastboot flash recovery twrp-3.1.1-0-berlin.img# [use the OpenKirin twrp edition (the official leads to a bootloop] -> [url]https://forum.xda-developers.com/honor-6x/development/twrp-t3583413[/URL]
14. Important is not to boot to system after flashing TWRP, exactly like as you installed it the first time. So you do #fastboot reboot# and then Vol down + lock
15. backup your system over TWRP (for safety reasons)
16. #adb reboot recovery#
17. flash Magisk zip in TWRP again
18. reboot in twrp
19. you are ready to go with the latest stock rom​
How to extract boot.img and recovery.img out of your actual firmware is explained here:
[url]https://forum.xda-developers.com/honor-6x/how-to/extract-stock-recovery-img-boot-img-img-t3676880[/URL] thanks @Khan ubaid​
citizenserious said:
the Honor 6X is very easy to brick.
Click to expand...
Click to collapse
Not just the 6X but every Kirin device.
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
RedSkull23 said:
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
Click to expand...
Click to collapse
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
citizenserious said:
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
Click to expand...
Click to collapse
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
RedSkull23 said:
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
Click to expand...
Click to collapse
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Thank for this guide. I might use this when an update comes.

			
				
[email protected] said:
Click to expand...
Click to collapse
What's the matter?
citizenserious said:
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Click to expand...
Click to collapse
Finally i found some time to dedicate on updating my phone, and I'm happy to say that it worked. I made from B360 to B365 and from B365 to B367, both worked at first shot. The only thing that i just can't understand is why the OTA package downloaded yesterday worked immediately, while the same B365-FULL package downloaded a month ago, copied on PC before starting it and later started didn't. With stock recovery and boot images obviously. I tried to start it later but nothing, i tried dload method with the update.app but neither that worked. Probably the OTA downloaded creates a sort of signature that can't be recreated that easily, if the same package fails through dload method... But what matters most is that now I'm on B367, protected with the latest security patch. Sorry for the late answer, time is hard to find... Thanks
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Archerous said:
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Click to expand...
Click to collapse
B367 of which model BLN-LXXCXXX?
shashank1320 said:
B367 of which model BLN-LXXCXXX?
Click to expand...
Click to collapse
I forgot sorry
BLN-L21C432B367
Archerous said:
I forgot sorry
BLN-L21C432B367
Click to expand...
Click to collapse
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
shashank1320 said:
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
Click to expand...
Click to collapse
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Archerous said:
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Click to expand...
Click to collapse
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
I share ist,with the next update :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
If we find the B367 package I'll upload everything from it!
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Update: recovered with the official rollback software to 6.0.
shadowcliffs said:
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Click to expand...
Click to collapse
You can try full firmware for b365 if available via dload.
Unlock your bootloader and it will boot to twrp and then boot normally.

bootloader stock zip required to flash through twrp(need to go back to seslinux enfor

I flashed a modified bootloader to use magisk with oos as it forced seslinux to premissive
now i need to go back to stock bootloader
can anyone provide me zip for the stock bootloader so i can flash it throught twrp
the modified bootloader thread
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
the mordified bootloader zip file is in the download links ->magisk 14.3 zip-> oneplus_bootloader.zip
this might also help
https://www.xda-developers.com/onep...ng-of-selinux-to-permissive-mode-in-fastboot/
file also attached mordified bootloader
indroider said:
I flashed a modified bootloader to use magisk with oos as it forced seslinux to premissive
now i need to go back to stock bootloader
can anyone provide me zip for the stock bootloader so i can flash it throught twrp
the modified bootloader thread
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
the mordified bootloader zip file is in the download links ->magisk 14.3 zip-> oneplus_bootloader.zip
this might also help
https://www.xda-developers.com/onep...ng-of-selinux-to-permissive-mode-in-fastboot/
file also attached mordified bootloader
Click to expand...
Click to collapse
Simply dirty flash the ROM.
tnsmani said:
Simply dirty flash the ROM.
Click to expand...
Click to collapse
Its not wot m looking for.. Bootloader will not go enforced by its own . so.. Looking for bootloader stock zip
Hoping it's not too late: have you looked there?
Simone98RC said:
Hoping it's not too late: have you looked there?
Click to expand...
Click to collapse
No boot loader there
Just firmwares n boot logos
Still thanks for trying
indroider said:
No boot loader there
Just firmwares n boot logos
Still thanks for trying
Click to expand...
Click to collapse
Sure? You're wrong: the mentioned link include only bootloader+modem that are coming with every OOS release.
There's no system partition, because that packages are built for custom rom users.
I used them for a long time, until I went back to modded stock.
Ps also full firmware include bootloader+modem partitions, otherwise you would get in hard brick especially with major updates.
Are you referring to a particular partition? What you mean for firmware?
Simone98RC said:
Sure? You're wrong: the mentioned link include only bootloader+modem that are coming with every OOS release.
There's no system partition, because that packages are built for custom rom users.
I used them for a long time, until I went back to modded stock.
Ps also full firmware include bootloader+modem partitions, otherwise you would get in hard brick especially with major updates.
Are you referring to a particular partition? What you mean for firmware?
Click to expand...
Click to collapse
Yes they do include that bootloader img i have tried flashing multiple boot images but i used a bootloader zip from. A dev that changed the setting of my selinux of bootloader from enforced to permissive in order to use magisk 14.2 with oos as magisk earlier didnt support enforced state.... That is only poossible to replace when you have a bootloader zip that include instructions to do so .. So the default bootloader zip will have that instruction as default values
Did you find any solution?
theo.j22 said:
Did you find any solution?
Click to expand...
Click to collapse
Yes just flash community beta of pie n bootloader will be updated to stock settings

[DISCONTINUED]Stock ROM VER:WW-15.0410.1803.51_ROM 4/12 Update TWRP Flashable!

Hey guys since i dint see any stock roms here, i decided to make one thats possible to flash from twrp, its 100% stock nothing added nothing taken from original rom, no firmaware files in rom zip.
I have the the US Asus Zenfone 4 pro , tested ONLY ON THIS DEVICE DO NOT FLASH IT ON ANY OTHER ZENFONE YOU HAVE BEEN WARN!!
How to Flash:
1.Unlock Bootloader Via Official App
2.Flash TWRP
3:Swipe to allow modifications to system VERY IMPORTANT! flash noverity.zip just incase you get stuck in a bootlooop.
4lace zip on your sdcard/internal Storage
5:Wipe Data/System
6:Flash rom zip (Ignore "unknow command error" after flashing, i need to cleanup the update script )
7.Reboot to system
I followed these step and rom flashed fine.
I might try and do some other things with this phone, be advised i haven't tinker with android in a very very long time.
ROM Download LINKS:
OREO-WW-15.0410.1803.51.zip
Change log:
1.Security patch update
2.Improve touch sensitivity
3.Fix launcher home page folder cannot be changed
4.Fix play to/MI Box porject not full screen issue
5.Fix randomly auto reboot issue
6.Fix status bar icon to show more obviously
7.Fix audio issue in 3rd party APPs
OREO-WW-15.0410.1802.34 If you flash this you will need to flash 15.0410.1803.51 right after or you wont have audio and videos will lag.
WW-14.2610.1801.51_ROM
Change Log: January Security Updates
WW-14.2610.1712.45_ROM
Thanks Dude! Now I cant root it safe, without worrying about not having a recovery
No problem!, This will also allow people that unlocked bootloader before getting the latest ota, to be on the latest software update, il keep making these as asus releases future updates for our phones.
Added Latest WW-14.2610.1801.51 update enjoy guys.
rafyvitto said:
Added Latest WW-14.2610.1801.51 update enjoy guys.
Click to expand...
Click to collapse
Thanks dude...and sorry to ask...but can you do one with the oreo update? Thank
As soon as someone posts the oreo ota zip i will, haven't gotten the update on my phone yet ;/.
ok guys i have a working flashable OREO! but videos are lagging because i havent been able to flash the firmware files need to dig deeper into this, before releasing it, give me some time guys, also twrp is unable to decrypt OREO internal data so thats another issue, but this one si out of my league shakalaca will need to update our recovery to decryot oreo data, il upload the current rom if anyone is willinf to flash it with the current issues, let me know.
Here's a screenshot of about screen.
Proof of root on oreo
Hi.Can I update my firmware if bootloader is unlocked and root is installed?If so, how?
You want to upgrade to oreo? Or just update your current firmware?
Just wondering.Are phones updated when the bootloader is unlocked?
Yes you can update phones with unlock bootloader's, if you want official updates you need the stock recovery, the twrp flashable roms i made will give you stock recovery.
Where is the stock recovery to take?
Flash any of the twrp stock roms i made and it will give you stock recovery.
Download firmware from the official website of asus, install it via twrp
and I get stock recovery with the new firmware???You don't know when to do an unofficial unlock of the bootloader?
rafyvitto said:
ok guys i have a working flashable OREO! but videos are lagging because i havent been able to flash the firmware files need to dig deeper into this, before releasing it, give me some time guys, also twrp is unable to decrypt OREO internal data so thats another issue, but this one si out of my league shakalaca will need to update our recovery to decryot oreo data, il upload the current rom if anyone is willinf to flash it with the current issues, let me know.
Click to expand...
Click to collapse
Hi. I flashed the stock rom you uploaded because I accidentally lost mine... aside from audio/video lag issues, audio from calls were also unable to hear. Will patiently wait for your stock rom with firmware files. thaaaaanks
Go into recovery and flash the official oreo zip this will flash firmware files and fix no audio/video lag issues.
rafyvitto said:
Go into recovery and flash the official oreo zip this will flash firmware files and fix no audio/video lag issues.
Click to expand...
Click to collapse
:'(
Groundz said:
:'(
Click to expand...
Click to collapse
If you flash my oreo zip with no firmware and boot it up, this will give you stock recovery, which you will need to flash the stock oreo zip , and ofcourse you will need to reflash twrp after.

WW 1910.64 RAW FULL & OTA update download links + root img link, notes & instructions

WW 1910.64 RAW FULL & OTA update download links + root img link, notes & instructions
RAW WW 1910.64 2.66GB
https://mega.nz/#!spBlACjC!S1UcaxBmnL_e3GGeoBL1ebWJPbSyPQBZESFdxbakuGc
WW OTA file (From. 44 to. 64) 122MB
https://fota2.asus.com/delta_packag...910.44-16.0631.1910.64-12100105-fota-user.zip
FULL WW FIRMWARE 2.2GB
http://dlcdnets.asus.com/pub/ASUS/Z..._I001_1-ASUS-16.0631.1910.64-1.1.253-user.zip
rootww191064.img 48.2MB
https://mega.nz/#!PzYhma5b!1did324GAxfvRk6z4LCKM2pfhbwf4jKpb1e1ER6bLYk
The safest way to update without losing anything is to download the 2.2gb full firmware file on your device then move it to root using the built in file manager. Once you have moved it restart your device and follow the upgrade instructions, takes less than 5 minutes.
Version number
16.0631.1910.64
Update information
1.Fixed Docomo SIM often disconnected mobile network issue.
2.Fixed occasional touch failure.
3.Fixed that navigation bar will not shrink to bottom automatically when playing PUBG MOBILE game.
4.Fixed call volume being lower than normal for Facebook and WhatsApp calling.
5.Fixed File Manager crashing when opening a picture in the middle folder.
6.Fixed that user can’t share Airtrigger or key mapping settings in “Star Commander”.
It still has the October 1st Android security patch.
FULL WW FIRMWARE
http://dlcdnets.asus.com/pub/ASUS/Z..._I001_1-ASUS-16.0631.1910.64-1.1.253-user.zip
Updated and keep root, thanks mate.
cloud1 said:
FULL WW FIRMWARE
http://dlcdnets.asus.com/pub/ASUS/Z..._I001_1-ASUS-16.0631.1910.64-1.1.253-user.zip
Click to expand...
Click to collapse
What's the difference between the User version and the raw version please. Everytime i have to wait for the raw version, is there a way for me to move to the User version and get quick updates? If there is please how? Thanks
tnbt said:
What's the difference between the User version and the raw version please. Everytime i have to wait for the raw version, is there a way for me to move to the User version and get quick updates? If there is please how? Thanks
Click to expand...
Click to collapse
Just download the full one and put on root.
That's what I did and it updated after a restart.
cloud1 said:
Just download the full one and put on root.
That's what I did and it updated after a restart.
Click to expand...
Click to collapse
I did that with the previous updates and it never worked till i got the raw version and flashed. Dunno how to get to use the fota versions. Any help?
tnbt said:
I did that with the previous updates and it never worked till i got the raw version and flashed. Dunno how to get to use the fota versions. Any help?
Click to expand...
Click to collapse
Seriously just grab the full version and put on root, I did it like half an hour ago zero issues.
tnbt said:
I did that with the previous updates and it never worked till i got the raw version and flashed. Dunno how to get to use the fota versions. Any help?
Click to expand...
Click to collapse
Do you have a WW version with WW fingerprint? In case you have a WW version with CN fingerprint FOTA versions won't work!
How about keeping rooted using FULL WW FIRMWARE 2.2GB?
FOTA update will work on Tencent with WW rom. Just rename FOTA zip file exactly as full ROM
Mad_Duke said:
Do you have a WW version with WW fingerprint? In case you have a WW version with CN fingerprint FOTA versions won't work!
Click to expand...
Click to collapse
I have changed fingerprint as well to WW
---------- Post added at 03:25 PM ---------- Previous post was at 03:25 PM ----------
SkipperRyujin said:
FOTA update will work on Tencent with WW rom. Just rename FOTA zip file exactly as full ROM
Click to expand...
Click to collapse
Will try this out, thanks
Can i install from 16.0631.1908.12 to this FULL version with update or i must have 1910.44 version ? Have fingerprint to WW.
I just tryed and its working Thanks for update !
cloud1 said:
Just download the full one and put on root.
That's what I did and it updated after a restart.
Click to expand...
Click to collapse
What do u mean by put on root.
Which folder are u talking about ?
Just downloaded the full rom.
I am currently on 1910.44 and rooted.
Will I be able to tay rooted after update ?
CRYPTfromCATACOMBZ said:
How about keeping rooted using FULL WW FIRMWARE 2.2GB?
Click to expand...
Click to collapse
Download full rom, place in root of storage, reboot, update. Don't select restart, select later. Open magisk manager, click to install magisk, select after ota, force install ok then reboot. Job done, root maintained
reg66 said:
Download full rom, place in root of storage, reboot, update. Don't select restart, select later. Open magisk manager, click to install magisk, select after ota, force install ok then reboot. Job done, root maintained
Click to expand...
Click to collapse
I forgot about the magisk part and rebooted losing root in the process.
Any way to extract the boot image so I can patch it with magisk? It do I need to wait for the RAW ROM?
gilsol said:
I forgot about the magisk part and rebooted losing root in the process.
Any way to extract the boot image so I can patch it with magisk? It do I need to wait for the RAW ROM?
Click to expand...
Click to collapse
Well I have just asked over on the Vietnam Telegram group if there's an ETA on the patched root img. Hopefully I'll get a response soon and will let you know ASAP. But yeah, once that's released you can go ahead and flash it for root using the cmd "fastboot flash boot xxxx.img"
Hopefully you can/don't mid waiting a couple of days for it to be released - until then, you'll just have to be unrooted
I'll keep you posted...
reg66 said:
Well I have just asked over on the Vietnam Telegram group if there's an ETA on the patched root img. Hopefully I'll get a response soon and will let you know ASAP. But yeah, once that's released you can go ahead and flash it for root using the cmd "fastboot flash boot xxxx.img"
Hopefully you can/don't mid waiting a couple of days for it to be released - until then, you'll just have to be unrooted
I'll keep you posted...
Click to expand...
Click to collapse
Thanks a lot, I have been researching this a bit and I'm going to try to get the boot image from the fulll ROM payload.bin. there are tools for this, if I'm successful than magisk can take care of the rest.
I'll keep you posted as well.
:good:
zohaibshafijutt said:
What do u mean by put on root.
Which folder are u talking about ?
Just downloaded the full rom.
I am currently on 1910.44 and rooted.
Will I be able to tay rooted after update ?
Click to expand...
Click to collapse
Just move the zip update from downloads folder and paste it into the main area where other folders are stored, like downloads/music/ringtones etc etc... Don't place it in any folder, just place it in the same location as those other folders...
From there, restart the phone and when update is detected, choose to update but DON'T select to reboot once it is done. Instead, open Magisk Manager and select 'install' for Magisk (not magisk manager), then select 'Install to Inactive Slot (After OTA). Install it and reboot. That's it, root will be maintained :good:
Hi pls help. Even though i put it in internal storage and restart it. My phone cant detect an update. My firmware is 1910.44 and tencent fully converted to WW with WW fingerprint
carlaldous said:
Hi pls help. Even though i put it in internal storage and restart it. My phone cant detect an update. My firmware is 1910.44 and tencent fully converted to WW with WW fingerprint
Click to expand...
Click to collapse
Did you download the full rom or the small ota? If it's the small ota you need to rename it to exact name of the full ota, or just download the full... I went for the full rom. Did you restart the phone after?

Categories

Resources