It is my first time trying to port roms... it seems like i messed up..
First.. i have ported my roms using this guide:
forum.xda-developers.com/showthread.php?t=2707438
and made a mistake while registering my device on kitchen (copied all text from recovery.fstab to A11Q)
and thoroughly followed steps until porting Step I (use CWM to port)... and didnt realise it until my 3rd times reading it..
and it seems my sd card partition also messed up..
when i boot to recovery mode... there's a message like this:
E: Can't mount /cache/recovery/command
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
and then.. i searched for solution and one of the source said to format /cache, when i do there a message like this:
Formatting /cache...
E:format_volume: make_ext4f4fs failed on /dev/block/mmcblk0p6
Error formatting /cache
and it was the same with /data, /system, /cache, /emmc,.. only /sdcard, and /sd-ext worked somehow...
i tried to restore but it said:
Checking MD5 sums...
Erasing boot before restore...
restoring boot image...
restoring system...
E:format_volume: make_ext4f4fs failed on /dev/block/mmcblk0p5
Error while formatting /system!
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
and the problem is.. i didnt understand which guide i should follow knowing all of them just showing one of these problem.. so, please HELP!
Related
hi everybody, i tried to look also in the forum with the search and i didn't find anything relevant...
i have the blade from china unicom, i rooted it and installed cw. everything was almost smooth (i downloaded the wrong z4root, but then i got it right).
when i tried to make a backup or anything else vis CW it shows me this:
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/command
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
basically i can't do anything. i can't even make a factory reset.
what went wrong?
I woke up this morning and my phone was at the first HTC screen (the white one).
This is rooted.
I am using CMW 6.0.3.2 so I was going to try and clear the cache thinking something was wrong...
Right when it opens up it says:
Code:
E:Can't mount /cache/recovery/command
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
Then, when I go to the 'wipe cache partition', I get:
Code:
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p33
Cache wipe complete.
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
That's odd....so I went to factory reset:
Code:
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p33
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure
Skipping format...
Data wipe complete.
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
Is my phone hosed or is there something else I can try?
Same problem here.
Had you solved ?
I can't do nothing in Odin too.
Tried to apply PIT file or CF-Root again, but both "FAIL!" with message: "Complete(Write) operation failed."
My phone is a samsung s3 i9300 , and started with the same problem as yours, when i woke up.
romuloff said:
Same problem here.
Had you solved ?
I can't do nothing in Odin too.
Tried to apply PIT file or CF-Root again, but both "FAIL!" with message: "Complete(Write) operation failed."
My phone is a samsung s3 i9300 , and started with the same problem as yours, when i woke up.
Click to expand...
Click to collapse
I have not solved yet. I saw some posts about maybe installing a different recovery and trying to overwrite the partition information.
Everything I see suggests the EMMC chip died
I'm trying to install the rom miui in my neken n6
First I rooted the phone successfully, after I installed "rua1 autoCWM v5.5.0.4 for neken n6".
The problem is when I restart in recovery mode I get some errors in the beginning:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
If I try to wipe data/factory reset i get:
"
E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p7
Formatting /cache...
E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p6
Formatting /sd-ext...
No app2sd partition found. Skipping format of /sd-ext.
Formatting /sdcard/.android_secure...
error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
"
If I go to "mounts and storage" anything that I try to mount also gives error.
I restart the phone and nothing changed, all the data is still there.
Any help would be very very appreciated
Thanks
jkoelho said:
I'm trying to install the rom miui in my neken n6
First I rooted the phone successfully, after I installed "rua1 autoCWM v5.5.0.4 for neken n6".
The problem is when I restart in recovery mode I get some errors in the beginning:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
If I try to wipe data/factory reset i get:
"
E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p7
Formatting /cache...
E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p6
Formatting /sd-ext...
No app2sd partition found. Skipping format of /sd-ext.
Formatting /sdcard/.android_secure...
error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
"
If I go to "mounts and storage" anything that I try to mount also gives error.
I restart the phone and nothing changed, all the data is still there.
Any help would be very very appreciated
Thanks
Click to expand...
Click to collapse
No one has any idea of something I could try?
I can't install Miui and the stock firmware is very bad. I'm completely stuck :crying:
jkoelho said:
No one has any idea of something I could try?
I can't install Miui and the stock firmware is very bad. I'm completely stuck :crying:
Click to expand...
Click to collapse
Anyone can help me?
Anything thing at all that can at least point me in some direction to try to solve my problem?
I'm completely stuck, I really need anyone help, anything at all
I know this is not about the topic but i dont know where to ask, is anyone else having trouble with he focus on the neken n6?
the very close pictures are fine but if i take a pic of someone standing at 2 meters in front of me it wont focus
My daughters cubby is preforming a factory reset every time it is powered off. It is running Android 4.4.2 v4.6_20140408. I noticed it started after the internal SD card partition was erased.
When the tablet is loading in system recovery the following is displayed:
E: failed to mount /cache (Invalid argument)
E: failed to mount /data (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_log
E: Can't open /cache/recovery/last_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: Can't mount /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
I believe the file structure needs to be restored/recreated, but I don't know what it should be or if it might be a different issue. Preforming the factory reset doesn't solve the problem.
Did you ever find a fix? I am having the same problem.
Unfortunately, I did not.
Same problem here. We've been dealing with it since mid-2018. The best advice I have is to always keep it plugged in and never let it power down or run out of battery. I wish I never did the factory reset on it. However, I will add that we have another Cubby that works FINE after the reset (in fact, I've reset it a few times now). The production date is a year newer than the Cubby that won't behave. We finally went to the Amazon Fire in 2018 and we do not like it as much as we loved the Sprout Cubby! My daughter's Fire died after 2 years, and we recently have brought the good Cubby out again. Now my other daughter is asking for hers (the one that malfunctions). I am revisiting this to see if anything can be done to save it-- but so far, no luck.
My dad recently bought an HP 10 tablet from my uncle and asked me to root it...which was a mistake. I had a successful root with the Android-based version of King Root, cleaned it up with SuperSU Me, and thought everything was fine until I rebooted...and the tablet got stuck on the boot animation. Booting with the volume down button down resulted in just the HP logo, without the boot animation. Booting with the volume up button down booted into recovery. When I boot into recovery I'm greeted by this lovely message at the bottom:
Code:
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_log
E:Can't open /cache/recovery/last_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)
I have tried the following things from the recovery menu:
wipe data/factory reset:
Code:
-- Wiping data...
Wiping /data...
Formatting /data...
E:failed to mount /cache (Invalid argument)
Formatting /cache...
Data wipe complete.
wipe cache partition
Code:
-- Wiping cache..
E:failed to mount /cache (Invalid argument)
Formatting /cache...
Cache wipe complete.
apply update from internal storage
Code:
E:failed to mount /data (Invalid argument)
E:error opening /data/media/0: No such file or directory
Install from internal storage complete.
apply update from external storage
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /extsd (Invalid argument)
(Tablet was booted with microSDXC card inside)
apply update from cache
Code:
E:failed to mount /cache (Invalid argument)
apply update from ADB
adb was...weird. I verified the connection through adb devices, but most commands, including adb reboot bootloader, resulted in error: closed.
Windows side:
Code:
C:\Users\jkmar>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
CNU4389ZNS sideload
C:\Users\jkmar\Desktop>adb reboot recovery
error: closed
C:\Users\jkmar\Desktop>adb sideload UPDATE.ZIP
loading: 'UPDATE.ZIP'
sending: 'UPDATE.ZIP' 100%
Tablet side:
Code:
Now send the package you want to apply to the device with "adb sideload <filename>"
...
E:failed to mount /cache (Invalid argument)
E:failed to set up expected mounts for install; aborting
Installation aborted.
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_log
E:Can't open /cache/recovery/last_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)
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_log
E:Can't open /cache/recovery/last_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)
UPDATE.ZIP came from HP's download page. I just don't know what to do at this point.
Please help also having the same problem with my HP 8 G2 1411
You can't reboot in adb sideload, you can't do many things in adb sideload since it is intended for recovering from a brick and that is the only feature I know (if you have a custom recovery and want to do a clean install, you wipe every partition and then sideload it, so the sideload feature is intended for flashing), you can't reboot, I fired up my test device to confirm this and it was true. If you extract the .zip file, does it contain any .img files and .gz files?
Crap, somehow I missed this thread actually getting a reply. Thanks!
Yes, there is a boot.img file as well as a system folder containing what I'm used to seeing in the root directory.
jkmartindale said:
Crap, somehow I missed this thread actually getting a reply. Thanks!
Yes, there is a boot.img file as well as a system folder containing what I'm used to seeing in the root directory.
Click to expand...
Click to collapse
Can you boot into the bootloader? It can be a weird combination by the way, my tablet is press and hold power button then one second later you'd have to press and hold volume down.
I'm not entirely sure what the bootloader looks like, so I don't know if I have. As mentioned in OP, I did manage to boot into something that just showed the HP logo and nothing else. In that stage I tried both adb devices and fastboot devices, but nothing showed up. Rebooting into recovery and picking apply update from ADB was the only way I was able to get it to be recognized by adb devices so far.
jkmartindale said:
I'm not entirely sure what the bootloader looks like, so I don't know if I have. As mentioned in OP, I did manage to boot into something that just showed the HP logo and nothing else. In that stage I tried both adb devices and fastboot devices, but nothing showed up. Rebooting into recovery and picking apply update from ADB was the only way I was able to get it to be recognized by adb devices so far.
Click to expand...
Click to collapse
Extract the boot.img and then adb sideload it. Report result and log.
For your information, the boot.img is the kernel so you will basically reflash the kernel.
If I helped, hit "thanks" .
I got the same result for both update.zip files on the support website. boot.img was extracted using 7-zip both times.
Code:
C:\WINDOWS\System32>adb sideload boot.img
loading: 'boot.img'
* cannot read 'boot.img' *