That's expected. Devices with A/B partition scheme don't have a recovery partition. You can only boot in recovery mode with fastboot boot twrp.img. But to permanently flash recovery to device which can be booted into by proper key combination, you need to unpack both of your boot.imgs (A/B) from device and replace the ramdisk with the one extracted from twrp....
1) You can boot into TWRP recovery from fastboot
fastboot boot twrp.img
2) Then you can backup your whole emmc from adb
adb pull /dev/block/mmcblk0
Does /dev/block/mmcblk0 include my internal storage, my app data, contacts, sms, wifi passwords, bluetooth pairings, system settings etc? Have you personally tried that method on an encrypted device?
There are different versions of fastboot.exe available.
One old version I have has the command line option -c as
-c <cmdline> override kernel commandline
The recent versions for Android SDK (v29.0.5-5949299) does not has the -c option. Instead it has the option --cmdline which seem to the the exactly same thing:
--cmdline CMDLINE ...
/dev/mmcblk0 is whole MMC storage chip which includes GUID partition table (GPT) and all partitions. On Android devices some of these eMMC partitions hold bootloaders (like sbl, aboot on Qualcomm devices) which have hard-coded paths in SoC firmware. Fully overwriting (erasing) such partitions means the SoC won't be able to boot device. Since fastboot and ...
it's too late for this post, but I'm answering for anyone else finding this post
refer to this link http://www.gandalfk7.it/2019/03/24/fastboot-too-old-and-error-cannot-generate-image-for-userdata/
you must update your os platform tools and execute sh flash-all.sh after updating the platform set the PATH in your directory as this reference says
do these ...
This question is nearly a duplicate of this which has a detailed answer by @Firelord, except the Termux part. As mention by @DeathMaskSalesman in comment, Termux is more like a Linux environment, but so far it doesn't have adb and fastboot in repositories, though proposed. Most probably because they are meant for rooted devices. But you can use static ...
Full credit to alecxs for this answer. Posting incase anybody else has the same problem in the future.
Download stock image(Mine was oneplus.com/uk/support/softwareupgrade/details?code=9)
Use extract_android_ota_payload-master to split the payload.bin inside the zip
(Method for step 2 https://pastebin.com/RfEHuvu7 , I did this on linux because my linux ...
You probably meant fastboot mode.
And no, Magisk cannot be flashed using Fastboot mode. It is a zip file and not an image file that you can just flash to a partition. If you want to use fastboot, you should consider patching your boot image using Magisk Manager and then boot that image using fastboot boot command.
fastboot boot magisk-patched.img
Or if ...
The command shouldn't have any spaces. The correct command will be:
Or if you want to write it in short:
fastboot -aa to set the active slot to A.
fastboot -ab to set the active slot to B.
G7 Power, being a new device, has the new A/B partition layout, requiring new installation procedures that differ from standard A-only devices. This is clearly outlined in the thread where you got your image from:
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. ...
I was in a similar issue on a Nokia running a stock ROM. Basically Magisk module killed my phone and the TWRP won't allow decryption.
I was able to boot successfully to system again by.. Removing Magisk, because in the absence of Magisk, the Magisk modules shouldn't load and hence the system should boot just fine. I did that by flashing my stock boot image....
SuperSU is discontinued and shouldn't work as expected on new versions of Android. You should consider using Magisk.
Flash the zip the same way you did for SuperSU. Then remember to launch magisk app and do the necessary additional installation steps.
i have experienced this with two other Xiaomi devices. first i could track it down to older unofficial variant of twrp 3.2.3 which is still decrypting with default password when official twrp 3.3.1 fails. so implementation of decrypting differs from each build, sometimes it is just a missing line in fstab, sometimes they forgot a flag during build.
But this ...
Firstly the main Android OS (what you call "boot mode") and recovery are two independent operating systems. When one is running, other is not. Running processes are different, environment is different, loaded properties are different and so on.
Recovery has its own default.prop file in ramdisk from which it reads properties. In order to permanently change ...
You can try to boot directly into recovery instead of flashing image: fastboot boot recovery.img
If it doesn't work, go for flashing factory firmware in bootloader or Emergency Download mode. Here are the detailed instructions for Xiaomi devices.
Some phone needs to be plugged to light before it can boot to recovery mode/hard reset. Try putting the plugged charger in the phone when it's switched off and immediately it shows the charging signal press the volume down⬇key+power key, if that doesn't work try volume up⬆key+power key.
The both work for my phone innjoo i2s.
adb and fastboot are different modes. you can enter recovery without usb debugging. Press and hold Power + Vol Down. This is the bootloader screen. Now navigate to recovery with Vol Keys, Power to confirm. Wait a Moment. When the android symbol appears, press Vol Up + Power to enter recovery. Now do Factory reset.
If device is locked you may not be able ...
So you mentioned that
is a command that works for you, but you didn't mention whether or not you saw any output from your device. While I don't have a lot of experience with MediaTek processors, I'm aware that most of them share the same set of drivers and as a result, you should be able to download the appropriate "universal" USB drivers ...
I guess the problem is related to cache partition. you can try to fix it with
fastboot format:ext4 cache
or from twrp recovery with
adb shell twrp wipe cache
also formatting the cache partition will help
adb shell mke2fs -t ext4 /dev/block/mmcblk0p27
You can manually backup your data (sdcard) partition. if data is encrypted, mount it with
The twrp.img you trying to boot from is for Moto G7 (river). It is the wrong recovery, thats why it fails.
Unfortunately there is no TWRP available for your device Moto G7 Power (ocean). But you have options.
You can root your phone with Magisk.
You can port TWRP for your device.
unpack your ...
fastboot works, adb doesn't?
my ans: you can use image loader which is compatible with that device,erase all the previous data and freshly build new Meta data by including the partitioning,after success u might get expected output like flatten success(related to build of that device).then adb will work fine with usb port detection.
hopes this works!