Jump to content
RealModScene
Lévai �dám

xbox 360 slim e79(dash update)

Recommended Posts

Hello everyone
I upgraded to the Dashboard, an error occurred.
I tried to write original nand was, Rawflash v4 were posted, but it does not work.
All he writes that no signal input.
I apologize for my bad english

please help me

console type: Slim Cronona V2 4GB

 

 

  • Like 1

Share this post


Link to post
Share on other sites

Hello everyone

I upgraded to the Dashboard, an error occurred.

I tried to write original nand was, Rawflash v4 were posted, but it does not work.

All he writes that no signal input.

I apologize for my bad english

please help me

console type: Slim Cronona V2 4GB

Can you make a mistake during the update Did you try naming Rawflash to updflash To restore the file 

Follow update correct way 

http://forum.homebrew-connection.org/index.php?topic=144.0

xell/rawflash dont work on 4gb consoles.. you have to use swizzy's simple nand flasher for 4gb consoles.. but.. since it doesn't boot anymore, he has to use a 4gb r/w kit to re-do the nand..

Share this post


Link to post
Share on other sites

xell/rawflash dont work on 4gb consoles.. you have to use swizzy's simple nand flasher for 4gb consoles.. but.. since it doesn't boot anymore, he has to use a 4gb r/w kit to re-do the nand..

It can be a mistake in the update incorrectly I followed the right way and every good thing I have a xbox 360 4GB 

Share this post


Link to post
Share on other sites

E79 indicates an error within xam.xex, on NAND consoles (any console except for 4GB Corona/Winchester) this usually indicates a unhandled badblock (or one that was handled incorrectly)

I've thus far never seen E79 on a MMC console, but it's a indicator that the write went wrong, most likely caused by a bad USB memory or similar (could also be something on your computer messing with the data, such as bad antivirus or even a piece of malware)

Share this post


Link to post
Share on other sites

likely caused by a bad memory stick error
"Dumping Your NAND
Using Xell (works on all consoles as of Xella-v0.992 Reloaded) "
I read this:
flashdmp.bin
keyvault_raw.bin
fuses (CPU key, key DVD)
rawflash 4gb model does not work
swizzy's simple nand flasher I can not start from Xell menu
Xell: looking for files on local media and TFTP ...

  • Like 1

Share this post


Link to post
Share on other sites

likely caused by a bad memory stick error

"Dumping Your NAND

Using Xell (works on all consoles as of Xella-v0.992 Reloaded) "

I read this:

flashdmp.bin

keyvault_raw.bin

fuses (CPU key, key DVD)

rawflash 4gb model does not work

swizzy's simple nand flasher I can not start from Xell menu

Xell: looking for files on local media and TFTP ...

You cant flash your nand via xell.. if you console no longer boots, you need the 4gb r/w kit installed.. period.. swizzy's app can flash once the console is running normally.. you need to take notice the 4gb corona have extra steps needed to be handled properly
  • Like 2

Share this post


Link to post
Share on other sites

Hello Guys again

 J-Runner error code : 

J-Runner v0.3 Beta (8) Started
 
 
It's advised to run in administrator mode on Windows 8
Connection Error
Checking Files
Connection Error
 
Failed to get DiskGeometry.
 
TX Corona 4GB Nand reader qsb kit

 

Share this post


Link to post
Share on other sites

does not work

Are you sure your console is a 4GB MMC Corona? if not, you installed the wrong hardware to read/write it

Seeing as you're getting E79 it's highly unlikely to be a MMC Corona (they shouldn't be able to get that as they don't have badblocks)

Another thing to know is that the kit needs a MMC compatible SD Card Reader... if you don't have that, then it won't work anyways...

Share this post


Link to post
Share on other sites

I can see that by the last image, the first 2 are useless...

Did you provide power to your console? (connect the power cable, don't power it on)

Share this post


Link to post
Share on other sites

yes see (PhysicalDrive2)

That's just the cardreader...

Does windows ask you to format when you connect the kit? If not - the reader probably isn't mmc compatible or there is a connection problem somewhere...

Sent from my SM-G903F

Share this post


Link to post
Share on other sites

I could read

checksum.md5

image_0000000.ecc

nanddump1.bin (3.5GB)

nanddump2.bin(3.5GB)

nanddump3.bin(3.5GB)

nanddump4.bin(3.5GB)

nanddump1.bin(48,0MB)

What more should I do?

What's that you're saying? I don't understand...

Sent from my SM-G903F

Share this post


Link to post
Share on other sites

Next step now would be to rebuild the nand and flash it back i guess?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...