It is currently Wed Dec 12, 2018 3:40 am

All times are UTC - 7 hours





Post new topic Reply to topic  [ 125 posts ]  Go to page Previous  1 ... 5, 6, 7, 8, 9
Author Message
PostPosted: Sat Nov 17, 2018 2:30 am 
Offline

Joined: Tue Jan 11, 2011 4:41 am
Posts: 43
I have this error when trying to install unlaunch 1.8: "You have discovered unknown old firmware version"

My dsi xl was on 1.4E. I used flipnote to install unlaunch 1.8. I had some problems with hiyacfw and decided to start everything form scratch. So i uninstalled unlaunch using the uninstall option. After that I updated the console to 1.4.5E. Also I deleted 2 brain training games from it's memory. Also the internet browser and nintendo dsi+ internet. Now If i try to install unlaunch again, I get that error.


Top
 Profile  
 
PostPosted: Sat Nov 17, 2018 5:05 am 
Offline

Joined: Fri Feb 24, 2012 12:09 pm
Posts: 729
That is odd. I had added that warning in unlaunch v1.5, hoping to find with people who have old firmware from 2008 (ie. firmware v1.2 or older). Mostly because I want to ask them if they have the same system files as later consoles (eg. font and wifi firmware).

What I am doing is checking the file creation timestamp for the launcher's title.tmd file. If it's saying year 2008 then unlaunch is bugging you with the unknown firmware warning message.

Not sure why you get warning that on firmware v1.4.5E. Maybe your console did originally have v1.2E or older installed? And any later system update(s) did maintain the old file creation timestamp for title.tmd. I don't if that would happen - it would depend on if the update is "overwriting" the old .tmd file, or if it's "replacing" the old .tmd file.

But... you didn't get the warning with firmware v1.4E on the same console? Weird. Or did you use an older unlaunch version back then (ie. something older than unlaunch v1.5)?
EDIT: Stupid question. You said you used v1.8 for install+uninstall (and uninstall didn't even exist before v1.5).
Hmmm, maybe the battery backed realtime clock was somehow reset back to 2008 at time when installing v1.4.5E?

---

Well, I could try to detect older firmware versions via some other method. Best would be checking the version data file (but it's difficult to extract the data from there).
Or better: Does somebody HAVE dumped old firmware versions like v1.0J, and could answer a few questions about it?
Then I could just completely remove the warning about yet unknown firmwares : )


Top
 Profile  
 
PostPosted: Sat Nov 17, 2018 5:40 am 
Offline

Joined: Tue Jan 11, 2011 4:41 am
Posts: 43
nocash wrote:
That is odd. I had added that warning in unlaunch v1.5, hoping to find with people who have old firmware from 2008 (ie. firmware v1.2 or older). Mostly because I want to ask them if they have the same system files as later consoles (eg. font and wifi firmware).

What I am doing is checking the file creation timestamp for the launcher's title.tmd file. If it's saying year 2008 then unlaunch is bugging you with the unknown firmware warning message.

Not sure why you get warning that on firmware v1.4.5E. Maybe your console did originally have v1.2E or older installed? And any later system update(s) did maintain the old file creation timestamp for title.tmd. I don't if that would happen - it would depend on if the update is "overwriting" the old .tmd file, or if it's "replacing" the old .tmd file.

But... you didn't get the warning with firmware v1.4E on the same console? Weird. Or did you use an older unlaunch version back then (ie. something older than unlaunch v1.5)?
EDIT: Stupid question. You said you used v1.8 for install+uninstall (and uninstall didn't even exist before v1.5).
Hmmm, maybe the battery backed realtime clock was somehow reset back to 2008 at time when installing v1.4.5E?

---

Well, I could try to detect older firmware versions via some other method. Best would be checking the version data file (but it's difficult to extract the data from there).
Or better: Does somebody HAVE dumped old firmware versions like v1.0J, and could answer a few questions about it?
Then I could just completely remove the warning about yet unknown firmwares : )


I've used version 1.8 for install and uninstall. The thing is that i never set the date and the clock. But I've adjusted it now and I get the same error.
PS: Most likely when I updated the console the date was set to 2008.
EDIT: I downgraded the console to 1.4 and then I updated again to 1.4.5E, but this time i set the correct date. Now unlaunch works. But if I choose launcher i have no sound in the menu. This happened before too.
EDIT2: My dsi compatible R4 doesn't start from unlaunch (black screen). It isn't recognized in unlaunch (instead of the name it shows some scrambled tiles). I need to go to launcher and start it from there. My cart: wi-fi R4i v5.0 3ds www.r4i-sdhc.com


Top
 Profile  
 
PostPosted: Mon Dec 03, 2018 3:02 pm 
Offline
User avatar

Joined: Tue Jul 24, 2018 6:28 pm
Posts: 16
Ok got my DSI back. Tested 1.8 myself now (the reports about HIyaCFW Launcher not working was based on reports I was getting from others so hadn't tested that myself yet).

It's able to boot my prepatched Launcher SRL off SDMC (it just shows up in your file browser with the rest of the apps so didn't have to move it)

It's applying your patches ontop of the existing ones though (so no bootsplash/system menu music). But it otherwise appears to work! But only if I booted it from menu. BUT it seems to take a considerable amount of time. Maybe a full 30+ seconds? If I set it as the default boot option it just blackscreens (waited in excess of a minute to be sure. It never goes any further). :(

Now if there was a flag I could set in the header to tell Unlaunch to not patch it but still boot it like Launcher then this would replace the need of using a prepatched stage2 SRL. Part of the issue may be due to the existing patches baked into the SRL which may be slowing Unlaunch's loader down. Oh of coarse maybe still good idea to at least patch Launcher so that it doesn't delete it's own TMD (as I recall certain versions of Launcher did this?) in the event someone does boot a custom Launcher that doesn't have SD redirection applied to it.

Oh also I moved it to SD:\\Launcher.dsi and SD:\\Launcher.prv respectively and from the menu it was able to boot it from there too. (but again with Unlaunches patches stacked ontop of the existing patches)

As before it took 30+ seconds to boot. Almost thought it just got stuck. but it did eventually boot it.

EDIT: Tested altering the title ID of Launcher. It would load it immediately after I did this. But Launcher then just white screens. Looks like you can't mess with title ID of Launcher. It doesn't like that. It's not a modcrypt issue. I disabled modcrypt in the header and left it decrypted so I had nothing besides the header CRC to fix after I altered the TID. (that too could be slowing the loader down. It sees that it's launcher and then wastes time trying to decrypt it?)

EDIT2: Re-modcrypted it. This didn't change anything so modcrypt not causing the problem.


Top
 Profile  
 
PostPosted: Sun Dec 09, 2018 2:04 am 
Offline

Joined: Fri Feb 24, 2012 12:09 pm
Posts: 729
Apache Thunder wrote:
EDIT: Tested altering the title ID of Launcher. It would load it immediately after I did this. But Launcher then just white screens. Looks like you can't mess with title ID of Launcher. It doesn't like that.

Then breakpoint on "[2FFE230]?" or whatever you had changed, and patch the launcher code that uses that address.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 125 posts ]  Go to page Previous  1 ... 5, 6, 7, 8, 9

All times are UTC - 7 hours


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group