Develop Bugs

[Q] [Help] Loading CyanogenMod onto Nexus 7 2013 (WiFi) (flo)

Hello,
I am trying to load CyanogenMod onto my Nexus 7 2013 (WiFi) via this guide: wiki.cyanogenmod[.]org/w/Install_CM_for_flo
I have successfully flashed the recovery partition (ClockWork Mod 6.0.4.7). However, when I boot into CWM, I am greeted with these errors:
Code:
E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (no such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (no such file or directory)
I attempted to load CyanogenMod via the "push and install method", which entails mounting the /data partition. CWM errored out when trying to mount any of the following partitions:
Code:
Error mounting /system!
Error mounting /data!
Error mounting /cache!
So instead, I tried the sideloading method ("adb sideload nightly.zip"), and CWM spit back a bunch of mounting/filesystem errors:
Code:
Restarting adbd...
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed; no such volume
Patching system unconditionally...
failed to open /dev/block/platform/msm_sdcc.1/by-name/system: No such file or directory
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Can anybody help me out with this? Thanks!

Update:
I just tried TWRP (2.8.6.0) as an alternative to Clockwork Mod. FYI, my device is currently running stock Android 5.1 Lollipop, if that makes a difference.
I received the following errors:
Code:
E:Unable to find partition size for /boot.
E:Unable to find partition size for /recovery.
E:Unable to find partition size for /misc.
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data/' is not present!
E:Unable to mount /data.
E:Unable to find partition size for /sb11.
More similar mounting issues. Any idea what the problem could be?
Is TWRP 2.8.6.0 not compatible with Android 5.1? (Build: LMY47O)

Resolved -- Use TWRP MultiRom
I had the same issue on a number of new Nexus 7 2013 wifi devices. Turns out Google had made some firmware updates, rendering new N7 devices incompatible with KitKat stock images.
I resolved it by flashing a custom TWRP build (the MultiRom build) onto these devices. Here's the download links that someone uploaded. You need to be familiar with using fastboot on nexus 7 devices in order to flash these onto the recovery partition:
WIFI (FLO) https://drive.google.com/file/d/0B3fHxCdm5V_Mc2szNnFzT1I0eVk/view
LTE (DEB) https://drive.google.com/file/d/0B3fHxCdm5V_MU1hfXzV6dFlEZ2c/view
As a refresher, after booting into fastboot mode (hold VolDn+Power), type 'fastboot flash recovery TWRP_multirom_flo_20150328.img'
(Thanks to csmnn for posting the original solution here: https://www.reddit.com/r/cyanogenmo...ng_cyanogenmod_onto_nexus_7_2013_wifi/cscxb93 and to masterchiefb117 for uploading the files in this forum post: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562)

Errr... This the Galaxy Nexus forums, not Nexus 7.
Sent from my Nexus 5 using Tapatalk

[NEED HELP] TWRP wiping + flashing ERROR, Bootloop

hello,
does someone know what problem i have and how i should fix this?
first of all, when i was wiping my phone it all went fine but it took to long so i turned off my phone and turned it back on, i got in an boot loop and couldnt even get into recovery mode because that would also led me into a ''teamwin'' bootloop, anyway i reflashed my recovery so luckily i can get back into recovery, but i still have bootloop for the system so i cant start up, but now i also face this problem.
i wanted to flash stock rom and this is the full error log i get ( i also tryed with custom rom but same problem)
_____________________________________________________________________________________________
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I also tryed wiping my phone, i tryed advanced wipe and full wipe and also factory reset, but i always get this same kinda error.
anyone know a fix for this?

Which version of twrp do you use?

i use Twrp 2.8.7.3

Try the last one : https://dl.twrp.me/Z00A/twrp-3.0.0-0-Z00A.img.html
Your zenfone 2 is WW or CN?

its CN

sorry for the kinda late answer tho,
well i wanted to flash the 3.0 twrp version, but it gives me an weird kind of bootloop, so thats why i downgraded to 2.8.7 :/

that's strange, are you sure it was for Z00A?
Look at this : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 to change to WW version.

FIRE TV 2 BOOT LOOPS,Thanks for telling me the details of the repair steps

my model is FIRE TV 2, it boot loops (amzon logo
then will eventually display this twrp screen
and Runing OpenRconveryScript screen then will
loop).
OpenRconveryScript screen:
failed to mount '/data'(Invalid argument)
Unable to recreate /data/media folder.
Updating parititon details...
Failed to mount '/data'(Invalid argument)
...done
Unable to mount storage
full SELinux support is present.
Running boot script...
Done.
Unable to mount /data/media/TWRP/.twrps
Runing Recovery Commands
Failed to mount '/data'(Invalid argument)
Formatting Cache using make_ext4fs...
Failed to mount '/data'(Invalid argument)
Done processing script file
Online wait for guidance

maleclub said:
my model is FIRE TV 2, it boot loops (amzon logo
then will eventually display this twrp screen
and Runing OpenRconveryScript screen then will
loop).
OpenRconveryScript screen:
failed to mount '/data'(Invalid argument)
Unable to recreate /data/media folder.
Updating parititon details...
Failed to mount '/data'(Invalid argument)
...done
Unable to mount storage
full SELinux support is present.
Running boot script...
Done.
Unable to mount /data/media/TWRP/.twrps
Runing Recovery Commands
Failed to mount '/data'(Invalid argument)
Formatting Cache using make_ext4fs...
Failed to mount '/data'(Invalid argument)
Done processing script file
Online wait for guidance
Click to expand...
Click to collapse
Can you pop in a USB flash drive or micro sd with a pre rooted ROM and flash?

Update to TRWP 3.4.0-0 failed - factory reset?

TWRP won't start after updating from 3.3.. to 3.4.0-0 using fastboot. Output includes "Failed to mount '/data'" - see following post.
I guess because I accidentally ran fastboot unlock although it was already unlocked. (The TWRP website fastboot update procedure starts right back with installing the tools and I jumped in at the wrong place)
Tried installing previous TWRP version but no dice.
Any ideas?
I did a TWRP backup before all this. Not exactly sure where it's located but would like to recover it if possible. Will a factory reset likely overwrite it?
Lenovo P2 LineageOS 17.1 Kuntao

Output when booting to recovery:
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...
Unable to mount storage
Failed to mount '/data' (Invalid argument)
fs_mgr_mount_all
Full SELimux support is present.
Unable to mount /data/media/TWRP/.twrps
Running recovery commands
Failed to mount '/data' (Invalid argument)
Formatting cache using mke2fs...
Done.
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.

Realme 6 pro Broken Encrypt

My realme 6 pro is broken, it does not allow me to install anything through twrp, or flash the stock roms, I tried using a different twrp and the error still persists, the operating system was deleted, so I cannot turn on the phone, it was trying to install a new custom rom, but no longer possible
The following is the copy of the twrp record, without having performed any action
E:Unable to decrypt FBE device
Updating partition details...
...done
Updating partition details...
...done
**********************************
PicthBlack Recovery: Welcome! ^_^
Maintained By PBRP Team
**********************************
Encryption Status : unencrypted
MTP Enabled
Failed to mount ´/system_root´(Invalid argument)
Failed to mount ´/vendor´(Invalid argument)
Update partition details...
Failed to mount ´/system_root´ (Invalid argument)
Failed to mount ´/vendor´(Invalid argument)
...done
Failed to mount ´/system_root´(Invalid argument)
Failed to mount ´/vendor´(Invalid argument)
E:Unable to open ´/system_root/
Full SELinux support is present
ps: i'm kinda new and i really have no idea how to fix this please someone help me
Attached pictures of the device status

Which recovery Better Between TWRP or PBRP?