Not-So-Noob Jasper 512MB RGH Problem

Tag234

Full Member
Apr 12, 2010
45
0
California
Hello, I posted in this forum because I do not yet have the post count to post elsewhere:

I sold a Jasper 512MB RGH console to someone online about 2 months ago. They had it working just fine for about a month. The guy calls me after a month and says that it won't boot the dashboard anymore, it will only boot xell. He says that his brother was trying to add online functionality with some patch and that made the dash not boot anymore.

I do not know what patch he is refering too or anything like that, so I am treating the console as if it had a bad flash and trying to go from there.

Here is the problem: I get the console back, and the LDV value is 2 (fuse line 07 has 2 fs). Xell is indeed booting just fine and the KV seems to be correct. The Original 13599 NAND that I have from when I first did the console also has an LDV value of 2, so I do not believe that the console was put through any kind of Microsoft update. However, when I make a 14719 update using J-runner, the CPUKey and the Original NAND, the console will still only boot Xell and will not boot dash.

The console boots Xell on the first green blink every single time. When I try to boot with the power button, the green light blinks once, and then does not blink again. There is nothing that happens on screen at all.


I have no idea where to go from here. It seems that the LDV value is fine, and my method for creating the NAND is fine, but it doesn't boot. I have tried flashing the Original NAND and booting it: that works fine too.

Any ideas? I could post you wiring if you want, but I have rewired the whole console since this started with no change.
 
Last edited:

hodgie

VIP Member
Apr 8, 2011
428
0
Southern, VT (usa)
have you tried another source of creating your image? maybe multi-builder? just to try.
wire routing issue maybe?
 
Last edited:
  • Like
Reactions: Tag234

Tag234

Full Member
Apr 12, 2010
45
0
California
Yea I actually tried multi builder first back when Jrunner wasn't even out >.< No change.

I do not think its wire routing because I let the wires hang free and tried booting a few times before gluing em down in the spots that I normally route through. Nothing ever happened at all.

Since I have gotten it back, I havent even seen the dash boot and freeze once. Xell is 100% boot, dash is 0%

try and flash ur 14699 freeboot n c if it boots.
it does, the 13599 stock dash I have does boot just fine.
 
Last edited:

hodgie

VIP Member
Apr 8, 2011
428
0
Southern, VT (usa)
so you have a 14699 ggbuild(freeboot) image running, but cant get 14719 ggbuild to boot?
 
Last edited:
  • Like
Reactions: Tag234

Tag234

Full Member
Apr 12, 2010
45
0
California
14699 ggbuild is a no go, just like 14719.

I am saying the stock NAND works (13599), once I try and build any hacked dash from it, only the Xell eject button works...
 

Tag234

Full Member
Apr 12, 2010
45
0
California
Lol after messing with this console for about a month, of course as soon as I make this topic, I find the solution:

I flashed the Original NAND (13599), updated to stock 14699, and then re RGHd 14719 from there. Worked just fine.... If any has an ideas on what could cause the console to be put in such an odd state, I would really like to know.