Right ive been offered a felcon xbox with a hitchachi 79 with 2.0, whats the chances of playing flashed games? and xpgpaddy's games are 3.0 and the felcon is 2.0? and he said i will get banned going online?
using a flashed console online no matter will always run the chance of getting banned,its just a matter of being smart and lucky lol
the drive is hitachi and he said he'll change the drive to benq or liteon what are the chances of being banned?
the newest firmware is 2.0 for hitachi but it may not be safe Spoiler For those of you out there that like me have an Hitachi 79 inside. You will find that using LT+2.0 as recommended by c4evaSpeaks for you to boot XGD3 backups, you won't be able to play your latest game backups still. A fix is supposedly on its way.... LT+ 2.01 (but for Hitachi 79's only). The thing is I also have a Hitachi 78 drive inside another xbox 360, and this gave me similar errors. This is not yet addressed on c4evaSpeaks and there is no mention of a fix. Thing is, the Hitachi LT+ 2.0 was 'In Testing' for weeks and in development for even longer. As it had been tested for weeks I assumed it would work correctly for all Hitachi's (or that they would at least uncover the problems) but obviously not. Spoiler Hitachi 78/79 LT+ v3.0 IN PROGRESS Hide content Hide version details This version adds support for topology data in place of AP2.5 replay data for all XGD3 and AP2.5-active XGD2 backups. *NOTE: For drives that support AP2.5, all backups containing AP2.5 replay data will need to be patched or re-dumped and re-burned for compatibility with v3.0. iXtreme LT+ v3.0 for Hitachi 78/79 does not support the use of truncated backups, and requires full XGD3 burns made with a compatible Lite-On iHAS drive flashed with the iXtreme Burner MAX fw. In LT+ v3.0, backups remain the same layout, but require new "AP2.5 topology data" in place of the older "AP2.5 replay sector" that was used in LT+ v2.x and older. Burned backups made for v2.x will not work on v3.0, and vice-versa. In the case of v3.0, the firmware would be looking for nonexistent topology data on a backup burned for v2.x. For v2.x, the firmware would be looking for nonexistent AP25 replay data on a backup burned for v3.0. Either way will not work, and will flag your 360 by failing AP2.5 challenges outright. yer i would 100% checking it out more mate