Database Info

Bricked One plus 6 [no software workd] [Help post]

My one plus 6 device suddenly bricked without any sign. Shows only boot loader screen. I can reach recovery mood. I wiped all data (I select "erase everything(Music, pics, etc). Then I tried MSM tool (Run as administrator). After complete download it reboot again and wait for 1/2 min. It gose again to boot loop. Then I tried fastboot method. It said "failed to load 'images.zip': Not enough space". I try to wipe data by command "fastboot erase userdata". It said "FAILED (remote: Erase is not allowed in Lock State)". Also run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on my phone screen. Typed "fastboot continue" and it goes to boot loop. Now I stacked in boot loop screen. What should i do now??

you can go into recovery mod that means your phone is not brick.should you try to use fastboot rom?

soihuvuontrang said:
you can go into recovery mod that means your phone is not brick.should you try to use fastboot rom?
Click to expand...
Click to collapse
of course i tried that method. Download latest OOS and adb - platform tools v28.0.0. pest all into OSS file after unzip. I went to fastboot recovery mood. Run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on mobile screen. (NB: when I type command "fastboot devices" it can recognize my device).
{
"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"
}

zobayer.a.m said:
of course i tried that method. Download latest OOS and adb - platform tools v28.0.0. pest all into OSS file after unzip. I went to fastboot recovery mood. Run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on mobile screen. (NB: when I type command "fastboot devices" it can recognize my device).
Click to expand...
Click to collapse
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...

James Blode said:
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
Click to expand...
Click to collapse
distinguish beetwen Msm tool and fastboot rom(https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
your phone isnot brick,it boot into fastboot mood,you can you fastboot rom (link above). goodluck!

soihuvuontrang said:
distinguish beetwen Msm tool and fastboot rom(https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665)
your phone isnot brick,it boot into fastboot mood,you can you fastboot rom (link above). goodluck!
Click to expand...
Click to collapse
Unfortunately my boot loader is locked. This will not work. I tried it also

James Blode said:
Of course You can't flash anything in fastboot nor in recovery...when you fleshed with msm download tool first time you've LOCKED YOUR BOOTLOADER...SO NO MORE FASTBOOT AND RECOVERY FLASHES...TRY WITH MSM TOOL AGAIN...AND DON'T CHANGE ANYTHING...OR UNLOCK YOUR BOOTLOADER AGAIN...YOU CAN READ HOW BASED ON WHAT OOS VERSION IS YOU ON. READ ABOUT IT. AND REMEMBER WHEN IT SAYS LOCKED STATE AND CAN'T FLASH IN FASTBOOT IT MEANS YOUR BOOTLOADER IS LOCKED...
Click to expand...
Click to collapse
Ok i understand. I tried MSM tool also. After connect my phone with PC this software show connected status. After hit start it start to update. All process work perfectly fine and goes to completed status (text in MSM tool become green). My phone boot up and 1 or 2 min later it shows welcome screen without any touch response. Touch do not work (though touch was ok). After a few second my phone reboot again and stuck into bool loop again. I tried "enchilada_22_O.09_180517", "ANDROID+9+OOS+9.0.8+enchilada_22_O.33_190801_repack", "ANDROID+10+OOS+10.3.2+enchilada_22_J.44_200222". All MSM tools ended up with same result

Are you not able to unlock bootloader via fastboot and then flash a fastboot ROM?

zobayer.a.m said:
Ok i understand. I tried MSM tool also. After connect my phone with PC this software show connected status. After hit start it start to update. All process work perfectly fine and goes to completed status (text in MSM tool become green). My phone boot up and 1 or 2 min later it shows welcome screen without any touch response. Touch do not work (though touch was ok). After a few second my phone reboot again and stuck into bool loop again. I tried "enchilada_22_O.09_180517", "ANDROID+9+OOS+9.0.8+enchilada_22_O.33_190801_repack", "ANDROID+10+OOS+10.3.2+enchilada_22_J.44_200222". All MSM tools ended up with same result
Click to expand...
Click to collapse
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...

°Washy said:
Are you not able to unlock bootloader via fastboot and then flash a fastboot ROM?
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"

James Blode said:
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom (9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT) and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonseance work. I tried "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and then enchilada_22_O.09_180517 2 times, later on "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214". It worked!! My phone showing welcome screen. Every things seems ok. But i a few min latter realize that none of phone sensor working. So i decided switch other OOS. but 1st i unlock boot loaded. Use "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" role back pack via local OTA update. But its not working. stack in boot loop. Use fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip". Same this goes there. stuck in boot loop. how can i get my phone sensor worked or Is there any way to role back?

zobayer.a.m said:
Yes i tried it also. Download fastboot rom (9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT) and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonseance work. I tried "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and then enchilada_22_O.09_180517 2 times, later on "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214". It worked!! My phone showing welcome screen. Every things seems ok. But i a few min latter realize that none of phone sensor working. So i decided switch other OOS. but 1st i unlock boot loaded. Use "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" role back pack via local OTA update. But its not working. stack in boot loop. Use fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip". Same this goes there. stuck in boot loop. how can i get my phone sensor worked or Is there any way to role back?
Click to expand...
Click to collapse
Did you switch on "unlock bootloader" under developer options? It could be the reason for bootloop after MSm flash.

James Blode said:
Ok...i think you haven't tried full stock firmware which is msmdonwload tool but with 5.1.6 firmware...or you tried it?that might change everything...
Plus if that didn't worked as well...you should search for oneplus 6 fastboot roms here in xda...mauronofrio has a dedicated thread for it...search oneplus 6 fastboot rom on google and you should see an xda thread...go there download latest 10.3.3 and read all the instructions CAREFULLY...it might help you...try it and give us a feedback...
Click to expand...
Click to collapse
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonsense work. I flash "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and flash "enchilada_22_O.09_180517" 2 times and then flash "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214.zip". Surprisingly it worked!! I dont know why and how it worked.
But after e few min i realize that none of my phone sensor working. I decided to role back to android 9. I unlock boot loader. Flash "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release" role back pack via local OTA update. But it again goes to boot loop. After that i try fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT". but again goes to boot loop. [N.B all rom i maintained in above were flash successfully]. Is there any way to get back my phone sensor worked or goes to previous version??

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
Click to expand...
Click to collapse
you did not unlock bootbloader.and fastboot rom was completely failed.you should read on forum how to unblock bootloader,root oneplus 6.wish you success!

°Washy said:
Did you switch on "unlock bootloader" under developer options? It could be the reason for bootloop after MSm flash.
Click to expand...
Click to collapse
Negative. When I laslt flas MSM tool oos 10.3.0 boot loader was locked. I unlocked it as normal procedure (under developer opetion
turn on oem, usb debugging and other then go to fastboot mood any type command "fastboot oem unlock").

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
I also do some nonsense work. I flash "MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5" and flash "enchilada_22_O.09_180517" 2 times and then flash "ANDROID+10+OOS+10.3.0+enchilada_22_J.42_191214.zip". Surprisingly it worked!! I dont know why and how it worked.
But after e few min i realize that none of my phone sensor working. I decided to role back to android 9. I unlock boot loader. Flash "fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release" role back pack via local OTA update. But it again goes to boot loop. After that i try fastboot rom "9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT". but again goes to boot loop. [N.B all rom i maintained in above were flash successfully]. Is there any way to get back my phone sensor worked or goes to previous version??
Click to expand...
Click to collapse
Flash whatever build you want...and then go to mauronofrios xda page where it has fastboot roms for op6...download the oos version that you have...and there will be one option FLASH ONLY PERSIST(FLASH PERSIST)...flash it via fastboot with oos installed and sensors should work...but for that you have to unlock your bootloader first...
Feels like you've damaged your phones critical partitions....I SAID READ MAURONOFRIOS THREAD CAREFULLY... ESPECIALLY FLASHING INSTRUCTIONS...
Wait here for a minute...

Read this carefully...i said you damaged all your phones CRITICALS...SO WHAT YOU NEED TO DO?
ALSO READ FOR THE SENSOR FLASH THAT I'VE SAID...AND TRY IT...i also had a sensor problem back in the days(touch worked...but no other sensor like proximity or gyro working)...and tried msmtool several times... didn't helped me...but this guys thread helped a lot with that...
Here is the thread also if You can't find it
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/amp/

zobayer.a.m said:
Yes i tried it also. Download fastboot rom and copy all file to adb - platform tools v28.0.0. After clicking all-flash.bat it continuing some work and at last says "FAILED (remote: Flashing is not allowed in Lock State)"
Click to expand...
Click to collapse
you should use miniADB and fastboot tool to unlock bootbloader using instruction in forum.
fastboot rom,you only run all-flash.bat by clicking on it (not copy all files to adb-platform tool)before run the line" flash-all.bat" you should unzip file images.zip in fastboot rom.

soihuvuontrang said:
you should use miniADB and fastboot tool to unlock bootbloader using instruction in forum.
fastboot rom,you only run all-flash.bat by clicking on it (not copy all files to adb-platform tool)before run the line" flash-all.bat" you should unzip file images.zip in fastboot rom.
Click to expand...
Click to collapse
I do that and click all-flash.bat. All work perfectly on PC CMD command prompt. Successfully finish and it seems like bellow
-----
sending sparse 'vendor' 1/2 (504897 KB)...
OKAY [ 12.021s]
writing 'vendor' 1/2...
OKAY [ 0.003s]
sending sparse 'vendor' 2/2 (284097 KB)...
OKAY [ 9.762s]
writing 'vendor' 2/2...
OKAY [ 0.003s]
Setting current slot to 'b'...
OKAY [ 18.228s]
erasing 'userdata'...
OKAY [ 0.714s]
sending 'userdata' (5273 KB)...
OKAY [ 0.134s]
writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 129.194s
Press any key to exit...
----
My phone reboot again and nothing actually happen. I stuck in boot loader as like before.

zobayer.a.m said:
I do that and click all-flash.bat. All work perfectly on PC CMD command prompt. Successfully finish and it seems like bellow
-----
sending sparse 'vendor' 1/2 (504897 KB)...
OKAY [ 12.021s]
writing 'vendor' 1/2...
OKAY [ 0.003s]
sending sparse 'vendor' 2/2 (284097 KB)...
OKAY [ 9.762s]
writing 'vendor' 2/2...
OKAY [ 0.003s]
Setting current slot to 'b'...
OKAY [ 18.228s]
erasing 'userdata'...
OKAY [ 0.714s]
sending 'userdata' (5273 KB)...
OKAY [ 0.134s]
writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 129.194s
Press any key to exit...
----
My phone reboot again and nothing actually happen. I stuck in boot loader as like before.
Click to expand...
Click to collapse
it's quite strange.Did you unzipped the file"IMAGES.ZIP"?
---------- Post added at 10:31 AM ---------- Previous post was at 10:27 AM ----------
zobayer.a.m said:
My one plus 6 device suddenly bricked without any sign. Shows only boot loader screen. I can reach recovery mood. I wiped all data (I select "erase everything(Music, pics, etc). Then I tried MSM tool (Run as administrator). After complete download it reboot again and wait for 1/2 min. It gose again to boot loop. Then I tried fastboot method. It said "failed to load 'images.zip': Not enough space". I try to wipe data by command "fastboot erase userdata". It said "FAILED (remote: Erase is not allowed in Lock State)". Also run "flash-all.bat" and it said "FAILED (remote: Flashing is not allowed in Lock State)". Nothing happen on my phone screen. Typed "fastboot continue" and it goes to boot loop. Now I stacked in boot loop screen. What should i do now??
Click to expand...
Click to collapse
error at"images.zip" it means that you have to unzip the file images.zip.

Recovery installing error: Writing 'recovery' FAILED (remote: 'Not allowed on PRODUCTION device')

Hello, I wanted to go back to the initial system that was on my U11 but there was a very big problem because I can not lock the bootloader or install recovery because it shows the error: FAILED (remote: '4 RU_BATTERY_LOW please connect charger (0% <30%)'). And I will add that the battery is 100%

I don't have a answer for you but you can check out this thread for ideas,, hth,
[help] FAILED (remote: 4 RU_BATTERY_LOW please connect charger (0% < 30%))
I try to downgrade form Pie to Oreo but It's not work. Now I can't install any thing (RUU exe firmware, TWRP), message error: FAILED (remote: 4 RU_BATTERY_LOW please connect charger (0% < 30%)). I charge my phone 100%. But anything change. I...
forum.xda-developers.com

Hurray: D I fixed error: "Recovery" FAILED error (remote: "Not allowed on PRODUCTION device").
Guide to the incomprehensible
1. Download the original firmware from (https://4pda.ru/forum/index.php?showtopic=830013) (the firmware information can be read in the download mode. Example: radio-8998-002772-1711161638)
2. Download RUU-Decrypt-Tool (https://forum.xda-developers.com/t/...sal-htc-ruu-rom-decryption-tool-3-6-8.3382928) I extract the system (extraction guide is described in the link)
3. From the extracted system, copy the file (hosd_signed.img) to the adb folder on the computer, then turn on the phone in bootloader mode and enter the command: fastboot flash hosd hosd_signed.img
4. Our described bug has just been fixed. Now you can install TWRP without any problems. Good luck

wksawery71 said:
Hurray: D I fixed error: "Recovery" FAILED error (remote: "Not allowed on PRODUCTION device").
Guide to the incomprehensible
1. Download the original firmware from (https://4pda.ru/forum/index.php?showtopic=830013) (the firmware information can be read in the download mode. Example: radio-8998-002772-1711161638)
2. Download RUU-Decrypt-Tool (https://forum.xda-developers.com/t/...sal-htc-ruu-rom-decryption-tool-3-6-8.3382928) I extract the system (extraction guide is described in the link)
3. From the extracted system, copy the file (hosd_signed.img) to the adb folder on the computer, then turn on the phone in bootloader mode and enter the command: fastboot flash hosd hosd_signed.img
4. Our described bug has just been fixed. Now you can install TWRP without any problems. Good luck
Click to expand...
Click to collapse
Hi. Can you help me with this one? I've downloaded "2PZCIMG_OCEAN_DUGL_P90_SENSE10GP_MR_HTC_Europe_3.31.401.1_Radio_8998-200321-1905141529_release_540931_signed.zip" and after that i did " RUU_Decrypt_Tool.exe 2PZCIMG_OCEAN_DUGL_P90_SENSE10GP_MR_HTC_Europe_3.31.401.1_Radio_8998-200321-1905141529_release_540931_signed.zip -f" and in the end i've rebooted my HTC U11 in bootloader menu. And from the PC after i have connected my phone to it , i have run the command : "fastboot flash hosd hosd_signed.img" and rebooted the phone again in bootloader mode and trying to install recovery image with fastboot command but i am still getting the error that you having .
Please advise !

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 :
How to Restore OnePlus Nord Back to Stock OxygenOS Software - A Complete Guide
In this guide, we will show you how to restore the stock OxygenOS software on the OnePlus Nord by flashing the factory image/Fastboot ROM. Things like custom ROMs, TWRP, and Magisk root are pretty…
www.thecustomdroid.com
I currently am stuck there
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (1996 KB)...
OKAY [ 0.055s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.057s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock_critical
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
Click to expand...
Click to collapse
I just simply do not understand what could be wrong here.
In fastoot mode I get "device - State unlocked"
As you already saw, it seems the device is completely unlocked. What could be wrong ?
Also, some steps before, I get that :
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
I suspect switching to the automated in Windows won't change much.
It is strange because I am able to perform these steps without problems, ones the ones after seem to not work :
./fastboot flash boot boot.img
./fastboot flash dtbo dtbo.img
./fastboot flash modem modem.img
./fastboot flash recovery recovery.img
./fastboot --disable-verity flash vbmeta vbmeta.img
./fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
My phone is a Oneplus Nord and I am using the advised Oxygen OS ROM provided in the tutorial I linked at the beginning of my message.
I hope you'll be able to get me out of this as I unfortunately can't figure out how to solve this problem on my own.
Best regards

krakard said:
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Yes, that makes sense.
Fastboot should be located at /usr/bin/fastboot. Since you're not in that directory, ./fastboot won't work. (This ./ means: "Look at the current working directory for the command fastboot." If it cannot find fastboot there or it isn't a shell command, it will throw an error.)
However, since you didn't install fastboot globaly, you have to address its exact path inside your platform-tools folder. If fastboot is not in Partition-image folder, ./ won't work.
Can't help you with your main issue though.
Edit: You seem to have fastboot installed globally though:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
So my first explaination is valid.

Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.

krakard said:
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
Click to expand...
Click to collapse
You're welcome.
BTW:
krakard said:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
There is no "fastboot" to boot into. Instead, type
Code:
fastboot reboot bootloader
I didn't mention that yesterday for some reason.

Guys, here is where I am at now. Still struggling but I feel I am very near ! Some help maybe ?
https://forum.xda-developers.com/t/...your-device-to-oxygenos.4148415/post-85022511
best regards

SOLVED

krakard said:
SOLVED
Click to expand...
Click to collapse
How did you fixed this? I'm currently stuck at the same point as you with a oneplus 8

Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?

mbootsman1 said:
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
Click to expand...
Click to collapse
I found the solution, you have to do fastboot reboot fastboot which reboots you to fastbootd instead of fastboot. There you can flash critical partitions without issue.

Hi,
As the command recommanded everywhere :
Code:
fastboot flashing unlock_critical
had never worked for me in the bootloader environment,
I have to reboot i my rom embedded recovery in order to flash the file (apply update menu) through the :
fastbootD
To sum up :
#From Android (while having all prerequisite done ie bootloader unlocked...)
Code:
adb reboot bootloader
#From the bootloader I choose to boot to recovery and I get to the rom custom recovery
#In the custom recovery, I choose the menu "apply update" that will lead me to the fastbootD mode
#I type the appropriate command to flash the persist partition
Code:
fastboot flash persist "c:\your_path_to_your_persist_file\persist.img"
#Then I simply reboot the phone
Code:
fastboot reboot
PS : Initially flash the OxygenOS (OOS) 11, then apply the CRdroid Android v8 custom rom (based on Android 12)

I did it similar like solid-snake:
In my case I also had no access to fastbootD
The solution came randomly when I flashed back the first part from my lineageOS package:dtbo.img, vbmeta.img and the recovery.img --> after that my phone naturally booted in a fastbootD mode from the lineageOS package.
I modified the flash-all.bat from the stock ROM fastboot flash package:
I removed the line with the reboot command, because I'm already in the fastbootD mode.
Then I ran the modified flash-all.bat and everything went well.

If anyone else struggles (like I did) to get the phone in EDL mode, or the "Flashing is not allowed for Critical Partitions" error ,even if the "fastboot flashing unlock_critical" cmd was executed, here are some hints that might help.
I tried forever on a Linux computer without any luck, so I ended up installing Windows 10 on actual hardware to finally unbrick my One Plus Nord (Avicii). Here are the most important steps, YMMV, execute at own risk:
bcdedit.exe /set nointegritychecks off run this cmd as admin in terminal, toggle to "on"
then install edl drivers as admin, This is where I struggled the most, I finally found an .exe file(QDLoader HS-USB Driver_64bit_Setup.exe) that I just installed and then phone showed up as it should in device manager. ("Qualcomm HS-USB QDLoader 9008," not "QUSB_BULK")
install adb and fastboot. (platform-tools)
install MSM-Download-Tool
download stock OS for use in MSM-Download-Tool program
open msm tool, if phone is not recognised try turning on and holding power pluss both volume, or just one of the volumes.
uncheck the "sha hash check" box
flash
if you get the "Sahara Communication Failed", just try again, it worked for me.
wipe
erase Windows 10 and replace with any Linux distro, tell your PC it will never happen again.
enjoy
Here are link to the EDL-drivers that worked for me. Or just do a web-search for "QDLoader HS-USB Driver_64bit_Setup.exe"
The flashing process will take over 300 seconds, be patient.

[SOLVED] Unable to flash boot image - Pixel 4a

I have been using this method to flash new stock update every month to my rooted pixel 4a.
Steps I follow:
- Download the factory image of the last month
- Extract the boot.img. And patch it using magisk canary build
- Move the boot.img to the computer and flash it in fastboot mode
- flash the complete image
- Reroot the phone using magisk
This time with January update, I am getting stuck on step 3. Everytime I try to flash the bootloader image using the command:
C:\platform-tools>fastboot flash bootloader "C:\platform-tools\magisk_boot.img.img"
I get the following error:
Sending 'bootloader' (65536 KB) OKAY [ 1.609s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
No, It isn't booted in fastbootd mode. I am using correct Fastboot mode using the hotkeys
Kindly assist. Thank you

Your fastboot may be old... Upgrading it might help.
Or you might be able to use fastboot boot patched.img to get temporary root and use Magisk manager to install (direct) to make it permanent. That's what I do, and it's always worked.

Absarock said:
I have been using this method to flash new stock update every month to my rooted pixel 4a.
Steps I follow:
- Download the factory image of the last month
- Extract the boot.img. And patch it using magisk canary build
- Move the boot.img to the computer and flash it in fastboot mode
- flash the complete image
- Reroot the phone using magisk
This time with January update, I am getting stuck on step 3. Everytime I try to flash the bootloader image using the command:
C:\platform-tools>fastboot flash bootloader "C:\platform-tools\magisk_boot.img.img"
I get the following error:
Sending 'bootloader' (65536 KB) OKAY [ 1.609s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
No, It isn't booted in fastbootd mode. I am using correct Fastboot mode using the hotkeys
Kindly assist. Thank you
Click to expand...
Click to collapse
fastboot flash boot
And not
fastboot flash bootloader
Cheers!

Typhus_ said:
fastboot flash boot
And not
fastboot flash bootloader
Cheers!
Click to expand...
Click to collapse
Thank you, sir. It helped

a1291762 said:
Your fastboot may be old... Upgrading it might help.
Or you might be able to use fastboot boot patched.img to get temporary root and use Magisk manager to install (direct) to make it permanent. That's what I do, and it's always worked.
Click to expand...
Click to collapse
I tried updating fastboot. Didn't work.
Either way I was able to solve by using the command boot_b instead of bootloader. B being the partition

Stuck in fastboot mode

I tried to install LineageOS on my OnePlus Nord following this thread:
[ROM][13][UNOFFICIAL] LineageOS 20 - microG [OnePlus Nord/avicii]
You care a lot about privacy and security? You want an up to date LineageOS build that will not hold you back in regards of user experience? Then LineageOS 20 microG edition is right for you! (Non-microG vanilla LineageOS version also available)...
forum.xda-developers.com
I successfully flashed the recovery.img (provided in the thread), and did a factory reset in recovery. However, I could not find the "Apply Update / Apply from ADB" option, so I though I'll just flash TWRP on there instead. But this bricked my phone. And I got this error message:
{
"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"
}
If I hold vol-down + power button I was also able to reach fastboot mode.
I found MSMDownloadTool and this thread:
[OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
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
But whatever Firmware image I tried to use the result was always the same: "Device not match image".
(On the box that the phone came in it says "OnePlus Nord AC2003")
I tried different versions of Global, EU and India Firmware files.
I have also tried different versions of Qualcomm drivers (1.00.25 and 1.00.55)
And I have tried different cables, and USB ports.
So I tried to flash stock ROM using this thread:
[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com
It works fine in the beginning, but after the fastboot reboot fastboot step I start getting:
FAILED: Flashing is not allowed for Critical Partitions.
Also, If I do fastboot flashing unlock_critical it says the phone is already unlocked.
I have also tried fastboot boot recovery.img with different .img files (recovery.img provided in the first thread I linked, and also TWRP.img) but this just reboots the phone, and then it gets stuck at Oneplus logo reading "Fastboot Mode" below, until I restart and it gets into fastboot menu again.
I can only reach fastboot mode as shown in picture above, and EDL mode.
I have no clue on how to fix my phone. Any ideas?

Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps

sinkoo1979 said:
Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps
Click to expand...
Click to collapse
Thanks a lot for your reply!
You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.
What do you mean by change slots?
What is pronton lock off rom A13? Is it something I should use as well?
How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?
Thanks in advance!

sixtenson1 said:
Thanks a lot for your reply!
You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.
What do you mean by change slots?
What is pronton lock off rom A13? Is it something I should use as well?
How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?
Thanks in advance!
Click to expand...
Click to collapse
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.
Custom Rom
Don't know which android version you have
Use this link https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/

sinkoo1979 said:
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.
Custom Rom
Don't know which android version you have
Use this link https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/
Click to expand...
Click to collapse
Thanks for the additional information!
I started by checking what slot was in use:
fastboot getvar all
(bootloader) current-slot:a
I then changed slot to b:
fastboot --set-active=b
And then started following the link you provided.
However, running in to the same problem as before.
When running:
fastboot reboot fastboot
I get the following Error:
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And when trying to flash abl:
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot flashing unlock
fastboot flashing unlock_critical
both generate the same Error message:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
What could this be?
Thanks in advance!

sixtenson1 said:
Thanks for the additional information!
I started by checking what slot was in use:
fastboot getvar all
(bootloader) current-slot:a
I then changed slot to b:
fastboot --set-active=b
And then started following the link you provided.
However, running in to the same problem as before.
When running:
fastboot reboot fastboot
I get the following Error:
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And when trying to flash abl:
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot flashing unlock
fastboot flashing unlock_critical
both generate the same Error message:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
What could this be?
Thanks in advance!
Click to expand...
Click to collapse
Mine worked with that. Don't really know now. Hope you solve it.

sinkoo1979 said:
Mine worked with that. Don't really know now. Hope you solve it.
Click to expand...
Click to collapse
When I run:
$ fastboot oem device-info
I get the following:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Device does not seem to be critical unlocked. When I run:
$ fastboot flashing unlock_critical
Output is:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Does the device need to be critical unlocked? And if so, how can I unlock it?

I have noticed we have the same issue, easy fix !
I fixed it by following this simple guide -
* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).
* download the QUALCOMM driver(link in the YouTube video description).
* turn your phone off by pressing the power button and the + volume.
* when phone is turned off- press both volume buttons for 10 sec
* connect an original usb cable to your phone and to the 3.0 port on your pc.
* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)
* open msm tool and look if the device is recognized (COM4)
* if it is recognized change target to india and click start.
* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly
feel free to ask any questions, I know how frustrating it could be.
device used- one plus nord ac2003
ROM + MSM TOOL VERSION- avicii_14_I.13_210204

unbrickmee said:
I have noticed we have the same issue, easy fix !
I fixed it by following this simple guide -
* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).
* download the QUALCOMM driver(link in the YouTube video description).
* turn your phone off by pressing the power button and the + volume.
* when phone is turned off- press both volume buttons for 10 sec
* connect an original usb cable to your phone and to the 3.0 port on your pc.
* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)
* open msm tool and look if the device is recognized (COM4)
* if it is recognized change target to india and click start.
* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly
feel free to ask any questions, I know how frustrating it could be.
device used- one plus nord ac2003
ROM + MSM TOOL VERSION- avicii_14_I.13_210204
Click to expand...
Click to collapse
Thanks a lot for your answer!
I followed every of your steps, but I get the same result as I describe in the original post.
In MSMDownloadTool, in the "Status of Last Communication" column it says, in red:
"Device not match image".
Any idea how to fix this?

Try to reinstall correct drivers