Hello everybody,
first of all: congratulations for this helpful and amazing forum. I love reading and testing the roms which are offered here.
I just tried the Hybrid v 5.0 rom - the best i ever tested. Everything was smoothie and very harmonic.
Unfortunately it was not possible to write emails and to connect with Samsung Kies.
So i decided to use the known 2.3.4 version which works satisfiying.
To prepare the phone i made a wipe data/factory reset.
After reseting the phone shows me - when turned on and booting - the logo of Galaxian Kernel and the blue "loading beam" with the notice "is loading now."
But it doesnt quit loading.
The cwm shows me:
"E: can't mount /cache/recovery/command
E: unknown volume for path [/cache/recovery/log]
E: can't mount /cache recovery/log
E: can't open /cache/recovery/log
E: unknown volume for path [cache/recovery/last_log]
....
"
Maybe some important datas are erased?
I really don't know what to do now.
Could you please give me some helpful advices (please use the easiest words because i'm no expert...) ?
Greetings from Germany
dennish90 said:
Hello everybody,
first of all: congratulations for this helpful and amazing forum. I love reading and testing the roms which are offered here.
I just tried the Hybrid v 5.0 rom - the best i ever tested. Everything was smoothie and very harmonic.
Unfortunately it was not possible to write emails and to connect with Samsung Kies.
So i decided to use the known 2.3.4 version which works satisfiying.
To prepare the phone i made a wipe data/factory reset.
After reseting the phone shows me - when turned on and booting - the logo of Galaxian Kernel and the blue "loading beam" with the notice "is loading now."
But it doesnt quit loading.
The cwm shows me:
"E: can't mount /cache/recovery/command
E: unknown volume for path [/cache/recovery/log]
E: can't mount /cache recovery/log
E: can't open /cache/recovery/log
E: unknown volume for path [cache/recovery/last_log]
....
"
Maybe some important datas are erased?
I really don't know what to do now.
Could you please give me some helpful advices (please use the easiest words because i'm no expert...) ?
Greetings from Germany
Click to expand...
Click to collapse
For connecting kies you just have to install one patch, it will connect.
Regarding resetting, some files i deleted for utilizing space, which required for factory reset thats why you getting that.
let me explain why i delete that files, see when someone switch ROM ever developer want that user do fresh install but usualy people are lazy so they simply flash rom on other ROM, by deleting that files i conform that if someone want to change ROM then he had to flash first stock rom then other ROM so atleast he didnt got error or didnt able to claim that he coming from that ROM and so he getting this error.
btw for both issue why didnt u asked for patch, its easy task for me to make cwm for that and you able to connect kies and able to do factory reset.
Thank you very much for your fast answer.
i didn't thought about asking, sorry..
That's right. Before flashing your great rom i used the clear 2.3.4 firmware. I did the whole procedure as described here. Use a stock rom and than the other rom.
What could i do right now?
My phone doesn's start. "is loading now... " is written under the logo of Galaxian Kernel. The phone doesn't boot, isn't known by the PC, so i don't know what to do....
Boot to recovery and try wipe almost everything you can, factory reset, cache, dalvik-cache.
I remember one firmware gave me some errors about mounting and wiping stuff always fixed it.
I tried as you proposed but following message appears:
E: unknown volume for path [/data]
...
E: Unable process volume! Skipping...
Checking /cache...
Doesn't that mean that the necessary datas aren't there?
After wiping of all proposed things i tried to restart, but the blue beam under Galaxian still stops when it almost reached the end.
The main problem was Kies.
Phone couldn't be connected, so i couldn't fix the problem.
I just had to update the drivers so that the PC could connect to my little friend. Now it works
Thanks a lot for your help!!
Hi,
I've got the exact same problem.
Tried to flash Galaxian over Odin because my phone was in a boot loop. Then it just stuck when the Galaxian kernel "is now loading" screen appeared.
I can access Recovery and wiped data aswell as cache partition- then I just tried to flash Galaxian a second time with Odin but I have the same problem with the "is now loading" screen now.
Plus I updated Kies drivers.
What can I do? Im really not that experienced but I really NEED my phone!
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
Hi guys,
I've tried to flash a new rom and now my phone doesnt start. When i power on the LG logo displays and i automatically enter the clockworkmod menü with this message:
ClockworkMod Recovery v5.0.2.0
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log
E: Cant open /cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open /cache/recovery/last_log
I cant even get into the recovery mode.
Is there anything i can do? Ive tried to wipe the cache and everything a few times but had no success!
I hope you can help me!
Edit: I have tried the instructions from here: http://forum.xda-developers.com/showthread.php?t=1007825
And i got this error message at the end: http://s1.directupload.net/file/d/2833/czj32463_jpg.htm
Is my phone Dead? :-(
Edit Nr.2: Ok my Optimus got a second chance XD
I just changed the usb port. Used the fron one before. Its better to use one on the back side of the computer. The nvflash was sucessull. Startet Smartflash and flashed the official 20l.
Now everything is fine. Puh i realy thought this was the end XD
I already trying to mutch things on it....
i'm trying to reset it, to the factory settings(format)
i already try to flash it with the RSD Light and when it's done i got the after reboot exclamation problem screen.
i'm getting these errors on the recovery screen:
E:Can't read MISC:
(No space left on device)
E:Can't open /cache/recovery/command
E:Can't read MISC:
(No space left on device)
E:Can't read MISC:
(No space left on device)
every time i put the battery, my milestone try to run the android and get de exclamation screen after the motorola logo.
i'm already tryed the "got_telus_2_2_1_full.sbf" and my default "milestone_base_2.2.1.sbf".
can someone help me ? my device is already brinked ?
rankdobr said:
I already trying to mutch things on it....
i'm trying to reset it, to the factory settings(format)
i already try to flash it with the RSD Light and when it's done i got the after reboot exclamation problem screen.
i'm getting these errors on the recovery screen:
E:Can't read MISC:
(No space left on device)
E:Can't open /cache/recovery/command
E:Can't read MISC:
(No space left on device)
E:Can't read MISC:
(No space left on device)
every time i put the battery, my milestone try to run the android and get de exclamation screen after the motorola logo.
i'm already tryed the "got_telus_2_2_1_full.sbf" and my default "milestone_base_2.2.1.sbf".
can someone help me ? my device is already brinked ?
Click to expand...
Click to collapse
Got the same Problem...Can anybody help?
i can flash vulnerable recovery, can flash bootloader everything works but after full sbf flash starts the phone in recovery with the same problem...
E:Can't read MISC:
(No space left on device)
E:Can't open /cache/recovery/command
E:Can't read MISC:
(No space left on device)
E:Can't read MISC:
(No space left on device)
HELP HELP HELP
Not sure how much help This will be but I did my device for the weekend. I used Open Recover 3.3 from bellow
Instructions: http://androidforums.com/milestone-...date-milestone-android-2-3-3-instruction.html
Open Recovery 3.3: http://forum.xda-developers.com/showthread.php?t=796679
Note that by default the device may not get signal. I used the steps bellow to set it up for Telus. Please note you need Open Recovery 3.3
The Version included in the Instruction does not have the option to change baseband for some reason.
Wipe your phone. Select Wipe Dalvik Cache, Wipe Data / Factory Reset, and Wipe Cache Partition.
Select Change Baseband and select Telus.zip
Best of luck. Remember Just because it worked for me don't mean it will work for you. So attempt at your own risk.
My goal was to install the ROM JB-4.1.2.
I've rooted my phone with flashtool, uncloked the bootloader also with flashtool and since then everything went great.Next step which wasn't hard at all was to flash the kernel via flashtool and it also happened with great result.The problem appeared when I was turning phone on, the system haven't turned up and my phone had showed only CWM Recovery.I knew that something went wrong but I made full wipe, cache and dalvik cache and installed JB-4.1.2. The CWM has said that system has been installed but when I've tried to boot phone JB didn't show up; again there was only CWM.
I've tried few times the procedure ( installing stock 2.1 android from Update Service, rooting phone with Flashtool, and flashing the kernel) but I'm facing the same problem with CWM.
Maybe I did something wrong, but don't know exactly what; or maybe my phone is not suitable for kernel?
I'm waiting for help!
Did you format the partitions before flashing the rom?
Yes, I did and nothing has changed.I again saw a screen with CWM and under options to choose at CWM I had a message from CWM like that:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Can anybody help with that odd problem?