Manual update notification not appearing after downloading Android O firmware - Asus ZenFone 3 Deluxe Questions & Answers

Hello,
Asus finally released Android O for ZS570KL and I tried to manually update, but after downloading the file and placing it in the root folder, the update notification doesn't appear.
It doesn't matter if I restart the phone or just disconnect the USB, the notification still won't appear.
Anyone else that has this problem and found a solution?
Thanks.

Try to put it in the root of the sd-card then enter recovery and apply update from zip.

Dabiolos said:
Try to put it in the root of the sd-card then enter recovery and apply update from zip.
Click to expand...
Click to collapse
Did that, worked The update took only like 5 minutes and works like a charm, haven't encountered any bugs in it so far.

Do you happen to know if the update will relock the bootloader?

Related

[Q] Can't update it

Hi, I'm from Italy and my uncle send me an SGH-i747.. I've unlocked it for use my Italy Sim.
The phone is currently 4.1.1 and it doesn't check update. Kies says me that the 4.1.1 is the latest update.. I've download OTA Updater but it says that the rom haven't got otaupdater.otaid or it is empty.
I hope you can help me. :3 Sorry for my bad english.
Spyro1997 said:
Hi, I'm from Italy and my uncle send me an SGH-i747.. I've unlocked it for use my Italy Sim.
The phone is currently 4.1.1 and it doesn't check update. Kies says me that the 4.1.1 is the latest update.. I've download OTA Updater but it says that the rom haven't got otaupdater.otaid or it is empty.
I hope you can help me. :3 Sorry for my bad english.
Click to expand...
Click to collapse
You won't be able to get an OTA update in Italy because the update is delivered via AT&T which you probably don't have access to. You would need to have a valid AT&T SIM card in the phone with Wi-Fi access. You may be able to update manually in 2 steps first to 4.1.1 and then to 4.3 which is the latest OS version by following the process in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2387423
Download the 2 stock files for 4.1.2 and 4.3 respectively. Copy both zips to a good quality micro SDHC card
Power off the phone. Place the SD card into your phone. Boot into recovery mode by simultaneously holding down the volume up, power and home buttons. Wait until you see a blue message flash across the screen then release the power button but continue to hold the volume up and menu button until the Android image appears. Install the 4.1.2. Wait for the process to finish and your phone to reboot. Power off again and repeat for 4.3. Hope this helps you.
Now I try, Thanks .. But I've need to Root my phone?
I've tried to update to 4.1.2 but at the restart of the phone, after "rethink is possible" it remain on the Samsung screen... help D:
Spyro1997 said:
I've tried to update to 4.1.2 but at the restart of the phone, after "rethink is possible" it remain on the Samsung screen... help D:
Click to expand...
Click to collapse
If you got to that stage, then it worked. Sometimes it takes several minutes for the rest of the set-up menu to come up after reboot. Wait for a while and if nothing comes up, pull out and replace the battery, then reboot into recovery mode. Do a hard wipe/factory reset in recovery mode and reboot.
You do not need to root your phone for this process. In fact, it may not work with a rooted phone. You can, however, still root your phone after the update and there are several ways of doing this. However, first get through the updating process and let's know how that goes.
Really thanks, I've done an Hard Reset and it works.. now i've 4.3 thanks a lot. You can close the thread.

[Q] Help! - Rooted Zenfone 2 (ZE551ML) bricked after OTA accidently

followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?

CAN NOT UPDATE TO 2.2..40.194 and therefore to MM

Hi, in early September I started checking the OTA update notification to MM in my recently purchased ZENFONE 2 551ML (4/64GB): NOTHING - then I tried to do it manually, I downloaded the file from the ASUS website (V4.21.40.134) and follow the instructions, once I copied the zip file in the internal memory I found the notification and: did the update started? No, the phone rebooted and after a few seconds I saw a broken green robot with the word ERROR, ok, back to Lollipop, I double checked and saw a note "Before attempting the manual update, please make sure you are updated to V2.20.40.194 or later via the System Update app." while I still have WW 2.20.40.184 - ok, so I downloaded this update (that I should have received OTA having it being released in July - but I didn't), nay no, I had to download the WW 2.20.40.196 release (as the 194 wasn't available), I tryed to do the update but I got the very same error and the same broken green robot after rebooting - and lucky again it wasn't started anything so I could go back to dear old LOLLIPOP.
Note, the phone is not ROOTED I was waiting the MM upgrade to do so.
CAN SOMEONE HELP? (I COME FROM 5 YEARS OF SAMSUNG AND HUAWEI UPDATING / ROOTING / MODDING WITHOUT ANY KIND OF PROBLEMS)
This may possibly be more than you need. But, it will work for you. https://www.asus.com/zentalk/in/thread-100891-1-1.html
Sent from my ASUS_Z00AD using Tapatalk
mikeletron said:
Hi, in early September I started checking the OTA update notification to MM in my recently purchased ZENFONE 2 551ML (4/64GB): NOTHING - then I tried to do it manually, I downloaded the file from the ASUS website (V4.21.40.134) and follow the instructions, once I copied the zip file in the internal memory I found the notification and: did the update started? No, the phone rebooted and after a few seconds I saw a broken green robot with the word ERROR, ok, back to Lollipop, I double checked and saw a note "Before attempting the manual update, please make sure you are updated to V2.20.40.194 or later via the System Update app." while I still have WW 2.20.40.184 - ok, so I downloaded this update (that I should have received OTA having it being released in July - but I didn't), nay no, I had to download the WW 2.20.40.196 release (as the 194 wasn't available), I tryed to do the update but I got the very same error and the same broken green robot after rebooting - and lucky again it wasn't started anything so I could go back to dear old LOLLIPOP.
Note, the phone is not ROOTED I was waiting the MM upgrade to do so.
CAN SOMEONE HELP? (I COME FROM 5 YEARS OF SAMSUNG AND HUAWEI UPDATING / ROOTING / MODDING WITHOUT ANY KIND OF PROBLEMS)
Click to expand...
Click to collapse
According to the ASus site, you need to be at least ver 184 to upgrade to MM. So according to the asus site you are good to go for MM.
I did upgrade to MM from 194 though. Here is the link for 194.
Since you are saying that you did not find 194, you might be looking in the wrong directory.
Here is the link for the MM update. I am sure you have the correct firmware.
Dead robot with red triangle and error message sometime happened when you were trying to go to recovery or the phone trying to go to the recovery. To go to the recovery from the dead robot.
You need to press and hold the power button, and quickly press and release the volume-up button. The phone should go to the recovery if you still have the stock recovery. Sometime you need to click that volume-up button several times while you holding the power button to go into the recovery mode.
Since you are familiar with samsung and Huawei, you could use adb reboot recovery to go the recovery mode. However, if you see the dead robot and error you have to go through the above method.
Once you were in the recovery, you can use adb sideload to install the MM firmware.
mikeletron said:
Hi, in early September I started checking the OTA update notification to MM in my recently purchased ZENFONE 2 551ML (4/64GB): NOTHING - then I tried to do it manually, I downloaded the file from the ASUS website (V4.21.40.134) and follow the instructions, once I copied the zip file in the internal memory I found the notification and: did the update started? No, the phone rebooted and after a few seconds I saw a broken green robot with the word ERROR, ok, back to Lollipop, I double checked and saw a note "Before attempting the manual update, please make sure you are updated to V2.20.40.194 or later via the System Update app." while I still have WW 2.20.40.184 - ok, so I downloaded this update (that I should have received OTA having it being released in July - but I didn't), nay no, I had to download the WW 2.20.40.196 release (as the 194 wasn't available), I tryed to do the update but I got the very same error and the same broken green robot after rebooting - and lucky again it wasn't started anything so I could go back to dear old LOLLIPOP.
Note, the phone is not ROOTED I was waiting the MM upgrade to do so.
CAN SOMEONE HELP? (I COME FROM 5 YEARS OF SAMSUNG AND HUAWEI UPDATING / ROOTING / MODDING WITHOUT ANY KIND OF PROBLEMS)
Click to expand...
Click to collapse
Just download the zip from Asus.com then rename to mofd_sdupdate.zip, put it in the root directory of internal storage, reboot your phone to recovery then it will do everything automatically. Use this method to update to lastest 5.0, then MM. No need to type adb commands

Cannot get to download mode. Phone working fine.

I want to flash a custom rom but unable to install recovery because I'm on Android 6.0 and have no root.
Tried to root with 1 click but realized later that it doesn't work with 6.0
So now I'm following a procedure to downgrade to Android 5 but unable to get into download.
When I press volume up and plug in the phone it shows me a screen with a white phone and yellow triangle like this one (https://images-na.ssl-images-amazon.com/images/I/61JPlI0IYWL._SL256_.jpg).
Also when I try to do it through "adb reboot download" the phone just reboots and goes back to OS.
What are my options here?
Thank you in advance.
pashunka said:
I want to flash a custom rom but unable to install recovery because I'm on Android 6.0 and have no root.
Tried to root with 1 click but realized later that it doesn't work with 6.0
So now I'm following a procedure to downgrade to Android 5 but unable to get into download.
When I press volume up and plug in the phone it shows me a screen with a white phone and yellow triangle like this one (https://images-na.ssl-images-amazon.com/images/I/61JPlI0IYWL._SL256_.jpg).
Also when I try to do it through "adb reboot download" the phone just reboots and goes back to OS.
What are my options here?
Thank you in advance.
Click to expand...
Click to collapse
First of all could you please tell me what LG G3 Model are you?(example: D855)and also what "V" (version) of Marshmallow (example:v30c).
They are needed to proceed at downgrading or even rooting immediately without downgrading.(KingRoot is the one that is working well)
Sotiris02 said:
First of all could you please tell me what LG G3 Model are you?(example: D855)and also what "V" (version) of Marshmallow (example:v30c).
They are needed to proceed at downgrading or even rooting immediately without downgrading.(KingRoot is the one that is working well)
Click to expand...
Click to collapse
Hey
Thanks for quick reply.
It's D852
Software verion: D85230d
Android 6.0
Kernel 3.4.0
I hope this is what you need
pashunka said:
Hey
Thanks for quick reply.
It's D852
Software verion: D85230d
Android 6.0
Kernel 3.4.0
I hope this is what you need
Click to expand...
Click to collapse
Did you try installing "King Root"( NOT "Kingo Root"!)to your Device?
If you've downloaded king root and it didn't give a positive answer then downgrade will be required to Root.
Downgrading Guide​
Not necessary
Before starting you may need to backup your photos,etc.
Go to Settings then "Backup and Reset" then you will see "LG Backup" click on it and make the backup.After all these steps move your backup file to your SD Card or to your PC.(Go to File Explorer then to the folder "LG backups")
So let's go on..!
Go here and select the one of them(they are the same) But if you already have a kdz file then bypass his
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/Canada+D852/MM+6.0/
Then go over here
http://forum.xda-developers.com/showthread.php?t=2785089
And scroll down to "How to flash ROM kdz method"
Enable USB debugging
https://www.recovery-android.com/enable-usb-debugging-on-android.html#part1
Connect your phone to your PC
Download LG drivers(Not Verizon one's!)
Download Lguptool, unzip it,open the folder and inside of it where all the lguptool files are located move the kdz file that you downloaded.
Open lguptool with admin prompt!
Select type CMDA and phone mode DIAG
Select the kdz file and click "CSE Flash"
Then click "start"
A menu will appear,select language and click "Ok"
After all these steps you will need to wait till the phone boots.
Then you will be able to root your phone(King root) and flash TWRP and ROMs!
If you also want a guide on how to get SuperSU after getting Root access from King Root,then just tell me and I'll reply as fast as i can.
Greetings and Good luck!
Thank you! I will try this right now.
But this KBZ file is for MM no? Wouldn't I need one for Lollipop?
pashunka said:
Thank you! I will try this right now.
But this KBZ file is for MM no? Wouldn't I need one for Lollipop?
Click to expand...
Click to collapse
It's Marshmallow one.Because "v30b" of marshmallow is Rootable.
Sotiris02 said:
It's Marshmallow one.Because "v30b" of marshmallow is Rootable.
Click to expand...
Click to collapse
OK that makes sense.
I tried the KingRoot but no luck, so will try the second method.
I'm having issues with windows recognizing my phone... says "usb device descriptor request failed". I tried installing/reinstalling LG drivers, still have issues. Funny thing is it worked not too long ago... Same happens on another Win10 machine.
Once I figure it out I will try your 2nd method.
Thanks a lot!
Sotiris02 said:
It's Marshmallow one.Because "v30b" of marshmallow is Rootable.
Click to expand...
Click to collapse
Looks like I still have issues with USB. I finally got it to recognize the device but when LGUP reboots the phone it again says "device not recognized".... no clue what the problem with USB is...
pashunka said:
Looks like I still have issues with USB. I finally got it to recognize the device but when LGUP reboots the phone it again says "device not recognized".... no clue what the problem with USB is...
Click to expand...
Click to collapse
The phone boots or not?
Windows 10 have always been problematic...(program error's etc etc.)That's why i stick on Windows 7 ultimate
Don't you have a "Internet cafe" or a place where you can use a PC nearby(that hasWindows 7.)
Sotiris02 said:
The phone boots or not?
Windows 10 have always been problematic...(program error's etc etc.)That's why i stick on Windows 7 ultimate
Don't you have a "Internet cafe" or a place where you can use a PC nearby(that hasWindows 7.)
Click to expand...
Click to collapse
Yeah the phone works fine. It is Windows 10...
I might install W7 quickly to try it...
Sotiris02 said:
It's Marshmallow one.Because "v30b" of marshmallow is Rootable.
Click to expand...
Click to collapse
So I finally made it work, there was a problem with USB port on the phone.
Now how do I reboot to recovery?
I rooted with KingRoot and installed SuperSU from play market and TWRP recovery from the app.
When I reboot it doesn't go to recovery, I assume because KingRoot gives temp root? I downloaded reboot app to go to recovery but when it reboots it just flashed the LED light.
pashunka said:
So I finally made it work, there was a problem with USB port on the phone.
Now how do I reboot to recovery?
I rooted with KingRoot and installed SuperSU from play market and TWRP recovery from the app.
When I reboot it doesn't go to recovery, I assume because KingRoot gives temp root? I downloaded reboot app to go to recovery but when it reboots it just flashed the LED light.
Click to expand...
Click to collapse
FYI,
I tried this so far with no luck:
1) Tried this script. It removed KingRoot and at the end when it installs SuperSU it fails to update binaries. Tried this multiple times
2) Installed Super-Sume app but it just sits and does nothing. Tried different versions.
3) I read that there is AutoRec for D852 but the link does not work and I can't find a copy (https://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396)
Do I even need to install SuperSU? I just want to flash a different ROM but cannot get into recovery because Kingroot is temporary.
So I gave up on KingRoot.
Just downgraded with LGUP using old .TOT Lollipop file, rooted and installed custom ROM.

ANDROID 10 with MAGISK ROOT working on s10+

*****This was done on an EXYNOS s10+ SM-G975F*****
All you have to do is download the firmware
Get the AP file
Patch it with MAGISK
then take the patched file and flash it in place of the AP file WITH THE REST OF THE FIRMWARE FILES with ODIN
But make sure you uncheck auto reboot
Then when you are done flashing turn if off
The turn it on holding the recovery buttons till the first screen comes back for a couple seconds the let go
You should now have ANDROID 10 (Q) rooted with MAGISK
Enjoy
Taking this one step further, would we be able to insert a twrp image into the AP file so that we also have TWRP installed? Or is it incompatible?
I might try this later.
Really? its good news. But is battery life any better in Android Q?
need to unlock oem or not ?
tofayas said:
need to unlock oem or not ?
Click to expand...
Click to collapse
1- unlock oem
2- unlock Bootloader
3- root
can we patch twrp too and pu that in the ap file?
Has anyone managed to root Android10 but without losing data?
Tried it but ended up with bootloop: Unable to disable quotas on /dev/block/platform/13d60000.ufs/by-name/userdata because /system/bin/tune2fs is missing. Followed instructions exactly. Pathed image, moved image to odin along with the other files, flashed, passed, turned off and started with recovery buttons.
Need to press and hold buttons in order to start device in rooted mode each time you restart or power off and power on device??
ShahbazParviez said:
Need to press and hold buttons in order to start device in rooted mode each time you restart or power off and power on device??
Click to expand...
Click to collapse
Yes,
Player04 said:
Yes,
Click to expand...
Click to collapse
This what i don't want. I believe mostly people don't like this method too. Device must be work in normal mode with root and key combination to enter in recovery mode.
ShahbazParviez said:
This what i don't want. I believe mostly people don't like this method too. Device must be work in normal mode with root and key combination to enter in recovery mode.
Click to expand...
Click to collapse
hi. you meant its not working in root mode after restart if we dont press the combination button ? Is android 9 same thing ? Sorry still new with Magisk things
I mean you have to press several buttons to enter in rooted mode after rooting your device and it's obviously not a good way.
Does this work with the latest Android 10 stable build? Can anyone confirm please?
I wonder the same thing...... Does this work with the latest stable version of Android 10? Can anyone please confirm?
Merry Christmas ALL!!
Anyone had tried upgrading to Android 10 successfully?
Thank you.
Link from Gofile are down.
Fix this....
iamsyh said:
Does this work with the latest Android 10 stable build? Can anyone confirm please?
Click to expand...
Click to collapse
yes, work
hi. i was running android 9 rooted and i decided to upgrade to android 10. i also included twrp in the installation using magisk and patching the AP file.
The first boot was fine. i had to reboot the phone and now if i start with root, i can't unlock the screen, i put the pin,it gives black screen and then pin request again. i rebooted with no root (same problem). i wiped the cache and now i can use phone if i start without root. i tried to remove pin and fingerprint, but anyway if i start with root i cannot use phone, it goes in bootloop after the unlock screen.
Any suggestion?
thank
81! said:
*****This was done on an EXYNOS s10+ SM-G975F*****
All you have to do is download the firmware
Get the AP file
Patch it with MAGISK
then take the patched file and flash it in place of the AP file WITH THE REST OF THE FIRMWARE FILES with ODIN
But make sure you uncheck auto reboot
Then when you are done flashing turn if off
The turn it on holding the recovery buttons till the first screen comes back for a couple seconds the let go
You should now have ANDROID 10 (Q) rooted with MAGISK
Enjoy
Click to expand...
Click to collapse
Which firmware?
Get AP file from where?
Which Magisk?
Sorry, new to S10 and no links showing.
Thank you

Categories

Resources