Hacking Quick question on recovering for the bricker

  • Thread starter Thread starter Trel
  • Start date Start date
  • Views Views 3,186
  • Replies Replies 15

Trel

Well-Known Member
Newcomer
Joined
Sep 21, 2007
Messages
93
Reaction score
0
Trophies
1
XP
113
Country
United States
In this scenario, I already have flashme installed.
I now get hit with the bricker.

Do I need to short again to recover?
 
I don't think so. You need to short it to write the recovery code. The bricker is not able to write it.

Dont worry about the bricker. I have activly looked for the bricker and I CANT find it.
 
From my understanding, you'd use the failsafe recovery code to boot your homebrew device, where you would run FlashMe.nds again to reinstall it. No shorting necessary.
 
In this scenario, I already have flashme installed.
I now get hit with the bricker.

Do I need to short again to recover?


No.

If the percentage stops, then yes. Otherwise the progress percentage will fill up itself.


Wrong. The percentage won't stop as the protected area of the firmware hasn't been overwritten.

QUOTE(bfoos @ Dec 9 2007, 09:21 AM)I can't find it either. I wanted to do some recovery testing.

I wouldn't mess around with it. There's parts of the firmware that aren't meant to be erased
 
I just downloaded both the brickers. (Thanks for the link) I havent run any yet, but I have found that they are a harmless way to test Virus Scan programs.
 
I've run both of them on my flashme v8a DS Lite. They didn't erase anything other than the system settings. No brick, no need to recover.
 
Right, the DS Lites protect everything but the user settings underneath the SL-1 contact. Guess I forgot to mention that earlier.
 
Right, the DS Lites protect everything but the user settings underneath the SL-1 contact. Guess I forgot to mention that earlier.
Well that's no fun. I had to pull my battery while flashing to get a right proper brick. Recovery worked well. I had to encrypt flashme_noauto with r4enc and rename it to _DS_MENU.DAT in order to recover though. The R4 doesn't like to run .nds files when booted with the fail safe.
 
Right, the DS Lites protect everything but the user settings underneath the SL-1 contact. Guess I forgot to mention that earlier.

Well that's no fun. I had to pull my battery while flashing to get a right proper brick. Recovery worked well. I had to encrypt flashme_noauto with r4enc and rename it to _DS_MENU.DAT in order to recover though. The R4 doesn't like to run .nds files when booted with the fail safe.

So you held select during the boot up and the new R4 'firmware' booted up? I didn't know that you could do that, I always assumed that you could only recover with a slot-2. Guess I was wrong.

Also - to anyone who flashed their lite with v8a_noauto, when I boot up my DS there is a fraction of a second where the screen is static. (it's garbled, seemingly-random pixels). Anyone else have this problem?
 
Well I just learned that you most likely could use R4enc to make a temporary firmware on the R4 for flashing initially.
happy.gif
 

Site & Scene News

Popular threads in this forum