FALCON FLashed NAND, but stuck in boot

devisius · Sep 19, 2015

I flashed my NAND and all seemed to have worked, but now it seems to reset the boot cycle (no display)
Light at power button keeps flashing, ring of licht does not light up.

The nand read and compare were all OK
****************

J-Runner v0.3 Beta (7) Started

WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Checking Files
Finished Checking Files
Checking Console..
Version: 10
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5771
Falcon/Opus
Initializing nanddump1.bin..
Falcon/Opus
Glitch Selected
Nand Initialization Finished
* unpacking flash image, ....
Spare Data found, will remove.
Removed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 1.6
CB_A: 5771
CB_B: missing
CD (image): 8453
CD (decrypted): 8453
* this image will be valid *only* for: falcon
* patching SMC...
Patching Falcon version 1.6 SMC at offset 0x12A3
* zero-pairing...
* constructing new image...
* encrypting CB...
* encrypting CD...
* base size: 70000
* No separate recovery Xell available!
* Flash Layout:
0x0..0x1FF (0x200 bytes) Header
0x200..0xFFF (0xE00 bytes) Padding
0x1000..0x3FFF (0x3000 bytes) SMC
0x4000..0x7FFF (0x4000 bytes) Keyvault
0x8000..0x1133F (0x9340 bytes) CB_A 5771
0x11340..0x1733F (0x6000 bytes) CD 8453
0x17340..0xBFFFF (0xA8CC0 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
* Encoding ECC...Done!
------------- Written into output\image_00000000.ecc
Version: 10
Flash Config: 0x01198010
Writing Nand
image_00000000.ecc
Done!
in 0:18 min:sec

I made some pictures, but somehow i get an error while uploading.
See my dropbox link for the pictures.
First few are with the kit i got from the shop, but during soldering i noticed it was not coompatible so i dropped the SQB (J2B1 V2)and did the wiring myself.

https://www.dropbox.com/sc/uu6ouecvn9x45ih/AADjWJ0wi_gRYTgEG5v7EqKza

For wiring i used this guide, with the exeption of the red wire. I did it straight on the 5V
http://team-xecuter.com/forums/threads/148002-CR4-XL-PHAT-Opus-Falcon-Jasper-Install-Guide-(RGH2-)

briggs01 · Sep 19, 2015

the only way you will get any help mate , is to post pics of all your soldering and your glitch chip , first thing to try flash your stock nand back , remove red wire from glitch chip and see if the console boots

devisius · Sep 19, 2015

After a good night rest(i really needed that)

Reflashed the Original NAND back, unsoldered the red wire. Tried to boot.....same story.
I made some new pictures, with in the last one it shows the red wire unsoldered from "13".
Files are now far below 1MB of size and still can't upload?!?
So i post new pics within dropbox again ;(
https://www.dropbox.com/sh/bzzbyahiizbdj3i/AACKNYacJiqtLt4_pJozbnSCa?dl=0

Nintendo · Sep 19, 2015

devisius said:
After a good night rest(i really needed that)

Reflashed the Original NAND back, unsoldered the red wire. Tried to boot.....same story.
I made some new pictures, with in the last one it shows the red wire unsoldered from "13".
Files are now far below 1MB of size and still can't upload?!?
So i post new pics within dropbox again ;(
https://www.dropbox.com/sh/bzzbyahiizbdj3i/AACKNYacJiqtLt4_pJozbnSCa?dl=0

I saw this thread yesterday and now I understand what's going on.

You are using a CR4XL to install an RGH1.

I opened your nand on J-Runner and your console can be RGH1'd. CR4XL doesn't support RGH1.

devisius · Sep 19, 2015

So i have to change something in J-runner? Manual there just referes to the CR3.

I followed this manual, with the exeption of SQB; http://team-xecuter.com/forums/threads/148002-CR4-XL-PHAT-Opus-Falcon-Jasper-Install-Guide-(RGH2-)
5V red wire goes straight to pin 13 of R3B3.

*Reading al the post that can relate, that it now starts confusing me what does and doesn't applies.:crazy:

Nintendo · Sep 19, 2015

devisius said:
So i have to change something in J-runner? Manual there just referes to the CR3.

I followed this manual, with the exeption of SQB; http://team-xecuter.com/forums/threads/148002-CR4-XL-PHAT-Opus-Falcon-Jasper-Install-Guide-(RGH2-)
5V red wire goes straight to pin 13 of R3B3.

*Reading al the post that can relate, that it now starts confusing me what does and doesn't applies.:crazy:

The issue here is: Your console CB is compatible with RGH1, not RGH2, and CR4XL just support RGH2 (And R-Jtag). So you can keep your RGH1 CB and buy a RGH1 compatible glitcher or you can update your console and use RGH2, but RGH1 boots faster IMO.

jsinger47 · Sep 19, 2015

Nintendo said:
The issue here is: Your console CB is compatible with RGH1, not RGH2, and CR4XL just support RGH2 (And R-Jtag). So you can keep your RGH1 CB and buy a RGH1 compatible glitcher or you can update your console and use RGH2, but RGH1 boots faster IMO.

He doesn't have to update his console. RGH2 works on any dashboard.

Nintendo · Sep 19, 2015

jsinger47 said:
He doesn't have to update his console. RGH2 works on any dashboard.

As far as I know, on Jrunner, when you select "Glitch" on Xebuild, you can't select "CR4". It's been a long time since my last RGH1 though.

jsinger47 · Sep 19, 2015

Nintendo said:
As far as I know, on Jrunner, when you select "Glitch" on Xebuild, you can't select "CR4". It's been a long time since my last RGH1 though.

Correct. Which is why you select "Glitch2."

Like i said. RGH2 works on any dashboard.

devisius · Sep 19, 2015

Just to be sure, i unsoldered all wires and tested. Xbox boots normal

Nintendo · Sep 19, 2015

jsinger47 said:
Correct. Which is why you select "Glitch2."

Like i said. RGH2 works on any dashboard.

Never tried it, sorry if that created any confusion.

Then, for the OP. Load your nand on J-Runner, in the upper right corner, select Glitch2 and tick the CR4 box, then create and write Ecc.

devisius · Sep 22, 2015

K, I soldered all back as before run the check, jrunner backupped the NAND and verified. All was oke.
I checked the boxes RGH2 and with it the CR4 and ran the ECC. After writing the ECC I plugged the x360 in and booted. Same sh*te as before. No boot, no screen.
I returned to reprogram the NAND but now get no connection or sometimes I get Wrong version 0.0
Almost looks like the NAND is not responding well.

Will continue soon, kinda frustrated now ;(

alexander_1333 · Sep 22, 2015

Wrong version 0.0?Replug nand reader.

devisius · Sep 22, 2015

I resoldered and replugged several times, even did a check with multimeter A to B and top/bottom check if all is soldered correct.
Still get;
Version: 10
Flash Config: 0x00000000
Can not Continue
Can not continue

Gonna resolder again en test all cables.

briggs01 · Sep 22, 2015

soldering on nand reader wires to the board

devisius · Sep 22, 2015

Faulty connector, was giving signal trough one sec and not the other!
(brown/black)

Checking Console..
Version: 10
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5771
Falcon/Opus

devisius · Oct 6, 2015

programmer is dead now aswell and faulty NAND on x360, so seems all is dead now.

Sometimes things just suck

briggs01 · Oct 6, 2015

devisius said:
programmer is dead now aswell and faulty NAND on x360, so seems all is dead now.

Sometimes things just suck

if you have the original nand just get your programmer sorted and flash it back

Search

Search

FALCON FLashed NAND, but stuck in boot

devisius

Junior Member

briggs01

devisius

Junior Member

Nintendo

devisius

Junior Member

Nintendo

jsinger47

Nintendo

jsinger47

devisius

Junior Member

Nintendo

devisius

Junior Member

alexander_1333

devisius

Junior Member

briggs01

devisius

Junior Member

devisius

Junior Member

briggs01