I had LinegeOS installed on my xperia. But don't have root. I wanted to install root addon, but didn't have TWRP because previous time I just temporary boot with
fastboot boot twrp.img
Now I do the same fastboot boot twrp.img
and flash the root addon. I got this error Failed to mount /data invalid argument but also got successful flashed or something like that.
When I press Reboot > System it reboots in TWRP
I tried to flash LineageOS but I get error:
Code:
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, asuming f2fs
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /date: No such device unmount of /data failed: no such volume
Patching system image unconditionally
Updater process ended with signal: 7
Error installing
Failed to mount /data
Is there a way to fix that without losing data ?
In TWRP file manager I see the system folders
try to boot on the latest twrp by fastboot boot twrp.img then wipe system then try to install the rom again.
copy the twrp.img to the internal memory
After booting download and flash the latest SuperSU then install terminal then type "su" then grant root access, then flash the TWRP on the FOTAKernel PArtition by
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Related
Hi guys,
I currently have an issue with a Nexus 5 which runs smothly the last 2 years but suddenly didn't booted anymore.
I figured out, that something with the partitions is wrong, but didn't found any solutions.
Here is what I've done so far to solve the issue:
At first i tried to reinstall the factorey images via fastboot (unlocked bootloader). The install script run without any error promts, but I wasn't still unable to boot the device (stuck at Google logo).
After some research I found this thread which I think matched my issue the most: [Q] Phone not mounting and unable to flash roms. I followed the instructions and installed Phils recovery
log:
Code:
PhilZ Touch 6.57.9
ClockworkMod v6.0.5.1
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/misc
(No Such file or directory)
Then I got adb shell access and typed the commands in cmd:
Code:
C:\Users\mw>adb shell
~ # e2fsck /dev/block/platform/msm_sdcc.1/misc
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/misc
Possibly non-existent device?
~ # e2fsck /dev/block/platform/msm_sdcc.1/system
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/system
Possibly non-existent device?
~ # e2fsck /dev/block/platform/msm_sdcc.1/userdata
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/userdata
Possibly non-existent device?
~ # cat /proc/partitions
major minor #blocks name
~ #
I think that of some reason all partition information (or somethink simliar) got lost, which course the errors.
I would be greatful if somebody could help me.
Greetings Bulkatos
I would re-flash the latest stock ROM and flash the userdata.img file last. Immediately after flashing userdata, use the buttons to boot directly to recovery and perform and wipe data, cache, and reboot.
audit13 said:
I would re-flash the latest stock ROM and flash the userdata.img file last. Immediately after flashing userdata, use the buttons to boot directly to recovery and perform and wipe data, cache, and reboot.
Click to expand...
Click to collapse
I allready did this alot and with different factory images (android versions). All flash processes were successfuly. But I'm still not able to boot into Android.
If I'm booting into recovery (thats the only Image I can flash and boot into) I allways get the same error messages (see first post)
Code:
C:\Users\mw>adb shell
~ # cat /proc/partitions
major minor #blocks name
~ # e2fsck -y /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/by-name/persist
Possibly non-existent device?
~ #
~ # make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
open: No such file or directory
~ #
~ # make_ext4fs /dev/block/mmcblk0
Need size of filesystem
~ #
~ # make_ext4fs /dev/block/mmcblk0 32G
Need size of filesystem
~ #
Did you perform a factory wipe right after flashing userdata?
I'd recommend, download the full stom from google, go to fastboot, EXTRACT den ZIP file and flash every image file on your on with:
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash cache cache.img ...
then reboot, let the phone FULL boot. If the boot finished, shutdown, reflash recovery and your rom, and try adb shell again
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.
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.
When trying to flash img files via this guide
https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203
flashing vendor and system fails
ERecovery will download a ROM but gets error "authentication failed"
Now installed TWRP and wipe fails to wipe vendor and system partition saying
Failed to mount /vendor (invalid argument)
any ideas?
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?