Related
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
its ok you can, but make sure you have Stock recovery installed not the TWRP
ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
shashank1320 said:
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
Click to expand...
Click to collapse
Not necessary!
You just have to flash stock recovery!
gaebzn said:
Not necessary!
You just have to flash stock recovery!
Click to expand...
Click to collapse
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
shashank1320 said:
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
Click to expand...
Click to collapse
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
gaebzn said:
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
Click to expand...
Click to collapse
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
shashank1320 said:
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
Click to expand...
Click to collapse
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
gaebzn said:
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
Click to expand...
Click to collapse
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Thank you mate!
shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
gaebzn said:
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
Click to expand...
Click to collapse
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
RedSkull23 said:
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
Click to expand...
Click to collapse
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
gaebzn said:
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
Click to expand...
Click to collapse
You may try uninstalling the busybox and then retry to see if it works.
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
System
1.Optimized network connection
2.Optimized stability for wi-fi connection
3.Fixed screen flickering issue in day light
4.General bug fixes and improvements
5.confirm pin without tapping
Camera
Improved HDR mode
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
I also get that update.
If i download it.. can i just not update right away?
because i want to manually update from twrp and re root with magisk.
Thanks in advance
Sent from my ONEPLUS A6000 using Tapatalk
ossy1337 said:
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
Click to expand...
Click to collapse
I have no photos with older firmware.i think now the photos taken are more brighter
Root users beware: issues with newer TWRP version!
This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
So since twrp latest works fine on my device with encryption included, I can just start the update?
Sent from my ONEPLUS A6003 using Tapatalk
Neurom67 said:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
Click to expand...
Click to collapse
Can you link 3.2.1-1 version? https://eu.dl.twrp.me/enchilada/ There is only 3.2.1-0 or 3.2.2-0
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
No problem with blue twrp.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Fails for everyone atm. Was working fine for me until two days ago before Google updated the api
Sent from my ONEPLUS A6003 using Tapatalk
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Here is why; https://mobile.twitter.com/topjohnwu/status/1029239685338419200
3.2.1.0 installed 5.1.11 fine on my OP6.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
SpectraFun said:
No problem with blue twrp.
Click to expand...
Click to collapse
Batfink33 said:
3.2.1.0 installed 5.1.11 fine on my OP6.
Click to expand...
Click to collapse
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Have TWRP 3.2.3 and installed 5.1.11 just fine.
SMS786 said:
Have TWRP 3.2.3 and installed 5.1.11 just fine.
Click to expand...
Click to collapse
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Vuska said:
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Didn't disable my pattern lock..worked just fine.
I downloaded the zip online and installed through TWRP. Just make sure to reinstall your TWRP installer after installing the full rom OTA (wipe cache/dalvik first), then reboot back into TWRP and install Magisk..then boot into system.
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Chinaroad said:
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Click to expand...
Click to collapse
People seem to be saying this for every release
giebeka said:
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Click to expand...
Click to collapse
Used Oxygen updater to download zip. Rebooted to bootloader. Went Install and selected ZIP. then added TWRP zip as well. Installed both. Rebooted to bootloader again. Flashed elementalx kernel(you can skip it) and magisk. All works fine.
kakkooran said:
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
...
5.confirm pin without tapping
Click to expand...
Click to collapse
I can't find where to enable this. Anyone found it?
Hi, i share my personnal experience, struggled to figure out what was wrong after flashing OB2 but it seems it's all good now.
Did this from OpenBeta2, no specific firmware required i guess as long as the tool we will use is there to erase everything.
I used the official 3.2.3.0 twrp to avoid strange encryption thing (link here)
a user reported this bug because of a custom recovery
1. Download MSMDownloadTool. The 4 files in the MEGA links seems to be requrired so download as zip the whole thing.
2. Follow the guide i quoted then check my instructions
credit to @Fivegates
Guide how to revive your op6:
First of all, you need to access to fastboot mode, if you can't , contact Oneplus support, then have a windows computer and download these file and drivers qualcomm ( https://androidfilehost.com/?fid=24052804347798730) and extract in one folder.
After you have all the file ready, plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug.
Now you have to go in Windows test mode to not let him install default drivers, so:
windows key (on keyboard) + X, windows powershell (or normal prompt) administrator and write and enter: bcdedit /set testsigning on ( you will repeat the same process with "off" to stop the test mode after you will finish to do all the things).
Reboot the system and you could see in bottom right corner the test mode, now you are ready to install properly drivers.
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process (https://www.youtube.com/watch?v=PpLvmID1wdI)
Right click con US8_BULK in device manager and update drivers by system files (go to the folder's drivers you had extracted before).
Now you should see qualcomm drivers under port (COM).
You are ready to let the tool to do all the stuff, so let plugged the phone, always powered off, right click on msmdownloadtool and execute as administrator.
You should see your device and click start to begin the process; if it gives you some error (like sahara or something else), unplug, power on, power off and the plug it again, now it should be fine.
And that's it, the tool will do all the work and, at the end, you will have like a brand new phone ready to a new setup.
EDIT: if you are stucked in bootloader, you have only to power off and continue with the part: ... hold for 5 seconds vol up... (it happened in page 4)
Click to expand...
Click to collapse
lil shortcut guide (might be wrong lol check @Fivegates post if scared)
# go to Device manager, delete your op6 drivers
# enable the test mode with
Code:
bcdedit /set testsigning on
(don't forget to turn off when you're done)
# reboot your pc
# open msmdownload
# power off phone, press vol up and connect phone to pc
# upgrade mode ticked, click once on the only line you see and hit START
# wait
# unplug when it's done
3. Once process is over the phone is back stock 5.1.5 with locked bootloader
4. update to OB2 via local update in settings
Comprehensive guide to update manually
5. unlock your bootloader
6. you should be able to boot on OB2 without that red annoying popup, flash a twrp and magisk whatever
Useful Guide to Unlock Bootloader, Flash TWRP, Root and more
VISUAL GUIDE
Tell me if it works for you too, personnally i've been able to unlock bootloader, flash the latest twrp and magisk
I am living along with corrupted device no problem at all.
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Toni Moon said:
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Click to expand...
Click to collapse
Same here for me. I tried the method mentioned in the op too. It gives the same error once I update to pie. The error is still there for hydrogen and oxygen. Dp3 doesn't have that issue
Toni Moon said:
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Click to expand...
Click to collapse
Yeah that "issue" is terrific :crying:
Did you try this way ?
80s Baby said:
Same here for me. I tried the method mentioned in the op too. It gives the same error once I update to pie. The error is still there for hydrogen and oxygen. Dp3 doesn't have that issue
Click to expand...
Click to collapse
you tried this and it fails ?
Neil_Armstrong_ said:
you tried this and it fails ?
Click to expand...
Click to collapse
Yes it does fail for me. It clears that warning when it's downgraded but once updated to any version of pie. The warning comes back again
80s Baby said:
Yes it does fail for me. It clears that warning when it's downgraded but once updated to any version of pie. The warning comes back again
Click to expand...
Click to collapse
Huh
Did you unlock bootloader before or after updating to Pie ? I honestly don't know what/where the wolf is
Neil_Armstrong_ said:
Huh
Did you unlock bootloader before or after updating to Pie ? I honestly don't know what/where the wolf is
Click to expand...
Click to collapse
Before..I guess right around the first update 5.1.6 or 7. That's when I bought the phone
80s Baby said:
Before..I guess right around the first update 5.1.6 or 7. That's when I bought the phone
Click to expand...
Click to collapse
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Neil_Armstrong_ said:
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Click to expand...
Click to collapse
Yes, this is the way
Neil_Armstrong_ said:
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Click to expand...
Click to collapse
Can I root my device after updating? Coz that's when the issue normally comes in as well
80s Baby said:
Can I root my device after updating? Coz that's when the issue normally comes in as well
Click to expand...
Click to collapse
Hi
I did exactly the same process as mentioned above and I have no problem with root
I first unlocked bootloader then fastbooted twrp + installer.zip
Then I flashed magisk and tons of stuff no red warning
Keep me updated
Neil_Armstrong_ said:
Hi
I did exactly the same process as mentioned above and I have no problem with root
I first unlocked bootloader then fastbooted twrp + installer.zip
Then I flashed magisk and tons of stuff no red warning
Keep me updated
Click to expand...
Click to collapse
Tried this last night it is still the same. Everything went well until I flashed magisk. That's when I got the warning this time.
Did you flash blu spark twrp?
This method works to me..
80s Baby said:
Tried this last night it is still the same. Everything went well until I flashed magisk. That's when I got the warning this time.
Click to expand...
Click to collapse
Toni Moon said:
Did you flash blu spark twrp?
This method works to me..
Click to expand...
Click to collapse
Yes, I haven't tried the official one yet..should I try that out instead?
80s Baby said:
Yes, I haven't tried the official one yet..should I try that out instead?
Click to expand...
Click to collapse
Official TWRP
I had the same error when I dirty flashed from 5.1.11 to the official 9.0. The method from OP fixed it. I'm back to 9.0 with TWRP, Magisk, and custom kernel without the annoying message.
Thanks a lot!
sasho36 said:
I had the same error when I dirty flashed from 5.1.11 to the official 9.0. The method from OP fixed it. I'm back to 9.0 with TWRP, Magisk, and custom kernel without the annoying message.
Thanks a lot!
Click to expand...
Click to collapse
can I still use the bluspark twrp or no?
R0ttenB4ndit said:
can I still use the bluspark twrp or no?
Click to expand...
Click to collapse
just read bro used official twrp 3.2.3
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
Use bluespark or black themed twrp
https://forum.xda-developers.com/showpost.php?p=77748695&postcount=7
another member is having the same issue, here's my recommendation. let me know if it helps please.
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
Same situation, same problem. I tried:
Code:
fastboot boot twrp-3.2.3-x_blu_spark_v9.85_op6.img
and still I end up in CrashDump Mode.
mackler said:
Same situation, same problem. I tried:
and still I end up in CrashDump Mode.
Click to expand...
Click to collapse
Use v9.86
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Works. Thank you!! :victory:
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Same, that was the issue, thanks!
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
actually, now my phone wont get past those spinning circles when it starts up. I can get into recovery. What can i do to fix this?
EDIT: I restored my old bootloader, but now my phone isn't rooted. I have twrp recovery. i tried flashing magisk 17.1, is there something here i shouldn't have done?
Giodude12 said:
actually, now my phone wont get past those spinning circles when it starts up. I can get into recovery. What can i do to fix this?
EDIT: I restored my old bootloader, but now my phone isn't rooted. I have twrp recovery. i tried flashing magisk 17.1, is there something here i shouldn't have done?
Click to expand...
Click to collapse
if you are on stock firmware, why do you want twrp? Unless you are going to aosp rom or want to decrypt the phone, twrp is not needed then.
MrSteelX said:
if you are on stock firmware, why do you want twrp? Unless you are going to aosp rom or want to decrypt the phone, twrp is not needed then.
Click to expand...
Click to collapse
Just looked into it. For whatever reason it doesn't work on Android p unless I run the uninstaller first. Thanks for the help though, I'm all good.
Use v9.86 of ... ??
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Use v9.86 of what ??
dash_z1 said:
Use v9.86 of what ??
Click to expand...
Click to collapse
Blu spark twrp..
Thank you
whizeguy said:
Blu spark twrp..
Click to expand...
Click to collapse
thank you just reialized that i`m supposed to use blue spark version of twrp for my op6 although they provided the original twrp links which was misleading in the root post
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
I tried this today and happened the same, i guess you have to clean flash to downgrade.
Also a tip, if you got stuck in recovery and yet cannot decrypt (doesn't ask for password/pin in TWRP), boot to fastboot mode, use the command "fastboot boot <the img file name for twrp>" so that you can boot directly to the img file from your PC. This way it will ask for your password.
Killua96 said:
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
Click to expand...
Click to collapse
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
maigre said:
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
Click to expand...
Click to collapse
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
jiatern said:
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
Click to expand...
Click to collapse
Flash Magisk again.
maigre said:
Flash Magisk again.
Click to expand...
Click to collapse
I did as well but it didn't help. Still the same.
jiatern said:
I did as well but it didn't help. Still the same.
Click to expand...
Click to collapse
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Why horrible?
PuCiNhOOO said:
Why horrible?
Click to expand...
Click to collapse
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Killua96 said:
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Click to expand...
Click to collapse
I think they pushed the update too fast from beta to stable... But yes, agree with the gestures bug... Its a fact, but the other stuff is good
Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
jiatern said:
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
Click to expand...
Click to collapse
I've wiped everything, then downgraded to Pie directly, but I was in a slightly different situation (only fastboot available).
Just to be sure flash the Oreo one and then upgrade to Pie.
With the whole A/B partition layout it should be easier to downgrade too right?