Hacking Help with Blue screen + BOOTROM 8046 error + R4i Deluxe/3DSlink

[willdunz]

Actually there is some pictures, and this user is so sure that he didn't use the modified launcher.
But, he left his 3DS in sleep mode for couple hours before it bricks.
http://bbs.tgbus.com/thread-5360192-1-1.html

Another instance, a GW user said that he encountered blue screen once during playing a game, but the blue screen is not permanent, it just gone after reboot.

the link you provided is dead.
Anyway people have been playing with 2.0b2+emu7.1 for a while now. I find it strange these bluescreen reports all came up in a few days. You would expect people reporting bluescreen a long time ago, espeically during the period when people were experimenting to see if they can emu 7.1 or not.
This whole thing is confusing

 

[Commoner]

The simple fact that r4i is rereleasing their 2.0 firmware labeled as 3.3b should be a total red flag that they are willing to lie and hide things from their customers for the sake of continued sales.

If they seriously had their customer's best interest in mind instead of being more concerned about lining their own pockets, they would have admitted to the bricking issue, apologized profusely to those affected and advised their customers to revert back to firmware 2.0 for the time being.

Instead, they choose to hide the issue and pretend they are making progress by releasing an old version of their firmware and pretending they are introducing something new.

This is not only unethical but also significantly increases the risk of their customers being affected by the bricking issue by downplaying the problem. A lot of people who are simply unaware of the issue might see the new beta update and put off "upgrading" because they are completely oblivious of the fact that staying on their current firmware could cause them to brick their 3ds.

Honestly, at this point, I would trust the clone manufactures about as far as I could throw them. And since there has been some evidence that the people behind the MT-Card are the same people who are behind the R4i Deluxe Gold, I wouldn't trust that cart very much either.

 

[gamefan5]

I'm not saying it's impossible that there is a bug in gateway, but what I will say is that how come in the nearly 2 weeks between gateway releasing and the clones releasing their hacked version of the gateway firmware, why was there no reports of gateway bricking anything.....as soon as people come out saying the clones are bricking after only one or 2 days of days of the clone launcher getting released, suddenly some people pop up blaming gateway as well, it all seems way too convenient for the clones in my opinion.

Btw in my efforts to try find the truth I have actually tried pretty much everything the people are claiming bricked on a gateway......been to data management, left it in sleep mode for hours, left it to go flat in gateway mode....and nothing

People said that the bricks have started the weekend tho. I wonder what would be the cause, since there's so many different info on it. For now, I have no problem on my second 3DS, it works nicely. No SD problem as well since I don't use the kingston brand. People say that GW has placed a checksum that makes clones brick the 3DS but IDk about that.

 

[temp1312]

the link you provided is dead.
Anyway people have been playing with 2.0b2+emu7.1 for a while now. I find it strange these bluescreen reports all came up in a few days. You would expect people reporting bluescreen a long time ago, espeically during the period when people were experimenting to see if they can emu 7.1 or not.
This whole thing is confusing

Yeah, it was alive 5 min ago.
You know, in that forum, your post will be "checked" by the admins even after editing, so it will be alive few min later.

 

[Coto]

weird.. gw has no issues at all. just the other teams.

AP caussing issues? Ah the wonders of custom execution code + business practices..

 

[gamesquest1]

I think people assumed it was like the DS flash card scene where if the card is similar they can get away with just hacking up a firmware until it works with a clone......with the 3DS it's the software side of things that matters, no matter how close they copied the gateway specs, if they can't use a 1:1 copy of the gateway firmware your putting your 3DS's life in the hands of people who can't even code for the 3ds, and just tinkered away at the FW until it showed up on the menu, probably not knowing what it was they where editing in the process......it's quite simply asking for trouble

 

[hiron]

The simple fact that r4i is rereleasing their 2.0 firmware labeled as 3.3b should be a total red flag that they are willing to lie and hide things from their customers for the sake of continued sales.

Well according to this thread, gw is lying/hiding as well just for more sales. Dont know how much of it is true but Im always skeptical when a company announce something. You never know if its true or a lie just for more sales.

http://gbatemp.net/threads/warning-gateway-team-bricks-card-on-purpose.360568/

 

[C RONALDO]

Hello all,

I got the r4i gold deluxe 2 weeks ago and I just bricked my 3dsxl
I've been searching for a fix but it seems that there's none, so I'm about to buy a ****ing new console!
I want to know are games like ( mario tennis - mario party - zelda link between worlds - bravely default....) working with that 3.3b firmware?

EDIT/ I have the backed up NAND if that could help me to fix it ?!

 

[gamefan5]

Hello all,

I got the r4i gold deluxe 2 weeks ago and I just bricked my 3dsxl
I've been searching for a fix but it seems that there's none, so I'm about to buy a ****ing new console!
I want to know are games like ( mario tennis - mario party - zelda link between worlds - bravely default....) working with that 3.3b firmware?

EDIT/ I have the backed up NAND if that could help me to fix it ?!

First, my condolescence for your 3DSXL. Consider it dead in the literal sense.
You may buy a console, but if u still want to play roms. I suggest u buy the gateway as using clones will result in bricks.

 

[randomxiii]

Buy a new console and burn that r4i card; it's what causing the brick. If you still want to pirate games then yeah, GW is your only choice.

Hello all,

I got the r4i gold deluxe 2 weeks ago and I just bricked my 3dsxl
I've been searching for a fix but it seems that there's none, so I'm about to buy a ****ing new console!
I want to know are games like ( mario tennis - mario party - zelda link between worlds - bravely default....) working with that 3.3b firmware?

EDIT/ I have the backed up NAND if that could help me to fix it ?!

 

[condiczek]

weird.. gw has no issues at all. just the other teams.

AP caussing issues? Ah the wonders of custom execution code + business practices..

I know what causes that!


Its in "encrypted message" in "THEIR" (r4i/3dslink) firmware changelog! lol


And now one sentence for real, and then a little bit of humor

REAL: its "THEIR" firmware fault! clone users downloaded THEIR firmware
from THEIR sites! (tip: focus on what "their" word really means )

FUN: their (both clones almost the same) last changelog is:

Change Log:
1. Fixed the saving issue caused by V3.2
2. Fixed the breaking card issue caused by V3.2
3. Increase the stability

Attention: Multi-rom will be supported in Ver4.0

And what I found after decrypting is:

Change Log:
1. Fixed the saving issue caused by V3.2
2. Fixed the bricking card issue caused by V3.2
3. Increase the 'stability' lol

Attention: Multi-bricking will be supported in Ver4.0

i think i will stick with my org gateway
good night all

 

[C RONALDO]

First, my condolescence for your 3DSXL. Consider it dead in the literal sense.
You may buy a console, but if u still want to play roms. I suggest u buy the gateway as using clones will result in bricks.

I will get the mt card soon, but at least i want to play the playable games on that r4i!


guys, is it 100% safe to play on 3.3b firmware ?

 

[gamefan5]

I will get the mt card soon, but at least i want to play the playable games on that r4i!


guys, is it 100% safe to play on 3.3b firmware ?

Absolutely not. Modified launchers are the cause of this problem.

 

[tofast4u]

Absolutely not. Modified launchers are the cause of this problem.

Stop spreading all this false information you Gateway fanboy. Yes it is safe, only the launchers based on 2.0b aren't safe

 

[juins]

Stop spreading all this false information you Gateway fanboy. Yes it is safe, only the launchers based on 2.0b aren't safe

i dont understand something. Do u risk bricking your 3ds without using emunand? or is it only if u use emunand? Because im on 3.2 and not bricked yet (no emunand)

So... 3.1, 3.2 and 3.3 are to be avoided?

 

[gamefan5]

Stop spreading all this false information you Gateway fanboy. Yes it is safe, only the launchers based on 2.0b aren't safe

LOL, srsly?
3.3b is based on GW 2.02b firmware. The fact that it's a modified version of the firmware IS the fact that it causes the bricking.

From the front page that you didn't apparently read:
As of right now, users who wish to proceed onward are urged to do so with caution, taking note about not mixing files from different flash cart teams, as the Gateway team has noted that the console will not brick when using only pure Gateway software. As a routine, users should check their launcher.dat md5 hash value frequently to insure proper values are given, as a slight corruption in this value may render a bricked console (optional step). The issue has since become more isolated and down to the b2 firmware, so if the user should become concerned a recommendation is to simply not use the b2 firmware or the 3.1-3.2 (that includes 3.3 as well) firmwares for the R4i/3DSLink.

 

[tHciNc]

I think the "GW Users" that where bricked, where "GW Users", they where just clone users/affiliates trying to taint the waters so it doesnt just look like they arent the only failures

 

[tofast4u]

LOL, srsly?
3.3b is based on GW 2.02b firmware. The fact that it's a modified version of the firmware IS the fact that it causes the bricking.

From the front page that you didn't apparently read:
As of right now, users who wish to proceed onward are urged to do so with caution, taking note about not mixing files from different flash cart teams, as the Gateway team has noted that the console will not brick when using only pure Gateway software. As a routine, users should check their launcher.dat md5 hash value frequently to insure proper values are given, as a slight corruption in this value may render a bricked console (optional step). The issue has since become more isolated and down to the b2 firmware, so if the user should become concerned a recommendation is to simply not use the b2 firmware or the 3.1-3.2 (that includes 3.3 as well) firmwares for the R4i/3DSLink.

Maybe you should brush up on your research. 3.3B is a repack of the original 2.0 firmware on the 3DSLink/R4i, it doesn't have emunand.

 

[tofast4u]

i dont understand something. Do u risk bricking your 3ds without using emunand? or is it only if u use emunand? Because im on 3.2 and not bricked yet (no emunand)

So... 3.1, 3.2 and 3.3 are to be avoided?

No 3.2 is not safe, even if you don't use emunand. The reason why you didn't get bricked yet is because you are lucky. Change your launcher ASAP.

 

[gamefan5]

Maybe you should brush up on your research. 3.3B is a repack of the original 2.0 firmware on the 3DSLink/R4i, it doesn't have emunand.

*sigh, and maybe u should do more research before spouting things u don't even know. -_-'
It's not even caused by Emunand but by a malicious code founded in modified firmware.