Develop Bugs

[Q] Why does root cause bootloop??

Just a question that jumped out of curiosity.
Why does the Zenfone bootloop on applying OTA on rooted firmware??
The 2.18 OTA zip has patch files to system apps. I dont see why it should cause bootloop on a rooted device which has all the system apps intact?
And on unrooting, OTA works perfectly. What is the reason?? How does the OTA zip understand that the device has been rooted even if no system apps have been tampered with?
Anyone with knowledge on this please post your reply.
Thank you in advance.

black.pearl said:
Just a question that jumped out of curiosity.
Why does the Zenfone bootloop on applying OTA on rooted firmware??
The 2.18 OTA zip has patch files to system apps. I dont see why it should cause bootloop on a rooted device which has all the system apps intact?
And on unrooting, OTA works perfectly. What is the reason?? How does the OTA zip understand that the device has been rooted even if no system apps have been tampered with?
Anyone with knowledge on this please post your reply.
Thank you in advance.
Click to expand...
Click to collapse
Its probably an OEM root check at runtime, if runtime detects an SU binary the zygote runtime will halt, this could be confirmed with a logcat while booting, its a guess here but im pretty sure thats whats going on.

does this always happen? i mean, is there a way to root the device without getting a boot loop after applying OTA?

SquallDNA said:
does this always happen? i mean, is there a way to root the device without getting a boot loop after applying OTA?
Click to expand...
Click to collapse
I think the other question to be asked is why a fresh install of the pre-rooted firmware allows an OTA to go through with no problems...
I have installed a pre-rooted image on 2 phones now and then done the OTA update.
It seems to check for something altering the system AFTER the firmware is flashed as a pre-rooted firmware does in fact have supersu already installed and will allow the OTA update to work (or at least that has been my experience with 2.18.40.X and 2.19.40.18.).

ultramag69 said:
I think the other question to be asked is why a fresh install of the pre-rooted firmware allows an OTA to go through with no problems...
I have installed a pre-rooted image on 2 phones now and then done the OTA update.
It seems to check for something altering the system AFTER the firmware is flashed as a pre-rooted firmware does in fact have supersu already installed and will allow the OTA update to work (or at least that has been my experience with 2.18.40.X and 2.19.40.18.).
Click to expand...
Click to collapse
what happened after OTA update? did it went boot looping?
asus obviously doesn't want thier devices rooted.

Booted fine, no bootloop or other problems and updated to latest firmware. Either I lucked out and got 2 aberrant Zenfone 2's that update fine with the pre-rooted image or there is some other factor involved.
Just a quick note, I re-flashed a pre-rooted image over the old system. It was the same firmware version, 19.40.18 over 19.40.18 so it essentially just reset to how the pre-rooted image was before supersu was updated. OTA worked fine like this.

ultramag69 said:
Booted fine, no bootloop or other problems and updated to latest firmware. Either I lucked out and got 2 aberrant Zenfone 2's that update fine with the pre-rooted image or there is some other factor involved.
Just a quick note, I re-flashed a pre-rooted image over the old system. It was the same firmware version, 19.40.18 over 19.40.18 so it essentially just reset to how the pre-rooted image was before supersu was updated. OTA worked fine like this.
Click to expand...
Click to collapse
that's awesome. which variant of zf2 do you have? i'm using 551 2gb 1.8ghhz variant under 2.19.40.22.. if you dont mind, can i have the exact same root tutorial you followed?

SquallDNA said:
that's awesome. which variant of zf2 do you have? i'm using 551 2gb 1.8ghhz variant under 2.19.40.22.. if you dont mind, can i have the exact same root tutorial you followed?
Click to expand...
Click to collapse
I have a 4gb 64gb 2.3ghz and a 4gb 32gb 1.8ghz zenfone 2. Both work fine. As I said though I have unlocked the bootloader and rooted prior to doing it this way. It may be the bootloader goes through a check.
Way I rooted was to install the pre-rooted image a long time ago but when I have OTA'd I used the temporary CWM to reroot with latest supersu.
Once I found we could put TWRP on the Zenfone 2 I unlocked the bootloader and then installed TWRP 2.8.7.0(?) though I believe reflashing the pre-rooted image back on may have removed this.
I was using this for a while when the new OTA came out. As I had updated SuperSU I reflashed the pre-root image for the firmware installed (I believe it was 2.19.40.18) then installed the OTA from settings.
When the OTA came out for 2.19.40.22 I reflashed the pre-rooted image on again (2.19.40.20 this time) and then ran the OTA update from the settings again. No boot-loops or anything else wrong... Been running fine since on both though I got the flashing bug and flashed the custom rom SuperZen on my 1.8ghz 32gb Zenfone 2. Again no problems but I haven't tried reverting that back yet...

ultramag69 said:
I have a 4gb 64gb 2.3ghz and a 4gb 32gb 1.8ghz zenfone 2. Both work fine. As I said though I have unlocked the bootloader and rooted prior to doing it this way. It may be the bootloader goes through a check.
Way I rooted was to install the pre-rooted image a long time ago but when I have OTA'd I used the temporary CWM to reroot with latest supersu.
Once I found we could put TWRP on the Zenfone 2 I unlocked the bootloader and then installed TWRP 2.8.7.0(?) though I believe reflashing the pre-rooted image back on may have removed this.
I was using this for a while when the new OTA came out. As I had updated SuperSU I reflashed the pre-root image for the firmware installed (I believe it was 2.19.40.18) then installed the OTA from settings.
When the OTA came out for 2.19.40.22 I reflashed the pre-rooted image on again (2.19.40.20 this time) and then ran the OTA update from the settings again. No boot-loops or anything else wrong... Been running fine since on both though I got the flashing bug and flashed the custom rom SuperZen on my 1.8ghz 32gb Zenfone 2. Again no problems but I haven't tried reverting that back yet...
Click to expand...
Click to collapse
thanks man. i found this, http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596, and i believe you used the 1st method of rooting. i prefer using the 3rd method.

SquallDNA said:
thanks man. i found this, http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596, and i believe you used the 1st method of rooting. i prefer using the 3rd method.
Click to expand...
Click to collapse
I used both 1 and 3... Flashed pre-rooted image then downloaded OTA using system settings and flashed with system update. Didn't download the OTA and copy tophone as system update did this for me...

SquallDNA said:
what happened after OTA update? did it went boot looping?
asus obviously doesn't want their devices rooted.
Click to expand...
Click to collapse
I do not think so.
Why would Asus bother with what YOU do with YOUR phone.
Bootloops are caused if you delete something from the /system directory or modify something on which the system depends upon (e.g. v4a, busybox, etc)
As long as you do not touch any system stuff, Asus wouldn't bother. If they wanted their phones to strictly remain untouched, they wouldn't have released bootloader unlocking tools for the previous gen devices.

[email protected] said:
I do not think so.
Why would Asus bother with what YOU do with YOUR phone.
Bootloops are caused if you delete something from the /system directory or modify something on which the system depends upon (e.g. v4a, busybox, etc)
As long as you do not touch any system stuff, Asus wouldn't bother. If they wanted their phones to strictly remain untouched, they wouldn't have released bootloader unlocking tools for the previous gen devices.
Click to expand...
Click to collapse
They haven't released bootloader unlock tool for the Zenfone 2. By your logic they do care until they release that, then it should no longer matter...

What Steps Do I Take To Update From 2.19.40.20?

So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?

I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.

So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse

Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.

I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse

Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.

DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?

Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.

Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse

Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.

So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?

Is it safe to update M8 to marshmallow?

Hi friends, I am getting notifications to update my M8 to marshmallow.Its with unlocked bootloader,rooted and with S-OFF and running stock rom.Currently its running Android 5.0.1 with Htc sense version 6.0 on a Rogers(canadian) network.Will it be safe to update it to marshmallow?Will i be able to root it afterwards?Any suggestions please?Thanks

You will need an unrooted (never rooted) stock Rogers ROM, and corresponding stock recovery, in order to update by OTA.
Otherwise, there haven't been any issues reported (such as root) with Marshmallow. Root requires a newer version SuperSU (2.51 or later), but otherwise there aren't any major issues.

redpoint73 said:
You will need an unrooted (never rooted) stock Rogers ROM, and corresponding stock recovery, in order to update by OTA.
Otherwise, there haven't been any issues reported (such as root) with Marshmallow. Root requires a newer version SuperSU (2.51 or later), but otherwise there aren't any major issues.
Click to expand...
Click to collapse
Thanks redpoint! what if i unroot my M8 first and then take OTA update?Will it be fine?

ninja_zx11 said:
Thanks redpoint! what if i unroot my M8 first and then take OTA update?Will it be fine?
Click to expand...
Click to collapse
Nope, unrooting won't work OTA will still fail). I specified never rooted for that reason.
You can use a TWRP backup, if you made one before rooting. Otherwise, you'll need to find a stock (unrooted) TWRP backup on the forums.

redpoint73 said:
Nope, unrooting won't work OTA will still fail). I specified never rooted for that reason.
You can use a TWRP backup, if you made one before rooting. Otherwise, you'll need to find a stock (unrooted) TWRP backup on the forums.
Click to expand...
Click to collapse
I have a copy of final lollipop OTA zip file which i used last time 3-4 months ago.Can i use that?File is "OTA_M8_UL_L50_SENSE60_MR_Rogers_WWE_4.20.631.2-3.34.631.4_release".

ninja_zx11 said:
I have a copy of final lollipop OTA zip file which i used last time 3-4 months ago.Can i use that?File is "OTA_M8_UL_L50_SENSE60_MR_Rogers_WWE_4.20.631.2-3.34.631.4_release".
Click to expand...
Click to collapse
I'm not sure what you are asking. You can't run the OTA as-is, in order to return to stock ROM, if that is what you mean. This will fail for the same reason a Marshmallow OTA will fail (due to modified software) in addition that version check will probably also make it fail (you can't OTA to the same version already on the phone).
You might be able to extract the ROM for the zip file. But this can be risky, too. Its best you find a previously posted TWRP backup of the stock ROM; or ask someone to post it.

redpoint73 said:
I'm not sure what you are asking. You can't run the OTA as-is, in order to return to stock ROM, if that is what you mean. This will fail for the same reason a Marshmallow OTA will fail (due to modified software) in addition that version check will probably also make it fail (you can't OTA to the same version already on the phone).
You might be able to extract the ROM for the zip file. But this can be risky, too. Its best you find a previously posted TWRP backup of the stock ROM; or ask someone to post it.
Click to expand...
Click to collapse
Thanks redpoint!! Please bear with me due to my limited knowledge.I have my own twrp back up which i made just after i got the phone and before doing anything but its an year old backup.I think at that time it was android 4.4.3.But after that my phone took 3 OTA updates.So i can i still use my old stock android 4.4.3 TWRP backup?
I also have recovery.img which i made just after getting OTA update 6-7 months ago.I used "dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img" to save recovery image.

ninja_zx11 said:
Thanks redpoint!! Please bear with me due to my limited knowledge.I have my own twrp back up which i made just after i got the phone and before doing anything but its an year old backup.I think at that time it was android 4.4.3.But after that my phone took 3 OTA updates.So i can i still use my old stock android 4.4.3 TWRP backup?
Click to expand...
Click to collapse
That one is probably too old. The backup needs to match your firmware (hboot, radio, etc.) or at least be close.
ninja_zx11 said:
I also have recovery.img which i made just after getting OTA update 6-7 months ago.I used "dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img" to save recovery image.
Click to expand...
Click to collapse
Can't tell if that is too old, either.
You should be able to find the needed stock nandroid and stock recovery here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Sounds like you current version is 4.20.631.2?

redpoint73 said:
Sounds like you current version is 4.20.631.2?
Click to expand...
Click to collapse
@ninja_zx11
Use 4.20.631.3 then MM OTA

redpoint73 said:
That one is probably too old. The backup needs to match your firmware (hboot, radio, etc.) or at least be close.
Can't tell if that is too old, either.
You should be able to find the needed stock nandroid and stock recovery here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Sounds like you current version is 4.20.631.2?
Click to expand...
Click to collapse
Thanks.will check that out.
One more silly question.Would it work if unroot it and then run recovery to do factory reset.

ckpv5 said:
@ninja_zx11
Use 4.20.631.3 then MM OTA
Click to expand...
Click to collapse
my current version is 4.20.6313 and i saved my OTA update file before doing update.

ninja_zx11 said:
One more silly question.Would it work if unroot it and then run recovery to do factory reset.
Click to expand...
Click to collapse
What part about never rooted do you not understand???
Stop trying to invent ways around it. You can dance around and cluck like a chicken if you want, it still won't make a previously rooted ROM never rooted.
You've been told the proper way to proceed.

redpoint73 said:
What part about never rooted do you not understand???
Stop trying to invent ways around it. You can dance around and cluck like a chicken if you want, it still won't make a previously rooted ROM never rooted.
You've been told the proper way to proceed.
Click to expand...
Click to collapse
I agree.will follow your way and try to find the twrp backup.I am sorry for the hassle.

Cannot update to Oreo

I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.

Comet1966 said:
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Click to expand...
Click to collapse
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk

piscesjoey said:
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It's like the system and recovery don't have access to the storage at all.

Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.

Uzephi said:
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Click to expand...
Click to collapse
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859

Comet1966 said:
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Click to expand...
Click to collapse
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?

Uzephi said:
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Click to expand...
Click to collapse
I did the flashall and that's it. I have no idea what's up with it

Comet1966 said:
I did the flashall and that's it. I have no idea what's up with it
Click to expand...
Click to collapse
What is your current version? -11/November patch?

Uzephi said:
What is your current version? -11/November patch?
Click to expand...
Click to collapse
This

Comet1966 said:
This
Click to expand...
Click to collapse
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.

Uzephi said:
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Click to expand...
Click to collapse
I am trying that one again. Factory reset didn't help either.

I did the flashall to 122-59-8. Now I am updating to 122-59-8-6

Comet1966 said:
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Click to expand...
Click to collapse
Which version of the bootloader? If the Oreo bootloader then perhaps this will result in an error.
If you installed Oreo Global or TMO after that, the bootloader will be upgraded to Oreo, perhaps this will lead to an error.

So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.

Comet1966 said:
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Click to expand...
Click to collapse
Wow, must've been some kind of bad flash previously? Either way glad that you've finally joined the rest of us!
Sent from my Moto Z (2) using Tapatalk

Rooted P2XL with stock recovery

Hey everyone, I have a pixel 2XL rooted with stock recovery (and stock firmware).
I was wondering if I can get OTA updates ? I thought I could receive them and install them (and then re-root of course), but I still haven't received the March OTA yet.
Thanks!

youssefkr said:
Hey everyone, I have a pixel 2XL rooted with stock recovery (and stock firmware).
I was wondering if I can get OTA updates ? I thought I could receive them and install them (and then re-root of course), but I still haven't received the March OTA yet.
Thanks!
Click to expand...
Click to collapse
You'll likely get the notification, and it might even download, however, it won't install. But no biggie, you can either fastboot the monthly updates, or flash the OTA zip in twrp. Either way, you'll still have root it again :good:

Badger50 said:
You'll likely get the notification, and it might even download, however, it won't install. But no biggie, you can either fastboot the monthly updates, or flash the OTA zip in twrp. Either way, you'll still have root it again :good:
Click to expand...
Click to collapse
Thanks, but I thought the whole point of keeping the stock recovery is that I could install OTA directly ?
In that case I should probably flash TWRP.

youssefkr said:
Thanks, but I thought the whole point of keeping the stock recovery is that I could install OTA directly ?
In that case I should probably flash TWRP.
Click to expand...
Click to collapse
Stock recovery yes, however, root is the ota killer as well :good:

There was a moment that flashing twrp would brick the phone and that they made it where you couldn't flash twrp anymore
Looks like they found a work around
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Sent from my Pixel 2 XL using Tapatalk