Related
So this is my first post on XDA, due to the lack of information on this particular device. Here I'll try to explain how I managed to root this device after trying several methods available here and all over the web. First I'll explain what didn't work:
VROOT (*)
Framaroot
Motochopper
SRS Root
MTK Toolkit
Nearly every solution on the web
After trying every method above, I noticed none of them were working. They all were giving false positives. No ROOT at all. I was kinda frustrated, 'cause I had followed every instruction possible, without success. I double checked my PC drivers, and I noticed something odd: Every time I changed the USB connection type on the L50, Windows installed different drivers for the device. I'm saying this was odd because I installed the drivers from LG drivers pack, so I was a bit confused. So, after Windows Installed the drivers for MTP, Modem, PTP and LG mode, I tried VROOT and... VOILÁ! I had ROOT:laugh::laugh:
So here are the steps I followed, and the tools I used:
Download VROOT (a.k.a. as IRoot) from w w w. mgyun. c o m / en / getvroot (without spaces)
Enable DEBUG MODE (Surf the web if you don't know on how to do it).
Plug your device to your PC and wait until Windows Installs the drivers for the connection type.
Without unplugging the device, Change the USB connection type to the next one. Wait 'till windows finishes installation.
Repeat the previous step untill you finish with all connection types.
Check Device Manager for missing drivers. If you have some missing, repeat steps above.
Open VROOT/IROOT and plug your device to the PC. Follow on-screen instructions and wait.
ENJOY!
Now, I have to find a Custom Recovery that works with L50... so if you guys know where I can get one, I'll appreciate your help.
Your Thread will be moved to appropriate Section.
So I tried to make a recovery for this phone, but it cannot boot. It says boot certification error, and the phone reboots normally.
So is it possible that the bootloader is locked? I want recovery for this phone too.
someone know how i can do a nandroid backup on LG L50 ?
Thank you so much. Worked on D213AR
Can you confirm if there is a way to unlock NFC hidden option on my phone?
jam66 said:
someone know how i can do a nandroid backup on LG L50 ?
Click to expand...
Click to collapse
If you managed to get Root (with the steps described on the OP) You can use Titanium Backup.
THE Ghost2 said:
So I tried to make a recovery for this phone, but it cannot boot. It says boot certification error, and the phone reboots normally.
So is it possible that the bootloader is locked? I want recovery for this phone too.
Click to expand...
Click to collapse
same for me i made cwm for it cant boot to it because it has locked boot loader
So is it possible to root the phone with the official rom?
Or am i missing something?
Hi everyone,
So, I just picked up a oneplus 8T, unlocked the bootloader, loaded TWRP, backed up my stock rom, and attempted to flash the vanilla version of the arrow rom. Everything was fine until TWRP said that something in the flash failed towrds the end of the flashing. I went back into TWRP, tried to wipe everything except internal storage and try again. The wipe also said that it failed. When I clicked reboot in TWRP, it got stuck in a soft boot loop.
I got the phone to boot back into recovery mode, and used the platform tools to get it back into fastboot. Somehow, I lost the stock recovery that I stored on the internal storage. I found this link, which had a one-click flash-all to bring an 8T back to stock OS.
Unbrick OnePlus 8T from a Hard-Bricked State using MSMDownload Tool
A complete guide on how to unbrick the OnePlus 8T from a hard-bricked state using the MSMDownload Tool and restore stock OxygenOS software.
www.thecustomdroid.com
My 8T is an unlocked carrier version, so I chose the global version labeled kebab_15_O.12_201110.zip
Once I unzipped it and clicked the flash all exe, it opened a terminal window, connected to the phone, and seemed to be flashing properly. When it finished, the phone rebooted, but never really rebooted. It is stuck on a black screen, which I believe is EDL mode.
The only sign of life now is when plugging in the USB cable, I can see the phone in device manager under OTHER DEVICES and it is labeled QUSB_BULK_CID:0412. I found another thread which explained this means the USB driver has been corrupted. I downloaded and tried to install the qualcomm drivers from this link
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
but the installation fails right at the end saying
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any way to unbrick this oneplus 8T, or did I just destroy it forever? I really feel like it should be able to be reflashed and fixed, I just can't figure it out. My next step today is going to be to call oneplus support, explain the situation, and hopefully they have some sort of insight for me, or at least a tool to get the proper USB drivers back into the phone so that I can access fastboot again.
Any help you guys could give me would be greatly appreciated.
-Vr4Mike
vr4mike said:
Hi everyone,
So, I just picked up a oneplus 8T, unlocked the bootloader, loaded TWRP, backed up my stock rom, and attempted to flash the vanilla version of the arrow rom. Everything was fine until TWRP said that something in the flash failed towrds the end of the flashing. I went back into TWRP, tried to wipe everything except internal storage and try again. The wipe also said that it failed. When I clicked reboot in TWRP, it got stuck in a soft boot loop.
I got the phone to boot back into recovery mode, and used the platform tools to get it back into fastboot. Somehow, I lost the stock recovery that I stored on the internal storage. I found this link, which had a one-click flash-all to bring an 8T back to stock OS.
Unbrick OnePlus 8T from a Hard-Bricked State using MSMDownload Tool
A complete guide on how to unbrick the OnePlus 8T from a hard-bricked state using the MSMDownload Tool and restore stock OxygenOS software.
www.thecustomdroid.com
My 8T is an unlocked carrier version, so I chose the global version labeled kebab_15_O.12_201110.zip
Once I unzipped it and clicked the flash all exe, it opened a terminal window, connected to the phone, and seemed to be flashing properly. When it finished, the phone rebooted, but never really rebooted. It is stuck on a black screen, which I believe is EDL mode.
The only sign of life now is when plugging in the USB cable, I can see the phone in device manager under OTHER DEVICES and it is labeled QUSB_BULK_CID:0412. I found another thread which explained this means the USB driver has been corrupted. I downloaded and tried to install the qualcomm drivers from this link
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
but the installation fails right at the end saying View attachment 5563423
Is there any way to unbrick this oneplus 8T, or did I just destroy it forever? I really feel like it should be able to be reflashed and fixed, I just can't figure it out. My next step today is going to be to call oneplus support, explain the situation, and hopefully they have some sort of insight for me, or at least a tool to get the proper USB drivers back into the phone so that I can access fastboot again.
Any help you guys could give me would be greatly appreciated.
-Vr4Mike
Click to expand...
Click to collapse
Fun Fact: THIS IS NOT WHERE YOU POST STUFF LIKE THIS this szection is for ROMS kernels and recoveries
GbnrVR said:
Fun Fact: THIS IS NOT WHERE YOU POST STUFF LIKE THIS this szection is for ROMS kernels and recoveries
Click to expand...
Click to collapse
well I tried to install a rom from this section, and need some form of recovery, so I figured the people here would likely be able to help. I will gladly post in another section if I have to...
Hey, ah, I assume it is done yet recommend disabling DSE (Driver Signature Enforcement) in Windows & then install the driver.
To do so, open CMD with admin privilege > type: bcdedit /set TESTSIGNING OFF and then try installing the driver. Because drivers don't usually failed to install or run properly. I understand the severity of the device's condition and also I'm glad you chose not giving up that's great, again I'll say install proper drivers after disabling DSE and then flash the original stock software. If it boots in EDL means its recoverable. Happened with me many times but the device was of different vendor/oem. Great luck.
psi.singh03 said:
Hey, ah, I assume it is done yet recommend disabling DSE (Driver Signature Enforcement) in Windows & then install the driver.
To do so, open CMD with admin privilege > type: bcdedit /set TESTSIGNING OFF and then try installing the driver. Because drivers don't usually failed to install or run properly. I understand the severity of the device's condition and also I'm glad you chose not giving up that's great, again I'll say install proper drivers after disabling DSE and then flash the original stock software. If it boots in EDL means its recoverable. Happened with me many times but the device was of different vendor/oem. Great luck.
Click to expand...
Click to collapse
I just searched qualcomm hs-usb, and found a download for the computer. After installing it, I rebooted my computer, and device installer now finds the phone listed as Qualcomm HS-USB QDLoader 9008 and assigned it to COM3. I have not had luck yet finding a working version of the MSM Download Tool. Every version I find and download says "packed image does not exist"
Can somebody give me the msm download tool? I have downloaded 4.0 from a few places and can not get it to work. Most downloads say package does not exist as the above screenshot shows. Others seem to work, and give a message that msm tool is running, but no windows ever pop up to log in or anything.
Am I doing something wrong trying to use the tool?
Try with this
MsmDownload_Tool_v5.0.15
MsmDownload_Tool_v5.0.15.zip - Devdrive - File Hosting For Publishers
Download file - MsmDownload_Tool_v5.0.15.zip
cutt.ly
mortazanabin said:
Try with this
MsmDownload_Tool_v5.0.15
MsmDownload_Tool_v5.0.15.zip - Devdrive - File Hosting For Publishers
Download file - MsmDownload_Tool_v5.0.15.zip
cutt.ly
Click to expand...
Click to collapse
Same thing. I keep getting this message when I try to open it. I tried double clicking the exe and also tried right click/run as administrator. Both give the same result.
try this patched version...
6T_MsmDownloadTool_v4.0.58_patched.rar | by OvrDriVE for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
if antivirus detected as virus then turn it off....
mortazanabin said:
try this patched version...
6T_MsmDownloadTool_v4.0.58_patched.rar | by OvrDriVE for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
if antivirus detected as virus then turn it off....
Click to expand...
Click to collapse
It did not detect as a virus, but how do I run/install a .rar file?
Are you able to get into fastboot? Did you check fastboot devices command and see your device listed? Then let me know there are ways to restore
kirankowshik said:
Are you able to get into fastboot? Did you check fastboot devices command and see your device listed? Then let me know there are ways to restore
Click to expand...
Click to collapse
I can not get into fastboot. I believe the phone is stuck in EDL mode. I have gotten MSM Download tool to open, but it will not flash to device. The tool knows that my phone is connected to COM3, but the MSM tool says waiting for device after clicking start, and never goes any further.
If anyone has experience with the MSM Downloading Tool and can help out, please chime in.
Thanks for the help everyone. I'm slowly getting there.
So, I noticed the caution label on the device in device installer...which usually indicates a driver problem. I reinstalled the qualcomm driver, and it says that it is installed properly. Is there an updated driver or something that I am missing?
try this method...
i thik this will help you to unbrick your device...
mortazanabin said:
try this method...
i thik this will help you to unbrick your device...
Click to expand...
Click to collapse
I can follow that exactly. The problem comes down to when connecting to USB cable and pressing start, the tool always says waiting for device, as if my device is not in EDL mode. I really think the issue is coming down to drivers for the phone to communicate with the tool. I do not think there should not be a caution symbol in device installer (as noted above) when the driver is properly installed. (even tho windows says I have the latest qualcomm driver for the device)
Does anyone have an updated driver in case I have an incorrect version? I am using the below. It says from 2014, so Im not sure that it is the correct driver. I got the link from a oneplus 8T post somewhere. I do not recall exactly which post it was.
your windows version? windows 10 or 11?
mortazanabin said:
your windows version? windows 10 or 11?
Click to expand...
Click to collapse
windows 10
I uninstalled and tried reinstalling the drivers, and now I can't get any of them to install. Device installer is back to saying QUSB_BULK for the device.
Disable windows dirver signature enforcement check
=========
Try this driver
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
=========
Try this msm tool
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
thanks me later if successful....
vr4mike said:
So, I noticed the caution label on the device in device installer...which usually indicates a driver problem. I reinstalled the qualcomm driver, and it says that it is installed properly. Is there an updated driver or something that I am missing?
View attachment 5563605
Click to expand...
Click to collapse
You have a yellow triangle there disable the driver signature in windows the MSN tool should be work properly
I got it to work!!!!
It was the driver signature enforcement.
However, that was not the only issue. After disabling the signature enforement, it was connecting to the device, but still not working. The stsus in the configuration panel started to connect, but then failed in red. I tried it a few times with the same result. I tried holding the 2 volume buttons while plugging in the USB, that didn't change anything either.
What ended up working was holding all 3 buttons while the tool was connected. It caused the device to momentarily disconnect and reconnect to the USB (via disappearing and reappearing in device installer, as well as the laptop making the disconnected and connected sounds) As soon as it reconnected and the laptop made the sound, the tool instantly started transmitting data and functioning.
My phone boots up as it did stock now, and does not even tell me that the bootloader is locked anymore upon first power up. It is 100% functioning just as it came out of the box!!!
I CAN NOT THANK THIS FORUM ENOUGH!!!!!
I have been using information here for years since I rooted my first Galaxy S3. This is the first time I have had to make an account and post.
You guys are the best, and were my only saving grace. Oneplus doesn't even have a working phone number anymore. All support must go thru email.
THANK YOU ALL SO MUCH!!!
I hope this information helps somebody else.
After trying to restore stock OOS and rebooting fastboot my phone is now stuck in Qualcomm Crashdump mode. I have MSMDownloadTool installed but it won't open, it just opens a windows saying "Program has been started" after executing it.
I also can't reboot to the bootloader, the phone just turns on or off.
What to do?
From my rather long post in https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-86563159 :
"connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect."
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
petrolblue said:
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
Click to expand...
Click to collapse
The delete/create logical commands are in the thread OP, but you have to tap on "click to show" button.
Note that fastbootd is not the same as fastboot. And you need to be in that mode to avoid the "critical" warning and to be able to do the logical partitions stuff.
So, after massively failing to update my 8T I am stuck in a bootloop with a bit of Crash dump [dm-verity device corrupted force dump].
I am still able to access fastboot but that is it. I can't get adb working, when I attempt to enter recovery mode all I get is a black screen, MSM is not able to find my phone/I can't get my phone to enter EDL (been trying for about 5 hours now).
I feel so defeated by this can anyone help me?
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Angilias37 said:
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Click to expand...
Click to collapse
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see the option to update the driver.
PS: you may need to flash boot, DTBO, and recovery in fastboot first before you can use fastbootd to flash the other partitions for the fastboot method.
BillGoss said:
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see l the option to update the driver.
Click to expand...
Click to collapse
Right but where's the update? From everything that I can find it is the most updated version
Angilias37 said:
Right but where's the update? From everything that I can find it is the most updated version
Click to expand...
Click to collapse
I use the driver (Qualcomm HS-USB QDLoader 9008) from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
OK
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Ok I take back what I said! That link with the CMDs worked!
I really don't know what I did differently, probably skipped a step or something, but I was able to reset my phone!
Still unsure what is going on with the drivers but the crisis has been averted!
Thank you BillGoss! You are incredibly helpful!
I am trying to use the msm tool to unroot my OnePlus 8t tmobile variant. Using the MSM tool I have run into a few different problems.
1. Drivers. When my phone is in edl mode plugged in to my computer, device manager recognizes it as usb_bulk. I tried using the provided .cab file to update windows Qualcomm drivers but windows could not ever find the files when updating. I found on another forum a automatic installer.
2. Although it now says Qualcomm 9008 windows says that driver digital signature is not recognized or corrupted. However the MSM tool does finally show COM 5 and when I plug in my device is stuck at waiting for device.
I'm pretty stuck right now and any information to help me out would be appreciated.
You need to disable driver signature verification in windows to successfully install drivers.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Rootk1t said:
You need to disable driver signature verification in windows to successfully install drivers.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
thank you I tried this and it still didnt work eventually i went into the registry and deleted lowerfilter, and now the drivers work however,
I am faced with another issue. The MSM tool says ddr not automatically detected and wont continue so we are now trying solve this issue
mreese14 said:
thank you I tried this and it still didnt work eventually i went into the registry and deleted lowerfilter, and now the drivers work however,
I am faced with another issue. The MSM tool says ddr not automatically detected and wont continue so we are now trying solve this issue
Click to expand...
Click to collapse
I have encountered this error and what I found was that there are some people, me being one where you need to disable your network and change your PC date to December 2018 and then open msm and proceed.
gforceriders said:
I have encountered this error and what I found was that there are some people, me being one where you need to disable your network and change your PC date to December 2018 and then open msm and proceed.
Click to expand...
Click to collapse
Worked for me, thank you!
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com