So yeah, my phone was regular 2.3.4 and it wouldn't always reboot easily (took multiple tries). So I figured I'd install CyanogenMod 7 like all the cool kids. I'm a programmer, this should be easy, right? Wrong.
So after much trial and error fastboot decided to randomly find my phone and let me unlock it (long story...). I start playing around with adb and fastboot, having a good old time. I decide to do the ClockworkMod Recovery image and it works great. I try to do an "update from sdcard" with the latest CyanogenMod for Nexus S and it amazingly works!... Except that it still won't boot up. It sits on the Google loading screen--I suspect failing to mount anything.
I found out about this:
Code:
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/platform/s3c-sdhci.0/by-name/media (null)
2 /system ext4 /dev/block/platform/s3c-sdhci.0/by-name/system (null)
3 /cache yaffs2 cache (null)
4 /data ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata (null)
5 /misc mtd misc (null)
6 /boot mtd boot (null)
7 /recovery mtd recovery (null)
8 /bootloader mtd bootloader (null)
9 /radio mtd radio (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Notice all of the (null)s....
Also this:
Code:
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
E:Can't mount /sdcard/update.zip
Installation aborted.
mtd: successfully wrote block at 0
I:Set boot command ""
E:Unable to write to ums lunfile (No such file or directory)
...and this, clearly from fstab:
Code:
/dev/block/platform/s5pc110-onenand # mount -a
mount -a
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
: No such file or directory
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/system on /system failed
: No such file or directory
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/media on /sdcard failed:
No such file or directory
There's no s3c-sdhci.0 in /dev/block/platform.... only s5pc110-onenand (which happens to be the title of the processor and memory used in my phone).
So yeah, that's where my brain gives out.
I'd like to install CM7, or at the least get a working phone back somehow.
Oh yeah, I tried doing adb shell and a nandroid restore command w/ downloaded nandroid backup. No love. It told me "unknown volume for path [/sdcard] Can't mount /sdcard". No ****.
Ideas?
Thanks!
Small update:
about 1 out of 100 times, it'll allow me to mount the sdcard after some random fiddling. I have tried multiple recovery images, erasing partitions, flashing random things... nothing works!
The one or two times it mounted the sdcard, I was able to perform an "update from sdcard" but then it would just do what it has done for a long time--sit at the google loading screen for hours and never actually boot into the real OS.
Sigh. Hardware issue maybe?
Hi,
what's your phones status?
My Nexus seems at a similar state now I came across http://forum.xda-developers.com/showthread.php?t=991276 and had to try it (why not, I have nandroid backups, Titanium etc. ...) I applied a setting, rebooted and got stuck at the google logo. It would boot into recovery but there it has no access to sdcard, system, data (but cache is mounted). After lots of fiddling I got it to work once, whiped, flashed a rom and all looked good again. But now I did a reboot and the phone is stuck again and in recovery (CWM 3.something) I get no sdcard
What happened and how to fix it?
I managed to flash a stock system back on the phone and it still didn't work, so I called Samsung and they let me RMA the phone. I got it back three weeks later, in good shape. They had to replace the PBA, the mainboard, and they did it all for free. They even gave me a shipping label to use when I shipped it out. Nice.
At the least, I think it's necessary to flash a stock bootloader and lock the phone before calling them.
Good luck!
Good for you
I tried flashing a stock rom, both using fastboot and also using Odin, both methods fail or get stuck while flashing the system.img
Looks like I've screwed up
If I could at least once get to the data on sdcard ...
i think i found a workaround
i tried flashing the old clockworkmod (3.1.0.1) and the flashing the latestest one twice and then clockworkmod was able to mount the sdcard. huge relief. installed the rom and then rebooted and the system booted well.
also tried installing the clockwork manager app and flashing the latest recovery from the app and then rebooted into recovery. it was able to mount the sdcard now.
not sure if this random success or a fix. it worked.
Had the same exact issue. Sprint tech replaced the phone for me for $35 without insurance. But basically the internal memory would only mount once every 10-100 reboots.
Definitely a manufacturing issue.
obsanity said:
Had the same exact issue. Sprint tech replaced the phone for me for $35 without insurance. But basically the internal memory would only mount once every 10-100 reboots.
Definitely a manufacturing issue.
Click to expand...
Click to collapse
Have you tried reflashing the recovery twice?
Did the sprint tech provide the details on what exactly the issue was?
In my case, the phone is contract free and I have to approach samsung support if this issue occurs again.
Since the sdcard is some times mounting, i am hopeful that there should be a way out via sw.
gsrdemon said:
Have you tried reflashing the recovery twice?
Did the sprint tech provide the details on what exactly the issue was?
In my case, the phone is contract free and I have to approach samsung support if this issue occurs again.
Since the sdcard is some times mounting, i am hopeful that there should be a way out via sw.
Click to expand...
Click to collapse
Samsung service center repaired the device (mother board replaced); in warranty.
Sent from my Nexus S
EDIT: Screw it. Odining stock and seeing what happens. *shrugs*
So if anyone points me towards an existing thread. I did search. CyanogenMod Hard Reset, CM Hard Reset, CM can't reset, etc. If there is something out there I missed. Sorry.
ANYWAYS! So I want to get off of Cynanogenmod. Right now my system is encrypted. So I figured I need to get that removed before I ODEN back to stock. I go into Backup & Reset -> Factory Data Reset. It reboots, has the green android with the spiny icon in its stomach for about 10 seconds, reboots, and nothing happens. It prompts me to get past encryption, and back into CM. No reset.
Also it won't allow me to decrypt in CM either.
I'm currently on 10.0.0-d2vzw \ Kernel 3.0.48 -cyanogenmod-ge67063c
I tried upgrading to the latest and greatest nightly under about. I download it successfully the system reboots, it goes into clockworkMod v6.0.1.2 and I get the following
Finding Update Package...
E: Can't mount/sdcard/cmupdater/cm-10.1-20130115-NIGHTLY-d2vzw.zip
Installation aborted.
service.adb.root=1
init.svc.adbd=running
Finding update package...
I: Update location: /sdcard/cmupdater/cm-10.1-20130115-NIGHTLY-d2vzw.zip
I: using /data/media for /sdcard/cmupdater/cm-10.1-20130115-NIGHTLY-d2vzw.zip
W: failed to mount /dev/block/mmcblk0p15 (Invalid Arguments)
E: Can't mount/sdcard/cmupdater/cm-10.1-20130115-NIGHTLY-d2vzw.zip
Installation Aborted
I: Can't partition non-vfat: datamedia
I: Can't partition unsafe device: /dev/block/mmcblklpl
I: Can't format unknown volume: /emmc
Soooo! I go boot into clockwork mod, select factory reset and get
Formatting /data
Error mounting /data!
Skipping format...
Formatting /cache
formatting /sd-ext...
formatting /sdcard.android_secure...
error mounting /sdcard.android_secure...
skipping format...
Data wipe is complete.
So I can't wipe a drive if its encrypted?!? HELP! Any ideas? Might I be able to ODEN over this with the factory image or is there a corruption that might brick my system?!
I just bought this Note 4 and I am doing a factory reset but I get this error when I choose wipe data/factory reset.
My phone shows as follows
-- preload checkin...
E:failed to mount /preload (No such file or directory)
Data wipe complete.
The phone is wiped and it seems to operate normally, but this error bugs me, anyone have any ideas? My assumption from looking around the web is that this phone has been rooted before, if so how do I reset things back to factory? How can I tell if it's still rooted?
FYI, I have updated to Lollipop and I am familiar with using ODIN. Once again this is a Note 4.
Thanks in advance...
Shield tablet neverending loop
Hello guys,
Today I've tried flashing my Shield Tablet using Shield Custom ROM guide from by cots from gbatemp.net forums (can't post links).
Despite doing everything carefully, step by step, my Shield is now rebooting forever showing only one screen and rebooting again.
Unfortunately I can't post a picture, because forums rules don't allow me, so I wrote down the text from TWRP:
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'.
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'.
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands...
E:Unable to mount '/data'
--Wiping Data Partition...
Formatting Cache using make_ext4fs function.
E:Unable to mount '/data'
--Data Partition Wipe Complete!
Done processing script file
aaaaand it reboots.
Pressing "Home" and/or "Back" button at that TWRP screen does nothing, Shield is still rebooting to that screen over and over again.
Help would be greatly appreciated. Any ideas?
Best regards,
Łukasz
I had the same problem; the same thread that you referred to had a post yesterday on resolving this issue. This worked for me.
Re-do all the steps except that before doing the TWRP flash, do a fastboot -w.
Can you boot into twrp? The sequence is: Volume DOWN (keep pressed) + Power (click and release keeping VDOWN pressed)
This should give you access to bootloader mode, where you can eventually reboot into recovery or enable fastboot protocol. So if twrp works you should be able to use the "format" which will fix your corrupted filesystem. Once you've done that you can restore your official OTA, copy your custom rom files again somewhere inside the now-restored filesystem, go back into recovery and flash again (just wipe system, cache and dalvik, nothing else).
If you cannot access twrp, once in bootloader mode you can enable fastboot and flash twrp again via adb from your pc.
Just to clarify, once you're in the bootloader, fastboot is ALREADY enabled and you will need to use fastboot, NOT adb, to flash anything.
so I was trying to flash custom rom and everything go just fine and then for the flashing repartitoner part my phone just restart itself for some reason after the flashing and I thought everything should've been normal but it's not for the part that I flash customrom.zip I started noticing "can't mount /data /system /system_root /cache (invalid argument) and I think it's easy to find tutorial how to fix them on youtube
here's what I found on youtube and tried
1.wipe everything (not working and can't even mount anything)
2.format data(yep still impossible it's just red and say "failed to mount"
3.change filesystem(yep still impossible)
my phone is samsung j7 2016 (j7xelte) or sm-j710f
here's the clip (of me trying every ways to fix the problem
sorry if my english is bad
this is the log I got from advanced > copy log
nvm fixed using twrp/orangefox terminal and delete /data /cache /system /vendor folder and then try to "repair partition" and now it says that it's presented now