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.
Related
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
MM MaD said:
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
Click to expand...
Click to collapse
You can do either but ensure two things for avoiding a possible bootloop. One is the TWRP and the other is wiping all except internal storage before flashing the ROM.
You should have the modified TWRP 3.0.2-23.
Wipe, flash ROM and flash TWRP before booting as the existing TWRP is likely to be overwritten by the stock recovery. Speaking from experience!
Though I was going from 3.2.7 to 3.2.8, TWRP was overwritten which I found only after booting and when I tried to get back into recovery.
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
jfodra said:
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
Click to expand...
Click to collapse
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
lekronop said:
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
Click to expand...
Click to collapse
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
jfodra said:
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
Click to expand...
Click to collapse
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
lekronop said:
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
Click to expand...
Click to collapse
Oh okay. Thanks a lot for the clarifications.
jfodra said:
Oh okay. Thanks a lot for the clarifications.
Click to expand...
Click to collapse
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
lekronop said:
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
Click to expand...
Click to collapse
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
jfodra said:
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
Click to expand...
Click to collapse
Yes it does.. That's the reason I unlock the bootloader as soon as I get a new device
i was on freedom os . i am back on stock oxygen os but i have 2 issues.
1) when i got an update to 3.2.7 it showed in german that there is an update even though the language i chose was english
2) The boot animation shows the freedom os splash screen and then the boots into stock. Ihave got the boot animation of stock os but need instructions on how to flash the zip.
Can someone throw light on the above 2 issues?
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!
Hello XDA, I am running rooted Oxygen OS 3.2.2 with unlocked bootloader on my OnePlus 3 and TWRP version 3.0.2-0 and I want to update to the newest Oxygen OS (I think 4.1.6) How should I proceed? Can I just dirty flash it over it? I am kinda scared because I have read somewhere that some versions of TWRP cause issues. Thanks in advance.
NoddyCzech said:
Hello XDA, I am running rooted Oxygen OS 3.2.2 with unlocked bootloader on my OnePlus 3 and TWRP version 3.0.2-0 and I want to update to the newest Oxygen OS (I think 4.1.6) How should I proceed? Can I just dirty flash it over it? I am kinda scared because I have read somewhere that some versions of TWRP cause issues. Thanks in advance.
Click to expand...
Click to collapse
Just flash it on top of whichever rom you are. You'll be good, but keep în mind that flashing stock 4.1.6 will restore stock recovery.
To preventiv this, flash stock 4.1.6 the flash the latest recovery before rebooting. I personally bluspark's twrp. Cheers
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?