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!
Related
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
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've searched and soft bricked and restored via msm and even got twrp on one time. Is there a straight forward guide anywhere that shows the process of going from stock TMobile android 10 or 11 to the global device software? Im either misunderstanding it or just can't find it. The one guide that i thought was correct was good all the way until it got to the part where it said not for branded devices but there's not actually a link that leads to a section to do branded devices. Please help as this thing is almost unusable on mint mobile with the current stock rom.
I mean I know there is the wip guide in the other forum. But I can't seem to get out of crash dump or fastboot loop so I figured maybe that's the wip part of it?
I can't stress enough to read, read, read. There are not that many threads here so it should be pretty easy to do. I'm posting the link to convert to global for you. Used it many times. In fact I used it this weekend. Happy modding!
[ROM][STOCK][FASTBOOT][OP8] Stock Fastboot ROMs for OnePlus 8
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com
.
i dont know if you have been succesful yet or not but the WIP guide is the way to go. Like you i kept getting flash dump error then flash back to t-mobile and very frustrated.
but if you read through the forum with the wip guide, somewhere it mentions that you have to first flash an earlier t-mobile version of OOS then you can flash the same version Global OOS and just like that it worked for me. After you can upgrade to the latest.
i hope that helps.
I am reading conflicting things trying to figure this out. Can someone who is absolutely sure please let me know? I can't afford to waste another entire day making educated guesses.
It doesn't seem like the TWRP version numbers correspond to the Android builds, but if they do please correct me.
Thank you
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
RokCruz said:
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
Click to expand...
Click to collapse
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
didymus said:
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
Click to expand...
Click to collapse
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
RokCruz said:
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
Click to expand...
Click to collapse
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I know I installed it correctly too because in the past week I've installed TWRP so many times I could practically do it blindfolded now.
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things. I just hope yall don't ban me before then, lol.
didymus said:
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things.
Click to expand...
Click to collapse
That screenshot was for this
didymus said:
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly.
Click to expand...
Click to collapse
If you're in android 11 forget the thread about android 9 & 10
RokCruz said:
That screenshot was for this
If you're in android 11 forget the thread about android 9 & 10
Click to expand...
Click to collapse
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
didymus said:
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
Click to expand...
Click to collapse
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
RokCruz said:
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
Click to expand...
Click to collapse
Im trying to install TWRP. I do it exactly how the thread says and then system never boots into OOS again and I just have fastboot and TWRP. Basically bricked. Then when I try to reboot to recovery which should be TWRP (right?) it just boots me into the regular "recovery".
Thats why I think this is broken and I resigned to just not updating into 11.
I've never had this much trouble doing this. Ever. Not even close.
Edit: Yeah, so I patched the 11 boot.img and now I have root again, but no TWRP. I don't know how to keep both in 11. When I was 9.5.3 I used the Magisk A/B retention script and kept it, but once it became 11 it bricked the phone and the TWRP logo just flashed. I had to reflash the OTA to boot again. Thats another reason why I thought it didn't work for OOS11.
Starting to think I have a learning disability, lmao. Wish I was joking.
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
caca12357 said:
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
Click to expand...
Click to collapse
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
@caca12357 I'm going to try to do a local OTA upgrade then before I reboot run the A/B retention script and then Magisks option for OTA and see if that does anything. If TWRP works for 11 something like that should make it work, but who knows. Have you messed with A/B Retention at all?
If you want to PM me we can figure it out together.
Thread moved to proper section
didymus said:
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
Click to expand...
Click to collapse
Yes, and do you know how I flash TWRP to my OP7P? First, I flashed Pixel Experience recovery by fastboot, and I used Pixel Experience recovery to sideload the official TWRP. (In other words, I never can temporarily or permanently flash TWRP directly). If I did not want to convert my /data to the f2fs file system I will not do this meaningless work...
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.