Database Users

Recovery Question (TWRP 3.0.0-1)

Quick question:
I am very used to flashing so this isn't new to me. I recently updated to android build MHC19I. I'm use to the "lock your bootloader" warning, but now that I'm on TWRP 3.0.0-1, I'm also receiving the "your device is corrupt" warning. Now this doesn't seem to affect day to day use, so I don't seem to care, but am I doing something wrong? I usually wouldn't receive that message.
Thanks!

dbroer91884 said:
Quick question:
I am very used to flashing so this isn't new to me. I recently updated to android build MHC19I. I'm use to the "lock your bootloader" warning, but now that I'm on TWRP 3.0.0-1, I'm also receiving the "your device is corrupt" warning. Now this doesn't seem to affect day to day use, so I don't seem to care, but am I doing something wrong? I usually wouldn't receive that message.
Thanks!
Click to expand...
Click to collapse
Have you flashed SuperSU since flashing this version of TWRP? I haven't been able to pinpoint the cause of this message, but I believe it occurs when you have a modified /system partition (from installing TWRP). If I recall correctly (I had it a while ago) flashing SuperSU seemed to get rid of it. Could be a coincidence but that was my experience.

Heisenberg said:
Have you flashed SuperSU since flashing this version of TWRP? I haven't been able to pinpoint the cause of this message, but I believe it occurs when you have a modified /system partition (from installing TWRP). If I recall correctly (I had it a while ago) flashing SuperSU seemed to get rid of it. Could be a coincidence but that was my experience.
Click to expand...
Click to collapse
Here is the crazy thing.
So I hadn't flashed anything but TWRP, didn't modify the system partition at all, and that message would come up. I then flashed the latest Pure Nexus (actually then removed Root) and the message is now back to just the relock the bootloader message. I checked what build was used in that rom, and it is some crazy build (MHC19J) which isn't even available on the the Android Factory Images site. So I don't really know. As of now though, I'm just back to the normal lock your bootloader message.

dbroer91884 said:
Here is the crazy thing.
So I hadn't flashed anything but TWRP, didn't modify the system partition at all, and that message would come up. I then flashed the latest Pure Nexus (actually then removed Root) and the message is now back to just the relock the bootloader message. I checked what build was used in that rom, and it is some crazy build (MHC19J) which isn't even available on the the Android Factory Images site. So I don't really know. As of now though, I'm just back to the normal lock your bootloader message.
Click to expand...
Click to collapse
TWRP itself modifies the system partition in order to persist through reboots, I believe this is what causes the message to appear.

I think the Warnung is only red then the vendor image with the cert.check goes wrong the mhc19j is the last march build from the nexus5x and the devs changed the Rom for the angler- so try to flash the vendor image Märchen from Angler the mhc19i and the Rom certificate check goes right and the yellow Warnung is back.....i had for a few days the same Problem.... Download the vendor in the Rom thread and flsh it with wugs toolkit and then reboot.... Sry for my terrible english

[Updata]WW-4.21.40.223(andriod M)

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

Help with new update and Magisk

Hey guys
so initially i rooted partition B using magisk now i got the new update of 75mb. I switched to partition A where it was still on august security patch and i made update of 1gb followed by 75mb update.
So i switched back to partition B and it was unrooted but the update did not install on this partition and told me to make update of 75mb again but i tired to update and it gave me an error but safetynet was not passed ctsproilfe:false
can someone help me? i tried to flash boot.img of stock but same result.

faddys123 said:
Hey guys
so initially i rooted partition B using magisk now i got the new update of 75mb. I switched to partition A where it was still on august security patch and i made update of 1gb followed by 75mb update.
So i switched back to partition B and it was unrooted but the update did not install on this partition and told me to make update of 75mb again but i tired to update and it gave me an error but safetynet was not passed ctsproilfe:false
can someone help me? i tried to flash boot.img of stock but same result.
Click to expand...
Click to collapse
I ended up having to flash the previous Oct (7.10.14) fastboot ROM using MiFlash, rebooted back into the stock ROM and then took the single 1GB OTA update which has the Oct 30 kernel and build number. Booted into TWRP and reflashed Magisk 14.4 and Safetynet passed.
BTW, did you try booting into partition A and check whether the Oct 30 kernel and build OTA (75MB) update was installed? Just thinking this might be the case since you took 2 OTA updates.

cmk7128 said:
I ended up having to flash the previous Oct (7.10.14) fastboot ROM using MiFlash, rebooted back into the stock ROM and then took the single 1GB OTA update which has the Oct 30 kernel and build number. Booted into TWRP and reflashed Magisk 14.4 and Safetynet passed.
BTW, did you try booting into partition A and check whether the Oct 30 kernel and build OTA (75MB) update was installed? Just thinking this might be the case since you took 2 OTA updates.
Click to expand...
Click to collapse
using miflash did you do this without the data being wiped?

faddys123 said:
using miflash did you do this without the data being wiped?
Click to expand...
Click to collapse
I selected the "save user data" option before flashing in MiFlash but somehow all my data was erased when the phone rebooted. Not sure why that happened.

cmk7128 said:
I selected the "save user data" option before flashing in MiFlash but somehow all my data was erased when the phone rebooted. Not sure why that happened.
Click to expand...
Click to collapse
if i just download the stock rom extract boot.img and system.img and flash manually via fastboot it should return to stock? with my app data etc still intact then i can run the update and then flash magisk for root?

faddys123 said:
if i just download the stock rom extract boot.img and system.img and flash manually via fastboot it should return to stock? with my app data etc still intact then i can run the update and then flash magisk for root?
Click to expand...
Click to collapse
Not sure, but worth a try. What about booting from partition A?

cmk7128 said:
Not sure, but worth a try. What about booting from partition A?
Click to expand...
Click to collapse
i booted into A and it is updated with build 30 oct not rooted, but if i root this using new magisk 14.4 for future updates i won't be able to update and partition b is still on update from 14 oct

faddys123 said:
i booted into A and it is updated with build 30 oct not rooted, but if i root this using new magisk 14.4 for future updates i won't be able to update and partition b is still on update from 14 oct
Click to expand...
Click to collapse
If I am not mistaken, you can boot into partition B (which is unrooted) for future OTA updates. Being on 7.10.14 updates would just mean the OTA files will be bigger in size compared to the OTA file for updates from 30 Oct?

Yesterday, I run into problems updating my phone to 30 oct version too. At the end I stuck into bootloops. This is how I solved it:
- boot into fastbootmode
- flash 14 oct Image with MiFlash (option: save user data)
- reboot
- download and install update 30 oct
- reboot into fastbootmode
- fastboot oem unlock
- fastboot boot recovery.img
- flash Magisk 14.4
- reboot Phone

cmk7128 said:
If I am not mistaken, you can boot into partition B (which is unrooted) for future OTA updates. Being on 7.10.14 updates would just mean the OTA files will be bigger in size compared to the OTA file for updates from 30 Oct?
Click to expand...
Click to collapse
well partition B was the one originally rooted, but i could not install the new update, so switched partition to A and did the update but booting into partition b still has build of 14th oct whereas partition A (unrooted) is on 30th oct build. so both partitions are not getting updated together

Screen Blinking After stable Pie Fota

Today I updated my Asus Zenfone max Pro M2 to pie via fota update.
After successful installation the phone rebooted,
And then the thing happened, screen keeps blinking.
Any suggestions? I have 6gb varient

Fix for screen blinking after pie stable fota update
Vikassir33 said:
Today I updated my Asus Zenfone max Pro M2 to pie via fota update.
After successful installation the phone rebooted,
And then the thing happened, screen keeps blinking.
Any suggestions? I have 6gb varient
Click to expand...
Click to collapse
1.First unlock the bootloader of your phone.
2.Download Oreo fastboot rom raw zip file.
3.Install the necessary drivers and platform tools in your laptop.
4. Extract the rom zip file.
5. Copy all contained files in the rom file and paste in the platform tools folder.
6.Now enable usb debugging and connect phone to the laptop.
7.Enter the platform tools folder and open cmd and write "adb reboot bootloader"
8. Now once you are in fastboot mode double click on Flash_All.cmd in platform tools.
9.After that you will boot your system in oero build .
10.Now final stem check for system updates and you will get a fota update arround 800mb
11.After the update done you are good to go.
12. For further any quarry you can contact me(Whatsapp+call) : 8670647386 Gmail: [email protected]
WARNING!! : 1. DO NOT UPDATE IN PIE AFTER 800mb UPDATE UNTILTHE NEXT PIE UPDATE IS COMMING.
2. ANY MISTAKE CAN BRICK YOUR DEVICE I WILL NOT BE RESPONSIBLE FOR THIS.
All the links and screenshots will be given tomorrow.

subhojit2016 said:
1.First unlock the bootloader of your phone.
2.Download Oreo fastboot rom raw zip file.
3.Install the necessary drivers and platform tools in your laptop.
4. Extract the rom zip file.
5. Copy all contained files in the rom file and paste in the platform tools folder.
6.Now enable usb debugging and connect phone to the laptop.
7.Enter the platform tools folder and open cmd and write "adb reboot bootloader"
8. Now once you are in fastboot mode double click on Flash_All.cmd in platform tools.
9.After that you will boot your system in oero build .
10.Now final stem check for system updates and you will get a fota update arround 800mb
11.After the update done you are good to go.
12. For further any quarry you can contact me(Whatsapp+call) : 8670647386 Gmail: [email protected]
WARNING!! : 1. DO NOT UPDATE IN PIE AFTER 800mb UPDATE UNTILTHE NEXT PIE UPDATE IS COMMING.
2. ANY MISTAKE CAN BRICK YOUR DEVICE I WILL NOT BE RESPONSIBLE FOR THIS.
All the links and screenshots will be given tomorrow.
Click to expand...
Click to collapse
Fastboot ROM?????? Where can we get fastboot ROM from? I am searching from last few days, but I didn't get the fastboot ROM.

nice_guy75 said:
Fastboot ROM?????? Where can we get fastboot ROM from? I am searching from last few days, but I didn't get the fastboot ROM.
Click to expand...
Click to collapse
Download This Version WW-15.2016.1812.179 OR WW-15.2016.1901.186 (revert back to oreo from android p)

RedRobbin said:
Download This Version WW-15.2016.1812.179 OR WW-15.2016.1901.186 (revert back to oreo from android p)
Click to expand...
Click to collapse
@RedRobbin
There are no active links,

The blinking problem solved by itself, I don't know what changed, but now no blinking any more

Vikassir33 said:
The blinking problem solved by itself, I don't know what changed, but now no blinking any more
Click to expand...
Click to collapse
Sadly my phone is still giving me this screen blinking issue.
Anything you remember particularly doing before your phone was fixed?

nice_guy75 said:
@RedRobbin
There are no active links,
Click to expand...
Click to collapse
You can download from official website its size around 1.7 gb

RedRobbin said:
You can download from official website its size around 1.7 gb
Click to expand...
Click to collapse
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
Sent from my ASUS_X01BDA using Tapatalk

Is there a technical reason why you can rollback to the last month's ROM from the Asus website with the stock recovery? Has the filesystem changed or something?

nice_guy75 said:
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
-- Flash stock recovery
-- Put downloaded zip file into external SD
-- Boot into stock recovery
-- Apply update from external storage and locate file
-- done
Click to expand...
Click to collapse

RedRobbin said:
nice_guy75 said:
Official site does not have fastboot ROM, those zips are meant to be flashed via stock recovery.
-- Flash stock recovery
-- Put downloaded zip file into external SD
-- Boot into stock recovery
-- Apply update from external storage and locate file
-- done
Click to expand...
Click to collapse
That I know, I wanted to have Fastboot ROM, which can be flashed via PC.
Click to expand...
Click to collapse

I tried to install the laat Oreo ROM from the Asus website using stock recovery but it failed with a message something like, you can't flash an older version than the one installed.

damole said:
Is there a technical reason why you can rollback to the last month's ROM from the Asus website with the stock recovery? Has the filesystem changed or something?
Click to expand...
Click to collapse
Dear simply visit any Asus service center they will downgrade it to Oreo, I visited today, and one interesting thing is they don't have any stable update for now . Soon a newer fota update will release.

damole said:
I tried to install the laat Oreo ROM from the Asus website using stock recovery but it failed with a message something like, you can't flash an older version than the one installed.
Click to expand...
Click to collapse
First flash twrp then wipe everything except sd card and then flash stock recovery and try again

I posted here about the issues I had. I know that at first the problem is the old firmware can't be installed over newer firmware, when I fix that problem the zip package is no longer signed correctly.
Please could you explain why the method you suggest will work.

Yes it's work i done with 2 max pro m2

damole said:
I posted here about the issues I had. I know that at first the problem is the old firmware can't be installed over newer firmware, when I fix that problem the zip package is no longer signed correctly.
Please could you explain why the method you suggest will work.
Click to expand...
Click to collapse
In case of system update failure the zip file you are trying to flash will be corrupted. (Happened with me many times as i renamed the oreo stock rom to above the build number of the pie update so my phone would treat the downloaded oreo rom to be new .but during the system update after reaching aroung 25 % it displayed an error and the next thing i remember is the zip file getting corrupted) so always keep a backup!
On 25th of april new pie update was released which fixed screen blinking issue.

Problem sideloading June update QQ3A.200605.001

Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.

SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I downloaded the OTA package from the Google page,and dirty flashed over my qq2a with no problems.
Sent from my Pixel 2 XL using Tapatalk

That's what I've always done. And this time it won't take it
Sent from my Pixel 2 XL using Tapatalk

I must have screwed something up at some point. I figured it out. I upgraded using the factory image and eliminated the -w command from the flash all script so it didn't wipe my phone.

SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I was having the same issue. I was running a stock rom with the may update . After several tries I desisted and check for updates in the phone and the june ota installed successfully

SuperShadow1021 said:
I must have screwed something up at some point. I figured it out. I upgraded using the factory image and eliminated the -w command from the flash all script so it didn't wipe my phone.
Click to expand...
Click to collapse
I've been removing the -w from the factory images for a few months now. Too much trouble to do a clean flash and I saw no real benefit from the clean flash so I stopped. June update flashed for me just fine.

I was having the same issue. I was running a stock rom with the may update

Check and see that platform tools and all of your driver's are upto date

Solution that work for me
SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I have also face same issue while sideloading June OTA than after lot of searching i found fully working solution.
I am assuming you have not flashed Custom recovery (i usually only boot Custom recovery so that i can sideload ota update using Stock Recovery)
Now connect you phone (USB Debugging: On)
Command: adb devices
Your device must show up in Command prompt
2nd command: adb reboot bootloader
Must be boot into fastboot mode
Now as pixel 2 xl has A/B partition so we have to check active partition first then have to change to another.
To check active slot
3rd command: fastboot getvar current-slot
To change active slot
4th command:
if your active slot is "a"
fastboot --set-active=b
OR
if your active slot is "b"
fastboot --set-active=a
Now reboot to stock recovery (please do not boot into system)
5th Command: fastboot reboot recovery
Now select "apply update from adb"
Once again check for device connection, must show as sideload, then....
Command: adb sideload [filename]
Please replace [filename] with the OTA .zip file you have downloaded.
Ex: adb sideload c:\user\name\Desktop\taimen-ota-qq3a.200605.001-992633c8.zip
Now this should work, as it works for me.
Sorry for detailed instructions, i am pretty sure you already know the basic commands but I just want to post it as guide for everyone.
My First reply on XDA, Happy to help you.