|
|
Post by shelby on Mar 30, 2022 17:18:25 GMT
Sorry if this is basic question, however I have spent a day and a half trying to bring my C64 Maxi using the advice on this forum such as: thec64community.online/thread/720/rescue-bricked-c64-maxi thec64community.online/thread/708/the64-maxi-mode-rescue-bootIt's obvious I am not as technologically savvy as many of you, so bear with me. I followed a youtube video on how to use TheC64 game tool to remove the stock games on my Maxi and replace with 40 of my personal favorites. At the end of the day after everything was done, I powered up TheC64 which displayed the splash screen and the screen went blank. BTW, I am running Windows 11. I followed the suggestions on the aforementioned sites to remedy the issue. Things go swell until I get to the step where I run boot.cmd in the FEL Rescue Boot folder; as I don't see the addition of the two drives for the NAND files Any thoughts? Thank you for your time Shelby |
|
|
|
Post by jj0 on Mar 30, 2022 19:50:33 GMT
Sorry if this is basic question, however I have spent a day and a half trying to bring my C64 Maxi using the advice on this forum such as: thec64community.online/thread/720/rescue-bricked-c64-maxi thec64community.online/thread/708/the64-maxi-mode-rescue-bootIt's obvious I am not as technologically savvy as many of you, so bear with me. I followed a youtube video on how to use TheC64 game tool to remove the stock games on my Maxi and replace with 40 of my personal favorites. At the end of the day after everything was done, I powered up TheC64 which displayed the splash screen and the screen went blank. BTW, I am running Windows 11. I followed the suggestions on the aforementioned sites to remedy the issue. Things go swell until I get to the step where I run boot.cmd in the FEL Rescue Boot folder; as I don't see the addition of the two drives for the NAND files Any thoughts? Thank you for your time Shelby I haven't ever done this in Windows 11, but I assume it is the same as using it in Windows 10. Do you see the files being uploaded when you run boot.cmd: USB device 001:062 Allwinner H3 02c00081:25c04620:78a28014:542c0793
100% [================================================] 13 kB, 184.4 kB/s
100% [================================================] 934 kB, 259.6 kB/s
100% [================================================] 15626 kB, 260.1 kB/sIf not, are there any error messages? What happens if instead of boot.cmd you manually run: sunxi-fel.exe -l |
|
|
|
Post by shelby on Apr 3, 2022 19:56:07 GMT
Sorry if this is basic question, however I have spent a day and a half trying to bring my C64 Maxi using the advice on this forum such as: thec64community.online/thread/720/rescue-bricked-c64-maxi thec64community.online/thread/708/the64-maxi-mode-rescue-bootIt's obvious I am not as technologically savvy as many of you, so bear with me. I followed a youtube video on how to use TheC64 game tool to remove the stock games on my Maxi and replace with 40 of my personal favorites. At the end of the day after everything was done, I powered up TheC64 which displayed the splash screen and the screen went blank. BTW, I am running Windows 11. I followed the suggestions on the aforementioned sites to remedy the issue. Things go swell until I get to the step where I run boot.cmd in the FEL Rescue Boot folder; as I don't see the addition of the two drives for the NAND files Any thoughts? Thank you for your time Shelby I haven't ever done this in Windows 11, but I assume it is the same as using it in Windows 10. Do you see the files being uploaded when you run boot.cmd: USB device 001:062 Allwinner H3 02c00081:25c04620:78a28014:542c0793
100% [================================================] 13 kB, 184.4 kB/s
100% [================================================] 934 kB, 259.6 kB/s
100% [================================================] 15626 kB, 260.1 kB/sIf not, are there any error messages? What happens if instead of boot.cmd you manually run: sunxi-fel.exe -lI have attached what I get when running the above command  Thank you Shelby |
|
|
|
Post by shelby on Apr 5, 2022 17:02:53 GMT
I haven't ever done this in Windows 11, but I assume it is the same as using it in Windows 10. Do you see the files being uploaded when you run boot.cmd: USB device 001:062 Allwinner H3 02c00081:25c04620:78a28014:542c0793
100% [================================================] 13 kB, 184.4 kB/s
100% [================================================] 934 kB, 259.6 kB/s
100% [================================================] 15626 kB, 260.1 kB/sIf not, are there any error messages? What happens if instead of boot.cmd you manually run: sunxi-fel.exe -lI have attached what I get when running the above command <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button> Thank you Shelby |
|
|
|
Post by shelby on Apr 5, 2022 17:28:23 GMT
Almost there in regards to restoring the C64 Maxi to original state; after using with the C64 Game Tool, which resulted in Bricking.
I have the two drives E: (~16mb) F: (~192MB), unformatted
However when I run the imager I get the following message:
Not enough available space 1.0
required: 384512 sectors
available : 383488 sectors
Sector size: 512
Running Windows 11
Shelby
|
|
|
|
Post by jj0 on Apr 5, 2022 18:56:45 GMT
I haven't ever done this in Windows 11, but I assume it is the same as using it in Windows 10. Do you see the files being uploaded when you run boot.cmd: USB device 001:062 Allwinner H3 02c00081:25c04620:78a28014:542c0793
100% [================================================] 13 kB, 184.4 kB/s
100% [================================================] 934 kB, 259.6 kB/s
100% [================================================] 15626 kB, 260.1 kB/sIf not, are there any error messages? What happens if instead of boot.cmd you manually run: sunxi-fel.exe -lI have attached what I get when running the above command <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button> Thank you Shelby From the output of the sunxi-fel -l command you can see that the Maxi is recognised as being in FEL mode. So that at least works. But you haven't answered my first question: Do you see the files being uploaded when you run boot.cmd: USB device 001:062 Allwinner H3 02c00081:25c04620:78a28014:542c0793
100% [================================================] 13 kB, 184.4 kB/s
100% [================================================] 934 kB, 259.6 kB/s
100% [================================================] 15626 kB, 260.1 kB/sIf not, are there any error messages? Also if possible: - Can you please copy/paste output you see in 'code' mode rather than adding pictures/screenshots? You can get 'code' mode by clicking on the 'C' icon
- When replying including quoting the post you are replying to please type your reply outside the quoted text box. It makes it easier to read and understand
|
|
|
|
Post by jj0 on Apr 5, 2022 19:10:08 GMT
Almost there in regards to restoring the C64 Maxi to original state; after using with the C64 Game Tool, which resulted in Bricking. I have the two drives E: (~16mb) F: (~192MB), unformatted However when I run the imager I get the following message: Not enough available space 1.0 required: 384512 sectors available : 383488 sectors Sector size: 512 Running Windows 11 Shelby Out of interest, how did you get it showing up the drives when at first it didn't work? On the error message: - What imager program did you use?
- What is the exact size in bytes of the nandb file you are trying to write back to drive F:?
- What is the exact size in bytes of the full drive F:?
384512 sectors of 512 bytes = 196870144 bytes which is the size of a Maxi nandb copy AFAIK. 383488 sectors of 512 bytes = 196345856 bytes which is less than that but I don't know why that would be The difference = 1024 sectors of 512 bytes |
|
|
|
Post by shelby on Apr 10, 2022 15:19:30 GMT
Previously, I would simply double click on the boot.cmd file in the Windows directory of the recovery tool. Alas, the command prompt screen would only show for half a second.
The next go-round was successful because I decided to open the command prompt window and run boot.cmd from there. It was nice as I could watch the progress and it resulted in the E: and F: drives being created.
As far as the imager, I tried both Win32 and BalenaEtcher. Both told me that NANDB.img was 524.3 kb larger than the drive space.
NANDB-Maxi is 192,256 kb and it came from the recovery one drive folder
When I go into Win11 disk management, it shows F: 100% free @ 187MB
Shelby
|
|
|
|
Post by jj0 on Apr 10, 2022 15:55:45 GMT
Previously, I would simply double click on the boot.cmd file in the Windows directory of the recovery tool. Alas, the command prompt screen would only show for half a second. The next go-round was successful because I decided to open the command prompt window and run boot.cmd from there. It was nice as I could watch the progress and it resulted in the E: and F: drives being created. As far as the imager, I tried both Win32 and BalenaEtcher. Both told me that NANDB.img was 524.3 kb larger than the drive space. NANDB-Maxi is 192,256 kb and it came from the recovery one drive folder When I go into Win11 disk management, it shows F: 100% free @ 187MB Shelby Hard to say. You could try to boot off a Ubuntu install USB stick, then you can start FEL mode and actually mount the nandb drive (as Linux supports the ext4 format it is in) and edit it. Or try to restore it see if that works. Or restore regardless of the size difference if that's possible. |
|
