Homebrew Please RECONSIDER it good to install UNLAUNCH !!!

[Alexander1970]

Hello.

I have no Idea,what causes it ("Bad" NAND Chip,Unlaunch de-Installation......)
I never modified the NAND or SD NAND on this Device.It was my 3rd DSi and not really in Operation except updating TWiLight Menu.


I "lost" my Black/Red assembled from 2-3 DSi today by uninstalling Unlaunch 2.0 (I made with full intent and full knowledge that it can happen)

Result - BLACK Screen / Blue LED.


Uninstalling UNLAUNCH is a RISK !!

@Robz8
@maorninja
@Zense
and all the other DSi Hacking/Unlauch Profis (please be not angry,I do not know/remember all of you,my Freinds).I can not recommend an uninstall with Version 2.0/1.8 *tested*
And NO I will not try it with my other Devices with v1.9,1.8 and so on.


Maybe @KleinesSinchen make some "Tests" too acutal....

Thank you and please READ IT before you do it.
https://dsi.cfw.guide/

 

[KleinesSinchen]

Why?? Seriously why?

If somebody tells you: "Fire is hot!" will you put your hands into the fire to test if it's true? We discussed the problem yesterday in PM.
That was completely unnecessary! Sorry, I have too:

Now… please get out the soldering iron and do a hardmod (You have a backup. Tell me you have a backup!). I'm very interested in the result concerning the NAND chip from hardware perspective. My question is:

• NAND damaged?

– or–

• Simply bad data or a mistake by unlaunch (un)installer.

 

[Alexander1970]

Why?? Seriously why?

If somebody tells you: "Fire is hot!" will you put your hands into the fire to test if it's true? We discussed the problem yesterday in PM.
That was completely unnecessary! Sorry, I have too:

Now… please get out the soldering iron and do a hardmod (You have a backup. Tell me you have a backup!). I'm very interested in the result concerning the NAND chip from hardware perspective. My question is:

• NAND damaged?

– or–

• Simply bad data or a mistake by unlaunch (un)installer.

Hey,keep cool,Sinchen.

Why did you think do I such Things.
I need such "Challenge" to do.But I need peace and calm for it.

Not this:




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

Now… please get out the soldering iron and do a hardmod (You have a backup. Tell me you have a backup!).

Bien sûr, ma dame.
(Of course, my Lady.)



Soldering Iron is there,Tutorial is ...there ok SD Card Reader is not there....
No Problem,I will get one.

 

[IC_]

Maybe if unlaunch wasn't closed source proprietary garbage we wouldn't have issues like this

 

[KleinesSinchen]

Hey,keep cool,Sinchen.

Why did you think do I such Things.
I need such "Challenge" to do.But I need peace and calm for it.

Bien sûr, ma dame.
(Of course, my Lady.)

I am calm and quiet. And I'm not a bit angry.

← Sinchen​

Okay. It was unnecessary but… Alas! Now make the best out of the situation. There have been a few bricked DSi due to unlaunch uninstall, one due to borked unlaunch upgrade and (can't find it, hope I remember that correctly) one initial installation that failed right away. Until now I know of no case where somebody reported back if hardmod and NAND restore revived a DSi which has been bricked this way.

Maybe if unlaunch wasn't closed source proprietary garbage we wouldn't have issues like this

Open source could help other devs to look into the problem.
Given that unlaunch is the only boot time exploit… I still recommend installing it and NEVER uninstalling afterwards.

@ManuEcheveste
Here we have yet another case.

 

[Alexander1970]

I am calm and quiet. And I'm not a bit angry.

← Sinchen​

Honestly,I do not believe the Hardmod will work.

and NoCash seems a little "uninterested" to Answer the Situation (@Robz8 and a User asked him but got no Answer) so I think it HAS to do with V2.0:

http://forums.nesdev.com/viewtopic.php?f=23&t=17581&start=195

Also User saturnu tested some Things about WiFiBoot and Installation Issues and it also seems "newer Versions" have Issues...

saturnu
Posts: 23
Joined: Wed Aug 05, 2015 2:22 pm
Re: DSi unlaunch (bootcode exploit)

Post by saturnu » Thu Mar 26, 2020 10:22 am

oh man, i was so happy that it's working and now i have to brick it again?

ok i did it for science anway. it stops working with unlaunch v1.5.
is it interesting for you to look into the nand with the broken v1.5 installation? i dumped it - just in case.

tested - not working
v2.0
v1.9
v1.7
v1.5

working
v1.4
v1.3

 

[Alexander1970]

Update:
(I know @KleinesSinchen is getting mad now....sorry,but I want to know it now.)

The Indications (V2.0 has issues) are getting a little clearer for me.
Successfully uninstalled V1.8 on my modded DSi XL (modded with Memory Pit Exploit,same as the "deceased" DSi from my first Post).

And with this Device I have done a lot.Also installed DSiware but only to the SD NAND.

 

[KleinesSinchen]

Honestly,I do not believe the Hardmod will work.

Why not? According to the unlaunch thread on forums.nesdev.com restoring a stock NAND image did work for saturnu (and this was the case of non working installation). No wonder I did not find it on GBAtemp! I simply didn't remember where I read this before.

Nocash did not seem to be uninterested in my opinion. The problem is: If nocash can't reproduce the error on his console(s) he will have a hard time debugging the issue.

Maybe somebody should send him an affected console.

Update:
(I know @KleinesSinchen is getting mad now....sorry,but I want to know it now.)

The Indications (V2.0 has issues) are getting a little clearer for me.
Successfully uninstalled V1.8 on my modded DSi XL (modded with Memory Pit Exploit,same as the "deceased" DSi from my first Post).

And with this Device I have done a lot.Also installed DSiware but only to the SD NAND.

 

[Alexander1970]

Maybe I will try to get some cheap/optical damaged DSi´s and try.
It could be also a Combination from "different" DSi Hardware (maybe "cheap produced Chips" ?) and Unlaunch.

So personallly,I change my Mind/Opinion into:

Uninstalling UNLAUNCH in generell is a RISK !
There is a 50 Percent Brick Chance.

 

[KleinesSinchen]

Maybe I will try to get some cheap/optical damaged DSi´s and try.
It could be also a Combination from "different" DSi Hardware (maybe "cheap produced Chips" ?) and Unlaunch.

So personallly,I change my Mind/Opinion into:

Uninstalling UNLAUNCH in generell is a RISK !
There is a 50 Percent Brick Chance.

I don't think the percentage is that high. We would have heard more cries for help. Not all people who try something out (without reading and thinking) and uninstall afterwards make a GBAtemp account. If everything goes well we never get to hear anything. Somebody searches the web "uninstall unlaunch"… and they will inevitable find some information how to do it and "will render your console mostly useless" is a joke.

But those who end up with a brick are more likely to sign up here (or somewhere else) and ask for help.

High percentage or not: There seems to be a risk involved, particularly with uninstallation. So my advise for the future will not change:

Don't uninstall CFW. It has no benefits and is potentially dangerous.

 

[Alexander1970]

Do not give me a like,@KleinesSinchen ....

I don't think the percentage is that high. We would have heard more cries for help. Not all people who try something out (without reading and thinking) and uninstall afterwards make a GBAtemp account. If everything goes well we never get to hear anything. Somebody searches the web "uninstall unlaunch"… and they will inevitable find some information how to do it and "will render your console mostly useless" is a joke.

But those who end up with a brick are more likely to sign up here (or somewhere else) and ask for help.

High percentage or not: There seems to be a risk involved, particularly with uninstallation. So my advise for the future will not change:

Don't uninstall CFW. It has no benefits and is potentially dangerous.

..so then,the 50 Percent Chance is now raised:

Second DSi is bricked.
But this Time with Version 1.8

(I now you hate me.......)


I can do a HARDMOD,I have NAND Backups....all is ok.

 

[Alexander1970]

Blue DSi original:



Black/Red DSi (assembled from 2-3 broken DSis)

 

[KleinesSinchen]

Blue DSi original:

View attachment 214182

Black/Red DSi (assembled from 2-3 broken DSis)

View attachment 214183

Two different Samsung NAND chips.

I very much doubt at this point that this is a spontaneous hardware failure or "poor NAND quality".

All jokes aside: It is a good thing you did some testing. But honestly: Stop it now. There is no need to scrap all your consoles. This needs systematic "investigation" and not blindly killing DSi's.

If you can successfully restore an image via hardmod, this is the time to do systematic tests. Different unlaunch versions, upgrade, downgrade, uninstallation. Booting the installer from unlaunch File Menu, from TWL++, from Memory Pit… If the NAND dies of write cycles from repeated restore: Okay. Sacrificing one chip (and therefore motherboard) is not that bad.

 

[Alexander1970]

If the NAND dies of write cycles from repeated restore: Okay. Sacrificing one chip (and therefore motherboard) is not that bad.

I will try to remember:

Blue DSi:
3-4 Write Cycles (from UNLAUNCH)
1 System Update to 1.4.5E
Flipnote was pre-installed and was used for Modding.
Nothing additional downloaded

Of Course I have no Idea how many Pictures and Soundrecordings the Pre-Owner did.

Black/Red DSi:
3-4 Write Cycles (from UNLAUNCH)
1 System Update to 1.4.5E
Nothing additional downloaded
Memory Pit Exploit used.

also: Of Course I have no Idea how many Pictures and Soundrecordings the Pre-Owner did.

I think also System Settings Changes will count.

My "Feeling" is it has nothing to do with "too much write Cycles"...
(Why is the WiFi not initialized,on both Devices only the BLUE LED is on ?)

On the DSi XL (where the Uninstallation worked) I have installed v1.8 over v2.0
Then Uninstalled Unlaunch
Installed Unlaunch again.
So 3 Write Cycles in less than a Minute.

 

[RocketRobz]

I very much doubt at this point that this is a spontaneous hardware failure or "poor NAND quality".

All jokes aside: It is a good thing you did some testing. But honestly: Stop it now. There is no need to scrap all your consoles. This needs systematic "investigation" and not blindly killing DSi's.

If you can successfully restore an image via hardmod, this is the time to do systematic tests. Different unlaunch versions, upgrade, downgrade, uninstallation. Booting the installer from unlaunch File Menu, from TWL++, from Memory Pit… If the NAND dies of write cycles from repeated restore: Okay. Sacrificing one chip (and therefore motherboard) is not that bad.

^this

As soon as my Yellow DSi LL (imported from Japan, and ordered last month) arrives, and as someone with no hardmodding experience, I won't be installing Unlaunch on it, after hearing those reports.
I've already implemented fixes into nds-bootstrap so that it works fine without Unlaunch.

btw, is there anything I could do to improve dsi.cfw.guide, so that bricks are reduced?
There's already messages such as:

If you have not yet done so, please made a NAND backup. Unlaunch modifies the NAND which could result in a brick if done improperly.

and

This may result in a brick if you have installed any non-legit DSiWare to your System NAND (not the SDNAND redirection provided by hiyaCFW), or have otherwise tampered with system files.

 

[Alexander1970]

As soon as my Yellow DSi LL (imported from Japan, and ordered last month) arrives, and as someone with no hardmodding experience, I won't be installing Unlaunch on it, after hearing those reports.

Thank you.that encourages.

^this
btw, is there anything I could do to improve dsi.cfw.guide, so that bricks are reduced?
There's already messages such as:

and

Since it happens with v1.8 and v2.0 it is really hard to say which Version can be "safely" used....
To tell the Users "Please open first your DSi and check the Samsung Chip Version.." is also not really a good Idea.

The only really Advise:

Please consider the Unlaunch Installation very good before you do it.You maybe never get rid of it.

 

[Deleted User]

Hello.

I have no Idea,what causes it ("Bad" NAND Chip,Unlaunch de-Installation......)
I never modified the NAND or SD NAND on this Device.It was my 3rd DSi and not really in Operation except updating TWiLight Menu.


I "lost" my Black/Red assembled from 2-3 DSi today by uninstalling Unlaunch 2.0 (I made with full intent and full knowledge that it can happen)

Result - BLACK Screen / Blue LED.


Uninstalling UNLAUNCH is a RISK !!

@Robz8
@maorninja
@Zense
and all the other DSi Hacking/Unlauch Profis (please be not angry,I do not know/remember all of you,my Freinds).I can not recommend an uninstall with Version 2.0/1.8 *tested*
And NO I will not try it with my other Devices with v1.9,1.8 and so on.


Maybe @KleinesSinchen make some "Tests" too acutal....

Thank you and please READ IT before you do it.
https://dsi.cfw.guide/

I have a pink DSi as having the same problem sortoff but I do have a dsi NAND EUR+USA dsi NAND

 

[N7Kopper]

Maybe if unlaunch wasn't closed source proprietary garbage we wouldn't have issues like this

It's harder to inject a political statement into open source code, isn't it?

 

[ManuEcheveste]

I still haven't made the hardmod to my DSi, cause I don't have some of the things that I need and I can't buy them quickly enough because of the virus thing, but when I made it, I'll make a post explaining all the things that happened to me, and the results of the hardmod, also here's a picture of my NAND's chip xD

 

[Alexander1970]

I still haven't made the hardmod to my DSi, cause I don't have some of the things that I need and I can't buy them quickly enough because of the virus thing, but when I made it, I'll make a post explaining all the things that happened to me, and the results of the hardmod, also here's a picture of my NAND's chip xD

Thank you.

I am (also) waiting for the Card Reader.
Please if you be so kind and post your Progress here ? It would really help other Users,for sure.
I would really appreciate your Work and your Help.

Thank you.