https://github.com/GaryOderNichts/Bloopair/releasesNice work. I've tested it a few hours now and it works like a charm! Thank you for your effort.
Btw, am I the only one who can't find Bloopair for Tiramisu?
https://github.com/GaryOderNichts/Bloopair/releasesNice work. I've tested it a few hours now and it works like a charm! Thank you for your effort.
Btw, am I the only one who can't find Bloopair for Tiramisu?
Well guess I'm blind. Thank you. ^^
https://github.com/GaryOderNichts/Bloopair/releases/tag/v0.5.0-tiramisuBtw, am I the only one who can't find Bloopair for Tiramisu?
This link on first post is broken.via the PayloadLoader.
thanks, just tested the usb loader gx forwarder. it worked, no problem.The Autoboot and HBLInstallerWrapper modules have been updated.
Download the latest Tiramisu package here:
https://tiramisu.foryour.cafe/package/tiramisu (Click on "Download All" and copy the files to your sd card)
Changelog:
- Autoboot: Fix quick starting into applets
- HBLInstallerWrapper: Fix launching channels that execute their own exploits. (e.g. Homebrew launcher channel and any forwarders based on this channel like the Retroarch forwarder)
Hey! Long time nohi,
nice work ! glad seeing you are still working on wiiU.
Mocha is patching the IOSU to override the link to the update server and the name of name in the XML result. This also happens when booting the console without hacks (no sd card or holding R while launching). Update are not blocked when you boot it an environment that is not using mocha (or an other of mocha without this builtin update blocker).there are unanswered questions asked multiple times in the thread, like "how the blocking update is working?" while eshop still sorking.
You can directly run the "installer"-environment if you plan to install anyway. The guide is just telling the user to run tiramisu first because the installer step is fully optional.Can we run the "installer" environment on first run, or should we follow the guide and run "tiramusu" first without installing, then on next boot run installer?
The installer only supports injecting into H&S, the guide may be a bit misleading there. There is just a summary which title + region will be used for the injection, but no selection."Press the A button to check if you can install the PayloadLoader. It should now tell you what app the PayloadLoader can be installed onto."
why check if it "can" be installed? it can't always be done? there are different app it can be installed onto? the guide doesn't tell to select health&safety. maybe it's currently the only possible title.
Yes, in theory you don't need to remove anything. It would still be confusing though. Even setup a coldboot Tiramisu while CBHC is still active should work (aka won't brick your console), but still not recommended. Better have a clean start before migrating.I suppose haxchi users can keep the patched apps even if the guide suggest to delete it first (can be deleted later), as long as they don't launch haxchi while tiramisu is running. one or the other. but haxchi is not needed anymore if we can patch using h&s app instead.
Yeah, updating the PayloadLoader is exactly the same as updating. You have to remove coldbooting before you can update though. In an ideal world we won't ever need to update the PayloadLoader, at least thats the idea. All the updating should be possible by just putting new files on the sd card.the installer has "install/update" choice. maybe the guide could add an update page explaining which file to put/replace on SD, run h&s, press X, installer, update. (am I good?)
oh, that one is important to know. You said it shouldn't need to be updated, but just in case, that info is usefulYou have to remove coldbooting before you can update though
its working now. but idk why Hyrule Warriors not working anymore.The Autoboot Module and EnvironmentLoader have been updated
Download the latest tiramisu + environment package here and copy the files to your sd card.
https://tiramisu.foryour.cafe/api/download?packages=tiramisu,environmentloader
Changelog for both:
- Fix a black TV screen issue when coldbooting into the environment or autoboot menu.
This post right here: https://gbatemp.net/threads/cbhc-v1-6-coldboot-haxchi-cfw.452615/page-91#post-8272093Do you have a link to info on this?
the updates are coming fast, and all it seems to be is replacing files. can now load the homebrew launcher channel as well as usb loader gx forwarder.This post right here: https://gbatemp.net/threads/cbhc-v1-6-coldboot-haxchi-cfw.452615/page-91#post-8272093
The more I'm thinking about it, the more I'm thinking this isn't the biggest deal of a feature to lose, I only ever really quickstart 1 of 2 homebrew apps, the autboot plugin system or sdcafiine (and of course I would quickboot to the homebrew loader or vWii menu, but the return of the system's quickboot screen should replace those quick launch methods). So what I could do is make channels for these 2 homebrew and use them enough so that they appear on my GamePad's quickboot selection screen every time. Yeah, I'm probably about to make the change today I think.
I found a problem (I don't know if someone already pointed out)
If you have an usb device connected to the console and then access system settings, when you go back to Wii U Menu it will say that you've connected/disconnected one of the usb ports, it will then proceed to load the Wii U Menu once again and the same message will pop up again, it will keep looping on that until you reboot the console.
Oh shit, a lot happens when you're asleep lolthe updates are coming fast, and all it seems to be is replacing files. can now load the homebrew launcher channel as well as usb loader gx forwarder.
Video:
Started recording it from the moment I powered the console on.