Page 1 of 1
Ripping, anyone?
Posted: Thu Dec 08, 2011 12:52 am
by nobody
From the BD player shell I can see the mounted bluray disc and obviously I can transfer it using FTP.
Does anybody know a way to rip it using the bd player itself?
Re: Ripping, anyone?
Posted: Thu Dec 08, 2011 3:29 pm
by julianbb
Yes,for BD-Dxxx
Model please...
Re: Ripping, anyone?
Posted: Fri Dec 09, 2011 2:33 am
by nobody
BD-D5300
I manage to rip a bd disc in this way:
I copied the files from /mnt/cdrom/ to an external hdd
then I made an iso/udf image from them.
Then I used anydvd + virtualclonedrive and decrypted them.
I tried making an image with DD but it only saved 1GB data then errors out.
Even telling dd to ignore errors produced a 1GB file (instead of 48GB).
I could compile udftools and automate the process...
I just wonder if there's another way (there usually is one...always)

Re: Ripping, anyone?
Posted: Fri Dec 09, 2011 7:15 pm
by julianbb
The other way
sm.JPG
This one ?
See... even samsung think about it...

Re: Ripping, anyone?
Posted: Sun Dec 11, 2011 4:02 am
by nobody
How to access the service menu on BD-D5300 ?
using rucommand with info+factory doesn't work...
Re: Ripping, anyone?
Posted: Mon Dec 12, 2011 3:34 pm
by julianbb
RuSamsungComunicator don't detect the player or it detect and sequenz don't work ?(info@phisical remote-factory@pc)
Last option is the physical "factory remote control" ...but not tested...
Re: Ripping, anyone?
Posted: Thu Dec 22, 2011 12:57 am
by nobody
julianbb wrote:RuSamsungComunicator don't detect the player or it detect and sequenz don't work ?(info@phisical remote-factory@pc)
Last option is the physical "factory remote control" ...but not tested...
That's wrong, rucommunicator works with the player, I can issue commands. It's the sequence that doesn't work.
Re: Ripping, anyone?
Posted: Thu Dec 22, 2011 4:43 pm
by julianbb
It's up to you to decide next step:
1.You can try to gain root acces , take a look at files inside BD and then find out WHY the sequence don't work anymore...
thats what we try to do...
2.Wait for other user who risk bricking his device to find out...
3.Ask Samsung Support...
