I have a VFD-600 that is stuck in a bootloop but, surprisingly, adb works. I can type "adb shell ls" and it shows all the files, but I can't go to /sdcard (which is a symlink to /mnt/user/0/primary, which does not exist.). I tried wiping cache, mounting system and wiping data, but I always got `E: fangjun failed to mount /cache (Invalid argument)`. What can I do?
Andrei_07 said:
I have a VFD-600 that is stuck in a bootloop but, surprisingly, adb works. I can type "adb shell ls" and it shows all the files, but I can't go to /sdcard (which is a symlink to /mnt/user/0/primary, which does not exist.). I tried wiping cache, mounting system and wiping data, but I always got `E: fangjun failed to mount /cache (Invalid argument)`. What can I do?
Click to expand...
Click to collapse
Hi, is fastboot working for you? Using fastboot you can flash the firmware for your device and thus fix the bootloop.
Jan Skokan said:
Hi, is fastboot working for you? Using fastboot you can flash the firmware for your device and thus fix the bootloop.
Click to expand...
Click to collapse
Yes, and I've tried that but it gives me the same error. I only tried ADB sideload, but I don't think flashing from SD card will make a difference
Andrei_07 said:
Yes, and I've tried that but it gives me the same error. I only tried ADB sideload, but I don't think flashing from SD card will make a difference
Click to expand...
Click to collapse
What exactly happened before you got the bootloop? Do you have an unlocked bootloader and a rooted phone?
Try formatting the data or factory reset the phone
Jan Skokan said:
What exactly happened before you got the bootloop? Do you have an unlocked bootloader and a rooted phone?
Click to expand...
Click to collapse
I haven't used this phone in a year, and it was working back then. Unfortunately, the bootloader is locked and the phone is not rooted.
Andrei_07 said:
I have a VFD-600 that is stuck in a bootloop but, surprisingly, adb works. I can type "adb shell ls" and it shows all the files, but I can't go to /sdcard (which is a symlink to /mnt/user/0/primary, which does not exist.). I tried wiping cache, mounting system and wiping data, but I always got `E: fangjun failed to mount /cache (Invalid argument)`. What can I do?
Click to expand...
Click to collapse
Hello and good afternoon, @Andrei_07
Prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Jan Skokan said:
Try formatting the data or factory reset the phone
Click to expand...
Click to collapse
I tried that, but it gave me the same error.
Related
Hi
I've got a SmartQ Q8 for 4 weeks. When I recieved it I updated the firmware to the custom rom by D3BA. Everything has been running smoothly until today. While syncing Google Currents, the system crashed and rebooted. This happens sometimes, but this time it hasn't restarted. It shows SmartDevices logo for a time and then goes blank.
I can boot into CWM, so I have tried to restore D3BA firmware and I've also tried the official firmware, version 3.0. With the official I don't see any problem, but it keep on failing. When I install the custom server, I've seen some errors wiping the data partition and also some installing the zip. This are the messages
/data
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
and
/cache
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
I don't know what has happened. After googling the error, it seems like the partition is corrupted, and some directories are missing?? Is there a way to access a console? Maybe using fdisk this could be solved.
Can anyone help me with this?
Best Regards
trustno12003 said:
Hi
I've got a SmartQ Q8 for 4 weeks. When I recieved it I updated the firmware to the custom rom by D3BA. Everything has been running smoothly until today. While syncing Google Currents, the system crashed and rebooted. This happens sometimes, but this time it hasn't restarted. It shows SmartDevices logo for a time and then goes blank.
I can boot into CWM, so I have tried to restore D3BA firmware and I've also tried the official firmware, version 3.0. With the official I don't see any problem, but it keep on failing. When I install the custom server, I've seen some errors wiping the data partition and also some installing the zip. This are the messages
/data
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p9
and
/cache
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
I don't know what has happened. After googling the error, it seems like the partition is corrupted, and some directories are missing?? Is there a way to access a console? Maybe using fdisk this could be solved.
Can anyone help me with this?
Best Regards
Click to expand...
Click to collapse
You can enter in BOOTLOADER Mode and flash the STOCK ROM.
Best regards from Mr.Indigo!
Hello
I think i've tried that. I put the Stock Rom v1 (SMARTQQ8 file) in the root of my SD Card and then I booted with the Power + Vol+ buttons, so it shows a logo and starts doing something, with a progress bar. Once it finishes, the screen goes blank again. Is that what you meant?
Best Regards
EDIT: After flashing the stock rom, I've enter Recovery again (With Power+Ctrl-) and now I can wipe data. I've install the stock again and now everything seems to be OK. Thank you Mr. Indigo, you save my day.
Best Regards
trustno12003 said:
Hello
I think i've tried that. I put the Stock Rom v1 (SMARTQQ8 file) in the root of my SD Card and then I booted with the Power + Vol+ buttons, so it shows a logo and starts doing something, with a progress bar. Once it finishes, the screen goes blank again. Is that what you meant?
Best Regards
EDIT: After flashing the stock rom, I've enter Recovery again (With Power+Ctrl-) and now I can wipe data. I've install the stock again and now everything seems to be OK. Thank you Mr. Indigo, you save my day.
Best Regards
Click to expand...
Click to collapse
Hey, would you mind letting me know which method you used to flash stock firmware? I am having a similar case with an S3 (Gt-i9300)
So i've posted pieces of this in other threads assuming i knew what the problem was, but nobody has been able to help me so far so i'm posting the whole saga anew.
First off, my phone:
LazyPanda S-OFF
HBOOT:1.12.111
RADIO-1.12.11.0809
I was running MeanRom 4.8 with TWRP 2.3.0.1
Like so many others i tried to OTA update just to get stuck at the recovery screen on reboot. I then found out that i had no ROM installed. I tried to wipe (cache, dalvik, system, etc) and flash a new ROM but i kept getting FAIL messages in TWRP.
"Formatting and mounting partition...
e:error in /sdcard/meanrom-ics-v49-jewel-ltevo.zip
(status 1)
error flashing zip '/sdcard/meanrom-ics-v49-jewel-ltevo.zip'
updating partition details"
I figured it might be a botched DL so i did it manually, MD5 checked out after copying to the mounted device. Attempted to flash the clean DL and i got the same error message. I nandroid restored an old stock rooted ROM I had and it installed just fine. After booting up to the system ROM for the first time I immediately got an "Internal storage is low" error. Checked and after a clean restore (no apps installed, fresh out of the box...) i only have ~200MB free in the app storage section (out of 1.92GB). I can't fathom what's taking up all the other space, nothing seems to be there. Because of this i can't install Titanium, Rom Toolbox, or anything else that may be remotely useful. I tried fixing permissions and re-wiping, re-restoring and i got the same thing.
I tried to flash the TWRP 2.2.2.0 image from recovery thinking this was the problem and got this message:
"updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
Formatting cache...done
Formatting Data... done
Using rm -rf on .android_secure
Updating partition details
E:unable to open ums lunfile 'sys/class/android_usb/android/f_mass_sto.....
E:unable to open zip file."
And THEN i tried to ABD flash the TWRP image through fastboot with "fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img" then 'fastboot flash boot openrecovery-twrp-2.2.2.0-jewel.img' and got this error:
"FAILED (remote partition is not allowed to be flushed!)"
So, i'm stuck with a device that loads a stock ROM, cant flash a new recovery or ROM, and cant' install anything useful because it's full after a restore. Does anyone have any suggestions how to clean/resore my partitions through ADB or a script? Your advice is much appreciated.
I can't help, but I suspect you'd have better luck posting this in the TWRP thread.
I'm wondering if fastboot erase cache would help here. I've seen that command used I think to clean a partition, but it may have been for something else. Sorry, this is a bit over my head. Hope you get help.
hurled from my AOKP'd Evo LTE. Enjoy.
You might have to re lock and run the RUU and then unlock and flash twrp, 2.3 has issues with the partitions for some reason so stick to 2.2
Try updating to the latest twrp. The latest is 2.3.1.0 not 2.3.0.1.
2.3.0.1 had issues which you can read about here
http://www.pocketables.com/2012/10/...for-htc-evo-4g-lte-fixes-rom-flash-death.html
It's been updated already? Cool
om4 said:
It's been updated already? Cool
Click to expand...
Click to collapse
Yeah, it fixes the mounting of the sdcards and the flashing rom problem
You may also want to get the 1.12.2222 hboot from the unlimited site. It has fastboot commands enabled.
I noticed you tried flashing TWRP to both the recovery and boot partitions...Do you get the same error when you flash to just recovery? TWRP should not be on boot.
Sent from my EVO LTE
I have a DNA and while trying to restore to a previous backup I made in an attempt to restore to a stock rom, I ended up wiping my system from TWRP's wipe screen. Now i'm stuck in a boot loop and despite adb pushing a rom over to try to flash and recover to it, I'm pretty sure all of my files are gone and i'm screwed. Help?
dscuevas said:
I have a DNA and while trying to restore to a previous backup I made in an attempt to restore to a stock rom, I ended up wiping my system from TWRP's wipe screen. Now i'm stuck in a boot loop and despite adb pushing a rom over to try to flash and recover to it, I'm pretty sure all of my files are gone and i'm screwed. Help?
Click to expand...
Click to collapse
You should still be able to get into the bootloader by holding volume down and power or by adb reboot recovery. Then just adb push the rom to somewhere like /data(just because I know it exists) and flash the rom.
123421342 said:
You should still be able to get into the bootloader by holding volume down and power or by adb reboot recovery. Then just adb push the rom to somewhere like /data(just because I know it exists) and flash the rom.
Click to expand...
Click to collapse
I can get to TWRP's recovery screen, and push the rom to /data, but when I try to flash and install I get error messages saying it failed because it's unable to mount /storage or /data
dscuevas said:
I can get to TWRP's recovery screen, and push the rom to /data, but when I try to flash and install I get error messages saying it failed because it's unable to mount /storage or /data
Click to expand...
Click to collapse
make sure they are mounted in the twrp mount screen. You may have to do a full wipe of them too.
123421342 said:
make sure they are mounted in the twrp mount screen. You may have to do a full wipe of them too.
Click to expand...
Click to collapse
I can mount system and cache, but not data
dscuevas said:
I can mount system and cache, but not data
Click to expand...
Click to collapse
install CWM in bootloader and try it again
.torrented said:
install CWM in bootloader and try it again
Click to expand...
Click to collapse
It worked! Thank you guys so much for your help haha
Hello,
i tried to root my Samsung Galaxy S3 (stock rom, encrypted) with this manual,
Code:
translate.google.com/translate?sl=cs&tl=en&js=y&prev=_t&hl=cs&ie=UTF-8&u=http%3A%2F%2Fandroidforum.cz%2Fgalaxy-s-iii-root-recovery-t28119.html&edit-text=
Because my S3 was encrypted, it stuck on Samsung logo, so i tried to wipe it with CWM Touch, and tells me:
Code:
-- Wiping data --
[COLOR="Red"]Formating /data
Error mounting /data !
Skipping format...[/COLOR]
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android-secure...
[COLOR="Red"]Error mounting /sdcard/.android-secure!
Skipping format...[/COLOR]
Data wipe complete.
And now i trying to use CyanongenMod 11 Nightly (16.05.2014), but it also stuck on CyanogenMod logo.
How can i fix this ?
Thanks for any reply
---
Sorry for my bad english.
Follow the guide in general forum, sticky threads on how to flash a stock firmware with Odin. After flash then factory reset in recovery.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Follow the guide in general forum, sticky threads on how to flash a stock firmware with Odin. After flash then factory reset in recovery.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I tried, but still in bootloop. Im searching now for tool that wipes whole phone.
Hey guys
Don't know where exactly to post this. But I need urgent help. Not sure what went wrong, but tried to flash Lineage. However, when I wanted to do a clean wipe I got a failed to Mount ' /vendor (invalid agreement)
Any idea of how to get out of this, or if there is something I can re flash ? I tried to change the partitions etc but nothing seems to be working.
I have a Moto Z and I'm stuck in TWRP. Apologies for the inconvenience here
Guys might have figured it out. quick question, when wiping, what are the ones i need to tick off, before installing a new rom?
is it
'Cache
davlik
system
vendor
isgakbrfc said:
Guys might have figured it out. quick question, when wiping, what are the ones i need to tick off, before installing a new rom?
is it
'Cache
davlik
system
vendor
Click to expand...
Click to collapse
To get around tha "mount vendor" issue you have to update to latest TWRP 3.3.1.0.