Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
grego34 said:
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
Click to expand...
Click to collapse
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
[email protected] said:
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
Click to expand...
Click to collapse
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
grego34 said:
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
Click to expand...
Click to collapse
I have had luck with this downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
TexnoViking said:
I have had luck with //oxygenos.oneplus.net/fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
Click to expand...
Click to collapse
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
grego34 said:
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
TexnoViking said:
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
Click to expand...
Click to collapse
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
grego34 said:
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
Click to expand...
Click to collapse
Great! I am glad you managed to fix your phone! Enjoy
Related
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
jjcdennis said:
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
Click to expand...
Click to collapse
Would appreciate some help...
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
clcdev said:
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
Click to expand...
Click to collapse
Thanks very much for the help.
Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.
Bruce777 said:
Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.
Click to expand...
Click to collapse
What version of the is are you on right now
I just reset with the msm tool, so it's back to OOS 9.5.3GM21AA.
It will take OTA updates fine up until before the 11 beta
My model is GM1917 (12GB RAM + 256GB ROM)
Bruce777 said:
Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.
Click to expand...
Click to collapse
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com
Gr8man001 said:
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com
Click to expand...
Click to collapse
I did that exact one a couple of times and when I get it back booted into stock the Wi-Fi does not work. The toggle stays in the off position.
Gr8man001 said:
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks Gr8man001.
Thought I had done this guide before and done it correctly but I buckled down and tried it once more (slow as molasses) and was able to get twrp and root! Appreciate it.
I understand that I may not be able to switch to Oxygen, but that's ok, I just need to get rid of all these Chinese apps
So,just got my OP9, literally few hours ago and just turned it on now, it's a LE2110 model (chinese?) flashed with OOS 11.2.4.4.LE25DA which seems to be an Indian version of OOS. Also, on Android if you turn on
USB debugging
You can disable apps via adb
It is possible. Just follow the guide and take your time doing it.
Official OnePlus 9 Oxygen to Color and back
hi everyone I got the official firmware How to install? 1.Download firmware 2.Put the file in the phone directory 3. Open system update, select local update Warning！ 1.Please backup your data！ 2.imei cannot be recognized correctly...
forum.xda-developers.com
I just tried that but I get 'Verification Failed' message when I try to update to Oxygen
I flashed the img manually, so I cannot help. Do not attempt anything over fastboot unless you know what you are doing, we already have several posts about people bricking their phone when they do not take care.
dotuletz said:
So,just got my OP9, literally few hours ago and just turned it on now, it's a LE2110 model (chinese?) flashed with OOS 11.2.4.4.LE25DA which seems to be an Indian version of OOS. Also, on Android if you turn on
USB debugging
You can disable apps via adb
Click to expand...
Click to collapse
Could you let me know how you did that, or point me to a thread please?
noname122414 said:
I flashed the img manually, so I cannot help. Do not attempt anything over fastboot unless you know what you are doing, we already have several posts about people bricking their phone when they do not take care.
Click to expand...
Click to collapse
I've used fastboot before, but never with this brand, I'm not sure which rom I should use or if the process is different
It is the img from the link I posted. I unpacked it and flashed it. But again, make sure you know what you are doing! Nobody can help you when you do a mistake there, read carefully. I will maybe later post a small guide on how to do it.
I am coming from a OnePlus 5, I literally just got my hands on OnePlus 9 a couple of hours ago. It looks like a few things has changed and things are not as straight forward as flashing a zip file in TWRP. I have been reading through a few things and just want to ask some questions.
Is TWRP even needed anymore? Most instructions on flashing roms is done via sideloading and booting into recovery via fastboot (some requires OSS while others LOS recovery).
What is the easiest way to root (on OSS 12)? Seems to be a good mixture of different ways to root and reading comments does not make it any easier, if anything even more confusing.
Which OnePlus 9 do you have? I'm assuming you're on global OOS 12 as I don't think 12 has come to the T-Mobile variant officially, but I wanted to double check and see if I could point you in the right direction.
posar said:
Which OnePlus 9 do you have? I'm assuming you're on global OOS 12 as I don't think 12 has come to the T-Mobile variant officially, but I wanted to double check and see if I could point you in the right direction.
Click to expand...
Click to collapse
I got the 2115 model, I believe that is global. Can you not just flash ROMs in TWRP anymore? I see all of the ROMs requires sideload which means you need a computer. I am a bit of a flashaholic and even though sideload is not a big issue.
Z-Blade said:
I got the 2115 model, I believe that is global. Can you not just flash ROMs in TWRP anymore? I see all of the ROMs requires sideload which means you need a computer. I am a bit of a flashaholic and even though sideload is not a big issue.
Click to expand...
Click to collapse
Not really, unfortunately. For most ROMs, it seems you have to go to the most recent version of OOS 11 and then flash from there.
posar said:
Not really, unfortunately. For most ROMs, it seems you have to go to the most recent version of OOS 11 and then flash from there.
Click to expand...
Click to collapse
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Z-Blade said:
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Click to expand...
Click to collapse
Yeah, it seems as if the simple TWRP days are over, at least for OnePlus. Maybe someone smarter than me will get it working flawlessly.
Z-Blade said:
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Click to expand...
Click to collapse
Can you tell me how did you obtain root on OSS 12? I tried severalmethods but ended up with errors an even some soft-bricked times. As you stated in the 1st message, there is plenty of ways around the internet and comments making it really confusing.
JustLeoSC said:
Can you tell me how did you obtain root on OSS 12? I tried severalmethods but ended up with errors an even some soft-bricked times. As you stated in the 1st message, there is plenty of ways around the internet and comments making it really confusing.
Click to expand...
Click to collapse
I downloaded the patched boot.img from the link below and I recommend you also down the normal stock boot.img as well.
[DISCONTINUED][OOS & PA] OnePlus 9 stock/patched boot images
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP. Hi! There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android...
forum.xda-developers.com
In that thread there is a link to a 'Great root guide', I used that root guide and the patched boot.img to root Android 12.
Nice! After several tries, some softbricks and a lot of haste for the different methos I finally got it rooted. Thank you man, it worked like a charm!
I was under the impression my phone was compatible and began the install instructions for LineageOS after unlocking my phone through this guide. I flashed the two partitions, flashed the recovery, attempted to boot into recovery and it gets stuck on boot. After attempting to ask the LineageOS community I realized Verizon's version is not supported, woo. I then tried to follow the unlock guide to flash back the stock image and Msm fails on Param preload with the error "Device not match image." Googling that I only found someone implying they were using the incorrect global image, however, I know I'm not. Is it possible to recover my phone now and if so, how?
LineageOS is a base ROM for many other custom ROMs such as crDroid. Try using their recoveries and installation guides; crDroid worked perfectly in the past.
Xryphon said:
LineageOS is a base ROM for many other custom ROMs such as crDroid. Try using their recoveries and installation guides; crDroid worked perfectly in the past.
Click to expand...
Click to collapse
I'm waiting for the phone to recharge now before attempting. I feel like it will fail however as the crDroid steps require you having stock 11 on "both slots." I am too new to this scene to understand what that means or if I can even do that anymore.
rusty-op8 said:
I'm waiting for the phone to recharge now before attempting. I feel like it will fail however as the crDroid steps require you having stock 11 on "both slots." I am too new to this scene to understand what that means or if I can even do that anymore.
Click to expand...
Click to collapse
You might want to the follow this guide as a basic requirement for flashing any Custom ROM on 'instantnoodle'.
It's always good to re-read, proofread and re-read again before proceeding.
rodken said:
You might want to the follow this guide as a basic requirement for flashing any Custom ROM on 'instantnoodle'.
It's always good to re-read, proofread and re-read again before proceeding.
Click to expand...
Click to collapse
Thank you for the resource. I will attempt this instead once I can. I see that it makes a very important note about copying slot a to b to prevent potential hard-bricks. Since the "official" guide I started with did not mention that before I attempted going down this route, does this mean I'm ruined anyways? I only flashed 2 "boot" images and then the recovery image when this happened. This is all because I was using 19.1 without realizing that a) it's A12 and b) one of the maintainers said the Verizon version wasn't supported. Seeing as I can grab the last 18.1 from the link you provided me, maybe there's hope after all.
rusty-op8 said:
Thank you for the resource. I will attempt this instead once I can. I see that it makes a very important note about copying slot a to b to prevent potential hard-bricks. Since the "official" guide I started with did not mention that before I attempted going down this route, does this mean I'm ruined anyways? I only flashed 2 "boot" images and then the recovery image when this happened. This is all because I was using 19.1 without realizing that a) it's A12 and b) one of the maintainers said the Verizon version wasn't supported. Seeing as I can grab the last 18.1 from the link you provided me, maybe there's hope after all.
Click to expand...
Click to collapse
All is not lost as long as your device can power on and is not completely bricked.