Database Develop

Won't boot past boot screen

Hi everyone! I'm new here, please don't shout at me!
Basically, I've been rooting and installing recoveries images all night. But I've run into a problem. I was going to flash to the Super-Hybrid HD-Desire ROM by MicroMod777 (link to thread: http://forum.xda-developers.com/showthread.php?t=784260) but it won't install, and now won't boot past the Nexus colour logo with the unlock bootloader padlock symbol at the botom. Here is what I did to get to this stage:
Followed these guides: http://wiki.cyanogenmod.com/index.ph...l_Update_Guide
http://androidandme.com/2010/01/hack...t-a-nexus-one/
I then downloaded said ROM and put it in my SD card like it said, and booted into ClockWork from ROM Manager. I tried to flash it, but it didn't work, coming up with this error:
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Copying files...
Copying files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
E:Can't mount SDEXT:
E:Failure at line 24:
copy_dir PACKAGE:ext SDEXT:
Installation aborted.
I then did a factory wipe, and that didn't work, so I wiped the cache partitions. Nothing worked, always the same error. I also did a backup before I tried to flash for the first time, I've tried to restore that, but it doesn't work either; it also says that it can't mount SD-EXT, but I don't know if this is the error.
I can still get into the bootloader (trackball + power buton) and get to recovery through there, and I saw someone say in a thread here that if you can get into the bootloader it is basically impossible to be bricked. The phone will also not mount when I connect it to the PC, however the PC knows it's there, as I can see the phone, and on fastboot's menu it says 'fastboot usb'.
I hope some of you guys can help me! I really do love my phone, I need it ASAP! Ideally, I'd get onto the ROM I mentioned above, but restoring it to factory settings would also be perfect. Whatever is easier!
Thanks
redbullcat
This is also in the General section, but I realised I posted it in the wrong section. Sorry.
EDIT: Just completed this tutorial and it worked! I am now back to where I started! I'll post in this thread if I have any more problems!

LINK doesnt work in your EDIT
Edit: i did this :
fastboot, unlock, flash clockwork recovery, nandroid

[Q] [CWM Problem] can't load cache

Ok so i tried flashing Epic got into a bootloop...so went to stock KF1...ODINed the Cognition kernel with CWM...flashed Fasty II V2.0 onto it...The ROM booted up just fine!
Then I went to Market to Download TiBu..but got a error message saying "Device doesn't have sufficient space blah blah" ...I know this..just need to wipe cache partition and am back up running...but when I boot into Recovery...I get this message:
E: can't open /cache/recovery/command
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
And every time I try to wipe cache partition..it just skips the wipe and gives the above error again
Shot a PM to LostLogic...till then anyone else who knows the solution to the problem please help me
How do I remove these errors?

Mount cache in cwm before wipe?
Sent from my MB860

Pirateghost said:
Mount cache in cwm before wipe?
Sent from my MB860
Click to expand...
Click to collapse
It gave Error can't mount cache...
Anyways I fixed this by :
1) ODINed back to Stock KF1
2) ODINed the Stock KH3 tar file onto it
3) ODINed boog's kernel
4) Installed Fasty II V2.0 using CWM 4.0
Now everything seems to be fine again.
No errors while going into Recovery!

[Q] Stuck on Samsung logo, recovery says can't mount /dev/block/mmcblk0p1

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

Tried to revert to gb from kingdroid - 'media files copy failed'

Hi!
I've followed the below instructions to return by Galaxy Note to gingerbread from ics via mobile odin.
(http://forum.xda-developers.com/showthread.php?t=1424997)
All was going well until it reached system recovery, where i got the errors;
your storage not prepared yet. please use UI menu for format and reboot actions
Media files copy failed
MANUAL MODE
Updating Application
Successfully updated application
Appying multi csc
Cant access to system/csc/DBT/system/
successfully applied multi csc
E: Failed to mount /cache (Unknown error: 0)
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 (Unknown error: 0)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Failed to mount /cache (Unknown error: 0)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Failed to mount /cache (Unknown error: 0)
What should I do?
Thanks for your help~!

Is ur gb running well???
Sent from my GT-N7000 using xda app-developers app

Thanks for the reply ~ No - it's stuck in system recovery with those error messages. Rebooting takes me back to system recovery with the same errors. I've removed the battery and will try and reflash using pc odin...

Try to reflash pre rooted gb rom from dr ketan.you can find him in android developement.put the tar file in pda thru pc odin.
Sent from my GT-N7000 using xda app-developers app

dont forget when your going to reflash back to stock GB.. check on PC Odin if Re-Partition is turn OFF.. It should be Off..
just an f.y.i.

Thanks for your help - I flashed the pre rooted gb rom with odin and it said 'pass', however on reboot I was taken back to the exact same system restore with the exact same errors. Have I bricked it?! What should I do? Thank you!!

Do I need to wipe data from system recovery? Seems to be the only thing I can do there...

mxkun said:
Do I need to wipe data from system recovery? Seems to be the only thing I can do there...
Click to expand...
Click to collapse
Try to wipe the data but on gingerbread only
dont wipe your data on ICS.
and what exactly you are facing???i mean you sgn is booting correctly???and are you able to see your homepage?

When I boot my note, I am taken straight to system recovery, where I am given the error message in the first post. I'm able to enter download mode and system recovery but that's it... Dr.Ketan recommended that I try flashing a stock gingerbread rom from odin now, so I guess i'll try that...

Yep....try to flash it from dr ketans thread....
Hit thanks
Sent from my GT-N7000 using xda app-developers app

Thanks for your help - it finally worked! Now that i'm running stock, is it okay to upgrade the software through the samsung software update app? Thank you!

Yep it is
Sent from my GT-N7000 using xda app-developers app

[Q] Samsung Galaxy S GTI9000 stuck with restoration

I recently rooted my Samsung Galaxy S GTI9000 ZSJW4 with SuperOneClickv2.3.3-ShortFuse & flashed Semaphore_2.7.4 with Odin3 v3.04. Then updated to cm-10.0.0-galaxysmtd with Semaphore CWM Recovery V5.0.2.7. Everything went well.
Before these steps, I did a backup and saved in my Pc. and then did another backup after i flashed everything, it was working just fine until I tried to restore it using my first backup where everything got messed up. It seemed to complete the restoration from backup just fine, but after I rebooted it from CWM. On startup the bootlogo blinked once and went straight back into recovery which I wasn't expecting. And this is what it shows up on recovery.
Semaphore CWM Recovery C5.0.2.7
-----------------------------------------------------------------------------------------
E:failed to open /etc/recovery.fstab (No such file or directory)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
-------------------------------------------------------------------------------------------------------
(This keeps on coming up every time i reboot , I still have access to download mode and recovery, thats about it, not further than that)
I am not sure what caused this, I have tried to find posts on similar issues and haven't come across any that explains clearly how to fix the issue:
Can somebody please explain what part I went wrong and perhaps someway to fix it?
Any help will be greatly appreciated!

ahadh.h4x0r said:
I recently rooted my Samsung Galaxy S GTI9000 ZSJW4 with SuperOneClickv2.3.3-ShortFuse & flashed Semaphore_2.7.4 with Odin3 v3.04. Then updated to cm-10.0.0-galaxysmtd with Semaphore CWM Recovery V5.0.2.7. Everything went well.
Before these steps, I did a backup and saved in my Pc. and then did another backup after i flashed everything, it was working just fine until I tried to restore it using my first backup where everything got messed up. It seemed to complete the restoration from backup just fine, but after I rebooted it from CWM. On startup the bootlogo blinked once and went straight back into recovery which I wasn't expecting. And this is what it shows up on recovery.
Semaphore CWM Recovery C5.0.2.7
-----------------------------------------------------------------------------------------
E:failed to open /etc/recovery.fstab (No such file or directory)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
-------------------------------------------------------------------------------------------------------
(This keeps on coming up every time i reboot , I still have access to download mode and recovery, thats about it, not further than that)
I am not sure what caused this, I have tried to find posts on similar issues and haven't come across any that explains clearly how to fix the issue:
Can somebody please explain what part I went wrong and perhaps someway to fix it?
Any help will be greatly appreciated!
Click to expand...
Click to collapse
These links may be helpful:
- Flashing To Original Rom - Using Odin on GT-i9000
- Flashing To Original Rom - Using Heimdall on GT-i9000
- Rooting GT-I9000 2.3.3 [DDJV9]

flash darky 10.2 re
http://www.darkyrom.com/index.php?threads/darkyrom-first-aid.8178/
see if that works

gopalasubramanium said:
These links may be helpful:
- wwwfixmystuff dot in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom-using-odin.46/"
Flashing To Original Rom - Using Odin on GT-i9000
]
Click to expand...
Click to collapse
I tried your first link /Odin,
After it reboots, it goes into Android system recovery and this shows up:
E:failed to mount /dbdata (Invalid argument)
-- Copying media files...
E:failed to mount /dbdata (files exists)
E:copy_dbdata_media: Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TGY/system/'.
Successfully applied multi-CSC.

gopalasubramanium said:
These links may be helpful:
"fixmystuff in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom-using-odin.46/"]Flashing To Original Rom - Using Odin on GT-i9000
"fixmystuff in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom-using-heimdall.126/"]Flashing To Original Rom - Using Heimdall on GT-i9000
"fixmystuff in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-rooting-gt-i9000-2-3-3-india-ddjv9.47/"]Rooting GT-I9000 2.3.3 [DDJV9]
Click to expand...
Click to collapse
I tried the steps on your second post:
docsgoogle/open?id=0B67As4gsEH4XODdZSnhMMGtaUEU
Step 1: Start Odin
Step 2:
a. Select PIT file as 's1_odin_20100513.pit'
b. Select PDA file as 'PDA_DXJV9_Deodexed_Zipaligned.tar'
c. Select PHONE file as 'PHONE_DXJV9.tar'
d. Select CSC file as 'CSC_OLBJV9.tar'
Step 3: Under Options: Check Re-partition, Check Auto Reboot and Check F. Reset Time
Step 4: Start the phone in the download mode
Step 5: Once ID:COM/phone is 'Added!!' click Start
Step 6: You will see a lot of red text after the flash is done, don't panic, just do a 'wipe data/factory reset' and reboot the device when done.
Step 7: Let the device boot all the way then turn it off.
Step 8: Re-enter Download Mode and re-flash only the CSC file [Step 2 d] without pit and without re-partition.
It should work now...ENJOY
THIS WORKS!

where is the lockscreen file of a rom?and whats its name?
and the wallpapers of the rom?