|
|
Post by zlymag on Jun 25, 2019 16:39:53 GMT
Hi
Got c64mini someone was playing with .IT doesnt start c64 emu on screen .I can see missing files on system .Any way to flash firmware without on screen menu or restore nand directory ?Cant see aby backup of filesystem as well anywhere.Any help ?
|
|
|
|
Post by frankybyte on Jan 10, 2020 11:53:39 GMT
|
|
|
|
Post by refused75 on Nov 18, 2020 18:53:00 GMT
Dear All,
I would need to recover my mini from " black screen" matter as one day during some game sessions I don'know exactly why but my mini became black screen. Probably I changed too much usb pen drives in few minutes and I messed up the system overfloading the ram. However I am very unexpert linux but I read carefully all the posts about FEL mode hack and how restoring nand through FEL mode.
I can reach quite easily FEL mode thanks to all of you so I still hope Ram is not damaged but I would need your further help because I didn't have my nanda and nandb backup so I used this Frankbyte backup that he kindly put to our disposal but I could not success in restoring my Mini after a lot of efforts.
I am trying using these FEL instructionss after copying in USB pen drive this nanda and nandb given by Frankbyte :
mount /dev/sda1 /mnt
insmod -f /opt/nand.ko
dd if=/mnt/nanda of=/dev/nanda
dd if=/mnt/nandb of=/dev/nandb
But after that I can see only the blu screen but only ***c64 ramfs system *** first line appears but I cannot write anything.
So I kindly ask you mostly if possible whether you could check if my commands are Ok , i read them in other FEL posts in the forum and they seemed that for other users worked well and if the commands are ok if anyone else could put at disposal his nanda and nandb backups as Frankbyte did it I would like to try with other buckups if possible.
Thank you very much to everyone could give me his hand
|
|
|
|
Post by spannernick on Nov 18, 2020 20:33:39 GMT
Did you copy nanda and nandb to the root of your usb stick or pen drive..? `/mnt/` is the root of the usb stick.
|
|
|
|
Post by refused75 on Nov 18, 2020 21:28:21 GMT
Yes, I have formatted my USB pendrive with SD card formatter in "overwrite format" that is the " long way" ( so no quick format ) and copied in the pen drive root only nanda and nandb files by frankbyte. Maybe I am wondering whether I should cancel with some commands my old nanda and nandb files of my mini before copying the new nands. Is this could be the point ? Thank you for your help highly appreciated.
|
|
|
|
Post by spannernick on Nov 19, 2020 1:23:53 GMT
You should not need to copy nanda, just copy nandb and the C64 Mini should work.
|
|
|
|
Post by jj0 on Nov 19, 2020 20:06:26 GMT
Dear All, I would need to recover my mini from " black screen" matter as one day during some game sessions I don'know exactly why but my mini became black screen. Probably I changed too much usb pen drives in few minutes and I messed up the system overfloading the ram. However I am very unexpert linux but I read carefully all the posts about FEL mode hack and how restoring nand through FEL mode. I can reach quite easily FEL mode thanks to all of you so I still hope Ram is not damaged but I would need your further help because I didn't have my nanda and nandb backup so I used this Frankbyte backup that he kindly put to our disposal but I could not success in restoring my Mini after a lot of efforts. I am trying using these FEL instructionss after copying in USB pen drive this nanda and nandb given by Frankbyte : mount /dev/sda1 /mnt insmod -f /opt/nand.ko dd if=/mnt/nanda of=/dev/nanda dd if=/mnt/nandb of=/dev/nandb But after that I can see only the blu screen but only ***c64 ramfs system *** first line appears but I cannot write anything. So I kindly ask you mostly if possible whether you could check if my commands are Ok , i read them in other FEL posts in the forum and they seemed that for other users worked well and if the commands are ok if anyone else could put at disposal his nanda and nandb backups as Frankbyte did it I would like to try with other buckups if possible. Thank you very much to everyone could give me his hand You could try the following which has some extra checks: mount /dev/sda1 /mnt
ls -l /mnt
ls -l /dev/nand*
insmod -f /opt/nand.ko
ls -l /dev/nand*
dd if=/mnt/nanda of=/dev/nanda
dd if=/mnt/nandb of=/dev/nandb
e2fsck -y /dev/nandb
md5sum /dev/nand*
md5sum /mnt/nand*Are you doing this from the TV-screen command line or from the UART? |
|
|
|
Post by refused75 on Nov 20, 2020 18:54:45 GMT
Hi JJ0, Thank you very much for your help, I am in the FEL MODE ( no UART ) and I enter commands from rootc64mini# and in my usb pen drive ( 4 gb FAT 32 ) there is in the USB root the nanda and nandb from Frankbyte files. I did again some efforts following your lines, the problem is always when I do the dd if=/mnt/nandb of=/dev/nandb It seems to work but after this command the mini start flashing on the blu screen like if it is apparently copying the new nandb but it seems it can't ...and some writings appear on the screen but very fast like " bin/ash inappropriate ... " or something similar but I cannot read them well as they disappear while flashing. About your commands they seem to work except : ls -l /dev/nand* ---- > when I do this --- > no such file or directory md5sum /dev/nand*------ > when I do this --- > no such file or directory e2fsck -y /dev/nandb----- > when I do this--- > mini start flashing similar way to when I do the command " dd if=/mnt/nandb of=/dev/nandb " ...but after few flashings of the monitor nothing important happen Last thing : when I do ------- > dd if=/mnt/nanda of=/dev/nanda ---> 32768 records in 32768 records out What do it mean ? Was my mini able at least to copy the nanda and is it ok at least nanda? I attach a pic ( very low quality I apologize for this ) in which I did your commands. Then I took the picture before launching the if=/mnt/nandb of=/dev/nandb because after this I cannot do any pic as everything start flashing .... Many thanks again Attachments:
|
|
|
|
Post by spannernick on Nov 20, 2020 19:22:24 GMT
It be alot easier if you connect a UART to it, you can still connect one to it even if you are using FEL Mode, link to how to is here... thec64community.online/thread/76/2020-thec64-maxi-modding-gameslooks like nanda copied ok, I don't know why nandb didn't, did you wait to see if the screen would stop flashing and see if it copied the nandb over ok..? |
|
|
|
Post by jj0 on Nov 20, 2020 21:21:54 GMT
Hi JJ0, Thank you very much for your help, I am in the FEL MODE ( no UART ) and I enter commands from rootc64mini# and in my usb pen drive ( 4 gb FAT 32 ) there is in the USB root the nanda and nandb from Frankbyte files. I did again some efforts following your lines, the problem is always when I do the dd if=/mnt/nandb of=/dev/nandb It seems to work but after this command the mini start flashing on the blu screen like if it is apparently copying the new nandb but it seems it can't ...and some writings appear on the screen but very fast like " bin/ash inappropriate ... " or something similar but I cannot read them well as they disappear while flashing. About your commands they seem to work except : ls -l /dev/nand* ---- > when I do this --- > no such file or directory md5sum /dev/nand*------ > when I do this --- > no such file or directory e2fsck -y /dev/nandb----- > when I do this--- > mini start flashing similar way to when I do the command " dd if=/mnt/nandb of=/dev/nandb " ...but after few flashings of the monitor nothing important happen Last thing : when I do ------- > dd if=/mnt/nanda of=/dev/nanda ---> 32768 records in 32768 records out What do it mean ? Was my mini able at least to copy the nanda and is it ok at least nanda? I attach a pic ( very low quality I apologize for this ) in which I did your commands. Then I took the picture before launching the if=/mnt/nandb of=/dev/nandb because after this I cannot do any pic as everything start flashing .... Many thanks again From the picture it looks like even though you load the nand driver (insmod -f /opt/nand.ko) the /dev/nanda and /dev/nandb devices are not created. You can see this because both before and after the insmod command the ls command returns 'no such file and directory' and the md5sum gives a similar result. That would also explain why the system crashes at some point because the 'dd if=/mnt/nandb of=/dev/nandb' then actually creates a new /dev/nandb file of 197MB but as the system runs from a ramdisk this will use up all RAM and then crash. To check if this is indeed the case, can you please do: mount /dev/sda1 /mnt
insmod -f /opt/nand.ko
dmesg >/mnt/dmesg.txt
sync
umount /mntAnd then reply with the dmesg.txt file - preferably in a code block for readibilty, or as attachment? |
|
|
|
Post by refused75 on Nov 20, 2020 22:54:31 GMT
Hi JJ0 ,
Attached you find my dsmesg.txt file after following your instructions.
However after creating the dmesg.txt file I have done an other try ( with no result ) but when I did the command : insmod -f /opt/nand.ko ----- > insmod : ERROR : COULD NOT INSERT MODULE /OPT/NAND.KO : FILE EXISTS
Attached you find pic about this effort.
Thank you again for your time checking this mess hoping you can find something helpful to understand how to take my mini back to life :-)
Attachments:dmesg.txt (37.02 KB)
|
|
|
|
Post by jj0 on Nov 21, 2020 10:07:09 GMT
Hi JJ0 ,
Attached you find my dsmesg.txt file after following your instructions.
However after creating the dmesg.txt file I have done an other try ( with no result ) but when I did the command : insmod -f /opt/nand.ko ----- > insmod : ERROR : COULD NOT INSERT MODULE /OPT/NAND.KO : FILE EXISTS
Attached you find pic about this effort.
Thank you again for your time checking this mess hoping you can find something helpful to understand how to take my mini back to life :-)
The nand.ko loads succesfully the first time (that's why you can't load it again), and correctly identifies your nand chip (an ESMT one): [SCAN_DBG] Nand flash chip id is:0xc8 0xd1 0x80 0x95 0x42 0x7f
[SCAN_DBG] NandIDNumber: 0xc0003, NandTwoPlaneOp: 1, DriverTwoPlaneOPCfg: 0
[SCAN_DBG] ==============Nand Architecture Parameter==============
[SCAN_DBG] Nand Chip ID: 0x9580d1c8 0xffff7f42
[SCAN_DBG] Nand Channel Count: 0x1
[SCAN_DBG] Nand Chip Count: 0x1
[SCAN_DBG] Nand Chip Connect: 0x1
[SCAN_DBG] Nand Rb Connect Mode: 0x1
[SCAN_DBG] Sector Count Of Page: 0x4
[SCAN_DBG] Page Count Of Block: 0x40
[SCAN_DBG] Block Count Of Die: 0x400
[SCAN_DBG] Plane Count Of Die: 0x2
[SCAN_DBG] Die Count Of Chip: 0x1
[SCAN_DBG] Bank Count Of Chip: 0x1
[SCAN_DBG] Optional Operation: 0x4000008c
[SCAN_DBG] Access Frequence: 0x1e
[SCAN_DBG] ECC Mode: 0x0
[SCAN_DBG] Read Retry Type: 0x0
[SCAN_DBG] DDR Type: 0x0
[SCAN_DBG] =======================================================
[SCAN_DBG] ==============Optional Operaion Parameter==============
[SCAN_DBG] MultiPlaneReadCmd: 0x0, 0x30
[SCAN_DBG] MultiPlaneWriteCmd: 0x10, 0x80
[SCAN_DBG] MultiPlaneCopyReadCmd: 0x0, 0x0, 0x35
[SCAN_DBG] MultiPlaneCopyWriteCmd: 0x85, 0x11, 0x80
[SCAN_DBG] MultiPlaneStatusCmd: 0x70
[SCAN_DBG] InterBnk0StatusCmd: 0x70
[SCAN_DBG] InterBnk1StatusCmd: 0x70
[SCAN_DBG] BadBlockFlagPosition: 0x2
[SCAN_DBG] MultiPlaneBlockOffset: 0x1
[SCAN_DBG] =======================================================
However when it wants to actually use the nand reading the mbr partition table it encounters bad block/ecc checksum errors that prevent it to continue to provide /dev/nanda and /dev/nandb: [NE]mbr read 8
[NE]mbr read ok!
[NE]mbr read end!
[NE]mbr partition start!
[NE]mbr partition ok!
[NE]mbr partition end!
[NE]new nand info init!!
[NE]mbr read 8
[NE]mbr read ok!
[NE]mbr read end!
[NE]get mbr_data table
[ND]ok get factory_bad_block table!
PHY_PageReadSpare bad flag: bank 0x0 block 0xa page 0x0
plane:0, ch:0, chip:0, blk:0x15, pg:0x0, 0x008b060a 0xc2b8530a 0x55555555 0x55555555
PHY_PageReadSpare: too much ecc err, 0xfffffff4, 0x0, 0x0, 0x0
bank 0 block 0xa,page 0x0
secbitmap low: 0x33, high 0x0
[PHY_DBG] Find a bad block (NO. 0xa) in the Die 0x0
[NE]can not find no use block 12!
So it is likely that you have an actual physical error on your nand. To try to fix this there are basically two options: - If you haven't modded your Mini you could contact RGL for a replacement - after all it just failed without you doing anything special. You could refer them to this thread or provide the dmesg.txt explaining you retrieved this dmesg non-intrusively via FEL mode.
- It might be possible to reformat the nand, and write back a full copy of somebody else's ESMT nand. I've done this for my Mini though that had a Toshiba nand so it would need some further developmentto do the same for an ESMT nand as they are different. Also, my nand didn't have bad blocks AFAIK
So I would advice first to get back to RGL and if they can't provide a solution I'm willing to look into providing the tools to reformat and write back a copy.
|
|
|
|
Post by spannernick on Nov 21, 2020 11:59:22 GMT
I have 2 THEC64 Mini's, the first one is the preorder one with a Toshiba Nand and the other one, the second model, it has a ESMT Nand...  , I knew me buying them they would came in handy, even thought I don't use them no more... So if you want a copy of my ESMT nand I am willing to copy it for you but will need the tool to copy it, me and jj did do this with my Toshiba nand but I can't find the program we used to copy it. Maybe we could keep a copy of the nands on one drive so if anyone needs them, they could be kept in the PCU Download Folder, I don't have a copy of the Toshiba Nand no more. This is one of the reason why I never used THEC64 Maxi Game Tool to flash games to THEC64 Mini/Maxi,(even when I was testing it I never used it), it can mess up the firmware if you try to add to many games to the update. NEVER COPY GAMES WITH THEC64 MAXI GAME TOOL TO YOUR FIRMWARE, PCU IS THE BEST WAY TO GO NOW, You are taking a risk every time you use it that way, thats why I added Autoboot to PCU so its like the games are on the firmware when there not. And THEC64 Maxi Game Tool can void your 1 year warranty too but the tool was made before PCU was available. |
|
|
|
Post by refused75 on Nov 21, 2020 14:18:41 GMT
Good day JJ0 and Spannernick, I have never modded my mini but now I am really fond about the matter to restore
my mini nand and this hassle has been in any case a nice occasion to learn a lot of
things and know both of you. So I would ask to JJ0 whether you can provide this program to copy the ESMT nand so Spannernick can do his copy and put at disposal for me and for any needed users and whether you can instruct me with these tools to reformat and write back a copy of my ESMT nand. Many thanks to both of you for your time and kind assistance. |
|
|
|
Post by spannernick on Nov 21, 2020 18:07:24 GMT
Cool No problem, Thats what I am here for and why I made the forum.. |
|
|
|
Post by kugelblitz on Nov 23, 2020 13:19:24 GMT
Just a quick note / warning: I took the 1.20 Mini nandb backup that Nick has on the Onedrive to bring my Mini back to factory conditions. Used the X-Windows-Mod, had the nand file renamed to "mini" in the directory "nands" on the USB drive. In the shell windows typed
dd if=/media/usb/nands/mini of=dev/nandb
(wait about a minute til prompt comes back)
sync
...and then logged out of X-Windows-Mod and powered down the device.
Worked perfectly! Mini back to original 1.20!
And then I was feeling adventurous and tried the very same thing with the VIC-20 nandb from the same onedrive to my C64 Maxi and bricked it! No idea what happend, will try FEL rescue this week. Just a warning that this might NOT be working.
Thanks, Boris
|
|
|
|
Post by jj0 on Nov 23, 2020 15:14:02 GMT
Just a quick note / warning: I took the 1.20 Mini nandb backup that Nick has on the Onedrive to bring my Mini back to factory conditions. Used the X-Windows-Mod, had the nand file renamed to "mini" in the directory "nands" on the USB drive. In the shell windows typed dd if=/media/usb/nands/mini of=dev/nandb (wait about a minute til prompt comes back) sync ...and then logged out of X-Windows-Mod and powered down the device. Worked perfectly! Mini back to original 1.20! And then I was feeling adventurous and tried the very same thing with the VIC-20 nandb from the same onedrive to my C64 Maxi and bricked it! No idea what happend, will try FEL rescue this week. Just a warning that this might NOT be working. Thanks, Boris The kernels of the Maxi and the VIC-20 are different so you need to restore nanda as well. Otherwise the VIC-20 will boot but be unable to load the nand driver and even if it does the Mali graphics driver so it won't be able to start the64. |
|
|
|
Post by kugelblitz on Nov 23, 2020 15:19:46 GMT
Aaah! Anybody got a factory mint C64Maxi NandB lying around?
|
|
|
|
Post by spannernick on Nov 23, 2020 15:39:06 GMT
Just a quick note / warning: I took the 1.20 Mini nandb backup that Nick has on the Onedrive to bring my Mini back to factory conditions. Used the X-Windows-Mod, had the nand file renamed to "mini" in the directory "nands" on the USB drive. In the shell windows typed dd if=/media/usb/nands/mini of=dev/nandb (wait about a minute til prompt comes back) sync ...and then logged out of X-Windows-Mod and powered down the device. Worked perfectly! Mini back to original 1.20! And then I was feeling adventurous and tried the very same thing with the VIC-20 nandb from the same onedrive to my C64 Maxi and bricked it! No idea what happend, will try FEL rescue this week. Just a warning that this might NOT be working. Thanks, Boris THE VIC 20 used a recompiled nanda so THEC64 Maxi nanda will not work with THE VIC 20 nandb, it works fine, I made a bootable version of it on sd card so I can boot it up on my OPI, I have THEC64 Maxi on sd card and THEVIC 20 on another so I can swap if I want to.. |
|
|
|
Post by jj0 on Nov 23, 2020 15:50:12 GMT
Edit: Updated instruction for running nand_rw - > ./nand_rw Good day JJ0 and Spannernick, I have never modded my mini but now I am really fond about the matter to restore
my mini nand and this hassle has been in any case a nice occasion to learn a lot of
things and know both of you. So I would ask to JJ0 whether you can provide this program to copy the ESMT nand so Spannernick can do his copy and put at disposal for me and for any needed users and whether you can instruct me with these tools to reformat and write back a copy of my ESMT nand. Many thanks to both of you for your time and kind assistance. I tested the process with @spannernick's copy and it worked fine for me. Obviously you do this at your own risk and there is a risk that your Mini will still be bricked or that it doesn't work due to the bad block. NOTE FOR ANYONE ELSE: THIS IS ONLY FOR THE ESMT NAND. The ESMT nand(c64mini-esmt-nand-Spannernick.bin) is available in the PCU Download folder here. - Download the nand image (c64mini-esmt-nand-Spannernick.bin) and the nand_rw program and copy them copy them onto a USB stick that you know works with the Mini
- Then start the Mini in FEL mode. Do not load the nand driver (no 'insmod -f /opt/nand.ko')
- Then run the following to check whether it is indeed the ESMT nand:
#mount /dev/sda1 /mnt
#cd /mnt
#./nand_rw 20 2112 read_id
Raw ID data: 0xC8 0xD1 0x80 0x95 0x42
As the ID is correct you can proceed with erasing and writing the copy:
#./nand_rw 50 2112 erase_blocks 0 1024
#./nand_rw 50 2112 write_full 0 65535 c64mini-ESMT-nand.bin
This will take a long time but progress will be shown. When it is completed you can reboot your Mini and hopefully you will have the same result as me, seeing a 'Spannernick special' Mini Carousel menu. |
|
|
|
Post by refused75 on Nov 23, 2020 23:20:42 GMT
Just a quick note / warning: I took the 1.20 Mini nandb backup that Nick has on the Onedrive to bring my Mini back to factory conditions. Used the X-Windows-Mod, had the nand file renamed to "mini" in the directory "nands" on the USB drive. In the shell windows typed dd if=/media/usb/nands/mini of=dev/nandb (wait about a minute til prompt comes back) sync ...and then logged out of X-Windows-Mod and powered down the device. Worked perfectly! Mini back to original 1.20! And then I was feeling adventurous and tried the very same thing with the VIC-20 nandb from the same onedrive to my C64 Maxi and bricked it! No idea what happend, will try FEL rescue this week. Just a warning that this might NOT be working. Thanks, Boris Thank you Boris for your post, Good to know your way to recover your mini but unfortunately for me when I power on my mini I get only "black screen" so I can only go in FEL mode. As far as I understood in other forum posts the only way to activate X-windows mode is to reach carusel and then go in settings and then you can activate x-windows mode through usb pendrive....but I can't...so I can only work through FEL. Simon |
|
|
|
Post by refused75 on Nov 23, 2020 23:21:44 GMT
Good day JJ0 and Spannernick, I have never modded my mini but now I am really fond about the matter to restore
my mini nand and this hassle has been in any case a nice occasion to learn a lot of
things and know both of you. So I would ask to JJ0 whether you can provide this program to copy the ESMT nand so Spannernick can do his copy and put at disposal for me and for any needed users and whether you can instruct me with these tools to reformat and write back a copy of my ESMT nand. Many thanks to both of you for your time and kind assistance. I tested the process with @spannernick's copy and it worked fine for me. Obviously you do this at your own risk and there is a risk that your Mini will still be bricked or that it doesn't work due to the bad block. NOTE FOR ANYONE ELSE: THIS IS ONLY FOR THE ESMT NAND. The ESMT nand(c64mini-esmt-nand-Spannernick.bin) is available in the PCU Download folder here. - Download the nand image (c64mini-esmt-nand-Spannernick.bin) and the nand_rw program and copy them copy them onto a USB stick that you know works with the Mini
- Then start the Mini in FEL mode. Do not load the nand driver (no 'insmod -f /opt/nand.ko')
- Then run the following to check whether it is indeed the ESMT nand:
#mount /dev/sda1 /mnt
#cd /mnt
#nand_rw 20 2112 read_id
Raw ID data: 0xC8 0xD1 0x80 0x95 0x42
As the ID is correct you can proceed with erasing and writing the copy:
#nand_rw 50 2112 erase_blocks 0 1024
#nand_rw 50 2112 write_full 0 65535 c64mini-ESMT-nand.bin
This will take a long time but progress will be shown. When it is completed you can reboot your Mini and hopefully you will have the same result as me, seeing a 'Spannernick special' Mini Carousel menu. Dear JJ0 and Spannernick, Many thanks for your files and instructions. I have duly copied both files in USB pendrive ...but unfortunately I cannot read the ID of my nand so I am stopped at first step...nand_rw not found. I have also tried writing 50 ( instead of 20 .. ) but nand not found as well. Hoping this is due because I am not writing the commnads properly. I have not tried the next 2 final lines (erasing+writing) as before I prefer check with you as I couldn't read my ID nand. Please check my enclosed pic hoping this helps you understand why. Thank you for your checking and help. Simon Attachments:
|
|
|
|
Post by spannernick on Nov 24, 2020 0:09:01 GMT
You need to download nand_rw and copy it to the root of your USB Stick, I think it can't find it.
Try
mount /dev/sda1 /mnt
cd /mnt
./nand_rw 20 2112 read_id
./nand_rw 50 2112 erase_blocks 0 1024
./nand_rw 50 2112 write_full 0 65535 c64mini-esmt-nand-Spannernick.bin
|
|
|
|
Post by refused75 on Nov 24, 2020 7:13:16 GMT
You need to download nand_rw and copy it to the root of your USB Stick, I think it can't find it. Try mount /dev/sda1 /mnt
cd /mnt
./nand_rw 20 2112 read_id
./nand_rw 50 2112 erase_blocks 0 1024
./nand_rw 50 2112 write_full 0 65535 c64mini-esmt-nand-Spannernick.binIt is working!!!! :-)
After a couple of attempts that I could see only for 20 seconds the special Spannernick Carousel after rebooting....because my mini was crashing and freezing again and it was apparently unstable....finally after last nand erasing and writing attempt everything seems now very stable!
I am crossing my fingers...but it's AMAZING! I have not only recovered back to life my mini but I can also enjoy Spannernick Carousel! I am so excited and joyful and I really wish to thank Spannernick and JJ0 for their time and patience because they literally saved my mini giving it an amazing second life :-)
Simon |
|
|
|
Post by jj0 on Nov 24, 2020 7:16:37 GMT
You need to download nand_rw and copy it to the root of your USB Stick, I think it can't find it. Try mount /dev/sda1 /mnt
cd /mnt
./nand_rw 20 2112 read_id
./nand_rw 50 2112 erase_blocks 0 1024
./nand_rw 50 2112 write_full 0 65535 c64mini-esmt-nand-Spannernick.binI made a mistake in the instructions (now corrected in my earlier post) on running nand_rw, it should indeed be './nand_rw' |
|
|
|
Post by jj0 on Nov 24, 2020 7:18:11 GMT
You need to download nand_rw and copy it to the root of your USB Stick, I think it can't find it. Try mount /dev/sda1 /mnt
cd /mnt
./nand_rw 20 2112 read_id
./nand_rw 50 2112 erase_blocks 0 1024
./nand_rw 50 2112 write_full 0 65535 c64mini-esmt-nand-Spannernick.binIt is working!!!! :-)
After a couple of attempts that I could see only for 20 seconds the special Spannernick Carousel after rebooting....because my mini was crashing and freezing again and it was apparently unstable....finally after last nand erasing and writing attempt everything seems now very stable!
I am crossing my fingers...but it's AMAZING! I have not only recovered back to life my mini but I can also enjoy Spannernick Carousel! I am so excited and joyful and I really wish to thank Spannernick and JJ0 for their time and patience because they literally saved my mini giving it an amazing second life :-)
Simon Cool, great that we could revive your Mini, enjoy playing games again! |
|
|
|
Post by spannernick on Nov 24, 2020 13:29:04 GMT
You need to download nand_rw and copy it to the root of your USB Stick, I think it can't find it. Try mount /dev/sda1 /mnt
cd /mnt
./nand_rw 20 2112 read_id
./nand_rw 50 2112 erase_blocks 0 1024
./nand_rw 50 2112 write_full 0 65535 c64mini-esmt-nand-Spannernick.binIt is working!!!! :-)
After a couple of attempts that I could see only for 20 seconds the special Spannernick Carousel after rebooting....because my mini was crashing and freezing again and it was apparently unstable....finally after last nand erasing and writing attempt everything seems now very stable!
I am crossing my fingers...but it's AMAZING! I have not only recovered back to life my mini but I can also enjoy Spannernick Carousel! I am so excited and joyful and I really wish to thank Spannernick and JJ0 for their time and patience because they literally saved my mini giving it an amazing second life :-)
Simon Glad its working, nice one.. you properly wiped the bad block, after flashing a few times.. |
|
|
|
Post by spannernick on Nov 25, 2020 16:52:06 GMT
I have made a script for you so if you need to back up or copy you esmt nand again it makes it easier, I used it to copy my esmt nand. Its has a menu in it so just select a option you want to run and away you go.. all you do is copy it to the root of your USB Stick with nand_rw program and then run it with.. nand_rw program is included in the zip file.
mount /dev/sda1 /mnt
cd /mnt
./nandrw.sh And it will do the rest for you.. just pick 1,2,3, or 4 for quit I would like to add the Toshiba nand to it too but need the command line for it, I will look for that latter and in the future maybe this script could became part of FEL Mode on THEC64 Mini. I need to add a while loop to it so it goes back to the menu options, I add that later. Attachments:nand_rw.sh.zip (248.09 KB)
|
|
|
|
Post by refused75 on Nov 25, 2020 19:56:57 GMT
I have made a script for you so if you need to back up or copy you esmt nand again it makes it easier, I used it to copy my esmt nand. Its has a menu in it so just select a option you want to run and away you go.. all you do is copy it to the root of your USB Stick with nand_rw program and then run it with.. nand_rw program is included in the zip file.
mount /dev/sda1 /mnt
cd /mnt
./nandrw.shAnd it will do the rest for you.. just pick 1,2,3, or 4 for quit I would like to add the Toshiba nand to it too but need the command line for it, I will look for that latter and in the future maybe this script could became part of FEL Mode on THEC64 Mini. I need to add a while loop to it so it goes back to the menu options, I add that later. Thank you Nick, your script sounds very cool and helpful! Hoping it's not needed soon :-) as for the time being as I got my mini recovered
I wish to enjoy it and your Carousel and hoping to stay far from FEL mode for more than a while as I did a lot of "indigestion" about FEL mode these days :-). One question : May I upgrade now to the new official firmware my mini and/or
future firmware release? For now of course I didn't... as I do not want to risk to lose again my mini and mostly I do not want to lose your Carousel.
Many thanks
Simon
|
|
|
|
Post by spannernick on Nov 25, 2020 20:30:07 GMT
I just tried to update my THEC64 ESMT Mini to 1.4.2 to upgrade it and now its stuck on a black screen, weird must be if you updated it and you have played around with your games folder it stops the Mini working, thats not right, I have to flash my bin file again now, ay well..  I did for you anyway to see if it could be updated and it can't, oh and my THEC64 ESMT Mini is on update v1.3.1 cause I use PCUAE now so its has all three Carousels in it, v1.0.5, v1.3.2 and v1.4.2.. so in PCUAE you be able to use the latest version of the carousel but only if you have a THEC64 Maxi or THE VIC 20 cause its THE VIC 20 carousel so it will not work on thec64 mini, I might look into running the newer version of the Carousel on the Mini, If I can get the update to work with with mine, I do have 2 theC64 Mini's one TOS and this one. DO NOT upgrade it, you will end up with a blank screen, so is there something wrong with the update, I don't see me changing the games and music would cause it but could do, it probably to do with the games, I did updated it but a long time ago and it was all right. |
|
, I knew me buying them they would came in handy, even thought I don't use them no more... 
I did for you anyway to see if it could be updated and it can't, oh and my THEC64 ESMT Mini is on update v1.3.1 cause I use PCUAE now so its has all three Carousels in it, v1.0.5, v1.3.2 and v1.4.2.. 