Print

[AnimeCommander]

QUOTE(majinsoftware @ Nov 21 2009, 09:36 PM)

Congrats, Thats pretty much the same method as mine.

Just one problem tho. Now that its public knowledge MS will be able to change it.
So you should have waited intill the ban wave had been over for a few weeks.

Who cares if they update it? I mean those that banned by surprise (the first few days or so) can now regain the features and stay offline. It's pretty much up to each person individually if they're going to decide to try to sign a new box on Live with a mod. To me it's just asking to get banned. And I'm fairly certain that this isn't a "ban wave" and that they're now setup to detect and band in near real time (meaning once you're detected, there is no more months on end delay before banning).

Anyway, I'm rigging up my cable now and hopfully my next post will have some saves done.

[DemisesAngel]

QUOTE(majinsoftware @ Nov 22 2009, 12:36 AM)

Congrats, Thats pretty much the same method as mine.

Just one problem tho. Now that its public knowledge MS will be able to change it.
So you should have waited intill the ban wave had been over for a few weeks.

How do you think they would propose to ban the consoles again if they can't log back in to live?

[Ironaxe]

Is a NAND Dump whitch looks like this good enough to keep it safe ( in case something wents wrong ^^ )

Thats the best Dump i got in about 10 tries ( i got 6 of that with exact the same Bad Block and Bad Block Location )

( Found the Picture via Google but got the same Bad Block Adress & Location at my Dumps. Allso used the same 1BL-Key in Degraded1.1 than the one at the Infectus Website )

(IMG:http://www.infectus.biz/INFECTUS-BOOK/Tutorial_Eng/Xbox360/Timing_Attack_Infectus/File/Degraded.jpg)

(IMG:http://www.infectus.biz/INFECTUS-BOOK/Tutorial_Eng/Xbox360/Timing_Attack_Infectus/File/Bad_Block_DUMP.jpg)

[majinsoftware]

You dont understand me, That its public knowlage now ms will change it so they re-write secdata a few times so the old one isnt in the nand anymore. And all the people that get banned from say now on will be stuck with out the hdd features since MS has made changes to there banning.

AnimeCommander: Every one who gets banned after they fix the bug will care.

[thwack]

QUOTE(majinsoftware @ Nov 22 2009, 05:36 AM)

Congrats, Thats pretty much the same method as mine.

Just one problem tho. Now that its public knowledge MS will be able to change it.
So you should have waited intill the ban wave had been over for a few weeks.

Right, since you're singling me out for this - you appear to have insider knowledge as to when the ban waves will finish? No-one except MS has details about this, and to be frank this is a very different ban - I suspect it's not a wave, and will re-occur every time people with the none LT ixtreme go online ad-infinitum.

Personally, I think you're piddled off that you can't charge people a fair whack of cash for a hex editing job you claimed to take an hour. It doesn't - if you've already got your NAND dump (and not getting people to email it to you) it takes around 10-15 minutes to check dump, extract table and zero table and insert.

MS may well find a loop hole to plug this in future updates, I'd rather stop people charging an excess of money for a method that was fathomed from a PUBLIC COMMUNITY OF SHARERS and then used for greed. You should have shared from the begining

QUOTE(Ironaxe @ Nov 22 2009, 10:35 AM)

Is a NAND Dump whitch looks like this good enough to keep it safe ( in case something wents wrong ^^ )

Thats the best Dump i got in about 10 tries ( i got 6 of that with exact the same Bad Block and Bad Block Location )

( Found the Picture via Google but got the same Bad Block Adress & Location at my Dumps. Allso used the same 1BL-Key in Degraded1.1 than the one at the Infectus Website )

You should be fine

[Ironaxe]

Soooooo....
All i got to say now is THX
It works like a charm again ( so no big loud dvd player anymore ^^ )

[thwack]

QUOTE(majinsoftware @ Nov 22 2009, 11:11 AM)

You dont understand me, That its public knowlage now ms will change it so they re-write secdata a few times so the old one isnt in the nand anymore. And all the people that get banned from say now on will be stuck with out the hdd features since MS has made changes to there banning.

AnimeCommander: Every one who gets banned after they fix the bug will care.

Again, without this devolving into a slanging match - this ban 'wave' is different - it's a live logging issue that won't go away. You go on live with pre LT ixtreme = ban at some point - they'll keep doing these checks, so your argument is a moot point.

Also it's common knowledge that they will ban you with modified firmware thats out at the minute, so people should be aware not to play backups on or off line at the moment.

Advertising a NAND fix is going to flag up with MS just as much as having a tut to fix your own 360 - MS will pay attention, and then eventually cripple this method, but as Garyopa said, flash memory/eproms/proms/eeproms etc all have a limited lifespan when it comes to re-writing to the same sectors so thay have to produce a fall back otherwise BOOM - dead 360 and it's their fault. Unless you know of a non-degrading chip that they'll chuck out in future revisions of the 360?

[AnimeCommander]

Ok. This is my first time even thinking about the NAND. I've got NandPro reading right (it says it is anyway). I've got a couple questions before I proceed with the second reading, etc. First, what's the -"r16" for? Is it specifying a 16 MB NAND? NandPro says I have a 512 MB NAND. I don't need to run "-r512" and wait the decade, do I? Second, I can't seem to find much information on the errors NandPro gives. This is the first run:

CODE

C:\NandPro20>NandPro lpt: -r16 nand.bin

NandPro v2.0 by Tiros

Testing LPT device address:0378
Using LPT device at address:0378
FlashConfig:00AA3020
512MB Nand Detected
Starting Block:0x000000
Ending   Block:0x0003FF
Press any key to begin reading nand
Error: 250 reading block 1C0
Error: 250 reading block 1C8
Error: 210 reading block 1C9
Error: 210 reading block 1CA
Error: 210 reading block 1CB
Error: 210 reading block 1CC
Error: 210 reading block 1CD
Error: 210 reading block 1CE
Error: 210 reading block 1CF
03FF

C:\NandPro20>

Mainly looking for clarification on the "-r16" bit. Thanks.

EDIT: Nothing seems to be matching up with what I should be seeing when I check the dump. Going to start another while I stop for the night.

This post has been edited by AnimeCommander: Nov 22 2009, 01:04 PM

[thwack]

Animecommander - you should read the whole NAND, ie -r256 or -r512 depending on your NAND version. Over LTP this is going to take you quite some time, so I would recommend the USB route (although it'll cost you to do). Or you coud just leave the the 360 and PC chugging away over LPT by using Grim's Nandpro batch read file here:

http://forums.xbox-scene.com/index.php?showtopic=697023

Those errors look like somthings not quite right with your config - have you used the switching diode? Or possibly it's your PC bios config - try different LPT set ups. If not try another PC (tried sucessfully on a 5 year old ASUS and MSI mobo) You'll get a good dump in the end (IMG:style_emoticons/default/smile.gif)

This post has been edited by thwack: Nov 22 2009, 01:40 PM

[thwack]

Can also now confirm that this restores ALL hard drive funcionality. You can play games and get achievements on a banned 360 offline, install to the HD and have none corrupt profiles/saves. (IMG:style_emoticons/default/smile.gif)

DO NOT go back online with your banned console - this does not unban your 360, it just restores 'trusted content' signing to the console. If you do go back online, you'll get banned again, and have to re-do the flash!

This post has been edited by thwack: Nov 22 2009, 02:01 PM

[danthaman673]

Will this tut and/or FSTOOL (mfc ver) work for a 256mb Jasper?? or is it a different address??

[thwack]

QUOTE(danthaman673 @ Nov 22 2009, 01:42 PM)

Will this tut and/or FSTOOL (mfc ver) work for a 256mb Jasper?? or is it a different address??

Yes, this'll work - haven't tested FSTool yet, but the address is different pretty much on all 360's - you have to find the latest secdata.bin, on the example the Russian example was 0158, for one of the one's I tested it was 11D.

[Omikron199]

I have a question

I've soldered 7 wires, nandpro reads all good but it is taking too long

If I use  "LPT to USB" cable and plug my xbox lpt wire in it, usb - to my pc will the process be faster?

Or it will burn the box or have no changes and be as slow as without the "lpt to usb"

Any help please?

[cjackson]

i ve banned 360 and it has 8955 kernel
if i didn't read wrong, soldering is different from jtag. if it is wrong tell me and i'll do jtag wiring or if it is true show (or give link) about soldering for just reading NAND
and can someone explain what will do after found lastest secdata.bin. What kind of hex editing we need what i ve to change.

[thwack]

QUOTE(Omikron199 @ Nov 22 2009, 01:49 PM)

I have a question

I've soldered 7 wires, nandpro reads all good but it is taking too long

If I use  "LPT to USB" cable and plug my xbox lpt wire in it, usb - to my pc will the process be faster?

Or it will burn the box or have no changes and be as slow as without the "lpt to usb"

Any help please?

Not sure about the LPT to USB cable - give it a go and report back There's a few threads about using the USB dump, although it'll cost a bit more to do it via this method, it dumps much quicker.....

QUOTE(cjackson @ Nov 22 2009, 02:51 PM)

i ve banned 360 and it has 8955 kernel
if i didn't read wrong, soldering is different from jtag. if it is wrong tell me and i'll do jtag wiring or if it is true show (or give link) about soldering for just reading NAND
and can someone explain what will do after found lastest secdata.bin. What kind of hex editing we need what i ve to change.

Read the first page of this thread, you do not need to do the JTAG wiring as you're just dumping the NAND, and you've got a non exploitable kernel (8955).
The hex editing is explained in my post on how to, post no #12 in this thread.