Updating NANDs with flashed drive.

[Scrufdog]

Trying to figure something out here. I'll be overly specific so that you know what I mean.I'm preparing to install a Demon and R-jtag on a 16203 Falcon with a flashed DVD Rom, I use it to play backups online currently.Once everything is installed, and NANDs are dumped, is there any reason why I wouldn't be able to create a retail 16537 NAND with jrunner and flash it to the Xbox side, and still be XBL safe? I ask this to see if I can skip flashing my DVD Rom back to stock, update online or usb, then flash back to custom firmware.So long as LDVs all match, is this something I can safely do? Basically, if I have a retail 16203 dump and my CPU key, can I use jrunner to create an Xbox Live Safe retail NAND?

 

[scott1503]

I believe the answer is no as the update you will officially have in the console will not be the actual update needed from Microsoft and the xbox will technically still be on 16203. I could be wrong but im sure a someone like Martin will confirm the right path for your console

 

[BrockThunderjam]

I believe the answer is no as the update you will officially have in the console will not be the actual update needed from Microsoft and the xbox will technically still be on 16203.

Huh? A retail nand is a retail nand. If he's building a retail nand and the LDV is incremented correctly then what's the difference?

 

[gavin_darkglide]

Yes i believe you can....... i have updated stock this way before, and was still able to get on xbox live....... so load 16203 image in jrunner and create 16537 retail image(NOTE when updating this way the efuses dont blow, so there is no need to change ldv)(also this will only work with this 16537 dash if the xbox has been updated to 15+). flash retail image to stock nand. install avatar and kinect data via stock 16537 usb update. then create jtag nand and flash to demon. for this you can now use dashlaunch 3.08 and Xebuild 1.08(included in latest j-runner) to install avatar and kinect data for demon nand.

 

[Scrufdog]

I'm unsure if Microsoft has some way to see the LDV when an update is installed and you eventually get online. Meaning is there a database that knows when I updated my console to 16203 I had an LDV of 8, and now I'm on 16537 with the same LDV. Obviously this could be fixed by just adding 1 to the LDV, which I'll do anyway. I'll wait for more verification before I try. Thanks so far for helping. Looks like it shouldn't be a problem.

 

[BL4K3Y]

I'm unsure if Microsoft has some way to see the LDV when an update is installed and you eventually get online. Meaning is there a database that knows when I updated my console to 16203 I had an LDV of 8, and now I'm on 16537 with the same LDV. Obviously this could be fixed by just adding 1 to the LDV, which I'll do anyway. I'll wait for more verification before I try. Thanks so far for helping. Looks like it shouldn't be a problem.

If the console boots fine from a retail NAND, you can update using XBL and everything will be fine.

The CPU eFUSEs are only burned/changed when an official system update is applied.

 

[Scrufdog]

Well yeah, I know that. My concern with this thread is doing an official update with a flashed drive. That little bit of thought was just wondering if Microsoft can track LDV values.

 

[BL4K3Y]

Well yeah, I know that. My concern with this thread is doing an official update with a flashed drive. That little bit of thought was just wondering if Microsoft can track LDV values.

If the drive is flashed, there is a chance that the console will get stuck in an update loop.

M$ can and will update the LDV with official system updates, but I don't think they can tell what the LDV is on *your* specific console.

M$ send a "hit" with every official update which causes the LDV to increment by one.

 

[Scrufdog]

That's why I'm figuring if you update the Xbox side with a retail NAND that's has the avatar data pre-installed it should bypass the firmware check and possible error.

 

[gavin_darkglide]

if you are that woried you would just flas back to stock before updating. i never had any problems updating like this, but have never tried to do it with a flashed drive.

 

[Scrufdog]

I'm not stressing about it, just wondering if it's a possible shortcut.

 

[korn_16_f_t_l]

I'm not stressing about it, just wondering if it's a possible shortcut.

The person that RGH'd my system (WNY) told me to do it this way if i was concerned about updating offical MS update with a flashed DVD rom as well so ill be watching this thread.

i dont have the means nor the patience to want to piss with my GOW3 slim and all the flashing and it was kamakazied, no hardware to flash it back to stock if i wanted to ect. this isent just a possible work around...its a work around for people that may not have a means to flash there DVD rom to stock...but ya ill be watching this

 

[Scrufdog]

I'll find out one way or another by the weekend, and report back.

 

[korn_16_f_t_l]

I'll find out one way or another by the weekend, and report back.

good deal ill build the NAND and install the drivers and be set to simply flash when u report back, nothing is truly LIVE safe when it comes to mods we are all aware but it pays to be as truly cautious as you can specially when you do not have the tools at your disposal for flashing DVD roms

 

[stefanounick]

Its always best to update stock nand via official updates. Especially if the CB changes. Last time Microsoft flashed a drive was on 13599, and those affected were mostly people with phat spoofed drives, or the unlocked 0272. Not saying its impossible but they wouldn't check the fw since they would be giving away the goods, only thing they could easily check is OSIG. So if you're gonna make it a big deal that you don't want to flash stock back, grow a pair and just update.

 

[Scrufdog]

Its always best to update stock nand via official updates. Especially if the CB changes. Last time Microsoft flashed a drive was on 13599, and those affected were mostly people with phat spoofed drives, or the unlocked 0272. Not saying its impossible but they wouldn't check the fw since they would be giving away the goods, only thing they could easily check is OSIG. So if you're gonna make it a big deal that you don't want to flash stock back, grow a pair and just update.

Wow. Well, I assure you I have a set swinging. I'm not lazy either. I'm just trying to see what happens and checked to see if anyone else had tried. Not everyone has the ability to flash their drive back to stock for an official update, this is mostly for those people. If it helps I updated my friend's Xbox with a flashed Benq last night from 14719 to 16203 using the official update on a Usb drive, no problems. That tells me that MS probably isn't checking the firmware at the moment. Once I get his Rjtag sorted out I will Rjtag and Demonize my Falcon with flashed Benq and experiment.

 

[stefanounick]

haha, if the retail image matches the CB fuses and LDV it should be working fine
thing is, only the official update burns the fuses, so you wont be able to use a 16573 image on a 13599 last updated console for example
thats why its recommended to do official updates

 

[korn_16_f_t_l]

haha, if the retail image matches the CB fuses and LDV it should be working fine
thing is, only the official update burns the fuses, so you wont be able to use a 16573 image on a 13599 last updated console for example
thats why its recommended to do official updates

i used this method and didnt set the LDV's to match or any thing was not to concerned about it....probably MAYBE only 1 new ban wave otw to push people to buying the xbox one any how, the way i see it there not horribly concerned with these things at the moment and focusing more toward gearing up for the xbox one any how......if there going to use the existing live service im curious if they have already changed a lot of there security up for the xbox one live service also perhaps removing checks for the 360's? no one will really know for sure but as i said im almost positive MS is more geared toward the xbox one than being concerned with these things at them moment.