Database Users

OXYGEN OS(Download link ,installation guide & Issues)

Download OxygenOS http://oxygenos.oneplus.net/oxygenos_1.0.0.zip
DO UNZIP your ZIP before flashing!!! installation ZIP is in ZIP file provided
Plain Aosp Rom
Download Feedback App https://s3.amazonaws.com/oxygenos.oneplus.net/Feedback_v1.0.2.apk
Note: You’ll need to enable installations from unknown sources (settings > security) in order to install the feedback app on OxygenOS.
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
List of known issues:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes

manishsharma17 said:
Download OxygenOS http://oxygenos.oneplus.net/oxygenos_1.0.0.zip
Download Feedback App https://s3.amazonaws.com/oxygenos.oneplus.net/Feedback_v1.0.2.apk
Note: You’ll need to enable installations from unknown sources (settings > security) in order to install the feedback app on OxygenOS.
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
List of known issues:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
Click to expand...
Click to collapse
OMG!!! Is this a Dream???? Is this real?

CM version?

manish.kumar86 said:
CM version?
Click to expand...
Click to collapse
its not based on Cm its based on AOSP its 5.0.2

Yash Kanchhal said:
So when we are factory resetting the phone in recovery is it the same thing like wiping the other thing (cache, dalvik cache etc). I'm new in this so I'm not able to understand that please help me in this & when is the CM12S coming anyone knows?????
Sent from my A0001
Click to expand...
Click to collapse
TWRP has an option for factory reset ...

There's already a thread for this here:
http://forum.xda-developers.com/showthread.php?t=3072259
Transmitted via Bacon

Yash Kanchhal said:
Ohk thnx mate it means wiping is every thing????? Right ????
Sent from my A0001
Click to expand...
Click to collapse
yes sir ..use the option of factory reset in twrp and you should be good

timmaaa said:
There's already a thread for this here:
http://forum.xda-developers.com/showthread.php?t=3072259
Transmitted via Bacon
Click to expand...
Click to collapse
When i created the thread the thread was not there in present form

manishsharma17 said:
When i created the thread the thread was not there in present form
Click to expand...
Click to collapse
Unfortunately it looks like he created his first.
Transmitted via Bacon

Nice spam indeed. Three threads, three posts, three times begging for thanks. Bah.

Can you add my guide thread to the OP please?
http://forum.xda-developers.com/oneplus-one/general/guide-how-to-install-oxygenos-t3072500

Word of caution! I backuped on the internal sd. Had all my backups of os's and app data completely wiped. Never checked the wipe internal sd box. Use and external backup.

Is anyone with SuperSU 2.46 having issues with WIFI not turning on and also having screen artifacts that force to do a hard reboot?

cyberon said:
Is anyone with SuperSU 2.46 having issues with WIFI not turning on and also having screen artifacts that force to do a hard reboot?
Click to expand...
Click to collapse
Getting neither of those. Main problem I'm having is major Google Play Services drain. It's the same bug we had on CM12 nightlies some time ago and my phone is permanently awake
Sent from my A0001 using Tapatalk

Hello, due to having a similar topic here http://forum.xda-developers.com/oneplus-one/general/oxygen-os-released-download-t3072259, I will have to close this thread.
Please continue the discussion in the one linked.
Regards

Boot loop even after stock recovery! My bacon is cooked!

Okay boys Just got this phone like a week ago. Used it to replace my Samsung that was acting up. Convinced my wife I needed it and then proceeded to toy with it.
I unlocked the bootloader, flashed custom recovery (TWRP latest), and rooted (Magisk latest) to stick recovery. I was running full stock 8.1.0 no custom ROM yet I was doing reading before I wan
ted to flash. Got to feeling comfortable so I got everything ready files downloaded USB hooked up and decided to be safe and make one more back up.
So thats what I did, I made a full TWRP backup, every single partition onto an external USB. So I am safe, right? Best to be safe... But that's when I rebooted from TWRP it boot looped.
So now I am currently stuck at boot. I get the warning screen about the unlocked bootloader then "Google" logo boot screen then a black screen and back to the start again. I knew that wasn't right, so I booted into fastboot with Power + Volume Down, cycled to recovery and selected it then... boot loop. No recovery. Hmmm... That's not good. But keep calm... did some research and found a few things. So i did this...
Heisenberg said:
FAQ can be found in post #3!
[SIZE=+1]10. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all operations are complete you can reboot the device.
Click to expand...
Click to collapse
and that didnt work either so next I tried this
Train88 said:
Like other curious 6P users, I flashed the "full ota" zip to check out Nougat. Then I tried to restore my nandroid for Dirty Unicorns, and apparently TWRP 3.0.2-1 had a fatal flaw that borked the EFS backup. I tried literally everything I could think of, until I saw the process @be_vigilant did to revive his phone. I'm going to be using his process as the base for the guide, as well as linking you to my nandroid that has now helped two other people revive their device.
What you need:
*MMB29P factory image (although MTC20F also worked for someone).
Direct download link: https://dl.google.com/dl/android/aosp/angler-mmb29m-factory-616cf265.zip
*My nandroid backup (its stock MMB29P, decrypted and rooted)
https://www.androidfilehost.com/?fid=24686679545612465
*TWRP recovery image (3.0.2-0 or one of the newer builds that fixed the EFS stuff)
https://dl.twrp.me/angler/
*Android SDK or at least platform-tools (for fastboot, adb, etc)
The Process:
1. Extract the factory image into the location where you have fastboot.exe (mine is C:\Android\sdk\platform-tools)
2. Extract the nandroid backup - doesn't matter where, I'll explain later
3. Make sure you are in bootloader mode, and run flash-all.bat from the factory image
4. Flash TWRP (fastboot flash recovery twrprecovery.img)
5. Boot into TWRP, and make a new nandroid backup. This step is just to create the TWRP backup folder on your device
6. Now go to wipe, advanced wipe, click on each partition one at a time, choose "Repair or Change File System", then select "Repair File System" - do this for dalvik/art, system, data, internal storage, and cache. It may not work for all of them, but its ok.
***you must mount data again in TWRP after doing this, or you will not be able to see anything***
7. Copy & paste my nandroid onto your device in the correct location (sdcard/TWRP/BACKUPS/XXXXXX)
8. Restore my nandroid and try to boot.
9. If it still does not boot at this point, then you need to run these adb commands (while in TWRP) that @bogomil4e kindly reported to wipe the EFS partitions
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384 -and-
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Now you should be able to boot up and do anything you want again. Please do not mirror my nandroid or take advantage of it - I am making it available only for people to utilize as a way to unbrick their phone!
Click to expand...
Click to collapse
And that didn't work either. To be clear I left my bootloader unlocked. Each process works as far as flashing all the files via fastboot. But if I try to reboot or boot recovery, stock or custom, I boot loop. I have been looking everywhere and I dont see a solution and was hoping to get some help.
edit: Now I have also tried this... Doesnt seem to be the bootloop of death.
XCnathan32 said:
Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)​
*Update 8/22: Android O is working with 4 Cores now! Big thank you to @xls654 for finding out how to get Android O to work.
*Petition:
I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)
*Changelog:
8/25 - EX kernel for Android O added.
8/22 - Android O DPR6 boot.img and source added.
8/16 - Started making this fix open-source, source code section added in OP. Also uploaded modified Franco and Flash kernel & source.
8/10 - Added PA 7.2.2 and DarkROM boot images.
8/08, 2nd change - Uploaded modified boot.img for firmware 48C.
8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
8/07 - Added boot.img that only uses 1 core. Someone suggested I make a boot.img that only uses 1 core, just to see if it works for devices that didn't work with the 4 Core fix.
7/30 - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
7/29, 2nd change - Added Pure Nexus and PA dev version boot images, modified to use 4 cores, and utilize all 4.
7/29 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP.
7/21 - Fix created, stock boot.img, TWRP image, and EX kernel modified to use 4 cores.
*What this fix does, and how to apply it:
The problem:
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.
The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.
Requirements: For this fix to work, you need:
A brain
A computer
A bootlooping 6P with an unlocked bootloader/OEM unlocking enabled
The modified files of your choice
Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.
How to apply the fix:
Boot your phone into bootloader (hold power and volume down).
Connect your phone to the computer.
Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
Edit: With the new EX zip, you shouldn't need to flash the boot.img anymore, you can just flash twrp, and then flash EX in twrp.
Boot up your phone, and hopefully it should work!
*If your phone is bootloader locked/OEM locked:
You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.
To enable OEM unlocking and unlock bootloader:
Go to settings.
Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
Once you're in developer options, click on "OEM unlocking" and accept the prompt.
Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.
*Downloads:
Boot.img from stock 6.17, 8.0 firmware: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. It also disables forced encryption as a bonus. Thank you to @xls654 for figuring out how to get Android O to work.
Boot.img from stock 48C, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
Boot.img from stock 48B, 7.1.2 firmware: Download |Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
EX kernel version 5.03: Download | Mirror. EX kernel 5.03 works with android 8.0.0. This zip applies the 4 cores patch, but you will need to flash it over an already modified boot.img to work.
Elemental X kernel version 4.12, universal zip: Download | Mirror. This zip is EX kernel, modified to use only 4 cores. Update: I modified it to apply the CPU utilization patch too, so now this is a universal zip, flash it over almost any ROM, and you should now have the BIG cores disabled fix, and the little core utilization fix.
Flash kernel version 2.5: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
Franco kernel r55: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
You will most likely not need these images. It will be much easier, and much more universal to flash one of the custom kernel zips above ^^^
PA boot.img from PA version 7.2.2, build 8/10: Download | Mirror. Uses only 4 cores, and has core utilization patch.
PA boot.img from PA version 7.2.1: Download | Mirror. Boot.img from PA dev preview 7.2.1, uses only 4 cores, and is modified to utilize 4 cores more effectively. Flash it after you flash the PA zip, either with fastboot, or TWRP image flash.
Pure Nexus boot.img from Pure Nexus 7/25 build Download | Mirror. This image is modified to use only 4 cores, and it has a tweak to utilize the 4 cores more effectively. Flash it after you flash Pure Nexus, either with fastboot, or TWRP image flash.
DarkROM boot.img from 7/21 build: Download | Mirror. This image is modified to use only 4 cores, and has the utilization patch.
Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Edit: seems not to help unfortunately. Here it is: Download | Mirror
Unfortunately, I have not been able to get Android O working yet, but I am working on it right now.
If you have a favorite custom ROM or kernel you want to ported over to use 4 cores, let me know, and I'll put it up.
*Source code:
Flash kernel: source | Flash ramdisk/AK2: source.
Franco kernel: source | Franco ramdisk/AK2: source.
Android O boot.img: source.
p-0000000000000000000000000000007 (sorry that was my kitten)
*Tested custom ROMS/kernels
I have used Pure Nexus by flashing the modified EX zip over it, it has notably better performance than the stock ROM, and very good battery life. It's a clean, stable ROM, with plenty of good features that are actually useful.
I have also used Paranoid android dev preview, very good performance, definitely my favorite as of now. Battery life leaves something to be desired, but I have not tried a custom kernel yet. Also, 7.2.1 seemed smoother to me than 7.2.2.
If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.
*To improve performance slightly:
Flash a custom kernel. I will upload more kernels as I test more, so stay tuned.
Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
Turn resolution down to 1080p. On a small screen, the difference in between 1080p and 1440p is not very noticable. To do this, first get root access, then download a terminal emulator. In the terminal, type "su" and grant it root access, then type "wm size 1080x1920", and finally, change the density "wm density 400". Personally, I like my density at 400, but you can expieriment with it. Lower density=Smaller items and text, Higher density=Bigger items and text. Also @Adithya FRK mentioned that you also want to put density in build.prop so apps display correctly. Change ro.sf.lcd_density=560 to your density, if you changed it.
*Credits:
@rchtk, His post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
@tr1gg3r.man, He made the the PA kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
@BeansTown106, He made the Pure Nexus kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
@Dark_Eyes_, He made the DarkROM kernel, I just added a couple modifications to it. In no way am I trying to steal and/or discredit his work.
@[U][COLOR="Purple"]The Flash[/COLOR][/U], He made The Flash kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work. His posts have also helped me a lot with learning how to build a kernel from source, understanding how to use git more, etc. I recommend you check them out if you are interested in getting started with android development.
@[B]franciscofranco[/B], He made Franco kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work.
@xls654, He found out how to get Android O working with 4 cores.
FAQs
What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are your device may have a different problem.
Does EX kernel have the new speed fix? - Yep, you can flash this over just about any ROM, and it should patch it to use only 4 cores, and use them well.
I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.
I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated Donate to me here!
If this guide helped you, please click thanks, it means a lot to me
Click to expand...
Click to collapse
Please anybody if your willing to take a swing at helping me I would really appreciate it!
Thanks in advance!

Anybody have any insight?

Were you successful at returning to stock?
If not, I'm afraid you're suffering from the bootloop issue :'(

No i was not, but the standard 4 core fix isn't working for me either so I don't know what else to do.

I did something similar. Tried to update to latest may patch from custom rom. No sim found...so tried some radios..nothing. Thought I better get back to full stock. Similar to you tried the individual flashes and then the OTA as a whole. During that process I locked the bootloader. Now I get the yellow screen text says software isn't standard...then google logo...then the red text says os is corupt possibly...then google logo, forever. No loops it seems but just doesn't boot.
Anyone with thoughts?

i am on my 2nd 6p with the same problem after installing twrp. the first one i got operational by sideloading via twrp a factory img. to get the sideload to work i had to go back to android 6, 7 and 8 would not work. right now the google firmware site is not working, it has been out for a few days, so i have not been able to try it on the second 6p.
edit; now that i recall the factory img would not load after installing. i then went back to fastboot recovery and got the distress robot, twrp was of course gone. from there i did a factory reset which got me back to go and the long climb back to oreo.

[TOOL][HOW-TO] [Nexus 5X] Bootloop of Death (BLOD) Workaround [Flashable Zip]

Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 5X
osm0sis said:
Guys.. bad news.. my Nexus 5X just got hit with the BLOD.
Good news for everyone is I spent a bit of time tonight to first patch TWRP 3.2.1-0-FBE (File-Based Encryption support) image to be 4core, then made an AnyKernel2 zip which will patch the existing boot and recovery partitions on-device to add all the 4core fixes from @XCnathan32.
Should work over any ROM, any custom kernel, recovery, etc., can be added in queue after ROM, root zip + custom kernel to patch it from TWRP or FlashFire (so good for OTAs), and simplifies the initial process greatly since you can now fastboot boot any 4core recovery.img and then adb sideload my AK3 zip to fix the likely newer recovery you already had on your device.
Click to expand...
Click to collapse
Original thread posts: Nexus 5X, Nexus 6P
Now updated to an AnyKernel3 zip to support the SAR (system-as-root) and 2SI (2 stage init) ROMs that have popped up for Pie and Android 10+!
General Information
If you've found this thread then I'm sure you probably already know what the Bootloop of Death is - separation of the performance (perf) CPU cores - and that the only way to recover from it is to unlock your bootloader and patch to disable the faulty cluster. If you have not enabled unlocking your bootloader yet, the known methods to get it to boot long enough so you can go to System, then Developer Options and toggle "OEM unlocking" are:
super cooling the device in a freezer in a ziplock bag to keep out moisture,
super heating around the camera, and
letting the battery run all the way down before trying to boot.
For further details on these methods check out the original threads by @XCnathan32, linked in the "Thanks" section.
Some important notes before going any further:
Freezing at the Google logo likely points to it being perf cluster separation, but this could also be caused by other components separating.
Freezing at the boot animation suggests ROM/ROM data problem or could also potentially be a BLOD with other components now beginning to separate and that's what people have reported when the 4core mods suddenly stop working with no configuration changes - if you've tried the default boot.img for your ROM, patched with the BLOD AK3 and it still doesn't work, sorry but your device is a brick.
If no 4core recovery boots for you then you definitely have more components than just the performance cores separated, sorry but your device is a brick.
I haven't seen anyone say their devices only worked using a "1core" modification who had tried a proper 4core patched setup; 4core makes sense because it's the separate perf cores cluster becoming unsoldered, but if the 4 low power cores cluster also starts to come unsoldered logically not even a single core would work.. I think that's where the "Green Screen Of Death" comes into it.
DemiGod = Green Screen Of Death; unfortunately this (more components separating given more time - maybe the flash memory chip?) is why many call the 4core workaround only temporary.. there's not much that can be done after that from what I've read.
EX Kernel does not support FBE on these devices because the EX zip patches the fstab forcefdeorfbe flag to encryptable.
Android 10 does not appear to support FBE on these devices but the 4core FBE TWRP build can be used to BLOD patch the latest TWRP (see instructions in next post).
On Oreo, I was personally on stock ROM still, FBE enabled, rooted with SuperSU v2.82 SR5 + suhide and the latest Franco Kernel on my 5X. Then I bumped up the min freq on the low perf cores and it's working great - totally fine for general use, just anything creating a bit of heat like games maxing the low power cores for awhile, or charging, will make it pretty painfully laggy and risk further solder deterioration.
Even though SuperSU development is ostensibly dead, I still strongly recommend it on BLOD-affected devices using stock ROM for reasons I'll explain below.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Step-By-Step Installation Instructions
Any quoted commands should be entered without quotes
1) Download and unzip platform-tools for your PC from https://developer.android.com/studio/releases/platform-tools.html
2) Navigate to https://androidfilehost.com/?w=files&flid=312881 (also mirrored below) and download N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip to your platform-tools folder as well as
2a) twrp-3.2.1-0-fbe-4core-bullhead.img (Nexus 5X), or​2b) twrp-3.2.1-0-fbe-4core-angler.img (Nexus 6P)​3) Hold Shift + right-click on your platform-tools folder and
3a) Open a command window here (Windows <10), or​3b) Open a PowerShell window here, then enter "cmd" at the Windows PowerShell prompt (Windows 10+)​4) Reboot your phone to bootloader and connect it to your PC with a USB cable
5) Enter "fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img" into the cmd prompt
6) Reboot your phone to recovery and tap Advanced, then ADB Sideload
7) Enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip" into the cmd prompt
8) Reboot and cross your fingers that it works
For information how to seamlessly update to stock and custom ROM OTAs, see the following post
Source Code: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
Status: No Longer Updated
Thanks:
- @XCnathan32 for researching and developing the 4core workarounds for both the Nexus 5X and Nexus 6P
- chetgurevitch (GitHub) for the original FBE supporting TWRP builds
- @Aukaminator for the original step-by-step write-up

Update Flashing Instructions
Keep N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip on your device sdcard, henceforth referred to as BLOD AK3 zip
The correct manual order for a clean flash is: ROM -> root -> custom kernel -> BLOD AK3
Always flash the BLOD AK3 zip last!
Reflashing the BLOD AK3 zip will likely be required after anything that could modify the boot.img or recovery.img, including (but not limited to): ROM updates, custom kernel updates, custom recovery updates.
ROMs:
On custom ROMs with built-in Flash After Update (i.e. OmniROM-based), place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/OpenDelta/FlashAfterUpdate/ ensuring the BLOD AK3 is last in the directory listing so that they will be flashed after each update.
On custom ROMs that do not have built-in Flash After Update (i.e. LineageOS-based), you may add my FlashAfterUpdate addon.d script to /system/addon.d/ and then place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/FlashAfterUpdate/ ensuring the BLOD AK3 is last for the same effect: flashed after every OTA.
On stock ROM rooted with SuperSU (SuperSU v2.82-SR5 recommended) instead of tapping "Reboot & Install" once the OTA is downloaded you should use @Chainfire's excellent FlashFire app to queue the OTA from /data/ota_package/update_s.zip then queue the SuperSU zip, custom kernel and BLOD AK3 zip, ensuring the BLOD AK3 is last. This is how I have mine set up, since this is by far the most seamless. Be sure to disable EverRoot since SuperSU v2.82-SR5 is newer than the SuperSU included in FlashFire.
On stock ROM rooted with Magisk you must uninstall Magisk from within Magisk Manager to restore your stock boot.img, reboot the ROM to restore your stock recovery partition, tap "Reboot & Install" once the OTA is downloaded, then go through the steps above to flash the 4core TWRP and BLOD AK3 zip again. I definitely recommend SuperSU on this device to avoid the hassle of unrooting and/or messing with factory images.
Kernels:
Custom kernels can be flashed from an app like Franco Kernel Manager & Updater, which can be set to flash without reboot for Franco Kernel updates, or "Flash only" can be chosen in the manual flasher. The FK app supports all types of AnyKernel3 zip so the BLOD AK3 zip may then be flashed after the custom kernel zip to repatch the new kernel's ramdisk.
For other kernel managers that don't support AK3 zips, simply reboot to recovery and flash the BLOD AK3 zip from there to repatch before attempting to boot the ROM again. Also see above under "stock ROM rooted with SuperSU", since FlashFire also works perfectly for this use-case, queuing the custom kernel zip and then the BLOD AK3 zip, with FlashFire's EverRoot option disabled since the device is already rooted.
Recoveries:
Download the updated custom recovery .img and, without flashing it, reboot to recovery, use TWRP's flash image feature to flash the new recovery.img, then without rebooting immediately flash the BLOD AK3 zip to patch it. You can then dump/backup the recovery partition if you want it as a recovery.img. Custom recovery updates can also be done from FlashFire, queuing the BLOD AK3 zip afterward, but the "Preserve recovery" feature must be disabled.
If you prefer to stay on stock recovery for some reason, you can still use TWRP to do the above without flashing TWRP to the device by using "fastboot boot twrp-3.2.1-0-fbe-4core-bullhead.img".
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Changelog
2018-01-15 - Original post in other BLOD threads.
2018-07-21 - Update AK2 Core+Backend files to latest, add searching of all init.*.rc files for problematic cpuset commands which were popularized by Franco Kernel and are now used by multiple custom kernels. (6734 downloads)
2019-10-30 - Update to AnyKernel3, add support for SAR and 2SI Treblized ROMs. (886 downloads)
2020-01-16 - Update AK3 Core+Backend files to latest to fix AVBv1 signing in recovery on Android 10, update boot_signer-dexed.jar. (428 downloads)
2020-02-17 - Update AK3 Core+Backend files to latest to fix SAR mount support in fragmented TWRP and Lineage 16+17 Recovery. (1188 downloads)
2020-05-25 - Update AK3 Core+Backend files to latest to improve SAR mount support in Lineage 17 Recovery and AVBv1 signing. (1276 downloads)
2021-07-21 - Update AK3 Core+Backend files to latest to support Lineage 18.1 recovery and Android 11 ROMs.
Good luck and enjoy!

Thanks a lot for your hard work Sir ..!
Sent from my Redmi Note 5 using XDA-Developers Legacy app

hey,
my nexus 5x unfortunately started having the bootloop issue yesterday.
i tried fixing it using your instructions, now it's stuck in the colored boot animation. it's not frozen, but just stays in the animation forever (i waited already more than 1.5 hrs).
do you have any suggestions what i could try?
thanks in advance!

en_jo said:
hey,
my nexus 5x unfortunately started having the bootloop issue yesterday.
i tried fixing it using your instructions, now it's stuck in the colored boot animation. it's not frozen, but just stays in the animation forever (i waited already more than 1.5 hrs).
do you have any suggestions what i could try?
thanks in advance!
Click to expand...
Click to collapse
Does the 4core recovery work? If so, try flashing the lastest factory image, then the BLOD AK2 zip again and see if that helps. If not, you're out of luck.

Hey! Thanks for your instructions, im unbold my nexus 5x! But now my wifi doesn't work. Can it be problem with your img? Bluetooth works by the way.

Jatsu said:
Hey! Thanks for your instructions, im unbold my nexus 5x! But now my wifi doesn't work. Can it be problem with your img? Bluetooth works by the way.
Click to expand...
Click to collapse
I don't have an img, I patch whatever's there. What ROM are you using?
Dirty flash your ROM, rename the BLOD AK2 zip to test-debugging.zip, flash and upload the debug.tgz it creates and I'll take a look.

Hey! Thanks for your instructions.
In my the error appears:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Do you have a solution?

ediofelipe said:
Hey! Thanks for your instructions.
In my the error appears:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Do you have a solution?
Click to expand...
Click to collapse
Are you booted into 4core TWRP? Did you go to the Advanced | ADB Sideload page and swipe to start the sideload mode? Make sure your PC has adb sideload drivers installed? Try a different USB cable? Try adb pushing the file to your device and flashing it from there instead?
Side note to all: BasketBuild is having some down time so I've mirrored the uploads in the OP. :good:
Edit: And BasketBuild is back!

Thanks
So, first of all i would like to tell u that, I thank u a lot for your amazing work, i finally got my nexus 5x out of bootloop after a year
Got to say i thought i would never get it back from there. Also i would like to get some advice:
Currently im running 7.1.2, i wanna download the OTA for oreo, my question is:
As i dont have it rooted, what i should do is download and install it. then make this:
"Reboot your phone to bootloader and connect it to your PC with a USB cable
5) Enter "fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img" into the cmd prompt
6) Reboot your phone to recovery and tap Advanced, then ADB Sideload
7) Enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip" into the cmd prompt"
Or what do u suggest??
Also it would be better if i get root and then get the OTA? in that case, if i root it should i flash again your patch? or is not necesary.
So Thanks again, for all your work.

FYI the TWRP does matter. I already had TWRP 3.2.1 so I didn't flash the suggested one and it didn't work. Flashing the suggested TWRP worked.

I can't seem to boot into recovery or normally boot(black screen but fastboot mode works fine), with or without the 4core fix (recovery + boot img). Also, to enter fastboot I have to hold power down and volume for a minute or so. Does this mean I'm out of luck?

With stock kernel it doesn't work right? Only custom kernel?
I'm trying to resurrect an old 5X. So i Should:
- fash latest factory image on fastboot
- flash suggested twrp on fastboot
- flash custom kernel, like Franco
- adb sideload in recovery the fix
- reboot and hope ?
Thanks
EDIT: I'm stuck at Google logo, when I reboot to suggested recovery above. It's stuck at Google logo and rebooting also when it is switched off and I plug the wall-charger. Only bootloader mode works! What to do?
EDIT 2: at the end everything works now and boots! Let's see if it stays like this!

Everything worked for couple hours without issues, then it bootloop again. The strange thing is that it doesn't power on anymore after some reboot, tried everything, long press for 10 seconds, 30 seconds, either power only and power + volume buttons.. It switch on only if I disconnect and reconnect the battery by opening the device,it starts but bootloops and then again no sign of life after some bootloops. I remember it happened the same when it died the first time almost 1 year ago I believe. Not even the bootloader come up when it is in this strange state, unless I disconnect the battery.
With the fix I thought it would keep staying alive.. But no luck seems

ok, perfect, everything work....but if I check cpu I see 4 CPU* 1.44GHZ + 2CPU stopped, instead 4 CPU* 1.82GHZ + 2CPU*1.44GHz. Why Did u change frequency of 4 cpu, lowering them?

fricco1983 said:
ok, perfect, everything work....but if I check cpu I see 4 CPU* 1.44GHZ + 2CPU stopped, instead 4 CPU* 1.82GHZ + 2CPU*1.44GHz. Why Did u change frequency of 4 cpu, lowering them?
Click to expand...
Click to collapse
I didn't and it doesn't.
Oh and as a general FYI to everyone, if I don't respond to your question/post it's because it's already answered in the OPs.

Thank you very much for your work. My phone went into a bootloop today and flashing stock rom didn't work. Your guide was well-written, easy to follow and most importantly worked like a charm!

Hi when i make the 7th point of guide my PC open the zip file.
Which is my error?
Inviato dal mio iPhone utilizzando Tapatalk

It's alive!
Thanks, man. It worked great and was really easy. I will happily make a donation!
Initially my 5X was booting to the Google logo and then rebooting, forever.
I am hoping this will last me until the end of the year when I will get a OP6T or Pixel 3 maybe.
Is there any advice for maintaining the device in this state? For example doing a factory reset, flashing a custom ROM?

Gazza2907 said:
Thanks, man. It worked great and was really easy. I will happily make a donation!
Initially my 5X was booting to the Google logo and then rebooting, forever.
I am hoping this will last me until the end of the year when I will get a OP6T or Pixel 3 maybe.
Is there any advice for maintaining the device in this state? For example doing a factory reset, flashing a custom ROM?
Click to expand...
Click to collapse
Hi! Use some kernel manager to make sure your N5X doesn't turn big cores on, and keep it as cool as possible. Good luck!

GAPP error 70 HELP

I was messing around and deleted google play store, now none of the google apps works. I went a head to download gapps and tried sideloading it. It showed me the error, then i downloaded the pico version and also fix my system partition. It says i have 140mb of free space in that partition. I tried sideloading pico again and still the same error.

Yurodd said:
I was messing around and deleted google play store, now none of the google apps works. I went a head to download gapps and tried sideloading it. It showed me the error, then i downloaded the pico version and also fix my system partition. It says i have 140mb of free space in that partition. I tried sideloading pico again and still the same error.
Click to expand...
Click to collapse
You're probably going to have to flash your phone back to stock to re-gain all of your apps.

Zachisimo said:
You're probably going to have to flash your phone back to stock to re-gain all of your apps.
Click to expand...
Click to collapse
So flash the rom again? is that going to wipe my phone?

Dark Nightmare said:
This is a basic write up to convert your bootloader unlocked T-Moilbe OnePlus 6T to the International Version firmware via fastboot flashable firmware files.
Contents:
-Disclaimer
- Full Device Backup - Precautionary - Optional, but Recommended.
-Firmware Versions and Flashing Instructions
-Rom Sources
-MSMDownloadTool
-FAQ's
-Additional/Optional Tools
-Credits
Disclaimer:
Like any other form of modding, there are risk involved, we have a near flawless option to recovery by use of the MSMDownload linked at the end of this post, but like with any form of modification, you are solely responsible for what is done to your device and you accept all risk involved, should something go wrong, for the most part, recovery is fairly simply, no matter how bad we screw up, thanks to OP.
Instructions to a full device backup:
1. Download the zip below and extract it to it's own folder
2. run cmd.exe while in fastboot mode and run the following commands:
3. Once twrp boots, run the backup.bat script included, it will backup all partitions on your device, including your efs.
4. zip all of the image files and store it somewhere safe.
Backup: https://androidfilehost.com/?fid=11410963190603855581
For Users Looking to Flash to Firmware versions 9.0.4-9.0.5
FLASHING STEPS
Requirements:
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file.
3. PC/MAC/LINUX
Flashing Process
1.. Whichever full rom zip you choose, extract its contents. (In my case I used the 9.0.5 full zip)
2. In each zip file you'll find images.zip as well as others_flashall.zip, extract both of them into the same folder/directory as the rest of the original zip file.
(Optional, download the modded flash-all-partitions-fastboot.bat file at the end of the thread, it includes the reboot command to auto reboot when done flashing)
Attached Below is also a flash-all-partitions-fastboot.sh script for Mac OS users (Note this script will not wipe your device, so if you need to wipe, run the ./fastboot -w command in fastboot manually)
All bat files, images and adb files should all be in the exact same folder, no subfolder(s)
3. Now boot into fastboot using either the vol+/vol- and power key combo or via adb using the following adb command .
4. Once in fastboot run the bat file called flash-all-partitions-fastboot.bat
9
5. When asked, I would advise typing 'Y' for yes to format the device. (wipe only if you're converting for the first time)
The sparse header error is completely normal.
6. Upon completion, the script should pause and say press enter to continue, it will not reboot your device...
WAIT UNTIL NOTHING ELSE IS HAPPENING AND ITS NO LONGER FLASHING ANY FILES
At this point, hit power and reboot.
All done!
Firmware Version 9.0.6
Requirements
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file.
3. PC/MAC/LINUX
Steps to Flash
Note: Modded fastboot flashing script attached at the end with the reboot command included, also attached is a script for MAC users, mac script will not wipe your device, wipe manually if you need to using
ROM Sources
Mauronofrio's Thread
T-Mobile 9.0 FULL Fastboot ROM
Saythis' International Firmware 9.0.6
Recovery - MSMDownloadTool
If for some WEIRD reason you brick, have a HW mismatch, etc, or you just can't boot go to this thread -> MSMDownloadTool - T-Mobile 9.0
OPTIONAL Steps
Root is available via two Options below:
- OnePlus Rooter
- Manual Root Using a Patched Boot Image
Automated Process
Luckily There are devs looking to make things simpler:
More an automated tool to carry out this process, go to the thread below:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-oxygen-os-9-0-6-fastboot-windows-t3870170
WARNINGS!
-Advisable you disable automatic updates in developer options upon boot if it is enabled.
-Do not attempt to update using the OTA files, so far we've had one softbrick due to it and said user was unable to boot into fastboot to attempt any kind of recovery.
-ALSO DO NOT FLASH WITHOUT THE FILES IN THE FOLDER, IF YOU DO YOU WILL END UP WITH A SOFTBRICK
-If you get either dump mode or fastboot bootloop check your downloaded rom file to make sure its complete, unzip again and flash again
FAQ
Q. Will this enable dual sim functionality?
A. Dual sim functionality works, volte, Wifi calling and vvm.
Q. Can I take OTA's like a regular device?
A. No, sadly.
Q. What about when a new update comes out?
A. Once a fastboot flashable ROM is made, you can update using the steps above, using the new ROM files.
Q. What if I brick or have a HW/SW mismatch?
A. Use the MSMDownloadTool to recover.
Q. Do all the features work?
A. For the most part, there are minor bugs, but they aren't consistent, so can't really say.
Q. Is this a full conversion?
A. Somewhat.
Q. Do I have to wipe everytime I update?
A. No, wiping may only be necessary for conversions, no wipe needed to update.
Q. Do I have to root everytime I update?
A. Yup, sadly.
Q. Do I have to convert to a specific version?
A. Nope, you can convert to any version.
if any edits are suggested, I'll include them.
Credits:
@mackentosh for testing and unfortunately bricking using the OTA File
@Velrix for being the second successful tester, among others.
All the other users who've been testing/contributing to testing
I'll add names when I get to comb through the threads.
@Dameon87 for the correct ROM source link of the unpacked ROM with batch files.
@Krunk_Kracker for the disable auto updates image
Thanks to @Addiso for the Stock T-Mobile Backup images
@mauronofrio for the scripts and for hosting the Rom zip @hartleyshc for testing and confirming full dual sim functionality.
@Saythis - for the 9.0.6 FULL ROM Zip
Click to expand...
Click to collapse
I would follow this guide. Than choose Y when asked to wipe data. If you want to choose N let me know how it goes. But the easiest way is going to be to start from fresh using this guide by @Darknightmare.

Stubborn Pixel 2 XL doesn't wan't to have Magisk anymore

Dear Android Community,
I have a small problem during the process of rooting my phone - Google Pixel 2 XL.
Before I will explain what I have already tried, I would like to notice that in the past I already rooted exactly this phone. But then, after a while, I started to have some screen issues, I thought it can be some firmware issue, so i wiped my phone completely through cmd (flash-all.bat). A moment after I've realized, that the screen issue was the hardware issue.
Afterwards every time I try to root my phone, i follow this loop:
fastboot boot twrp 3.2.3-1,
adb push twrp.rar & install
*phone works normally*
From there on I have usually two further loops:
a)
adb reboot bootloader,
adb push magisk (various versions)
install magisk.rar (success)
Android can't load - stuck in loading screen
adb reboot bootloader
flash-all.bat
b1)
download & install Magisk manager
download magisk.rar from manager
adb reboot recovery
install magisk.rar (success)
phone can't load
adb reboot bootloader
flash-all.bat
b2)
download & install Magisk Manager
copy & paste the boot.img,
patch boot.img in Magisk Manager
copy it back on my computer
adb reboot bootloader
fastboot flash boot patched_boot.img
phone can't load
adb reboot bootloader
flash-all.bat
I did that both with and sometimes without allow debugging through USB option (from dev options). No difference.
Anyway, at the end, I have to install android system from over and over again, without any success. Google can't help, DuckDuckGo can't help, I hope you guys can help. As I have mentioned, this phone was rooted once, so it has to be possible!
Thanks in advance for any help
Regards

Where are you getting the rar files? I've only ever used zip files.

jd1639 said:
Where are you getting the rar files? I've only ever used zip files.
Click to expand...
Click to collapse
Sorry, my mistake. Of course I meant zip files.

One thing I would not do is push the zip or TWRP image to the device. Instead, in Android I would download the zip or image from twrp.me using Chrome, which will store it in the downloads folder. I then download the Magisk zip file using Magisk Manager, which stores it in the downloads folder. Once that's done, try the following:
fastboot boot twrp.img.
Navigate to the previously downloaded file and install it.
Flash Magisk.
Reboot.
Be patient.
The last one I put in there because there have been occasions where it has taken my P2XL a few minutes to get to the lock screen, but it eventually gets there. Now, if you're still looping a half hour later that's a cause for concern and you may need to redo things.

Strephon Alkhalikoi said:
One thing I would not do is push the zip or TWRP image to the device. Instead, in Android I would download the zip or image from twrp.me using Chrome, which will store it in the downloads folder. I then download the Magisk zip file using Magisk Manager, which stores it in the downloads folder. Once that's done, try the following:
fastboot boot twrp.img.
Navigate to the previously downloaded file and install it.
Flash Magisk.
Reboot.
Be patient.
The last one I put in there because there have been occasions where it has taken my P2XL a few minutes to get to the lock screen, but it eventually gets there. Now, if you're still looping a half hour later that's a cause for concern and you may need to redo things.
Click to expand...
Click to collapse
I just tried your system, unfortunately doesn't work for me. I was waiting around 20-30 min, nothing happened. Which version of image / OTA do you use? Maybe I should use some custom ROM?

I would boot into TWRP, install Magisk Uninstaller to clean up the old Magisk files, then install magisk again, followed by clear dalvik and cache. Then reboot system.
Downloads, here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

VanDerPe said:
Maybe I should use some custom ROM?
Click to expand...
Click to collapse
No need for a custom ROM.
I'm totally stock, except for root and TWRP. I download my OTAs direct from where Google hosts them, so these are complete system images.
Back up your device. Download the latest stock ROM image (NOT an OTA) and flash it using fastboot. Boot into Android, make sure OEM Unlocking is enabled, then return to the bootloader so you can flash TWRP and then Magisk.

Strephon Alkhalikoi said:
One thing I would not do is push the zip or TWRP image to the device. Instead, in Android I would download the zip or image from twrp.me using Chrome, which will store it in the downloads folder. I then download the Magisk zip file using Magisk Manager, which stores it in the downloads folder. Once that's done, try the following:
fastboot boot twrp.img.
Navigate to the previously downloaded file and install it.
Flash Magisk.
Reboot.
Be patient.
The last one I put in there because there have been occasions where it has taken my P2XL a few minutes to get to the lock screen, but it eventually gets there. Now, if you're still looping a half hour later that's a cause for concern and you may need to redo things.
Click to expand...
Click to collapse
Patience is good advice, I wiped my phone a few days ago, when all was said and done, I should have waited longer, because I was not boot looping.
I had the same problem yesterday as the OP, and running Magisk Uninstaller fixed it for me.