Related
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
do you have fastboot on your device???
can u enter fast boot by key combination vol down and power???
if yes then just install twrp recovery or stock recovery with following command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
flash cm 13, beanstock,tipsy or RR rom if you use twrp
flash stock firmware if you use stock recovery
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Contact support.... you're the first one with a bricked device....
And it would be great if you could share the support e-mail.... it would help me get unbrick files for this device
---------- Post added at 22:17 ---------- Previous post was at 22:16 ----------
i.snehal.kiran said:
do you have fastboot on your device???
can u enter fast boot by key combination vol down and power???
if yes then just install twrp recovery or stock recovery with following command
flash cm 13, beanstock,tipsy or RR rom if you use twrp
flash stock firmware if you use stock recovery
Click to expand...
Click to collapse
Fastboot on op2 is already a mess and we don't have enough info of what could happen in op3... best avoid fastboot except for flashing twrp
Flash the stock ROM through twrp
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Your oneplus bricked itself?
are you sure there wasn't a human involved in the process?
As other people says, you're the first one with a " bricked" device, so please tell everyone what your device status is, and how it got bricked.
did you unlock bootloader, did you have root? as much info as possible..
anupritaisno1 said:
Contact support.... you're the first one with a bricked device....
And it would be great if you could share the support e-mail.... it would help me get unbrick files for this device
---------- Post added at 22:17 ---------- Previous post was at 22:16 ----------
Fastboot on op2 is already a mess and we don't have enough info of what could happen in op3... best avoid fastboot except for flashing twrp
Flash the stock ROM through twrp
Click to expand...
Click to collapse
I already have the link for that file. Someone shared. But, what next ?
Sent from my OnePlus2 using XDA Labs
anupritaisno1 said:
Fastboot on op2 is already a mess...
Click to expand...
Click to collapse
Why a mess?
Fastboot itself is very simple.
fastboot flash <<partition you need to flash>> <<file patch>>.
Is it different from the "common" fastboot we can find on a Nexus?
When I try to do this I get the following message:
target reported max download size of 536870912 bytes
sending 'recovery' (18677 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.590s
Any way I can force this to happen?
Thanks in advance
CyberCROC said:
When I try to do this I get the following message:
target reported max download size of 536870912 bytes
sending 'recovery' (18677 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.590s
Any way I can force this to happen?
Thanks in advance
Click to expand...
Click to collapse
You did 'fastboot oem unlock' first, correct?
I tried yes but that results in the following:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
CyberCROC said:
I tried yes but that results in the following:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
Click to expand...
Click to collapse
And have you enabled OEM Unlocking in Developer Options ?
BTW Please reply to my PM ASAP if possible.
Thanks.
Best Regards,
Naman.
I can't OEM unlock in developer options as I no longer have access to my device
PM answered
Experiencing the same problem here.
I had the same in other thread. OEM unock was disabled. Do You have working stock recovery or TWRP? If stock works You can flash stock rom by ADB sideload.
My bootloader is locked so it's showing FAILED (remote: Partition flashing is not allowed) and cannot get into recovery.
cepheid46e2 said:
My bootloader is locked so it's showing FAILED (remote: Partition flashing is not allowed) and cannot get into recovery.
Click to expand...
Click to collapse
I am experiencing the same problem right now. Cannot boot into recovery mode or flash something...stuck in fastboot mode. .
Any ideas?
I have the same problem too
sino84 said:
I am experiencing the same problem right now. Cannot boot into recovery mode or flash something...stuck in fastboot mode. .
Any ideas?
Click to expand...
Click to collapse
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
x___treme said:
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
Click to expand...
Click to collapse
try this:
http://www.androidbrick.com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008/
you need the OnePlus3_Unbrick_Tool_Full.rar to unbrick your phone, i was also in your situation,
you need also the Qualcomm_Diag_QD_Loader_2016_driver.exe with this two tools you can flash to restore the OP3
me helped al lot this thread http://forum.xda-developers.com/onep...icked-t3405700
a had a success with this part How to Make the device show as Qualcomm 9008
it is important that you have the correct driver installed on your pc that the phone will be recognized as Qualcomm 9008
I did the exact same stupid thing... locked bootloader before flashing stock recovery.
This post saved me:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I used method 2 in the post which wiped everything but at least i got the phone back.
x___treme said:
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
Click to expand...
Click to collapse
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Since im a new member I cannot post links so ill have to give you directions.
Search google for Hard Bricked OnePlus 3 and it will be the first one called Mega Unbrick guide.
Use method 2. Ive used it multiple times when flashing goes wrong on my oneplus 3.
Another step, download the latest stock recovery from OnePlus and name it recovery.img and replace the one in the folder. You should understand more when you have all of the files.
You can download the latest recovery from OP at the bottom of the page linked here:
Google OnePlus 3 beta download and it should be the first one saying community build.
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem
amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?
Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here
Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk
tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Update: solved. I had to run the command window and admin and it flashed just fine. Thanks spotmark!
superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
Download whatever build you're on and extract the boot image. Then fastboot flash the boot image.
superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
Try flashing Magisk again in TWRP.
spotmark said:
Download whatever build you're on and extract the boot image. Then fastboot flash the boot image.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash boot bl.img
Sending 'boot_a' (8489 KB) OKAY [ 0.310s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
FAILED (remote: '(boot_a) No such partition')
Finished. Total time: 0.564s
thats what it doesn when i try to flash boot image
superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
.
Plz read line #1 on post #1 for twrp . . . ( hint ) it'll tell you that the twrp team has "not" yet got adb sideload working. . We all have to be patient !
.
And the good News is . . . if you use the usb-C adapter in the box and plug in a usb-A thumb drive into the pixel when running twrp . . . . you can see and grab stuff off that thumb drive. . . . . it worked for me 1
superbean83 said:
Code:
c:\adb>fastboot flash boot bl.img
Sending 'boot_a' (8489 KB) OKAY [ 0.310s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
FAILED (remote: '(boot_a) No such partition')
Finished. Total time: 0.564s
thats what it doesn when i try to flash boot image
Click to expand...
Click to collapse
You need to flash the boot.img not the bootloader.
superbean83 said:
thats what it doesn when i try to flash boot image
Click to expand...
Click to collapse
Fastboot flash boot --slot all boot.img
airmaxx23 said:
You need to flash the boot.img not the bootloader.
Click to expand...
Click to collapse
Do you have the latest sdk platform tools?
Sent from my [device_name] using XDA-Developers Legacy app
I am new to flashing custom roms, and I got lineage running but I wanted to try Evo X, when I tried flashing through lineage Recovery it booted back into lineage, ok, so I erased all datat through lineage recovery and installed TWRP. I got that on but within a few clicks of messing around I found myself with no recovery or OS and im only stuck in fastboot, I have no idea how to get out of it. mods take this post down if posted in the wrong community. I just though this would be the best place to post it. I am new to XDA, I have these ADB logs from the command I was trying to run
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot boot C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools\TWRP-3.5.1-lemonadep-Nebrassy-2.img
Sending 'boot.img' (196608 KB) OKAY [ 4.500s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
I have no idea why it keep failing, I would greatly appreciate any help to get my phone working again.
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
oddlyspaced said:
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
Click to expand...
Click to collapse
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
Click to expand...
Click to collapse
I guess you should try msm tool then
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
RazOne said:
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
Click to expand...
Click to collapse
I have gotten msm tool and my firmware, but nothing is showing up in msm when my device is connected
ive linked a screenshot of what my msm tool looks like, im just so desperate to get my phone back
Power off phone, position mouse cursor o er start button on msm tool, hold down vol up and down simultaneously, plug phone into computer wait a quick second and press start. That should work.
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
Click to expand...
Click to collapse
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
I LITERALLY CANNOT THANK YOU ENOUGH, YOU ARE LIKE THE DAD I NEVER HAD.
Lol, i'm not that old found the answer myself in a forum after 2 days of being stuck in fastboot.
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
hello guys i am facing that same issue but my own show slot_b and then i try to use your step but still not work help me plizzz
Googled the error you have. Check this post (and following ones)
[SOLVED] - Bootloop with completely new OPO9pro after oem unlock
Hello, just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup) Enabled developer options, OEM unlocking and USB debugging. After update, 1*reboot. then another reboot to bootloader, and executed...
forum.xda-developers.com
I think you should start over and use "fastboot flashing unlock" instead of fastboot oem unlock.
Follow the link in that thread. Droidwin has the best tutorials for oneplus you'll find. Never had this error myself, so can't say for sure what to do.
Redmi note 8 (unlocked bootloader) stuck on "Your system has been destroyed" (I was trying to install PixelExperience 12, but was not able to boot into the PitchBlack recovery itself). Unable to boot to recovery or fastboot (no button combination is working).
If connected via USB (while just charging too), it just keeps rebooting & shows "Your system has been destroyed".
When disconnected from external power supply, it shuts down automatically after a few seconds, but when I try to boot into the bootloader (or try to turn it on), it again goes to the system destroyed screen.
Here are the set of commands I ran just after unlocking the bootloader:
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.404s]
Writing 'recovery' OKAY [ 0.385s]
Finished. Total time: 1.824s
PS D:\Android\ADB> ./fastboot boot ginkgo_recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 1.391s]
Booting OKAY [ 0.148s]
Finished. Total time: 1.591s
PS D:\Android\ADB> ./fastboot devices
97900a40 fastboot
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.414s]
Writing 'recovery' OKAY [ 0.381s]
Finished. Total time: 1.808s
PS D:\Android\ADB> ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.003s
PS D:\Android\ADB> ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PS D:\Android\ADB> ./fastboot devices
PS D:\Android\ADB> ./fastboot devices
What I believe is that I forgot to disable vbeta verification before flashing the new recovery (when I tried flashing a new recovery in my POCO, I got an error regarding this, but this time none of that happened). Is there any way to do it now? without having to go into EDL mode & stuff?
Rocker_2102 said:
Is there any way to do it now? without having to go into EDL mode & stuff?
Click to expand...
Click to collapse
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
loopypalm said:
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
Click to expand...
Click to collapse
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Rocker_2102 said:
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Click to expand...
Click to collapse
did you try the comand while "system destroyed" is displayed ?
No.. but I tried connecting using adb and it did not work. I think I event tried "fastboot devices" which too didn't show anything .
But I'll try again now to confirm this.
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Rocker_2102 said:
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Click to expand...
Click to collapse
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
loopypalm said:
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
Click to expand...
Click to collapse
It wasn't my phone so just bringing it back to working condition is pretty awesome for me . On my phone I keep trying new ROMS (just tried Projet Elixir)
bro how did you booted into fastboot i also in same situation
how did you fixed i also in same situation
Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
same here, it's not booting to fastboot even tho I tried the combination when "Your system has been destroyed" was displayed ;-;
Rocker_2102 said:
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Click to expand...
Click to collapse
I got it to working condition this way only, unfortunately.