Database Info

Disaster Recovery - Life after wrong Flash ? OnePlus

Hello all,
2 days ago when on vacation i decided to temper around with my OnePlus one that i recently bought (have bought the Chinese version but it was already rooted and had cyanoged mod on it)
All was fine until i decided to flash Paranoid Android and i posted a question here, about how to bypass the always apearing CyanogenMod Simple Recovery tool.
After trying what everyone suggested and not getting result i had 1 last thing that someone suggested:
http://forum.xda-developers.com/showthread.php?p=54717885
If you still have not fixed this issue, for some reason when I was flashing my recovery it would NOT work for the life of me until I changed the name of the custom recovery file to 'recovery.img'. Everytime I flash (for example) openrecovery-twrp-blah-bacon.img it would say success, but it kept rebooting into CM fastboot mode.
Click to expand...
Click to collapse
I misunderstood and i renamed the .zip file from paranoid sources into recovery.img and flash (Kernel) it via some app from play store, i thin it was TRWL
Now my phone is stuck into loading faze and the only thing i can do is enter Fastboot mode.
I tried to do a:
fastboot erase cache
But it did not work, its still stuck in loading and will not do anything.
Could you help me out ? I have a really bad feeling i just lost my phone due to hurrying and not having a pc around to read more.

You can try to fastboot flash recovery(original or proper one that works) but I don't know the exact commands.

In the first case where your recovery would not switch from CM to TWRP/CWR was because you had "Update CM Recovery" enabled in Developer Options. If you ticked that off, then it would have replaced CM Recovery. Its confusing yeah.
So wait... you renamed the .zip to a .img? Thats not good. But at least you can enter fastboot mode so thats at least something. Is your bootloader still unlocked? Are you able to boot into recovery mode? Try fastboot boot <name-of-recovery-for-twrp>.img and see if you can get into recovery.
If you can then perform a wipe and then enable adb sideload within TWRP and then type,
adb sideload <name-of-zip>.zip and then after its done sideloading, reboot

Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help

vidockq said:
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
Click to expand...
Click to collapse
I'd appreciate it if we helped give us a thanks.
Sent from my One using Tapatalk

black screen when booting into twrp

does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer

You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.

hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
Hey funny you should say that. I'm actually on my second Asus 3 ultra. The same thing happened to my first one got stuck during a firmware update, or corrupted firmware zip.,now the phone won't boot to twrp or bootloader, just vibrates like yours. If I plug the charging cord in vibrates then just get those red led notification light blinks,computer won't even recognize the device so can't flash the bootloader back to the phone to fix, so I guess it's hard bricked paperweight. I only had it for about a week before the brick, had to buy a new one. The thing that's funny to me the first one would boot to twrp no problem, now this new one seems to boot to twrp but just presented a black screen, it's in twrp recovery because you can feel the vibrations for the buttons, just can't see the screen. I would love to be able to fix the bricked one it's brand new, and can't send for warranty because I'm in the US, sucks.

If you have the address for the foreign country's location of manufacturing, you can send it in for repairs. That's what we are working on doing. The horrible thing is, after reading about stories of other customers, Asus really rakes you over the coals price wise for the repair, & then does similarly for return shipping. So we are still trying to find a way around the high shipping prices, at least.
.

gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
What stock keeping unit (SKU) is your phone? WW, TW, CN, or JP?
What version of TWRP did you flash?

hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG

qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
i think the mistake people may be making is flashing stock rom through twrp
twrp only for supersu zip and other things imo
stock rom just flash through the stock recovery apply update from sd (microsd card) need to make sure the recovery and rom match
can you get to stock recovery? also charge it first to a good 80 to 90 if not 100 percent

gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
After you get that black screen, just press once the power button to close and then press it again to open, just like you do when you normally close and open the screen. You will see after that the twrp interface.

qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
read your post again...noticed...
one thing-if you were on ww-14 i.e. android nougat then cannot simply flash the ww 13 marshmallow as I believe the bootloader is different - think that is why the flash did not work (know this from other zenfone forums where you cannot simply downgrade by flashing a previous android level rom) if it was not a case of downgrading then maybe because of using twrp for stock rom instead of the update process using stock recovery
I tried to flash ww 13 when on ww 14 through stock recovery and it was giving me an error (saying version is not ww which was not the case anyway)-found out through other forums that it is because one cannot downgrade in that manner - therefore I think cause of flash error is the bootloader version. For downgrading one needs the raw file. I found raw file for our ultra (WW13 level) at a Vietnamese site and the flashing tool but have not tried it (no reason to) but am keeping it just in case.
you can get stock recovery from here (note the ww 13 or ww 14 types pick the right one)
https://mega.nz/#F!9tEj2azZ!QKmvc-VJZR1Iqk6H7alQnQ
flash it through fastboot
need to have fastboot drivers installed
https://developer.android.com/studio/releases/platform-tools
or
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
make sure path variable has fastboot folder in it in environment variables of computer
preferably have recovery image in that folder too so you don't have to type some long path names
power off
volume up press and hold then press power
get to bootloader fastboot mode
connect by usb
open command prompt window in folder where fastboot installed
check fastboot devices to verify phone is seen
filename.img = filename of the twrp.img
twrp flash recovery filename.img
if successful then
twrp boot filename.img
may have to press power or volume up to get to the screen
while in stock recovery better to do factory reset too before update
then apply update from sd card
btw I have successfully used the twrp march version 3.2.1 (also at the above mega link) with the latest stock ww 14 (from jan 8 2018) backed up restored successfully, rooted, and have xposed as well
a note on twrp restore if ever having to (just don't check system image restore in twrp when restoring)
trying to do miui port

Can anyone help me???My device isn't opening after twrp flashing.when I reboot I see dark screen,not twrp recovery... please somebody help me,fast.....

Same problem with my iball tablet
Even flashing stock recovery doesn't give me recovery back i have also tried philz recovery but no luck i need help too

Wileyfox Spark X

Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !

@Asansi
I'm sorry I can't help you, but may I ask how you rooted the phone? I can't get mine to be properly rooted.

I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA

HackerAce said:
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
Click to expand...
Click to collapse
Apologies for ressurecring a zombie thread but, OP has a spark X and you have a Spark, so it would appear that you SENIOR person in that model failed at the very first hurdle.
Am still wonderng if there is an sign of a 7.0 compatible twrp for spark X? Don't suppose anyone has a link to the latest Spark X firmware either?

TWRP versions
Asansi said:
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
Click to expand...
Click to collapse
I've tried TWRP 3.0.2-0 (i.e. latest from https://dl.twrp.me/porridgek3/): it flashes Ok but it won't boot up afterwards. I've tried 3.0.2-0 but as you say "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. Have you progressed with this issue? BTW I've emailed TWRP Support (from their web page) asking if they have a working version.

Same problem here, It's pretty annoying. My sister's getting this same phone (on Android 6) soon so I might just make a full backup with TWRP on it and somehow restore it on my phone.

Systemless Root
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?

Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs

Systemless Root
ScreamingSteve said:
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Click to expand...
Click to collapse
Steve,
Have you tried the method detailed in post #7?

johnaaronrose said:
Steve,
Have you tried the method detailed in post #7?
Click to expand...
Click to collapse
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?

TWRP
ScreamingSteve said:
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
Click to expand...
Click to collapse
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.

johnaaronrose said:
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
Click to expand...
Click to collapse
Thanks a lot, I'll try your method, the explicit call to boot the TWRP image could really help.
Thanks for your extended explanation tho, showed me some new ways to eventually get this stuff to work.
Sent from my Wileyfox Spark X using XDA Labs

johnaaronrose said:
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Click to expand...
Click to collapse
Finally, your advice with "Fastboot boot twrp.img" worked magic!
Got twrp installed, but now I'm facing the same problem as you with the systemless root. I'll dig around a little and see what I can find.

Screen unlock doesn't work, blank boot screen and fastboot.

Hello!
I had recently gotten a Xiaomi Redmi Note 6 Pro brand new, and its been working fine for a while, but recently I ran into an issue: Namely, it often refuses to turn the screen on. The phone still makes sounds, it can receive calls, hell, it can even play music with no issue whatsoever, other than the fact that the screen itself appears dead. Once in a while the display turns on, and it works perfectly fine for as long as the screen is on, if I turn off automatic sleep, it can just run indefinitely like it usually would. When turning the phone off and back on, there are no boot animations, just a blank screen (sometimes they do appear, however rarely and I haven't noticed a pattern as to when they actually work as intended).
I figured it was an issue with MIUI 11, specifically 11.0.2.0, so I decided to flash a custom ROM. When attempting to enter fastboot mode, I am greeted by a blank screen, identical to the one that is present while booting up, but ADB recognizes the device just fine and I managed to unlock the bootloader despite no visual feedback from the device itself (I did manage to load into a fastboot mode with the Soviet android logo thing, but that was once, and it would revert back to being blank after 10 seconds). It had done a factory reset, and the problem persisted, it took me a good 5 minutes of spamming the power button for the screen to come back on, and the issue wasn't solved. I flashed official TWRP recovery on the unlocked device, and the ADB console reported the flashing as successful, however I have no way of accessing the bootloader or the recovery. (Not even the stock recovery would work, i tried that before I even touched the bootloader, it would just boot to system with a blank screen, and the phone would remain on, however largely unusable).
Now, I am a complete noob for these things, this is my first thread here, and I have no idea what could be causing the issue. Would flashing an older MIUI 10 stock ROM via MiFlash fix the issue? Or is this some sort of a hardware problem, although it doesn't seem that way as the phone was never dropped or exposed to the elements. I tried leaving it to completely discharge and then fully recharge, however that did precisely nothing. If you could look into this issue and help me find a solution, it would be greatly appreciated!
Thanks in advance!

Hey!
I think you should flash stock ROM from the Flash tool selecting clean_all_and_flash from fastboot mode

Nitin Rai said:
I think you should flash stock ROM from the Flash tool selecting clean_all_and_flash from fastboot mode
Click to expand...
Click to collapse
Hey, thanks a lot for replying!
That's what I thought I'd have to do, but I have a question: should I flash the MIUI 10 ROM or 11? Would downgrading it like that cause any issues? The only MIUI 11 ROM available on Xiaomi site is the OTA update that caused the issue. Also, in the meantime I managed to get into proper fastboot with ADB commands and flashed an AOSP extended Android 10 ROM, the issue is still there but I can now consistently get into TWRP either by an ADB terminal or by rebooting into recovery directly from the ROM with the power menu. I had downloaded an MIUI 10 recovery ROM from the Mi Community forums, can I flash that through TWRP or would it be safer to use MiFlash to flash the fastboot ROM? Do I have to flash the stock recovery before using the tool or will it just work with the TWRP already present on the device?

TacticalDisadvantage said:
Hey, thanks a lot for replying!
That's what I thought I'd have to do, but I have a question: should I flash the MIUI 10 ROM or 11? Would downgrading it like that cause any issues? The only MIUI 11 ROM available on Xiaomi site is the OTA update that caused the issue. Also, in the meantime I managed to get into proper fastboot with ADB commands and flashed an AOSP extended Android 10 ROM, the issue is still there but I can now consistently get into TWRP either by an ADB terminal or by rebooting into recovery directly from the ROM with the power menu. I had downloaded an MIUI 10 recovery ROM from the Mi Community forums, can I flash that through TWRP or would it be safer to use MiFlash to flash the fastboot ROM? Do I have to flash the stock recovery before using the tool or will it just work with the TWRP already present on the device?
Click to expand...
Click to collapse
No, I had downgraded from 11 before when I didn't had the miui 11 rom.zip I had miui 10 as backup. There is a thread for that anti rollback thing you can see that for more information. I would recommended you to go with the latest one if you are going to download or just flash the old one if you already have it
Here is the link for the anti rollback: https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219

Oneplus 6 QUALCOMM CrashDump Mode

My oneplus 6 after the latest android 11 update recently crashed it reboots automatically without entering to the OS and shows QUALCOMM DumpCrash Mode there are still some data i didn't backup yet. is there any way to back up my data
-usb debugging not turned on

Did you ever manage to boot after applying the update? Or did it go straight into crash dump mode?

agent_07 said:
My oneplus 6 after the latest android 11 update recently crashed it reboots automatically without entering to the OS and shows QUALCOMM DumpCrash Mode there are still some data i didn't backup yet. is there any way to back up my data
-usb debugging not turned on
Click to expand...
Click to collapse
Flash stock recovery first from Fastboot . And do not wipe anything. Just reinstall OOS and boot. That should help.
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As OnePlus doesn't always provide download links for all of for their Oxygen OS ROMs & OTA update zips, we mirrored them on AndroidFileHost and put the links in one post so that they're easy to find. This is not a support thread for issues you...
forum.xda-developers.com

facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though

MoresM said:
Did you ever manage to boot after applying the update? Or did it go straight into crash dump mode?
Click to expand...
Click to collapse
yes after update it was fine for a week

MITHUN7888 said:
facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though
Click to expand...
Click to collapse
if you found any was pls inform me

MITHUN7888 said:
facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though
Click to expand...
Click to collapse
If you flash old TWRP on Android 11 it will go to Crash Dump Mode. Suggest doing a clean install of Android 11 or use Nebrassy TWRP and reinstall OOS11. Other TWRP's have already been repacked to latest version to carter Android 11.

agent_07 said:
if you found any was pls inform me
Click to expand...
Click to collapse
i tried nearly 10-15 msm tools all were success but when booted up same message " Qualcomm crash dump mode" the thing is my bootloader was locked . i couldn't flash twrp or flash fastboot rom's to revive my phone...gave my device to oneplus authorized service center they said i need to get my motherboard replaced which costs 24,050 for 256gb variant.. currently i have asked them to replace the motherboard , as motherboard for my variant was not available i need to wait 10 more days to get it fixed .
UPDATE: if u have ur bootloader unlocked search for how to get out of qualcomm crash dump mode using fastboot roms.
if not look out for a local mobile repair center which does chip level repairs and ask them to reball ur phone ram and cpu, theres a 50/50 chance ur device might boot up.

mm_rajesh said:
If you flash old TWRP on Android 11 it will go to Crash Dump Mode. Suggest doing a clean install of Android 11 or use Nebrassy TWRP and reinstall OOS11. Other TWRP's have already been repacked to latest version to carter Android 11.
Click to expand...
Click to collapse
my device bootloader was locked , had no twrp installed , after updating to os11 directly went into crash dump mode .

MITHUN7888 said:
my device bootloader was locked , had no twrp installed , after updating to os11 directly went into crash dump mode .
Click to expand...
Click to collapse
I don't know who is that Mahaaan who said it's a Motherboard fault. Crash Dump Mode is an error while loading with the Firmware. This can be fixed with MSM tools. Try this step if you cannot fix with MSM tool.
Safe Mode Procedure :
Hold the Power Button Until Android Starts to Boot Up.
As Soon as Android Starts Booting Up, Let Go of the Power Button.
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons.
Continue Holding Both Volume Buttons Until Android is Fully Booted.
If successful, backup your phone, and do a full factory Erase All Data reset of Android.
See if that helps.

like many even i too ugraged my op6 to oo11.1.1.1, rooted was running well for a week till i encountred face crash dump mode error
Stupid thing i did was instead of flashing fastboot oos 10.3.8 i tried to flash msm 10.3.8 which didnt solve crash dum and also locked my BL.
now nonof the msm could solve crash dump nor we can unlock BL bz we cant toggle OEM in Dev option,
i discussed with @L0ND0NB0Y regarding this, his suggestion would be to take a backup of oos10.3.8 config partation of a working rom, then use edl to flash it on affected op6, by that way we can unlock bootloader and flash fastboot rom.
we need to fide a working op6 and back config which @L0ND0NB0Y can guide us. if it works he ll creat a post to solve crashbump and BL locked issue.
if this wont work, we may need to wait for msm oos11 file.
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.

How to resolve the issue . I got the same issue 1 week after SW upgrade . Nothing is fixing the issue

Jagadish-ravi said:
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.
Click to expand...
Click to collapse
exactly describes what I have encountered the last few days. MSMDownloadTool works fine for 5.1.5, 5.1.11, 9.0.8, 10.3.0 and 10.3.8 (10.3.0 and 10.3.8 with new driver, ends in crash dump where I startet). Currently no solution in sight?
I have the strong feeling this error is correlated with the update to android 11. Going back to a previous recovery.img might initiate the qualcomm crashdump mode error on boot.
Seems to be worth a try to restore android 11 via MSMDownloadTool. Did not find a file for that. Anyone?
Another way out of the horror seems to be getting get unlock ability to 1.
https://forum.xda-developers.com/t/...stuck-in-fastboot-mode.4135563/#post-83153239
Last case is to modify the devcfg binary and flip the lock bit and reflash through EDL
Click to expand...
Click to collapse
I've got no idea on how to do that. Anyone?

I've contacted OP support. They answered i should send the phone in for repair.
Currently I am issuing a repair order.

My oneplus went to crashdump mode on Oct 21st... Really shocked to see many users reporting this issue.. Tried to revive it using msm tool , but ended up with crashdump mode even after successful flashing

I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .

cpr437 said:
I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .
Click to expand...
Click to collapse
That is some terrible news. I thought I'd be able to keep safe from this nonsense by staying on 10.

even in bootloader unlocked state its same
I brought op6 motherboard which had OOS 11 running.
I tried to downgrade to oos10 via fast boot, gave crash dump.
flashing other versions fastboot rom gave same error again n again
can't boot twrp, stock recovery non works,
flashing recovery stock or twrp gave "no such partation error"
next I would try reballing ram my old MB try n see if it works.
or should wait for OOS11 MSM flash file.

Update: OnePlus charges 307,67€ for the repair of their own fault. Game over for the phone and OnePlus. We will both change the manufacturer.

cpr437 said:
I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .
Click to expand...
Click to collapse
Same here bro.. My phone was on stock android 10...