|
Post by omgngx on Jul 6, 2013 8:23:22 GMT -5
The X Shows up as an Ingenic Semiconductor when plugged in? Is that the correct driver? Sounds right... as long as your on 32 bit Windows (even though the program seems to install and run on 64 bit Windows, no one has gotten this thing to work on a 64 bit setup - even running a virtual 32 bit desktop, I think this is why chansterling is having trouble - he is still trying to implement this on a 64 bit setup through virtual software). Make sure that the micro SD is formatted in either fat16 or fat32, don't click anything else on the interface and your file should be in .img format even though you are choosing the uboot.bin option.
|
|
|
Post by superfrick on Jul 6, 2013 10:25:06 GMT -5
The X Shows up as an Ingenic Semiconductor when plugged in? Is that the correct driver? Sounds right... as long as your on 32 bit Windows (even though the program seems to install and run on 64 bit Windows, no one has gotten this thing to work on a 64 bit setup - even running a virtual 32 bit desktop, I think this is why chansterling is having trouble - he is still trying to implement this on a 64 bit setup through virtual software). Make sure that the micro SD is formatted in either fat16 or fat32, don't click anything else on the interface and your file should be in .img format even though you are choosing the uboot.bin option. Ok. I am certainly doing it wrong. In the pulldown I've been choosing the usb_boot.bin as the file. I tried again, this time choosing the hd_sd_image.img file and it still immediately jumps to 100% without actually doing anything. Is there any troubleshooting steps I can take to make sure the computer is actually seeing the X and Card? And yes, I am using a laptop with a fresh install of windows XP 32bit Edited to clarify: The device that immediately jumps to 100% is on the list as #2
|
|
|
Post by omgngx on Jul 6, 2013 14:19:00 GMT -5
Are you holding start when you plug the NGX in (NGX off)? Reboot the program, unplug the NGX, make sure the NGX is off and hold start on the NGX while plugging it in. You might also want to try running the program and flashing the image from the lowest level (root of c:) of your drive.
|
|
|
Post by superfrick on Jul 6, 2013 21:50:00 GMT -5
I think there may still be glue on a couple of pins. I'm researching what sort of solution I can do for the glue that won't ruin the X. I wish there was some sort of Diagnostic tool I could use to determine if I'm actually connecting and can see the card or not. We'll see how the glue removal comes along and I will post my results. I'm not afraid of sounding like an Idiot. I figure I'm asking the same questions others are nervous to ask
|
|
|
Post by superfrick on Jul 7, 2013 18:29:29 GMT -5
Are both the red and blue lights supposed to be lit during the flashing process? Once, it looked like it was going to actually start flashing. It didn't immediately jump to 100%, but only the blue light was lit and stayed at 0% for two hours.
Since then it jumps right to 100%.
My sd card was damaged in the removal. So I don't have a way of testing if the X will boot with its original settings, unless someone can direct me to a method of making a "new" micro sd card.
|
|
|
Post by superfrick on Jul 9, 2013 12:23:54 GMT -5
Are you holding start when you plug the NGX in (NGX off)? Reboot the program, unplug the NGX, make sure the NGX is off and hold start on the NGX while plugging it in. You might also want to try running the program and flashing the image from the lowest level (root of c:) of your drive. I've completed the inspection of the pins. None of them are broken, and they are all touching the proper pads of the micro sd card. I have the micro sd held in with electrical tape and confirming that USB Boot Device is showing up on the list of connected hardware before running the software. I moved the software and the image to the C drive on a windows 98 laptop. I run the software and select the hd_sd_image.img in the pulldown for uboot.bin and click the checkbox. 2 BOOT...Please Waite 100% appears for a second, and then drops to 0% and stays there. I am going to let it run for the next few hours to see if the progress bar moves at all.
|
|
|
Post by superfrick on Jul 9, 2013 18:16:43 GMT -5
UPDATE: Program ran for 5 hours and nothing changed. My NGX still does not boot. Any suggestions at this point would be appreciated. I've had nothing but bad luck when it comes to to the NGX.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 9, 2013 22:39:18 GMT -5
I'm very much starting to think that some 337 units just won't flash right whatever method used. I mean many people had trouble with the official update so it's possible whatever affected updating is also stopping up using this update method. I don't think all that many people have opened up the 337 so it's hard to tell how many can't update at all or if it's just us and we damaged the sd connector.
In any case I hear that tommo are offering an additional warranty if you register the neogeo x and one of the game packs.
|
|
|
Post by superfrick on Jul 10, 2013 10:32:52 GMT -5
I'm very much starting to think that some 337 units just won't flash right whatever method used. I mean many people had trouble with the official update so it's possible whatever affected updating is also stopping up using this update method. I don't think all that many people have opened up the 337 so it's hard to tell how many can't update at all or if it's just us and we damaged the sd connector. In any case I hear that tommo are offering an additional warranty if you register the neogeo x and one of the game packs. Oh? Their website is pretty lousy for information. I'll check again
|
|
|
Post by superfrick on Jul 10, 2013 10:54:54 GMT -5
Okay. I've tried again on a different computer. Another wiped laptop running a clean Windows XP 32 Service Pack 2 in Administrator Mode. Fail again. But hopefully we can get to the bottom of this. And thanks to the forum for not being a bucha haters during all of this I've PMed a couple of people and it turns out I'm not the only one who is unable to get this to work. Hopefully there is something in common we're not doing correctly or something different that can be done. To help with this, I'm uploading screenshots. This first one is just me loading the software with no changes to anything. Next, I closed the program and plugged in the X while holding start. I installed the drivers. Here's my device manager after I installed the drivers, unplugged the X, then plugged it back in holding start: whee! So I unplug the X again and run the software. Once the software is loaded, I plug in the X holding start, confirm that the USB Boot Device is showing up as a plugged in device and I select the image! It jumps to 100% for a split second, and then does nothing. Nooooothing! It stays at 0% forever. So, here are my questions: 1) Other people with bricks. Did you do anything different? 2) People with working updates. Did you do anything different? 3) People in the know, with big brains and are awesome for helping: Is there anything else we can try? I can follow directions. I'm willing to try alternate images, alternate flashers, and heck if you can get me an alternate OS I'd even try that too! I really don't have to own a $129 brick, and the others who are in the same boat as me don't want to own a $129 brick either. ($129 is the cost of the Handheld-only 500 unit coming out maybe in August).
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 10, 2013 11:10:10 GMT -5
The information was on their facebook as is most information they seem to post. The official site is rarely updated so you won't find much there. Here is the link to register: tommo.com/neogeox/registration/
|
|
|
Post by omgngx on Jul 10, 2013 17:23:41 GMT -5
Shoot. Try the Uimage button for flashing the image file instead of Uboot.bin (just in case) It's been about 6 months since I have personally done this so, maybe I am remembering it wrong... I also know that some types/brands of SD cards don't work well with the SD card hack, maybe some brands won't work on the internal as well... try different brands of 4 GB micro SDs...
|
|
|
Post by superfrick on Jul 10, 2013 19:07:06 GMT -5
Shoot. Try the Uimage button for flashing the image file instead of Uboot.bin (just in case) It's been about 6 months since I have personally done this so, maybe I am remembering it wrong... I also know that some types/brands of SD cards don't work well with the SD card hack, maybe some brands won't work on the internal as well... try different brands of 4 GB micro SDs... Nah. Unfortunately the Uimage gets the same result. I am using a Scandisk card, which is what the 2gb one I pried out of the X was as well. I'm hoping there is either a step I'm missing, an alternate way to flash this thing, or a way to get a new card image and boot this thing back to normal. I'd even put 500 on it at this point.
|
|
|
Post by omgngx on Jul 10, 2013 19:10:11 GMT -5
It is possible that the failed 500 update is to blame...
|
|
|
Post by superfrick on Jul 10, 2013 19:18:00 GMT -5
It is possible that the failed 500 update is to blame... I never tried to put 500 on this This was an untouched 337 that I've now thoroughly jacked up
|
|