Develop Bugs

[TOOL][PIXEL 2 XL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

Cant wait to try it

Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you

I'll wait for a few others as well

Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly

does this do the critical unlock as well?

razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work

mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply

razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works

This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:

jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?

mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate

jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first

Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?

almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol

almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key

mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.

Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.

dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.

dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??

[Magisk] Root P20 [EML]

Since I promised ill patch ramdisk of P20 (versions) ill try live up to it my promise. Please do note that this is untested since currently I don't own nor any device of P20 line
Installation instructions.
Download the zip for your device and unpack it to your computer.
Boot your phone into bootloader (volume down and plug in cable)
Type: fastboot flash ramdisk yourpatchedboot.img
Reboot!? Proofit!?
Edit: if you have issues with Magisk and safetynet read
secXces_debaki said:
Like i wrote on p20 pro forum @LastStandingDroid you should include that here too..
After flashing the patched ramdisk they should install magisk over magisk manager again to pass safteynet and install modules.
Click to expand...
Click to collapse
Downloads:
EML-L29
https://mega.nz/#!gPBCCCyI!HOCiXH2Zrl84l01PT99U_ElMMuC_JukjgS47DZGkqPQ
Eml-l09?
https://mega.nz/#!dOoAnaIS!MMw2QFp_JNegVG0g95RrVm_AmqDpvtO-wGQX1LLkmYs
EML-TL00/AL00 8.1.0.106
https://mega.nz/#!hKQXgCKT!C2tObO92jyuYBvrVrPeOIfWHSkpVeUCtIgjfuhENaCo

EML-L29 working
EML-L09 untested
EML-AL00/TL-00 untested
Everyone should be pre rooted though
Sent from my DUK-L09 using Tapatalk

will test EML-TL00/AL00 8.1.0.106 tomorrow,thks~!

Thanks!
I'm going to test it on the p20.

Ladies and gentlemen soon a twrp will be hopefully released for P20 pro (tested) and should hopefully work on P20 which will have decryption support.
Don't believe me?
I'm talking to the developer who built it so stay tuned you'll eventually see it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my DUK-L09 using Tapatalk

quick question, does the bootloader have to be unlocked to flash magisk?

Samueldanny said:
quick question, does the bootloader have to be unlocked to flash magisk?
Click to expand...
Click to collapse
Yes

LastStandingDroid said:
Since I promised ill patch ramdisk of P20 (versions) ill try live up to it my promise. Please do note that this is untested since currently I don't own nor any device of P20 line
Installation instructions.
Download the zip for your device and unpack it to your computer.
Boot your phone into bootloader (volume down and plug in cable)
Type: fastboot flash ramdisk yourpatchedboot.img
Reboot!? Proofit!?
Click to expand...
Click to collapse
Hello!
First and foremost, massive thank you for your work.
Second: it, unfortunately, doesn't work for me on my EML-L29TWRP (or I just messed up something). I followed the flash trough Fastboot command, installed magisk manager app but there is no supersu available like on your screenshots I have unlocked my bootloader properly ( get all warnings how my phone cant be trusted).
I just need superSU to remove retail demo app but if necessary I'm willing to debug software.
Also, I have screen captures to show my issue but because I am a new user I cant share them.

LastStandingDroid said:
Ladies and gentlemen soon a twrp will be hopefully released for P20 pro (tested) and should hopefully work on P20 which will have decryption support.
Don't believe me?
I'm talking to the developer who built it so stay tuned you'll eventually see it
View attachment 4476320View attachment 4476321
Click to expand...
Click to collapse
This is a good news. We all wait for this famous twrp, so if it is almost operational it's really an excellent news.

Foglito said:
Hello!
First and foremost, massive thank you for your work.
Second: it, unfortunately, doesn't work for me on my EML-L29TWRP (or I just messed up something). I followed the flash trough Fastboot command, installed magisk manager app but there is no supersu available like on your screenshots I have unlocked my bootloader properly ( get all warnings how my phone cant be trusted).
I just need superSU to remove retail demo app but if necessary I'm willing to debug software.
Also, I have screen captures to show my issue but because I am a new user I cant share them.
Click to expand...
Click to collapse
Which file did you flash
If anyone needs help or has questions
You can join
https://t.me/joinchat/EzNJoUnSYrj_M7CnVvzNKg
I'll be more available at telegram than tapatalk/xda
Sent from my DUK-L09 using Tapatalk

fanfan7110 said:
This is a good news. We all wait for this famous twrp, so if it is almost operational it's really an excellent news.
Click to expand...
Click to collapse
Only downside for now is you can only decrypt if you have no password set. Though
Sent from my DUK-L09 using Tapatalk

LastStandingDroid said:
Only downside for now is you can only decrypt if you have no password set. Though
Click to expand...
Click to collapse
You might want to tell the builder to check the commit from TWRP for Pixel 2. February security patch causing that decryption problem when user have password set. But it has been fixed since march by DeesTroy.

Saftynet is being tripped.
I have L29

otonieru said:
You might want to tell the builder to check the commit from TWRP for Pixel 2. February security patch causing that decryption problem when user have password set. But it has been fixed since march by DeesTroy.
Click to expand...
Click to collapse
I've forwarded this thanks for the info [emoji16]
Sent from my DUK-L09 using Tapatalk

Samueldanny said:
Saftynet is being tripped.
I have L29
Click to expand...
Click to collapse
Interesting. This could be though due to demo unit possibly. Since it most likely isn't going to pass safetynet I can't tell
Sent from my DUK-L09 using Tapatalk

LastStandingDroid said:
Interesting. This could be though due to demo unit possibly. Since it most likely isn't going to pass safetynet I can't tell
Click to expand...
Click to collapse
I'm also unable to install modules.

Samueldanny said:
I'm also unable to install modules.
Click to expand...
Click to collapse
Please do join https://t.me/joinchat/EzNJoUnSYrj_M7CnVvzNKg for better assistance.
Tapatalk gives me tons of updates so can't keep track
Sent from my DUK-L09 using Tapatalk

LastStandingDroid said:
Only downside for now is you can only decrypt if you have no password set. Though
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
On a other side, it's not a big problem. It's simple to remove security password, install twrp and root, and then, put again the security with password.
That was what we had to do with the OnePlus 5T at the beginning of the first versions of TWRP.
we hope that a functional and downloadable version will be available soon
On the other hand if huawei could allow to download a ROM Stock, it would still be safer in case of bad flashing or brick phone. But can we hope that soon, not sure.

Like i wrote on p20 pro forum @LastStandingDroid you should include that here too..
After flashing the patched ramdisk they should install magisk over magisk manager again to pass safteynet and install modules.

secXces_debaki said:
Like i wrote on p20 pro forum @LastStandingDroid you should include that here too..
After flashing the patched ramdisk they should install magisk over magisk manager again to pass safteynet and install modules.
Click to expand...
Click to collapse
Oh yah didn't knew that was needed until a hour ago or two. Have had little time busy spending time with family.
Sent from my DUK-L09 using Tapatalk

Which is the Best Rom for Pixel 3 Xl

Which is the best Kernel you have used on Pixel 3 Xl

Have you looked in the ROM section? There is currently only one available.

airmaxx23 said:
Have you looked in the ROM section? There is currently only one available.
Click to expand...
Click to collapse
I messed up I wanted to say Kernel

Maty360414 said:
I messed up I wanted to say Kernel
Click to expand...
Click to collapse
Gotcha. :good:

"best" is very subjective so try some and see how they work for you.
Sent from my [device_name] using XDA-Developers Legacy app

Maty360414 said:
I messed up I wanted to say Kernel
Click to expand...
Click to collapse
That's for you to decide, it's really down to preference. What's good for one person might not be for another. This question is pretty much the same as "whats the best phone", it just depends. But, I'm using the Proton kernel v7 and I'm happy with it. Battery life and performance are good.

Mine is DU
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 3 XL using Tapatalk

Saw it dropped yesterday, and plan to flash.
Did you follow the steps in the pinned post, or modify it somewhat?
superchilpil said:
Mine is DU View attachment 4660559
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL, #WhiteUIsMustDie, #EndDarkAppOppression

micmars said:
Saw it dropped yesterday, and plan to flash.
Did you follow the steps in the pinned post, or modify it somewhat?
Sent from my Pixel 3 XL, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
I "followed" the instructions, but I just did it out of habit. I found the rom before I found their instructions and where it was actually posted.
A few days before it dropped I tried building it but kept running into build environment issues, but I did notice its targeted towards the December update so make sure you update first.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
Mine is DU View attachment 4660559
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Are you talking about Dirty Unicorn ?. Where can i find it , dont see it in the Roms section .

jawonder said:
Are you talking about Dirty Unicorn ?. Where can i find it , dont see it in the Roms section .
Click to expand...
Click to collapse
It's not on XDA, gotta search around for it.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
It's not on XDA, gotta search around for it.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
So you just factory rest and flash Rom and TWRP zip and it boot up fine and working ?.

So i flash and it keeps rebooting back to TWRP Recovery from the GU Boot Animation . Wonder if it's because i was on the December update ?. Any had success flashing from December update ?.

I'm also curious as to what makes each Kernel different. I can't really tell what each Kernel does, for example:
Freak07 said:
Graphic related features:
- KCAL to control the display
- Adreno Boost
- Enabled NAP power saving state of Adreno 630
Click to expand...
Click to collapse
This is from Kirisakura.
It sounds good, but I don't know how it would affect my phone.
Five or so Kernels are out for Pixel 3 XL. How do I know which is "best for me?"
So I ask, what do you look for in a Kernel / How should I choose a Kernel?

ZzEzZ said:
I'm also curious as to what makes each Kernel different. I can't really tell what each Kernel does, for example:
This is from Kirisakura.
It sounds good, but I don't know how it would affect my phone.
Five or so Kernels are out for Pixel 3 XL. How do I know which is "best for me?"
So I ask, what do you look for in a Kernel / How should I choose a Kernel?
Click to expand...
Click to collapse
IMHO, unless you want to mess around with clock speeds and stuff, stock kernel is just fine.
Sent from my [device_name] using XDA-Developers Legacy app

jawonder said:
So you just factory rest and flash Rom and TWRP zip and it boot up fine and working ?.
Click to expand...
Click to collapse
jawonder said:
So i flash and it keeps rebooting back to TWRP Recovery from the GU Boot Animation . Wonder if it's because i was on the December update ?. Any had success flashing from December update ?.
Click to expand...
Click to collapse
I made sure to update to the December update. Well at least the vendor, radio, and BL. The build is targeted towards the December update.
I factory reset, flashed the rom followed by twrp, booted up and set everything up then after it was done then I flashed magisk.
So what I would say is make sure everything is up to date (BL, vendor, and Radio) then make sure that your zip isn't corrupt
If all of the above is good then f reset in twrp, then wipe system. Flash the rom and twrp. Profit?
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
I made sure to update to the December update. Well at least the vendor, radio, and BL. The build is targeted towards the December update.
I factory reset, flashed the rom followed by twrp, booted up and set everything up then after it was done then I flashed magisk.
So what I would say is make sure everything is up to date (BL, vendor, and Radio) then make sure that your zip isn't corrupt
If all of the above is good then f reset in twrp, then wipe system. Flash the rom and twrp. Profit?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I was on the latest December update . I Factory Reset Flashed the Rom them flashed TWRP 3.2.3.2 zip. I rebooted and got to the DU boot Animation froze then reboot back to TWRP . What version of TWRP did you use ?. Also i downloaded the DU zip many times and checked the MD5 with different MD5 checker and the MD5 doesn’t match, i get the same MD5 with all the app that i used and it doesn’t match the one generated from the DU download area .
Also do have the December update Bootloader and Radio on both A bad B slots ?.

Yeah it has to be on both slots. Whenever you flash firmware it should to be to both slots always.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
Yeah it has to be on both slots. Whenever you flash firmware it should to be to both slots always.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Is there a command that can be used to ensure firmware is flashed to both slots ?.
Edit: Got DU working. I was flashing TWRP 3.2.2.1 zip over 3.2.3.2 image don't know if made any difference but the only thing i changed was to flash TWRP 3.2.3.2 zip after flashing DU and it booted fine

I chose DU because I didn't need to go back to a month old operating system to get it to install.
Booted to TWRP and did a factory reset. Installed DU zip and rebooted. Set up user and let it settle.
Rebooted to TWRP and installed Kirisakura kernel 1.8.5, and Magisk 18.0.
Rebooted to system and all is well.
Nice ROM, and the kernel is absolutely the best.
JMO!

Question Keeping Stock Camera App, Throwing out Google Analytics (boot.img, Magisk, Debloater?)

Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!

lai.sha said:
Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!
Click to expand...
Click to collapse
Never mind - I just found it here: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-c-65.4252373/
I'm stil open for better solutions if someone has them!

Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM

GolovaRaoul said:
Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Click to expand...
Click to collapse
Oh thank you, that is very satisfying to know. Why is that?
GolovaRaoul said:
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Click to expand...
Click to collapse
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
GolovaRaoul said:
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
Click to expand...
Click to collapse
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
GolovaRaoul said:
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM
Click to expand...
Click to collapse
Thank you for all your help!

lai.sha said:
Oh thank you, that is very satisfying to know. Why is that?
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
Thank you for all your help!
Click to expand...
Click to collapse
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also

GolovaRaoul said:
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
View attachment 5742135
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also
Click to expand...
Click to collapse
Interesting, I thought that maybe that's what you meant but I wasn't sure if it just means "compatible" with...
Thank you so much, I guess it's time to play

Question [NEW ONEPLUS USER] - Happy to be amoung you.

Hello everyone, I just bought the OnePlus 9 Pro 5G LE2123 Dual SIM 12GB+256G. Due to my inexperience, I ask for considerations in reference to a possible procedure for obtaining Root + TWRP permissions. ​I also ask if obtaining root permissions invalidate the warranty with some alleged counter (for example samsung knox counter). ​In the previous smarphone ( samsung galaxy note 9 ) I corrupted the EFS IMEI file by mistake and I don't want to repeat the same mistake. Thanks to all the Admins of the topic for your attention, as I can't help but be happy to be part of your oneplus family ​​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com

Thank you so much my friend

Congratulations on your OnePlus 9 Pro! Enjoy!!

You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​

pronegate said:
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​
Click to expand...
Click to collapse
Use the MSM tool to get back to stock.
I don't install TWRP, but boot it in temp mode for flashing etc.
SwiftBackup app for backing up apps and data, call logs and sms. Messed up data, MSM tool to factory and restore with SwiftBackup. Copy internal storage to PC for it's backup.....

Thanks friend
Other questions
In your experience, do you recommend staying on OOS 13 or immediately flashing some of the custom roms you recommend?
Before flashing the new custom rom, which partition should I wipe?
Once the new custom rom is installed, for ota updates is the same procedure with magisk to maintain root permissions?
Thank you for your time @TheGhost1951.​

pronegate said:
Thanks friend
Other questions
In your experience, do you recommend staying on OOS 13 or immediately flashing some of the custom roms you recommend?
Before flashing the new custom rom, which partition should I wipe?
Once the new custom rom is installed, for ota updates is the same procedure with magisk to maintain root permissions?
Thank you for your time @TheGhost1951.​
Click to expand...
Click to collapse
As for custom roms, it is just a matter of choice. I have seen people that are happy and seen some that have had problems. As for me I prefer stock because it is made specifically for your phone. Less chance of problems. If you install a custom ROM it is usually advisable to go into recovery and factory reset. That is the wiping that is talked about. Finally, go back and read the link I gave you on keeping root. Read it until you have a clear picture as to what you need to do...

TheGhost1951 said:
As for custom roms, it is just a matter of choice. I have seen people that are happy and seen some that have had problems. As for me I prefer stock because it is made specifically for your phone. Less chance of problems. If you install a custom ROM it is usually advisable to go into recovery and factory reset. That is the wiping that is talked about. Finally, go back and read the link I gave you on keeping root. Read it until you have a clear picture as to what you need to do...
Click to expand...
Click to collapse
Thank you for your time @TheGhost1951 ​

pronegate said:
Thank you for your time @TheGhost1951 ​
Click to expand...
Click to collapse
You are most welcome. Like I said, staying with stock roms are more trouble free. They are made for your phone. Custom roms are ok for the most part, but I have seen too many in the forums trying to run a custom ROM and having too many problems or it doesn't have everything the stock ROM has to begin with. On the OnePlus 9 Pro, there is one more little nugget I can offer the will give you full root that Magisk is short on. Once you are rooted with Magisk, send me a PM and I will clue you in on it....

Oh, by the way, you need to disable driver signing on windows PC from this link https://www.techpout.com/disable-driver-signature-enforcement/ and then search for and install latest OnePlus and Qualcomm USB drivers and install them. This way you can connect your phone to PC in ADB, Fastboot and EDL modes for maintenance tasks!

TheGhost1951 said:
You are most welcome. Like I said, staying with stock roms are more trouble free. They are made for your phone. Custom roms are ok for the most part, but I have seen too many in the forums trying to run a custom ROM and having too many problems or it doesn't have everything the stock ROM has to begin with. On the OnePlus 9 Pro, there is one more little nugget I can offer the will give you full root that Magisk is short on. Once you are rooted with Magisk, send me a PM and I will clue you in on it....
Click to expand...
Click to collapse
I INSTALLED THE DRIVERS AS GIVEN IN YOUR GUIDE
I WAIT VERY HURRY FOR THE ARRIVAL OF MY ONEPLUS 9 PRO. I WILL UPDATE YOU AS SOON AS I HAVE NEWS

I would recommend first testing Oxygen OS software, I thinks it is not necessary for most users to tinker with custom roms.
In some time you will discover if your needs are covered with official soft or not, I know Oxygen Os is not what it used to be, it is nor good nor bad, it just was so much better before merging with Oppo because it had its own dev team and they actually did care about users, now they pretend to but ignore important matters, just answer silly questions in their forums but always abstract and tasteless...
You can always root your phone and stay in Oxygen Os but with benefits of magisk, you can tinker with it staying in Oxygen OS, but beware, you need to dome some certain things in order to "trick" some sensitive apps to root, like banking, when it detects your phone is rooted some functions may not work for "safety reasons", read magisk tutorial and enable saferynet, magisk hide deny list and you will be good to go, pretty easy for certainly experienced user, if not feel free to ask, we all will be happy to help!

pronegate said:
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​
Click to expand...
Click to collapse
When you have your phone in edl and recognized by the msm tool, you can press F8 and choose partitions to back up. Take a backup of modemst1/2, efs/persist and while you're in there, grab boot_a so you can inject magisk into that boot image for root.
After you select the partitions you want, press read back and they will be saved to C:\ - with the partitions backed up, even if you do manage to break something the msm tool can't fix, you'll have the originals to put back in place.
The password is oneplus, one word all lowercase.
I don't use twrp anymore but that's your choice. I also stay on oos11. Some stay on 11, some go to 13, some go custom rom. It just depends on what you want and need from your phone. For now, we have the last OnePlus phone with real custom rom support as the newer OnePlus phones don't have public msm tools for flashing or recovering from brick state