Differences

This shows you the differences between two versions of the page.

--- denon_prime_console [2024/05/12 21:37] – ounsatn
+++ denon_prime_console [2024/05/17 14:14] (current) – ounsatn
@@ Line 19: / Line 19: @@
 On your raspberry, make mpcimg executable ( chmod +x ) and then run the following command to get information about the current file:
-**! Important ! note the compatible string (inmusic,jp11)  and the device hex value (0x15e4d00c) -- its needed for the repack **
+**! Important ! note the compatible string (inmusic,jp11)  and the device hex value (0x15e4d00c) and the version (3.4.0) -- its needed for the repack **
 <code>
@@ Line 186: / Line 186: @@
 Now it's time to repack image file.
-To repack file, its mandatory to change headers in binary/script mpcimg at line 161.
+Copy the binary/script "mpcimg" to a copy named "mpcimg_prime".
-For prime JP11 ( prime GO ) change the lines
+<code>
+root@osmc:/home/osmc/Prime# cp mpcimg mpcimg_prime
+</code>
+{{http://dnttalo.cluster029.hosting.ovh.net/Pictures/PrimeGo_Console_15.JPG}}
+Change headers in the copied binary/script mpcimg_prime_ at line 161.
+For prime JP11 ( prime GO ) change the lines
 <code>
     if mpc == "make-force":
@@ Line 209: / Line 218: @@
 **NB : you can put what you want in description, important thing is compatible and inmusic,devices**
+**NB : __compatible and devices__ are the string we had when getting info on the original file upper**
+Once done, repack the firwmare with command
+<code>
+./mpcimg_prime make-force rootfs_PRIMEGO-3.4.0-Update_uncomp.img.img rootfs_PRIMEGO-3.4.0-UpdateTLN 3.4.0
+</code>
+{{http://dnttalo.cluster029.hosting.ovh.net/Pictures/PrimeGo_Console_16.JPG}}
+Take another coffee ! it may be longer to repack, depending of the performance of your arm chip.
+New image is there, ready to be uploaded on Hardware.
+{{http://dnttalo.cluster029.hosting.ovh.net/Pictures/PrimeGo_Console_17.JPG}}
+Download it on your computer, put you prime in update mode.
+Take the Windows Setup Upgrade image from denon on their site (Prime+GO+3.4.0+Updater.exe).
+open it with 7zip, and extract all the files **except update.img** to a dedicated folder.
+in this folder put your new created file file rootfs_PRIMEGO-3.4.0-UpdateTLN and rename it to update.img.
+Like below :
+Connect Prime to your computer via USB, and launch FirmwareUpdater.exe, then if your prime is detected you can run update.
+{{http://dnttalo.cluster029.hosting.ovh.net/Pictures/PrimeGo_Console_19.JPG}}
+{{http://dnttalo.cluster029.hosting.ovh.net/Pictures/PrimeGo_Console_20.JPG}}
+Once update done, PrimeGo reboot with new version.
+Now launch a putty, put ip of the prime with port 230.
+{{http://dnttalo.cluster029.hosting.ovh.net/Pictures/PrimeGo_Console_21.JPG}}
+login with root / pwd : prime
+Tadaaaa your in !
+{{http://dnttalo.cluster029.hosting.ovh.net/Pictures/PrimeGo_Console_22.JPG}}
+To finish, i tried to enable sshd to be run at the startup in the firmware but each times i tried , it failed.
+I should ask on AkaiF/MPC Moddings Groups how it's done, however with telnet it's working well.
+Of course after the telnet connection you can launch ssh
+<code>
+## edit /etc/ssh/shd_config
+## put PasswordAuthentication yes
+## put PermitRootLogin yes
+## and then launch ssh daemon
+systemctl start sshd
+</code>
+As we put telnet in the prime service, if you restart or stop prime service it will kill your telnetd.
+So launch an ssh session before restarting/stopping engine.service via systemctl otherwise you'll loose control of the beast.
+If needed here is my img file , tested on my prime go and working, however use it at your own risk i cannot be responsible for bad usage.
+[[http://dnttalo.cluster029.hosting.ovh.net/Akai/PrimeGOTln/]]