RGH Freeze at Xbox Logo, Xellous Reloaded works fine

G

GT Mocha

Junior Member
Jan 8, 2012
19
0
Thanks to Ir0nman for fixing my messed up nand!!!

So, I had my RGH working perfectly earlier I had XexMenu 1.1 installed along with FSD. I then decided to install DashLaunch, I then recieved an error stating DashLaunch was only compatible with Kernel 14699 I made the mistake of thinking I was under that Kernel instead of above it. Not realizing this I installed Nand Flasher 360, dumped my nand(it was called orig_nand.bin) when it dumped. Then I ftp'd that over to my pc and I followed this guide to update: http://digiex.net/guides-reviews/co...-xbox-360-kernel-dashboard-14699-xebuild.html

At the end I ended up with a "udpflash.bin" file and was told to write that back using Nand Flasher 360, so I did. I then powered off my console, unplugged everything, power, av, and other periferals etc... Left it off for a good 5 minutes, and turned it back on. Console glitched very quickly as usually within 30 seconds. And on the boot animation it would freeze. Like say the boot animation were to load, at the very end of it right as it is about to load the Dashboard that is when it freezes. So after I then decided to see of I could boot xellous reloaded and I could. So I then tried to flash back my previous nand that I created (nandflash.bin) from XeBuild when I first RGH'd. And I got the same thing, Xell would load but anything else would freeze. I really don't know what to do at this point, I loaded my nandflash.bin into 360 Flash tool and noticed there was one bad block, I tried remapping it with Jtag tool in which it seemed to of worked as when I opened it back up in 360 Flash tool no bad blocks were found when I "um_mapped" it. I tried rebuilding nandflash's and writing them back but nothing has worked.

Here are some images of xell reloaded and my rgh freezes.



Xell: http://gyazo.com/6cf81f0051a87256d5f30b4f5fbf5f05

Someone, please help me :(
 
Last edited:
BL4K3Y

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
Take your original (un-touched) NAND dump and create a new, modified image using XeBuild or J-Runner.
(Don't worry about bad blocks, XeBuild will deal with them automatically).

Images of your wiring and wire positioning will be helpful in this instance.
 
Last edited:
G

GT Mocha

Junior Member
Jan 8, 2012
19
0
BL4K3Y said:
Take your original (un-touched) NAND dump and create a new, modified image using XeBuild or J-Runner.
(Don't worry about bad blocks, XeBuild will deal with them automatically).

Images of your wiring and wire positioning will be helpful in this instance.
Click to expand...
I did as you instructed and opened my original nand dump in J-Runner and created a glitch boot. I checked my original nand in 360 Flash tool for bad blocks and this is what I recieved:




Here is the new modified glitch boot/nand flash:


And when I tried flashing with xell(rawflash4)

This is what I received:
Bad block at 1A9
Bad block at 1AA
Bad block at 3FF

Should I upload my original nand dump and modified nand?
 
G

GT Mocha

Junior Member
Jan 8, 2012
19
0
BL4K3Y said:
Try writing the modified image back with NandPro, some people have reported issues when writing back with RawFlash.
Click to expand...
Thanks ill give it a shot in the morning. It's almost 3 AM and I'm not in the mood to take any chances here :p

Really though man, I appreciate your help. And quick responses. Not gonna lie, I'm glad I went with TX products as the support sh*ts on everything else :)

Night.
 
I

Ir0nman

Full Member
Mar 13, 2011
59
0
Do you have a dump of the current nand on the system? That way it will show all the current bad blocks. Using your original will not help you as your original is showing 1 bad block and raw flash is telling you 3 (if you are reading it correctly). Dump your current nand and run that thru J-Runner which will tell you how many bad blocks there are. Does it say 3?
 
wienio

wienio

Full Member
Feb 21, 2010
42
0
Nowy Sącz
Nand Clear by the programmer (nand-x) and write nand again.
J-runer create a new dash for example 14719
nandpro usb: -e512
nandpro usb: -w512 nand.bin
( Your file name nand.bin)
 
Last edited:
G

GT Mocha

Junior Member
Jan 8, 2012
19
0
Well I think I need to send my NandX back to Xconsoles too, because I get "Looking for usb, cannot continue" and it isn't detected even though I have the drivers installed. I also tried on 2 other PC's and 5 other boxes and got the same error, I looked over my soldering too many times to count, and there were absolutely no shorts at all. So now I'm really in a mess, I no longer have a nand flasher and the only thing I can use to read/write is xell reloaded.

What should I try next?
 
Last edited:
G

GT Mocha

Junior Member
Jan 8, 2012
19
0
Update:
This was the nand I had before I flashed with XeLL:


This is the nand I had after fixing it with XNandHealer GUI, but before flashing.:


This is the nand that I read after flashing with Xell/rawflash:


So since I currently have no other way to read/write except for Xell what should I do?
 
Last edited:
G

GT Mocha

Junior Member
Jan 8, 2012
19
0
Martin C said:
Do you still have your original, untouched NAND?

Build a new image in J-Runner and post the log. Do NOT mess with any blocks.
Click to expand...
Yes I do, however I tried doing that 4 times already today and it's not worked. It does the same things, freeze at xbox logo/boot anim. But when I can boot xell fine.

Also, whenever I flash a new image I always get the same three bad blocks:
Bad block at 1A9
Bad block at 1AA
Bad block at 3FF


which is odd because if I try re-mapping blocks before I flashed I only had 1 bad block. at 1AA location: 3FF



I'd just like to add that all three of my orig nand dumps were identical and all had that bad block. So it wasn't really a big deal to me.

Also LDV's are correct.
 
Last edited:
BL4K3Y

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
Route your wires away from the coils and DON'T remap any bad blocks manually, you were already told that XeBuild will deal with those.
 
Last edited:
G

GT Mocha

Junior Member
Jan 8, 2012
19
0
Code: 
===================================================
Sunday, March 18, 2012 6:10:11 PM



No Updates Found


Checking Files
Finished Checking Files
Initializing Nand..
Comparing...
Nands are the same
Initializing Nand..
CpuKey is Correct
Key already Exists
Load Files Initiliazation Finished
Initializing Nand..
CpuKey is Correct
Key already Exists
Started Creation of the xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.01.421
---------------------------------------------------------------
building glitch image
---------------------------------------------------------------
C:\Users\Brandon\Desktop\For martin\077649283207\nandflash.bin image built, info:
---------------------------------------------------------------
Console  : Falcon
NAND size: 16MiB
Build    : Glitch
Xell     : power on console with console eject button
CPU Key  : C38FDE063A27E6A29EE308CD70DXXXX
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key  : ADD09D5B68868B8AE3CA8C4F8965XXXX
CF LDV   : 7
KV type  : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

press <enter> to quit...

Saved to C:\Users\Brandon\Desktop\For martin\077649283207
Image is Ready
INFO: You can write the resulting image to the nand using this app's Write Nand button
However if you wish, you may copy the "Nandflash.bin" and "Xenon.elf" to a USB stick.
Place that in console and boot the console using the eject button.
(this will use rawflash and overcome any bad blocks you may have on your nand)
 
Last edited:
G

GT Mocha

Junior Member
Jan 8, 2012
19
0
BL4K3Y said:
Did you try writing the image back with NandPro as opposed to RawFlash like I suggested in one of my previous posts?
Click to expand...
I can't:
GT Mocha said:
Well I think I need to send my NandX back to Xconsoles too, because I get "Looking for usb, cannot continue" and it isn't detected even though I have the drivers installed. I also tried on 2 other PC's and 5 other boxes and got the same error, I looked over my soldering too many times to count, and there were absolutely no shorts at all. So now I'm really in a mess, I no longer have a nand flasher and the only thing I can use to read/write is xell reloaded.

What should I try next?
Click to expand...
 
G

GT Mocha

Junior Member
Jan 8, 2012
19
0
BL4K3Y said:
I strongly suggest you look over your soldering again, if your NAND-X was faulty then it wouldn't even show up in Device Manager.

Read this for more information.
Click to expand...
It doesn't... I stated that it can't be detected. I guess I wasn't specific enough, I should of stated that it wont be detected in Device Manager.
 
You must log in or register to reply here.