How long does it freeze for? It could be your harddrive too. Are you using the latest multibuilder v7 to build your image and latest rawflash v4? Also try, manually remapping the bad block, flash the image you make with multibuilder v7 with your nand flasher and not rawflash.
RGH Jasper BB 512MB~ 6751 Won't Glitch and CR Green Light doesn't Flashes
- Thread starter watkmogi
- Start date
Your blocks are probably not remapped properly.
Did you manually remap them or they were remapped automatically?
RawFlash will still show the blocks are bad cause it will try to flash them and churn out an error.
But that you don't have to worry. Just take the original untouched nand you extracted originally. MultiBuild 0.7 does that all automatically for you.
Did you manually remap them or they were remapped automatically?
RawFlash will still show the blocks are bad cause it will try to flash them and churn out an error.
But that you don't have to worry. Just take the original untouched nand you extracted originally. MultiBuild 0.7 does that all automatically for you.
Now that thing won't glitch anymore, i think the problem are the bad blocks, how could i remap the bad blocks manually? I tried nand healer and multibuilder, didnt work.. and now when I put the orginal/stock nand the console gives 3RL, WTH?Your blocks are probably not remapped properly.
Did you manually remap them or they were remapped automatically?
RawFlash will still show the blocks are bad cause it will try to flash them and churn out an error.
But that you don't have to worry. Just take the original untouched nand you extracted originally. MultiBuild 0.7 does that all automatically for you.
3RL, but whats the secondary error code? If it's 0022, most probably there's something wrong with your wiring, you could try to put the CR in PRO mode and see if it boots. Bad blocks. Just rebuild the Freeboot using Multibuilder, and use the original Dump file in the DATA folder.
Rebuild the freeboot with the CPU KEY. and you`re good to go. That should work.
The last time i tried remapping manually and whatever, it just became worse. I left multibuilder to do it all. The system at 7 BAD BLOCKS on a bloody slim. And constant hanging issues. Until i let it remap manually. it was fine Hope this helps.
Do know that the bad blocks are remapped. From the First Bad block to the REAR of the Reserve blocks.
Rebuild the freeboot with the CPU KEY. and you`re good to go. That should work.
The last time i tried remapping manually and whatever, it just became worse. I left multibuilder to do it all. The system at 7 BAD BLOCKS on a bloody slim. And constant hanging issues. Until i let it remap manually. it was fine
Hope this helps.Do know that the bad blocks are remapped. From the First Bad block to the REAR of the Reserve blocks.
This box is really DRIVING me NUTS. been trying so many things and NOTHING works.
Here's what i`ve did so far.
Replaced Coolrunner chip to another.
Redone Wires using original Wires that came with the chip.
Redone Wires, (Replaced Points A,B,C,D with AWG 30 Wires)
Put in caps in GND and A and InLine with D point.
Also tried 50CM, 30CM AWG 30 wires for point D as well.
And also using DOUBLE BLUE ORIGINAL Cables for the D Point.
It still does the same stupid thing. (think there's something wrong with signals here, not sure which wire.)
It still starts up, blinks once, and stops, and stays red, No XELL. I`ve used this method of wiring for my other JasperBB sets and they boot up within 10 seconds or less. It's just the one particular board that is really CHEESING me off. Been trying to get it to work for the last 24 hours.
AT THE END OF THE DAY, NOTHING WORKS. PLEASE HELP
Does anyone have a solution? I`ve tried the PHAT and SLIP Swtiches as well. still no GO.
Here's what i`ve did so far.
Replaced Coolrunner chip to another.
Redone Wires using original Wires that came with the chip.
Redone Wires, (Replaced Points A,B,C,D with AWG 30 Wires)
Put in caps in GND and A and InLine with D point.
Also tried 50CM, 30CM AWG 30 wires for point D as well.
And also using DOUBLE BLUE ORIGINAL Cables for the D Point.
It still does the same stupid thing. (think there's something wrong with signals here, not sure which wire.)
It still starts up, blinks once, and stops, and stays red, No XELL. I`ve used this method of wiring for my other JasperBB sets and they boot up within 10 seconds or less. It's just the one particular board that is really CHEESING me off. Been trying to get it to work for the last 24 hours.
AT THE END OF THE DAY, NOTHING WORKS. PLEASE HELP
Does anyone have a solution? I`ve tried the PHAT and SLIP Swtiches as well. still no GO.
Have you moved the actual paths of the wires or just replaced them? you should try messing around with the paths
Does anyone has a nand donor that I could use to try to build a new one? At least I got the cpu key... Still getting 3rl when I put back the stock nand on
x360ccm
BANNED
i would of done but were i upload um that i had has been took down.so looking for new file shareing place lol.
and no i lost all these nands dumps coz of this.
and no i lost all these nands dumps coz of this.
Last edited:
Now i'm getting 3rl 0022 after 3~5 secs when I flashs the stock nand back. Took all CR's wires from the board then put the stock nand back and still getting 3rl...
PS: I had the first nand dump with 13599 dash, but i ran xell and get the cpu key then I fashed the nandflash with rawfash and the hacked nand(14699) were freezing @ Xbox's logo, so I tried to flash again but that time using multibuilder 0.7(used 0.5 before) and now poof, always 3rl after stock nand(13599) flashed on console~
PS2: I tried with retail nand 14699 made in multibuilder too, but still nothing.
Do I need to try changing the LDV something? I checked on 360 dump tool and there shows LDV 0 and 4... Some ppl told me that 0022 is GPU that went poof :/
PS: I had the first nand dump with 13599 dash, but i ran xell and get the cpu key then I fashed the nandflash with rawfash and the hacked nand(14699) were freezing @ Xbox's logo, so I tried to flash again but that time using multibuilder 0.7(used 0.5 before) and now poof, always 3rl after stock nand(13599) flashed on console~
PS2: I tried with retail nand 14699 made in multibuilder too, but still nothing.
Do I need to try changing the LDV something? I checked on 360 dump tool and there shows LDV 0 and 4... Some ppl told me that 0022 is GPU that went poof :/
Goldensavage
VIP Member
If you've been messing about with the Nand and got a 0022 error. Then it is most likely the LDV
The LDV Value has changed. Different dash means different Value.
Go Here to sort it out
http://team-xecuter.com/forums/showthread.php?t=77634
---------- Post added at 14:55 ---------- Previous post was at 14:53 ----------
Just use nand x to flash your original Nand back.
Also. Can i suggest you start a new thread, you'll get more people helping.
i should open a new thread but please answer me a last time.
i reflash the nanddump.bin to nand
reassemled and desoldered all cr and qsb. now e79.
please i want to turn original if possible. then i'll stop bother you
---------- Post added at 16:12 ---------- Previous post was at 16:10 ----------
and only one red led blinking
i reflash the nanddump.bin to nand
reassemled and desoldered all cr and qsb. now e79.
please i want to turn original if possible. then i'll stop bother you
---------- Post added at 16:12 ---------- Previous post was at 16:10 ----------
and only one red led blinking
I dunno if I can post those inf, but... Just opened on Dump tool the reatail nand and the reatail nand made on multibuilder, i dont know if im doing right so...
Goldensavage
VIP Member
You original Nand read does not have any values 6BL and 7BL? Are you sure you read the original Nand correctly, or it was soldered correctly.
and
Have you tried what Martin has said in his sticky about LDV
In the my360 folder of the Multibuilder program is an Options.ini
Open this with any text editor and about 17 lines down it says "cfldv="
put a 5 next to that that is the LDV value. The problem is, that is was 4 for 13599. So it will most likely be 5 for 14699. It normally goes up in increments of 1
The nand you originally took was from 13599, and the Multibuilder you used was for 14699.
An earlier version of multibuilder had the previous dashboard.
and
Have you tried what Martin has said in his sticky about LDV
In the my360 folder of the Multibuilder program is an Options.ini
Open this with any text editor and about 17 lines down it says "cfldv="
put a 5 next to that that is the LDV value. The problem is, that is was 4 for 13599. So it will most likely be 5 for 14699. It normally goes up in increments of 1
The nand you originally took was from 13599, and the Multibuilder you used was for 14699.
An earlier version of multibuilder had the previous dashboard.
Last edited:
Thnaks for the answer, I'm @ work right now, gonna test it out when I get back home...
Still the same, tried LDV values 4,5,6,7,8 and still getting 3rl after 5 secs... Maybe I screwed the GPU, dunno how but :/
Martin C
VIP Member
Goldensavage
VIP Member
PPS timing your 0022 error is quite important. Approx timings for 0022 on stock NAND:
5s- issue with CPU_RST/CPU_PLL_BYPASS
15s - LDV
30s - GPU issue.
From Martin's LDV guide