Database Info

Bootloop! & Can't mount SDCARD

I have a Glaxaxy S SCL i9003 from Spain and after flashing KPE via Odin it booted into recovery and it showed a few errors in red. Then I rebooted the phone and now it shows the first static logo (that says Samsung Galaxy S i9003) and then it loops in the second boot screen (the one with the animated samsung logo)
Booting into recovery shows this:
Code:
E:failed to mount /data (No such file or directory)
-- Copying media files...
E:failed to mount /sdcard (File exists)
E: copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions
Media files copy failed
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEC/system/'
Successfully applied multi-CSC
EDIT: I've now flashed a Froyo ROM. Same problem but different errors in recovery:
Code:
-- Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
lfs pass open fail
-- movi_checking undone!...
update media, please wait...
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E: copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.
¿Any solutions?

ktix007 said:
I have a Glaxaxy S SCL i9003 from Spain and after flashing KPE via Odin it booted into recovery and it showed a few errors in red. Then I rebooted the phone and now it shows the first static logo (that says Samsung Galaxy S i9003) and then it loops in the second boot screen (the one with the animated samsung logo)
Booting into recovery shows this:
Code:
E:failed to mount /data (No such file or directory)
-- Copying media files...
E:failed to mount /sdcard (File exists)
E: copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions
Media files copy failed
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEC/system/'
Successfully applied multi-CSC
EDIT: I've now flashed a Froyo ROM. Same problem but different errors in recovery:
Code:
-- Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
lfs pass open fail
-- movi_checking undone!...
update media, please wait...
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E: copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.
¿Any solutions?
Click to expand...
Click to collapse
Flash cf root and try to entr into cwm recovery and wipe data.
The try to flash xxkpe twice and xxkpq. Factory reset after each flash.
Sent from my GT-I9003

sirilpta said:
Flash cf root and try to entr into cwm recovery and wipe data.
The try to flash xxkpe twice and xxkpq. Factory reset after each flash.
Sent from my GT-I9003
Click to expand...
Click to collapse
I managed to get into CWM and wipe data. But after flashing kpe and kpq it does the same thing again.

assuming u done every thing right
then this will be hardware problem
take the hand st to sumsung support after flashing original firm

internal sndisk sd memory corrupted. rehot or replace.

getting boot loop in my galaxy GT-I9003
i was trying to upload android from odin, but my system os maybe corrupt. evrytime its rebooting( boot loop). samsun galxy symbol again reboot. even USB port is also not detected by PC. so kindly help me how can i restore to old or to update with new os.
kindly provide the help in this regard and also support files if any.

bricked device?

hi,
I tried upgrading my tf300t from cm10.1 to cm10.2 . after a few failed attempts during which I am not exectly sure what I did wrong i got the device into a condition in which it only boots directly into CWM v6.0.2.3 without any option to do anything else. pressing power+volume down does not stop it from directly booting into recovery.
inside the recovery it says:
"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/",
and i cannot mount any partition on the device. trying to access it from fastboot\adb has not been successful.
Any help would be appreciated.
thanks a lot,
guy

I now recall that at some point after trying to flash cm10.2 didn't work I tried flashing the offical asus firmware blob. after that the device successfully booted but when I tried to return to the recovery mode I still could not mount the /data partition. after that I tried some more flashing which brought me to the current situation.

new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.

Ghtm said:
new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.
Click to expand...
Click to collapse
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.

cmendonc2 said:
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.
Click to expand...
Click to collapse
how do i flash a rom using fastboot?

Ghtm said:
how do i flash a rom using fastboot?
Click to expand...
Click to collapse
like this:
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
Code:
fastboot -i 0x0B05 flash system blob

cmendonc2 said:
like this:
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.

Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"

Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
Ghtm said:
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"
Click to expand...
Click to collapse
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.

cmendonc2 said:
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.
Click to expand...
Click to collapse
it says permission denied (cause i do not have root access?)

Ghtm said:
it says permission denied (cause i do not have root access?)
Click to expand...
Click to collapse
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.

cmendonc2 said:
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.
Click to expand...
Click to collapse
the /data prevents me from accessing anything on the sdcard so i cant flash anything from inside the recovery itself.

so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy

Ghtm said:
so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy
Click to expand...
Click to collapse
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.

cmendonc2 said:
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.
Click to expand...
Click to collapse
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.

Ghtm said:
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.
Click to expand...
Click to collapse
Using twrp 2.6.3.0 -4.2 ? Or -jb?

cmendonc2 said:
Using twrp 2.6.3.0 -4.2 ? Or -jb?
Click to expand...
Click to collapse
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"

Ghtm said:
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
Click to expand...
Click to collapse
Use the 4.2 one. The jb will result in a very bad brick.

cmendonc2 said:
Use the 4.2 one. The jb will result in a very bad brick.
Click to expand...
Click to collapse
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:

Ghtm said:
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:
Click to expand...
Click to collapse
No problem, Merry Christmas!

[Q] My Internal sdcard is corrupted! Please Help!

I Think my Internal sdcard is corrupted!
Please Help! Reflashing android won't work. I think the partition is corrupted!
Device: Google Nexus 5
Original OS: Android 5.1.0_r1 (LMY47D)
Recovery: TWRP 2.8.6.0
One day I turned my phone off, and later i decided to go into recovery. I believe I went inside Advanced Options and clicked "Fix Permissions." Then I proceeded to reboot. I was busy at the time, so when I remembered about my phone, I saw that it was still booting. It had been at least 30 minutes so I knew it was in a bootloop. I decided to go back into recovery and reflash the system.img onto it. No luck. I realized I had to try flashing the entire Nexus image (using the flash-all.bat). The phone would still not turn on. I tried flashing different versions of android, and here are my findings:
Android 5.1.0_r3, 5.1.0_r1, 5.0.1: all cause my phone to not be able to boot up (stuck on the 4 color flying animation)
Android 4.4.4, CyanogenMod (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip): Allow my phone to boot up.
However, after I found that I could boot onto Android 4.4.4 and CyanogenMod, I realized that I could not get access to the sdcard!
Here are my findings:
When I go to the phone's root folder, I see a FILE called "sdcard"
When I go to \storage, I see a FILE called sdcard0
When I open camera, the app crashes (possibly because it stores pictures on the sdcard).
I tried to delete these files when I had root access with CyanogenMod but the file manager said "can't delete file." When I am in recovery mode (TWRP) however, I can see the sdcard folder and the contents. Just through every system boot, the sdcard is inaccessible.
After I realized that the problem wasn't due to the data on my phone (after flashing many system images), I realized my data partition might be corrupted. Then I went to this site and followed the directions: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
The e2fsck command didn't do anything as cmd said "The superblock could not be read or does not describe a correct ext2 filesystem."
Afterwards, my friend told me to try mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
I typed that in adb shell and something happened. I started processing blocks or something. Unfortunately now, I am unable to mount the data partition at all. I am also unable to flash the userdata.img onto my phone through fastboot.
UPDATE: When I open up twrp recovery and look in the log I see the following:
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'
E: Unable to mount '/cache/
E: Unable to mount '/persist'
...done
E: Unalbe to mount 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'
MTP Enabled
Anyone know how to fix this? Please help, I owe you so much if you can solve this! Reply to me if you're able to help, I'm also new to xda so I don't really know how messages work. Thanks!

Try taking it out and putting it back in. It happened to me too.

mygoldeneye said:
Try taking it out and putting it back in. It happened to me too.
Click to expand...
Click to collapse
By sdcard I mean the internal sdcard (/storage/emulated/0). Nexus 5 does not have an external sdcard slot anyways.

So you are saying you have no apps, no widgets, nothing... /storage/emulated/0 is your main storage which INCLUDES your system files (unless you have a phone or tablet that has a separate internal SD card - would be /storage/emulated/1 ... I am guessing)

I am having trouble rooting Samsung j7 Perx SM-J727P.

I am totally new to rooting, not sure what I've done wrong.
I started trying to root my SM-J727P by installing TWRP with Odin. This works fine, then I added the superSU v2.82 file to the device's microSD card. I went to install tab in TWRP recovery mode->select storage->Micro SD card->superSU.
Then when I try to flash it, a red message appears saying "Could not mount /data and unable to find crypto footer. Failed to mount /data (Invalid Argument). At the bottom it says "Failed to mount /system (Device or Resource Busy). Failed to mount /data (Invalid Argument.)
After this I read that I need to format storage.
I went to wipe->format data->typed yes and the same message appears, "Failed to mount /system (device or resource busy).
I'm extremely new to this so I don't really know what I'm talking about but do I need to disable dm-verity?
Any help would be greatly appreciated.

ColoPhone said:
I am totally new to rooting, not sure what I've done wrong.
I started trying to root my SM-J727P by installing TWRP with Odin. This works fine, then I added the superSU v2.82 file to the device's microSD card. I went to install tab in TWRP recovery mode->select storage->Micro SD card->superSU.
Then when I try to flash it, a red message appears saying "Could not mount /data and unable to find crypto footer. Failed to mount /data (Invalid Argument). At the bottom it says "Failed to mount /system (Device or Resource Busy). Failed to mount /data (Invalid Argument.)
After this I read that I need to format storage.
I went to wipe->format data->typed yes and the same message appears, "Failed to mount /system (device or resource busy).
I'm extremely new to this so I don't really know what I'm talking about but do I need to disable dm-verity?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I now have manually mounted system and no errors showed, after tapping reboot system, the phone entered a bootloop. Not sure if this is supposed to happen or not and if it is, how long does it take?

ColoPhone said:
I now have manually mounted system and no errors showed, after tapping reboot system, the phone entered a bootloop. Not sure if this is supposed to happen or not and if it is, how long does it take?
Click to expand...
Click to collapse
This happened to me when I was doing my first root with samsung. What I did was completely start over with a new stock ROM and TWRP. Be sure you have all the right things ticked on Odin. What I had to do with my sm-j700p was un-tick auto-restart when done, and when the TWRP was done flashing, I had to remove the battery instead of wait for it to shut down. Then QUICKLY go into recovery mode by pressing the buttons after you turn it back on. Flash ROM. If I remember correctly, I was so good from there, but the timing with samsung when pushing the buttons apparently is EVERYTHING.
And making sure it is the correct TWRP file. I also made the mistake of picking the wrong TWRP file. Same model and carrier...different year of phone. Software version number is where it's at to get the best info.
Good luck!

"Failed to mount 'protect_f' (Invalid argument)" while trying to flash through TWRP

"Failed to mount 'protect_f' (Invalid argument)" while trying to flash through TWRP
My Lenovo A536 went into boot loop cycle and I have been trying to flash a new rom or even a stock one for a while, but I keep getting this error when I try and do it through TWRP.
"
Failed to mount 'protect_f' (Invalid argument)
Failed to mount 'protect_f' (Invalid argument)
"
I flashed the phone multiple times through Smart Phone Flash Tool and it doesn't seem to work either.
The farthest I have come is a loading animation of the OS but it crashes shortly after that.
When I try to mount those two partitions in the mounting section of TWRP, it doesn't want to select them.
I looked at Android Scatter file that is used to install the OS for this phone and at the part with "protect_f' and "protect_s" is says Operation type: Protected, does this have anything to do with that error?
Some people told me that the phone is just on end of it's life and it's an internal memory issue. If it is something to do with hardware side of things, can I install the OS onto my SD card (SanDisk 16GB), and run the phone through that, since, while the phone was working, I noticed option to transfer the entire phones main data to SD Card, so is that possible to do through TWRP or other tools?
I tried Vibe+, Vibe 2.0, Lollipop 5.0, Slim 6.0.1 and non of those can get boot.