Posts by gorski

Latest YB plugin for E2 and this....

Quote from Raze

Thank you Gorsky

I had a look in YouTubeUi.py and i saw that :

Code

# Read API keys from key file
if os.path.exists('/etc/enigma2/YouTube.key'):

So i think leaving plugin untouched and creating the file Youtube.key in /etc/enigma2/ is enough, non?

Regards

Display More

Excellent catch! Exactly what needs to be done!

YT plugin makes a YouTube.key file in etc/enigma2, which must be edited with your newly created API details (3 of them):

API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

YOUTUBE_API_CLIENT_ID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com

YOUTUBE_API_CLIENT_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Tested, all working, both in Enigma2 > Kodi > YouTube addon and in

Enigma2 > YouTube plugin!

Cool! :)

Quote from Raze

Thank you Gorsky

I had a look in YouTubeUi.py and i saw that :

Code

# Read API keys from key file
if os.path.exists('/etc/enigma2/YouTube.key'):

So i think leaving plugin untouched and creating the file Youtube.key in /etc/enigma2/ is enough, non?

Regards

Display More

Excellent catch! Exactly what needs to be done!

YT plugin makes a YouTube.key file in etc/enigma2, which must be edited with your newly created API details (3 of them):

API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

YOUTUBE_API_CLIENT_ID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com

YOUTUBE_API_CLIENT_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Tested, all working, both in Enigma2 > Kodi > YouTube addon and in

Enigma2 > YouTube plugin!

Cool! :)

OSCam is available in any image! It works really well and it is Open Source!

CCcam is old tech, not open to inspection etc.

Once you do that, then do as George says:

Quote

...you have to create your own "Api Keys" , and than replace the default in "YouTubeUi.py" file

the file is in usr/lib/enigma2/python/Plugins/Extensions , and depends the image, the .py file may missing, and there will be only the .pyo

in that case , you need to download the content from here: https://raw.githubusercontent.com/Taapat…rc/YouTubeUi.py

and create a .py file .change the Api keys, place it in youtube foder, and reboot your receiver.

Attached is a YT plugin and an example py file, so George's link above is then not needed (I think)...

YT plugin installs like this, using PuTTy Telnet app:

opkg install -force-overwrite /tmp/*.ipk

* = the exact name of the YT file you will install.

A long but instructive tutorial: https://seo-michael.co.uk/how-…be-api-key-id-and-secret/ - it requests some patience!

Quote

How to Create Your Own Youtube API Key, ID and Secret

MJD on Feb 26, 2020

WARNING - THIS IS A LONG GUIDE. BUT HAVE A BIT OF PATIENCE AND YOU'LL GET THROUGH IT

Below is a guide for creating your own Youtube API Key with ID and Secret. The reason for doing this is to eliminate any YouTube over quota limit messages you may get in Kodi and also allow access to your subscriptions etc.

Go to developers.google.com & login to your Google account (you probably already will be but this step is added just to ensure you are)

Now go to console.developers.google.com

Click on Create Project in the top left

You will now see a box labelled Project name. Give it a simple name you can easily recognise and then click Create

Wait for the notification (top right) saying the project has been created

Now click on the Google APIs logo in the top left

Select Library from the left hand menu

Scroll down and select YouTube Data API vX

Select Enable on the next screen

Select Create Credentials on the right hand side of the screen

Click on the Dropdown Box

Select YouTube Data API vX

Now click on the Where will you be calling the API from dropdown box

Select Web Server

In the What data will you be accessing box check Public Data

Now click on What credentials do I need?

You will now see your API key. Click on Copy on the right hand side and then click done

Now you have it copied save it to a text file as we need to now get the ID & secret

After clicking done you will be back at the screen where we clicked on Library. Look on the left hand side again and click on OAuth consent screen

Click External and then Create

Enter a name (just use the same name as you did at the beginning)

Scroll to the bottom and click Save

Now click on Credentials in the left hand menu

Now click Create Credentials in the top left

Select OAuth Client ID

Select Other give it a Name (use the same name as we did before) and click Create

You will now see a box with your Client ID and Secret. Copy both and add to the text file where we saved the API key before

Now open YouTube on Kodi

Scroll down to Settings

Highlight API in the left hand menu

Now paste your API, Client ID and Secret in the corresponding boxes on the right and then click OK

Now click on Sign In in the YouTube app on Kodi

You will now see a message saying you need to sign in twice to your Google account

Click ok and it will give you a code. Go google.com/device and enter the code. Then click on your account and verify it.

A new code will then appear in the YouTube app so repeat the process

When you enter the second it will say you cannot do this as the app is not verified. But it is you who created this so you can trust it. So in your browser (I'm using Chrome) click on Advanced

Now click on Go to 'nameofkey' and allow your API access

You will now be signed into YouTube and be able to access all your lists/likes etc.

Display More

In short, we should create our own API keys and if we do share our version of YouTube plugin then, we better do it only with a small number of people, not everybody, because it won't work for long...

Good luck!:cool1:

Quote from georgeflu

1)first you have to create Api Keys.

2) and than replace the default in "YouTubeUi.py

3) and than replace only the YoutTubeUi.py in the receiver.

making only one of the above, nothing happens...

A long but instructive tutorial: https://seo-michael.co.uk/how-…be-api-key-id-and-secret/ - it requests some patience!

Quote

How to Create Your Own Youtube API Key, ID and Secret

MJD on Feb 26, 2020 0 Comments Comments

WARNING - THIS IS A LONG GUIDE. BUT HAVE A BIT OF PATIENCE AND YOU'LL GET THROUGH IT

Below is a guide for creating your own Youtube API Key with ID and Secret. The reason for doing this is to eliminate any YouTube over quota limit messages you may get in Kodi and also allow access to your subscriptions etc.

Go to developers.google.com & login to your Google account (you probably already will be but this step is added just to ensure you are)

Now go to console.developers.google.com

Click on Create Project in the top left

You will now see a box labelled Project name. Give it a simple name you can easily recognise and then click Create

Wait for the notification (top right) saying the project has been created

Now click on the Google APIs logo in the top left

Select Library from the left hand menu

Scroll down and select YouTube Data API vX

Select Enable on the next screen

Select Create Credentials on the right hand side of the screen

Click on the Dropdown Box

Select YouTube Data API vX

Now click on the Where will you be calling the API from dropdown box

Select Web Server

In the What data will you be accessing box check Public Data

Now click on What credentials do I need?

You will now see your API key. Click on Copy on the right hand side and then click done

Now you have it copied save it to a text file as we need to now get the ID & secret

After clicking done you will be back at the screen where we clicked on Library. Look on the left hand side again and click on OAuth consent screen

Click External and then Create

Enter a name (just use the same name as you did at the beginning)

Scroll to the bottom and click Save

Now click on Credentials in the left hand menu

Now click Create Credentials in the top left

Select OAuth Client ID

Select Other give it a Name (use the same name as we did before) and click Create

You will now see a box with your Client ID and Secret. Copy both and add to the text file where we saved the API key before

Now open YouTube on Kodi

Scroll down to Settings

Highlight API in the left hand menu

Now paste your API, Client ID and Secret in the corresponding boxes on the right and then click OK

Now click on Sign In in the YouTube app on Kodi

You will now see a message saying you need to sign in twice to your Google account

Click ok and it will give you a code. Go google.com/device and enter the code. Then click on your account and verify it.

A new code will then appear in the YouTube app so repeat the process

When you enter the second it will say you cannot do this as the app is not verified. But it is you who created this so you can trust it. So in your browser (I'm using Chrome) click on Advanced

Now click on Go to 'nameofkey' and allow your API access

You will now be signed into YouTube and be able to access all your lists/likes etc.

Display More

Sorry, a quick Q: for Edision+ model, the new 32b image is the latest of 22/3/2020?

And do we need to do anything with the multiboot file or... what is it for, please?

Thanx! :)

Cool! Ta, m8! :) This should make things easier for some... ;)

Perhaps it would be good to make the main posts a sticky, for users who are newbies, m8s?

And the rest can be moved to a thread for discussing the issues around it, perhaps?

Thanx! :)

Sorry, I don't get it - H7 has MultiBoot natively, without any additional plugins/tools, so...??

This STB has 4 partitions natively, so it's baffling...

Just to add, from within the image you can erase partitions, except the one you are using... Search my posts...

Why don't you open a thread in PurE2 section?

This question is not in a good spot, m8... This is a thread about a special image for a special box, not these minor issues...

Btw, we use 1, 4, 7 for RW and for FF the opposite = 3, 6, 9 buttons.

Yo, George!

All fine now with 32b version of the image, kernel, drivers and all? Is it public? Haven't see it yet, sorry...

I don't know if the native Edision multiboot allows for mixing of the kernels, say 32b in one partition and 64b in others, do you know?

I'd like to test SatDreamGr new 32b, without having to remove the 64b images, of course...

Thanx!

Quad core processor, 1GB RAM - of course, everything must be flying by comparison... ;)

http://www.pur-e2.club/OU/images/index.php?dir=6.5/vuplus/ - is it here?

If not: http://www.pur-e2.club/OU/images/index.php?dir=6.3/vuplus/

Moreover, E2iPlayer aggressively overwrites essential libs, so if you have an advanced image but old plugins - there is a problem, for the reasons mentioned...

Ideally, E2iPlayer should be installed from feeds, prepared for that image and not updated, unless it comes with SW update for that specific image - so it doesn't go overwriting libs etc.

He may have been shaken but never stirred, Sir! :rasta2bigsmoke0gf1:

I exchanged some messages with him since the Earthquake in Croatia - they are (almost) all fine, just cleaning and you know... trying to get back to life as before...:cool1:

Nice somebody noticed!:thumbup:

P.S. AFAIK, only one 15 year old girl ended up seriously injured... One is too many but as these things go it was not three bad, as it were...:frown::oml_face_:

Hello, guys!

I tortured mine a little bit too much, apparently... It gave up...

So, now it seems I may need the following:

445423a169c616859097.jpg

-Download HiTool (tool for rs232) here: https://mega.nz/#!0zRERTAC!HbM…bmI1Uo7D9BcWFDWheGCAQq4GA

A newer version 5.06 is here: https://archive.org/download/HiToolSTB5.0.6

You need the appropriate cable and for this box the connectors are on the motherboard itself, so open it up and connect only (my case below: https://www.adafruit.com/product/954 ):

grd (black)

rx (white)

tx (green)

More here:

Also: https://jb8a8f8.com/support/in…icked-boxes-recovery.510/ - thanx to Raza05!

WARNING!!! BE CAREFUL, THESE DEVICES DIFFER IN TERMS OF
NAND or

eMMC

etc.

H9S has Hi3798MV200 Main chipset

These settings and files might not be for your machine!!! It seems like a lot of experimenting should go on, as I could not see anything PRECISE and EXHAUSTIVE on the net... It seems I must dig into this...

More help here: https://rickcaylor.websitetool…-brick-my-sf8008-10299227

Dead Zgemma H92h

Could be, let say that the sent (tx) part is fine of the usb to ttl rs232, but the recipient (rx) has issues. Than you also could get the waiting...

jb8a8f8.com

Zgemma h9s Dead-Bricked

"Zgemma h9s alive again! Have? Simple ! hitool (tool for rs232)!You must have driver for hi3798v200-Important! Normaly conection with rs232(in the Mother.B. is conector)You conect only rx-tx-grd...!You put in hiburn- fastboot.bin and only burn! Thanks a loot for Zgemma support.Are have some problem ,i like help!Thanks Openatv forum! Hansmayer!"

Dead Zgemma H92H - Seite 2

[HowTo] SF8008 Full Recovery mit Hitool

Good luck to us all... I have to try this myself, later on today... ;)

Actually, he said he had a problem with OpenATV 6.2, not PurE2.

But you are probably right - badly coded file...

My idea was to test it in another (PurE2) image. Also the same (OpenATV) image but a newer version (6.3). Given he has 4 partitions natively in Zgemma H9 Twin...

Then he would know if it's the files or images... ;)

Which box, which image (date), which channel, which picon - otherwise...

Mine show (6.3 and 6.5) in some boxes (not all) and not for all channels, so we must be more precise...

All this is still a test and libs etc. keep changing, so...