Hello!
So, you've been able to get official update (through System > Update) after relocking bootloader?
Like one month ago I've relocked the bootloader by installing B320 firmware from Firmware Finder. However, System > Update wasn't showing any update. I'm not sure, but perhaps I had to wait some time like 1-2 days to check for update?
I'm thinking to try this again as I wanna try the new B350 update. Yeah, I know that there are download links for that firmware, but I'd like to get it through the official way.
SOLUTION: here.
I got my Ota while I was rooted, had twrp with unlocked bootloader. This was in marshmallow. I unrooted, flashed the official recovery L11 recovery (my phone is L12) and relocked (causing a low level format of the data partition. After this, I booted back into the cleaned marshmallow without my sim card. I inserted the sim card after and rebooted. Checked for the update which I had previously downloaded B330 , but it wasn't detected and was re-downloaded. The update ran successfully without issues at all. Everything seems to work as it should, including themes.
I haven't rooted yet. I'll have a go at it this evening if I have some time.
#Henkate said:
Hello!
So, you've been able to get official update (through System > Update) after relocking bootloader?
Like one month ago I've relocked the bootloader by installing B320 firmware from Firmware Finder. However, System > Update wasn't showing any update. I'm not sure, but perhaps I had to wait some time like 1-2 days to check for update?
I'm thinking to try this again as I wanna try the new B350 update. Yeah, I know that there are download links for that firmware, but I'd like to get it through the official way.
Click to expand...
Click to collapse
rodlane said:
I got my Ota while I was rooted, had twrp with unlocked bootloader. This was in marshmallow. I unrooted, flashed the official recovery L11 recovery (my phone is L12) and relocked (causing a low level format of the data partition. After this, I booted back into the cleaned marshmallow without my sim card. I inserted the sim card after and rebooted. Checked for the update which I had previously downloaded B330 , but it wasn't detected and was re-downloaded. The update ran successfully without issues at all. Everything seems to work as it should, including themes.
I haven't rooted yet. I'll have a go at it this evening if I have some time.
Click to expand...
Click to collapse
Im sorry, i have forgot to mention that i have solved my problem.
Ive wrote here how ive relocked bootloader and updated to B350.
Related
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Hub00 said:
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Click to expand...
Click to collapse
Try it once again... I've never received OTA updates from b560 onwards.. You could flash your way through
crashpoum99 said:
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Click to expand...
Click to collapse
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
You can try local update......And preferably Force update but it will delete all your data so backup your data And Force update........ Btw leave B584 because B588 is avaiable
Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
I would try force updating using the Power+Vol.Up+Vol.Down method. Go for B588 if you want, as it's newer with the latest security patch. If the error comes after the reboot, it's most likely that force updating will fix this. Remember, force updating will delete your files!
What actually worked is downloading 'full package' in the update menu (the file was 1.56Go instead of 260 Mo). It updated overnight even with twrp. Of course, I lost gyroscope in the process...
So I'm know with B584. I will try to force update to B588 as soon as it is downloaded.
Ok, i'm know on B588 and I have gyroscope back again. Thanks for your help.
However, despite the changelog, i didn't notice any improvement with the whatsapp notifications.
Any idea why ?
ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V4.21.40.223 for WW SKU only* (andriod M)
Improvement Item:
1)Improve Wi-Fi/Bluetooth stability
2)Update Security patch
3)Improve system stability
4)Support India SOS call (India only)
Full Rom Download Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-4.21.40.223-user.zip
Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks
fredlamour said:
Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks
Click to expand...
Click to collapse
It is, but not if your bootloader is unlocked.
Rodepo said:
It is, but not if your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks.
bootloader unlocked so no way.
I am thinking about jumping into a lineage rom.
VoLte support?? in this new update....
I felt like this was happening today! came in and here it is. Updating right now.
Thanks
any update for this update of asus zenfone 2
optimumgiant said:
any update for this update of asus zenfone 2
Click to expand...
Click to collapse
Hello. This forum is for galaxy 8.07. We don't know about zendroid 2 or whatever you ask.
Just joking. This IS for zenfone 2.
I'm currently using the update. Screen flickering has stopped for the time being.
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
it seems you are first. Give it a try and find it out for yourself and let us know!
crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
My way is unroot and uninstall Xposed first, than sideload the whole rom with stock recovery.
I had failed to OTA many times because I modified some system files (forgot to restore them), so now I just reflash rom to save the trouble.
Wifi auto-connect problem seems fixed and the phone has more available ram after "power and boost".
It's worth to update imo.
Battery life seems the same
All sensors working with this version in my brazilian zenfone 2 z00a.
Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.
I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
audit13 said:
After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
I had unlocked the BL before so i updated and directly tried regaining root and xposed but failed (softbrick at asus loading screen), I confirm that applying the whole ota from sideload sort of relocks the bootloader and you must do it again, now it is booting and rebuilding the dalvik cache.
audit13 said:
I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
In conclusion you did only flashed stock recovery and, from that, you flashed the whole zip in the first post, right?
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
timbernot said:
Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.
Click to expand...
Click to collapse
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
timbernot said:
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
can you please share your adblock app with us.
thanks
crownpiyush said:
can you please share your adblock app with us.
thanks
Click to expand...
Click to collapse
its a add-on downloaded and installed from ` tools ` in firefox browser settings :good:
ps, i had trouble using adblockplus add-on from firefox ,when viewing XDA pages ..they turned out blank , XDA i think prevented the use of such adblock , so now i use the less blocking add-on in firefox called `uBlock`
its good enough
Hi there guys so , as stated above I have bought my Moto g4 a while now and today I got the official nougat greece ( i live in greece) OTA , so I downloaded it and it went to restart opened TWRP and then nothing.
My question is should I flash the stock recovery , or can i find the update file in TWRP and just flash it and also do i need to wipe if so.
Can't wait for nougat on this poor man's phone , thanks.
Edit: Forgot to mention when i boot to system from TWRP at some point it renders my phone unusable and says " preparing to update" I am guessing the problem is TWRP.
Pavlovits said:
Hi there guys so , as stated above I have bought my Moto g4 a while now and today I got the official nougat greece ( i live in greece) OTA , so I downloaded it and it went to restart opened TWRP and then nothing.
My question is should I flash the stock recovery , or can i find the update file in TWRP and just flash it and also do i need to wipe if so.
Can't wait for nougat on this poor man's phone , thanks.
Edit: Forgot to mention when i boot to system from TWRP at some point it renders my phone unusable and says " preparing to update" I am guessing the problem is TWRP.
Click to expand...
Click to collapse
You need to have your phone on the stock recovery and unrooted to update via OTA. I am assuming since you got the OTA notification you have everything else stock?
pastorbob62 said:
You need to have your phone on the stock recovery and unrooted to update via OTA. I am assuming since you got the OTA notification you have everything else stock?
Click to expand...
Click to collapse
So in order to do it correctly do I need to find the greek firmware variant and flash the recovery and system , or can I just flash the stock recovery and if so where can i find all of the files.
No you dont need a specific variant on my moto g4 XT1622 i flashed the indian variant but my software channel stayed the same(retgb) which is the U.K
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Trying to update the 4.5.1 and it seemed to have gone fine until it automatically reboots into TWRP recovery. Upon rebooting into system, it states the update failed. With TWRP having all those jumbled folder names right now (has this been fixed yet?) it's hard to see if the update downloaded somewhere to internal storage, and further if it could be flashed even if I found it. Is updating with an OTA like this possible? I know on basically all other phone it is not. Has anyone gotten the update to work while being unlocked, rooted, with TWRP? Thanks.
xgerryx said:
Trying to update the 4.5.1 and it seemed to have gone fine until it automatically reboots into TWRP recovery. Upon rebooting into system, it states the update failed. With TWRP having all those jumbled folder names right now (has this been fixed yet?) it's hard to see if the update downloaded somewhere to internal storage, and further if it could be flashed even if I found it. Is updating with an OTA like this possible? I know on basically all other phone it is not. Has anyone gotten the update to work while being unlocked, rooted, with TWRP? Thanks.
Click to expand...
Click to collapse
Generally you need to reflash the previous Full ROM with TWRP and then flash the OTA on top for it to work as the system must be unmodified. Alternatively, you can just flash the latest Full ROM. Currently those are not available, but that's generally how it works.
If u have installed twrp before updating the stock rom, I guess we have to wait for full rom of latest update 4.5.1 which can be flashed via twrp.
P.s. FLASHING the dwnloaded update via twrp will gives u error.. So have to wait for full rom. ?
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Sovjohn said:
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Click to expand...
Click to collapse
Hello,
my doubt is that you flashed a different firmware version from the one you had, thus corrupting the device's oem file. Could you post which was the latest complete firmware without this problem and the last one you downloaded and flashed? ( ex. L21CxxxB382 & LxxCxxxB506 ).
Let me know this info ...
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Sovjohn said:
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Click to expand...
Click to collapse
Yep, you used correct file but anyhow the firmware has been corrupted.
I think you have some ways to solve...
1 - if you have stock recovery, reboot into it and
download and flash the same latest firmware.
If you do not have it, you can extract (with huawei update extractor) it
(should be recovery1.img) from B506 firmware (update.zip) you already got,
then can be flashed via fastboot commands.
2 - Flash a previous or B380 firmware via HuRUpdater, then
update to latest via Firmware Finder with dns/vpn method.
3 - Repeat the whole job you done with B506 firmware. (via HuRupdater)
4 - Reboot recovery, reflash L21OEMinfo file, dual sim one, then the latest firmware again...
P.S.: method 1, 2, 4 will re-lock the bootloader, no problem if still you got the code...
Beware method 4, after you flash the oeminfo file do not shout down, reboot to bootloader
and unlock it again with the code. Device will reboot into twrp, then flash B506 firmware.
Good luck and let the community know..