Develop Bugs

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

help for correct firmware to unbrick k5 plus 3 gb variant

hey guys, i found 3-4 firmware on shreps or scritch Server they shared, but i am confused about selecting correct firmware for my device, as i have K5 Plus with following specs ( MSM8916 Snapdragon 615 as per CPU-Z and Snapdragon 616 as per gsmarena and lenovo said.) with 3GB of RAM i am on A6020a46_S051_160805_ROW STOCK and i show new update A6020a46_S051_160805_ROW_TO_A6020a46_S056_161019_16G_ROW. (59 MB in size) i downloaded update but i am on twrp recovery so i flash stock recovery using fastboot and then try to UPDATE my devie but it failed to download new system just updating system and then rebooted to normal and after that got ERROR update failed? any one faced same issue if yes and if you solved please guide a little. or tell me the correct firmware for our devie so i can restore to full stock firmware again using QPST.
Thanks
Hardik.

BHARDIK said:
hey guys, i found 3-4 firmware on shreps or scritch Server they shared, but i am confused about selecting correct firmware for my device, as i have K5 Plus with following specs ( MSM8916 Snapdragon 615 as per CPU-Z and Snapdragon 616 as per gsmarena and lenovo said.) with 3GB of RAM i am on A6020a46_S051_160805_ROW STOCK and i show new update A6020a46_S051_160805_ROW_TO_A6020a46_S056_161019_16G_ROW. (59 MB in size) i downloaded update but i am on twrp recovery so i flash stock recovery using fastboot and then try to UPDATE my devie but it failed to download new system just updating system and then rebooted to normal and after that got ERROR update failed? any one faced same issue if yes and if you solved please guide a little. or tell me the correct firmware for our devie so i can restore to full stock firmware again using QPST.
Thanks
Hardik.
Click to expand...
Click to collapse
Download s042 ....the fourth zip file in shreps page and if u want to update it to s051, you have to flash India ota zip before you download and install the update

Harry8242 said:
Download s042 ....the fourth zip file in shreps page and if u want to update it to s051, you have to flash India ota zip before you download and install the update
Click to expand...
Click to collapse
i downloaded that file too and tried flashing through qpst tool provided with that file but at last step i got download failed error i meant when i put device with pc while pressing both volume up + down button device detected and i press download button and after some seconds it show error message download failed.
i searched some methods to flash stock rom tried all, even tried lenovo assistant and download user firmware S045 fro. there but after extract and download it through qpst and through lenovo assistant both give failed error!
then now i post this threads.
i need stock recovery which come with S051 sotck if anyone have it please upload it.
thanks for reply
Regard,
Hardik

BHARDIK said:
i downloaded that file too and tried flashing through qpst tool provided with that file but at last step i got download failed error i meant when i put device with pc while pressing both volume up + down button device detected and i press download button and after some seconds it show error message download failed.
i searched some methods to flash stock rom tried all, even tried lenovo assistant and download user firmware S045 fro. there but after extract and download it through qpst and through lenovo assistant both give failed error!
then now i post this threads.
i need stock recovery which come with S051 sotck if anyone have it please upload it.
thanks for reply
Regard,
Hardik
Click to expand...
Click to collapse
Oh sorry i forgot ..... the qpst tool included in our stock rom is the newest version ........it does not work with our device....download the older version from the link below and let me know if it works .
https://docs.google.com/uc?id=0B_MAL3K1CFyUWUZNTTBVcmtzNGs&export=download

Harry8242 said:
Oh sorry i forgot ..... the qpst tool included in our stock rom is the newest version ........it does not work with our device....download the older version from the link below and let me know if it works .
https://docs.google.com/uc?id=0B_MAL3K1CFyUWUZNTTBVcmtzNGs&export=download
Click to expand...
Click to collapse
okay let me try with this and will tell you letter for sure
ryt now downloading cm14. 1, i want to give it a try
stock download done with older QPST 2.7.400 thanks for sharing

BHARDIK said:
okay let me try with this and will tell you letter for sure
ryt now downloading cm14. 1, i want to give it a try
stock download done with older QPST 2.7.400 thanks for sharing
Click to expand...
Click to collapse
And btw when did you get the s056 update because when i checked 10 days back,
it was still in s051.

Harry8242 said:
And btw when did you get the s056 update because when i checked 10 days back,
it was still in s051.
Click to expand...
Click to collapse
i am already on latest update S056_161019_ROW(5.1.1)
i got it exact date when i create this thread.
Regard,
Hardik

the latest version is this s105 for 46 3gb one with volte modem....

[LUX][STOCK][6.0.1] MPDS24.107.70.1-5 (1. Jan 2017 security level) TWRP backup

Since there doesn't appear to be any full stock firmwares for the January Patch around
Retail ASIA, DUAL SIM variant
Does not contain supersu or anything else
How it was made:
Flashed stock firmware LUX_RETASIA_DS_6.0.1_MPD24.107-70-1_cid7_subsidy-DEFAULT_CFC.info and then sideloaded the OTA package MPDS24.107-70-1-5
The only thing i have changed is the bootlogo (removed the pesky bootloader unlocked screen), but i am unsure if that's even in the backup contents
How to install:
I suggest grabbing a LUX_RETASIA_DS_6.0.1_MPD24.107-70-1 firmware and flashing that first, just so you don't get boot or modem issues
(you can get it here https://firmware.center/firmware/Motorola/Moto X Play/Stock/XT1562/)
(instructions on how to flash here at the bottom https://github.com/motoxplay/stock)
You need a TWRP recovery flashed (https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656)
Extract, put the folder on your device next to your own TWRP backups, reboot recovery, restore from it.
Download:
https://mega.nz/#!Bxk31KiR!xdVWV1M-06xfatAUetjeY94p1qArhiSefa4ezj4431c

AtomicStryker said:
Since there doesn't appear to be any full stock firmwares for the January Patch around
Retail ASIA, DUAL SIM variant
Does not contain supersu or anything else
How it was made:
Flashed stock firmware LUX_RETASIA_DS_6.0.1_MPD24.107-70-1_cid7_subsidy-DEFAULT_CFC.info and then sideloaded the OTA package MPDS24.107-70-1-5
The only thing i have changed is the bootlogo (removed the pesky bootloader unlocked screen), but i am unsure if that's even in the backup contents
How to install:
I suggest grabbing a LUX_RETASIA_DS_6.0.1_MPD24.107-70-1 firmware and flashing that first, just so you don't get boot or modem issues
(you can get it here https://firmware.center/firmware/Motorola/Moto X Play/Stock/XT1562/)
(instructions on how to flash here at the bottom https://github.com/motoxplay/stock)
You need a TWRP recovery flashed (https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656)
Extract, put the folder on your device next to your own TWRP backups, reboot recovery, restore from it.
Download:
https://mega.nz/#!Bxk31KiR!xdVWV1M-06xfatAUetjeY94p1qArhiSefa4ezj4431c
Click to expand...
Click to collapse
Is it possible to get the MPDS24.107-70-1-5 firmware to flash since, I tried flashing the MPD24.107-70 firmware and it is just throwing error left right and center, invalid signed image, preflash validation failed. I'm really stuck in what should be my next step

Presumably, getting the correct firmware for your device. I never had any issues and i re-flashed a single slot device to dual slot...

Not +ve response
siddharthnair96 said:
Is it possible to get the MPDS24.107-70-1-5 firmware to flash since, I tried flashing the MPD24.107-70 firmware and it is just throwing error left right and center, invalid signed image, preflash validation failed. I'm really stuck in what should be my next step
Click to expand...
Click to collapse
The method you've mentioned above. It's quiet helpful. But it's not success in my device.
I'm using Moto X play XT1562, dual sim and Location : India. Stock Rom with : 6.0.1 Marshmallow. Help me to flash with stock Rom ASAP Dude.

RohithAbi said:
The method you've mentioned above. It's quiet helpful. But it's not success in my device.
I'm using Moto X play XT1562, dual sim and Location : India. Stock Rom with : 6.0.1 Marshmallow. Help me to flash with stock Rom ASAP Dude.
Click to expand...
Click to collapse
You can download all the tools and stock ROM (MM) from my google drive link below. I have included the steps and commands to be executed.
ADB Drivers, USB Drivers, steps and commands : https://drive.google.com/open?id=0B5a7fC9ekt7seWF5SkVMNUIwTmc
Stock Rom (adb flash file) : https://drive.google.com/open?id=0B5a7fC9ekt7sVHF4VFdEdUlQcms

Can I get the modem of mpds24? Thanks

ZETROzky said:
Can I get the modem of mpds24? Thanks
Click to expand...
Click to collapse
Sorry, I don't have it..

Stock Recovery needed
Shibin_1985 said:
You can download all the tools and stock ROM (MM) from my google drive link below. I have included the steps and commands to be executed.
ADB Drivers, USB Drivers, steps and commands : https://drive.google.com/open?id=0B5a7fC9ekt7seWF5SkVMNUIwTmc
Stock Rom (adb flash file) : https://drive.google.com/open?id=0B5a7fC9ekt7sVHF4VFdEdUlQcms
Click to expand...
Click to collapse
Can you please upload just the recovery.img file for Moto X Play Marshmallow 6.0.1? I need the stock recovery image in order to get the Nougat OTA update.

Can you post the stock `recovery.img` as a separate file?
AtomicStryker said:
Since there doesn't appear to be any full stock firmwares for the January Patch around
Retail ASIA, DUAL SIM variant
Does not contain supersu or anything else
Click to expand...
Click to collapse
---------- Post added at 10:46 AM ---------- Previous post was at 10:39 AM ----------
Shibin_1985 said:
You can download all the tools and stock ROM (MM) from my google drive link below. I have included the steps and commands to be executed.
ADB Drivers, USB Drivers, steps and commands : https://drive.google.com/open?id=0B5a7fC9ekt7seWF5SkVMNUIwTmc
Stock Rom (adb flash file) : https://drive.google.com/open?id=0B5a7fC9ekt7sVHF4VFdEdUlQcms
Click to expand...
Click to collapse
Is the build number MPDS24.107.70.1-5?
If so can you also post the stock `recovery.img` as a separate file? Thanks

[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.

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?