View Single Post
Old 06-29-2016, 06:44 AM   #3
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by knc1 View Post
Plus -
The 'diags' system and kernel contains copyrighted materials which is against site policy here to redistribute without the copyright holder's permission.
Amazon tech support staff DID give me verbal permission to share firmware images (for debricking purposes only). However, they did NOT follow that up with written permission as I requested. They also recommended my "simple debricking" thread here to their customers (which has been replaced by kubrick, which automates my procedure). Mobileread policy allowed us to link to a list (stored elsewhere) of firmware images (also stored elsewhere), but not directly to any firmware images themselves.

That said, we must be careful to not share any partition that contains private data such as our login credentials or "idme vars" (including device serial number). Twobob discovered this the hard way when his DXG got blacklisted because others using his shared "private" partition resulted in multiple exact clones of his device.

It should be safe to PRIVATELY share (via PM) a link to a diags firmware image (and diags kernel) stored offsite. But publishing such content openly is technically a copyright violation despite amazon tech support staff verbal permission, so such things must be shared only privately (via mobileread PMs or other means) if only to avoid unwanted DMCA takedown notices.

Last edited by geekmaster; 06-29-2016 at 11:16 AM.
geekmaster is offline   Reply With Quote