Develop Bugs

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?

Updating after installing TWRP

Does anyone have a suggestion of the easiest way to update android to the latest March security update after installing TWRP and rooting with xceede's kernel as per oRAirwolf's guide?
I see there is an updated version of the kernel available but cannot work out how to update android system without OTA or custom ROMs.
Many thanks, sorry for my ignorance.

zezayer said:
Does anyone have a suggestion of the easiest way to update android to the latest March security update after installing TWRP and rooting with xceede's kernel as per oRAirwolf's guide?
I see there is an updated version of the kernel available but cannot work out how to update android system without OTA or custom ROMs.
Many thanks, sorry for my ignorance.
Click to expand...
Click to collapse
I would recommend downloading the latest factory image (or whatever version you want to update to) and flashing all of the partitions individually (EXCEPT USERDATA, as that will wipe your device). This is what I've done for years on all my Nexus devices when updating. You'll just have to re-flash TWRP and Xceed after upgrading. Shouldn't be too difficult. Some may say you really only need to flash certain partitions like system, boot, vendor etc., but I always find it better to err on the side of caution to make sure I don't bork anything in the process.
tl;dr
See Step 9 from this post from the Nexus 6P forums (obviously, make sure you replace the angler image files with the appropriate Pixel C images): http://forum.xda-developers.com/showpost.php?p=62924118&postcount=2

Success: - Thanks for the tips.
Downloaded MXC14G vendor image from google. (Link)
Unzipped system and vendor from the image.
Downloaded xceed's modified MXC14G boot image. (Link)
Flashed system, vendor and xceeds boot via fastboot.
Rebooted into system and let it all update.
Finally rebooted into TWRP to reflash Xposed / Viper etc.

zezayer said:
Success: - Thanks for the tips.
Downloaded MXC14G vendor image from google. (Link)
Unzipped system and vendor from the image.
Downloaded xceed's modified MXC14G boot image. (Link)
Flashed system, vendor and xceeds boot via fastboot.
Rebooted into system and let it all update.
Finally rebooted into TWRP to reflash Xposed / Viper etc.
Click to expand...
Click to collapse
What version of Viper are you using? There seem to be various version out there now, which have been modified for specific devices. Please post a link to the one that you are using? Any issues with it?

SmokinCharger said:
What version of Viper are you using? There seem to be various version out there now, which have been modified for specific devices. Please post a link to the one that you are using? Any issues with it?
Click to expand...
Click to collapse
I'm using the Loliviper flashable zip. Working really well.

zezayer said:
I'm using the Loliviper flashable zip. Working really well.
Click to expand...
Click to collapse
Which specific version. I noticed that there are various loliviper versions that are device specific

I used the nexus 5 version which was recommended for the 6p and other nexus phones http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Works well!

zezayer said:
I used the nexus 5 version which was recommended for the 6p and other nexus phones http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Works well!
Click to expand...
Click to collapse
Thank you.

Community Build and OTA/Update questions

I've ordered a OP 3 and its due to arrive at the end of the month. Till then I've been reading about the OP3 and have a few questions. I'm a relative novice when it comes to phone mods.
1. What is a "Community Build"? Googling did not render a good answer but my understanding is that it is sort of a "beta" build that does not come via OTA. Is this correct? Are the community builds generally pretty stable? I ask because the OP website recommends the standard build over the community build (see attached screenshot). I assume the community builds eventually make it to a final build?
2. If you are rooted, how do you update your phone? I assume taking an OTA will not work on a rooted phone so what is the best method of doing an update?
Thank you

1. Yes, community build (a.k.a Community Edition - most often just "CE" on forums") is a beta version of ROM with some new features and a bit different looks. Actually it's a merger between OxygenOS and HydrogenOS (Chinese ROM).
Not using it myself, but from what I hear it's stable in last couple of versions - good enough for daily driver.
There's no ETA so we don't know when/if it will become stable. Like I said before, it's not just a newer version but a completely new ROM so it's not directly related to standard version. I put "if" as an option because Nougat is already on the works so this may never be finalized (just a guess).
2. For updating rooted device you need to download full ROM zip (not just OTA package) and flash it manually in recovery (TWRP). You'll also need to flash SuperSU and other system modifications (if any) after every update as the ROM will overwrite them.
Sent from my OnePlus 3 using Tapatalk

shobuddy said:
I've ordered a OP 3 and its due to arrive at the end of the month. Till then I've been reading about the OP3 and have a few questions. I'm a relative novice when it comes to phone mods.
1. What is a "Community Build"? Googling did not render a good answer but my understanding is that it is sort of a "beta" build that does not come via OTA. Is this correct? Are the community builds generally pretty stable? I ask because the OP website recommends the standard build over the community build (see attached screenshot). I assume the community builds eventually make it to a final build?
2. If you are rooted, how do you update your phone? I assume taking an OTA will not work on a rooted phone so what is the best method of doing an update?
Thank you
Click to expand...
Click to collapse
1. Yep a community build is pretty much a beta. Anyone can download it and flash it but i don't recommend it as "daily drivers". A "CE" is for testing purposes and to report bugs, so of course it's not going to be stable enough. I recommend just staying with the standard build "unless you have another op3 to test "CE" builds xD". Yes once they polished the beta versions, they will make it into the stable version for everyone to use.
2. The only way you can update is by flashing (flashing means installing just in case if you didn't know what that meant) the update into the op3 using twrp. I recommend to flash the "signed versions". Basically what that means is when you flash the update using "the signed version" it doesn't delete twrp cuz if you flash the normal version downloaded from the op website, it will revert back into the normal recovery, so you have to flash twrp again. You can get the signed versions on xda when they become available.
Hope on what i wrote helped you.

williefromthedark said:
1. Yep a community build is pretty much a beta. Anyone can download it and flash it but i don't recommend it as "daily drivers". A "CE" is for testing purposes and to report bugs, so of course it's not going to be stable enough. I recommend just staying with the standard build "unless you have another op3 to test "CE" builds xD". Yes once they polished the beta versions, they will make it into the stable version for everyone to use.
2. The only way you can update is by flashing (flashing means installing just in case if you didn't know what that meant) the update into the op3 using twrp. I recommend to flash the "signed versions". Basically what that means is when you flash the update using "the signed version" it doesn't delete twrp cuz if you flash the normal version downloaded from the op website, it will revert back into the normal recovery, so you have to flash twrp again. You can get the signed versions on xda when they become available.
Hope on what i wrote helped you.
Click to expand...
Click to collapse
The latest CE is probably more stable than the latest standard build. It's completely daily driver worthy.

dpryor88 said:
The latest CE is probably more stable than the latest standard build. It's completely daily driver worthy.
Click to expand...
Click to collapse
Yeah when i was writing mine, you already posted yours so i didn't knew xD. Anyway your right. Sorry for the confusion.

williefromthedark said:
Yeah when i was writing mine, you already posted yours so i didn't knew xD. Anyway your right. Sorry for the confusion.
Click to expand...
Click to collapse
Haha no worries. I love the CE build. The h2os beta is basically the same, but I like it better than the CEs cause it has better battery life.

williefromthedark said:
I recommend to flash the "signed versions". Basically what that means is when you flash the update using "the signed version" it doesn't delete twrp cuz if you flash the normal version downloaded from the op website, it will revert back into the normal recovery, so you have to flash twrp again. You can get the signed versions on xda when they become available.
Click to expand...
Click to collapse
Thanks for the replies! I was not aware of the signed version thing so thats good to know. Does flashing a signed version wipe data off your phone? (pictures, messages, apps, etc.) If so, how do you get around this?
I'm currently on a Nexus 4 with root and to apply updates, I would dirty flash thus preserving the phone data.

shobuddy said:
Thanks for the replies! I was not aware of the signed version thing so thats good to know. Does flashing a signed version wipe data off your phone? (pictures, messages, apps, etc.) If so, how do you get around this?
I'm currently on a Nexus 4 with root and to apply updates, I would dirty flash thus preserving the phone data.
Click to expand...
Click to collapse
Yeah you can do a dirty flash when you install the update and it won't wipe your data but a reminder, since you are getting the op3 for the first time, you first have to unlock the bootloader and when you unlock the bootloader, it will delete everything that's on the phone, so i recommend when you first get the phone, don't put any media or any important files just yet, first unlock the bootloader, then flash twrp, then you can flash the update and since you won't have any data on the op3 just do a clean flash so it will have better results. Then after all of that, then you can go ahead and put all of your data on the op3. Oh and if you want, you can flash SuperSu so you can have root privileges.

shobuddy said:
Thanks for the replies! I was not aware of the signed version thing so thats good to know. Does flashing a signed version wipe data off your phone? (pictures, messages, apps, etc.) If so, how do you get around this?
I'm currently on a Nexus 4 with root and to apply updates, I would dirty flash thus preserving the phone data.
Click to expand...
Click to collapse
If nothing goes wrong, you should always keep your files, even when doing clean flashes. In TWRP you'll see you can wipe "data" without touching "internal storage".
Doing this gets rid of all apps and their settings, but your files stay safe.
Anyways, while you're on the same ROM and just applying updates there's usually no need to wipe anything, dirty flash and that's it.
I'd recommend making a nandroid backup every time before wiping and flashing stuff, just in case. And backing up apps, messages, call logs ... with some app also comes in handy. I'm using Titanium Backup Pro and SMS Backup and Restore for that purpose.
Sent from my OnePlus 3 using Tapatalk

Thanks again for the responses. I was torn between the OP3 and the Axon 7 and was leaning towards the Axon 7 because I could get it from BestBuy for $225 since I have $175 worth of gift cards with them but I chose the OP3 purely because of the cleaner Android experience and the user/developer community. I think I chose wisely Can't wait to get my hands on the phone.

Explorer23 said:
2. For updating rooted device you need to download full ROM zip (not just OTA package) and flash it manually in recovery (TWRP). You'll also need to flash SuperSU and other system modifications (if any) after every update as the ROM will overwrite them.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Can you confirm which version of TWRP to use for 3.2.7(latest stable build)? I am seeing messages on xda to use twrp-3.0.2-19 else you will get bootloop but it is not immediately clear if that is for stable build or CE. I feel twrp-3.0.2-1-oneplus3.img should work but don't know exactly due to this confusion thus asking.
Also while we are at it, can you please give link to latest working SuperSU & Xposed for 3.2.7 stable build? my OP3 is arriving today so gathering all info

power2top said:
Can you confirm which version of TWRP to use for 3.2.7(latest stable build)? I am seeing messages on xda to use twrp-3.0.2-19 else you will get bootloop but it is not immediately clear if that is for stable build or CE. I feel twrp-3.0.2-1-oneplus3.img should work but don't know exactly due to this confusion thus asking.
Also while we are at it, can you please give link to latest working SuperSU & Xposed for 3.2.7 stable build? my OP3 is arriving today so gathering all info
Click to expand...
Click to collapse
3.0.2-19 is for CE only, use the official 3.0.2-1 for stable.
SuperSU link: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
For Xposed install this app: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
and then download and install framework through the app (correct version will be preselected - standard for arm64).
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
3.0.2-19 is for CE only, use the official 3.0.2-1 for stable.
SuperSU link: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
For Xposed install this app: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
and then download and install framework through the app (correct version will be preselected - standard for arm64).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Thanks @Explorer23 but saw something else on http://forum.xda-developers.com/oneplus-3/how-to/3-2-7-t3471679/page7 where regular twrp i.e 3.0.2-1 did not work and they are facing bootloop issues but modded one (which I presume 3.0.2-19) works. Is my understanding correct?

power2top said:
Thanks @Explorer23 but saw something else on http://forum.xda-developers.com/oneplus-3/how-to/3-2-7-t3471679/page7 where regular twrp i.e 3.0.2-1 did not work and they are facing bootloop issues but modded one (which I presume 3.0.2-19) works. Is my understanding correct?
Click to expand...
Click to collapse
Interesting ... There's always that one person that does everything the same as others but gets new issues [emoji19] Quite possible it bootlooped for some other reason and not due to recovery.
Version 3.2.7 doesn't bring any substantial changes so there's no reason for official TWRP to not work. And it did work for majority of people.
That said, I can only provide my "educated guess" about 3.2.7 as I haven't personally flashed it. I'm sticking with FreedomOS (modified OxygenOS), which is still at 3.2.6 (probably because 3.2.7 wasn't officially released, it only came as OTA).
Sent from my OnePlus 3 using Tapatalk

shobuddy said:
Thanks again for the responses. I was torn between the OP3 and the Axon 7 and was leaning towards the Axon 7 because I could get it from BestBuy for $225 since I have $175 worth of gift cards with them but I chose the OP3 purely because of the cleaner Android experience and the user/developer community. I think I chose wisely Can't wait to get my hands on the phone.
Click to expand...
Click to collapse
Heard software experience on Axon 7 is bad and almost no dev support

Update to EMUI 8 (Mate SE) after nuking Factory ROM w Twrp?

Pulled kind of a boner. Got a Mate SE yesterday. It came with EMUI 5.1 and Android 7.0. I had read that version was still fairly easy/cheap to unlock the bootloader so I just left it as is without updating anything. Unlocked the bootloader, installed Twrp (to both recoveries) and now am unsure how to proceed with installing custom ROMs because I ended up nuking the factory ROM to install an older AOSP buggy build I found on here.
Didn’t realize that every custom ROM now seems to want you to install via fastboot with EMUI 8 required to have been installed beforehand, but I'm now stuck on this old AOSP ROM with no backup of the original & with Twrp recovery.
Sorry for all the questions but I've flash a million ROMs the old school Twrp ways since forever but this seems like a different beast. Should’ve slowed my roll. Is there some files I can flash via Fastboot or Twrp in order to use these new treble ROMs while keeping my boot loader unlocked? Thanks.

peestandingup said:
Pulled kind of a boner. Got a Mate SE yesterday. It came with EMUI 5.1 and Android 7.0. I had read that version was still fairly easy/cheap to unlock the bootloader so I just left it as is without updating anything. Unlocked the bootloader, installed Twrp (to both recoveries) and now am unsure how to proceed with installing custom ROMs because I ended up nuking the factory ROM to install an older AOSP buggy build I found on here.
Didn’t realize that every custom ROM now seems to want you to install via fastboot with EMUI 8 required to have been installed beforehand, but I'm now stuck on this old AOSP ROM with no backup of the original & with Twrp recovery.
Sorry for all the questions but I've flash a million ROMs the old school Twrp ways since forever but this seems like a different beast. Should’ve slowed my roll. Is there some files I can flash via Fastboot or Twrp in order to use these new treble ROMs while keeping my boot loader unlocked? Thanks.
Click to expand...
Click to collapse
Yes, in order to use the new "gsi" rims you need to do stock firmware upgrade. It is easy to do. But completely different then you seem to be used to , with twrp.
Just search for hwota , and I have a guide thread for 7x (basicly same as mate)

mrmazak said:
Yes, in order to use the new "gsi" rims you need to do stock firmware upgrade. It is easy to do. But completely different then you seem to be used to , with twrp.
Just search for hwota , and I have a guide thread for 7x (basicly same as mate)
Click to expand...
Click to collapse
Thank you. Just getting the files together but a little confused on one part. At the beginning, you say to extract the HWOTA package then put all the downloaded system files into the appropriate folder (HWOTA7 in my case), but at the final step you say to "From in TWRP install sdcard HWOTA--hi6250-7-8.zip", however that is the package we extracted from zip already before?
Does that mean I need to zip it back up with the system files I added in it in order to flash via Twrp? As is its just folders. Thanks. Just want to make sure I get everything right.

peestandingup said:
Thank you. Just getting the files together but a little confused on one part. At the beginning, you say to extract the HWOTA package then put all the downloaded system files into the appropriate folder (HWOTA7 in my case), but at the final step you say to "From in TWRP install sdcard HWOTA--hi6250-7-8.zip", however that is the package we extracted from zip already before?
Does that mean I need to zip it back up with the system files I added in it in order to flash via Twrp? As is its just folders. Thanks. Just want to make sure I get everything right.
Click to expand...
Click to collapse
Should be two folders. One each for 7 and 8. Each with twrp, and no-check recovery . And a zip file.

mrmazak said:
Should be two folders. One each for 7 and 8. Each with twrp, and no-check recovery . And a zip file.
Click to expand...
Click to collapse
Got it all done & went fine. Running Lineage at the moment. You're a life saver man, thanks!

Question flashing Oos update through twrp?

can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol

freddienuxx said:
can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol
Click to expand...
Click to collapse
I'm also curious about this. My current method is to just use the MSM tool whenever I want to go back to stock but it is definitely time consuming. As far as I know TWRP is still early in development and a lot of things that should normally work dont work perfectly

I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.

Haunt3r said:
I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.
Click to expand...
Click to collapse
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error

thirtythr33 said:
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error
Click to expand...
Click to collapse
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.

Haunt3r said:
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.
Click to expand...
Click to collapse
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.

thirtythr33 said:
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.
Click to expand...
Click to collapse
there is no "full" update for 7.7aa it's solely an OTA

Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
yeah man there is, came out June 28th, check oxygen updater or oneplus software download.
lol either way I can't flash it so fml

Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
Yes there is, it came out a few days ago about 3gb's on OnePlus website...

Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though

Haunt3r said:
Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though
Click to expand...
Click to collapse
yeah man we have to wait insane long for AA full updates. yeah my issue is very frustrating and I've tried everything short of msm, I just don't see how it is possible that twrp reports I am missing those partitions yet my phone boots, but slot B is f'd, and I can't flash full AA update either through twrp or local upgrade.

Okay so if we do flash the full ota through recovery what's the correct process on this to keep twrp and magisk without needing a PC to push the recovery and root back onto the device?