I'm having issues booting into my innjoo device.
It all started one morning, I woke up and saw some errors on my screen like (android.process has stopped working) I switched off the phone and turned it back on, but it got stuck on the innjoo logo and never booting up.
I decided to boot into recovery, where I encountered a list errors saying
(E: failed to mount /cache - invalid argument)
(E: cant mount /cache/recovery/log)
(E: cant open /cache/recovery/log)
And some other similar errors.
Choosing the wipe cache partition and the factory format option resulted in the same error. Which led me to believe my internal memory may be corrupted somehow (the data partition perhaps).
Is there a fix for this? And does anyone know of a way to correctly partition an Sdcard so it can be bootable and recognised by the device?
Related
Recently, my Nexus 4 has been crashing randomly - shutting off with no warning or notice. It has always rebooted back up without issues. Last night, however, it just got stuck in a boot loop - spinning balls for hours on end.
Bootloader and Recovery Mode come up with no trouble.
The phone is and always has been pure OEM/stock. I've only ever updated using built in OTA process.
I tried to reflash to stock using Wug's Nexus Toolkit, but it repeatedly failed saying the device was locked. I tried to unlock the bootloader, but that seems to require a reboot to take hold, and every time I tried the reboot it would loop again.
In Recovery Mode, I get the following:
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:failed to mount /cache (Invalid argiument)
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​
I have downloaded the full image and tried flashing the cache, and system with no effect. Toolkit doesn't show an error, but nothing changes.
Does anyone have any suggestions? I'm at a loss.
Did you try
fastboot erase cache.img
fastboot flash cache cache.img
Then perform wipe data/factory reset before booting into android.
Hi guys,
I'm seeking your help in assisting me getting my tablet works again. It's Nexus 7 2012 with last updated Android version 5.1.1 (LMY47V). The problem started when the tablet suddenly restarted and the loading intro (that appears after Google's logo) didn't change for long time. I entered the recovery mode and tried to wipe cache partition unfortunately which made my problem worse! upon reboot I only get the Google logo repeatedly with no change!
The recovery logs are as follow:
E: failed to mount /cache (invalid argument)
E: Can't mount / cache/recovery/log
E: Can't open / cache/recovery/log
I've searched on the forum and found an opinion that I should download the Android Image from the developers.google website and unzip till I find a cache.img file, but it wasn't there after I've extracted the image zip file.
I've important data that I need to retrieve from the tablet. What should I do? Taking into consideration that I didn't unroot the tablet but I did make the undebugging step before (working with pdaNet).
Thank you very much in advance!
Support
Can anyone help??
so, I have a Oneplus 2 phone that is 5 months old... I wanted to root it so in 10th December, I downloaded and flashed supersu (I have TWRP and bootloader working C: ) but When I rebooted, It was boot looping (does that make sense) so I backed up data and did a factory reset, still the boot loop, so I decided to do an advanced wipe but when I was choosing which to wipe I accidentally wiped the whole internal storage, I realized it later when I rebooted, the boot was not showing up, just the oneplus 2 logo :c
so I decided to download Oxygen OS, GAPPS ARM64 6.0 STOCK.
after downloading them I copied them to oneplus 2 by TWRP (thank god)
then I installed them, after installing, The boot logo was working, when it finally booted it said encryption error: internal storage damaged and some other text
so What should I do?
install a new rom? buy a new phone (hopefully not)
Projonmo112 said:
so, I have a Oneplus 2 phone that is 5 months old... I wanted to root it so in 10th December, I downloaded and flashed supersu (I have TWRP and bootloader working C: ) but When I rebooted, It was boot looping (does that make sense) so I backed up data and did a factory reset, still the boot loop, so I decided to do an advanced wipe but when I was choosing which to wipe I accidentally wiped the whole internal storage, I realized it later when I rebooted, the boot was not showing up, just the oneplus 2 logo :c
so I decided to download Oxygen OS, GAPPS ARM64 6.0 STOCK.
after downloading them I copied them to oneplus 2 by TWRP (thank god)
then I installed them, after installing, The boot logo was working, when it finally booted it said encryption error: internal storage damaged and some other text
so What should I do?
install a new rom? buy a new phone (hopefully not)
Click to expand...
Click to collapse
Go to advanced wipe and format data
Confirm and do not tell me that you have data there. I'm assuming you have already made the necessary backups. This is the only way to fix it
anupritaisno1 said:
Go to advanced wipe and format data
Confirm and do not tell me that you have data there. I'm assuming you have already made the necessary backups. This is the only way to fix it
Click to expand...
Click to collapse
I don't have the backup :c
is there any way to fix it without a backup?
anupritaisno1 said:
Go to advanced wipe and format data
Confirm and do not tell me that you have data there. I'm assuming you have already made the necessary backups. This is the only way to fix it
Click to expand...
Click to collapse
I don't have the backup
halp meh pls
I flashed cm 13, Now in a boot loop :/
I then went to stock rom, still the unsuccessful encryption
sorry I am a noob :c
Projonmo112 said:
I don't have the backup
halp meh pls
I flashed cm 13, Now in a boot loop :/
I then went to stock rom, still the unsuccessful encryption
sorry I am a noob :c
Click to expand...
Click to collapse
Format data
Any solution?
anupritaisno1 said:
Format data
Click to expand...
Click to collapse
I was talking on a phone and suddenly my OP2 got restarted and what I see is "Encryption Unsuccessful".
I don't know what has gone wrong, maybe when on call it just got mistakenly browsed into encryption option or something?
I am on Oxygen OS 3.5.6 and rooted with TWRP 3.0.2-2.
Now whenever I boot my phone it shows
"Encryption unsuccessful
Your phone storage has been damaged, please download the firmware package to brush".
It appears that some part of OS is loaded because when I change the volume the android styled indicator bar and the settings gear appears but nothing happens when I tap it.
I entered TWRP to erase data (again because I'm sure had checked it) and it says (in red):
E:Unable to load '/twres/languages/en-US.xml'
Could not mount /data and unable to find crypto footer.
Failed to mount '/cache' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
...done
Unable to mount storage.
Failed to mount 'data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Full SELinux is present.
Failed to mount '/cache' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)
Formatting cache using make_ext4fs...
Failed to mount '/cache' (Invalid argument)
Updating partition details...
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
...done
Unable to mount storage
When I go to Wipe / Repair File System selecting Data partition it shows me:
Present: Yes
Removable: No
Size 0MB
Used: 0MB
Free: 0MB
Backup Size: 0MB
When I select Internal Storage and tap Repair or Change File System it says Invalid partition selection (in red).
Tried this: https://forum.xda-developers.com/one...oos-3-t3402020
but I am stuck at recovery tool. After clicking the square button it shows ok and then pressing start it starts some procedure and then stuck on something called FirehoseCheckRSPE and some Chinese thing written ahead of it.
https://drive.google.com/file/d/0B_l...ew?usp=sharing
Tried fastboot comands to check whether it works and it does work.
Like when entered comand fastboot devices, it does shows the device.
I tried to flash stock recovery by --> fastboot flash recovery recovery.img
It succeeds like this
target reported max download size of 536870912 bytes
sending 'recovery' (17013 KB)...
OKAY [ 0.400s]
writing 'recovery'...
OKAY [ 0.086s]
finished. total time: 0.490s
But when i restart to recovery it still shows TWRP.
What should I do?
I just need my phone to work.
Please help me out
I really don't know how it even happened suddenly.
Thank-you in advance.
Hi Hello everyone
I am having a lenovo a6000
I think its bricked so I need ur attention here
I was able to access fastboot and then booted into twrp recovery.
In recovery I noticed following message (unable to mount /system... Invalid argument, Unable to mount /data... Inavlid argument
Unable to mount /cache... Invalid argument)
I am able to mount memory card and usb
And tried to install stock rom but no success..It ended with some kinda error I don't Remember...
I also tried qpst, qfil and all the qualcomm recovery tools but no success(stuck on firehose(firmware) for about 30-40 minutes)
The time required for flashing through these softwares is max. 5-10 mins I think...
Is there any way to revive my device?
I kindly req the devs to reply
Sorry for bad English
Thank you
I decided to install a custom ROM in my device and what I did was wiped all partitions except 'Micro SD Card' and 'USB OTG', after that I formated data and it wiped all files in my device. Then I tried to flash the custom ROM but I was unable to flash it and an error message pops up - "failed to mount '/cache' (no such device)." I again tried wiping the partitions and all the partitions gets wiped easily exept the cache partition and the same error message pops up. Also whenever I try to restart into recovery, everytime it shows a message "No OS Installed! Are you sure you wish to reboot?"
So please help me out with this problem I can't flash anything at all
engtika said:
I decided to install a custom ROM in my device and what I did was wiped all partitions except 'Micro SD Card' and 'USB OTG', after that I formated data and it wiped all files in my device. Then I tried to flash the custom ROM but I was unable to flash it and an error message pops up - "failed to mount '/cache' (no such device)." I again tried wiping the partitions and all the partitions gets wiped easily exept the cache partition and the same error message pops up. Also whenever I try to restart into recovery, everytime it shows a message "No OS Installed! Are you sure you wish to reboot?"
So please help me out with this problem I can't flash anything at all
Click to expand...
Click to collapse
TWRP version? Have you tried to flash Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
to prevent the device from encrypting itself?
Wolfcity said:
TWRP version? Have you tried to flash Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
to prevent the device from encrypting itself?
Click to expand...
Click to collapse
I'm using TWRP v3.2.3-1 and I've flashed that zip but still the cache partition doesn't gets mount.
anyone have idea, im also experiencing the same issue. I was trying to root, and it wasnt taking it on my Moto G5 Plus, so i wiped everything except the same stuff, and then after that, any time it tries to mount the cache it fails. It wont mount at all, refuses to check the box. This is my log when i try to wipe the cache only now.
Failed to mount '/cache' (No such device)
Updating partition details...
Failed to mount '/cache' (No such device)
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/cache' (No such device)
E:Unable to wipe '/cache' -- unknown file system 'auto'
Unable to wipe /cache.
Updating partition details...
Failed to mount '/cache' (No such device)
Nevermind, I got it solved,, must have been caught trying to get to the OS, and looping cause there was not OS, and messing things up. Had to make sure i was holding the buttons to go to boot loader every time, but got it working.