Hey all, new to xda. Hope I'm not asking stupid questions.
My friend gave me a Galaxy S to fix. Model: GT-I9003.
It has a boot loop problem, cycling the Samsung introduction animation (and sound first time round). The recovery mode didn't work to start with - also trapped in a boot loop.
I followed the instructions here (using Odin3 v1.85) and flashed XXKPE. It seemed to all work fine, but the boot loop remained. I booted it into recovery mode and the following error messages appear.
E:failed to mount /data (No such file or directory)
Click to expand...
Click to collapse
and under -- Wiping data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p3
Click to expand...
Click to collapse
then
Data wipe failed.
Click to expand...
Click to collapse
From my research I believe it's a corrupted internal SD-Card and is fixed via parted? Could anyone go into more detail on how I would do this?
Many thanks.
I am facing a similar problem on my Galaxy SL... Need a solution too... I would appreciate any help...
Data partition has been corrupted, try flashing userdata.rfs with heimdall. A friend of mine had an stock/untouched phone and this happened to it, even with the corrupted partition i was able to boot cyanogenmod, and tried a lot of things, but nothing worked, it was on warranty, so i flashed back the original firmware and he took it to the service center.
If you want to try do this:
Flash bam kernel PDA_BCK_CF-root_universal_beta14fix.tar (http://forum.xda-developers.com/showthread.php?t=1355675)
Then from CWM flash cyanogenmod (i used cm7, but you can try with cm9)
after that the phone should boot into cyanogemod and give an error on the notification bar
extract the 6 files off the zip i attached and copy them to /xbin
from terminal emulator or adb shell run this for the 6 files:
Code:
chmod 0755 <file>
then run:
Code:
parted /dev/block/mmcblk0 mkfs ext2
When it asks for the partition number, enter 3
finally reboot, and if it worked you can flash a stock rom again, thats it, good luck
My phone boots up, but there are random reboots. Tried a lot of stock and custom ROMs... Nothing works... Warranty expired last week...
Thanks for your time. I appreciate it.
bruisedcrow said:
Thanks for your time. I appreciate it.
Sorry, I'm very new at this - my first hour doing this kind of thing. Could you explain the procedure in more detail - I would like to learn (make the best of a bad situation).
Am I right to say that the Bam Custom Kernel gives super-root level privileges? Allowing the CWM to fiddle with partions?
I've downloaded the normalboot.img for BCK. How do I flash this to my device? Could you link me to a tutorial?
EDIT: Alternatively could you point me to all the prerequisites I need to properly understand the problem and the methods required to fix it?
Click to expand...
Click to collapse
I tried that... My phone was booting up...
I have Android SDK on my PC... It includes some tools like ADB.
If your phone is rooted, you can use ADB to do things, like formatting...
Connected my phone. Booted into recovery. From Command Prompt, I went to ADB folder, then typed "adb shell". Then, typed in the parted command, and followed steps. Successfully done...
But the problem continues...
I have found many other users have faced this problem -- http://forum.xda-developers.com/showthread.php?t=1736118
I am disappointed. My phone is no longer in warranty... I am too late...
it is possible that using cyanogenmod and S2E (simple2ext) will work as a workaround until you send it to service center.
grab a copy of s2e and push it to /system/app/
Repartition your External-SD using the same method used for phones with low storage capacity, warning: it will erase all the data in it, so make backups
Start s2e and mark to move:
App and Private app
Applications data
Dalvik and download cache
This makes another partition, and it does not fix data, but at least you should be able to install apps.
I face this problem too. Please someone give us the solution.
Update: I flashed BAM Custom Kernel and put it in recovery mode. Attached it to the computer, but I'm stuck at this error message.
Thanks again.
More information
EDIT: There doesn't seem to be a /data partition at all! I feel I'm getting closer to fixing this.
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
alfrix said:
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
Click to expand...
Click to collapse
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
bruisedcrow said:
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
Click to expand...
Click to collapse
I think that the problem is when /tmp/updater.sh tries to mount /emmc your internal memory (EDIT: I've just noticed you tried with CM7, so, if I remember correctly, /emmc is the external memory, but I think that the problem is always the impossibility to mount the internal memory.) to backup your /efs directory. Because of the not avaible internal memory (/emmc) it simply exits and aborts the installation.
A simple change in updater.sh will allow you to install CyanogenMod, but wait for a confirmation from alfrix, maybe there's something more.
Anyway here there's a thread of a user with the same problem, he solved this by using the external SD as internal SD, as alfrix suggested.
strange, before touching anything try with the release i used that time (14.12.2011), if it doesn't work, then edit the updater.sh and remove
Code:
if ! /tmp/busybox mount -t ext4 /dev/block/mmcblk0p3 /data ; then
/tmp/busybox umount /data
/tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p3
fi
EDIT: is there any mmcblk on /dev/block?
Code:
ls /dev/block/
Weird the has mmcblk0 reappeared.
Code:
~ # ls /dev/block
ls /dev/block
bml0!c bml6 loop6 ram13 ram9 stl6 tfsr2
bml1 bml7 loop7 ram14 stl1 stl7 tfsr3
bml10 bml8 mmcblk0 ram15 stl10 stl8 tfsr4
bml11 bml9 mmcblk0p1 ram2 stl11 stl9 tfsr5
bml12 loop0 platform ram3 stl12 tfsr0!c tfsr6
bml13 loop1 ram0 ram4 stl13 tfsr1 tfsr7
bml2 loop2 ram1 ram5 stl2 tfsr10 tfsr8
bml3 loop3 ram10 ram6 stl3 tfsr11 tfsr9
bml4 loop4 ram11 ram7 stl4 tfsr12
bml5 loop5 ram12 ram8 stl5 tfsr13
So I tried
Code:
C:\Users\Bruised>adb shell
~ # /sbin/parted /dev/block/mmcblk0 mkfs ext2
/sbin/parted /dev/block/mmcblk0 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
/sbin/parted: invalid token: ext2
Yes/No? y
y
y
Partition number? 3
3
3
Error: Partition doesn't exist.
~ #
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
alfrix said:
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
What should I try next? 14.12.2011 download link is down.
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
alfrix said:
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
Click to expand...
Click to collapse
It installs it.
Code:
Checking state of RFS/EXT4...
Install from sdcard complete.
After I reboot CM9 boot screen loads then I get "Encryption unsuccessful" as shown here
After rebooting I get
Code:
CWM-based Recovery v5.5.0.4
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
Formatting /cache...
Data wipe failed.
Heres the log file from the sdcard:
Code:
+ /tmp/busybox test -e /sdcard/backup/efs/nv_data.bin
+ /tmp/busybox mount -t ext4 /dev/block/stl9 /system
+ /tmp/busybox mount -t ext4 /dev/block/stl10 /dbdata
+ /tmp/busybox mount -t ext4 /dev/block/stl11 /cache
+ /tmp/busybox umount -l /system
+ /tmp/busybox umount -l /cache
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument
+ /tmp/busybox umount -l /dbdata
+ /tmp/busybox umount -l /efs
umount: can't forcibly umount /efs: Invalid argument
+ exit 0
Hello guys,
I recently installed CWM on my GoClever device.
Booting into recovery from Android using ROM Manager didn't work, so I tried
Code:
su "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
And I booted in CWM right after it rebooted
but when I tried to boot the device back to Android, it booted to CWM.
Also the CWM is unable to mount any of the directories.
Code:
CWM-based Recovery v6.0.1.2
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /open/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
ADB should work I guess
Could anyone help me please? I guess it's not hard to fix this, probably some file modifying, but I don't really know what exactly to do... :/
EDIT: A recovery image that boots into Android instead of recovery would be a neat solution, but I'm not sure if it's possible
LAST EDIT [SOLVED] :
hajdulak said:
So I flashed an officcial firmware from this thread:
http://forum.xda-developers.com/showthread.php?p=36674128
Using this method:
http://www.goclever.com/manuals/update_a93_en.pdf
Didn't know the img contained a recovery image. Thank you XDA, for being helpful again
I really appreciate it
-> [SOLVED] pretty please
Click to expand...
Click to collapse
Well, i guess A13's will never get some solid support... At least I got my 10 posts... Weeee!
Guys, what's with all the views and no answers?
After some googling, I found out it's quite a frequent issue, but none of the googled threads helped in any way... Damn it...
Also, A13 devices have SOOOOO low support...
And an important thing
I got a dumped stock recovery img on the /sdcard/, just need to know if I can flash it and how to flash it using ADB, I'm quite afraid of doing anything now
Soooo...
When the device is plugged in, it identifies itself as "MID08"
Seems i installed a wrong recovery image
Now I need drivers for my TAB, as it can't appear in the
Code:
adb devices
menu... :/
If anyone can really help, this is a list of my blockdevices:
Code:
loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 nandf ram0 ram1
And this is my fstab
Code:
/dev/block/nandh /cache ext4 rw
/dev/block/nande /data ext4 rw
/dev/block/nandi /emmc auto rw
/dev/block/nandd /system ext4 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
And this is recovery.fstab
Code:
# mount point fstype device
/boot emmc /dev/block/nandc
/cache ext4 /dev/block/nandh
/data ext4 /dev/block/nande
/emmc auto /dev/block/nandi /dev/block/nandi1
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/nandd
/recovery emmc /dev/block/nandg
Also when I try to cd to some dirs i get can't cd to XXX
I guess there's some script that does the mounting stuff, but I still don't know what it is... I just need to access my sdcard and get the recovery image outta there...
So I flashed an officcial firmware from this thread:
http://forum.xda-developers.com/showthread.php?p=36674128
Using this method:
http://www.goclever.com/manuals/update_a93_en.pdf
Didn't know the img contained a recovery image. Thank you XDA, for being helpful again
I really appreciate it
Hi XDA Users,
Before asking help, i would like to say that I'm newbies, i'm little bit lost here, and i don't know if i have the permission to post this question here. Sorry if i make a mistake
I have an error when i try to launch a CWM(Edify) script. :
I:Can't format unknown volume: /external_sd
Click to expand...
Click to collapse
I tried to change updater-binary(No change) and I tried to use empty updater-script: this error is not linked at a command line in my script(No change)
The recovery used is Carliv Touch Recovery porting on my device(Wiko Highway)(link: http://forum.xda-developers.com/showthread.php?t=2471479) he works without problems, but i noticed that i have some bad line in my /etc/fstab. I tried to repack a new .img whith good /etc/fstab version but my device was stay on boot image. I have restore my first recovery.img
My question is: CWM try to mount all partition in /etc/fstab at start of updater-script? And if yes, can i disable this function.
I you see something for my recovery problems, i take all tips!
Thanks for you attention,
Antoine
PS: I have forgot to say that I'm french with a very bad english level, but don't worry, i work on this x)
YES!
I have finally found the error in my recovery: my Fstab has some bad device. Now, it's work!
but update-binary will not work
I have this:
-- Installing: /sdcard/update.zip
Finding update package...
I:Update location: /sdcard/update.zip
Opening update package...
Installing update...
E:Error in /sdcard/update.zip
(Status 0)
Installation aborted.
I:Can't partition unsafe device: /dev/block/mmcblk0p8
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
Click to expand...
Click to collapse
For info, this is my /etc/fstab:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/cache ext4 /dev/block/mmcblk0p6
/data ext4 /dev/block/mmcblk0p7
/misc emmc /dev/misc
/recovery emmc /dev/recovery
/system ext4 /dev/block/mmcblk0p5
/sdcard vfat /dev/block/mmcblk0p8
/sd-ext auto /dev/block/mmcblk0p2
Click to expand...
Click to collapse
I feel that the error is in recovery... but i don't found an fonctionnal ROM for my phone(remember: Wiko Higway)
Thanks for you attention
Bummer
Sent from my One S using xda app-developers app
Can you please give me your recovery for the Highway?
Thank you.
Hi
I've cm-11-20150607-NIGHTLY-i9100 on my Samsung Galaxy SII i9100
It has gapps-kk-20140105-signed (as far as I remember).
I do have cwm 6.0.5.1
Two days ago, there was some update (haven't seen what exactly).
Now, while booting the phone hangs on the boot screen.
When I lunch into cwm-recovery I do see:
CWM-based Revocery v6.0.5.1
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
The show log says:
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Invalid argument
W: failed to mount /dev/block/mmcblk0p7 (File exist)
E:Can't mount /cache/recovery/log
(and more like this)
...
I do have MTP enabled, and debugging USB disabled- this is a big problem since i can not access adb...
I would like to backup data, but how can I enable adb from cwm?
I did try to wipe dalvik (I think it did work) /format cache - It does not work - it hangs.
I did try to "reboot to receovery (or reboot to bootloader): from the cwm- it hangs
I did try to mount /storage/sdcard0 - it hangs
I did try to create a backup from phone memory to scracd1 - it hangs
I can boot into fastboot.
It looks like some error on partition, or problem with internal phone memory.
Anything that try to access internal sdcard0 hangs
How can I backup the phone (or at lest photo - not all were synced yet).
What would be the next step?
Any idea howto enable USB debugging?
I've seen this tutorial
(can add a link so google "enable usb debbuging through clockworkmod with adb")
but it is for the Nexus, not for the i9100...
I do have Ubuntu, with
adb version 1.0.31
I can switch to Windows if it would help...
Ok,
For the moment, I made the wrong assumption.
I can access adb.
The solution was to install latest android SDK (cm11 is some like Android 4.4.4) to get newest adb
(developer.android com/sdk/installing/index.html?pkg=studio )
To be clear, if you're having this same issue the problem is probably an out-of-date SDK. As of 4.2.2 there is a security feature that requires you to confirm the RSA fingerprint of the connecting device. Open the SDK manager and update the tools! Then reboot. - quote from stackoverflow com/questions/14993855/android-adb-device-offline-cant-issue-command
Click to expand...
Click to collapse
stackoverflow com/questions/14993855/android-adb-device-offline-cant-issue-commands
and
having Enabled ADB Integration via Tools > Android > Enable ADB Integration
stackoverflow com/questions/26079838/android-studio-adb-error-device-unauthorized-please-check-the-confirmat
Now I can access
adb shell (while booting into cwm recovery - Power+volUp+Home)
Code:
# parted /dev/block/mmcblk0 print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 159MB 105MB CACHE
8 159MB 176MB 16.8MB MODEM
9 176MB 713MB 537MB FACTORYFS
10 713MB 2861MB 2147MB DATAFS
11 2861MB 15.2GB 12.4GB UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
~ # cat /etc/fstab
/dev/block/mmcblk0p7 /cache ext4 rw
/dev/block/mmcblk0p10 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
~ # mount -o ro -t ext4 /dev/block/mmcblk0p10 /data
mount: mounting /dev/block/mmcblk0p10 on /data failed: Invalid argument
The problem is - I can not backup the data nor mount the /data partition
Sir,
This forum is for helping new users to help members navigate the site, not for support.
I see you've found your device section and already know how things work on XDA.
So please note the sticky from the top of the Assist section and ask directly in this thread for I9100:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck