Database Users

Problems updating from 5.1.7 to 9

Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!

richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.

richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?

strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!

richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back

richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).

strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.

How should I update my phone's software if I have rooted it?

Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.

Ebeninyo said:
Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.
Click to expand...
Click to collapse
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda

strongst said:
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda
Click to expand...
Click to collapse
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.

Ebeninyo said:
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.
Click to expand...
Click to collapse
With which recovery and rom are you able to access your internal storage?

strongst said:
With which recovery and rom are you able to access your internal storage?
Click to expand...
Click to collapse
I've only tried using TWRP as my recovery, Pixel experience rom and oxygen os rom. The thing is because upon entering the phone after flashing a rom you can't access the internal storage of the phone with TWRP because phone encrypts itself. That means I can't dirty flash it and need to wipe everything out with TWRP then reboot TWRP again and install new rom after that flash magisk and reboot to system and set everything up from the scratch.
When I started this thread I didn't knew how to dirty flash a rom. Now I know and realize the problem I'm having is phone's encryption.

UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.

Ebeninyo said:
UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.
Click to expand...
Click to collapse
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.

strongst said:
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.
Click to expand...
Click to collapse
Can you be able link me that patch and instructions?

Ebeninyo said:
Can you be able link me that patch and instructions?
Click to expand...
Click to collapse
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.

strongst said:
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.
Click to expand...
Click to collapse
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.

Ebeninyo said:
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.
Click to expand...
Click to collapse
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.

strongst said:
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.
Click to expand...
Click to collapse
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.

Ebeninyo said:
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.
Click to expand...
Click to collapse
Cool:good:

Oneplus 5 hardstuck bootloop. Please help me out, I've tried everything!

Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!

You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.

Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!

BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190

strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.

BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?

strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)

BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk

strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop

BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop

My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter

BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up

strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!

BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?

strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!

PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!

BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter

Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!

[appeal][p]z3 dual D6633 patch for running z3 roms

hi guys
i need a patch for z3 dual that would be able to run z3 single-sim roms on z3 dual in android 9 pie
can any develpoer make it for me?please
thanks

please
somebody help meeeeeee

I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.

Zerikwan said:
I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.
Click to expand...
Click to collapse
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom

foli2 said:
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom
Click to expand...
Click to collapse
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.

Zerikwan said:
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.
Click to expand...
Click to collapse
i got frustrated completely

flashing 10.3

Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance

CptUnicorns said:
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
Click to expand...
Click to collapse
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear

Striatum_bdr said:
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Click to expand...
Click to collapse
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2

CptUnicorns said:
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
Click to expand...
Click to collapse
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM

Striatum_bdr said:
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Click to expand...
Click to collapse
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.

CptUnicorns said:
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
Click to expand...
Click to collapse
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.

OhioYJ said:
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
Click to expand...
Click to collapse
That does clear up things for me, I've either mis-read or not read that when on slot A you are actually flashing slot B and Visa versa.
I'll be flashing both my slots to 10.3.1 just so they're fully updated. ( A is my main)
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?

CptUnicorns said:
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
Click to expand...
Click to collapse
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.

OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Great stuff. Thought I understood from how you explained it. I'll check that guide as well and have it to hand just incase.

OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Something didnt want to play when I was flashing... Got to flashing gapps and magisk, gapps flash gave me a error 64 and i got magisk installed, booted, now I've got no twrp and when I use fastboot it just softbricks then restarts after about 5 minutes, I'm gonna try booting from 3.2.3-2 as that was fine and hope I can boot into recovery and just go lineage I think for something new
EDIT
So I used fastboot --set-active=a, managed to get back to twrp so now its flashed on both again. In the process of flashing lineage now, hopefully this wont chuck another error at me for gapps