Database Info

Boot loop Unresolvable? Hardware problem?

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

stuck on boot logo

hi
at first i have to say my English is not good!!
i have a tf700 and last night i installed CROMBi-kk on it after that because of lots of apps that i installed in past it had lots of lag then i decided to wipe my data so i went to twrp and did a full wipe but in middle of that battery ran out. i install CROMBi-kk again but it stuck on boot logo!!!
i think there is no partition on it!!
UNFORTUNATELY I DON'T HAVE ANY BACKUP!!
PLZ HELP!!!!!
thank you!!

Need more information.
Which bootloader are you on?
Which kernel are you on?
Which kernel did you choose?
Internal install? rom2sd? data2sd?
Which options?
recovery.log?
aroma.log?

sbdags said:
Need more information.
Which bootloader are you on?
Click to expand...
Click to collapse
android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.10-20130801" a03
sbdags said:
Which kernel are you on?
Which kernel did you choose?
Click to expand...
Click to collapse
_that modded Asus OC Kernel v10
sbdags said:
Internal install? rom2sd? data2sd?
Click to expand...
Click to collapse
internal install
sbdags said:
Which options?
Click to expand...
Click to collapse
data journaling is enable
sbdags said:
recovery.log?
aroma.log?
Click to expand...
Click to collapse
E:could not mount /data and unable to find crypto footer
E: unable to mount ' /data '
E: unable to recreat /data/media folder.
Updating partition details. . .
E: unable to mount ' /data '
E: unable to mount internal 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.
E: no valid storage partition found for MTP
E: unable to mount ' /data '
E: unable to mount ' /data '
in bootloader there is a line that say " key driver not found.. booting os
on detecting file system phase :
/data on internal (UDA) -> unknown

hoseinkh said:
android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.10-20130801" a03
_that modded Asus OC Kernel v10
internal install
data journaling is enable
E:could not mount /data and unable to find crypto footer
E: unable to mount ' /data '
E: unable to recreat /data/media folder.
Updating partition details. . .
E: unable to mount ' /data '
E: unable to mount internal 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.
E: no valid storage partition found for MTP
E: unable to mount ' /data '
E: unable to mount ' /data '
in bootloader there is a line that say " key driver not found.. booting os
on detecting file system phase :
/data on internal (UDA) -> unknown
Click to expand...
Click to collapse
Ignore the key driver message - we all get it.
So you /data partition is not in a recognisable format and cannot be mounted. Please format it in TWRP or from adb use this command when in TWRP (make sure MTP is turned off)
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
or in the bootloader use this:
Code:
fastboot erase userdata

sbdags said:
Ignore the key driver message - we all get it.
So you /data partition is not in a recognisable format and cannot be mounted. Please format it in TWRP or from adb use this command when in TWRP (make sure MTP is turned off)
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
or in the bootloader use this:
Code:
fastboot erase userdata
Click to expand...
Click to collapse
Code:
C:\adb>fastboot erase userdata
^C
C:\adb>
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ killall -19 recovery
killall -19 recovery
killall: recovery: no process killed
1|[email protected]:/ $ make_ext4fs /dev/block/mmcblk0p8
make_ext4fs /dev/block/mmcblk0p8
Need size of filesystem
1|[email protected]:/ $ reboot
reboot
reboot: Operation not permitted
1|[email protected]:/ $
how to turn off mtp??
when i select format data from TWRP it stuck on " formatting data using make_ext4fs function" and even after 30 min nothing happen!!

thank you man!!
it's finally worked!!
Thank you for your attention and answers!!

hoseinkh said:
thank you man!!
it's finally worked!!
Thank you for your attention and answers!!
Click to expand...
Click to collapse
You are welcome!
Which one worked?

sbdags said:
You are welcome!
Which one worked?
Click to expand...
Click to collapse
Code:
fastboot earase userdata

erase data failed
I just get the following:
fastboot earase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
device is unlocked, hang in bootloop, tried flashing but:
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount /data/meida/TWRP/ . twrps when trying to read settings file.
E: No valid storage partitions found for MTP.
E: Unable to mount '/data'
E: Unable to mount '/data'
thanks for your answers.

homer56 said:
E: Unable to mount '/data'
Click to expand...
Click to collapse
In TWRP, go to wipe -> advanced -> format data. This can take more than an hour, so be patient.

[Q] Soft bricked tab (GT-P3100)

Hello guys I've run into a weird problem.
I installed SlimLP alpha builds, everything was fine. One day, after trying to format /system etc. before flashing latest version, the tab started rebooting itself every 20 seconds. I tried to uninstall some apps, when I rebooted the tab the apps were back. I booted back into CWM recovery and when I tried to flash old version of this rom, it just stuck at the start. Moreover, when I try to exit recovery it always says "Root access probably lost. Fix?" But that does nothing.
I went into Odin and tried flashing two different stock roms, but it gave error "Complete(Write) operation failed" at system.img .It displayed my model number as "i9505" I then tried to flash through old Odin(v1.75) and it worked. But when I rebooted, it went back into SlimLP. I tried flashing TWRP and latest cwm version but it went back to previous version. The "download count" in Download Mode remained constant. I tried formatting /system and /data through cwm. There was no error but tab still boots straight into SlimLP.
I then tried my luck with ADB in cwm by trying to change file permission. With "chmod 755 /system" it gave the error "Read-only file system" With "mount" , it gave error "Operation not permitted". I booted into slimlp, quickly enabled root for "apps and ADB" through developer options and tried the commands but same error.
I also tried "NAND wipe all" in Odin, but it stuck at "Erase...." and then gave error after sometime.
Is there a way to completely wipe the OS now so I can flash stock one through Odin?

Which recovery version of cwm you have? Probably it will be lower than 6.0.4.4

It is 6.0.4.5

If you're tab still boots then try installing twrp using app called rashr

Tab reboots after 20 seconds, can't install app in that duration.

I9505 means you flashed the wrong firmware to your tablet, I 9505 is an international S4 phone rom.
You need a new tablet.
Reading is very important when it comes to flashing your Samsung devices.
Pp.

PanchoPlanet said:
I9505 means you flashed the wrong firmware to your tablet, I 9505 is an international S4 phone rom.
You need a new tablet.
Reading is very important when it comes to flashing your Samsung devices.
Pp.
Click to expand...
Click to collapse
I downloaded the correct firmware from sammobile, checked many times. Also, I flashed from other Odin version, which didin't display any model number. I just checked Odin3, and even without the device connected, it displays i9505 at top.
EDIT: Well downloaded Odin3 from another site, It didn't show any model number. Guess "i9505" was just a title edit.

I think there is a big in cwm, there are many having this problem with that recovery, all Android andi about it, try sending private message to him, our some other developer

Thanks, I'll try that and post it here.

Please do the following:
Boot/try to boot system
Try to get a dmesg using adb
Boot into recovery
Use adb to pull last_kmesg
Please get a recovery.log after wiping.
Attach the files here.
Send from OnePlus One using Tapatalk

Android-Andi said:
Please do the following:
Boot/try to boot system
Try to get a dmesg using adb
Boot into recovery
Use adb to pull last_kmesg
Please get a recovery.log after wiping.
Attach the files here.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
I tried the commands like "adb shell dmesg > dmesg.txt" But got error "access is denied" Then I copied dmesg from console window, and pulled other files.

ssqw1 said:
I tried the commands like "adb shell dmesg > dmesg.txt" But got error "access is denied" Then I copied dmesg from console window, and pulled other files.
Click to expand...
Click to collapse
Can you upload the cwm you flash first and send me on pm?
Want to check if it's for our tab.
Will check your logs later.
Send from OnePlus One using Tapatalk

Did you used rommanager for cwm?
Send from OnePlus One using Tapatalk

Nope

Looks like a broken EMMC...
Please boot into recovery and use "adb shell":
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p9 /system
if it mounts without problems do the same for data
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p10 /data
Moutns without problem?
Please unmount now.
Code:
adb shell umount /system
adb shell umount /data
Let´s try to check the partitions now:
Code:
adb shell e2fsck -vf /dev/block/mmcblk0p9
adb shell e2fsck -vf /dev/block/mmcblk0p10
if you got error messages, please inform me.
Maybe we can reformat the partition by using adb shell.

Android-Andi said:
Looks like a broken EMMC...
Please boot into recovery and use "adb shell":
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p9 /system
if it mounts without problems do the same for data
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p10 /data
Moutns without problem?
Please unmount now.
Code:
adb shell umount /system
adb shell umount /data
Let´s try to check the partitions now:
Code:
adb shell e2fsck -vf /dev/block/mmcblk0p9
adb shell e2fsck -vf /dev/block/mmcblk0p10
if you got error messages, please inform me.
Maybe we can reformat the partition by using adb shell.
Click to expand...
Click to collapse
It mounts without problem. Here are the results for checking:
First command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell e2fsck -vf /dev
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
1699 inodes used (2.59%)
16 non-contiguous files (0.9%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1355
182363 blocks used (69.57%)
0 bad blocks
0 large files
1148 regular files
207 directories
0 character device files
0 block device files
0 fifos
0 links
335 symbolic links (335 fast symbolic links)
0 sockets
--------
1690 files
Second:
Code:
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p10: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>?
It doesn't proceed, tried typing Y, Yes and all other keys.

Can you give me the output from:
Code:
adb shell ls -l /dev/block
Please from recovery and booting rom.
Have you tried flashing stockrom + pit file to repartition?
Send from OnePlus One using Tapatalk

For reference http://forum.xda-developers.com/showthread.php?t=2627490
Send from OnePlus One using Tapatalk

Please give me mount output too.
Code:
adb shell mount

Sorry for the late reply, here are the files.
EDIT: I tried flashing the pit file with stock rom 2 times with Odin version 1.75, it flashed successfully but tab booted straight into SlimLP again.

Stucked in TWRP

I had LinegeOS installed on my xperia. But don't have root. I wanted to install root addon, but didn't have TWRP because previous time I just temporary boot with
fastboot boot twrp.img
Now I do the same fastboot boot twrp.img
and flash the root addon. I got this error Failed to mount /data invalid argument but also got successful flashed or something like that.
When I press Reboot > System it reboots in TWRP
I tried to flash LineageOS but I get error:
Code:
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, asuming f2fs
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /date: No such device unmount of /data failed: no such volume
Patching system image unconditionally
Updater process ended with signal: 7
Error installing
Failed to mount /data
Is there a way to fix that without losing data ?
In TWRP file manager I see the system folders

try to boot on the latest twrp by fastboot boot twrp.img then wipe system then try to install the rom again.
copy the twrp.img to the internal memory
After booting download and flash the latest SuperSU then install terminal then type "su" then grant root access, then flash the TWRP on the FOTAKernel PArtition by
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

Can't mount vendor and system image as RW

I try to mount system and vendor partitions by using command below
Code:
sudo mount -o loop -t ext4 vendor.img vendor
got this error message
Code:
mount: xxx/xxx/vendor: wrong fs type, bad option, bad superblock on /dev/loop20, missing codepage or helper program, or other error
This command use to work on system image on different phone with same android version.
But I'm able to mount as RO using achieve mounter on Ubuntu.
Is there any way that I can mount those image as RW then edit some file in there?

OOS locks the system partition. No way in as of yet.

BeardKing said:
OOS locks the system partition. No way in as of yet.
Click to expand...
Click to collapse
Thank you