Yes since I got 1.1 installed, I have to get SafeB9SInstaller to launch againFixes a compatibility issue in 1.1 where some payloads would respond poorly to ntrboot.
This ?
Yes since I got 1.1 installed, I have to get SafeB9SInstaller to launch againFixes a compatibility issue in 1.1 where some payloads would respond poorly to ntrboot.
This ?
Personally, going to stay on the stable build until further notice.
I'm in the same position.Yes since I got 1.1 installed, I have to get SafeB9SInstaller to launch again
Use "SafeB9SInstaller.firm". Backup your boot.firm on your sd card, copy over safeb9sinstaller.firm, rename to boot.firm, profit.I'm in the same position.
I've no idea how to fix this.

Then SafeB9SInstaller probably needs be recompiled with the latest commits.Getting error trying to start SafeB9SInstaller with the b9s 1.2
--
An exception occured
Processor: ARM9
Exception type: data abort
--
it's a pre-release, you're not supposed to be using it yet.
Me also, it seems we will have to wait until a new version of SafeB9SInstaller is released.Getting error trying to start SafeB9SInstaller with the b9s 1.2. im on b9s 1.1
--
An exception occured
Processor: ARM9
Exception type: data abort
--
Doesn't work if you are on 1.1, that's why I'm looking for a way to fix this.Use "SafeB9SInstaller.firm". Backup your boot.firm on your sd card, copy over safeb9sinstaller.firm, rename to boot.firm, profit.
Doesn't work if you are on 1.1, that's why I'm looking for a way to fix this.
cool, thanks!https://transfer.sh/bi8b5/SafeB9SInstaller.firm From SciresM's Twitter post.
Yepp, Godmode9 still doesn't work, but however atleast on 1.2 now.
That means payloads still need updates I guess.
This seems familiar...
- Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience
- (∩ ͡° ͜ʖ ͡°)⊃━☆゚