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
Related
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.
Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
{
"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"
}
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.
gokhanc5 said:
Spoiler: didnt want to clog the thread with repeats of your pics
Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.
Click to expand...
Click to collapse
id reflash the stock firmware and re-root from there should you choose to do so
Youdoofus said:
id reflash the stock firmware and re-root from there should you choose to do so
Click to expand...
Click to collapse
thank you you answered. I'm uploading boot.img and recovery.img via fastboot. it does not give an error but comes to the same screen again. where am I doing wrong. Can you tell me exactly how to do it one by one.
@gokhanc5
As I can see your phone stucks in Fastboot ( AKA Bootloader ) mode: in Android device's boot-mode is set by ro.bootmode property - what can be normal, recovery or fastboot - which is set in Android's system file named build.prop.
Simply flashing some images as you did doesn't cause this property gets reset.
Typically you reset device's boot-mode property by means of ADB and/or Fastboot commands
ADB
Code:
adb devices
adb reboot
Fastboot
Code:
fastboot devices
fastboot reboot
jwoegerbauer said:
[USER = 11583799] @ gokhanc5 [/ USER]
Telefonunuzun Fastboot (AKA Bootloader) modunda takıldığını görebildiğim gibi: Android cihazının önyükleme modu, Android'in build.prop adlı sistem dosyasında ayarlanan ro.bootmode özelliği tarafından ayarlanır - normal, kurtarma veya fastboot olabilir .
Yaptığınız gibi bazı görüntüleri basitçe yanıp sönmek, bu özelliğin sıfırlanmasına neden olmaz.
Genellikle aygıtın önyükleme modu özelliğini ADB ve / veya Fastboot komutları aracılığıyla sıfırlarsınız.
ADB
[kod]
adb cihazları
adb yeniden başlatma
[/ kod]
Fastboot
[kod]
fastboot cihazları
fastboot yeniden başlatma
[/ kod]
Click to expand...
Click to collapse
OEM lock is on.
I'm installing recovery.img in fastboot mode.
fastboot flash recovery recovery.img
then when I turn it off and on again it comes to the fast boot mode screen.
I tried all the recovery.img files.
but it didn't happen.
Fast Boot Mode screen
Start - restart booting failed
Power Of
Recovery Mode - restart booting failed
Restart bootloader - restart booting failed
Can you describe how to do it from the very beginning?
gokhanc5 said:
...
Can you describe how to do it from the very beginning?
Click to expand...
Click to collapse
Already told you what to do.
jwoegerbauer said:
Sana ne yapacağını zaten söyledim.
Click to expand...
Click to collapse
I cannot enter anywhere except fastboot.
I cannot install TWRP.
fastboot devices
fastboot reboot
I'm doing these things, nothing changes.
i'm a beginner
sorry
jwoegerbauer said:
Already told you what to do.
Click to expand...
Click to collapse
I tried what they said
usb debugging is turned off
What will I change in the build.prop file.
What should I do for ro.bootmode?
I will be glad if you answer
I tried a lot but couldn't find a solution.
my hope is you
You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.
jwoegerbauer said:
You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.
Click to expand...
Click to collapse
thank you for everything.
but I could not.
-------------------------
fastboot oem unlock
(bootloader) Bootloader is already unlocked.
OKAY [0.008s]
finished. total time: 0.008s
-----------------------------------------
fastboot devices
3CQ3400QG9 fastboot
-----------------------------------------
fastboot flash bootloader Bootloader_phobos_4.4.2.img
target reported max download size of 641728512 bytes
sending 'bootloader' (7137 KB) ...
OKAY [0.266s]
writing 'bootloader' ...
FAILED (remote: (InvalidState))
finished. total time: 0.422s
-------------------------------------------------- ------
thank you for your help
@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.
jwoegerbauer said:
@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.
Click to expand...
Click to collapse
gave the same error again.
I downloaded it from 3 different places, the same error in all of them.
fastboot flash bootloader command fails
fastboot flash boot command works but the problem is the same
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.
Just got this phone today so I could boot lineage to it. Everything was running alright till I tried to boot into recovery mode. I flashed my image after I unlocked the phone officially and now it's just stuck at the stock Motorola Logo.
yarlio:[root]:/home/yerm/Documents/Moto G100# fastboot flash boot lineage-19.1-20220427-recovery-nio.img
Sending 'boot_b' (98304 KB) OKAY [ 3.076s]
Writing 'boot_b' OKAY [ 2.074s]
Finished. Total time: 5.190s
Click to expand...
Click to collapse
Worried about a optential hard brick here because I can't copy ensure all my firmware partitions are consistent
yarlio:[root]:/home/yerm/Documents/Moto G100# adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
Click to expand...
Click to collapse
It automatically writes to boot_b and I don't know if that'll be a issue
Here are all the files I have
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here is the site I used: https://lineageosroms.com/nio/ It doesn't come with twrp so I am just kinda stuck using a linux terminal and the bootloader
Did you Enable ADB in Advanced menu?
If yes, you probably didn't choose 2nd option in LineageOS recovery ...?
IntinteDAO said:
Did you Enable ADB in Advanced menu?
Click to expand...
Click to collapse
I am not getting in prompts to do so on the device. Just: Start, Barcodes, Bootloader Logs, Power Off, Recovery Mode, and restart bootloader. Going into recovery gives me nothing but the blue moto screen.
yerm said:
I am not getting in prompts to do so on the device. Just: Start, Barcodes, Bootloader Logs, Power Off, Recovery Mode, and restart bootloader. Going into recovery gives me nothing but the blue moto screen.
Click to expand...
Click to collapse
Try the newest version of Recovery
https://mirrorbits.lineageos.org/recovery/nio/20220604/lineage-19.1-20220604-recovery-nio.img
So, when doing this, the most important thing is having a way to revert to stock everything, far more so than backing up. This usually consists of a "fastboot ROM" of your stock software on the offchance something does tits up. Check development to see if one for your model number is available.
A issue I see immediately is you flashed the recovery using the flash boot command, when the instructions say temp boot using the boot command. Always stick to the instructions for that particular thing you're doing to the letter, otherwise you might get lucky or you'll get a weird oddity that is difficult to troubleshoot.
The instructions say to temp boot, use the copy partitions script to but it on both slots, and then install lineage. Given there is no mention of a recovery zip getting lineage recovery permanent is just done by flashing the ROM. So if you can I'd revert everything back to stock if that's a thing on this device, then do the steps again.
loulondono said:
So, when doing this, the most important thing is having a way to revert to stock everything, far more so than backing up. This usually consists of a "fastboot ROM" of your stock software on the offchance something does tits up. Check development to see if one for your model number is available.
A issue I see immediately is you flashed the recovery using the flash boot command, when the instructions say temp boot using the boot command. Always stick to the instructions for that particular thing you're doing to the letter, otherwise you might get lucky or you'll get a weird oddity that is difficult to troubleshoot.
The instructions say to temp boot, use the copy partitions script to but it on both slots, and then install lineage. Given there is no mention of a recovery zip getting lineage recovery permanent is just done by flashing the ROM. So if you can I'd revert everything back to stock if that's a thing on this device, then do the steps again.
Click to expand...
Click to collapse
I figured I went wrong somewhere, mostly because I ran into this when trying to copy partitions:
debord:[yerm]:~/Documents$ adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am now worried I beat my system to death and now I can't revert any of my changes. Do You have a terminal command list to sort this out how is it something i have ot get done from the bootloader on my phone?
Also the model is a "XT2125-4" Which is a supported device according to this tutorial.
yerm said:
I figured I went wrong somewhere, mostly because I ran into this when trying to copy partitions:
debord:[yerm]:~/Documents$ adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am now worried I beat my system to death and now I can't revert any of my changes. Do You have a terminal command list to sort this out how is it something i have ot get done from the bootloader on my phone?
Also the model is a "XT2125-4" Which is a supported device according to this tutorial.
Click to expand...
Click to collapse
Are you trying to sideload whilst in bootloader ( start, barcodes ect) or have you gotten into recovery?
loulondono said:
Are you trying to sideload whilst in bootloader ( start, barcodes ect) or have you gotten into recovery?
Click to expand...
Click to collapse
I am only able to jump between boot-loader and this powered by android Motorola screen. The only two places I can go
yerm said:
I am only able to jump between boot-loader and this powered by android Motorola screen. The only two places I can go
Click to expand...
Click to collapse
Yh sideload only works when booted into recovery, and having selected sideload ( seems to be renamed to apply update on lineage recovery) so that's a bust. You need to get into recovery. Any luck on finding a way to revert to stock? If not I would try the boot .IMG command from the instructions and see if that gets you into the recovery
loulondono said:
Yh sideload only works when booted into recovery, and having selected sideload ( seems to be renamed to apply update on lineage recovery) so that's a bust. You need to get into recovery. Any luck on finding a way to revert to stock? If not I would try the boot .IMG command from the instructions and see if that gets you into the recovery
Click to expand...
Click to collapse
No Luck, also getting this now:
debord:[yerm]:~/Documents$ fastboot flash boot lineage-19.1-20220427-nightly-nio-signed.zip
< waiting for any device >
Sending 'boot_a' (771805 KB) OKAY [ 20.216s]
Writing 'boot_a' (bootloader) Image size exceeds partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
And I had to change my device I was using to flash LineageOS. My PC kept hard crashing but that's a different issue
Start from installing recovery. Go to bootloader mode, download newest version of fastboot (31) and:
fastboot flash boot lineage-19.1-20220604-recovery-nio.img
IntinteDAO said:
Start from installing recovery. Go to bootloader mode, download newest version of fastboot (31) and:
fastboot flash boot lineage-19.1-20220604-recovery-nio.img
Click to expand...
Click to collapse
Still getting this error when I try to sideload
adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
Click to expand...
Click to collapse
I think boot_a and boot_b Might be occupied. (First attempt did b the first few times second kept flashing to a)
yerm said:
Still getting this error when I try to sideload
Click to expand...
Click to collapse
I understand that you were able to get LineageOS Recovery working?
IntinteDAO said:
I understand that you were able to get LineageOS Recovery working?
Click to expand...
Click to collapse
The img installs then I am still stuck in the Motorola powered by android when I try to get into recovery mode or restart the phone. I can only get into the standard android bootloader
To do a sideload, you must have LineageOS Recovery. I understand that your system loads over and over again?
IntinteDAO said:
To do a sideload, you must have LineageOS Recovery. I understand that your system loads over and over again?
Click to expand...
Click to collapse
Yeah It just gets stuck at the screen on recovery
yerm said:
Yeah It just gets stuck at the screen on recovery
Click to expand...
Click to collapse
When flashing recovery, does fastboot display any errors?
IntinteDAO said:
When flashing recovery, does fastboot display any errors?
Click to expand...
Click to collapse
It's been flashing fine when just flashing to boot_a
fastboot set_active a
<run recovery>
Is that works?
Hello comrades!
I heve some problem with my oneplus 8t. after latest update it cant boot with error:
"The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it."
Fastboot flash reovery normal, but if i try to reboot recovery it returns me back to fastboot.
If i tying o flash system via fastboot, it stops with error: partition not found.
MSM tool gives me "Param preload failed" error now it gives me "Shara Comunication failed"
(i use original oneplus cabel, usb 2.0 port, latest qalcomm drivers and follow this guide: https://community.oneplus.com/thread?id=1541327)
-------------------
MSM log: log.txt
photo of boot error: photo1.jpg
-P.S-
My english is not good, but i still lerning
qwerty960 said:
Hello comrades!
I heve some problem with my oneplus 8t. after latest update it cant boot with error:
"The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it."
Fastboot flash reovery normal, but if i try to reboot recovery it returns me back to fastboot.
If i tying o flash system via fastboot, it stops with error: partition not found.
MSM tool gives me "Param preload failed" error
(i use original oneplus cabel, usb 2.0 port, latest qalcomm drivers and follow this guide: https://community.oneplus.com/thread?id=1541327)
-------------------
MSM log: log.txt
photo of boot error: photo1.jpg
-P.S-
My english is not good, but i still lerning
Click to expand...
Click to collapse
Have a look at https://forum.xda-developers.com/t/the-current-image-boot-recovery-have-been-destroyed.4420821/
BillGoss said:
Have a look at https://forum.xda-developers.com/t/the-current-image-boot-recovery-have-been-destroyed.4420821/
Click to expand...
Click to collapse
Thank you, but it doesn't work for me.
When i trying to flash abl, aop, bluetooth e.t.c. with --slot=all it gives me: "fastboot: error: Could not check if partition bluetooth has slot all" error.
When i trying to flash it without --slot=all it gives me:
Sending 'PARTITION' (652 KB) OKAY [ 0.031s]
Writing 'PARTITION' FAILED (remote: 'Flashing is not allowed for Critical Partitions.')
fastboot: error: Command failed
---------------
I follow this guide: https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
qwerty960 said:
Hello comrades!
I heve some problem with my oneplus 8t. after latest update it cant boot with error:
"The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it."
Fastboot flash reovery normal, but if i try to reboot recovery it returns me back to fastboot.
If i tying o flash system via fastboot, it stops with error: partition not found.
MSM tool gives me "Param preload failed" error
(i use original oneplus cabel, usb 2.0 port, latest qalcomm drivers and follow this guide: https://community.oneplus.com/thread?id=1541327)
-------------------
MSM log: log.txt
photo of boot error: photo1.jpg
-P.S-
My english is not good, but i still lerning
Click to expand...
Click to collapse
Use paid service from online from mobile repair shop. They will fix your device remotely with nominal charges.
mvikrant97 said:
Use paid service from online from mobile repair shop. They will fix your device remotely with nominal charges.
Click to expand...
Click to collapse
It's good, but:
1) I ave no money
2)Servie support type to me "Hello, this is not possible remotely.only bring for diagnostics"
Now(and 5 more days) i can't go to service
qwerty960 said:
It's good, but:
1) I ave no money
2)Servie support type to me "Hello, this is not possible remotely.only bring for diagnostics"
Now(and 5 more days) i can't go to service
Click to expand...
Click to collapse
Oh I'm very sorry to hear that. I will try to find a working solution for you.
Other members will also come to rescue.
Keep hopes!
qwerty960 said:
Thank you, but it doesn't work for me.
When i trying to flash abl, aop, bluetooth e.t.c. with --slot=all it gives me: "fastboot: error: Could not check if partition bluetooth has slot all" error.
When i trying to flash it without --slot=all it gives me:
Sending 'PARTITION' (652 KB) OKAY [ 0.031s]
Writing 'PARTITION' FAILED (remote: 'Flashing is not allowed for Critical Partitions.')
fastboot: error: Command failed
---------------
I follow this guide: https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
That happens when you run the commands in bootloader instead of fastbootd (the 'd' isn't a typo!).
The guide you used does a fastboot reboot fastboot on the fourth command. If you skip that you get the errors you mentioned.
BillGoss said:
That happens when you run the commands in bootloader instead of fastbootd (the 'd' isn't a typo!).
The guide you used does a fastboot reboot fastboot on the fourth command. If you skip that you get the errors you mentioned.
Click to expand...
Click to collapse
I have some problems with this comands
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
and all solutions I found not working for me
Have you tried switching slots?
You can find the current slot using fastboot getvar current-slot
and change slots using fastboot --set-active=<other slot>, where <other slot> is b or a depending on your current slot (a or b).
Changing slots might let you get into fastbootd.
Otherwise, you'll have to use MSM to reset your phone. I've attached my personal notes on using MSM which might give you some ideas.
BillGoss said:
Have you tried switching slots?
You can find the current slot using fastboot getvar current-slot
and change slots using fastboot --set-active=<other slot>, where <other slot> is b or a depending on your current slot (a or b).
Changing slots might let you get into fastbootd.
Otherwise, you'll have to use MSM to reset your phone. I've attached my personal notes on using MSM which might give you some ideas.
Click to expand...
Click to collapse
Funy. Almost at the same time as your suggestion, I did the same thing via fastboot enhance.
Now I'm waiting for flashing payload.bin
Flashing via fastboot enhance was failed, phone reboot into EDL mod and I successfuly flash it via MSM.
Now I will write full unbrick guide for people like me.
UNBRICK GUIDE:
1)To fix "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it.", you may unsuccessful flash phone via MSM tool (to boot phone to edl mode, useadb reboot edl, if it not working: switch off your devie, hold volume up & down keys and insert usb cable. now you have 10 sec. to start MSM tool). MSM tool will crash(it is normal)
2)Now in fastboot menu check that secure boot is disabled, if it's not, switch correct slot
via fastboot fastboot --set-active=<a/b>, where <a/b> is b or a depending on your current slot (a or b).
Or via fastboot enhance just push "change slot" button.
3.1)falsh image via fastboot follow this guide: "https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/".
Or flash payload.bin using Fastboot enhance.
3.2)If device can't boot system, reboot it to edl, now you can successful flash it via MSM tool.
Spoiler: LINKS
Fastboot Enhane: "https://github.com/libxzr/FastbootEnhance/releases"
Spoiler: Qualcomm Drivers:
Spoiler: For Automatic and Direct Method:
32-bit version: QDLoader_HS-USB_Driver_32bit_Setup.exe
64-bit version: QDLoader_HS-USB_Driver_64bit_Setup.exe
Spoiler: For Manual Method:
Qualcomm-Driver.zip
Spoiler: MSM for OP8t:
Indian firmware (KB05DA) | kebab_15_I.12_200918.zip
Global firmware (KB05AA ) | kebab_15_O.12_200918.zip
Global firmware (KB05AA ) | kebab_15_O.12_200918.zip
T-Mobile (KB09CB ) | kebabt_15_O.01_200924.zip
----------------------------------------------------------------------------------------------------------------------------
Special thanks to:
BillGoss (Senior Member)