[Q] YP-G1CWY/XAA stuck at system recovery after failed backup[FIXED] - Samsung Galaxy Player 4.0, 5.0

After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery <3e> with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
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...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
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 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
[UPDATE]
1. I purchased a jig(link further down) and the jig got me into "Downloading..." mode
2. Once in download mode I flashed a ROM and pit file as from Hyperrunner's thread(again, link further down)
3. Using Yaph's experience on AnythingButIpod I flashed Steve's kernel again and gained access to CWM
4. I tried using the restore I was making before the bootlooping started and it went through but I am still stuck in CWM
[UPDATE 2]
All fixed. Big thanks to everyone, especially Zaclimon!

---

SGP4isokay said:
After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
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...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
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 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
Click to expand...
Click to collapse
Adb should work in recovery; type Adb reboot download and you should be in download mode. In download mode you have to flash zaclimon's full recovery rom for the 4.0.
Link: http://forum.xda-developers.com/showthread.php?p=23290249
Sent using Tapatalk

---

klin1344 said:
Adb should work in recovery; type Adb reboot download and you should be in download mode. In download mode you have to flash zaclimon's full recovery rom for the 4.0.
Link: http://forum.xda-developers.com/showthread.php?p=23290249
Sent using Tapatalk
Click to expand...
Click to collapse
Thank you. I've never worked with Android Debug Bridge but it looks drop dead simple from Androidsamurai's guide, so I'll give it a go along with Zaclimon's work. Much appreciated.

---

have you flashed the stock recovery for the 4.0? or did you already fix it?

---

minimeofctown said:
have you flashed the stock recovery for the 4.0? or did you already fix it?
Click to expand...
Click to collapse
I haven't flashed anything yet. I just downloaded the guide, the All In One tool, and the Google USB drivers. I'm trying to load the drivers now.

---

SGP4isokay said:
I haven't flashed anything yet. I just downloaded the guide, the All In One tool, and the Google USB drivers. I'm trying to load the drivers now.
Click to expand...
Click to collapse
For ADB you need samsung drivers not google's
Link to samsung drivers: http://forum.xda-developers.com/showthread.php?t=961956

---

zaclimon said:
For ADB you need samsung drivers not google's
Link to samsung drivers: http://forum.xda-developers.com/showthread.php?t=961956
Click to expand...
Click to collapse
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
With nothing following.

---

SGP4isokay said:
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
With nothing following.
Click to expand...
Click to collapse
Ensure that Usb debugging is enabled: settings-->applications-->developpment-->enable USB debugging.
also ensure that you don't turn on USB mass storage (which means the little android remains green.) Then try again. (Before trying again do this command: adb kill-server.

---

SGP4isokay said:
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
With nothing following.
Click to expand...
Click to collapse
youll have to have usb debugging on. it might give you that at first. just input the command again.

---

zaclimon said:
Ensure that Usb debugging is enabled: settings-->applications-->developpment-->enable USB debugging.
also ensure that you don't turn on USB mass storage (which means the little android remains green.) Then try again. (Before trying again do this command: adb kill-server.
Click to expand...
Click to collapse
Yeah, I saw that I needed debugging on when I started going through Androidsamurai's guide. I neglected to enable that before I tried making a backup and now there appears to be no way to enable it since I am stuck in "Android system recovery". A little Googling leads me to believe that any effort to recover at my device hinged on that being enabled.

---

SGP4isokay said:
Yeah, I saw that I needed debugging on when I started going through Androidsamurai's guide. I neglected to enable that before I tried making a backup and now there appears to be no way to enable it since I am stuck in "Android system recovery". A little Googling leads me to believe that any effort to recover at my device hinged on that being enabled.
Click to expand...
Click to collapse
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy

---

minimeofctown said:
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
Click to expand...
Click to collapse
Thanks! I'll wait for news from you. I'm in no rush and this experience has been a pretty decent learning opportunity.

---

SGP4isokay said:
After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery <3e> with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
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...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
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 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
Click to expand...
Click to collapse
so i have the exact same problem BUT i can access download mode and it is recognized by odin, the next post says to use the zaclimon's recovery rom but it is closed for US. also use ADB but idk if that would apply to my case and if so what do i do exactly because for someone like me its very confusing.
Thank you for any help.

---

minimeofctown said:
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
Click to expand...
Click to collapse
I purchased a Jig from here(USBJig). With it I was able to get back to the "Downloading..." screen(Android with shovel). I plugged the USB cable in and Windows XP recognized my device. So...hooray!
Vilai said:
so i have the exact same problem BUT i can access download mode and it is recognized by odin, the next post says to use the zaclimon's recovery rom but it is closed for US. also use ADB but idk if that would apply to my case and if so what do i do exactly because for someone like me its very confusing.
Thank you for any help.
Click to expand...
Click to collapse
Indeed, Zaclimon's rom is a No-Go. I have been following Kwipper's "[STOCK ROM]" but it says that, "Your phone should be rooted prior to doing this." I did root my device but I'm so hesitant to do anything at this point that I wanted to check with XDA before I do anything.
I'm going to drop a note in Kwipper's thread and ask for guidance. Vilai, I will update you as I progress. Any other input from XDA posters is obviously welcome.

---

i actually did that one too a no go for me just gonna wait out what i see here in the coming days.

---

Vilai said:
i actually did that one too a no go for me just gonna wait out what i see here in the coming days.
Click to expand...
Click to collapse
I found someone who has recovered from these errors but I don't know how to replicate his fix being that this is my first experience with Android/Odin. I will try to contact him and see if I can get a step-by-step repair process.
Here is his last post on the thread I linked just above:
So this is solved!
If anyone gets this kind of error (I think it appears after flashing something with a pit file, even if it is the same you just used), I fixed it by flashing a rom with those inside:
SBL
BOOT (IBL + PBL)
CACHE
DBDATAFS
PARAM
I have the 4.0 US but I took those from a 4.0 international.
PLEASE BE CAREFUL NOT TO USE A ROM WITH zimage & factoryfs INSIDE if you own the us version... if you do a usb jig will still do the trick.
Good to know: the unbrickable resurector does work on the 4.0, check that out if you have a hard brick (no screen response).
Click to expand...
Click to collapse
He mentions at the top of his post that he successfully applied Steve's Kernel to regain Clockwork Mod recovery access so I tried that and now I have CWM working.
[EDIT]
I tried to restore my device from the backup. It seemed to go through successfully(the restore process) but then it just keeps booting into CWM regardless of what I do.
Meh, progress. =- D

---

SGP4isokay said:
I found someone who has recovered from these errors but I don't know how to replicate his fix being that this is my first experience with Android/Odin. I will try to contact him and see if I can get a step-by-step repair process.
Here is his last post on the thread I linked just above:
He mentions at the top of his post that he successfully applied Steve's Kernel to regain Clockwork Mod recovery access so I tried that and now I have CWM working.
[EDIT]
I tried to restore my device from the backup. It seemed to go through successfully(the restore process) but then it just keeps booting into CWM regardless of what I do.
Meh, progress. =- D
Click to expand...
Click to collapse
I've decided to remake the rom for the US (I will not include bootloaders this time) just /cache /system /dbdata and zImage only. I will post it later today. (your error is the recovery can't mount /cache so reinstall it would work.) I will send you a PM for testing if you want before sending it to the recovery thread.

---

zaclimon said:
I've decided to remake the rom for the US (I will not include bootloaders this time) just /cache /system /dbdata and zImage only. I will post it later today. (your error is the recovery can't mount /cache so reinstall it would work.) I will send you a PM for testing if you want before sending it to the recovery thread.
Click to expand...
Click to collapse
For Vilai and anyone else wanting a progress report, I tried the ROM supplied by Zaclimon and it cleared all errors in Samsung Recovery but I am still stuck there. Apparently the next step was to try flashing the bootloader but that failed in Odin. I still have access to Samsung Recovery and "Downloading..." mode.

---

SGP4isokay said:
For Vilai and anyone else wanting a progress report, I tried the ROM supplied by Zaclimon and it cleared all errors in Samsung Recovery but I am still stuck there. Apparently the next step was to try flashing the bootloader but that failed in Odin. I still have access to Samsung Recovery and "Downloading..." mode.
Click to expand...
Click to collapse
I am having the same problem. I get no errors but keep booting into recovery. Tried flashing Steves kernel and it loaded into CWM with no errors. Still no system though.

---

Hmm, sorry for being late into the game, but I had these exact same errors, back before we really knew what we were doing, lol! I couldn't ever get rid of the errors, but I think that was because I was flashing the wrong partitions, so glad you got rid of them! I'm not sure why it still boots to recovery, I'll stay tuned to see what happens! Let me know if you need anything...
Sent using the XDA app.