Develop Bugs

Marshmallow OTA link here

Here's the official OTA link to update from LCA43 (Lollipop) to MEC24H (Marshmallow). Enjoy! You can only flash this on a watch that is completely stock! If you need to restore your watch, Sony PC Companion might work.
https://android.googleapis.com/pack...e2ee74fbab.signed-tetra-MEC24H-from-LCA43.zip
Small note: This OTA will update the bootloader to block "tethered booting" in fastboot while the bootloader is locked (so you will have to unlock the bootloader to use TWRP). If you want to keep the old bootloader, there is a post on the third page. This zip is signed by Sony, so you can flash it in stock recovery with a locked bootloader.
Edit: Here are some screenshots. Not much has changed compared to Lollipop, and Sony hasn't added anything compared to other watches, so they're not very interesting. https://imgur.com/a/Vp8hY (Ambient Mode might look worse on your watch because after I flashed Marshmallow I edited build.prop to disable low bit ambient mode. If you want to do this too, I made a crappy tutorial for that on reddit: https://www.reddit.com/r/AndroidWea...an_disable_low_bit_ambient_mode_to_make_your/)

Hi,
thanks for link. Could you give here some tutorial how to install this update ?
Must have unlock bootloader for this update ?
Thanks.

kalousek said:
Could you give here some tutorial how to install this update ?
Click to expand...
Click to collapse
Open up adb on a computer and plug in the watch. Issue adb reboot recovery and tap the watch screen when the recovery droid picture shows up. Swipe down to the sideload option then swipe right. Issue adb sideload blahblah.zip (obviously put the real zip name where "blahblah" is) and wait. After it finishes, swipe to the reboot option and swipe right to select. Your watch has been updated!

andrewia said:
Here's the official OTA link to update from LCA43 (Lollipop) to MEC24H (Marshmallow). Enjoy!
https://android.googleapis.com/pack...e2ee74fbab.signed-tetra-MEC24H-from-LCA43.zip
This OTA will update the bootloader to block "tethered booting" in fastboot with a locked bootloader. Unlocking the bootloader restores functionality. You can flash this zip in stock recovery with a locked bootloader.
Edit: Here are some screenshots. Not much has changed compared to Lollipop, and Sony hasn't added anything compared to other watches, so they're not very interesting. https://imgur.com/a/Vp8hY Ambient Mode might look worse on your watch because I edited build.prop to disable low bit ambient mode. I made a crappy tutorial for that on reddit: https://www.reddit.com/r/AndroidWea...an_disable_low_bit_ambient_mode_to_make_your/
Click to expand...
Click to collapse
so you have already disabled low bit mode??? and did you reup the zip after or was that done before you uploaded it?

andrewia said:
Open up adb on a computer and plug in the watch. Issue adb reboot recovery and tap the watch screen when the recovery droid picture shows up. Swipe down to the sideload option then swipe right. Issue adb sideload blahblah.zip (obviously put the real zip name where "blahblah" is) and wait. After it finishes, swipe to the reboot option and swipe right to select. Your watch has been updated!
Click to expand...
Click to collapse
Thanks for tutorial

lohtse said:
so you have already disabled low bit mode??? and did you reup the zip after or was that done before you uploaded it?
Click to expand...
Click to collapse
The zip is the stock zip on Google's servers. My mod is separate, I just mentioned it in case anyone was wondering why my card previews looked better than theirs.

andrewia said:
The zip is the stock zip on Google's servers. My mod is separate, I just mentioned it in case anyone was wondering why my card previews looked better than theirs.
Click to expand...
Click to collapse
anychance you can provide a revised zip with the mod??

Can Someone provide boot.img from MM update?

lohtse said:
anychance you can provide a revised zip with the mod??
Click to expand...
Click to collapse
No, because the mod is literally only adding a single character (#) to a line in build.prop. If I repacked it into a zip you would still have to boot TWRP and use adb to flash it, which is 90% of the work.

I'll try to pull the boot image tomorrow.

andrewia said:
I'll try to pull the boot image tomorrow.
Click to expand...
Click to collapse
Thanks. I want look at ramdisk. And recompile kernel for MM update...

anyone finding the UI really laggy since doing this update ?

I have a bone stock watch, locked bootloader etc. When trying to sideload I get status 7 error when trying to update. Any ideas?

pickles76 said:
I have a bone stock watch, locked bootloader etc. When trying to sideload I get status 7 error when trying to update. Any ideas?
Click to expand...
Click to collapse
mine was completely stock and i just followed instructions in this post and went fine

bigr1979 said:
mine was completely stock and i just followed instructions in this post and went fine
Click to expand...
Click to collapse
Yup, I've done this many times before on other devices but this one ends up with status 7 doing exactly as explained. Tried downloading the file a few times (im on OSX/Mac btw) and still the same results. Maybe should try on a windows-machine.

pickles76 said:
I have a bone stock watch, locked bootloader etc. When trying to sideload I get status 7 error when trying to update. Any ideas?
Click to expand...
Click to collapse
complete stock, locked bootloader and unrooted and no issues for me..
On that note what are the best ways to Unlock bootloader(will I loose data?), Flash twrp and then root?
---------- Post added at 11:49 AM ---------- Previous post was at 11:48 AM ----------
bigr1979 said:
anyone finding the UI really laggy since doing this update ?
Click to expand...
Click to collapse
Nope I actually find it snappier.... I have 30+ apps on as well

lohtse said:
complete stock, locked bootloader and unrooted and no issues for me..
On that note what are the best ways to Unlock bootloader(will I loose data?), Flash twrp and then root?
---------- Post added at 11:49 AM ---------- Previous post was at 11:48 AM ----------
Nope I actually find it snappier.... I have 30+ apps on as well
Click to expand...
Click to collapse
I used windows 10 64bit to flash mine.... Seems to be getting a bit snappier now that its calming down and have downloaded music onto etc cheers thanks OP for the update

andrewia said:
I'll try to pull the boot image tomorrow.
Click to expand...
Click to collapse
Never mind.
I've extracted boot.img.
Try to rebuild my kernel for MM.
Sent from my HTC One_M8 using XDA-Developers mobile app

pickles76 said:
I have a bone stock watch, locked bootloader etc. When trying to sideload I get status 7 error when trying to update. Any ideas?
Click to expand...
Click to collapse
Hello
I have the same problem. How do you solve it?
Thanks.
OK now I flashed the stock kernel of LCA43 before flashing the full rom

mickael91210 said:
Hello
I have the same problem. How do you solve it?
Thanks.
OK now I flashed the stock kernel of LCA43 before flashing the full rom
Click to expand...
Click to collapse
Could you explain more? Im still stuck..

New OTA File for build number 67

I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ

sandy108 said:
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
Click to expand...
Click to collapse
Is this ok to install on the US variants?
Sent from my iPhone using Tapatalk

From what I understand, I'm just supposed to download this and then go to my recovery and update from recovery right?
As in like update from internal storage right?

What version is this from?

hey bro did you have the flashligt icon and gesture in the new update?

Anyone flashed this with flash fire?

How to install on rooted devices???

sandy108 said:
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
Click to expand...
Click to collapse
You didn't tell us what variant of the phone you have

How to install???

zimplemeh said:
Is this ok to install on the US variants?
Click to expand...
Click to collapse
No this is not recommended to install on US variant

saqlainrattansi said:
From what I understand, I'm just supposed to download this and then go to my recovery and update from recovery right?
As in like update from internal storage right?
Click to expand...
Click to collapse
Yes you got it right

olive23 said:
What version is this from?
Click to expand...
Click to collapse
It's from build number *67

Jayesh Nirve said:
How to install???
Click to expand...
Click to collapse
Either use stock recovery or use Flashfire

zeft64 said:
You didn't tell us what variant of the phone you have
Click to expand...
Click to collapse
Indian Variant

Flash fire ain't working phone just reboots with no changes

can i install on retbr?

I think the location version does not matter as long as you have the right build number. I had retla .15 and tried to flash .35 in order to update to .67 (fail), the ota ask for .14/.15. So I had to install stock .15 again and redo the process.
Something I'd like to add is the stock recovery did not recognize internal or sd storage, so I had to push ota via ADB.
*Also my warning bootscreen changed from N/A to Bad Key multiple times for apparently no reason. But everything is working fine.

Pls tell me how u went back to 15 plsss

Aredhelelen said:
I think the location version does not matter as long as you have the right build number. I had retla .15 and tried to flash .35 in order to update to .67 (fail), the ota ask for .14/.15. So I had to install stock .15 again and redo the process.
Something I'd like to add is the stock recovery did not recognize internal or sd storage, so I had to push ota via ADB.
*Also my warning bootscreen changed from N/A to Bad Key multiple times for apparently no reason. But everything is working fine.
Click to expand...
Click to collapse
Exactly what I have been trying to tell. There is a fingerprint mismatch that happens. On a side note how did you manage to take yourself back from .35 to .15 and then update to .67. I get the last part, but downgrading with a higher bootloader; and where did you get the .15 build

You can simply install one of the stock versions already posted here in the forum, I just downloaded the .15 and installed it again via fastboot with the command lines (also explained in that post, in comments) like any other stock rom. Then, after starting the phone you must activate USB debbuging mode to be able to use ADB commands, so you can restart the phone in stock recovery and activate the push ota update via ADB.
Anyway, if this sounds complicated I think there is already a flashable .zip to apply ota, you can give it a try.

Roll Back to MarshMallow [BLN-L22]

Hi,
Below are the steps to rollback to Marshmallow from Nougat. I've only tested it on BLN-L22 so I don't know if it works with other variants.
Your bootloader would be locked. However, you can unlock again using the old unlock code.
You can find firmware of your version @ Honor Official Site
Download the Marshmallow firmware from here Honor India Official Support
Unzip it and place the dload folder in the sdcard (internal storage wont work)
Power off the device.
Press Volume Down + Volume Up + Power key to log into Huawei software upgrade
Let it finish. Now installation is done. But now when you will boot, it will bootloop and go to Huawei ercovery. Simply select the shutdown option
Once the device is off, press Volume Up + Power. This will take you to Huawei Recovery
Wipe data and Wipe Cache
Restart. You are back to MarshMallow
Kindly do the above at your own risk. It worked for me, but it may brick for you.
Edit : User @honor6xak was able to rollback after wiping the system using TWRP and following above steps. If there is no system, there would be no firmware for Honor to overwrite. It would be as good as flashing fresh.
Method 2.
1. Make a nandroid backup (complete backup) and save it somewhere safe. Just in case things get messy.
2. Download the official firmware (Marshmallow) from the Honor official site.
3. Extract the dload folder from the firmware and put it into an sdcard (physical one).
4. Reboot to TWRP and wipe data + system. Twrp will warn you about wiping system. Once you do it. Power off the device.
5. Press volume up + volume down + power this will take you to Huawei recovery and will auto install the firmware if the folder is there in sdcard.
This is a tad bit risky but if you have nandroid backup then you can be on a safe side. But still do it only if you are sure. I don't have money to pay if you Sue me

The above link is for the Indian firmware for the US firmware (L24) you'll have to go to the us website. I got a little confused earlier trying to download it, just thought I'd give a heads up to anybody else. I'd link it but I had to create a new account as my old one is apparrently tied to an email I don't remember.

Ziffnil said:
The above link is for the Indian firmware for the US firmware (L24) you'll have to go to the us website. I got a little confused earlier trying to download it, just thought I'd give a heads up to anybody else. I'd link it but I had to create a new account as my old one is apparrently tied to an email I don't remember.
Click to expand...
Click to collapse
Yes, that's the reason I specified the BLN number. You don't need to login to have the firmware download. If you can give the link we can update the post.
Edit : I've updated site for Official firmware of various regions in the main post

It's official mm r ( this is root mobiles or unrooting mobiles ) any virus problem

eddy7990 said:
It's official mm r ( this is root mobiles or unrooting mobiles ) any virus problem
Click to expand...
Click to collapse
If you flash these official version you'll get unrooted and your bootloader would be locked again. But you can unlock the bootloader again and root also.
Since it is from official website I doubt it will have any virus

So hacky but... you can find the 'rollback package' here http ://www, hihonor, ]com/us/support/details/index,html?[DOC_ID=94205] and the firmware here http ://www, hihonor, [com/us/support/details/index.html?][DOC_ID=94205]
Just remove the spaces, brackets and replace periods with commas.

suhel28 said:
If you flash these official version you'll get unrooted and your bootloader would be locked again. But you can unlock the bootloader again and root also.
Since it is from official website I doubt it will have any virus
Click to expand...
Click to collapse
Hello bro,
I several times tried the method that you mentioned in your thread using a memory card but it always failed. I'm very curious how it worked for you. Right now I unlocked and rooted my Honor 6x BLN-L22.
I just want to know if your phone was unlocked when you tried this method.
If yes I'll give it a try. It might work this time.
Thank you

Angircy said:
Hello bro,
I several times tried the method that you mentioned in your thread using a memory card but it always failed. I'm very curious how it worked for you. Right now I unlocked and rooted my Honor 6x BLN-L22.
I just want to know if your phone was unlocked when you tried this method.
If yes I'll give it a try. It might work this time.
Thank you
Click to expand...
Click to collapse
Yes, my phone was rooted as well as unlocked when I tried it. I hope it works for you.

suhel28 said:
Yes, my phone was rooted as well as unlocked when I tried it. I hope it works for you.
Click to expand...
Click to collapse
Bro it didn't work for me.

Angircy said:
Bro it didn't work for me.
Click to expand...
Click to collapse
You can do one thing I don't know if it work but you can try it. Download firmware finder from play store. Search for the latest nougat firmware then select download. There would be two files 1. Update.zip 2. BLNxxxx some name. Download the second file. Then flash it with twrp.
Now do the procedure as I described in the first post. When I did the roll back I was on the unofficial nougat version.
I'll search for some other method. Sorry it didn't work for you.

suhel28 said:
You can do one thing I don't know if it work but you can try it. Download firmware finder from play store. Search for the latest nougat firmware then select download. There would be two files 1. Update.zip 2. BLNxxxx some name. Download the second file. Then flash it with twrp.
Now do the procedure as I described in the first post. When I did the roll back I was on the unofficial nougat version.
I'll search for some other method. Sorry it didn't work for you.
Click to expand...
Click to collapse
Thanks a lot bro. I'll try that.

It worked for me on my BLN-L24, rolling it back to I could exchange it. However I had to do a couple other steps first to get it to work, so here's my full steps that worked for me:
1. If you have twrp or another custom recovery, flash it back to stock.
1a. To find the stock recovery I had to get it from the zip file here since I'm a dumbass and didn't make a backup: If you have twrp or another custom recovery, flash it back to stock.
2. If you have a custom bootloader, flash it back to stock.
3. Download and extract the stock rom. Flashing it from zip will not work.
4. Copy the UPDATE.app to /sdcard/dload/ (not a physical sdcard, if that's what's confusing you.
5. Turn the device all the way off.
6. Press and hold volume up, and volume down, then press and hold power until the phone starts booting, immediately release it once you see something on the screen.
It should now 'update' your phone back to EMUI 4.1.

Ziffnil said:
It worked for me on my BLN-L24, rolling it back to I could exchange it. However I had to do a couple other steps first to get it to work, so here's my full steps that worked for me:
1. If you have twrp or another custom recovery, flash it back to stock.
1a. To find the stock recovery I had to get it from the zip file here since I'm a dumbass and didn't make a backup: If you have twrp or another custom recovery, flash it back to stock.
2. If you have a custom bootloader, flash it back to stock.
3. Download and extract the stock rom. Flashing it from zip will not work.
4. Copy the UPDATE.app to /sdcard/dload/ (not a physical sdcard, if that's what's confusing you.
5. Turn the device all the way off.
6. Press and hold volume up, and volume down, then press and hold power until the phone starts booting, immediately release it once you see something on the screen.
It should now 'update' your phone back to EMUI 4.1.
Click to expand...
Click to collapse
I'd put the dload folder in the sdcard folder but it didn't work. I'd to use a physical sdcard

so can i flash the firware zip file using twrp please help me out am on twrp screen oly coudnt start my ddevice am running nougat emui 5 bln22
suhel28 said:
Yes, my phone was rooted as well as unlocked when I tried it. I hope it works for you.
Click to expand...
Click to collapse

honor6xak said:
so can i flash the firware zip file using twrp please help me out am on twrp screen oly coudnt start my ddevice am running nougat emui 5 bln22
Click to expand...
Click to collapse
What did you do that you are stuck at TWRP?
Tell the history then we can suggest something
Download the update_data_full_BLN-L22_channel_in.zip and place it on sdcard.
You can then flash it with TWRP

i was on emui 5 nougat tried to install arise it did installed fine and later the camera was not opening and restarting device didnt help .... hence i went ahead and tried to flash the nougat again with twrp as i didnt know it ll be messed up like this
suhel28 said:
What did you do that you are stuck at TWRP?
Tell the history then we can suggest something
Click to expand...
Click to collapse

honor6xak said:
i was on emui 5 nougat tried to install arise it did installed fine and later the camera was not restarting hence i went ahead and tried to flash the nougat again with twrp as i didnt know it ll be messed up like this
Click to expand...
Click to collapse
Download the update_data_full_BLN-L22_channel_in.zip and place it on sdcard.
You can then flash it with TWRP

suhel28 said:
What did you do that you are stuck at TWRP?
Tell the history then we can suggest something
Download the update_data_full_BLN-L22_channel_in.zip and place it on sdcard.
You can then flash it with TWRP
Click to expand...
Click to collapse
another confusion now i went to the honor official site and downloaded emui4 update its 1.7gb whears the file u mentioned above is just 733 mb so which one do i flash ??? bro
the file u mentioned above is it nougat ???
my twrp says there is no os on the device when i head to reboot so my question >>is it posible to install nougat and reboot them or shoould i go back to the marsh...
pls help me out bro

honor6xak said:
another confusion now i went to the honor official site and downloaded emui4 update its 1.7gb whears the file u mentioned above is just 733 mb so which one do i flash ??? bro
Click to expand...
Click to collapse
You cannot directly flash the 4.1 file on your nougat. If you want to do that then you have to use the procedure I gave in the first page.
The link I gave is for nougat version. Basically, when I had a similar problem like you I flashed the 733mb file and my phone was able to boot.
Wipe data in TWRP
Flash the 733mb file
Wipe cache
I hope it works

suhel28 said:
You cannot directly flash the 4.1 file on your nougat. If you want to do that then you have to use the procedure I gave in the first page.
The link I gave is for nougat version. Basically, when I had a similar problem like you I flashed the 733mb file and my phone was able to boot.
Wipe data in TWRP
Flash the 733mb file
Wipe cache
I hope it works
Click to expand...
Click to collapse
Both methods didn't work for me though I flashed the 733mb file using TWRP successfully.

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