Database Info

[ROOT][TRIAL][MAGISK] P20 Pro - Try out on Rooting Method

Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.

That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.

Fingers crossed twrp is possible soon

Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well

Would this method work on CLT-L09 model? Thanks

danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does

This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse

fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address

Great, thanks for that! I managed to find it on allrom.ir

Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post

danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?

otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks

danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?

otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?

danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well

otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!

danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command

otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol

danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.

danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.

[Pie][OB2] How to fix "Your device is corrupt" on boot

Hi, i share my personnal experience, struggled to figure out what was wrong after flashing OB2 but it seems it's all good now.
Did this from OpenBeta2, no specific firmware required i guess as long as the tool we will use is there to erase everything.
I used the official 3.2.3.0 twrp to avoid strange encryption thing (link here)
a user reported this bug because of a custom recovery
1. Download MSMDownloadTool. The 4 files in the MEGA links seems to be requrired so download as zip the whole thing.
2. Follow the guide i quoted then check my instructions
credit to @Fivegates
Guide how to revive your op6:
First of all, you need to access to fastboot mode, if you can't , contact Oneplus support, then have a windows computer and download these file and drivers qualcomm ( https://androidfilehost.com/?fid=24052804347798730) and extract in one folder.
After you have all the file ready, plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug.
Now you have to go in Windows test mode to not let him install default drivers, so:
windows key (on keyboard) + X, windows powershell (or normal prompt) administrator and write and enter: bcdedit /set testsigning on ( you will repeat the same process with "off" to stop the test mode after you will finish to do all the things).
Reboot the system and you could see in bottom right corner the test mode, now you are ready to install properly drivers.
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process (https://www.youtube.com/watch?v=PpLvmID1wdI)
Right click con US8_BULK in device manager and update drivers by system files (go to the folder's drivers you had extracted before).
Now you should see qualcomm drivers under port (COM).
You are ready to let the tool to do all the stuff, so let plugged the phone, always powered off, right click on msmdownloadtool and execute as administrator.
You should see your device and click start to begin the process; if it gives you some error (like sahara or something else), unplug, power on, power off and the plug it again, now it should be fine.
And that's it, the tool will do all the work and, at the end, you will have like a brand new phone ready to a new setup.
EDIT: if you are stucked in bootloader, you have only to power off and continue with the part: ... hold for 5 seconds vol up... (it happened in page 4)
Click to expand...
Click to collapse
lil shortcut guide (might be wrong lol check @Fivegates post if scared)
# go to Device manager, delete your op6 drivers
# enable the test mode with
Code:
bcdedit /set testsigning on
(don't forget to turn off when you're done)
# reboot your pc
# open msmdownload
# power off phone, press vol up and connect phone to pc
# upgrade mode ticked, click once on the only line you see and hit START
# wait
# unplug when it's done
3. Once process is over the phone is back stock 5.1.5 with locked bootloader
4. update to OB2 via local update in settings
Comprehensive guide to update manually
5. unlock your bootloader
6. you should be able to boot on OB2 without that red annoying popup, flash a twrp and magisk whatever
Useful Guide to Unlock Bootloader, Flash TWRP, Root and more
VISUAL GUIDE
Tell me if it works for you too, personnally i've been able to unlock bootloader, flash the latest twrp and magisk

I am living along with corrupted device no problem at all.

I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.

Toni Moon said:
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Click to expand...
Click to collapse
Same here for me. I tried the method mentioned in the op too. It gives the same error once I update to pie. The error is still there for hydrogen and oxygen. Dp3 doesn't have that issue

Toni Moon said:
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Click to expand...
Click to collapse
Yeah that "issue" is terrific :crying:
Did you try this way ?

80s Baby said:
Same here for me. I tried the method mentioned in the op too. It gives the same error once I update to pie. The error is still there for hydrogen and oxygen. Dp3 doesn't have that issue
Click to expand...
Click to collapse
you tried this and it fails ?

Neil_Armstrong_ said:
you tried this and it fails ?
Click to expand...
Click to collapse
Yes it does fail for me. It clears that warning when it's downgraded but once updated to any version of pie. The warning comes back again

80s Baby said:
Yes it does fail for me. It clears that warning when it's downgraded but once updated to any version of pie. The warning comes back again
Click to expand...
Click to collapse
Huh
Did you unlock bootloader before or after updating to Pie ? I honestly don't know what/where the wolf is

Neil_Armstrong_ said:
Huh
Did you unlock bootloader before or after updating to Pie ? I honestly don't know what/where the wolf is
Click to expand...
Click to collapse
Before..I guess right around the first update 5.1.6 or 7. That's when I bought the phone

80s Baby said:
Before..I guess right around the first update 5.1.6 or 7. That's when I bought the phone
Click to expand...
Click to collapse
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings

Neil_Armstrong_ said:
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Click to expand...
Click to collapse
Yes, this is the way

Neil_Armstrong_ said:
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Click to expand...
Click to collapse
Can I root my device after updating? Coz that's when the issue normally comes in as well

80s Baby said:
Can I root my device after updating? Coz that's when the issue normally comes in as well
Click to expand...
Click to collapse
Hi
I did exactly the same process as mentioned above and I have no problem with root
I first unlocked bootloader then fastbooted twrp + installer.zip
Then I flashed magisk and tons of stuff no red warning
Keep me updated

Neil_Armstrong_ said:
Hi
I did exactly the same process as mentioned above and I have no problem with root
I first unlocked bootloader then fastbooted twrp + installer.zip
Then I flashed magisk and tons of stuff no red warning
Keep me updated
Click to expand...
Click to collapse
Tried this last night it is still the same. Everything went well until I flashed magisk. That's when I got the warning this time.

Did you flash blu spark twrp?
This method works to me..
80s Baby said:
Tried this last night it is still the same. Everything went well until I flashed magisk. That's when I got the warning this time.
Click to expand...
Click to collapse

Toni Moon said:
Did you flash blu spark twrp?
This method works to me..
Click to expand...
Click to collapse
Yes, I haven't tried the official one yet..should I try that out instead?

80s Baby said:
Yes, I haven't tried the official one yet..should I try that out instead?
Click to expand...
Click to collapse
Official TWRP

I had the same error when I dirty flashed from 5.1.11 to the official 9.0. The method from OP fixed it. I'm back to 9.0 with TWRP, Magisk, and custom kernel without the annoying message.
Thanks a lot!

sasho36 said:
I had the same error when I dirty flashed from 5.1.11 to the official 9.0. The method from OP fixed it. I'm back to 9.0 with TWRP, Magisk, and custom kernel without the annoying message.
Thanks a lot!
Click to expand...
Click to collapse
can I still use the bluspark twrp or no?

R0ttenB4ndit said:
can I still use the bluspark twrp or no?
Click to expand...
Click to collapse
just read bro used official twrp 3.2.3

"System update installation failed" while trying to install Q dp3, what did I miss?

"System update installation failed" while trying to install Q dp3, what did I miss?
I am currently on oxygenOS 9.0.8, both slots completely stock. I have unlocked the bootloader and enabled USB debugging.
I am trying to install Q dp3, but everytime I select Q dp3 zip file and press ok, update manager immediately says "System update installation failed" with no specific error code or any leads.
I have tried:
-Redownloading the Q dp3 file from here (https://oxygenos.oneplus.net/OnePlus6Oxygen_22_OTA_003_all_1907120020_wipe_ae2a3b38959345b1.zip)
-Rebooting and trying again
-Relock and unlock the bootloader
-factory reset within the settings
The strange thing is, I can normally install oxygenos 9.0.8 full update file. So I suspected problem of the dp3 file. But redownloading didn't solve the problem.
Is there something I have missed out? Some settings I have to do? Specific conditions?
Searching haven't helped me much(I searched everywhere, but I think nobody has my problem).
If someone can help me, I will be grateful. Thanks!

Since your bootloader is unlocked anyway, you can flash Android Q DP3 zip using TWRP. Flash it on both slots. Haven't tried blu_spark, but mauronofrio's TWRP works with Q. Don't forget to format data.

remewer said:
Since your bootloader is unlocked anyway, you can flash Android Q DP3 zip using TWRP. Flash it on both slots. Haven't tried blu_spark, but mauronofrio's TWRP works with Q. Don't forget to format data.
Click to expand...
Click to collapse
Thanks! Will try that!
Can I ask you one more question? What is the best and convenient way to go back to stock? I used nexus 4 and mi a1 before, and both devices just had to use
fastboot roms to go back to complete stock. Is it same with OP6? Or do I have to use MSM tool or other things?

ddaggebi said:
Thanks! Will try that!
Can I ask you one more question? What is the best and convenient way to go back to stock? I used nexus 4 and mi a1 before, and both devices just had to use
fastboot roms to go back to complete stock. Is it same with OP6? Or do I have to use MSM tool or other things?
Click to expand...
Click to collapse
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.

remewer said:
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
Click to expand...
Click to collapse
Thanks you! Now I can flash away~

remewer said:
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
Click to expand...
Click to collapse
I successfully flashed Q dp3 thanks to you.
However, I can't boot TWRP with fastboot boot twrp.img method. Before updating to Q, it worked. Now, cmd line shows FAILED (remote: 'unknown command').
I have tested with newer versions of Fastboot, but the results were the same. Anybody knows how to solve this problem?

ddaggebi said:
I successfully flashed Q dp3 thanks to you.
However, I can't boot TWRP with fastboot boot twrp.img method. Before updating to Q, it worked. Now, cmd line shows FAILED (remote: 'unknown command').
I have tested with newer versions of Fastboot, but the results were the same. Anybody knows how to solve this problem?
Click to expand...
Click to collapse
Yep, it's a known issue with DP3 (or possibly earlier builds). Anyway, every time you flash a ROM, may it be stock or custom, you should always flash TWRP next. For now, you could try downgrading to Pie using fastboot ROMs.

remewer said:
Yep, it's a known issue with DP3 (or possibly earlier builds). Anyway, every time you flash a ROM, may it be stock or custom, you should always flash TWRP next. For now, you could try downgrading to Pie using fastboot ROMs.
Click to expand...
Click to collapse
Thank you so much. I don't know what I could've done without you. I'll try to downgrading. Still not accoustomed to how roms work in OP6. Guess I'll study more.
Again, thank you for kindly answering my noobish questions! It means a lot to me

ddaggebi said:
Thank you so much. I don't know what I could've done without you. I'll try to downgrading. Still not accoustomed to how roms work in OP6. Guess I'll study more.
Again, thank you for kindly answering my noobish questions! It means a lot to me
Click to expand...
Click to collapse
No problem. Read more about A/B partitions. It's actually just as easy to mod our phone once you know how A/B partitions work.

General T-mobile Stock boot.img

I have seen a few people still in need of the stock boot.img 11.2.2.2. for t-mobile Oneplus 9 (LE2117) So I have attached it for those in need!

Here is the stock boot.img for 11.2.3.3 Oneplus 9 T-Mobile

Jg1234 said:
I have seen a few people still in need of the stock boot.img 11.2.2.2. for t-mobile Oneplus 9 (LE2117) So I have attached it for those in need!
Click to expand...
Click to collapse
Alright so I've been sitting on this file for a few days. Willl I be able to flash this to my LE2117 on 11.2.2.2 and relock bootloader and be back to stock? Or will my system still be corrupt if I relock? G just wait for a non pro msm tool?

hiryupd said:
Alright so I've been sitting on this file for a few days. Willl I be able to flash this to my LE2117 on 11.2.2.2 and relock bootloader and be back to stock? Or will my system still be corrupt if I relock? G just wait for a non pro msm tool?
Click to expand...
Click to collapse
I'm not sure how you went about rooting it originally, but if you have only flashed boot.img and nothing else. Then yes that is how I would go about doing it on my phone, if I was wanting to go back to locked bootloader. I don't see any issue with doing that after you install the stock boot.img.

Jg1234 said:
I'm not sure how you went about rooting it originally, but if you have only flashed boot.img and nothing else. Then yes that is how I would go about doing it on my phone, if I was wanting to go back to locked bootloader. I don't see any issue with doing that after you install the stock boot.img.
Click to expand...
Click to collapse
So I took magisk and downloaded the global OP and took boot.img from that magisk patched it and installed it then unlocked so I had the backup of THAT boot, not the Tmo one.

hiryupd said:
So I took magisk and downloaded the global OP and took boot.img from that magisk patched it and installed it then unlocked so I had the backup of THAT boot, not the Tmo one.
Click to expand...
Click to collapse
Yes That sucks but we all learn from are mistakes.. Fastboot Flash this stock boot.img and then either lock bootloader or if you want to have root? have magisk patch same stock boot.img and reinstall.
P.s. I also have been able to update over ota by just restoring stock boot.img in magisk.
Incase you wanted to keep rolling out with root. If you need help.i will try to make a step by step way I did it.

Jg1234 said:
Yes That sucks but we all learn from are mistakes.. Fastboot Flash this stock boot.img and then either lock bootloader or if you want to have root? have magisk patch same stock boot.img and reinstall.
P.s. I also have been able to update over ota by just restoring stock boot.img in magisk.
Incase you wanted to keep rolling out with root. If you need help.i will try to make a step by step way I did it.
Click to expand...
Click to collapse
Went ahead and reflashed that boot.img. Worked fine. Now I can relock with no other steps at this point correct?

Correct.

Thank you my friend. This is most helpful. I was reluctant to root without a good way to return to stock for updates.

Jg1234 said:
I have seen a few people still in need of the stock boot.img 11.2.2.2. for t-mobile Oneplus 9 (LE2117) So I have attached it for those in need!
Click to expand...
Click to collapse
safetynet api error ？ How to do？

Magisk 22.1 has a safety net error. Download this app and it will show it passes. Also widevine is L1 https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest

Jg1234 said:
Magisk 22.1 has a safety net error. Download this app and it will show it passes. Also widevine is L1 https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest
Click to expand...
Click to collapse
Thank you! But I broke the system. Now that the update downloads more than half of the time, an error will occur. Do you have a backup of the system firmware or all system images？

This is maybe a stupid question but how do I flash this stock.img using Magisk?

iSkyJIE said:
Thank you! But I broke the system. Now that the update downloads more than half of the time, an error will occur. Do you have a backup of the system firmware or all system images？
Click to expand...
Click to collapse
I don't.. I would try factory reset or at least clear cache a few times consecutively. Sounds like there is a cache causing a issue with update.

inspron said:
This is maybe a stupid question but how do I flash this stock.img using Magisk?
Click to expand...
Click to collapse
Well you would fastboot the stock boot.img. but if you have never tampered with your original? And wanted root? you would have magisk patch the stock boot.img and then fastboot your.img. if you search how to root with boot.img you will find how to do it with the files above

Jg1234 said:
I don't.. I would try factory reset or at least clear cache a few times consecutively. Sounds like there is a cache causing a issue with update.
Click to expand...
Click to collapse
I have tried to clear the cache and format, but the update is still halfway through the download and an error occurs

iSkyJIE said:
I have tried to clear the cache and format, but the update is still halfway through the download and an error occurs
Click to expand...
Click to collapse
I know it sounds stupid but check Google play updates. Since you reset the phone. Just a thought have heard it cause issue with ota . Sorry Bud!

Jg1234 said:
I know it sounds stupid but check Google play updates. Since you reset the phone. Just a thought have heard it cause issue with ota . Sorry Bud!
Click to expand...
Click to collapse
Thank you. Convert TMO to Global, EU, or other variant I flashed my phone to the international version based on this article, and then updated it to EU 11.2.3.3, everything worked normally

iSkyJIE said:
Thank you. Convert TMO to Global, EU, or other variant I flashed my phone to the international version based on this article, and then updated it to EU 11.2.3.3, everything worked normally
Click to expand...
Click to collapse
Would you be able to share which file did you use to convert to global? I just got my unlock bootloader token from oneplus right now.

infamousvincci said:
Would you be able to share which file did you use to convert to global? I just got my unlock bootloader token from oneplus right now.
Click to expand...
Click to collapse
In the top thread, you can download the global and European firmware Rom. you only need to replace your own modem file

Custom ROM

Does anyone know a ROM/Gapps that actually works for this device? OnePlus 8 IN2015

Kerrylee1738$$$ said:
Does anyone know a ROM/Gapps that actually works for this device? OnePlus 8 IN2015
Click to expand...
Click to collapse
Did you already search this page?

rodken said:
Did you already search this page?
Click to expand...
Click to collapse
Yes...so far it's a toss up. It's either the ROM that somehow messes up and bricks the phone or the Gapps bootloops. I have literally used the MSM tool probably 15 times maybe more in the last 12hrs.

Kerrylee1738$$$ said:
Yes...so far it's a toss up. It's either the ROM that somehow messes up and bricks the phone or the Gapps bootloops. I have literally used the MSM tool probably 15 times maybe more in the last 12hrs.
Click to expand...
Click to collapse
As a precaution, it's usually the Custom ROM which is why a good number of folks revert back to stock and stay put.

It sideloaded a little weird but it's working. Only issue I'm having now is the Gapps won't sideload nor flash...it says error wrong format. Tried unpacking and repacking no luck And it won't let me boot TWRP at all. I have to do fastboot reboot just to get it out. Guess I'm going to have to use the unbrick tool just to get stock and try something other than lineage 19.1

Kerrylee1738$$$ said:
It sideloaded a little weird but it's working. Only issue I'm having now is the Gapps won't sideload nor flash...it says error wrong format. Tried unpacking and repacking no luck And it won't let me boot TWRP at all. I have to do fastboot reboot just to get it out. Guess I'm going to have to use the unbrick tool just to get stock and try something other than lineage 19.1
Click to expand...
Click to collapse
Try to utilize fastboot as a method to flash versus sideloading.