[Q] Problem trying to install CM10 for Galaxy Player 4.0 - Samsung Galaxy Player 4.0, 5.0

I tried following the instructions from this page:
http://forum.xda-developers.com/showthread.php?t=2233983
But i keep getting this error message in recovery mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What do i do to fix this?

---

smrtchopsticks said:
I tried following the instructions from this page:
http://forum.xda-developers.com/showthread.php?t=2233983
But i keep getting this error message in recovery mode:
What do i do to fix this?
Click to expand...
Click to collapse
Try redownloading and try to see off that gives you any problem
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta

---

goldflame09 said:
Try redownloading and try to see off that gives you any problem
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
Click to expand...
Click to collapse
i tried that, but it still giving an error "status 7" im stuck..

---

smrtchopsticks said:
i tried that, but it still giving an error "status 7" im stuck..
Click to expand...
Click to collapse
Go into advanced/show log, and write the output here.

---

zaclimon said:
Go into advanced/show log, and write the output here.
Click to expand...
Click to collapse
ok this is what the whole screen looks like:
gs
+ export PATH=/:/sbin:/system/xbin:/system/bin:/
tmp:/sbin:/vendor/bin:/system/sbin:/system/bin:/
system/xbin
+ /tmp/busybox test -e /dev/block/bm17
+ /tmp/busybox grep -q /mnt/sdcard /proc/mounts
+ rm -rf /mnt/sdcard/cyanogenmod_bml.log
+ exec
run_program: child exited with status 2
script aborted: assert failed: run_program("/tmp
/updater.sh") == 0
assert failed: run_program("/tmp/updater.sh") ==
0
E:Error in /sdcard/[ROMS]/CM10/[ROM][Player4][US
Intl] CM10 Jellybean 4.1.2 w 3.0 kernel for the
Galaxy Player 4/cm-10-20130614-EXPERIMENTAL-ypg1
.zip
(Status 7)
Installation aborted.
AND that's all the screen says. Thanks btw for helping me out! I really appreciate it!

---

smrtchopsticks said:
ok this is what the whole screen looks like:
gs
+ export PATH=/:/sbin:/system/xbin:/system/bin:/
tmp:/sbin:/vendor/bin:/system/sbin:/system/bin:/
system/xbin
+ /tmp/busybox test -e /dev/block/bm17
+ /tmp/busybox grep -q /mnt/sdcard /proc/mounts
+ rm -rf /mnt/sdcard/cyanogenmod_bml.log
+ exec
run_program: child exited with status 2
script aborted: assert failed: run_program("/tmp
/updater.sh") == 0
assert failed: run_program("/tmp/updater.sh") ==
0
E:Error in /sdcard/[ROMS]/CM10/[ROM][Player4][US
Intl] CM10 Jellybean 4.1.2 w 3.0 kernel for the
Galaxy Player 4/cm-10-20130614-EXPERIMENTAL-ypg1
.zip
(Status 7)
Installation aborted.
AND that's all the screen says. Thanks btw for helping me out! I really appreciate it!
Click to expand...
Click to collapse
I actually forgot two lines, so here is the updated one:
Installation aborted.
about to run program [/tmp/updater.sh] with 1 ar
gs
+ export PATH=/:/sbin:/system/xbin:/system/bin:/
tmp:/sbin:/vendor/bin:/system/sbin:/system/bin:/
system/xbin
+ /tmp/busybox test -e /dev/block/bm17
+ /tmp/busybox grep -q /mnt/sdcard /proc/mounts
+ rm -rf /mnt/sdcard/cyanogenmod_bml.log
+ exec
run_program: child exited with status 2
script aborted: assert failed: run_program("/tmp
/updater.sh") == 0
assert failed: run_program("/tmp/updater.sh") ==
0
E:Error in /sdcard/[ROMS]/CM10/[ROM][Player4][US
Intl] CM10 Jellybean 4.1.2 w 3.0 kernel for the
Galaxy Player 4/cm-10-20130614-EXPERIMENTAL-ypg1
.zip
(Status 7)
Installation aborted.

---

Hmm so by far you should have a file name cyanogenmod_bml.log am I right?

---

zaclimon said:
Hmm so by far you should have a file name cyanogenmod_bml.log am I right?
Click to expand...
Click to collapse
where do i find that?

---

smrtchopsticks said:
where do i find that?
Click to expand...
Click to collapse
In /sdcard or your internal storage if you prefer.

---

zaclimon said:
In /sdcard or your internal storage if you prefer.
Click to expand...
Click to collapse
well, i cant actually access the files on the device, since it didnt actually install the CM10. it keeps booting up than goes into CWMR and shows a "dead" android picture and looping... but i can use odin and go int download mode and install stock rom.. can i still access the cyanogenmod_bml.log file?

---

smrtchopsticks said:
well, i cant actually access the files on the device, since it didnt actually install the CM10. it keeps booting up than goes into CWMR and shows a "dead" android picture and looping... but i can use odin and go int download mode and install stock rom.. can i still access the cyanogenmod_bml.log file?
Click to expand...
Click to collapse
Hmm so you must be missing something in your /efs. Please restore to stock and show me the output of the cyanogenmod_mtd.log.

---

btw i keep installing stock rom after i fail to install cm10
than i flash Terrasilent kernel
and than root using doomlord zergrush
is that ok that i do that?
and i also found the .log file after i reflashed the stock rom.
here is what it says:
+ /tmp/busybox grep -q /efs /proc/mounts
+ /tmp/busybox mkdir -p /efs
+ /tmp/busybox umount -l /dev/block/stl3
umount: can't forcibly umount /dev/block/stl3: Invalid argument
+ /tmp/busybox mount -t rfs /dev/block/stl3 /efs
mount: mounting /dev/block/stl3 on /efs failed: Invalid argument
+ /tmp/busybox echo Cannot mount efs.
Cannot mount efs.
+ exit 2

---

zaclimon said:
Hmm so you must be missing something in your /efs. Please restore to stock and show me the output of the cyanogenmod_mtd.log.
Click to expand...
Click to collapse
i cant find the cyanogenmod_mtd.log file but i did find the cyanogenmod_bml.log file..
this is what it says:
+ /tmp/busybox grep -q /efs /proc/mounts
+ /tmp/busybox mkdir -p /efs
+ /tmp/busybox umount -l /dev/block/stl3
umount: can't forcibly umount /dev/block/stl3: Invalid argument
+ /tmp/busybox mount -t rfs /dev/block/stl3 /efs
mount: mounting /dev/block/stl3 on /efs failed: Invalid argument
+ /tmp/busybox echo Cannot mount efs.
Cannot mount efs.
+ exit 2

---

smrtchopsticks said:
btw i keep installing stock rom after i fail to install cm10
than i flash Terrasilent kernel
and than root using doomlord zergrush
is that ok that i do that?
and i also found the .log file after i reflashed the stock rom.
here is what it says:
+ /tmp/busybox grep -q /efs /proc/mounts
+ /tmp/busybox mkdir -p /efs
+ /tmp/busybox umount -l /dev/block/stl3
umount: can't forcibly umount /dev/block/stl3: Invalid argument
+ /tmp/busybox mount -t rfs /dev/block/stl3 /efs
mount: mounting /dev/block/stl3 on /efs failed: Invalid argument
+ /tmp/busybox echo Cannot mount efs.
Cannot mount efs.
+ exit 2
Click to expand...
Click to collapse
It can't even mount efs Are you sure you're restoring all your partitions? (including efs)

---

smrtchopsticks said:
well, i cant actually access the files on the device, since it didnt actually install the CM10. it keeps booting up than goes into CWMR and shows a "dead" android picture and looping... but i can use odin and go int download mode and install stock rom.. can i still access the cyanogenmod_bml.log file?
Click to expand...
Click to collapse
yes the file is stored on the root of your internal sdcard

---

zaclimon said:
It can't even mount efs Are you sure you're restoring all your partitions? (including efs)
Click to expand...
Click to collapse
well, i thought i was. i just use the ypgzusrestoreodin.tar.md5 file from the stock rom thread and flash using odin. I thought that would restore all my partitions. if im not doing that right, what else do i do to restore ALL my partitions?

---

smrtchopsticks said:
well, i thought i was. i just use the ypgzusrestoreodin.tar.md5 file from the stock rom thread and flash using odin. I thought that would restore all my partitions. if im not doing that right, what else do i do to restore ALL my partitions?
Click to expand...
Click to collapse
I don't think the tar file do have the efs partition. Even if you manage to restore /efs into rfs, you will need to restore all your efs information too...

---

zaclimon said:
I don't think the tar file do have the efs partition. Even if you manage to restore /efs into rfs, you will need to restore all your efs information too...
Click to expand...
Click to collapse
ok well, i just downloaded the .efs files from this thread (the stock rom recovery thread):
http://forum.xda-developers.com/showthread.php?t=1531850
and how do i go about restoring the .efs files on my device?

---

smrtchopsticks said:
ok well, i just downloaded the .efs files from this thread (the stock rom recovery thread):
http://forum.xda-developers.com/showthread.php?t=1531850
and how do i go about restoring the .efs files on my device?
Click to expand...
Click to collapse
You're supposed to have an efs backup into /sdcard, please search for it before using the dummy efs. Also all the informations on how to restore /efs are in the thread.

---

zaclimon said:
You're supposed to have an efs backup into /sdcard, please search for it before using the dummy efs. Also all the informations on how to restore /efs are in the thread.
Click to expand...
Click to collapse
ok thanks!
im restoring my efs but im stuck on one part.
and this is what im following:
MAKE SURE YOU ARE ON GINGERBREAD AND RUNNING CWM AND NOT THE STOCK KERNEL WHEN DOING THIS!!!
1. Extract the files inside the efs backup into a folder on your sdcard SEPERATE from anything else.
2. Move all of these files into your /efs folder.
3. Reboot into CWM.
4. Choose factory reset/data wipe.
5. Format system.
6. Under mounts and storage.
7. Reboot into download mode.
8. Flash the STOCK factoryfs.rfs onto your device.
9. Reboot and all should be fixed.
except when i get to step 8. what do i flash the STOCK factoryfs.rfs with? im currently in download mode on my device from step 7.