Hy, please i will like to solicit for your assistance, I bought a new Gionee v1(mtk6575 device) 4 days ago, after installing an app, the phone now doesn't boot but only shows white light, and if a boot it into recovery mode and try to wipe/data reset, i get multiple errors like:
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)
Please i need assistance
Related
I used zaclimon's Stock ROM and pit file for the SGP 4.0 US 8GB http://forum.xda-developers.com/showthread.php?t=1531850 and cannot load into the Android system. I can access the "Downloading" mode and recovery. I tried flashing Steves kernel. I wiped data, cache partition, and Dalvik cache and the device still isnt able to load the Android system. Are there any other stock ROMs I can try?
I just tried Kwipper's Stock ROM http://forum.xda-developers.com/show....php?t=1512331 and i get these errors in stock Recovery:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied Multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
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)
I think it's just the bootloader file. I have found many others have had this problem. Any help?
axvk97 said:
I just tried Kwipper's Stock ROM http://forum.xda-developers.com/show....php?t=1512331 and i get these errors in stock Recovery:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied Multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
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)
I think it's just the bootloader file. I have found many others have had this problem. Any help?
Click to expand...
Click to collapse
Did you wipe data in the stock recovery?
zaclimon said:
Did you wipe data in the stock recovery?
Click to expand...
Click to collapse
I wiped data, and cache partition, it removes the errors but it keeps loading into recovery.
I think it's the .pit file because after I flashed it that was when it started to load into recovery. I have no idea what to do now. Everything I try does nothing. It continues to load into recovery.
axvk97 said:
I wiped data, and cache partition, it removes the errors but it keeps loading into recovery.
I think it's the .pit file because after I flashed it that was when it started to load into recovery. I have no idea what to do now. Everything I try does nothing. It continues to load into recovery.
Click to expand...
Click to collapse
Did you find out a way out of this? I am stuck in the same situation.
Thanks is advance.
Yeah, any update on this. I am stuck with the exact same problem.
axvk97 said:
I used zaclimon's Stock ROM and pit file for the SGP 4.0 US 8GB http://forum.xda-developers.com/showthread.php?t=1531850 and cannot load into the Android system. I can access the "Downloading" mode and recovery. I tried flashing Steves kernel. I wiped data, cache partition, and Dalvik cache and the device still isnt able to load the Android system. Are there any other stock ROMs I can try?
Click to expand...
Click to collapse
I tried this and ended up just like you. After messing with this for a week I finally got it to work. I had to use heimdall. I used ver 1.32 make sure you follow the instruction about installing drivers or it will not work. Odin woul dnot work for me. Follow the instructions in Zaclimon post. Where I got confused was in the partions. I was doing them one at a time as it said but what is meant is list them in the order in heimdall so it does it in that order and moves to the next one. When done it will reboot into your stock ROM. Let me know if you have any questions
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
E: failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: Cant mount /cache/recovery/command
E: failed to mount /cache (Invalid argument)
E: Cant mount /cache/recovery/last_locale
locale is [(null)]
stage is[ ]
reason is [(null)]
fbo reports (possibly inaccurate):
command: "/sbin/recovery"
this is the error while updating to lollipop 5.0 on nexus 4...
during the first boot after update i waited for about six hours and the same boot animation kept on flashing and then the red light started flashing......and still stuck on the same problem..
please help sir.
thanks in advance
this is another one that i got from recovery logs...
E: failed to mount /cache (Invalid argument)
E: Cant mount /cache/recovery/log
E: Cant open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Cant mount /cache/recovery/last_log
E: Cant open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Cant mount /cache/recovery/last_install
E: Cant open /cache/recovery/last_install
E: failed to mount /cache (Invalid argument)
W: Cant unlink /cache/recovery/command
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' *