-Mafia5K- wrote

-Exploit wrote

-Mafia5K- wrote Find your ldv by counting the f's in XeLL.

It should be the same as your stock image.

But im trying to match my stock ldv with my rgh, bc my rgh is on latest dash and has ldv 2. But i think i efused it. Please keep in mind im a noob when it comes to all this ldv stuff so please bare with me and speak in a little bit more lower level vocabulary. thanks

Its simple to understand, You want to match your ldv always otherwise it wont boot.

I already explained what to do, so ill elaborate slightly,

You stock nand is never Negative, it is always the correct LDV(if it boots), Only your hacked image needsd to be updated on these applications/dual nand systems.

post #1 "dump your stock nand using your cygnos" (Why is this important - Becuase it has the latest LDV,(Lock down value)So, you will use it to build your Hacked image)

Post #2 "Use J-Runner to build hacked image and flash it to your extra Nand(cygnos)". Open jrunner, Select your stock nand you just dumped, now enter CPU KEY. Once you have entered it it will show Correct CPU KEY. Now click Build image, select your dashboard. Once your done this hacked image will have the same LDV as your stock nand The one "you dumped,and used for the build process/ the one that is installed to your xbox".

Simply, take your newly created image and flash it back to your Cygnos Nand bank, and your Done! Everything should work both nands should boot.

Unless you havent provided something i dont know this is the answer to your problem--(my hacked image wont boot after i updated my stock nand?)--in depth. just follow that and post back if you get stuck and ill help you via remote connection(teamviwer).

still having troubles the ldvs match but neither of them boot now.. this would make it alot easier for me due to how many times and how many ways i tried to fix this via teamviewer! Hopefully you will catch me when im online so i can resolve this slight issue. I appreciate your time Mafia...

-Exploit wrote

-Mafia5K- wrote

-Exploit wrote

-Mafia5K- wrote Find your ldv by counting the f's in XeLL.

It should be the same as your stock image.

But im trying to match my stock ldv with my rgh, bc my rgh is on latest dash and has ldv 2. But i think i efused it. Please keep in mind im a noob when it comes to all this ldv stuff so please bare with me and speak in a little bit more lower level vocabulary. thanks

Its simple to understand, You want to match your ldv always otherwise it wont boot.

I already explained what to do, so ill elaborate slightly,

You stock nand is never Negative, it is always the correct LDV(if it boots), Only your hacked image needsd to be updated on these applications/dual nand systems.

post #1 "dump your stock nand using your cygnos" (Why is this important - Becuase it has the latest LDV,(Lock down value)So, you will use it to build your Hacked image)

Post #2 "Use J-Runner to build hacked image and flash it to your extra Nand(cygnos)". Open jrunner, Select your stock nand you just dumped, now enter CPU KEY. Once you have entered it it will show Correct CPU KEY. Now click Build image, select your dashboard. Once your done this hacked image will have the same LDV as your stock nand The one "you dumped,and used for the build process/ the one that is installed to your xbox".

Simply, take your newly created image and flash it back to your Cygnos Nand bank, and your Done! Everything should work both nands should boot.

Unless you havent provided something i dont know this is the answer to your problem--(my hacked image wont boot after i updated my stock nand?)--in depth. just follow that and post back if you get stuck and ill help you via remote connection(teamviwer).

still having troubles the ldvs match but neither of them boot now.. this would make it alot easier for me due to how many times and how many ways i tried to fix this via teamviewer! Hopefully you will catch me when im online so i can resolve this slight issue. I appreciate your time Mafia...

Explain what you did and post logs.

-Mafia5K- wrote

-Exploit wrote

-Mafia5K- wrote

-Exploit wrote

-Mafia5K- wrote Find your ldv by counting the f's in XeLL.

It should be the same as your stock image.

But im trying to match my stock ldv with my rgh, bc my rgh is on latest dash and has ldv 2. But i think i efused it. Please keep in mind im a noob when it comes to all this ldv stuff so please bare with me and speak in a little bit more lower level vocabulary. thanks

Its simple to understand, You want to match your ldv always otherwise it wont boot.

I already explained what to do, so ill elaborate slightly,

You stock nand is never Negative, it is always the correct LDV(if it boots), Only your hacked image needsd to be updated on these applications/dual nand systems.

post #1 "dump your stock nand using your cygnos" (Why is this important - Becuase it has the latest LDV,(Lock down value)So, you will use it to build your Hacked image)

Post #2 "Use J-Runner to build hacked image and flash it to your extra Nand(cygnos)". Open jrunner, Select your stock nand you just dumped, now enter CPU KEY. Once you have entered it it will show Correct CPU KEY. Now click Build image, select your dashboard. Once your done this hacked image will have the same LDV as your stock nand The one "you dumped,and used for the build process/ the one that is installed to your xbox".

Simply, take your newly created image and flash it back to your Cygnos Nand bank, and your Done! Everything should work both nands should boot.

Unless you havent provided something i dont know this is the answer to your problem--(my hacked image wont boot after i updated my stock nand?)--in depth. just follow that and post back if you get stuck and ill help you via remote connection(teamviwer).

still having troubles the ldvs match but neither of them boot now.. this would make it alot easier for me due to how many times and how many ways i tried to fix this via teamviewer! Hopefully you will catch me when im online so i can resolve this slight issue. I appreciate your time Mafia...

Explain what you did and post logs.

Dump both nands through cygnos toolbox (Cygnos and Stock)

Updated the stock nand via Jrunner

Built a hacked img off of that one (Jrunner)

They both had the same ldv

Still doesnt work

What do you mean by updated stock nand? Since your stock nand doesnt boot its nothing to due with LDV, probably hardware failure or something with the cygnos wires.

-Mafia5K- wrote What do you mean by updated stock nand? Since your stock nand doesnt boot its nothing to due with LDV, probably hardware failure or something with the cygnos wires.

no ur misunderstanding my problem. I had the stupidity to try to write a different NAND to my stock bank. And when I did that I forgot to make a backup of that NAND and now when I just read the stock bank and take that NAND and try to update it the ldv is different from my Cygnos bank NAND which I have my updated (15574) ggbuild NAND on. Now the stock won't boot. What do you suggest I do? I aplogize if you have a hard time understanding. I'm trying my best to explain to you as simple as possible

-Exploit wrote

-Mafia5K- wrote What do you mean by updated stock nand? Since your stock nand doesnt boot its nothing to due with LDV, probably hardware failure or something with the cygnos wires.

no ur misunderstanding my problem. I had the stupidity to try to write a different NAND to my stock bank. And when I did that I forgot to make a backup of that NAND and now when I just read the stock bank and take that NAND and try to update it the ldv is different from my Cygnos bank NAND which I have my updated (15574) ggbuild NAND on. Now the stock won't boot. What do you suggest I do? I aplogize if you have a hard time understanding. I'm trying my best to explain to you as simple as possible

this isnt a ldv issue then, and it would have been better if you said this from the begining.

You dont have a nanddump from this system?

-Mafia5K- wrote

-Exploit wrote

-Mafia5K- wrote What do you mean by updated stock nand? Since your stock nand doesnt boot its nothing to due with LDV, probably hardware failure or something with the cygnos wires.

no ur misunderstanding my problem. I had the stupidity to try to write a different NAND to my stock bank. And when I did that I forgot to make a backup of that NAND and now when I just read the stock bank and take that NAND and try to update it the ldv is different from my Cygnos bank NAND which I have my updated (15574) ggbuild NAND on. Now the stock won't boot. What do you suggest I do? I aplogize if you have a hard time understanding. I'm trying my best to explain to you as simple as possible

no

this isnt a ldv issue then, and it would have been better if you said this from the begining.

You dont have a nanddump from this system?

-Mafia5K- wrote

-Exploit wrote

-Mafia5K- wrote Find your ldv by counting the f's in XeLL.

It should be the same as your stock image.

But im trying to match my stock ldv with my rgh, bc my rgh is on latest dash and has ldv 2. But i think i efused it. Please keep in mind im a noob when it comes to all this ldv stuff so please bare with me and speak in a little bit more lower level vocabulary. thanks

Its simple to understand, You want to match your ldv always otherwise it wont boot.

I already explained what to do, so ill elaborate slightly,

You stock nand is never Negative, it is always the correct LDV(if it boots), Only your hacked image needsd to be updated on these applications/dual nand systems.

post #1 "dump your stock nand using your cygnos" (Why is this important - Becuase it has the latest LDV,(Lock down value)So, you will use it to build your Hacked image)

Post #2 "Use J-Runner to build hacked image and flash it to your extra Nand(cygnos)". Open jrunner, Select your stock nand you just dumped, now enter CPU KEY. Once you have entered it it will show Correct CPU KEY. Now click Build image, select your dashboard. Once your done this hacked image will have the same LDV as your stock nand The one "you dumped,and used for the build process/ the one that is installed to your xbox".

Simply, take your newly created image and flash it back to your Cygnos Nand bank, and your Done! Everything should work both nands should boot.

Unless you havent provided something i dont know this is the answer to your problem--(my hacked image wont boot after i updated my stock nand?)--in depth. just follow that and post back if you get stuck and ill help you via remote connection(teamviwer).

Okay Mafia, Very nice simple and easy explaination but i guess i didnt fill you in completely. For my stock bank, I tryed flashing a img that was from a earlier dashboard to that bank but i already updated the nand using the MS update. so now even when i try to build a img off of my nanddumps, it never boots on the stock bank. Ive tryed making the ggbuild nand lower then the current stock one but it still didnt work. Now that ive tryed messing with the modded (cygnos bank) the ggbuild nand doesnt boot also. So basically i have too banks that have nands that dont boot. Although i do have the original nand from when i first got the console rghed which is in the 13 series. Ive tryed building imgs off that still no success. I know you said to post logs, but there really isnt anything you need to see. If you can help me i will be forever thankful. Thanks Mafia

Why are you making new threads to ignore my requests.

If you know its a ldv issue And how to fix whats this thread for?

-Mafia5K- wrote Why are you making new threads to ignore my requests.

If you know its a ldv issue And how to fix whats this thread for?

Ummm i replyed to the other thread, but the other one was replying to another member. This was my first post about this issue. and i dont know how to fix it! i never said i did. i have everything needed to fix it, but for some apparent reason the console still chooses not to boot.