Unsupported Disc, Stock Firmware Options

[lord^infamous]

I have a jasper here that needed the dvd key recovered so I RGH'd it. Things went smoothly and got the CPU and DVD key. When I dumped the nand, the xbox was stuck trying to update from 13146 but failed because the dvd drive was not connect. So instead of flashing the key to the new dvd drive first and proceeding with the update, I updated the dash to 14699. Yes, I know this was a mistake. At first I was getting RROD 0022 with stock 14699. My mistake, so I opened the 14699 nand to find the LDV value was 6 but should be 7. Patched it to 7 and now boots just fine. Dvd drive works and recognizes all my originals but I get "this disc is not supported" after trying to boot the game. Identical behavior of back ups that fail the recent AP2.5 checks. I opened the nand with 360 flash tool thinking the OSIG was wrong. The 13146 dump and 14699 both say 93450 but shouldn't they both say 02510? Never the less, I have tried stock 93450 and stock 02510 and both give me unsupported disc. Ideas?

[lord^infamous]

Bump

[SergioFoX]

How did you patch it?

[lord^infamous]

I used 360 Flash Tool to edit the LDV value of the nand. This really has me confused. What reason would original firmware, original game and stock dashboard give unsupported disc?

[pigbait]

funny i have the same thing going on, my LVD changed on my stock hand from 11 to 12 and when i keep it at 11 it gets RROD 0022 but if i patch it to LVD 12 it boots but gives me same errors Unsupported Disc laser is good

[lord^infamous]

I wish I had more info to give you but I put the system to the side until I found more time to play with it. Let me know if you find anything out.

[krizalid]

build the retail nand with multibuilder or xeBuild official and all AP25 checks are ignored even if the console OSIG and the drive suport it. Make sure you build the latest 14699, I can confirm this on a Jasper16mb with LiteOn drive flashed with LT+3.0 and booting old AP25 data on discs.

[lord^infamous]

I have built the retail nand with 360 multi builder already. I opened my original nand with 360 flash tool and noticed the cb version is 6751. To compare, I opened the retail_nand that multi builder gave me and it used a cb version of 6750. Could that be the probelm? If so, how do I get mult builder to use cb 6751?

[jrl]

Sorry to resurect an old thread but...

Did you ever find a solution to this problem? I have searched google but every result deals with CFW on the drives.
I dont have custom firmware, I just want to be stock and reading disks. I bought this xbox used online, the seller said it did not read disks. It had a really old dash on it and gave an e81 when I tried to update it. The DG-16D4S has not been modified in any way. I RGH to get CPU and DVD key and built a retail NAND with 360 multibuilder with a more current dash. Flashed it and removed all Coolrunner stuff. Then I updated to the most recent dash 14719 via $systemupdate on USB and it updated fine. Weird thing is now it will read disks if I am not connected to XboxLive. But as soon as I connect to XboxLive the drive magically gives unsupported disc error.

[lord^infamous]

Actually, I kinda gave up and decided to use the xbox to just stream movies. I'm pretty sure I know what the issue is but I don't have the time to try and fix it. I think it's a problem with my KV but that's as far as I want to dig on the subject. Feel free to let me know if you figured anything out.

[Farid]

@ lord^infamous
Maybe this is an stupid idea but you can try it :
Make a stock nand with the correct LDV and dashboard bellow 12625 with xeBuild-GUI-2.04. Then connect a liteon drive with orig-93450C.bin to your box and try to update your dashboard with version 13604. This should reflash your liteon with orig-02510C-1c000.bin and play games.