Open az4521 opened 7 years ago
if we figure out how to write to it, then we can use one card to recover the other. There's also the chance it just works(tm)
ok i will try it
@Dark-samus , if the card bricks, that doesnt mean it was wrote and flashed?
@dark-samus I just looked through your notes again, and I believe you're missing an "spi:6" to start the write function.
For those interested in how the update function works, you can view some of my notes here. They're not complete but explain parts of the process such as certain checks, order of operation, etc. I've only been able to work on this for a few minutes here and there, but it should still be pretty accurate.
@dark-samus
i have 2 BlueCards Laying around, waithing to be burned :P
If i can help, i would donate them both, just let me know
alright, finally got around to doing this; sorry everyone, just been busy. I believe I've patched everything so it should run on.... well, any cart really ace3ds_fix_all_mod.zip
@zaksabeast ahh, you're right. Thanks :)
the update starts but i get an error verify failed
interesting
but i didn't see any changes in the card
yeah, normal, it does no flash writes before it verifies the data
first says write and at 88% stops and says the verify error
The write appears to happen first, then the cart data gets read and compared against what was supposed to be written. That error occurs if the data doesn't match.
If your cart is fine, then it didn't write properly. (Meaning the commands to write and presumably read aren't the same as those that can use the update rom.)
my card is fine
sorry, I was thinking it was saying the verify failed at the decompress stage. Anyway, yeah, I think it's safe to say that those specific GW blue cards aren't anything like the Ace3ds+.
You're good :)
The gbatemp post I referenced earlier here mentioned a potential manufacturer change somewhere along the lines, which would support why some blue gateways work with ace3ds+ updates while others do not.
That was a neat experiment though and helped prove that there was probably manufacturer change as well as the checks being used are for hardware.
That happend with the new ace3ds_fix_all_mod.zip:
![img_20170901_101605 01](https://user-images.githubusercontent.com/6576487/29961225-2a89b97a-8eff-11e7-80d2-206146234fcd.jpg)
X-C1 also fails on verify.
this happens when i try to install ace3ds_fix_all_mod.zip.
![img_20170901_144513](https://user-images.githubusercontent.com/31549316/29983266-5212dea8-8f55-11e7-860c-076ada5b715b.jpg)
@LoLxD3D14 try the original one. It'll still give you that message, just need to press start+l anyway to start the update process. Is this a GW blue card or an ace3ds+ and if it's a GW blue card, what game does it show up as in the home menu
gateway "rev 002A", Deep Labyrinth Atlus Chip ID: 00000FC2 HW Rev: 00000000 with ace3ds_fix_all -> 00EF4015 Not a valid Cart. with the last ace3ds_fix_all_mod -> 00EF4015, Hardware=11.0, Firmware 2.1, Decompress data : OK, Check data OK, Don't need any patch... If i press start+L -> Patch successful ! Press A to power off The linker is OK :)
Hello! I have two ACE3DS+ carts with different PCB.
![01](https://user-images.githubusercontent.com/31561487/29993885-6f1b5eb2-8fc3-11e7-9b27-5af0d62b6a38.jpg) ![02](https://user-images.githubusercontent.com/31561487/29993887-73722ce8-8fc3-11e7-98b4-98e1e1212239.jpg)
![red-pcb-metroid](https://user-images.githubusercontent.com/31561487/29993898-a236879a-8fc3-11e7-8643-92dab7f052c1.png)
![green-pcb-spongebob](https://user-images.githubusercontent.com/31561487/29993925-4d384840-8fc4-11e7-881c-70e52714fb5a.png)
Gateway Blue, Deep Labyrinth Atlus Firmware: Wood R4 1.62
The ace3ds_fix_all_mod shows: ACE3DS firmware Fix 00FFFFFF Found Cart: Hardware:=11.0 Firmware=2.1 ... Verify failed!
But my cart seems ok.
![image](https://user-images.githubusercontent.com/3601376/30031116-27e1ae20-91cb-11e7-9800-7c569cec5194.png) ![image](https://user-images.githubusercontent.com/3601376/30031140-3c082eec-91cb-11e7-9de5-64d07030a82d.png) ![image](https://user-images.githubusercontent.com/3601376/30031097-1ba80a32-91cb-11e7-9cd4-ac960f282cdc.png)
@dark-samus I think the flash did not work properly. I can't use the Wood R4 1.62 or AOS 2.13 from Ace3ds Plus just the wood akmenu 1.56HW (gateway)
![p_20170904_190841](https://user-images.githubusercontent.com/31475297/30035108-d5fa13a0-91a6-11e7-87b6-38759d51348e.jpg) ![p_20170904_190938](https://user-images.githubusercontent.com/31475297/30035120-f9fbb56a-91a6-11e7-91a0-a3b743203060.jpg)
I get the same thing. Labyrinth Icon, 84% verify failed. Does nothing to the card though, because I can still use it. My board has the X-C on it.
I have the same; labyrinth icon, 82% verify failed. My board has X-C on the PCB.
@dark-samus I'm the guy who created the analysis thread on gbatemp about the blue GW cart. I see here that there are a lot more variations to these carts than I initially tought and it's (at least for me) impossible to keep track of what models exist and which do what. So a little suggestion from my side, would be to create a new thread at gbatemp, where we document these Ace3DS+ and blue GW cart PCBs in pictures, together with high res pics of all the ICs (if possible) and information about the compatability with any of the updaters posted here and when they have been bought + game icon in 3DS menu etc..
If that is something that might help you and you can confirm that these 2 carts are indeed the same, than please let me know and I will start this immediately.
@MRiCEQB I think the conclusion @dark-samus came to was that some GW Blue cards are Ace3DS+, while others are not even similar.
I think it could be a good idea, but I'd wait until @dark-samus confirms.
@kitling thanks for the reply, that's also the reason why I want to start this thread, so we all have a documentation which GW blue carts are indeed Ace3DS+ (like) devices and which are not.
Maybe this way we can also do assumptions for users, so they know what to expect beforehand from their available carts.
It would be awesome however, if the carts that failed with the modified updaters here could also be used with the same method - but that's something @dark-samus has to tell us :)
I have a Gateway Blue Card
With ace3ds_fix_all_mod I get: ACE3DS firmware Fix 00FFFFFF Found Cart: Hardware:=11.0 Firmware=2.1
And of course it fails writing at 84%
These are some pictures... I really hope model X-C can be flashed someday...
![back](https://user-images.githubusercontent.com/12029494/30124184-abb35d06-9334-11e7-9b02-f7989dce831e.png) ![front](https://user-images.githubusercontent.com/12029494/30124185-abb76f04-9334-11e7-8e06-2e2010e626b9.png)
@MRiCEQB it seems the main telling feature is the game the flashcart presents to the 3ds home menu. If it has deep labyrinth it seems to not be compatible, so far it seems the metroid and spongebob ones are compatible. That's an easy way to tell so far at least
@dark-samus of course my GW blue cart comes with deep labyrinth xD
I hope that one day these can be messed with as well, there has to be a way.
alright, people with Ace3ds+ cards and compatible GW blue cards, please try to backup flash with this: ntrboot_flasher.zip
post the results here on GH.
this is done by "Dump Flash", right? I am making an backup right now. (running since 10 minutes) How long can this take? (What is normal?)
Edit: After 30 minutes still not finished. Something seems to be not working correctly. Can I help to fix that problem? Can I find out, what exactly is causing this issue?
Can I flash boot9strap ntr 1.3 with this to my Ace3DS+(Spongebob as shown game)? Shall I upload the backup to make it accessible here?
Yeah same results here, only says "Dumping Flash" but nothing happens. You might need to add debug messages for every single step, so you can see what the problem is.
I tested it with my GW blue cart (Labyrinth icon - for the lulz) and with my Ace3DS+ (Spongebob icon), but both show the same thing.
@everyone else ... first make sure your flashcart is properly recognized by the 3DS in the home menu. My Ace3DS+ takes like 10 tries to finally show up in the home screen.
(Maybe this can also be added as a debug message, so the flasher first checks if the cart is even in there and displays something familiar, like the bootstrap name of the game).
same thing for me. I tried on my GW Blue w/ labyrinth icon. Just says dumping flash and never stops till I power off.
The same as the other guys... "Dumping flash" and nothing happens. Blue "Deep Labyrinth" card.
Yeah, I realized that I forgot to do the init sequence the updater does >.> I've implemented a lot of that, but not all of it yet. I'm working on it :)
Isn't this the same as the r4isdhc.com.cn?
I finally found my old Gateway Blue I had stashed away. I've got the same X-C board that @MollerAndre posted above, with the exception that my smaller chip matches with 25P10AV but says ST9341B underneath. The PCB markings are identical and it also identifies as Deep Labyrinth and the ACE3DS Firmware fix comes back as 00FFFFFF Hardware=11.0 Firmware=2.1
I would be willing to test new builds as they become available.
How Long it Takes?
When I try to run the fix all mod it tells me no update is needed. Is there a way to force the update? My board says X-D1 at the bottom.
Video of me trying: https://youtu.be/afZ09bly4fQ
UPDATE: I was able to press L and Start but it simply verified at 100% and the card still works fine. So ntrboot wasn't flashed.
@dark-samus Have you done any updates to the flasher since then? I'm willing to test new builds until either my cart is bricked or until you get a successful build. The most recent build didn't work it said successful but my cart wasn't modified.
Just got my r4isdhc.com.cn. Board is a little different, having epoxy on the flash chip, but otherwise pretty similar to the X-D1 found here. Deep labyrinth icon.
Another ace3ds-like clone: the gamecard 3D (www.n3dstt.com). It is not compatible with the kernel files for the ace3ds but it uses wood, too. Firmware update: https://www.dropbox.com/s/574q6s5lfkm2gme/fwUpdate_V6.20.rar?dl=0 Kernel: https://www.dropbox.com/s/l0oilq6okdfpkab/2013-N3DSTT.rar?dl=0
![2rwqdfs](https://user-images.githubusercontent.com/32749263/32231881-0e4feb44-be57-11e7-97d4-d18f4ee24662.jpg) ![vz78ua](https://user-images.githubusercontent.com/32749263/32231887-1462f9c2-be57-11e7-8cb9-021a0f4e42f2.jpg) ![fdhiep](https://user-images.githubusercontent.com/32749263/32231893-17a11cae-be57-11e7-9901-628576e05352.jpg)
@Tcm0 probably, it's not ace3ds+ clone. updater commands looks same as r4isdhc.hk's one.
You're right. The PCB looks identical to the r4isdhc.hk card.
@Tcm0 can you check dump as ak2i?
@d3m3vilurr I will try but the DS doesn't want to read the card currently. I think that it's a very bad contact issue.
Also got a X-C model (same as @polarbernd and @MollerAndre).
Sidenote, I got my Gateway in 08/feb/2015 (though it was from a Brazilian reseller).
firmware updates: https://filetrip.net/dl?Rqf4x1K5L5 - Wood R4 1.62 https://filetrip.net/dl?QCMwTu7FCo - AOS 2.13
Chip ID: 00000FC2 HW Rev: 00000000
Images (Click to Expand)