Homebrew [Release] Miiverse Custom Image Tool

  • Thread starter Thread starter PF2M
  • Start date Start date
  • Views Views 237,353
  • Replies Replies 1,563
  • Likes Likes 36
Status
Not open for further replies.
This tool? The tool itself, that's not cancer.

This, on the other hand...
Magicquote.jpeg
Kill me.
 
  • Like
Reactions: Ruby Gloom
I think I finally did it...

myMmoP9.png


#FrontPageHype
I think that this marks the first occasion ever when an image from a homebrew app was publically visible on the home page of a popular and high-traffic Nintendo-owned and operated website!:O

Congratulations on making history!:bow:
 
I would love to see someone post the URL to that ISO site, or an image of sysUpdater, Gateway, rxTools, etc.
 
  • Like
Reactions: PF2M
I nearly posted this then I remembered I wasn't supposed to have those apps
I just posted an image of sysUpdater downgrading a 3DS, plus I told everyone to Google MemChunkHax3 (because I assume everyone on MiiVerse is probably on 10.6). Counting the minutes until I'm banned (I've had four posts taken down already, but I think this is the straw that breaks the camel's back).
 
So while I was looking up some information about Wii homebrew, I found this old page that documented an older method to access the Wii Shop Channel from a PC. It says that it was patched in 2008 because a certificate is needed to do it nowadays, but I still wonder... what if we could trick Miiverse to think we were on a 3DS/Wii U, and upload any images we wanted through a computer?

Maybe someday!

Edit: If anybody knows anything about the Miiverse 3DS/Wii U client (domains, user agents, etc.) then feel free to post about it and I'll look into it!
 
Last edited by PF2M,
So while I was looking up some information about Wii homebrew, I found this old page that documented an older method to access the Wii Shop Channel from a PC. It says that it was patched in 2008 because a certificate is needed to do it nowadays, but I still wonder... what if we could trick Miiverse to think we were on a 3DS/Wii U, and upload any images we wanted through a computer?

Maybe someday!

Edit: If anybody knows anything about the Miiverse 3DS client (domains, user agents, etc.) then feel free to post about it and I'll look into it!
just dumped connection log. gonna check other info.
Pcap filter: [OK]
Gateway found: 192.168.10.1 : [A4-12-42-B5-80-E4]
Starting poisoning 192.168.10.3 : [CC-FB-65-91-6A-19]
01:41:24/12/03/16: 192.168.10.6:41938<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAVVAAi84X739.jpg (7Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAVVAAi84X739
*****************
01:41:24/12/03/16: 192.168.10.3:53195<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAVVAAi84X739.jpg (7Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAVVAAi84X739
*****************
01:41:24/12/03/16: 192.168.10.6:41940<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAXEQAtx63naw.jpg (4Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAXEQAtx63naw
*****************
01:41:24/12/03/16: 192.168.10.3:53207<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAXEQAtx63naw.jpg (4Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAXEQAtx63naw
*****************
01:41:24/12/03/16: 192.168.10.6:41944<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAYygAU8ycV0t.jpg (6Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAYygAU8ycV0t
*****************
01:41:24/12/03/16: 192.168.10.3:53209<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAYygAU8ycV0t.jpg (6Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAYygAU8ycV0t
*****************
01:41:24/12/03/16: 192.168.10.6:41942<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAUbwAAgsb8CW.jpg (783b)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAUbwAAgsb8CW
*****************
01:41:24/12/03/16: 192.168.10.3:53212<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAUbwAAgsb8CW.jpg (783b)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAUbwAAgsb8CW
*****************
01:41:24/12/03/16: 192.168.10.6:41939<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAUAABAQigApAr6j8k.jpg (2Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAUAABAQigApAr6j8k
*****************
01:41:24/12/03/16: 192.168.10.3:53198<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAUAABAQigApAr6j8k.jpg (2Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAUAABAQigApAr6j8k
*****************
01:41:24/12/03/16: 192.168.10.6:41943<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAXwQAcbqIuDG.jpg (1Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAXwQAcbqIuDG
*****************
01:41:24/12/03/16: 192.168.10.3:53217<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAXwQAcbqIuDG.jpg (1Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAXwQAcbqIuDG
*****************
01:41:24/12/03/16: 192.168.10.6:41941<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAXAgAZKPHNrg.jpg (8Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAXAgAZKPHNrg
*****************
01:41:24/12/03/16: 192.168.10.3:53208<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAXAgAZKPHNrg.jpg (8Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAXAgAZKPHNrg
*****************
01:41:24/12/03/16: 192.168.10.6:41947<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAVewAee1hyz2.jpg (3Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAVewAee1hyz2
*****************
01:41:24/12/03/16: 192.168.10.3:53222<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAVewAee1hyz2.jpg (3Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAVewAee1hyz2
*****************
01:41:24/12/03/16: 192.168.10.6:41949<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAASYwAASEeb2x.jpg (7Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAASYwAASEeb2x
*****************
01:41:24/12/03/16: 192.168.10.3:53230<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAASYwAASEeb2x.jpg (7Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAASYwAASEeb2x
*****************
01:41:24/12/03/16: 192.168.10.6:41945<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAXmgASkb3vQ9.jpg (2Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAXmgASkb3vQ9
*****************
01:41:24/12/03/16: 192.168.10.6:41952<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/zlCfzRQvoRs843cUm9.jpg (4Kb)
URL: d1akpag8su1p2e.cloudfront.net_o3p_zlCfzRQvoRs843cUm9
*****************
01:41:24/12/03/16: 192.168.10.3:53218<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAXmgASkb3vQ9.jpg (2Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAXmgASkb3vQ9
*****************
01:41:24/12/03/16: 192.168.10.3:53247<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/zlCfzRQvoRs843cUm9.jpg (4Kb)
URL: d1akpag8su1p2e.cloudfront.net_o3p_zlCfzRQvoRs843cUm9
*****************
01:41:24/12/03/16: 192.168.10.6:41946<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAASaAA030Jp-J.jpg (857b)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAASaAA030Jp-J
*****************
01:41:24/12/03/16: 192.168.10.3:53219<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAASaAA030Jp-J.jpg (857b)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAASaAA030Jp-J
*****************
01:41:24/12/03/16: 192.168.10.6:41948<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAWRgAWWRuxHv.jpg (4Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAWRgAWWRuxHv
*****************
01:41:24/12/03/16: 192.168.10.3:53225<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAWRgAWWRuxHv.jpg (4Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAWRgAWWRuxHv
*****************
01:41:25/12/03/16: 192.168.10.6:41950<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/zlCfzQ0fjvYnQuz2Uf.jpg (4Kb)
URL: d1akpag8su1p2e.cloudfront.net_o3p_zlCfzQ0fjvYnQuz2Uf
*****************
01:41:25/12/03/16: 192.168.10.3:53237<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/zlCfzQ0fjvYnQuz2Uf.jpg (4Kb)
URL: d1akpag8su1p2e.cloudfront.net_o3p_zlCfzQ0fjvYnQuz2Uf
*****************
01:41:25/12/03/16: 192.168.10.6:41951<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAUEAAPSrthP2.jpg (6Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAUEAAPSrthP2
*****************
01:41:25/12/03/16: 192.168.10.3:53244<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAUEAAPSrthP2.jpg (6Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAUEAAPSrthP2
*****************
01:41:25/12/03/16: 192.168.10.6:41954<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAAS7wAtdRBeYk.jpg (7Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAS7wAtdRBeYk
*****************
01:41:25/12/03/16: 192.168.10.3:53260<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAAS7wAtdRBeYk.jpg (7Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAAS7wAtdRBeYk
*****************
01:41:25/12/03/16: 192.168.10.6:41953<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/zlCfzRNrSx0E-a1zez.jpg (5Kb)
URL: d1akpag8su1p2e.cloudfront.net_o3p_zlCfzRNrSx0E-a1zez
*****************
01:41:25/12/03/16: 192.168.10.3:53250<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/zlCfzRNrSx0E-a1zez.jpg (5Kb)
URL: d1akpag8su1p2e.cloudfront.net_o3p_zlCfzRNrSx0E-a1zez
*****************
01:41:25/12/03/16: 192.168.10.6:41955<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/zlCfzQ0F5lo0CpUIVy.jpg (2Kb)
URL: d1akpag8su1p2e.cloudfront.net_c3p_zlCfzQ0F5lo0CpUIVy
*****************
01:41:25/12/03/16: 192.168.10.3:53263<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/zlCfzQ0F5lo0CpUIVy.jpg (2Kb)
URL: d1akpag8su1p2e.cloudfront.net_c3p_zlCfzQ0F5lo0CpUIVy
*****************
01:41:26/12/03/16: 192.168.10.6:41956<-54.192.233.161:80
Protocol: HTTP File:Res/HTTP/192.168.10.6/AAQAAAARcgAHgktahP.jpg (3Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAARcgAHgktahP
*****************
01:41:26/12/03/16: 192.168.10.3:53272<-54.192.233.196:80
Protocol: HTTP File:Res/HTTP/192.168.10.3/AAQAAAARcgAHgktahP.jpg (3Kb)
URL: d1akpag8su1p2e.cloudfront.net_t3p_AAQAAAARcgAHgktahP
*****************
 
  • Like
Reactions: I pwned U! and PF2M
If you had to describe this tool is one word what would it be.

CANCER
Everyone on Discord told PF2M not to release it with unique ID spoofing


He didn't listen

--------------------- MERGED ---------------------------

So while I was looking up some information about Wii homebrew, I found this old page that documented an older method to access the Wii Shop Channel from a PC. It says that it was patched in 2008 because a certificate is needed to do it nowadays, but I still wonder... what if we could trick Miiverse to think we were on a 3DS/Wii U, and upload any images we wanted through a computer?

Maybe someday!

Edit: If anybody knows anything about the Miiverse 3DS client (domains, user agents, etc.) then feel free to post about it and I'll look into it!
We can extract the 3DS offline mode data, and in fact, I have done that, (PM for link) but it works weirdly; Miiverse's applet is just the web browser, but with special controls
To extract the actual Miiverse online link, we would have to view RAM in the applet, which wouldn't really be much possible.
The 3DS/WiiU Miiverse probably doesn't need a user agent, but it definitely needs a valid-signed cert.
 
  • Like
Reactions: BurningDesire
Me on Discord told PF2M not to release it with unique ID spoofing
Fixed that for you.
We can extract the 3DS offline mode data, and in fact, I have done that, (PM for link) but it works weirdly; Miiverse's applet is just the web browser, but with special controls.
Will hit you up on Skype for that.
To extract the actual Miiverse online link, we would have to view RAM in the applet, which wouldn't really be much possible.
You sure that we couldn't look for links in the code of the Miiverse CIAs? Unless it's dynamic IPs or something like that, I'm sure it wouldn't be impossible to at least try searching for a domain kind of thing.
 
Is it possible to make custom Youtube post on Miiverse with this tool ?
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum