We will be able to make one for $1.00 by next week. Everyone just trying to cash in quickly before the tutorials and firmware comes out. These usb dongles will become "Jailbait", as it will have copyrighted code and Sony's legal team will do something to protect their interests in the coming weeks.

Sony had to release this to boost lagging sales compared to the 360, then they will patch it by Christmas - lol

If this pans out, I will finally get a PS3 and keep it this time and try the PSN online. Now just waiting for the usb dongle to be hacked or cloned -  The Irony!!

I had a jasper like that I had to add the bad blocks manually back into freeboot to match original nand dump bad block locations. Once I did that it booted fine without stalling out on logo with e79. BadBlockRemapper Helper for NandPro v0.1 by Nknave/Krizalid is what I used.

You should just practice on a xenon or falcon first, then step up to a Jasper bb. Jasper BB can be more challenging at times compared to the older smaller block boards, especially if its you first time and have not read enough info on the subject. It will be Cheaper in the long run rather then destroying good Jasper boards.

In Short: You need to get xex menu 1.1 (jtag program for HD1 or usb hd freestyle dash) XEX menu 1.1 is used  from your xbox 360 Hd or freestyle dash xbox live folder to discover and execute xex programs, in your case flash 360 which you will place onto the usb stick. Flash 360 (jtag program) is used to read/write or in your case redump your nand to the same usb stick. Then use xbr to freeboot (Pc program) to convert or rebuild you new freeboot nand. The end result you place your new freeboot 9199 dash back to the usb stick and reflash your console using once again flash 360. However, make sure you first use xell by pressing the eject button to read you fuse lines 3 & 5 to get cpu key as you will need it to rebuild your freeboot nand, if I remember correctly.

Just get those programs and read the readme carefully in each to understand what you are doing. Do two or three dumps and run nand compare to make sure everything is ok. The dumps will only take 10 - 15 seconds super fast read/ write to nand.  With flash 360 Just keep Kv dont have to over write to play it safe.

If you F*&CK it up you will have to wire in usb device or lpt again to reflash the original xbr dump, so make sure you don't ever delete them burn them to a disk  !!!

Sorry it was the nandflasher 360 for windows version 1 by Trancy that uses nandpro. That program may have a serious bug. I was doing everything manually  but got lazy and tried nandflasher 360 but end up being disastrous.  I now only use jtag tool by cool shrimp 1.74 to redump nand and write xell. As I can just use the  read/ write feature via usb without any issues.

Also like to share something else & a warning to others. When I was dealing with that 512 I also came a cross a hazardous buggy program. I was using nandpro20c windows Gui at the time and was taking good dumps and writing back ok when out of nowhere I started to get bad block errors when verifying after write. I thought ok got 5 good dumps but and every time I wrote them back with nandpro20c it did the same thing.

I thought it was my nand and spent 2 days with no luck. I then started to come to a realisation it may be the program and to my horror everytime I opened a clean orig nand it would end up being corrupt. All my good nands were F&*cked up.The only thing that saved my 512 from being a paper weight was that I had one and only good dump in my recycle bin & luckly I didn't use nandpro20c windows GUI. So I deleted that program and just use cool shrimp freeboot program as stated previously.  

This may of only happened to me but thought I should share that if people are currently using it and getting bad block errors & not being able to recover back to stock dash with their original dumps when previously everything was working just fine ..

I would get back to stock dash & only use jtag tool by cool shrimp 1.74 to redump nand and write xell. If that comes up with christmas lights then cb needs to checked again with hex editor or check diodes. When I used 360 dump tool it gave exploitable cb but when checked manually with hex editor the cb was in fact patched.
At 00008400, if it starts with "43 42 1A 5E", this mean that you have an unexploitable jasper and the CB is 6750.
 
The only two programs needed are Jtag tool by cool shrimp 1.74 to write xell and freeboot and 360 flash dump to get cpu key. There should be no problems if soldering and correct positioning of diodes and jumper wires are correct. I still use nand compare to triple check my dumps.

Again repeat solution:
If you have done everything by the book your jasper may not be exploitable. I would double check your cb version via hex editor. I made that mistake only once. What is the manufacture date on the console? After June may have patched 7371 kernel.

If he has the skills and spare board for parts he could replace resistors if that is the issue. I fired a Mt memory chip on a samsung ms 28 years ago replaced it and recovered the key. Lite-on a little different and harder if he has damaged the MT1319L.

Looks like an elaborate water pipe from Amsterdam

You have the latest dash and there is no hope of recovery. look at your pm.

The maximus version 2 spear extractor has fuse to prevent that kind of F*&ck-up. Been there done that!! Check the dash version of console.

Well, If your dash version is above 7371 you just have a nice white dvd player to watch your porn. Did you place the probe in the wrong hole or power molex upside down?

Well, if you have done everything by the book your jasper may not be exploitable. I would double check your cb version via hex editor. I made that mistake only once. What is the manufacture date on the console? After June may have patched 7371 kernel.

HI all,
I received a lite-on 74850c November 2008 drive with custom firmware to update. The drive works fine and has ixtreme 1.5 installed. I first used my maximus spear with  dosflash 32 and got no blue light or response when placed on point R707. I then tried the Mra hack and still no dice. After doing hundreds of drives over the past 4 years this is the first that has caused a problem. The person who flashed it last had R707 bridged with a piece of wire.I tried underneath the board on various R707 points without any luck.

I then did two new 93450c with mra hack and a 74850c with the spear without any issues. What could be the problem?

I didn't want to start a new thread so just posting the question here.

I have seen a few 93850 LiteOn where Liteon have just placed a white sticker over the top of the 83850c original label. So have they just flashed the 83850c board with the newer firmware or just placed a new board in 83850c and just placed a sticker to indicate the change. I have not opened one up to compare as I assume they have done the latter. It was a elite 120gig September system.

cheers

Well if they can now detect the firmware then there are a lot of 360's banned world wide. I will not sign in and will now sell my 360 to someone that won't use live. Looks like a guaranteed ban. I have a few old unstable 360's which I can use for testing. They freeze up after 15 mins. I will mod them and see if they get banned for just logging on & test and confirm if they are detecting firmware.

I would say that a computer would choose randomly throughout a region based on a ratio. They would not ban everyone as it would affect xbox live too much and upset too many people. They just ban enough to scare people and make people think twice about modding a brand new console especially for Christmas. This is Just a way to boost sales of consoles & games out of your misfortune of violating their terms & policies.

For detection they would use many methods to verify a modded console which we will never fully understand.

Solution: one modded Hd & console for backups and one legit console legit Hd & original game for live. End of story.

I think you are too lazy to be speared & probed.