ROM Hack Trouble running custom .code

  • Thread starter Thread starter JustPingo
  • Start date Start date
  • Views Views 47,425
  • Replies Replies 315
  • Likes Likes 8
Status
Not open for further replies.
The eshop is not working as expected, they are trying to find a solution, so you have to wait more for the PoC
Actually, I think they don't need an internet connection so I believe the eshop problem won't interfere
I believe they must have hit a rock, or possibly a diamond in the rough, given his last tweets.
 
Nah, I'm not talking about that. I can't give details, but the eshop application doesn't have access to a service required to install cias (and more), JustPingo told me a few hours ago.
 
Nah, I'm not talking about that. I can't give details, but the eshop application doesn't have access to a service required to install cias (and more), JustPingo told me a few hours ago.
So the dream is dead?
 
Nah, I'm not talking about that. I can't give details, but the eshop application doesn't have access to a service required to install cias (and more), JustPingo told me a few hours ago.

So I can't be a pirate now? Well my dreams have been crushed...
 
@MasterLel I'm pretty sure that was ment to be kept private.

Either way, no sense in panicking. There is more than one way of doing this, JustPingo has said that on the thread already.
 
Last edited by Coleman_C18,
  • Like
Reactions: KyogreKid
No it's not dead, I can't tell more because it's "private" (sorry JustPingo if I wasn't supposed to say that), and not really my business, but they are still hard working on it
 
Last edited by MasterLel,
Nah, I'm not talking about that. I can't give details, but the eshop application doesn't have access to a service required to install cias (and more), JustPingo told me a few hours ago.
I just looked at the service access list for eShop version 0x65 (10.0 or 10.1 or something along those lines).

It really says am:sys there. That's the same as what home menu has (and the reason why a particular FBI release found the am service but couldn't install CIAs after all) and really is unsifficient. tiger also has nim:s, though, which in turn has am:net. So I'm wildly guessing this is what happens:

  1. tiger causes creation of the ticket
  2. tiger passes the title ID to nim
  3. nim downloads the ticket and the title from the CDN, decrypts it and passes that off to am:net streamingly
  4. am:net then proceeds to actually install the ticket and title received from nim
 
I just looked at the service access list for eShop version 0x65 (10.0 or 10.1 or something along those lines).

It really says am:sys there. That's the same as what home menu has (and the reason why a particular FBI release found the am service but couldn't install CIAs after all) and really is unsifficient. tiger also has nim:s, though, which in turn has am:net. So I'm wildly guessing this is what happens:

  1. tiger causes creation of the ticket
  2. tiger passes the title ID to nim
  3. nim downloads the ticket and the title from the CDN, decrypts it and passes that off to am:net streamingly
  4. am:net then proceeds to actually install the ticket and title received from nim

Tiger is the codename for...
 
Pretty much. But there's other tricks, please not worry and wait longer lol. Sorry.

By the way some things can be misleading on 3dbrew. Be careful. We experienced that lol
 
Last edited by JustPingo,
  • Like
Reactions: DatHax0r
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum