Hello everyone,
My console has the LiteOn 83850 v1 and the dashboard is 13599. I just updated my firmware to 2.0 and when doing it, I got the following error: "the target f/w does not appear to match the drive ..." Before flashing it, my key was verified. I also double checked the source F/W was LiteOn DG-16D2S 02510C (generated a dummy.bin from the Key DB) and the Destination F/W was was the 2.0 for LiteOn drives. Everything looked good, so I ignored the error message and did the Lite-On erase, and the drive stated it was in 0x72 vendor mode. It did not, however, have the correct data in the side window (states Vendor ID, Device ID etc.) as it was all blank. Before realizing it, I tried the write. It kind of hung, then action (ability to use the program) was back in the JungleFlasher window, without finishing the write, almost like a glitch. I decided to do the Lite-On Erase again, and this time it returned all correct properties in the window to the right. I then did a successful write. Now I can not get my key to be verified on the drive, even after refreshing it. I tried to load from the Key DB, but still no verified key, as it was prior to the flash. I tested the drive in the box, and all works fine (games/dvds) because I knew it was the correct key. Will this make future problems when flashing the drive? How do I get my key back in verified status? Thanks to anyone who can help with this!!
My console has the LiteOn 83850 v1 and the dashboard is 13599. I just updated my firmware to 2.0 and when doing it, I got the following error: "the target f/w does not appear to match the drive ..." Before flashing it, my key was verified. I also double checked the source F/W was LiteOn DG-16D2S 02510C (generated a dummy.bin from the Key DB) and the Destination F/W was was the 2.0 for LiteOn drives. Everything looked good, so I ignored the error message and did the Lite-On erase, and the drive stated it was in 0x72 vendor mode. It did not, however, have the correct data in the side window (states Vendor ID, Device ID etc.) as it was all blank. Before realizing it, I tried the write. It kind of hung, then action (ability to use the program) was back in the JungleFlasher window, without finishing the write, almost like a glitch. I decided to do the Lite-On Erase again, and this time it returned all correct properties in the window to the right. I then did a successful write. Now I can not get my key to be verified on the drive, even after refreshing it. I tried to load from the Key DB, but still no verified key, as it was prior to the flash. I tested the drive in the box, and all works fine (games/dvds) because I knew it was the correct key. Will this make future problems when flashing the drive? How do I get my key back in verified status? Thanks to anyone who can help with this!!
I have an old XP PC that I have set up to do everything, and don't feel like updating the hardware to do it on my more modern PC. It was odd, when I first pulled up the Key, the Source F/W was the old Lite-On 83850, even though I knew it was suppose to be the 0250 because I previously flashed to stock, updated the xbox to 13599 dash, then upgraded the drive to the 1.91. That is why I chose to generate a Dummy.bin from the KeyDB, so that it would state 0250 in the source F/W which made (I thought) everything match. Thanks for the Info mate!