1. InstallSamygo_1_1_E.rar ([App] "Skype replacement" root E/F) -
379 downloadings
InstallSamygo_1_1_F.rar ([App] "Skype replacement" root E/F) -
299 downloadings
[Ended] E series widget -autostart w/o USB -
a huge number of downloads.
[Ended] SamyGO Extensions on F series -
a huge number of downloads.
All of these methods work without USB, with image-file (128mb.xfs or samyext4.img) in memory of TV. But
THERE IS NO EVIDENCE that someone had received a brick!
2. I have 2.5 years of use working without USB SamyGO on my 40F6330.
The problem occurred only once - there was a cyclic restart.
But after correcting sectroyer's errors, resulting to overfilling of "image" by log-files, everything returned to normal.
3. Getting the bricks due to overfilling folder /mtd_rwcommon - it's a myth !!! Because this folder is never overfilled due to SamyGO!!!
"Image"(samyext4.img) can overfilled (too many SamyGO Apps, log-files, etc), but the folder /mtd_rwcommon - never.
Because the "image" has fixed size, and
can not be more than 128MB.
samyext4.img uses the space for widgets. On my TV, for example, the size of this space - 1,42GB (i.e, samyext4.img uses 8,8% only !!!!)
Sectroyer, stop scaring people with bricks !
sectroyer wrote:setti wrote:
Someone already reported a brick with this root method? I didnt see one.
Yes.
Someone's review - this is not a proof.
Because we can not exclude marriage TVs, failure of internal storage for reasons beyond the control of SamyGO.
Similarly, the internal storage can be damaged during installation of application from Samsung Apps.
