Page 21 of 54

Re: [App] Rooting E and F Bluray

Posted: Tue Feb 24, 2015 8:19 pm
by pguizzesamygo
No, I didn't try FTP/Telnet.
I thought that launching the app was actually by default removing the cinavia protection.
Apparently I was wrong. I will give a try right now.

But shouldn't I have some new settings in the parameters menu ? Where can I see that my bluray is "patched" in a way.
Could I go somewhere and check something ? I do no see anything different.

Re: [App] Rooting E and F Bluray

Posted: Tue Feb 24, 2015 8:49 pm
by zoelechat
pguizzesamygo wrote:But shouldn't I have some new settings in the parameters menu ? Where can I see that my bluray is "patched" in a way.
Could I go somewhere and check something ? I do no see anything different.
Precisely by checking FTP connection (you can even only check opened ports, but anyway you'll need FTP client to install Cinavia patch), if it connects it means root succeeded, and you can install Cinavia patch :)

Re: [App] Rooting E and F Bluray

Posted: Fri Mar 06, 2015 12:50 pm
by NovaK
I am trying to root my BD-E5500-XA
Purchased in South Africa.
Software version: BSP-E5500WWB-1018.0

The SamyGo app appears in SmartHUB and runs but it does not extract the files.
See screen pic attached.

I have noticed that there is only 85MB free memory compared to hundred of MB from other posters' devices.
Any idea what I'm doing wrong here or is there anything else I need to do?
SGTVLog1.jpg

Re: [App] Rooting E and F Bluray

Posted: Fri Mar 06, 2015 1:20 pm
by sectroyer
NovaK wrote: I have noticed that there is only 85MB free memory compared to hundred of MB from other posters' devices.
Any idea what I'm doing wrong here or is there anything else I need to do?
Yeah looks this is a problem... We already had reports from some other user with also some "exotic" bluray device with "low memory". I think we can now confirm that on these "exotic" devices rooting method doesn't work :( Moreover we even don't know how to distinguish "exotic models" from other models...

Re: [App] Rooting E and F Bluray

Posted: Sat Mar 07, 2015 11:53 am
by scsi3
Hello,

I've a same probleme : only 85 Mb.

I think it's not possible for the BD E5500 :(

So what reference Samsung player ($ 100 to $ 150) would buy it for root and delete Cinavia?
thank you

Re: [App] Rooting E and F Bluray

Posted: Sat Mar 07, 2015 12:20 pm
by sectroyer
scsi3 wrote: I think it's not possible for the BD E5500 :(
I don't know how many times do we have to repeat... From what we know it's NOT model related. For example rooting and cinaviapatch doesn't work for your BD E5500 with little memory but might work for other BD E5500 with more memory :)

Re: [App] Rooting E and F Bluray

Posted: Sat Mar 07, 2015 12:36 pm
by zoelechat
sectroyer wrote:I don't know how many times do we have to repeat... From what we know it's NOT model related.
It's at least related to models with low memory :P
Btw, IIRC this problem has been reported only on some E5500 for now.
Would need a special 64mb xfs image ;)

To answer question, I think any higher range E/F model should be fine...

Re: [App] Rooting E and F Bluray

Posted: Sat Mar 07, 2015 2:08 pm
by scsi3
OK this is what I meant to say: do not work on BD E5500 with little memory (mine) because the xfs image is larger than the available memory.

Is that with the BD-H5500 it works or is there also there any models with different quantit?e of memory?

Thank's

Re: [App] Rooting E and F Bluray

Posted: Sat Mar 07, 2015 4:56 pm
by zoelechat
scsi3 wrote:Is that with the BD-H5500 it works or is there also there any models with different quantit?e of memory?
No it won't work, not because of memory but because it's H, not E/F :)

Re: [App] Rooting E and F Bluray

Posted: Sat Mar 07, 2015 11:01 pm
by sectroyer
scsi3 wrote:OK this is what I meant to say: do not work on BD E5500 with little memory (mine) because the xfs image is larger than the available memory.
The XFS image is mounted AFTER rooting and it's mounted from usb and doesn't take the memory from device :) For you even rooting doesn't work :) To be honest we don't know why it doesn't work on "low memory models" :)