Database Info

stuck on boot logo

hi
at first i have to say my English is not good!!
i have a tf700 and last night i installed CROMBi-kk on it after that because of lots of apps that i installed in past it had lots of lag then i decided to wipe my data so i went to twrp and did a full wipe but in middle of that battery ran out. i install CROMBi-kk again but it stuck on boot logo!!!
i think there is no partition on it!!
UNFORTUNATELY I DON'T HAVE ANY BACKUP!!
PLZ HELP!!!!!
thank you!!

Need more information.
Which bootloader are you on?
Which kernel are you on?
Which kernel did you choose?
Internal install? rom2sd? data2sd?
Which options?
recovery.log?
aroma.log?

sbdags said:
Need more information.
Which bootloader are you on?
Click to expand...
Click to collapse
android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.10-20130801" a03
sbdags said:
Which kernel are you on?
Which kernel did you choose?
Click to expand...
Click to collapse
_that modded Asus OC Kernel v10
sbdags said:
Internal install? rom2sd? data2sd?
Click to expand...
Click to collapse
internal install
sbdags said:
Which options?
Click to expand...
Click to collapse
data journaling is enable
sbdags said:
recovery.log?
aroma.log?
Click to expand...
Click to collapse
E:could not mount /data and unable to find crypto footer
E: unable to mount ' /data '
E: unable to recreat /data/media folder.
Updating partition details. . .
E: unable to mount ' /data '
E: unable to mount internal 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: no valid storage partition found for MTP
E: unable to mount ' /data '
E: unable to mount ' /data '
in bootloader there is a line that say " key driver not found.. booting os
on detecting file system phase :
/data on internal (UDA) -> unknown

hoseinkh said:
android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.10-20130801" a03
_that modded Asus OC Kernel v10
internal install
data journaling is enable
E:could not mount /data and unable to find crypto footer
E: unable to mount ' /data '
E: unable to recreat /data/media folder.
Updating partition details. . .
E: unable to mount ' /data '
E: unable to mount internal 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: no valid storage partition found for MTP
E: unable to mount ' /data '
E: unable to mount ' /data '
in bootloader there is a line that say " key driver not found.. booting os
on detecting file system phase :
/data on internal (UDA) -> unknown
Click to expand...
Click to collapse
Ignore the key driver message - we all get it.
So you /data partition is not in a recognisable format and cannot be mounted. Please format it in TWRP or from adb use this command when in TWRP (make sure MTP is turned off)
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
or in the bootloader use this:
Code:
fastboot erase userdata

sbdags said:
Ignore the key driver message - we all get it.
So you /data partition is not in a recognisable format and cannot be mounted. Please format it in TWRP or from adb use this command when in TWRP (make sure MTP is turned off)
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
or in the bootloader use this:
Code:
fastboot erase userdata
Click to expand...
Click to collapse
Code:
C:\adb>fastboot erase userdata
^C
C:\adb>
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ killall -19 recovery
killall -19 recovery
killall: recovery: no process killed
1|[email protected]:/ $ make_ext4fs /dev/block/mmcblk0p8
make_ext4fs /dev/block/mmcblk0p8
Need size of filesystem
1|[email protected]:/ $ reboot
reboot
reboot: Operation not permitted
1|[email protected]:/ $
how to turn off mtp??
when i select format data from TWRP it stuck on " formatting data using make_ext4fs function" and even after 30 min nothing happen!!

thank you man!!
it's finally worked!!
Thank you for your attention and answers!!

hoseinkh said:
thank you man!!
it's finally worked!!
Thank you for your attention and answers!!
Click to expand...
Click to collapse
You are welcome!
Which one worked?

sbdags said:
You are welcome!
Which one worked?
Click to expand...
Click to collapse
Code:
fastboot earase userdata

erase data failed
I just get the following:
fastboot earase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
device is unlocked, hang in bootloop, tried flashing but:
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount /data/meida/TWRP/ . twrps when trying to read settings file.
E: No valid storage partitions found for MTP.
E: Unable to mount '/data'
E: Unable to mount '/data'
thanks for your answers.

homer56 said:
E: Unable to mount '/data'
Click to expand...
Click to collapse
In TWRP, go to wipe -> advanced -> format data. This can take more than an hour, so be patient.

I'm stuck in TWRP recovery mode. [Huawei y635-l03]

Hi for everyone! i need some help. I flashed my huawei y635 phone with a cm12.1 rom . the process was completed but when i reboot it enters to twrp recovery instead of load the system. the rom is ok because i proved before in the same phone.
I tried to swipe the cach, dalvik cache, data and reinstall the rom but didn't work.
this line appears when i install the cm12.1 rom:
... detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Symlinking
20%
40%
60%
Metadata
Preparing Install...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
mount: failed to mount /dev/block/bootdevice/by-namme/system at /system: Device or resource busy
script succeeded: result was [/system]
...updating partitions datails...
...done
I would be grateful for any help.

HELP - RECOVERY j7(6) MN EXYNOS

Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
E:failed to mount /data
Cannot mount /data and unable to find crypto footer.
E:failed to mount /cpefs
Click to expand...
Click to collapse
HELP ME!

natanjuniors said:
hi!
I have trouble when i put twrp and make wipe cache, system and dalvik. The phone gives me the following information:
Help me!
Click to expand...
Click to collapse
Format Data

natanjuniors said:
Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
HELP ME!
Click to expand...
Click to collapse
Format data and fully wipe

You just erase or deleted files on your internal memory. But no biggie, just flash firmware with Odin (on windows) heimdall (on Linux).
Sent from my SM-J700P using Tapatalk

natanjuniors said:
Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
HELP ME!
Click to expand...
Click to collapse
Format Data ... Yes ...

JHAM2005 said:
Format Data ... Yes ...
Click to expand...
Click to collapse
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz

Mrntnn said:
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz
Click to expand...
Click to collapse
Ignore the cpefs error, it's erroneous and will be fixed.
As long as you can mount data you are good.

Mrntnn said:
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz
Click to expand...
Click to collapse
How to ... Unlock Memory and have Root on the J710MN with Nougat 7
https://forum.xda-developers.com/ga...d-7-nougat-t3674417/post73826249#post73826249

hey i have solution
first 1. flash letest twrp
2.flash magisk 19.2
3. reboot system
100% done

Unable to install any Rom , /system: No such file or directory

So I tried to install LineageOS on my Honor 8. I unblocked the Bootloader and I am currently able to get into TWRP and Fastboot Mode. I did change the filesystem for the cache system and data as described in this video: w w w. youtube.com /watch?v=X7yDPszoQ5s to enable the encrypted folders.
When I try to install any ROM I am getting the following Errors in red:
E: unknown command (log)
Updater process ended with ERROR: 7
Error installing zip file 'romname'
Also:
Skipping MD5 check: no MD5 file found
could not detect filesystem for /dev/block/bootdevice/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
patching system image uncoditionally...
E1001: Failed to update system image.

Bootloader screen showing "Device is LOCKED" even though I've enabled OEM unlock in Android settings

Hi,
I've a Pixel (sailfish) that I'm trying to load TWRP and Magisk, and I'm unable to flash the recovery image as the bootloader page shows "Device is LOCKED", even though I've already enabled OEM unlock in Developer Settings. How do I unlock the bootloader?

goister said:
Hi,
I've a Pixel (sailfish) that I'm trying to load TWRP and Magisk, and I'm unable to flash the recovery image as the bootloader page shows "Device is LOCKED", even though I've already enabled OEM unlock in Developer Settings. How do I unlock the bootloader?
Click to expand...
Click to collapse
Enabling the OEM Unlock option is the first step but it doesn't unlock the phone. It merely enables unlocking the phone. You have to use a specific adb command to unlock the phone. Since the command varies with models and I am not familiar with your phone, please search for the correct command on Google.

Thanks. I'm following this page - https://www.xda-developers.com/how-to-install-twrp/
I managed to unlock it with fastboot, but I can't seem to flash the recovery. I downloaded the TWRP image from https://dl.twrp.me/sailfish/twrp-3.7.0_9-0-sailfish.img.html and renamed it to twrp.img. I then performed the following steps as per the instructions from xda above:
booted to bootloader with adb reboot bootloader
Temporarily booted to TWRP with fastboot boot twrp.img
Copied TWRP image file to device with adb push twrp.img /sdcard
Go to Advanced->Install Recovery Ramdisk, select twrp.img and swipe to install
I get the following error
Updating partition details...
Failed to mount '/system_root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
...done
Unpacking Boot...
Backing up Boot...
Unpacking /sdcard/twrp.img...
Repacking Boot...
/sbin/magiskboot decompress /tmp/repakorig/ramdisk.cpio /tmp/repackorig/ramdisk-1.cpio process ended with ERROR: 1
Error repacking image.
I tried to mount vendor partition, wipe and format the device and retry step 4 and made it a bit further (no more failed to mount '/system_root' and '/vendor' errors, as below, but still fails.
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done
Unpacking Boot...
Backing up Boot...
Unpacking /sdcard/twrp.img...
Repacking Boot... /sbin/magiskboot decompress /tmp/repakorig/ramdisk.cpio /tmp/repackorig/ramdisk-1.cpio process ended with ERROR: 1 Error repacking image.
Any suggestions?

goister said:
Go to Advanced->Install Recovery Ramdisk, select twrp.img and swipe to install
Click to expand...
Click to collapse
You can download both the .img and the .zip files. After booting using the .img file, instead of step 4 above, you can try Install from the booted TWRP and navigate to where the .zip file is and simply install it. That is what the TWRP page for Pixel recommends:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
Click to expand...
Click to collapse

Damn...why did the xda instructions say otherwise?

OK so I managed to reflash to stock image again after the boot loop, and then I followed the TWRP instructions. I was prompted to enter the device password when booting up to TWRP temporarily, and was able to get to TWRP once I entered my device PIN.
After I installed the zip file, I get the following screen:
Installing zip file '/sdcard/twrp.zip'
Updating partition details...
...done
Attempting to decrypt FBE for user 0...
User 0 Decrypted successfully
Data successfully decrypted
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/system root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Installing zip file '/sdcard/twrp.img'
Unmounting system...
########################################
# TWRP Installer for A/B devices #
########################################
Unpacking the installer...
Running image patcher on boot_a...
Running image patcher on boot_b...
Image patching complete!
Done installing TWRP!
*** NOTE: You are now unrooted! ***
Updating partition details...
Failed to mount '/system root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
...done
After this, it reboots to Android fine, but whenever I try to reboot to recovery, it goes to the white screen with the Google logo, then reboots to Android.
I'm using the latest TWRP for sailfish - twrp-installer-3.7.0_9-0-sailfish.zip.
Any ideas why?