Database Info

[Q] Bricked Photon Q - boots into recovery

I think I've just successfully bricked my Photon Q.
Right now I'm stuck with Clockwork recovery (v 6.0.1.3) and my system backed up.
I've tried to install CM12 (cm-12-20150330-NIGHTLY-xt897) but it gives me an error :
Code:
Installing update...
Warning: No file_contextsThis package is for device: xt897asanti_c; this device is asanti.
E: Error in sdcard 0 update zip (Status 7)
Installation aborted.
When trying to recover my system from backup it gives me :
Code:
E: format_volume: make_extf4fs failed on dev block platform msm_sdcc.1 by-name system
Error while formatting system!
Right now I'd like to install ANY CM that would actually work. Please help!

Flash the correct recovery.
Use the one in this: http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-0-photon-q-t3034552
or this thread: http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781

Moto G Rom Flashing not Working

I was having some problems with the older rom on my Moto G, so I thought it would be a good idea for a new one. I am trying to flash the Tesla-falcon-6.0.1.Shock_Therapy.v1.0-test-20160125-1532 rom aand have also tried its 5.1.1 variant. Each time I tried to flash, I got this error.
Code:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Invalid argument
unmount of /data failed; no such volume
Patching system image unconditionally...
Verifying the updated system image...
Verified the updated system image.
Flashing SuperSU...
unmount of /system failed; no such volume
script succeeded: result was [ ]
Install from adb complete
EDIT: I also tried flashing this rom: http://forum.xda-developers.com/moto-g/development/stable-aosp-caf-t3284323 of 6.0.1 lollipop and this is what my recovery told me:
Code:
Finding update package...
Opening update package...
Installing update...
Target: motorola/aosp_falcon/falcon:6.0.1/MMB29M/16:userdebug/test-keys
Patching system image unconsitionally...
Verifying the updated system image...
Verified the updated system image.
script succeeded: result was [0.200000]
Install from ABD complete.
And this time it works. Now that there is a proper image of 6.0.1 running on the device, I'm going to try to flash the tesla rom again and see what happens.
My question is, what can I do to fix this?

check the update-script from that rom or feedback to developers.

[Q] Error on installing Magisk 16.4.zip

I tried to flash Magisk 16.4.zip on micromax a102 using TWRP custom recovery and got an error saying (unable to unpack boot image). I have Resurrection remix 5.8.5 Nougat(7.1.2) custom rom installed and 3.1.1 twrp. Can anybody help me how I can fix this problem?
SEE THIS ERROR LOG FOR MORE INFO----
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/bootimg
- Device platform: arm
- Constructing environment
- Adding addon.d survival script
- unpacking boot image
! Unable to unpack boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file 'external_sd/Download/Magisk-v16.4.zip'
Updating partitions details. . .
. . .done

TWRP unable to wipe or format `Failed to mount '/system' (Device or resource busy)`

I'm trying to install LineageOS and then GAPPS on my Pixel XL from TWRP recovery. I'll try to `Advance Wipe` the `/systems` directory and `Format Data`, but I continue to get multiple errors:
Code:
Failed to mount '/system' (Device or resource busy)
Code:
Failed to mount '/vendor' (Device or resource busy)
And
Code:
Unable to wipe 'System'
Code:
Unable to wipe '/system'
If I just continue with `adb sideload lineageos.zip` most of the time it stops about halfway (PowerShell shows `47%`) through and then TWRP shell shows:
Code:
Installing zip file '/sideload/package.zip'
Step 1/2
Step 2/2
I then try to `sideload` the `gapps.zip` file and get another error saying `/system` doesn't have enough space. I've tried sideloading several different gapps versions including their smallest `pico` zip fie of `91.39 MiB`.
I am able to then boot into LineageOS, but no GAPPS show and I'm not able to run any new apps installed via APK without them crashing.
My assumption is that I need to fully wipe `system` and format it, but I've been trying for two days now and still get the above `(Device or resource busy)` errors. Any help would be much appreciated!

Make sure you have the latest tools.
Latest TWRP for marlin is 3.3.0-0
Latest platform-tools is 29.0.1

Not sure what's the cause of this, but if you want to wipe and start fresh I think the best option is reflash the stock factory image that completely wipes everything and restores everything stock.
Then, you can retry wiping the device using the latest TWRP (currently, marlin is 3.3.1-0, the zip is 3.3.0-0, try just boot it and don't flash the zip), flash LOS and then gapps.
Also, as pointed by @post-mortem, make sure you are using the latest adb version when flashing the factory image, just to avoid any potential issue.

Don't use 3.3.1-0. Try 3.3.0-0. I had the same issue.

Why doesn't TWRP Team provide an answer as to why this happens? It appears to affect everyone with the latest official Pixel ROM.

Twrp is for Android pie and has trouble mounting stock Android 10. They have announced this on their website. This shouldn't matter since you're installing lineage. You don't need to wipe system before installing lineage because it installs into the inactive slot. You need to sideload lineage then reboot into recovery to switch slot's. The instructions are on the lineage website.

Did OP manage to solve this issue?

Can't boot Android or recovery mode

I have a Samsung Galaxy Note 10.1 GT-N8010. One day it suddenly stopped booting Android and wouldn't pass the first screen (it didn't even reach the one with only the Samsung logo, only the one that says "Samsung GALAXY Note 10.1"). I booted into recovery mode and tried to factory reset, but I got this error: "E:failed to mount /efs (invalid argument)." So I followed this guide: https://forum.xda-developers.com/t/how-to-fix-e-failed-to-mount-efs-invalid-argument.2858056/
Here is where the problem begins. When I rooted to remove the factory mode (just following the guide), I did it using CF-Auto Root. But then my tablet stopped booting to Android (again, not passing the first screen), and when I try to boot into recovery mode, the CF-Auto Root screen boots instead (even after flashing stock firmware and TWRP). On this screen, it says the following:
CF-Auto-Root
Copyright (C) 2011-2016 Chainfire
Detecting devices . . .
- Recovery: /dev/block/mmcblk0p6
- System: /dev/block/mmcblk0p9
- Cache: /dev/block/mmcblk0p8
Preparing cache . . .
Mounting . . .
- System
- Cache
Rooting (SuperSU) . . .
Restoring stock recovery . . .
Cleaning up . . .
Rebooting in 10 seconds . . .
Then nothing happens. It still doesn't boot into Android, and if I try to access recovery mode, I get to the same CF-Auto Root screen. I can only access Download Mode, but I don't know what to flash to solve the problem. As I said, I tried flashing the stock firmware and TWRP (when I did that, Odin said PASS!).
I have been using Odin 3.10 and flashing this firmware https://sfirmware.com/es/samsung-gt-n8010/ (ARO). I also tried with a firmware downloaded through Frija (probably the same one).
I think that's everything. If I missed any information, please let me know.
Any help is welcome!
Thanks,
Whilz.

Good afternoon. I cannot guarantee that this will help you, as I have not encountered this problem and have not used these instructions. But maybe this will help you.
I found these instructions on the russian forum of the platform our devices are built on (n80**, i9300, etc.)
I will give the translation in this post and links to the original posts.
Spoiler: E:failed to mount /efs (Invalid argument) and how to deal with it!
Original post: https://4pda.to/forum/index.php?showtopic=514244&st=0#entry26179020
According to the instructions, you need to flash I9300_Repair_efs.tar.zip efs image via Odin3. IMEI and S/N will be lost, so you will have to think about restoring it.
Spoiler: Error "E: unable to mount /efs (Invalid argument)" or "failed to mount /efs..."
Original: https://4pda.to/forum/index.php?showtopic=514244&st=0#entry24433995
Attention! This method will not raise IMEI and S / N without efs backup. If you do not have it, then you can only download your phone, but there will be no network.
Tested on SGS III​
1. If you currently do not have root rights, then download them from the link from the topic header, the version for installation via Odin, install.
2. Download Custom recovery. Also versions for Odin (.tar.md5), install.
3. Download AROMA Filemanager
4. Install the File Manager through the recovery as a normal update.
5. Run the built-in terminal File Manager (press menu / select "open console" or "terminal" from the list).
6. We write commands (after each enter - input):
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
reboot
The commands are taken here - http://forum.xda-developers.com/showthread.php?t=1896470
7. Reboot into the system (reboot system now).
8. We read the instructions for restoring efs (who did what) and restore.
If during loading we see a translucent pop-up window with yellow inscriptions on the desktop
then we decide like this - Club of Samsung Galaxy S III lovers (Post # 16738476)
Spoiler: Problem Solution: failed to mount /... (Invalid argument)
Original: https://4pda.to/forum/index.php?showtopic=343514&st=8900#entry38837011
There's quite a lot of information here that I'm not moving here. Perhaps you can learn something for yourself by translating the page into the right language.