I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?
I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well
In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.
I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?
Hi,
I installed custom ROM Lineage OS 14 + Micro G on my 1032. Then I root it with SuperSu. But after that I would to install Magisk (to get sppof location working), but both are incompatible.
So I remove SuperSu with the unSu script from XDA.
Then tried to install Magisk v23 but I need to flash the boot.img from my ROM.
Where can I find it ?
I found stock for Android 4.4 but now I'm on android 7 with LOS 14.
Thanks
I'm on Stock OOS 11 with all the latest firmware installed and no more updates from oneplus.
So I tried to flash lineage os 18.1 on my Oneplus 6 (enchilada).
I followed every step, unlock bootloader, flash lineage recovery to boot and use lineage recovery to copy partitions and install lineage os
and open gapps.
But when I reboot finally I get stuck in the Lineage OS boot animation. Can't get past that even after 2+ hours. Tried to reflash many times
with the same procedure.
Finally I gave up and used MSM Download Tool to get back to stock OOS 10 and then updated again to the latest version of OOS from oneplus.
Now what should I do different, to install Lineage OS 18.1 in my oneplus 6(enchilada)?
SOLVED:
The latest nightly has a major bug hopefully the future release may fix it. Until then use 220104 nightly and don't update through OTA.
Wait until next build comes with the reverted commit.
Revert "adbconnection: don't spin if adbd isn't running." Breaks boot for many devices.
Hi!
I recently made an update to Android 12 (OxygenOS 12.1) on my AC2003. So I tried to install TWRP on it with this Version: https://twrp.me/oneplus/oneplusnord.html and with this one https://forum.xda-developers.com/t/...ficial-twrp-for-oneplus-nord-testing.4142149/ . The last one was working fine when I had Android 11 still. I set up the ADB drivers as mentioned here: https://developer.android.com/studio/run/win-usb but when I either try to flash or boot any of the 2 images nothing happens :/ any idea what I'm doing wrong?
from what i've gathered, twrp is not working with 12 on oos yet. msm back to 11 and sacrifice. sorry.
Hello folks!
I have recently purchased a Oneplus 7 Pro phone with the intention of installing Kali Nethunter on it. I followed David Bombal’s Youtube video guide to do, and I had a soft brick on the phone. I unlocked the bootloader, rooted the phone successfully with Magisk. I had a Qualcomm error immediately after install dm-verity through TWRP.After tackling this issue, and learning a lot as a result, I managed to use the MSM tool successfully to restore the device. Afterwards, I managed to successfully install Kali Nethunter OxygenOS 11/Custom A11, and afterwards, I installed the kimocoder kernel 4.14 for the Oneplus 7 Pro. I had Kali Nethunter working successfully afterwards, albeit without usable Bluetooth in the Kali Nethunter app. I wanted to achieve the following, and I humbly ask for your guidance on these goals:
1. I initially wanted to dual boot Lineage OS 20and the OxygenOS11 Kali Nethunter, but realized that the security settings would be sacrificed realistically, as one rom would affect the other. Have you managed to do so ( I am intrigued by the Pixel Experience 13 ROM and Paranoid Android 13 as well)?
2. My current idea was to backup my Kali Nethunter rom, and boot TWRP (I boot it with the adb tools, as I could not install TWRP again to the recovery partition). Afterwards, I would wipe the partitions ( except boot and the data partition, which would have my /sdcard data etc) and install my rom of choice(It would be PixelExperience 14, LineageOS 20 or ParanoidAndroid 13. If CalyxOS or GrapheneOS would be available for my device, I would install them but they are not). After managing to do so successfully, the plan was to make a backup of everything, and then restore my rom of choice after backing up the roms of course. While researching the mentioned roms, I saw that updating to Android 12 is needed in order for the correct firmware to be in place. I am concerned that my restored backup of the Kali Nethunter rom would stop working.
the reasoning behind this is to keep the two completely separate from each other for security reasons. I am studying cybersecurity, and I wanted to practice sensible isolation. The other rom would be in place in order to daily drive the phone. I appreciate your assistance and wisdom on this folks, and I will happily provide any information that would help in accomplishing my mission, and complete the steps/research necessary. I am disappointed that we do not have a Nethunter rom that is based on Android 12/13, but i completely understand that it could be due to drivers/kernel issues.
I have included the following information about the Nethunter kernel that is installed currently :
4.14Oxygen OS 11BT_RFCOMM, HID-4, Injection, QCACLD, RTL8812AU kimocoder