|
1
|
Xbox 360 / Tech Support 360 / Re: XD Card Mod Questions [Slim]
|
on: May 05, 2012, 01:09:22 PM
|
shouldn't u cut the top smc line? From what iLLNESS says here. http://www.xboxhacker.org/index.php?topic=16997.msg127795#msg127795the CE line from the original nand does go both ways from the nand itself. i had the resistor on bottomside removed which wasnt sufficient as the bottom nand was still connected directly to sb ce. so, now ive done the trace cut and all is well with both resistors  thanks I am trying to figure out why u cut the trace when u could of removed the resister for what ur doing. Also by not cutting the top CE like to the SB ur original nand would always turn on right? with the 360 slim, removing the resistor just disables it from being pulled up. the nand is still connected to the southbridge so there is no way to isolate it. if you look at the nand CE pin it actually has two traces coming off of it. the nand ce pin connects to the southbridge on a trace that goes under the nand, then the trace that you can see coming off the pin is just the pullup. so, you can either lift the pin of the nand or cut the trace mentioned in the picture to isolate it from the southbridge. if you lift the pin though you will need to pull up the pin with the 10k ohm resistor or solder it to the trace again and cut the trace as well. there is many ways to do it but quite simply the easiest way is what is shown in the picture if you have the skills to solder to the trace. sorry and by picture i mean this one:  |
|
|
|
|
2
|
Xbox 360 / Tech Support 360 / Re: RGH CPLD DualNAND Mod v0.5.1 Trinity issues
|
on: April 28, 2012, 02:10:17 PM
|
So I decided to get rid of my ugly switch last night and start migrating over to the CPLD dual nand method. I'm using the seeedstudio board but have run into some problems. Basically, the NAND switching doesn't seem to work at all. Checking voltages the installation seems correct. When I press sync the voltage on the pin drops but thats it. The SMC doesnt reset, the nands dont switch. To verify, these are my board schematics:  according to the generic cpld diagram provided in the package http://dwl.modcontrol.com/XBOX360/nand_xell_freeboot/RGH%20CPLD%20DualNAND%20Mod/rgh_cpld_dualNAND_mod_v0.5.1.rar the pins being used do not have anything in between to affect the board. using the breakout pins on the board are no different then using the pins on the chip themselves like in the TX Coolrunner. The console boots to the retail nand fine but thats it. So the retail nand pin CE control is working. If the xsvf file didn't take both pins would be held low and the console wouldn't boot at all. Anyone have experience with this? I don't really want to scrap this seeedstudio board and drop a coolrunner in if i dont have to. UPDATE: FIXED. was the status wire after all. weird though considering i've seen 'working' installs without it?? |
|
|
|
|
3
|
Xbox 360 / Tech Support 360 / Re: RGH CPLD DualNAND Mod v0.5.1 Trinity issues
|
on: April 28, 2012, 12:53:32 PM
|
|
i said screw it and installed the tx coolrunner but i have the same results as with the other board.
the CE line from southbridge is cut (not connected to either nand), both nand CE's are pulled up with a 10k resistor, smc reset is connected directly, the sync button is pulled up with a 10k and wired correctly (tested voltages, voltage drops on the pin when sync is pressed when console is in standby).
when sync is pressed, there is no voltage change on SMC reset, the voltages don't change at all on the CEs (orig nand is low, second nand remains high).
i have not installed the status wire though. is this my problem? as far as I know it's for the LED's but i may be wrong?
UPDATE: FIXED. was the status wire after all. weird though considering i've seen 'working' installs without it??
|
|
|
|
|
4
|
Xbox 360 / Tech Support 360 / RGH CPLD DualNAND Mod v0.5.1 Trinity issues
|
on: April 28, 2012, 11:03:34 AM
|
So I decided to get rid of my ugly switch last night and start migrating over to the CPLD dual nand method. I'm using the seeedstudio board but have run into some problems. Basically, the NAND switching doesn't seem to work at all. Checking voltages the installation seems correct. When I press sync the voltage on the pin drops but thats it. The SMC doesnt reset, the nands dont switch. To verify, these are my board schematics: according to the generic cpld diagram provided in the package http://dwl.modcontrol.com/XBOX360/nand_xell_freeboot/RGH%20CPLD%20DualNAND%20Mod/rgh_cpld_dualNAND_mod_v0.5.1.rar the pins being used do not have anything in between to affect the board. using the breakout pins on the board are no different then using the pins on the chip themselves like in the TX Coolrunner. The console boots to the retail nand fine but thats it. So the retail nand pin CE control is working. If the xsvf file didn't take both pins would be held low and the console wouldn't boot at all. Anyone have experience with this? I don't really want to scrap this seeedstudio board and drop a coolrunner in if i dont have to. |
|
|
|
|
5
|
Xbox 360 / Xbox 360 "Modding" / Re: Dual NAND No trace Cuts/ Pads Lifted Method
|
on: April 22, 2012, 03:35:35 PM
|
|
what are you saving this way??? you're not cutting traces but you're still lifting pins which is riskier.
if you dont want to cut traces, just lift both nand CE pins and wire them accordingly to the pullup/gnd but again cutting the trace is still likely a much cleaner and better thing to do. messing with the VCC of the chip isn't needed.
|
|
|
|
|
6
|
Xbox 360 / Tech Support 360 / Re: jasper BB with 6751 cb problems + possible solutions
|
on: January 23, 2012, 02:56:30 PM
|
Jasper BB consoles with 6751 CB do have issues. I can confirm. In the last month I have glitched about 30 Jaspers now, all using Xecuter Coolrunners /w their cap and the same wire path. Nearly every single console boots within 5s EXCEPT for 3 6751CB Jasper BB consoles. These consoles do not boot at all.
What will happen is I will build an ecc normally using 360 Multi Builder, and after wiring everything up in the same way as normal, these consoles do not boot. The green light will blink as if it is attempting to glitch, and eventually it will stop blinking (as if it did glitch) but xell never shows. If I remove the cap, itll blink more times (as if its attempting to glitch and its taking longer) and will eventually stop blinking but will never show xell. Changing my wiring path seems to have no effect except for sometimes making the green light blink a few more times, which is expected.
This is not just for 512MB jaspers, the problem exists in 256MB also. It also doesnt happen to all 6751CB BigBlock Jaspers, only about a quarter of them. I don't have enough technical knowledge to understand how to fix or work on something like this, but I do have consoles with the issue to test solutions etc...
To me, it looks like these consoles are glitching, but xell just isnt showing up, and I don't understand why ~_~
i have seen a 512 jasper do this as well. have yet to find a solution. console appears to glitch normally, stops like a successful glitch but nothing on screen. also was 6751. i cant remember what the post showed but i believe it was an undocumented code or a code that shouldnt even appear (kernel related). |
|
|
|
|
7
|
Xbox 360 / Tech Support 360 / Re: RGH slim weird problem
|
on: December 23, 2011, 03:05:13 PM
|
|
not supposed to boot retail with glitcher.. the glitcher is still glitching and as you can imagine retail dash doesnt necessarily like that.
you need to disable the glitcher when boooting retail dash for best/safe results.
|
|
|
|
|
8
|
Xbox 360 / Tech Support 360 / Re: USB SPI Flasher with PIC18F2455 - now with source and binaries
|
on: December 21, 2011, 09:43:33 PM
|
|
ive written some modifications to the picflash code to suite my preferences but i need it to work with usb hid.
in the usb_config.h ive commented out the mchpusb bootloader and uncommented the usb hid bootloader #defines.
after compiling/etc though, the reset vector start address is STILL 0x800.
anyone here got any ideas?
to answer my own issue thanks to cory, the linker script needs to be changed to have codepage start at 0x001000 (tried that), as well, FILES c018i.o needs to be changed to hid_c018i.o, and the hid_c018i.c needs to be compiled to an output file, as well #define the usbhid bootloader.
after these obvious steps (lol) it is now working.
|
|
|
|
|
9
|
Xbox 360 / Tech Support 360 / Re: 16D4S DC Motor
|
on: December 19, 2011, 01:39:18 AM
|
Replace the pcb, don't waste your time on a dead board, even replacing the Mediatek 1335 won't cut it. You will be able to dump it even full dump, write firmware to it, but the trace inside the chip that signals power to the motor is cutted, customer is lying, plain and simple
if the trace is broken in the 1335, why wouldnt replacing the chip work? tx pro kits are like $20. it would be the cheapest solution. |
|
|
|
|
10
|
Xbox 360 / Tech Support 360 / Re: 14699 glitch update
|
on: December 13, 2011, 01:00:06 PM
|
you can use your original nandump it dosent matter since LDV did NOT change
by the way are you from ISR?
you mean, you cant use your original nanddump unless you change LDV since LDV did change? |
|
|
|
|
11
|
Xbox 360 / XboxHacking - General / Re: A new revision of the Slim, no more Glitch?
|
on: December 10, 2011, 06:17:31 PM
|
I am a bit confused here.....I was just about to crack open this slim with date code 2011-06-16 when I noticed the PSU rating of 9.6A on the same tag....I thought any date code before AUG was fine?....WTF
Confirmed has no HANA ship, tried to attach pic but won't let me
in brazil i think there were coronas out before august. the august thing i believe is for sure north america (not sure about europe, etc). |
|
|
|
|
13
|
Xbox 360 / Tech Support 360 / Re: 360 Slim Dual Nand Only Loading Xell After 13604 XBL Update...
|
on: December 07, 2011, 01:26:43 PM
|
|
i havent tested it quite yet, but new dash requires LDV increase (rolled out last night) if you want to dual boot 13604 with latest dash that came out (same issue as OP)
or as i mentioned, you can just dump the new dash nand after last nights update and rebuild with rgbuild to fix.
again,i havent confirmed as i didn't have time this morning but i was also only able to boot to xell and retail dash, not my ggbuild dash i built when 13604 came out.
|
|
|
|
|
16
|
Xbox 360 / XboxHacking - General / Re: A new revision of the Slim, no more Glitch?
|
on: November 26, 2011, 10:38:35 AM
|
Haha, just noticed one of the Forza4 videos is actually called - dolby_corona. Its strange though why MS released a new revision when the rumors about x720 devkits are coming out everyday, i mean if they develop a new console they should be focusing on it 100%.
dont forget ms still plans on selling the 360 afterwards. |
|
|
|
|
17
|
Research & Technical XboxHacking (Xbox 360) / Software (TECHNICAL) / Re: Dual boot (RGH/original for live) different Content folder name.
|
on: November 10, 2011, 04:29:56 PM
|
|
sure it might be 'safe' now... but what happens when a new dash or even just a random game starts scanning hdd contents looking for files logging to the hard drive itself? will you know?
best approach is to have two hard drives.. with the rgh drive not being an official 360 drive (aka, no hdss.bin flashed etc). this way atleast the stock dash by default cant accidentally pull data from the rgh hard drive unless again ms pulls a trick and decides to scan this drive despite not being shown as legit.
worst case with this scenario is your official 'live' drive gets left in while booting rgh and you save a game or it logs some data or something.
|
|
|
|
|
18
|
Xbox 360 / Tech Support 360 / Re: Help with programming coolrunner with nand-x
|
on: November 05, 2011, 01:16:59 AM
|
Do you have falcon.xsvf in the current directory?  I downloaded an already convereted falcon.sxvf file and placed it in the root directory of the nandpro30 folder (nandpro v3), no idea why it isn't working as my wiring looks good and the nand-x is running the latest nandpro 3. probably because your not in the nandpro directory? |
|
|
|
|
20
|
Research & Technical XboxHacking (Xbox 360) / Software (TECHNICAL) / Re: Changing osig (dvd rom) drive reset glitch?
|
on: October 31, 2011, 07:20:22 AM
|
if you want to change OSIG for a reset glitched console you need to edit it with a hex editor. i dont believe there are any tools that will do it without breaking the KV. in hex editor look for something along the lines of this in your decrypted KV.bin: OSIG.......2o...HL-DT-STDVD-ROM DL10N 0500p1(
4F53494700010104058000326F000000484C2D44542D53544456442D524F4D20444C31304E20202030353030703128A4
or:
OSIG.......2[...PLDS DG-16D4S 0225p1&.
4F53494700010103058000325B000000504C44532020202044472D3136443453202020202020202030323235703126AC
i used OSIG as a reference point for copying/pasting in this case. basically, you can change the DVD key fine, but touching the OSIG in a KV editor/360 flash tool will break the KV and your console will not boot (in my experience). patch your OSIG, save the decrypted KV and build your image using this KV. |
|
|
|
|
Show Posts
