Hi.
I'm trying to fix my boss' tab, SPH-P100 (Sprint).
I have tried all kinds of things and nearly bricked it (got the phone ! computer symbol, but it still accepted uploads, so I was OK).
Here's the issues:
- Continuous loop of Samsung logo on boot
- From Recovery screen, I performed a factory reset, but it didn't help - same logo loop
- In the Recovery screen, I get errors similar to the ones quoted above:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
I read all kinds of posts about simply flashing the stock ROM, and I found the ROM that was mentioned multiple times in these forums to be the right one for this tab (it did change the first boot animation, though...). The ROM I used is tab_sprint_noModem_20101226.tar inside Tab_Stock_-_No_Modem.rar.
I tried:
-ODIN with the stock ROM posted in this thread. It works, but it doesn't fix anything. I tried with and without the PIT file (one thread specifically warned NOT to use the PIT file, but in the end I tried it anyway - I think I did NOT hit Repartition, so it probably didn't do anything...).
-Heimdall doesn't seem to work at all for me. I found version 1.3.1, and the instructions in post 21 of the thread linked above don't seem to apply to this version. I finally figured out that I need to be in the FLASH tab, but I can't add files without the PIT file, it won't let me add the zImage file for recovery (or at least complains that there's no .bin file ending), and when I checked "Repartition", I got the error:
ERROR: Partition corresponding to -21 argument could not be located
Ending session...
Yes, I installed the drivers that came with Heimdall.
-Following other posts with very similar errors, I formatted the SD card in Windows using FAT32 - no change.
-I looked into another thread talking about parted, but I don't have root on that device, and I'm not sure what my boss would think about me rooting his pad... I also don't know enough to figure out which rooted ROMs would go with it - I'm scared enough with the "official stock rom" I'm using
I'm fairly tech savvy, know a little about Linux and have used adb to root my own phone, but otherwise a lot of the things I read here only make enough sense to me to follow the instructions and not get lost.
Maybe there's a different version of Heimdall that I should be using, or maybe I did something else wrong, but I'm sure I followed the instructions here.
Any help would be greatly appreciated!
Thanks in advance!
(PS, I originally posted this at the end of the thread I mentioned here but did not get an answer - I'm sorry, I had not read the post about not asking questions in that forum, even if it was attached to another post where similar questions were asked and answered, so I'm moving this post here instead.)
Update:
Found a different Rom in this thread - same situation:
I can flash it, but nothing changes, and I still get the error message I showed. The main change is that this ROM is the first I have found that has the same Sprint boot animation that the tab originally had.
The new information is that once it resets after flashing, it briefly shows a few messages - one said that if failed to wipe the cache, and I think the others showed the same error about /dev/block/mmcblk0p1 but I can't be sure (tried to get video of it, but I was too slow, and it's blurred - I'll try again later to get the exact error messages).
Update 2:
Found yet another ROM in this thread and tried it, and this one doesn't seem to work at all with this tab (tried with and without pit/re-partitioning) - the boot fails and immediately boots into Recovery by itself and shows the following:
-- bootmode=7 from cmdline
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting/cache...
E:format_volume: rfs format failed on /dev/block/mmcblk0p1
Data wipe failed.
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
Click to expand...
Click to collapse
Will try to flash the other ROM again to try and get a precise look at its error message...
UPDATE 3:
Flashed the first ROM again - no error message, just the same Samsung logo cycle that freezes briefly and then starts over.
Flashed the second ROM again (the one that has the correct Spring animation), and this time I got the error messages on video.
-- Wiping DATA:...
Formatting DATA:...
DATA: wipe failed.
-- Wiping CACHE:...
Formatting CACHE:...
CACHE: wipe failed.
--Wiping DBDATA:...
Formatting DBDATA:...
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
Rebooting...
Click to expand...
Click to collapse
Still hoping for ideas, but I think I'm at the end of what I can try...
Is it likely or possible that the internal memory got damaged?
I don't know exactly what my boss did to the tab, but he mentioned something about "the cold" meaning Minnesota winter cold - we had about 12 degrees last week, so maybe that's the cause...
Have you found and tried the EA24 stock flash tool?
Sent from my SPH-P100 using xda premium and ICS
Thanks for the reply!
If that's this file:
Sprint Galaxy Tab EA24 Flasher.zip
Then I have tried the ROM in it with Odin, but not the actual tool that came with it.
I'll see if I can get my boss to give me another shot with it (unless he's already returned it - I've had it for a few days already...).
Thanks!
has anyone found a solution to this? I am having the exact same issue...
Not sure why or how it happened everything was fine one day and next day wont go past logo and keeps rebooting.
Same problem here
My P100 started this problem last night, which was the first time it's been turned in in several days. It's fully stock, never had any rooting or flashing performed on it.
Booting into recovery mode shows failed mounts on everything it tries to do, and all the options for recovery also fail - except for "reboot system now", which does reboot it, but then it just sits on the pulsing Samsung logo endlessly. And I do mean endlessly, I let it go four hours last night, after which the battery ran out. Plugged it in after that, and it's right back to the same thing.
Every other thread I've found with this problem listed it as an after-effect of having attempted to flash a new ROM, but that is not the case with mine...
Hoping someone has the answer...
Thanks!
-mike
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
ChrisCTX said:
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
Click to expand...
Click to collapse
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
yappoe said:
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
Click to expand...
Click to collapse
I'm on it ASAP, thanks a ton for that
Edit: If possible mind giving a link to that specific kernel (or flashable .zip with it)?
Do you have this on your screen:
http://forum.xda-developers.com/attachment.php?attachmentid=1193979&d=1342124106
If so, we're in the same boat
Btw, I used a full repartition and boot following this thread:
http://forum.xda-developers.com/showpost.php?p=17817287&postcount=2
and same error occurs.
Bump in hopes of solving this issue.
My tab is basically bricked. I have this same issue after putting CM9 on it. Those errors consistently pop up. and thats it.
I guess its a paper weight now.
you may try flashing pit file and stock rom with micro SD inserted during flashing. that's what I did to my Samsung GT-I9003 when it failed to read the internal SD. At first, the camera may not work. Just root the device after flashing pit/ROM and do SD Swap Mod (external SD as internal SD).
Not sure if it's gonna work with Galaxy Tab. Give it a try. Hope this helps.
Hey guys, it appears JimRich is working on a solution for the CDMA (verizon and sprint) versions of thsi device, keep checking and be sure to let him know there are other people with this problem. http://forum.xda-developers.com/showthread.php?t=1789728
Hello Everyone​
my phone was running good just battery got off charge i plug the charger then i try to open phone i saw it loopboot i just see the welcome message of samsung
but i can get on recovery and download mode
Here is the error message I get when I flash a new rom or i go into recovery :
update media. please wait
E:can't mount /dev/block/mmcbl0p1
(No such file or directory)
E:copy_dbdata_media:can't mount SDCARD:
your storage not prepared yet . please use UI menu for format reboot actions.
copy default media content failed.
---------------------------------------------------------------------------
Here was my phone stock configuration before all that happens:
Baseband version
I9000JPJV6
Firmware
2.3.3
Build number
GingerBread.JPJV6
---------------------------------------------------------------------------
Please help, thanks a lot in advance.
Note: I hope I posted at the right place, if not the mods can feel free to move it
Fail to mount /data
I have the same problem and have tried various fixes but none have worked so far.
I flashed different combinations of the three .pit files (512, 513 and 803) with GB and froyo roms. I flashed some other files than people said would work (dbdata.rfs.tar and P-SBL.tar.md5.tar) although I don't really know what they are supposed to do.
I also used parted in an adb shell to try and change the /dev/block/mmc/blk0. I printed the partitions (there was a FAT32 one and an ext4 one). Using 'rm' I tried to erase these partitions so hopefully a flash with re-partition would work. But afterwards I printed the partitions again and they were still there, exactly the same.
Does this mean that my problem is hardware-related?
If anyone has alternative solutions please share.
My friend has an HTC Vivid that is stuck in a boot loop - it only boots into the recovery mode (CWM-Based Recovery v5.5.0.4). A bi difficult to troubleshoot over Skype, but I tried a few things.
The recovery can't mount /cache. Tried to run backup and got "Can't mount /system!"
adb sees the device, but I can't cd into /data/data to copy mmssms.db or the contacts.
I tried running 'su' in adb shell, but it wasn't found. Indeed, the 'bin' directory was empty.
Any way of pulling /data/data/com.android.providers.contacts/databases/contacts2.db ? Or otherwise getting the phone to boot?
Hi,
I'm sorry for my english.
I have a Samsung gt-8190 s3 mini and i have many problems. I had given my phone to a friend to update it and now i have a lot of problems.
I dont know the firmware, i dont know what he was done with my phone.
On the first screen arrears Samsung s2 i9100, On twrp menu when i put wipe, format, fix permissions i have messages like failed e:mount -o bind /data/media process ended with error=255 , failed to mount, e:unable to stat /data/lost+found. When i reboot to system appears the message panic kernel 0x00000008 or the system always reboot.
What can i do? Is there way to format all data and built the cellphone from the beginning?
Please help me.
Thanks, Giannis
Search on google "Reset android phone to stock with Odin"
so after flashing cm13 onto my s3 it worked for a while then my phone restarted and now i'm getting a failed to mount /tombstones error. Any idea how to fix this?
traceyjas said:
so after flashing cm13 onto my s3 it worked for a while then my phone restarted and now i'm getting a failed to mount /tombstones error. Any idea how to fix this?
Click to expand...
Click to collapse
I have the same problem with this phone, but with the R-N-v5.8.4-20170808-i9305-Official ROM. Were you able to fix it?
problem solved
Just got it solved!
I had the same problem with mounting efs & tombstones: Two month after flashing LOS14 my phone bricked & i was only able to boot into recovery (twrp). Monting efs & tombstones was not possible so new flashing failed.
My solution:
I got to sammobile.com, took the latest file from my country (in my case t-mobile) und flashed it via odin-ap.
Now I have dozens of t-mobile bloat , but my phone is unbricked! Halleluja!
I hope this works for you too
Just had the samce problem and fixed it with the following steps:
1: Booted to TWRP and connected the phone via usb to the pc
2: Connected to phone via adb
- adb shell
3: Got the partitionname of /tombstones from /etc/fstab
- cat /etc/fstab
-> look for something like /dev/block/mmcblkXXXXX in the same line as /tombstones
4: Repaired the partition:
- e2fsck -fvy /dev/block/mmcblkXXXXX
-> its the same name as in /etc/fstab
5: Reboot the phone
6: Profit
Depending on other problems you may or may not have it could also be useful to wipe your cache/dalvik.
Hope this helps other people with the same problem.