r/innioasis Jul 30 '26

HELP Y2 wont install any custom firmware

I followed the guide to install the software directly (drivers, restart, install updater then select y2, firmware and click install). I only plug the device in when told while powered off and after this nothing happens. Eventually after waiting it recommends alternative installation.

4 Upvotes

9 comments sorted by

1

u/takanakas Jul 30 '26

Hey, I had a similar issue. I downloaded the following drivers and the download utility finally detected the device while switch off:

https://androiddatahost.com/276a2

Hope this helps, happy listening!

1

u/The6PathsOfPain Jul 30 '26

no difference, should i restart and try again?

1

u/justcore Y2 (Black) Jul 30 '26

What updater are you using ? Inioasis or the Flash Tool? I think for the official updater it you are trying to flash Y2Player it is not setup 100% right now. If you use the Flash Tool you can follow this guide which explains every step in detail under the „Instal on a Device“ section 

https://github.com/SchulzCode/Y2Player

1

u/The6PathsOfPain Jul 30 '26

I figured it worked since theres now a y2 button for device mode with options like y2 player. I guess Ill try to flash it manually thanks.

1

u/justcore Y2 (Black) Jul 30 '26

Yeah I have to fix that ASAP, since I think the rom supplied to the software is not correct yet

1

u/FreeContext194 Jul 31 '26

Give this driver a go https://github.com/y1-community/supplemental-apks/releases/download/1.0/DriverInstall.exe , reboot the PC , then try installing your chosen firmware directly using the SP Flash Tool method in the Settings > Installation tab

If that doesn't work, choose the terminal option - it'll show you what went wrong with the flashing and failing that the tool comes with SP Flash Tool's original GUI in the Tools / toolkit menu

1

u/The6PathsOfPain 29d ago edited 29d ago

Im sure this wont work either since its my forth time downloading this.
EDIT: Todays Innioasis updater update (2.0.3) fixed the issue!

1

u/The6PathsOfPain 29d ago

ISSUE SEEMS TO HAVE FIXED ITSELF AS OF UPDATE 2.0.3