I already unrooted and setup custom os on a couple of Motorola G7 play phones. But on this one, I thought I would try a different way to install twrp permanently.
which was to boot into twrp, then "install recovery ramdisk" pointing it to the recovery.img that I know works correctly with this phone.
I got these messages....
I:Switching slots to flash ramdisk to both partitions
I:Setting active slot B
Updating partition details...
Iata backup size is 867MB, free: 14022MB.
I:checking for twrp app
I:Can't probe device /dev/block/bootdevice/by-name/vendor_b
Failed to mount '/vendor' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/vendor_b', current file system: 'ext4'
I:Can't probe device /dev/block/bootdevice/by-name/modem_b
Failed to mount '/firmware' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/modem_b', current file system: 'ext4'
I:Can't probe device /dev/block/bootdevice/by-name/dsp_b
Failed to mount '/dsp' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/dsp_b', current file system: 'ext4'
...done
Backing up Boot...
I:Reading '/dev/block/bootdevice/by-name/boot_b', writing '/tmp/repackorig//boot.emmc.win'
I:Restored default metadata for /tmp/repackorig//boot.emmc.win
I:Error unpacking /tmp/repackorig/boot.img, ret: 256!
Error unpacking image.
I:Set page: 'action_complete'
Iperation_end - status=1
At this point, I realized I didn't previously flash dtbo.img. I suspected if I reboot I would brick the phone. I decided to reboot to bootloader anyway. because to start flashing over the top of this seemed like a bad idea.
Which I in fact bricked the phone.
What should I have done at this point? Gone ahead and flashed dtbo from the PC while in twrp? flashed a copy of the boot.img (from my PC?). before I rebooted?
I actually have found NO info on why I am reflashing dtbo, or whats in these modified dtbo's, or how to tell I need to flash the dtbo. Or if it's even correct "before" commiting to unpacking/repacking the boot image.
And there are multiple links to different modified dtbo's and different instructions sometimes leave out no-verity-opt-encrypt.zip For the record I didn't do this no verity step on the last couple phones and worked fine.
What is the procedure to fix the boot before I reboot out of twrp. And how do I know I have a good copy of a modified dtbo
How can I tell I have (or not) already flashed dtbo?
So since this phone seems to have borked Slot B. Can I unbrick it somehow by going to Slot A? It does not respond to anymore to VolumeDown-Power button so it really bricked for good or not?
Sorry for all the questions, but I think this would save a ton of people wrecking phones.
Related
I have the MTK version of the RN3
I can't flash any roms using TWRP, I always get the following error:
Updater Process ended with ERROR: 7
Error installing zip file [rom file path here]
Updating partition details...
Failed to mount '/oem' (Invalid argument)
...done
I get the same 'Failed to mount '/oem' (Invalid argument) line when I try to factory reset/format the phone.
The formatting still (maybe partially) goes through though, which now results in me having no OS installed and not being able to install one.
Can someone help?
bump
For anyone wondering, this seems to always work when nothing else does anymore:
http://en.miui.com/thread-193681-1-1.html
Hello All,
I have a problem where TWRP is not able to mount /data, although the device still works without any other problems. It has happened when i upgrade the TWRP recovery from 3.2.1-0 to 3.2.1-1
This is preventing me to install Magis modules unfortunately.
I have a OOS Open BETA 1 for the Oneplus 5T.
Here's the log:
Code:
[COLOR="Red"]Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (No such device)
Unable to recreate /data/media folder.[/COLOR]
Updating partition details...
[COLOR="red"]Failed to mount '/data' (No such device)
Failed to mount '/preload' (Invalid argument)[/COLOR]
...done
Full SELinux support is present.
I have an issue when I build TWRP for my Huawei P10 Lite using minimal TWRP manifest..I get this:
E: failed to mount /data (Invalid argument)
failed to mount /system (valid argument)
etc...
And I get this for every partition declared in the fstab and I tried to change it with different layouts like FS before names or after etc.. I tried with the stock Huawei fstab from the recovery, same problem.
The device tree can be found here:
https://github.com/maxhartung/android_device_huawei_hi6250
If you take a look at the commits you can see the differents formats I tried.
They are a few TWRP made for P10 Lite but I want to do it myself and also add decryption support but this issue is blocking me to do it so.
After I did a factory data reset in TWRP, every thing looks normal but when I boot the OS and do the first boot setup
and then go back to TWRP the problem appears again.
How do I fix it?
Thanks in advance.
SPECS:
OS: lineage OS 8.1 official.
Phone: Redmi Note 4 snapdragon.
I have the same problem. Did you find a solution yet?
Everytime I try to wipe cache/dalvik I get
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
.
.
.
.
I'm using
twrp-3.2.3-0-mido.img
Found this on github:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1265
Hello
I've installed TWRP by following this thread here
and after which I flashed the custom rom from this thread here
After a awhile I did a factory rest to the phone which caused the phone to boot into TWRP and no matter what I do it keeps rebooting into TWRP
Tired to flash stock rom, which gives the following erros :
unable to mount storage
Failed to mount '/data' (invalid argument)
unable to mount '/data/media/TWRP/.twrps
tried Format Data:
unable to mount storage
Failed to mount '/data' (invalid argument)
unable to format to remove encryption
tried to repair data:
Failed to mount '/data' (invalid argument)
Failed to unmount 'external_sd' (Device or resource busy)
unable to repair data
tried to flash the custom rom again
....
...done!
enjoy!
updating partition details
Failed to mount '/data' (invalid argument)
....done
tried using terminal with this:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
no such file
Dont have ADB access (only sd card shows when i connect usb)
note: I have another vernee M5 if anyone thinks it could be useful (unrooted)
please help!
Saqwerzaman said:
Hello
I've installed TWRP by following this thread here
and after which I flashed the custom rom from this thread here
After a awhile I did a factory rest to the phone which caused the phone to boot into TWRP and no matter what I do it keeps rebooting into TWRP
Tired to flash stock rom, which gives the following erros :
unable to mount storage
Failed to mount '/data' (invalid argument)
unable to mount '/data/media/TWRP/.twrps
tried Format Data:
unable to mount storage
Failed to mount '/data' (invalid argument)
unable to format to remove encryption
tried to repair data:
Failed to mount '/data' (invalid argument)
Failed to unmount 'external_sd' (Device or resource busy)
unable to repair data
tried to flash the custom rom again
....
...done!
enjoy!
updating partition details
Failed to mount '/data' (invalid argument)
....done
tried using terminal with this:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
no such file
Dont have ADB access (only sd card shows when i connect usb)
note: I have another vernee M5 if anyone thinks it could be useful (unrooted)
please help!
Click to expand...
Click to collapse
UPDATE
booting into bootloader and using command 'f'astboot continue'' i was able to boot into system
the system reqiuers a password but gboard keeps crashing and i cant enter my password