Database Info

Installing a Custom Rom [RESOLVED]

I have an unlocked Verizon Pixel, I extracted the modem and radio images so connectivity isn't a problem. I have tried multiple time to install a custom rom but I keep messing up somewhere along the way and I don't know where. Could someone outline the EXACT steps to install a custom rom - I think I am messing up the order in which to flash the boot signer...
I'm going to sleep because I have been trying for the past 2 hours, i won't respond until after I get off school tomorrow, so sarry

red80mini said:
I have an unlocked Verizon Pixel, I extracted the modem and radio images so connectivity isn't a problem. I have tried multiple time to install a custom rom but I keep messing up somewhere along the way and I don't know where. Could someone outline the EXACT steps to install a custom rom - I think I am messing up the order in which to flash the boot signer...
I'm going to sleep because I have been trying for the past 2 hours, i won't respond until after I get off school tomorrow, so sarry
Click to expand...
Click to collapse
First things first man. What OS and version? Win 8? Win 10? Linux? Ubuntu? OSX? Help me help you!

TheArkive said:
First things first man. What OS and version? Win 8? Win 10? Linux? Ubuntu? OSX? Help me help you!
Click to expand...
Click to collapse
How about assuming that the Android tools like ADB and fastboot are all setup correctly. There rest should be OS agnostic. The script file names with change to either ".sh" or ".bat"

hackworks said:
How about assuming that the Android tools like ADB and fastboot are all setup correctly. There rest should be OS agnostic. The script file names with change to either ".sh" or ".bat"
Click to expand...
Click to collapse
Assume? Really?
@red80mini
An "unlocked pixel" is not uncommon, if you mean network unlocked. That is actually standard these days. But unlocking the bootloader is a separate issue altogether. What version of android are you on? If you say 7.1.1 then you have a chance. d8pixel (unsupported but may work) can get your bootloader unlocked. If your version of android is 7.1.2+ then I'm afraid you are basically out of luck unless you search some dark corner of the web. No solution I've seen on this forum can guarantee an unlocked boot loader on a stock Pixel android version of 7.1.2 or higher.
Other than that, your version of OS (and if your tools are setup properly) also determine your options. Though your version of android on your locked Pixel might trump all...
Let us know. Reddit might have some bleeding edge craziness that might help. I've heard of rare instances of a Verison Pixel v7.1.2 being unlocked, but they are few and far between, and not yet easy to replicate.

hackworks said:
How about assuming that the Android tools like ADB and fastboot are all setup correctly. There rest should be OS agnostic. The script file names with change to either ".sh" or ".bat"
Click to expand...
Click to collapse
This must be a Windows thing, using Debian sid and there is nothing to "setup" for adb/fastboot, it just works

TheArkive said:
First things first man. What OS and version? Win 8? Win 10? Linux? Ubuntu? OSX? Help me help you!
Click to expand...
Click to collapse
Sorry for late responses haha, finals have me all out of sync. I actually figured it out, I just flashed the April bootloader image :silly:

TheArkive said:
Assume? Really?
@red80mini
An "unlocked pixel" is not uncommon, if you mean network unlocked. That is actually standard these days. But unlocking the bootloader is a separate issue altogether. What version of android are you on? If you say 7.1.1 then you have a chance. d8pixel (unsupported but may work) can get your bootloader unlocked. If your version of android is 7.1.2+ then I'm afraid you are basically out of luck unless you search some dark corner of the web. No solution I've seen on this forum can guarantee an unlocked boot loader on a stock Pixel android version of 7.1.2 or higher.
Other than that, your version of OS (and if your tools are setup properly) also determine your options. Though your version of android on your locked Pixel might trump all...
Let us know. Reddit might have some bleeding edge craziness that might help. I've heard of rare instances of a Verison Pixel v7.1.2 being unlocked, but they are few and far between, and not yet easy to replicate.
Click to expand...
Click to collapse
Sorry for late response! Finals are killing me, my Verizon Pixel actually came with 7.1.1 and was OEM unlockable for some reason I actually figured it all out by flashing the April bootloader :silly:

Qualcomm Crashdump

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

Question Recovery and Rooting

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!

Hi guys please seriously help me about Android 12

How are you everyone I am new here I need your serious help please all of great expert kindly focus to my problem it would be easy for you so my problem is actually recently a couple of days ago I just root my Samsung A7 2018 SM-A750F mobile and its Android version was and are now Android 10 okay now I have successfully rooted my this Samsung A7 2018 Android 10 version mobile after hard and painful time I successfully rooted but now I want I like and I really Desire to install latest Android release version Android 12 ok but I want to install custom rom Android 12 with rooted capability so what should I do now I have already my mobile rooted with Android 10 how could I root my mobile with Android 12 version with this model please is someone give a video guide it would be greatful thank you.

hloooooo :;/

I heard about this TreeUI. It works perfectly for me.
https://forum.xda-developers.com/t/...eeui-0-9-5-beta-for-a8-a8-a7-m20-m30.4252235/
Download the file from there, and in TWRP, flash it as a system image. It should automatically redirect you to the setup. Keep in mind that the resolution and DPI will be incorrect. I fixed it using Easy DPI Changer.
There are some known bugs though. For example, Samsung Camera doesn't work (third party apps will work), and the face unlock. I'd recommend you read the page carefully. If you need anything else, let me know.
EDIT: Just noticed you want Android 12, not 11. My bad. You can try flashing Pixel Experience on your phone. Check this video. Look at the youtuber of this video too, I'm sure you'll find much more help there.

Zanci19 said:
I heard about this TreeUI. It works perfectly for me.
https://forum.xda-developers.com/t/...eeui-0-9-5-beta-for-a8-a8-a7-m20-m30.4252235/
Download the file from there, and in TWRP, flash it as a system image. It should automatically redirect you to the setup. Keep in mind that the resolution and DPI will be incorrect. I fixed it using Easy DPI Changer.
There are some known bugs though. For example, Samsung Camera doesn't work (third party apps will work), and the face unlock. I'd recommend you read the page carefully. If you need anything else, let me know.
EDIT: Just noticed you want Android 12, not 11. My bad. You can try flashing Pixel Experience on your phone. Check this video. Look at the youtuber of this video too, I'm sure you'll find much more help there.
Click to expand...
Click to collapse
I tried flashing Android 12 GSI (Arrow and Corvus) but both GSI have lockscreen bug and I can't access my TWRP when flashed. I was wondering if you have any workarounds or fix for these issues. I also tried following the steps shown in the attached link to a YouTube video but there are no fix as well.

Just asked that yesterday, still waiting for reply. I really hope someone will finally make a custom rom designed for this device! GSI images have that bug, and some apps don't open. I'm so sick of staying on Samsung firmware.

Futazaki said:
I tried flashing Android 12 GSI (Arrow and Corvus) but both GSI have lockscreen bug and I can't access my TWRP when flashed. I was wondering if you have any workarounds or fix for these issues. I also tried following the steps shown in the attached link to a YouTube video but there are no fix as well.
Click to expand...
Click to collapse
Get Odin, and flash the stock firmware on your phone. However, this will erase all data on your device, so make a backup first. If you have any questions, feel free to ask me.

Zanci19 said:
Get Odin, and flash the stock firmware on your phone. However, this will erase all data on your device, so make a backup first. If you have any questions, feel free to ask me.
Click to expand...
Click to collapse
I tried doing this, reverting to the 2020 version to bypass the Knox Security and Encrypted Data sh*t but still, Android 12 has its bugs.

Futazaki said:
I tried doing this, reverting to the 2020 version to bypass the Knox Security and Encrypted Data sh*t but still, Android 12 has its bugs.
Click to expand...
Click to collapse
Just before installing android 12, you would want to go to TWRP > Advanced > Terminal and type this command:
Code:
mount /vendor;rm /vendor/lib64/hw/keystore*&&echo "persist.sys.binary_xml=false" >> /vendor/build.prop
Hope this helps

AaliShine said:
How are you everyone I am new here I need your serious help please all of great expert kindly focus to my problem it would be easy for you so my problem is actually recently a couple of days ago I just root my Samsung A7 2018 SM-A750F mobile and its Android version was and are now Android 10 okay now I have successfully rooted my this Samsung A7 2018 Android 10 version mobile after hard and painful time I successfully rooted but now I want I like and I really Desire to install latest Android release version Android 12 ok but I want to install custom rom Android 12 with rooted capability so what should I do now I have already my mobile rooted with Android 10 how could I root my mobile with Android 12 version with this model please is someone give a video guide it would be greatful thank you.
Click to expand...
Click to collapse
Sorry for being a little late, ForkLineage-19.1 GSI seems to be working fine on stock kernel, except MTP. Link : https://xiaomemeindex.com/treble/?dir=ForkLineage

random.tek said:
Just before installing android 12, you would want to go to TWRP > Advanced > Terminal and type this command:
Code:
mount /vendor;rm /vendor/lib64/hw/keystore*&&echo "persist.sys.binary_xml=false" >> /vendor/build.prop
Hope this helps
Click to expand...
Click to collapse
Thanks, I'll try this later today. I kinda settled on stock rom since GSI has bad battery backup. Does this get rid of the lockscreen bug?
EDIT: it returns an error saying
Code:
rm: can't remove '/vendor/lib64/hw/keystore*': No such file or directory
any help?

Futazaki said:
EDIT: it returns an error saying
Code:
rm: can't remove '/vendor/lib64/hw/keystore*': No such file or directory
any help?
Click to expand...
Click to collapse
Sorry for the late reply. The directory is already removed, so you should be good to go

How to go back to official firmware from PE 12

Hello all, I need some help.
I am currently on Pixel Experience 12, with Pixel Experience Recovery, but there doesn't seem to be a way to upgrade directly to 13 (please do let me know if I'm wrong and there is a way).
Apparently I need to be on OOS 13, however I've only had OOS 11 on this phone.l and I think it's long gone.
How do I get back on stock (any version) safely? If possible, without MSM as I don't have easy access to a Windows PC (just Linux and Mac).
Thanks!

gongolino said:
Hello all, I need some help.
I am currently on Pixel Experience 12, with Pixel Experience Recovery, but there doesn't seem to be a way to upgrade directly to 13 (please do let me know if I'm wrong and there is a way).
Apparently I need to be on OOS 13, however I've only had OOS 11 on this phone.l and I think it's long gone.
How do I get back on stock (any version) safely? If possible, without MSM as I don't have easy access to a Windows PC (just Linux and Mac).
Thanks!
Click to expand...
Click to collapse
You can use fastboot enhance instead of MSM, but it'll require pc anyway.
Booting twrp or orangefox recovery and flashing stock oos .zip from it, comes to my mind as a possible solution to your issue, without requiring PC access.