How to move to Stable pie from open beta pie - OnePlus 6 Questions & Answers

I'm on unrooted, unlocked bootloader OnePlus 6 With open beta 3 on stock recovery.
Just want to shift to stable pie. How to do that? Because when i tried using local upgrade option in system updates i got it can't be downgraded. Refer screenshot for better understanding

I only know how to do this with twrp.
So: fastboot boot twrp.img (guide in forum) (use latest blu_spark)
Flash latest blu_spark twrp.zip
Reboot to twrp
Flash rom.zip
Flash blu_spark twrp again
Not booting do it one more time.
Dont want twrp at all? Don't flash it after the rom.. I would keep it atleast until you know it all works, then dirty flash rom.zip to get rid of it.. If that's your cup of tea

whizeguy said:
I only know how to do this with twrp.
So: fastboot boot twrp.img (guide in forum) (use latest blu_spark)
Flash latest blu_spark twrp.zip
Reboot to twrp
Flash rom.zip
Flash blu_spark twrp again
Not booting do it one more time.
Dont want twrp at all? Don't flash it after the rom.. I would keep it atleast until you know it all works, then dirty flash rom.zip to get rid of it.. If that's your cup of tea
Click to expand...
Click to collapse
Thanks buddy
But i didn't understand "Not booting do it one more time" thing

In youre screenshot you have ob03 or 9.0 stable (15.09.5018).
Ob04 date is 29.09.2018

harigavara said:
Thanks buddy
But i didn't understand "Not booting do it one more time" thing
Click to expand...
Click to collapse
If the phone doesn't boot... Start over from step 1 one more time

Is there anyway doing it without flashing twrp? Wouldn't flashing it avoid warranty?

gabris said:
Is there anyway doing it without flashing twrp? Wouldn't flashing it avoid warranty?
Click to expand...
Click to collapse
(Unlocking the bootloader, Flashing twrp, rooting.....) don't void warranty on oneplus devices

I want to do the same, go from Pie beta 4 to Original Pie version, but have no root, twrp ot whatever. I enabled Developer Option, enabled OEM Unlock(bootloader) , downloaded the official OxygenOS from OnePlus. I go to System Updates, click Local Upgrade and select the ZIP, but then it says it can't since this version is older than the one installed and downgrade is not possible. Now what?
Second question: what s better, has more latest updates and news stuff; beta or the stable?

Gee, really nobody has a clue?

There is a special downgrade image to move from the Pie betas back to Oreo.
Search XDA or the the OnePlus forums for the downgrade image (it should be in one of the announcement threads for the betas).
After the downgrade to Oreo you can use an OTA or full download to upgrade to official Pie.
olafd72 said:
Gee, really nobody has a clue?
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk

Related

Question About the Beta P Program on Verizon

So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.
i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!

[Newbie Question]TWRP gone after OTA update OSS 5.1.6

I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Have u not read anything in these forums, tutorials or anything?
There are like 50 threads on how to upgrade and about the new partitions for op6, it is even clear when u installed twrp too
dRakeNNNN said:
I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Click to expand...
Click to collapse
Hi, just to clarify when you install an OTA on the oneplus 6 it uses the new partitioning system which is different so to remedy the situation just try reflashing TWRP enchilada installer using fastboot.
cschmid44 said:
Hi, just to clarify when you install an OTA on the oneplus 6 it uses the new partitioning system which is different so to remedy the situation just try reflashing TWRP enchilada installer using fastboot.
Click to expand...
Click to collapse
Previously, i've installed Beta(unofficial) version of TWRP, now i want to re-install TWRP with Official version , do i need to remove or do something firstly?
To fix it just download the official TWRP for oneplus 6 from the official team win recovery project page and then you put that on your phone, and flash using your currently installed TWRP then after that make sure you also install the root package as installing the new version of TWRP will modify the new boot image, Also a good time to mention that it will install in both slots (Seamless update slots) Treble slots if you will just to be aware.
cschmid44 said:
To fix it just download the official TWRP for oneplus 6 from the official team win recovery project page and then you put that on your phone, and flash using your currently installed TWRP then after that make sure you also install the root package as installing the new version of TWRP will modify the new boot image, Also a good time to mention that it will install in both slots (Seamless update slots) Treble slots if you will just to be aware.
Click to expand...
Click to collapse
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
dRakeNNNN said:
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
Click to expand...
Click to collapse
Just follow one of the many upgrade guides. Skip the part about upgrading to 5.1.6 but for the rest follow the steps exactly. No need to explain all this in yet another thread imo. You'll need a pc though.
that's would be great if twrp can be flashed and stays there without wiping as well as root.
Pleasssseeeeee read before creating a new thread
dRakeNNNN said:
I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Click to expand...
Click to collapse
Wait!
Don't install 5.1.6 ROM because OP has retired it. The last version availabe on OP site is the 5.1.5.
MuttleyMB said:
Wait!
Don't install 5.1.6 ROM because OP has retired it. The last version availabe on OP site is the 5.1.5.
Click to expand...
Click to collapse
I'm using 5.1.6, so far so good. I don't have any issue on 5.1.6. ?
Sent from my OnePlus6 using XDA Labs
dRakeNNNN said:
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
Click to expand...
Click to collapse
You can't boot into twrp because it's not there anymore. The OTA created a completely stock version of the OS that you're now booted on. You need to reinstall twrp and magisk according to the posted guides. This is going to be the case with all OTAs. The stock updater looks for root, and when it's there, it installs a complete OS, not an incremental update.

Which version of TWRP bluespark?

I just currently got the latest ota and let it install and I installed magisk from the manager by choosing to install to inactive partition after ota. That worked flawlessly and was able to keep root. But I lost TWRP of course. I was using the official TWRP. I've been noticing everyone going to TWRP bluespark recovery. But which one do I download??? From what I understand there is a version for oos android 8 Oreo and a version for oos android 9 pie. I'm on official oos pie. So which one do I need?
vinnievegas said:
I just currently got the latest ota and let it install and I installed magisk from the manager by choosing to install to inactive partition after ota. That worked flawlessly and was able to keep root. But I lost TWRP of course. I was using the official TWRP. I've been noticing everyone going to TWRP bluespark recovery. But which one do I download??? From what I understand there is a version for oos android 8 Oreo and a version for oos android 9 pie. I'm on official oos pie. So which one do I need?
Click to expand...
Click to collapse
Just take the latest official TWRP and you are fine. Trust me.
https://dl.twrp.me/enchilada/
Thank you. But still would like to know if I decide to use bluespark version.
Sure. If you want to use Blu Spark TWRP use this one twrp-3.2.3-x_blu_spark_v9.86_op6
IMG and zip files are here https://forum.xda-developers.com/devdb/project/?id=27466#downloads
You can use TWRP official or Blu Spark TWRP. What ever you like. Blu Spark is recommended for people coming from oos beta to stable
Pundy said:
Just take the latest official TWRP and you are fine. Trust me.
https://dl.twrp.me/enchilada/
Click to expand...
Click to collapse
Pundy said:
Sure. If you want to use Blu Spark TWRP use this one twrp-3.2.3-x_blu_spark_v9.86_op6
IMG and zip files are here https://forum.xda-developers.com/devdb/project/?id=27466#downloads
You can use TWRP official or Blu Spark TWRP. What ever you like. Blu Spark is recommended for people coming from oos beta to stable
Click to expand...
Click to collapse
May I ask what the difference is?
Just to add a note to you for next ota.
After ota is installed go to magisk manager
Press download
Search for twrp a/b
Install (don't reboot)
Now go to main screen and press install
Choose to inactive slot (after ota)
This way you keep both twrp and root
Happy flashing
vinnievegas said:
May I ask what the difference is?
Click to expand...
Click to collapse
To be honest I don't know the differences between both.
vinnievegas said:
May I ask what the difference is?
Click to expand...
Click to collapse
You can find answer at its topic.
whizeguy said:
Just to add a note to you for next ota.
After ota is installed go to magisk manager
Press download
Search for twrp a/b
Install (don't reboot)
Now go to main screen and press install
Choose to inactive slot (after ota)
This way you keep both twrp and root
Happy flashing
Click to expand...
Click to collapse
Awesome!!!!! That's definitely a game changer!!
Thank you.
Hey, I have unlocked bootloader and have magisk installed.
But every time I have to go to bootloader to boot into twrp because of some issue.
I have the zip and img file of twrp by bluspark.
I have the img of bluspark twrp now I need to know which sector should I need to install. Boot, system or vendor? Please tell me. I'm new here.
there is a problem with magisk 20.1, first boot after all flashes is ok and magisk is working but after I giving root access to first program and going for restart its not booting and going to bootloader.
chetbiz said:
there is a problem with magisk 20.1, first boot after all flashes is ok and magisk is working but after I giving root access to first program and going for restart its not booting and going to bootloader.
Click to expand...
Click to collapse
Which OOS version are you running? Pie or Q?
Koeties said:
Which OOS version are you running? Pie or Q?
Click to expand...
Click to collapse
Android Q final
Hello, I have problem. I´m on Android 11, with OOS 11.1.2.2, but I can´t install TWRP - twrp-3.6.0_11-0-enchilada.img. When I wrote fastboot boot twrp-3.6.0_11-0-enchilada.img, it is stuck on logo a nothing happen. Please how to boot in twrp?
Thank you.

Havoc Pie downgrade to Havoc Oreo doesnt work

Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.
i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year

is it possible to upgrade from pie hos to a10 oos using local update?

hello there.
sorry for making a new thread .. ive asked my question multiple times no one answered properly. so here's the situation:
just received the phone from china . i'm on android pie hos. and want to update to ob7 . having root and twrp is it the right way to do it? :
1. update to ob7 using local update and full zip file.
2. unlock the bootloader and flash twrp 70 (or 74 i'm not sure?) using adb
3. flash magisk and twrp installer in twrp recovery
4. done!
i heared its better to use twrp 70 and dont know the reason. whats wrong with the latest version?
Not sure if that will work, but locally upgrading from h2OS to OOS worked on my old op6 when I had it.
If it does not work;
Backup your files first then you need to unlock your bootloader.
Then boot twrp via command prompt. Once booted into twrp. Wipe data and do a factory reset there. Flash twrp installer then reboot into recovery.
Flash OB7, twrp installer and magisk then reboot to recovery again and flash ob7, twrp installer and magisk then reboot to system
I'm using .74
Not sure what the problem is/are.
Regards
Dark Fear said:
hello there.
sorry for making a new thread .. ive asked my question multiple times no one answered properly. so here's the situation:
just received the phone from china . i'm on android pie hos. and want to update to ob7 . having root and twrp is it the right way to do it? :
1. update to ob7 using local update and full zip file.
2. unlock the bootloader and flash twrp 70 (or 74 i'm not sure?) using adb
3. flash magisk and twrp installer in twrp recovery
4. done!
i heared its better to use twrp 70 and dont know the reason. whats wrong with the latest version?
Click to expand...
Click to collapse
It can be done but I wasn't happy with it there were loads of bugs.. Issues slowdowns etc.. I would suggest strictly against it..
theocdguy said:
It can be done but I wasn't happy with it there were loads of bugs.. Issues slowdowns etc.. I would suggest strictly against it..
Click to expand...
Click to collapse
so whats the right way to do it
Dark Fear said:
so whats the right way to do it
Click to expand...
Click to collapse
Which route you want to follow twrp or official? If its official i'd say try the msm tool.. That will put you on oldest pie and then you can do OTA..
Twrp is self explanatory..
theocdguy said:
Which route you want to follow twrp or official? If its official i'd say try the msm tool.. That will put you on oldest pie and then you can do OTA..
Twrp is self explanatory..
Click to expand...
Click to collapse
i'm already on oldest pie.. whats the difference of his method with the one i mentioned?

Categories

Resources