I tried installing the pixel experience rom and after I flashed the aex recovery before side loading the ROM, it went into bootloop and ended up with the stock recovery and ROM. I tried to flash TWRP recovery and go a message that the the boot/recovery image is destroyed so I tried to flash the stock boot image back and since then I am not able to get it out of fastboot mode.
I tried everything, flashing the recovery again, both stock and TWRP and also tried using the flash-all to flash the stock ROM back but nothing seems to be working.
When using the flash-all, I get 'partitions not found' and 'flashing is not allowed in critical partitions' error.
I even tried msmtool but I am not able to get my phone into edl mode for the tool to detect it.
Tried holding the vol+/vol- and connecting the usb cable but to no vain, the tool does not seem to detect it.
I even tried using the all-in-one tool but my phone is not getting detected when it is turned off but it gets detected when it's in flashboot mode from where I cannot enter edl.
Let me know if there is anything I can do to fix it? Or if taking the phone to the official service center help?
Can you reboot from fastboot to edl by entering fastboot reboot-edl? Or similar, don't know exactly anymore
Alternatively see if this can help you getting into edl: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/
Related
Hello,
I was trying to change file system type to f2fs. For that, i wiped everything in my phone lenovo A6000plus. Then i got out of recovery without flashing another rom.
So now my phone is stuck on logo screen. I connected it to pc but adb doesn't detect the device as there is no rom currently. I tried all the key combinations to go to recovery but it didn't work. However, fastboot detects the device but i can't seem to boot into bootloader using fastboot command. It appears as if somehow i deleted the bootloader. Also i couldn't find a way to boot into recovery from fastboot. I also tried flashing zips and images from fastboot to system partition but it didn't work.
Please help.
My note 6 pro suddenly started doing boot loop. I tried to revive it by flashing stock firmware but nothing seems to help. It has unlocked bootloader, with TWRP installed. This is what I tried:
Put phone in fastboot mode, I do see the fastboot image.
Computer recognizes the phone. 'fastboot devices' shows correct device.
Using MI Flash tool to flash 10.3.6 global fastboot image. It takes about 160 seconds to flash all the partitions. The phone will reboot at the the end of the flash. Flash tool doesn't say "successful" though. Its status is still "flashing".
No other errors. When the phone restarts, it is still stuck in the boot loop. Interesting thing is, if I press volume + button and power button, I see TWRP flash for a quick second on the screen then boot again. Looks like the recovery image wasn't flashed properly.
Looked at the logs. Nothing strange. Also tried to run 'flash-all.bat' in a command line (not sure if we are supposed to do that), but all the fastboot flash commands look OK.
Anything else I can do to revive this phone?
Good morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
jwoegerbauer said:
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
Click to expand...
Click to collapse
I see.
What can I do to try to fix this issue?
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.
A while ago i installed Lineage OS onto my OP7Pro without issue. I am now trying to go back to the stock OP OS.
I seem to have completely wiped the storage and now I just get "Qualcomm Crashdump Mode dm-verity device corrupted force dump kernal_restart".
I installed twrp on my PC and managed to boot the phone into twrp, I then pushed the twrp-installer.zip to the phone using adb, and then using the phone installed the zip, however when the phone reboots it just goes straight back to the Qualcomm Crashdump screen.
I have tried:
fastboot boot twrp.img (sucessfully boots phone into twrp)
adb sideload twrp-installer-3.5.2_9-0-guacamole.zip (adb confirmed sucessfull but then I can not find the file on the phone)
adb push twrp-installer-3.5.2_9-0-guacamole.zip /sdcard/ (when I go the install on twrp the file is there and I can install it)
But after reboot it's just straight back to Qualcomm Crashdump.
I tried msm and that didn't work, it would not detect the device.
Can anyone please help??
Try:
fastboot --set-active=other
Then fastboot boot TWRP.img
Install any ROM.zip or stockOOS.zip reboot to fastboot, boot TWRP and flash magisk.
If that doesn't work try again with msmtool, remember press both volume buttons for 5 seconds and connect USB cable(still pressing volume buttons) and your device should be detected
IthinkIfckedmyphone said:
A while ago i installed Lineage OS onto my OP7Pro without issue. I am now trying to go back to the stock OP OS.
I seem to have completely wiped the storage and now I just get "Qualcomm Crashdump Mode dm-verity device corrupted force dump kernal_restart".
I installed twrp on my PC and managed to boot the phone into twrp, I then pushed the twrp-installer.zip to the phone using adb, and then using the phone installed the zip, however when the phone reboots it just goes straight back to the Qualcomm Crashdump screen.
I have tried:
fastboot boot twrp.img (sucessfully boots phone into twrp)
adb sideload twrp-installer-3.5.2_9-0-guacamole.zip (adb confirmed sucessfull but then I can not find the file on the phone)
adb push twrp-installer-3.5.2_9-0-guacamole.zip /sdcard/ (when I go the install on twrp the file is there and I can install it)
But after reboot it's just straight back to Qualcomm Crashdump.
I tried msm and that didn't work, it would not detect the device.
Can anyone please help??
Click to expand...
Click to collapse
have you tried the 3.4 mauronofrio TWRP? maybe if you can get it to boot use it to flash oos 10.3.8 then update to 11 after
Hi guys,
I think I've tried it all at this point so I'm in need of some help.
I've got the T-Mobile IN2017 version of the OP8. I wanted to get rid of the T-Mobile junk and get access to the "regular" updates.
I started with this guide: [Guide] Convert to Global [WIP]
I got my unlock token today and gave 11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA_0300_all_2010031624_c5e68b42b3325-FASTBOOT a shot. When it booted into Rescue Mode I assumed something had gone wrong so I told it to wipe everything and I figured I'd start over. I realized this was probably a good thing because I had neglected to backup anything.
I used instantnoodlet_15_O.16_201001 to reset. I couldn't get the volume up + volume down combination to work at all so used adb to reboot in edl. All went well.
I then re-unlocked the bootloader, flash booted into twrp-3.3.1-test10-instantnoodle-unified-mauronofrio.img and made some backups.
I installed the latest Magisk (changing .apk to .zip) within TWRP, and used adb shell to make a backup of my persist.img
I went back to 11.0.0-GLOBAL-OnePlus8Oxygen_15.O.30_OTA_0300_all_2010031624_c5e68b42b3325-FASTBOOT and ran the flash-all.bat but this time it failed and I've found myself bricked: CrashDump Mode.
I've only been able to switch betwen CrashDump Mode, off, and Fastboot. When I'm in Fastboot if I try to start or boot in recovery it just ends up back at CrashDump. If I do a hard power off and try holding volume up + down to get into edl I end up at Fastboot again as soon as I plug the usb in. The commands fastboot reboot edl, fastboot oem edl, and fastboot reboot-edl all give me errors. I can no longer flash boot into TWRP. I've tried flashing the 11.0.0 Global again but I get "Flashing is not allowed for critical partitions" and "partition not found" errors before I end up back at the CrashDump screen.
When in CrashDump it shows up in my device manager as Qualcomm HS-USB Diagnostics 900E (COM13). When I'm in fastboot it appears as OnePlus Android Bootloader Interace. I have uninstalled the drivers and reinstalled the drivers (OnePlus_USB_Drivers_Setup, QDLoader HS-USB Driver_64Bit, androidwinusb). I'm using the latest Platform Tools. I am in test mode and I have turned off driver signature.
I only have two USB 3.0 ports and I don't have access to another Windows PC. I have used three different USB cables, including the OnePlus original, in both ports. I have taken off my phone case to make sure nothing is interfering with me pushing volume up + down. My thumb hurts from pressing it so much. I've done this dozens of times now. No EDL.
I'm at a loss. Someone please help me!
Edit: I've tried using the All-In-One-Tool but it says reboot to EDL doesn't work because I'm in fastboot and trying to boot into the latest twrp still just sends me back to CrashDump.
Solved!
I came across this twrp guide: [TWRP][3.6.0-11-b7][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA] and unlike the other I had used, this one didn't warn against flashing and only booting. I flashed the img for twrp-op8-3.6.0_11-infected-b4 to recovery_a and recovery_b and booted into recovery. At first it just said I was in fastboot, it didn't give me all the usual twrp options, and the only buttons were to reboot and to switch between fastboot and adb (which did nothing, it stayed in fastboot). I tried to reboot to edl and ended up back at the fastboot screen. From here I tried again to boot into recovery and this time I got all the usual twrp options. I rebooted into edl and was able to successfully unbrick with the 10.5.7 MSM. Flashed the global 10.5.7 MSM and I'm set. Updated to A11 and everything is groovy!