Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Juuuul said:
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Click to expand...
Click to collapse
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
hammered58 said:
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
Click to expand...
Click to collapse
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Juuuul said:
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Click to expand...
Click to collapse
You actually boot into TWRP it does not have to be installed,, you install it once you boot into it plus you would probably need a otg because you do not have a OS . Here's a link to the Msm tools
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/
There are several great write ups on how to use and install msm tool right here in the op7p forum I will see what I can find and post later
[OP7PRO][LATEST OOS 11.0.5.1 GM21AA/GM21BA] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Related
Hello,
I have a Mi Mix 3, MIUI global 10.2 stable, 10.2.2.0 PEEMIXM.
I managed to root, install TWRP and gcam after a few days of trying.
* Two days ago I updated from phone settings (About phone, Check updates ...)
* I lost both root and TWRP.
* I tried exactly the previous methods to root and phone stuck at booting (three dots flicking on the screen) - via PC / adb / fastboot.
* After that, I reset phone to factory settings and try again - boot in fastboot, try to flash TWRP and I get this error message: error cannot load TWRP.img file (not available or missing).
I also mention:
1. Phone was already rooted by the same procedure
2. Phone is unlocked
3. Dev options / USB debugging check
4. I renamed TWRP.img with recovery.img
5. I even try "TWRP" without extension ".IMG" (last week before the update I succeeded this way - no .img in the name of the file)
Please help
I need something so that I can root phone again AND won't delete TWRP and root after next update.
Thx very very much.
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
PWn3R said:
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
Click to expand...
Click to collapse
Thank you very much for your time and information. I must add that I was able to flash TWRP according to the procedure explained above, but I couldn't enter/access TWRP recovery. Then, I tried to re-flash TWRP and I always get the message: "error cannot load 'twrp.img' no such file or directory"
And I've tried several methods, several TWRP, different USB cables - almost everything you can imagine. Still, I cannot load the TWRP.img - it's not found. I must say I follow exactly the procedure explained in every posts.
What options do I have?
If you are using adb to load twrp, try putting it in the c/ of your pc, and putting twrp image in the adb folder, and if that didnt work, try renaming the img file to pocorecovery
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide
Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.
no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system
I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching
Functionally on OOS 10.0.1 OP6 ?
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.
Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?
WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works
After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
As above. No wifi, no sound. What's going on?
Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...
ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!
loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes
Does anyone successful root razer phone? kindly looking for video tutorial from 0 . Or anyone be able root my phone remotely? I'm living in n Everett , WA. I will pay the service if success thank you
Recently pulled mine out of storage to see if I was going to be able to use it for anything.
Unfortunately, most guides are out of date or give instructions that simply do not work anymore.
My best advice to you is that if you're going to root, avoid TWRP completely. Every attempt to modify a boot image or flash updated boot images from within TWRP caused my device to bootloop.
If you want to do it yourself (and I recommend that you do)
On your Razer Phone, Unlock bootloader,
Unlock flashing and flashing critical,
Flash the entire last Pie boot image from Razer ( https://developer.razer.com/razer-phone-dev-tools/factory-images/ ) 9.0 - MR2
Reboot into the OS and make sure you get the Welcome screen before shutting it down.
On a different phone, Copy the Razer Pie boot.img from the Razer system image download above (9.0 - MR2) to the other phone (any other phone that has Magisk)
Go into Magisk, click to update Magisk Manager, but instead select update an image file from SD Card. (The Razer Pie boot.img file)
When the boot.img file is updated from within Magisk Manager, copy it back off the phone to your PC.
Reboot your Razer Phone into Download/Fastboot mode,
And flash that modified boot.img to your phone. (fastboot flash boot_a magisk_patched.img, fastboot flash boot_b magisk_patched.img)
I was unable to get any boot images to stick if I didn't reboot into the OS after flashing stock first.
If you are on Pie already, you can try my boot image. But as always, if you **** up, I'm not going to be able to help you fix it. These instructions assume that you know how to get into fastboot and use fastboot flashing commands. So if you know how to flash a stock image from Razer, you should know how to flash a modified boot image.
https://www.androidfilehost.com/?fid=8889791610682915381
MD5: 9cfe9fe7ed040511c1dfb3454207c1c4
File: Magisk Patched boot.img for Razer Phone (2017) latest Pie devices (cheryl-p-release-7083) ONLY. No TWRP.
I was also able to get Substratum to work on Razer Phone 1 Pie. That was a bit of an ordeal in of itself.
Can make a thread if people need to know how.
Disclaimer: I am not responsible for damages of any kind.
Warning: Read everything at least one. Maybe i've missed something or u screwed it up.
1 Starting point
1. Have a clean OOS10 on both slots (with unlocked bootloader).
If u're coming not from stock:
You can do that using the MSM OOS tool. Warning: I recommend using the downgrade package from the oos repo + clean OOS10 flash with twrp on both slots. I used the MSM to downgrade and my Widevine went to L3 (comes back on 11). This might not be related to the MSM tool.
2. Download the latest recovery image and the latest build of PixelExperience (I recommend the plus edition).
2 Install
1. Boot into bootloader and boot the twrp image using adb: adb boot twrp.img
2. Format the data, reboot to bootloader (and twrp)
3. update OOS:
- copy a OOS11 package (OOS 11.0.2.1 as of 01.11.2021) onto u're device and flash it
- flash twrp zip
- reboot to recovery (twrp)
- Flash the package again (this time it will be automatically the other slot), reboot to bootloader (twrp will be gone now)
4. Flash the PixelExperience boot:
- fastboot flash boot your_pixel_boot.img
On u're device use the volume keys to select reboot to recovery and use the power key to confirm
5. Select factory reset, confirm and reboot to bootloader afterwards
6. Convert data partition: fastboot format:f2fs userdata and reboot to recovery which u can select in the bootloader using the volume keys
7. Flash the PixelExperience build:
- Select apply update and sideload u're pixelexperience build: adb sideload your_pixel_build.zip and wait until its done
- reboot to system
8. Booting ~ U're bootloader unlocked message will be there fore some time cause the PixelExperience animation only plays at the end of the boot
3 Fixing
- For fingerprint to work i had to reboot one more time
- Everything is very small. So i changed mininal dp in dev options to 411dp and the scaling looks just like on OOS10 now
- In OnePlus settings activate Doly Atmos for better sound and probably DC-Dimming
- My battery needed 3 cycles, then i had a battery live like on OOS10
4 Update
Boot to bootloader, flash the new boot, reboot to recovery, sideload, reboot to system. Done
5 Root
- Extract boot.img form payload.bin from your_pixel_build.zip using payload dumper
- Patch using Magisk
- Flash the new boot and reboot
- Activate Magisk Hide to pass SaftyNet
6 Issues
My camera was unstable - Fixed
Fingerprint (Detection/Speed) - Fixed
7 Go back to OOS
Boot to EDL mode and restore with the MSM OOS tool (Detailed description included)
8 Conclusion
The rom is supersmooth and is much better than OOS11 cause "it simply works". OOS11 compared is slow, heats up the device and drains battery.
Hi, would you mind elaborating 1st step as well as provide links to PixelExperience Boot image files? Thanks!
I was on OOS 11, unlocked bootloader and flashed TWRP Nebrassy version, whenever I try to flash PE ROM zip directly, it just says "Flashing A/B zip to inactive slot: A. To flash additional zips, please reboot recovery to switch to the updated slot." and vice versa when switched to different slot. I thought I messed something up so I flashed YAAP and now I have YAAP recovery on Slot A and TWRP on slot B and YAAP rom so if you could maybe elaborate the steps, it would be really helpful!
Sachin7843 said:
Hi, would you mind elaborating 1st step as well as provide links to PixelExperience Boot image files? Thanks!
I was on OOS 11, unlocked bootloader and flashed TWRP Nebrassy version, whenever I try to flash PE ROM zip directly, it just says "Flashing A/B zip to inactive slot: A. To flash additional zips, please reboot recovery to switch to the updated slot." and vice versa when switched to different slot. I thought I messed something up so I flashed YAAP and now I have YAAP recovery on Slot A and TWRP on slot B and YAAP rom so if you could maybe elaborate the steps, it would be really helpful!
Click to expand...
Click to collapse
Just do exactly what i've written. I did link all files and tools. The recovery can also be found at PixelExperience. If u messed up then u can still use the MSM tool to bring it back to stock.
trueToastedCode said:
Just do exactly what i've written. I did link all files and tools. The recovery can also be found at PixelExperience. If u messed up then u can still use the MSM tool to bring it back to stock.
Click to expand...
Click to collapse
There are couple of steps which are still confusing for me so I thought to ask. Anyway, thanks for the help
trueToastedCode said:
mininal dp to 411dp
Click to expand...
Click to collapse
thanks for the guide, was able to follow through and get PE Running, I just wanted to know where did you change this dpi from? did you flash an external magisk module or is it right there in settings (which I am unable to find)
trueToastedCode said:
Disclaimer: I am not responsible for damages of any kind.
Warning: Read everything at least one. Maybe i've missed something or u screwed it up.
1 Starting point
1. Have a clean OOS10 on both slots (with unlocked bootloader).
If u're coming not from stock:
You can do that using the MSM OOS tool. Warning: I recommend using the downgrade package from the oos repo + clean OOS10 flash with twrp on both slots. I used the MSM to downgrade and my Widevine went to L3 (comes back on 11). This might not be related to the MSM tool.
2. Download the latest recovery image and the latest build of PixelExperience (I recommend the plus edition).
2 Install
1. Boot into bootloader and boot the twrp image using adb: adb boot twrp.img
2. Format the data, reboot to bootloader
3. update OOS:
- copy a OOS11 package onto u're device and flash it
- flash twrp zip
- reboot to recovery
- Flash the package again (this time it will be automatically the other slot), reboot to bootloader (twrp will be gone now)
4. Flash the PixelExperience boot:
- fastboot flash boot_a your_pixel_boot.img
- fastboot flash boot_b your_pixel_boot.img
On u're device use the volume keys to select reboot to recovery and use the power key to confirm
5. Select factory reset, confirm and reboot to bootloader afterwards
6. Convert data partition: fastboot format:f2fs userdata and reboot to recovery which u can select in the bootloader using the volume keys
7. Flash the PixelExperience build:
- Select apply update and sideload u're pixelexperience build: adb sideload your_pixel_build.zip and wait until its done
- in advanced options select reboot to recovery and confirm it with the power key
- Sideload the build again (this time it will be automatically the other slot)
- reboot to system
8. Booting ~ U're bootloader unlocked message will be there fore some time cause the PixelExperience animation only plays at the end of the boot
3 Fixing
- For fingerprint to work i had to reboot one more time
- Everything is very small. So i changed mininal dp to 411dp and the scaling looks just like on OOS10 now
- In OnePlus settings activate Doly Atmos for better sound and DC-Dimming
- My battery needed 3 cycles, then i had a battery live like on OOS10
4 Update
Boot to bootloader, flash the new boot to a and b, reboot to recovery, sideload on current slot, reboot to recovery, sideload again, reboot to system. Done
5 Issues
My camera was unstable: It freezed and crashed. I asked others using the same setup but they did not have the issue ~ At least that's what they told me i don't know if they use their camera the way i do.
I've published the bug: https://github.com/PixelExperience/android-issues/issues/296
6 Conclusion
The rom is supersmooth and is much better than OOS11 cause "it simply works". OOS11 compared is slow, heats up the device and drains battery. Unfortunetly i have to stick to OOS11 cause a not fully working camera is unacceptable for me. Probably its fixed when u're reading this
Click to expand...
Click to collapse
No matter how many times I reboot, I can't get my fingerprint registered. whenever I try setting up, when I place my thumb, I just get a white light shine on the FPS area and no vibration/ registration. sometimes I get just a small vibration for 1 second and then shows the error "partial fingerprint unable to capture"
tbiwalkar said:
No matter how many times I reboot, I can't get my fingerprint registered. whenever I try setting up, when I place my thumb, I just get a white light shine on the FPS area and no vibration/ registration. sometimes I get just a small vibration for 1 second and then shows the error "partial fingerprint unable to capture"
Click to expand...
Click to collapse
same here fingerprint also not working and unable to get widevine L1 too i don't know how some are getting widevine L1 even i followed guide in PE website where developer gives option to lock bootloader after flashing after locked bootloader too i am unable to get widevine L1 (i have indian/global oneplus 7)
tbiwalkar said:
No matter how many times I reboot, I can't get my fingerprint registered. whenever I try setting up, when I place my thumb, I just get a white light shine on the FPS area and no vibration/ registration. sometimes I get just a small vibration for 1 second and then shows the error "partial fingerprint unable to capture"
Click to expand...
Click to collapse
U can capture a logcat and report the bug on GitHub. Otherwise idk
sparkk_kk said:
same here fingerprint also not working and unable to get widevine L1 too i don't know how some are getting widevine L1 even i followed guide in PE website where developer gives option to lock bootloader after flashing after locked bootloader too i am unable to get widevine L1 (i have indian/global oneplus 7)
Click to expand...
Click to collapse
Widevine issues on OnePlus phones... Sooo weird. For some people it only works on OOS11 or only OOS10 and if it does not work at all and OnePlus does not fix it with an OTA then i guess u dont have WidevineL1 U can try to restore u're device with the MSM tool
trueToastedCode said:
Widevine issues on OnePlus phones... Sooo weird. For some people it only works on OOS11 or only OOS10 and if it does not work at all and OnePlus does not fix it with an OTA then i guess u dont have WidevineL1 U can try to restore u're device with the MSM tool
Click to expand...
Click to collapse
yes with stock OOS11 or OOS10 in locked bootloader state i can get widevine L1 whenever i unlock bootloader then itself it goes to widevine L3 it's weird even tried to lock bootloader by installing PE and their instructions after that also it stays at widevine L3 will try on 11.0.2.1 again and lets see now what happens
now i got widevine l1 after unlocking bootloader of my device bro with 11.0.2.1 i just unlocked bootloader setup normally and sideloaded drminfo app it shows widevine L1
Im having problems (adb server version (41) doesn't match this client (39) killing)
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP