Related
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,
I'm stuck on the HTC screen.
I just wanted to start my phone and it stays stuck on the white HTC screen.
I'm s-on and not rooted(i was a few weeks ago). When i go into recovery it first shows the green circle and the green down arrow, and then it shows the red circle with an exclamation mark, i then need to push sound up+power button to get into recovery.
It says at the top: Android system recovery <3e> and i get a lot of errors:
E:Can't open /cache/recovery/command
E:set_bootloader_message_block: emmc_read_data fail!
E:Can't mount /data/data/recovery/log
E:Can't open /data/data/recovery/log
E:set_bootloader_message_block: emmc_read_data fail!
I only have 4 options to choose from: Reboot system now, Apply update from sdcard, Wipe data/factory reset, Wipe cashe partition.
When i try Apply update from sdcard it says:
--Invalid Operation--
success rebooting by reasonem-00
E:Can't mount /data/data/recovery/log
E:Can't open /data/data/recovery/log
E:set_bootloader_message_block: emmc_read_data fail!
And then it just turns off.
When i choose Wipe data/factory reset, it says:
-- Wiping data...
Formatting /data...
E:Can't mount /data/cwpkg.zip
E:Can't mount /data/cw.prop
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
Formatting /cache...
E:Can't mount /data/data/recovery/log
E:Can't open /data/data/recovery/log
E:set_bootloader_message_block: emmc_read_data fail!
When i choose Wipe cache partition it says:
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
E:Can't mount /data/data/recovery/log
E:Can't open /data/data/recovery/log
E:set_bootloader_message_block: emmc_read_data fail!
When i try to reboot system now it first do 4-6 vibrations and the screen stays black. and i can't do anything only if i pull the battery out and back in. When i press power it stays stuck again on the White HTC screen!
What do i need to do to get rid of the White HTC screen?
vinyplayer said:
Hello,
I'm stuck on the HTC screen.
I just wanted to start my phone and it stays stuck on the white HTC screen.
I'm s-on and not rooted(i was a few weeks ago). When i go into recovery it first shows the green circle and the green down arrow, and then it shows the red circle with an exclamation mark, i then need to push sound up+power button to get into recovery.
It says at the top: Android system recovery <3e> and i get a lot of errors:
*stuff
When i try now to reboot system now it stays stuck again on the White HTC screen!
What do i need to do to get rid of the White HTC screen?
Click to expand...
Click to collapse
Well youre not rooted so no surprise that you cant do anything in recovery.... What are you even doing in the recovery anyways? And plus the White HTC Screen is a splash screen is there forever (if youre S-ON that is ). Flash a custom recovery like 4EXT or CWM, flash superuser arm script and then do whatever
Can you find me a tutorial or briefly write it down here?
vinyplayer said:
Can you find me a tutorial or briefly write it down here?
Click to expand...
Click to collapse
Check my signature.
vinyplayer said:
Can you find me a tutorial or briefly write it down here?
Click to expand...
Click to collapse
frankly, the "072665995" 's guide is most neat and easy to understand guide!!
i used the same to gain root, s-off, and flash a custom rom!!
do it and your problem will get solved!!
When i'm at step 4. Flash a recovery, i get stuck.
I go into fastboot usb, then i type: "fastboot devices", and it shows my serial.
Then i type: "fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img" and it stays at: Writing 'recovery'...
And my phone is stuck too.
What can i do?
vinyplayer said:
When i'm at step 4. Flash a recovery, i get stuck.
I go into fastboot usb, then i type: "fastboot devices", and it shows my serial.
Then i type: "fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img" and it stays at: Writing 'recovery'...
And my phone is stuck too.
What can i do?
Click to expand...
Click to collapse
this didnt happen in my case!!
but still if your phone is stuck try this,
rename the recovery.zip file as PG32IMG
put it on your sd card
reboot inbootloader
it should automatically flash recovery, theoretically.
obviously, DO IT ON YOUR OWN RISK
hit thanks, if i helped you!
---------- Post added at 07:07 PM ---------- Previous post was at 07:01 PM ----------
and i think for this to do you need sOFF first!!
so i think you should refer this guide
http://forum.xda-developers.com/showthread.php?t=1137008
First of all, hello.
My Moto G 2nd generation died suddenly. And i can't turn it on no way.. It's a XT1068 version.
I've read the forum and tried some things, but they're not working. I got into bootloader and recovery mode. And when i try to ""Wipe data/factory reset" or "Wipe cache partition" i get error messages, saying:
"E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last/install
E: Failed closing /dev/block/platform/ms_sdcc. 1/by-name/misc
(I/0 error)"
I don't know what to do already, i don't understand a lot of phones, and i've done nothing to it, this is the way the phone "came from fabric", so i did not touch a lot of things. And i wonder if anyone has a solution for this..
If i turn the phone on either the screen stays black, or a sign of "dead" android comes up saying "no commands" or the M of motorola start keeps loading forever.
ANY SOLUTION PLEASE? =( THANKS!
Seems like you need to flash a rom because yours isn't working.
1. Is your bootloader unlocked? If not then click here : https://www.youtube.com/watch?v=BLSTDsFG1xw (stop watching at like 4:40) just follow the instructions
2. Download: http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
3. This should restore your phone back to stock 4.4.4 and stock recovery.
Hope This helped!
(Not my fault if something goes wrong with your phone )
FrankCABJ said:
First of all, hello.
My Moto G 2nd generation died suddenly. And i can't turn it on no way.. It's a XT1068 version.
I've read the forum and tried some things, but they're not working. I got into bootloader and recovery mode. And when i try to ""Wipe data/factory reset" or "Wipe cache partition" i get error messages, saying:
"E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last/install
E: Failed closing /dev/block/platform/ms_sdcc. 1/by-name/misc
(I/0 error)"
I don't know what to do already, i don't understand a lot of phones, and i've done nothing to it, this is the way the phone "came from fabric", so i did not touch a lot of things. And i wonder if anyone has a solution for this..
If i turn the phone on either the screen stays black, or a sign of "dead" android comes up saying "no commands" or the M of motorola start keeps loading forever.
ANY SOLUTION PLEASE? =( THANKS!
Click to expand...
Click to collapse
"came from fabric" so you got broken phone out of box? If so then just return it back.
FrankCABJ said:
First of all, hello.
My Moto G 2nd generation died suddenly. And i can't turn it on no way.. It's a XT1068 version.
I've read the forum and tried some things, but they're not working. I got into bootloader and recovery mode. And when i try to ""Wipe data/factory reset" or "Wipe cache partition" i get error messages, saying:
"E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last/install
E: Failed closing /dev/block/platform/ms_sdcc. 1/by-name/misc
(I/0 error)"
I don't know what to do already, i don't understand a lot of phones, and i've done nothing to it, this is the way the phone "came from fabric", so i did not touch a lot of things. And i wonder if anyone has a solution for this..
If i turn the phone on either the screen stays black, or a sign of "dead" android comes up saying "no commands" or the M of motorola start keeps loading forever.
ANY SOLUTION PLEASE? =( THANKS!
Click to expand...
Click to collapse
Just restore it using mfastboot v2 with factory firmware image, it works fine...
Some days back I got same problem when I was trying to flash custom rom but couldn't flash because of these errors. so I restored it to 5.0.2 now it works as expected but I am unable to flash custom roms... what can be the solution for this. if anyone knows... tia
I woke up today and my Note 3 was dead. I assumed the battery died as that is in all likelihood what happened. I plugged my phone into the charger and attempted to turn it on. It stayed on the Samsung logo for several minutes. I then booted it into recovery mode, and noticed at the bottom, E: Failed to mount /efs (invalid argument). I attempted a cache wipe and at first it said failed to mount /cache, however another attempt and it completed without error. I then tried a reboot with the same problem. Next I tried a system/data wipe and got the same problem (failed to mount efs).
So, I used a 4 part Odin flash to 5.0 Lollipop OEM. This succeeded and upon reboot the phone got as far as the AT&T logo then hung again. Once in recovery I noticed the same E: Failed to mount /efs (invalid argument). I have searched on this and many other forums attempting to resolve this issue without success. I've been at this nonstop for 12 hours now. I know of a way to use adb to create a generic EFS folder, the problem is the phone is 100% stock, including no developer options(adb), custom recovery, etc. Not even busybox.
Anyone with any info on how I can unbrick this phone would greatly appreciated. Or even how I can use Odin to install safestrap w/ root thereby giving me the ability to mount the system with TWRP and send adb commands that way. To clarify, I have access to nothing but the stock recovery and download mode without ADB active on the phone. Thanks for your time.
My Touchpad (16GB) currently gets stuck at www.palm.com/ROM with an exclamation mark inside a triangle, very possibly caused by a corrupted bootloader and lack of webOS recovery mode.
Here's a little back story for you to help me out.
I installed Android Kitkat on it a while back using jcsullins' famous Touchpad Toolbox. At that time, I chose to completely remove webOS. Of course webOS recovery stayed by default. Lately I became interested in experimenting with Linux on my Touchpad. So I tried to install Ubuntu on it by following castrwilliam's instructions:
https://forum.xda-developers.com/showthread.php?t=2132703
and
https://forum.xda-developers.com/showthread.php?t=2225462
Clearly I didn't do my research sufficiently. When I did
novacom boot mem:// < uImage.SmackMe2
the installation was aborted and I got the following message:
"Android is already installed in the ACMEinstaller way.
Back it up and run the ACMEuninstaller, then re-run this SmackMe installer."
I decided to take a shortcut without thinking it through. Rather than launch jcsullins' Touchpad Toolbox to remove Android, I directly went with
novacom boot mem:// < ACMEUninstaller
The above two steps were done while I still had webOS reovery mode (the big USB symbol in the middle of the screen). But from this point on, I couldn't get to webOS recovery mode. Instead, each time I tried to reboot the Touchpad by pressing down power and home keys simultaneously for over 30 seconds, I went to the www.palm.com/ROM screen and got stuck there.
Now that Android appeared to be no longer in the system, I thought I'd give
novacom boot mem:// < uImage.SmackMe2
another go. Again, it was unsuccessful. Several lines that caught my eye are
Mounting boot partition
Mounting media LV
Mouting webOS root
mount: special device /dev/store/root does not exist
The final line above was alarming to me.
The installation just halted and the screen got stuck with two penguins and a screen full of information. And it wasn't frozen as the cursor kept flashing. The final two lines are
current MEDIA size = 14536M
/etc/init.d/S99smackme: line 168: syntax error: 14536 + 8.00m - 0 - 8
At this point, I realized the Ubuntu installation wasn't going anywhere. So I should try to recover my Touchpad to a working machine and then think about Ubuntu from there.
So I looked around online and collected some files (I thought might be helpful). I got uImage.ClockworkMod and tried to put the non-functioning Touchpad into cwm recovery. I typed
novacom boot mem:// < uImage.ClockworkMod
in a terminal while the Touchpad was still stuck at "www.palm.com/ROM".
I got to a CWM interface. Then I copied a certain CyanongenMod file (cm-11-20150113-SNAPSHOT-jcsullins-tenderloin.zip) from my laptop to the Touchpad with ADB
adb push cm-11-20150113-SNAPSHOT-jcsullins-tenderloin.zip /sdcard/.
FIle copying was successful.
Then I tried to install this zip inside CWM by choosing "install zip from sdcard". The system was at least responding to that. But I got the following messages on the screen.
CWM-based Recovery v6.0.1.9
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
No files found.
No files found.
-- Installing: /sdcard/cm-11-20150113-SNAPSHOT-jcsullins-tenderloin.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-11-20150113-SNAPSHOT-jcsullins-tenderloin.zip
(Status 7)
Installation aborted.
I have some ideas about the set_metadata_recursive error. But all the mounting errors led me to believe my ultimate problem is the partitioning on my Touchpad was destroyed by earlier uninstall of Android.
In summary, my Touchpad is stuck at www.palm.com/ROM. It can enter CWM recovery only through external intervention with
novacom boot mem:// < uImage.Clockworkmod
It has no ability to enter webOS recovery mode. WebOS Doctor couldn't find it.
My own diagnosis of the problems is that the bootloader is corrupted. The filesystem no longer exists because the partitioning was broken.
If you've read so far, I want to thank you for your patience. I just want to present as much detail as possible so that someone here can help me with the problem.
Given the fact that CWM can be "injected" into this broken Touchpad from outside (internally the recovery is obviously no more), I'm assuming there should be a way to salvage it.
Please help. Thank you.