Related
Hello all,
For the last 4-5 firmware updates I've had no issue using fastboot to flash the firmware images, then flashing SuperSU, ElementalX kernel, Viper4Android and AdAway host lists through recovery to update to the latest build but keep my root mods.
I would like to now to the same with DP5 (or, at the very least, the first official Nougat build when it drops soon) and make sure I do it safely without any bricking.
Here's the current status -
Bootloader: Unlocked
Build: Android 6.0.1 MTC19Z, July Security Patch
Root Status: Rooted
Root Mods: ElementalX Kernel, Viper4Android, AdAway
Essentially, I want the same set up/root mods as above, only on 7.0. My questions are as follows:
1. Does the process differ at all for both installation of the firmware (through fastboot) or root method (flash TWRP, flash SuperSU)?
2. Is a full data wipe required? Recommended?
3. Anything else I should know?
Thanks in advance for the help. I'd love to make this as painless as the monthly firmware updates without any hiccups.
- Moonboots
The process does not differ much for the installation of the firmware; all you need to do is flash the factory images and TWRP through fastboot, and flash SuperSU/root through TWRP.
However, for a working TWRP and root, you'll need to decrypt your phone again, which will of course wipe your phone's data and internal storage.
I suggest looking at this helpful thread over on the Nexus 6P forums saying how to switch to 7.0 here:
http://forum.xda-developers.com/nexus-6p/general/how-to-switch-to-android-n-preview-t3409538
Even though it's for the 6P, I have used it myself and the procedure is the same. Once you've done all that, you're good to flash the latest SuperSU through TWRP.
As for V4A, I'm not sure whether it is compatible with Android N yet. You can install the ElementalX kernel normally after installing 7.0, but I don't think it's been updated to DP5.
If you do decide to update to Nougat, the modified boot.img for NPD90G can be found here:
http://forum.xda-developers.com/nexus-5x/general/4-17-16-t3360574
Thank you! I actually kept my phone encrypted all this time. Have you seen significant performance increases by decrypting?
EDIT: I see it's actually necessary for working TWRP in 7.0, thus far. Interesting. I'll have to work on getting my data backups set tonight.
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
I'm not sure, but, you can just flash the ota in twrp and make sure to flash the twrp img after flashing the ota. And, always make a twrp backup
AFAIK you need stock recovery for OTA to work (not 100% sure).
If downloading whole 1.4GB ROM is not a big issue, it's safer to dirty flash the whole ROM. Otherwise you could flash back stock recovery, install small OTA, then flash TWRP again. A bit more work, but less downloading.
Sent from my OnePlus 3 using Tapatalk
This question doesn't belong in this section. @Stephen please move this to the Q&A section. Thanks.
DroidJay123 said:
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
Click to expand...
Click to collapse
Let me make it clear, the full rom flash is a better option and you can do so from twrp. You would not loose twrp after the flash and need not flash the recovery again. SuperSU/Magisk flash is optional after the ROM flash. I see that you are running 3.0.4-1 which is a 7.1.1 compatible TWRP so there is no need to worry of any data loss. TWRP is also able to flash the OTA's provided you have not made any changes to your system partition and have remained unrooted.
You can come to General / OOS thread and ask there for further understanding :fingers-crossed:
You can flash OTA as long as your kernel is on default, what I mean is stock/untouched which is basically same situation as yours since youre unrooted. ? So yes you can flash OTA no need for full flash
If me, i like waiting full ROM zip release and do clean install.
Sometimes, flash OTA getting error (cause root, bla bla bla hahaha )
Yeah, it could be lazy gonna install back all apps at least you backup it
My advice, if you update same Android version, no problem to do a dirty flash (same ROM like LOS 14 to LOS 14, but if different ROM, i suggest better do clean install)
But if different version, mean 7.0 to 7.1.1, better clean install (dirty also no problem, but wonder in future got problem)
But hey, different people, different way right? This just my 2cent
It is my understanding that when moving from whole version number changes (6 to 7, 7 to 8) etc that a clean install is definitely way to go but even from 7.0 to 7.1? Also when you download the OTA, is the file saved somewhere so you can then locate it in TWRP for flashing? I don't want to allow the system to install the ota automatically correct?
DroidJay123 said:
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
Click to expand...
Click to collapse
It is best to clean flash if you've major upgrade like 6->7 or 7>8 something like that but if as your question you're still on marshmallow so you can flash OTA zip through twrp and make sure after OTA you've to flash twrp again to maintain it. If the system shows OTA it can't flash it via open recovery on twrp, you must have stock recovery to do it.
This thread is not for ROM development. Please get a mod move this thread to the Q&A section.
Hi guys, I'm on the international beta rom but it's quite outdated now and I'd like to get up to speed with the OTA's.
I download the full version for flashing in TWRP as i'm rooted but it asks for a password everytime.
Apparently I need to format the internal storage to get past this, but I don't want to lose all my apps and setup etc. Is there anyway to update without losing root and files etc?
Thank you in advance,
Andy
The beta is based on Android 7 Nougat, right? And the stable is currently still based on 6.0.1. If you mean you'd like to get back to the stable channel I think a clean flash is the only option. You might be able to restore your data via TWRP but I'm not sure if that's OK when downgrading from 7 to 6. Maybe someone else can confirm this.
I'd say the best option would be a fastboot clean flash of the full ROM and go from there. Then you can reflash TWRP.
thank you for your reply, but I'm not on nougat at the moment, I'm happy sticking to the beta channel but as I'm rooted I can't OTA update to newer beta version which would be nougat.
Cheers,
Andy
andypa1 said:
thank you for your reply, but I'm not on nougat at the moment, I'm happy sticking to the beta channel but as I'm rooted I can't OTA update to newer beta version which would be nougat.
Cheers,
Andy
Click to expand...
Click to collapse
In that case, follow the steps I mentioned but using the Beta Fastboot ROM using the Mi Flash tool. Make sure you select "flash_all_except_storage.bat" and you'll keep your data and apps during the process. Once the device is booted, just make sure not to root and you'll be able to OTA to new beta roms when they are released.
Here's a link to the full list of Fastboot flashable ROMs. You didn't mention whether you're on Helium or Hydrogen, so make sure to pick the correct ROM for your device.
Good luck!
I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?
djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.
KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june
JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...
KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.
djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't
KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)
JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.
djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?
Hi all. New OP5T user here. Currently running on android 8.1 on PixelExperience ROM but planning on updating when the stable version of Pie gets released. Have a few questions:
- I've searched in the forum that updating to an open beta version of pie is as simple as wipe and flash for those on twrp when coming from previous android versions (such as 8.1). Does this mean I can do the same with the stable version and just flash Pie based ROMs afterwards?
- when I flashed a custom ROM which failed to boot, I tried to restore the nandroid backup of the stock rom but unfortunately, i was greeted with a black screen. Now Im scared to freely test out roms because of that failed nandroid backup. Did anything change in what specific partitions one has to back up? Ive always just backed up whatever partitions were checked by default in my Nexus 6p days and it always worked.
Did you already have 5.1.4 and 5.1.5? Check for project Treble. What I did to get the latest open beta without screwing up my phone is that I flashed through TWRP the latest stable release, then I flashed stock recovery so I can flash the latest Pie beta. After that you can choose to stay stock or flash twrp and magisk. Everything works fine. If you end up with a bricked phone and even recovery doesn't show there is a tool uploaded from 1+ customer service on this forum that can help you recover your phone! I tried and it worked!
Tehbro said:
Hi all. New OP5T user here. Currently running on android 8.1 on PixelExperience ROM but planning on updating when the stable version of Pie gets released. Have a few questions:
- I've searched in the forum that updating to an open beta version of pie is as simple as wipe and flash for those on twrp when coming from previous android versions (such as 8.1). Does this mean I can do the same with the stable version and just flash Pie based ROMs afterwards?
- when I flashed a custom ROM which failed to boot, I tried to restore the nandroid backup of the stock rom but unfortunately, i was greeted with a black screen. Now Im scared to freely test out roms because of that failed nandroid backup. Did anything change in what specific partitions one has to back up? Ive always just backed up whatever partitions were checked by default in my Nexus 6p days and it always worked.
Click to expand...
Click to collapse
To ensure no problems when updating, you must backup your apps and data with titanium backup or any other app that you like and do a complete wipe.
To ensure that all will work flawless, you must be sure that the last OOS that were installed in your phone was up to 5.1.4, flash de OOS 5.1.7 on TWRP after a factory reset, and then just update to 9.0.0 without any issues.
If your last OOS version was 5.1.4 or lower, you must flash the 5.1.4 in twrp and then the 5.1.7.
Or just use this, with this to flash 5.1.7
libnijunior said:
To ensure no problems when updating, you must backup your apps and data with titanium backup or any other app that you like and do a complete wipe.
To ensure that all will work flawless, you must be sure that the last OOS that were installed in your phone was up to 5.1.4, flash de OOS 5.1.7 on TWRP after a factory reset, and then just update to 9.0.0 without any issues.
If your last OOS version was 5.1.4 or lower, you must flash the 5.1.4 in twrp and then the 5.1.7.
Or just use this, with this to flash 5.1.7
Click to expand...
Click to collapse
Thanks. I was able to update OOS to 5.1.7 through OTA then flashed my current ROM. I was told i could just flash a custom PIE rom right away as I'm on the latest FW, yes?
Tehbro said:
Thanks. I was able to update OOS to 5.1.7 through OTA then flashed my current ROM. I was told i could just flash a custom PIE rom right away as I'm on the latest FW, yes?
Click to expand...
Click to collapse
For sure, now you can flash any pie ROM you want. (OOS Based)
For those that aren't based in OOS, depends from one to another, and now, as the official pie is recent, some are using old blobs ( from 5.1.7 and maybe have some incompatibilities with the new blobs)
libnijunior said:
For sure, now you can flash any pie ROM you want. (OOS Based)
For those that aren't based in OOS, depends from one to another, and now, as the official pie is recent, some are using old blobs ( from 5.1.7 and maybe have some incompatibilities with the new blobs)
Click to expand...
Click to collapse
Ah right. Does that mean its better to wait for non-OOS pie roms to be based on the latest official build? Sorry, but what are blobs?
Tehbro said:
Ah right. Does that mean its better to wait for non-OOS pie roms to be based on the latest official build? Sorry, but what are blobs?
Click to expand...
Click to collapse
Blobs are the things that ROMs are in the scratch, the device specific things. For now I think that all the mainstream ROMs already are based on the new OOS, but always is better to read all ROM specific thread to be sure.