OnePlus one got stuck on Cyanogen "MOD READY"
Hello Developers,
I need help in recovering my OPO from this state.
Not sure how i ended up in this state. It was working fine till Last week. Phone got turned off and after charging the phone and power on. It just got stuck on this screen.
I have never rooted this phone or installed any custom recovery.
I have tried many help guides to make the device working but nothing worked.
1. Charged the phone for 24 hours and then tried Power on. (Didn't work)
2. Entered in to Recovery mode by pressing Power button + Volume down --> Factory Reset--> Full factory reset -->Yes / and i got below errors while doing so.
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Can't open /recovery/log
E:failed to mount /cache/recovery/last_log
3. Entered in to Recovery mode by pressing Power button + Volume down --> Factory Reset--> Wipe cache partition -->Yes / and i got below errors while doing so.
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Can't open /recovery/log
E:failed to mount /cache/recovery/last_log
4. Entered in to Fastboot mode by pressing Power button + Volume up
-Executed the command fastboot oem device-info
# Bootloader Status #
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
- Executed the command fastboot oem unlock
Phone rebooted and entered in to recovery mode. But this command doesn't unlock bootloader for me.
After verifying the device-info here is the output.
# Bootloader Status #
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
Request someone to help me resolve this issue. Any help is much appreciated.
Thank you.
Related
I guys, I have a Galaxy tab 2 GT-5110, it is stuck in the Samsung Icon, it also won't start in Odin (download mode), when a press power + down volume it shows the message "no command" then E: failed to mount /efs (invalid arguments), I don't have the efs back up, and the Samsung Kies doesn't recognise the tablet, pleasessss any tips?, thank you so much
Hello,
So 2 days ago I received the OTA update for 6.0. Yesterday when my battery was low the device turned off unexpectedly. When I finally had a chance to plug it in the phone went into a BOOT LOOP. I left it over night hoping with the additional charge it would stop but no luck.
After not being able to get into recovery mode because of continued resetting. I looked up several videos and posts from Nexus users with the same issue. I found the solution to be tapping the power button repeatedly till device is fixed. It sounded absurd but it worked and the phone stopped resetting and started to charge as normal. I let the phone charge for about an hour and then proceeded to turn it on.
At that point it was then stuck at the Google logo. So after about 15 minutes of waiting I decided to do a hard reset. When doing so I an encountered an error which I am unfamiliar with. I have a picture of what it tell me but can't seem post it on the forum.
IT SAYS:
Supported API: 3
E: failed to mount/cache (Invalid Argument)
--Wiping Data...
Formatting Data...
E: failed to mount /cache (invalid argument)
Formatting /cache...
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/log
E: Can't open/cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/last_install
E: Can't open/cache/recovery/last_install
Data wipe complete.
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/log
E: Can't open/cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/last_install
E: Can't open/cache/recovery/last_install
E: failed to mount /cache (invalid argument)
After it did the wipe it got stuck at the new splash screen:
At this point I'm not sure what to do from here or where to begin to fix this problem.
djillusion954 said:
Hello,
So 2 days ago I received the OTA update for 6.0. Yesterday when my battery was low the device turned off unexpectedly. When I finally had a chance to plug it in the phone went into a BOOT LOOP. I left it over night hoping with the additional charge it would stop but no luck.
After not being able to get into recovery mode because of continued resetting. I looked up several videos and posts from Nexus users with the same issue. I found the solution to be tapping the power button repeatedly till device is fixed. It sounded absurd but it worked and the phone stopped resetting and started to charge as normal. I let the phone charge for about an hour and then proceeded to turn it on.
At that point it was then stuck at the Google logo. So after about 15 minutes of waiting I decided to do a hard reset. When doing so I an encountered an error which I am unfamiliar with. I have a picture of what it tell me but can't seem post it on the forum.
IT SAYS:
Supported API: 3
E: failed to mount/cache (Invalid Argument)
--Wiping Data...
Formatting Data...
E: failed to mount /cache (invalid argument)
Formatting /cache...
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/log
E: Can't open/cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/last_install
E: Can't open/cache/recovery/last_install
Data wipe complete.
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/log
E: Can't open/cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/last_install
E: Can't open/cache/recovery/last_install
E: failed to mount /cache (invalid argument)
After it did the wipe it got stuck at the new splash screen:
At this point I'm not sure what to do from here or where to begin to fix this problem.
Click to expand...
Click to collapse
This is why people should NOT, EVER let their devices batteries run low on juice.
Charge up your device with an AC charger, forget USB, and leave it for a few hours. then boot to bootloader and flash MRA56K factory image.
beekay201 said:
This is why people should NOT, EVER let their devices batteries run low on juice.
Charge up your device with an AC charger, forget USB, and leave it for a few hours. then boot to bootloader and flash MRA56K factory image.
Click to expand...
Click to collapse
MRA56K factory image???????????? what is that and where can I find it???
Maybe the op meant to say mra58k?
Hey. So, same problem here (same errors), but a faulty power button caused the reboot in the middle of the update.
Replaced the power button but now can't flash anything since my USB debugging was off (unrooted- from day one just auto-updated).
Can I do something or I'm screwed? we don't have here google services and I bought the device from US (google store website).
By a mistake I formatted EFS folder. Now I am unable to flash any firmware.
This error is getting on android recovery.
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verify error...
Please help me....
Are you able to go into download mode or a custom recovery. If you hold down volume down + home + power key - hold it for 5 secs, all at once, you will go to download mode automatically.
Sent from my SM-T377V using Tapatalk
my friend gave his phone G955f,it was only possible to enter download mode,no recovery,nothing..not even boot samsung logo..after 2 days i finally flashed firmware...now i have new problem,flash was done with odin,3 different german firmwares and i always get the same result
buttons are responsive,i can restart phone,get into download mode but it is stuck on boot logo..i have deleted cache and factory in recovery menu and still nothing..
But in down left corner in recovery i get message:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is UNKNOWN
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed...
Does anyone know why is that and how to fix it?
empty
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?