Is it possible for fastboot to get corrupted somehow? Tried on 2 different computers, same problem. Oneplus 3T gets recognized no problem with the fastboot devices command.
You should be able to hold the power + volume down buttons while powering on to boot into recovery mode. Hard to imagine a corrupted boot.img would break that functionality.Is it possible for fastboot to get corrupted somehow? Tried on 2 different computers, same problem. Oneplus 3T gets recognized no problem with the fastboot devices command.
You should be able to hold the power + volume down buttons while powering on to boot into recovery mode. Hard to imagine a corrupted boot.img would break that functionality.
It looks like power + volume down actually sends you to (most likely) fastboot, where they expect you to select recovery from there. Try power + volume up, or last option all 3 buttons. Obviously ensure you're holding them the entire time, from before the device powers off until it's fully on.Yeah, unfortunately it goes right into fastboot. Selecting the recovery option in fastboot also brings it right back into fastboot.
It looks like power + volume down actually sends you to (most likely) fastboot, where they expect you to select recovery from there. Try power + volume up, or last option all 3 buttons. Obviously ensure you're holding them the entire time, from before the device powers off until it's fully on.
If OP7 doesn't have the hardware buttons available to enter recovery directly, that's indeed a huge oversight.
In the meantime keep scouring online for people with fastboot connecting to pc issues - there might be a solution out there.
Don't use Minimal ADB, it might be using outdated binaries of platform-tools.C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
< waiting for any device >
Flash stock boot.imgAfter flashing the January update (QPMS30.80-63-6-8-5) to my Moto G Power XT2041-4 (sofia), Magisk v22.0 patched boot.img from this update causes bootloop showing the blue Android logo indefinitely. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allow phone to boot successfully.
The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from Magisk v21.4 to v22.0 using direct install in the Magisk app successfully last month.
I suspect there may be some changes in the updated boot.img that conflict with the changes Magisk makes when patching the boot.img.
Any thoughts???
I did and now twrp doesnt mount slot a or b..Flash stock boot.img
------------------------------------Experienced a similar issue with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img causes bootloop. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allows phone to boot normally but, of course, without root.
The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from v21.4 to v22.0 using the Magisk app direct install while on this update.
I suspect there may be some changes in the new boot.img that conflict with the changes Magisk makes when patching it.
Any thoughts???
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the Magisk log, said unknown image type and that it failed, rebooted phone, phone will now only reboot into fastboot mode. Not the quality I've been accustomed to and certainly does not belong in the stable branch. Now can someone please tell me what I should do to fix this hot mess?
Edit: Fixed boot with backup boot image. Included log of attempted but allegedly failed update.
Same thing on my OP7,
I can't go to recovery mode, only fastboot, and the phone isn't detected when i type 'adb devices'
Is there any way to get my data back?
- Target image: /dev/block/sde1
- Device platform: arm64-v8a
- Installing: 22.0 (22000)
Parsing boot image: [/dev/block/sde1
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
you needSame thing on my OP7,
I can't go to recovery mode, only fastboot, and the phone isn't detected when i type 'adb devices'
Is there any way to get my data back?