So i checked log, and was spit out this.
Unexpectated string line 2: col12
Also lower down,
Cant partition non-vfat: datameadia "assuming I need to mount data maybe"?
Cant partition unsafe device: /dev/block/mmcblklp1 (on VZW-SGS3 unlocked?)
Cant format unkown volume: /emmc (I mounted it but never wanted to format?
Here is script
Ive gotten really pissed at this.....
http://pastebin.com/9j6WJXy9
Related
So I flashed Simply Galaxy 3.0 JVB 2.3.3, and somehow it went wrong. Out of frustration i can't remember the exact result. Anyway, I odined back to stock but it gave me the black screen of death after the boot logo. So i odined to eugene's froyo that not bricks. It boots, but now I have 0.00B of application storage.
I think i tried every possible solution but still can't get the app storage back.
edit: forgot to mention that i can't flash roms through cwm as many errors pop up, here's what happens:
installing update... formatting system... formatting cache... formatting datadata... formatting data...
e:can't mount /dev/block/mmcblk0p2 (file exists)
error mounting /data/!
skipping format... deleting files...
e:can't mount /dev/block/mmcblk0p2 (file exists)
deleting files... copying files...
e:can't mount /dev/block/mmcblk0p2 (file exists)
e:can't mount DATA:
e:failure at line 15: copy_dir PACKAGE:data DATA:
installation aborted.
*I found this thread for the fascinate, is it safe to flash on the vibrant?
Help would be greatly appreciated!
do not flash anything that isn't fixed for use on the vibrant.
ODIN jfd to your phone and see if that fixed your phone.
I think i did that, I used the .tar/.pit provided by AIO Vibrant Toolbox
EDIT - flashed JFD to be sure - I get the boot logo for a few secs > black screen > boot logo again and so on...
Update - I managed to get 250MB app storage using parted(now i am able to flash through cwm again), it looks like this:
Number Start End Size Type File system Flags
1 512B 15.7GB 15.7GB primary fat32 lba
2 15.8GB 16.0GB 247MB primary fat32 lba
Now I need to expand partition 2 since 250MB isn't enough especially when i only have like 60MB left with no apps at all.
So I guess i need to unmount /system and resize it to approx 13GB, but CWM won't allow me to unmount(error unmounting system:!). Here's where I need your help
Cwm wil not allow you to unmount a running partition it's being used by the phone..I'll need to follow the guide precisely..at this step you hv to delete the partitions completely and then flash with Odin with the partitions option checked...and Odin wil take care of the partition size mismatch..the actual problem here is sumhow the phone makes a partition record tht doesn't exist...so the error in cwm abt the error mounting...hope this helps..
german103 said:
update - i managed to get 250mb app storage using parted(now i am able to flash through cwm again), it looks like this:
Number start end size type file system flags
1 512b 15.7gb 15.7gb primary fat32 lba
2 15.8gb 16.0gb 247mb primary fat32 lba
now i need to expand partition 2 since 250mb isn't enough especially when i only have like 60mb left with no apps at all.
So i guess i need to unmount /system and resize it to approx 13gb, but cwm won't allow me to unmount(error unmounting system:!). Here's where i need your help
Click to expand...
Click to collapse
how did you do that ???
Despite the fact that I had a lot of headache figuring this out, I don't remember for 100% what exactly I did.
What is your current partitions layout in parted?
replay
thanks dude it's work
Hi... Recovery's cant mount /data /system /cash and internal storage, I dont know what to do with that. I had sex with this problem for three days, and I found out that:
may be its broken one of the Partition. I have tried to fix it like in this solution http://forum.xda-developers.com/showthread.php?t=1949372
After six hours of sex, trying to find right adb driver and orher things, I'm stuck in a problem, that Parted cant list my partition table on /dev/block/mmcblk0, it says "Unable to satisfy all constraints on the partition". Fdisk show me this
http://hostingkartinok.com/show-image.php?id=2f324a6a8ce1541abfaaead675a4161b
and Cat this
http://hostingkartinok.com/show-image.php?id=80da3c65fad0cc52f1b7ed6e4936f066
So, i try to delete /data /cash and /system partition (/mmcblk0p20, /mmcblk0p16 and /mmcblk0p14), via
"parted /dev/block/mmcblk0
rm 14"
, for exemple, but it says "Unable to satisfy all constraints on the partition" again. So i cant use this guide
But! I cant mount /data /cash and /system, but if I use, for exemple in CWM "- format /data and /data/media (/sdcard)" item in "- mounts and storage", it will mount and format all I need. Than I can install ROM's and other zip's and all these things will even work... for a while. Some restarts of my phone (not sure), or entering in Recovery will give me bootloop.
:crying: I cant understand, why it can format and mount in the case of the one and only item and cant if I try to use any else.
Please... help
Oh, yes, The phone is LG p705 (or p700). Recovery is any. CWM or TWRP, any version...
Hi,
after flashing a custom ROM which did not work as expected, I got "E: unable to mount ..." errors.
After investigating I formated the preload and mounted preload manually in the recovery.
Somehow my SCARD now shows additional "/0" in the path to the data, leading to data being unable to be found.
e.g. to the download folder is now located in SDCARD/0/0/0/DOWNLOAD.
I assume this happened when mounting the preload or other folders maually?!
How can I get this back?
I do not tink this is realted to any ROM or device, but I am on OMNIRom 4.4.4, CWM 5.5., GTAB 7510 Wifi
Thanks
xdatroxx
"Preload" seems to be A system partition, secondary for preloaded system apps, so you really should not be mounting that to SDCARD (internal storage) unless it's unused by the roms and you know what your doing/want that partition for personal use.
If the rom gave you that error(unable to mount..) right after installing it then I would not recommend the ROM.
Can you access SDcard eg. use the files?
sdcard should normally be seen as:
/sdcard
or:
/storage/emulated/0(or legacy)
you can mount the partitions correctly but you have to find the right partition layout for your gtab.
Hi Guys,
I'm pretty new here and hoping you can all help me with unbricking my phone.
So I have a Samsung S3 I9300, with CM 13.0 installed, I am using CW recovery v2.7.0.0
I've installed many custom ROMS to this device over the past few years without a problem, each time formatting and wiping Dalvik cache etc..
Today my phone randomly rebooted and a message came up that my phone failed to encrypt and it wiped all my data and that I had to reboot into recovery to perform a factory reset.
A bit random I thought.. So I rebooted into recovery and did a "reset to default" in CW.. this was successful, however I noticed some issues on the terminal screen...
Code:
E: Unable to find partition size for /boot
E: Unable to find partition size for /recovery
E: Primary block device /dev/block/mmcblk0p12 for mount point is not present!
E: Unable to mount internal storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /cache
Full SELinux support is present
E: Unable to mount /cache
E: Unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount /data
Updating Partition details...
E: Unable to mount /efs
E: Unable to mount /data
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /preload
E: Unable to mount internal storage
I've tried to format but it shows failed.
I cannot install another ROM as both the internal memory and SD card both show 0MB
I've plugged the SD card into my computer and there are still files on the card.
I've had a look online and found that typing in a command into the terminal should fix it, however nothing happens..
I get an error that mmcblk0p12 does not exist.
Code:
mke2fs /dev/block/mmcblk0p12
Any help would be great! Although i'm pretty sure it's bricked
Cheers Guys!
Chris
Gizzy00360 said:
Hi Guys,
I'm pretty new here and hoping you can all help me with unbricking my phone.
So I have a Samsung S3 I9300, with CM 13.0 installed, I am using CW recovery v2.7.0.0
I've installed many custom ROMS to this device over the past few years without a problem, each time formatting and wiping Dalvik cache etc..
Today my phone randomly rebooted and a message came up that my phone failed to encrypt and it wiped all my data and that I had to reboot into recovery to perform a factory reset.
A bit random I thought.. So I rebooted into recovery and did a "reset to default" in CW.. this was successful, however I noticed some issues on the terminal screen...
Code:
E: Unable to find partition size for /boot
E: Unable to find partition size for /recovery
E: Primary block device /dev/block/mmcblk0p12 for mount point is not present!
E: Unable to mount internal storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /cache
Full SELinux support is present
E: Unable to mount /cache
E: Unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount /data
Updating Partition details...
E: Unable to mount /efs
E: Unable to mount /data
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /preload
E: Unable to mount internal storage
I've tried to format but it shows failed.
I cannot install another ROM as both the internal memory and SD card both show 0MB
I've plugged the SD card into my computer and there are still files on the card.
I've had a look online and found that typing in a command into the terminal should fix it, however nothing happens..
I get an error that mmcblk0p12 does not exist.
Code:
mke2fs /dev/block/mmcblk0p12
Any help would be great! Although i'm pretty sure it's bricked
Cheers Guys!
Chris
Click to expand...
Click to collapse
Did you have any success with this, Chris?
This sounds like what happened to my I9300 on CM12.1. It just froze and only rebooted to Samsung logo and stayed there.
When in TWRP recovery, there's just no access to internal memory or SD card.
The terminal mentions a lot of "E: unable to mount /data", /cache, /system, storage, etc
Most TWRP options fail to do anything, because of not being able to access partitions.
No factory reset, no wipes, no installing img's. When rebooting to system, it warns about no OS being installed.
Downloading a stock firmware now to see if it flashes via ODIN, but I don't have high hopes for it.
Does anybody know what would cause this? Or is it just bricked now?
petitgregory said:
Did you have any success with this, Chris?
This sounds like what happened to my I9300 on CM12.1. It just froze and only rebooted to Samsung logo and stayed there.
When in TWRP recovery, there's just no access to internal memory or SD card.
The terminal mentions a lot of "E: unable to mount /data", /cache, /system, storage, etc
Most TWRP options fail to do anything, because of not being able to access partitions.
No factory reset, no wipes, no installing img's. When rebooting to system, it warns about no OS being installed.
Downloading a stock firmware now to see if it flashes via ODIN, but I don't have high hopes for it.
Does anybody know what would cause this? Or is it just bricked now?
Click to expand...
Click to collapse
Hey there,
Nope the cmd I found on-line I found (above) didn't work.
Its currently just stuck on the Samsung splash screen and fails to do anything.
Gizzy00360 said:
Hey there,
Nope the cmd I found on-line I found (above) didn't work.
Its currently just stuck on the Samsung splash screen and fails to do anything.
Click to expand...
Click to collapse
Ah well, mine seems dead too. The recovery doesn't work anymore, only download mode, but ODIN can't get anything on it...
I think the main storage just died.
petitgregory said:
Ah well, mine seems dead too. The recovery doesn't work anymore, only download mode, but ODIN can't get anything on it...
I think the main storage just died.
Click to expand...
Click to collapse
Damn, I dunno what happened.. My CM was a nightly though, SO I can only assume it was unstable.
Just bizarre how my phone rebooted and gave the message that it was unable to encrypt the device and needed to be factory reset.
Gizzy00360 said:
Damn, I dunno what happened.. My CM was a nightly though, SO I can only assume it was unstable.
Just bizarre how my phone rebooted and gave the message that it was unable to encrypt the device and needed to be factory reset.
Click to expand...
Click to collapse
I was running a quite stable CM12.1 version for a couple of months now. Only had two reboots all this time.
petitgregory said:
I was running a quite stable CM12.1 version for a couple of months now. Only had two reboots all this time.
Click to expand...
Click to collapse
I had a few reboots when it was working, then it just suddenly bricked my phone
Sounds like the eMMC brickbug. You need to get the eMMC replaced. All of you that face the problems.
Well, after four years my S3 was getting very slow. It was bearable with CM, but I decided to say farewell now.
Also, my microphone was busted when I dropped it at some point, so I could only call with a headset anyway.
It's not worth replacing I think, time to move on
The same happened to my Beelink GT1 S912 9377 TV-box (after failed OTA update). Will check eMMC brickbug (from TWRP) ...
Hi all.
I'm trying to make a last backup of the stock Android of my Swift 2x before flashing LineageOS. But TWRP (version 3.3.0-0) Seems unable to use the /data partition. I got various messages like:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid Argument)
I tried to format the partition: Wipe -> advanced wipe -> repair or change filesystem -> change filesystem -> ext4 but it didn't change anything.
What's wrong? What can I do?
Thanks a lot for any hint.
bumping this thread as I also ran into this issue.
When using TWRP, the data and system partitions can't be mounted. they also show up as being 0mb in size.
Because of this, no backups can be made and a full system wipe also yields errors.
What I did was change the filesystem to ext2 and then change it back again to ext4.
Doing this at least allowed me to flash crdroid, but making backups still doesn't work.
Whenever i go into TWRP again, it's the same thing again: unable to mount and partitions show up as 0 mb in size.
Anyone know what's causing this?
Wileyfox encrypts there data when you factory reset your device or after youve rooted your device .To get around this you need to do a factory reset using stock recovery once thats done then turn off the device. Then using minimum adb and fastboot type (fastboot boot twrp.img) that will boot your already installed twrp now erase data internal storage etc you'll notice you can finally delete stock os youll see internal storage is showing mbs available again etc worked for me perfectly.