Jump to content

Recommended Posts

Hi Everyone,

I've got a 1.0 with a Hynix with DVD drive that won't eject that came previously TSOP'd. It had an older version of EVOX flashed and then the two TSOP junctions were removed. It unfortunately didn't have the LBA48 configured so thus I wanted to reflash. When I used the BIOS checker I would get Unknown. When I tried to use Flash tools (blastos and evox) I wouldn't get anywhere with flashing as it was unwritable (makes sense)

Today I reapplied the TSOP junctions and when I ran the BIOS Checker I was getting something back - identfying the correct chip and flash. I grabbed the 1mb size version of ind-bios, added a fresh config file to my c drive, started up blastos, and flashed it which seemed to be successful... until the restart. Now the xbox will start, power off, start, power off and then start again with a red/green alternating LED.

Have I ruined my TSOP? Should I have done the 256K? I've got a couple Alladiin's on the way, is this recoverable? I'd appreciate your thoughts and guidance.

Link to post
Share on other sites

Correct. 

BFM  (Bootable From Media) BIOSes do not include the hardware initialization code that is included in non-BFM BIOSes.

Loading a BIOS after intiailization - from media (the hard drive) - doesn't require that code section only the kernel (OS for the Xbox).

 

Edit: The easy fix.  Install a modchip that is always enabled.

  • Like 1
Link to post
Share on other sites
5 hours ago, Edge said:

Thanks for the informative answer KaosEngineer. It was my mistake just seeing the full 1mb size thinking that was the correct bios. I'll install a modchip and get it correctly flashed.

You could try Xblast lite chip from N64 Freak and that should let you reflash the TSOP or swap the TSOP chip from salvage (non working version 1.0-1.1) 

Or you could just leave the mod chip fitted and not worry about fixing the TSOP.

 

Cheers

SS Dave


Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.
 

  • Like 1
Link to post
Share on other sites

Thanks SS_Dave. You tipped me into something with this. It doesn't sound like I'll be able to reflash the TSOP with a Aladdin modchip alone. If I booted and removed the chip, the update would target the LPC port rather than the onboard TSOP, does that sound correct?

Is there any way I can reflash with an Aladdin or is getting an Xblast the next option.

I'm completely fine just using the Aladdin, but it would be great to be able to fix my mistake.

Link to post
Share on other sites
2 hours ago, Edge said:

If I booted and removed the chip, the update would target the LPC port rather than the onboard TSOP, does that sound correct?

No as once the Xbox boots from the LPC that is the only thing it looks at so to flash a TSOP it needs to boot from the TSOP.

 

The easiest is a just use a mod chip as to flash a non working TSOP there is a modded M7 BIOS that needs to boot from a mochip while there is 2 points on the mainboard held to ground and then disconnected from ground in the correct order and time, Thats where a Xblast lite chip helps as it does that for you automatically.

 

Cheers

SS Dave


Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.

 

 

 

  • Like 1
Link to post
Share on other sites
2 hours ago, SS_Dave said:

The easiest is a just use a mod chip as to flash a non working TSOP there is a modded M7 BIOS that needs to boot from a mochip while there is 2 points on the mainboard held to ground and then disconnected from ground in the correct order and time, Thats where a Xblast lite chip helps as it does that for you automatically.

Are you sure? According to the Xblast manual, a partially working TSOP is needed for this method to work.

Quote

To summarize the mechanism, the special BIOS, coupled with a XBlast Lite, will start booting the console from the LPC port, then reset and restart booting from on board TSOP and finally switch back to LPC, mid-boot, to load the kernel of the hacked BIOS. So the feature rely on the fact that the TSOP to recover contains partially valid data to work. If you TSOP is blank or too corrupted, the TSOP recovery feature will not work. Also, if your TSOP is already flashed with a "modern" hacked BIOS (like Evox M8+, X2 5035 or others), there is a strong possibility that this feature will not work, at least with the special BIOS tsop_m7.bin.

I bought an Xblast from N64 Freak a few months ago with the expectation that I could use it fix a board that had a bad copy of iND-BIOS flashed to it. Apparently the "inject config into BIOS" feature of the iND-BIOS configurator tool doesn't work and leads to a corrupt BIOS. I tried and failed to fix the TSOP using an Xblast, then researched it and found out this is the reason why. I just have a cheap Aladdin chip on that board that lives there permanently.

Edited by GoTeamScotch
Link to post
Share on other sites

I'll give it a go and let you know! I'm fairly certain I have good flash ... it just so happens to be the BFM version(ugh... my mistake). I've got my Xblast's on the way, my Aladdin's just arrived. At the worst case the Aladdin will work just fine.

Link to post
Share on other sites

The XBlast works only for some TSOP's and if you have a old bios on it. Something has changed between m7_TSOP and the newer bioses so you can kick the XBLast idea. psyko chewbacca wrote he would try do make a m8_TSOP (if possible) but thats a ~3-4 year old post ( https://www.xbmc4xbox.org.uk/forum/viewtopic.php?t=7081 ) which i have found because of 2 failed TSOP flashes with a faulty m8 bios on Winbonds TSOP's which i have tried to recover with a XBLast and an external programmer (whitout and luck).

 

 

  • Like 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By Landsraat
      Hello.
      I wanted to upgrade RAM on my Xbox. First I TSOPed Cromwell inside and it booted. Then I soldered 4 RAM chips from China and Xbox started reboots and showed errors: Green, Green, Green50%-Red50%. After which I desoldered new RAM, but FRAG was still there.
      I guessed something was wrong with TSOP chip. When I got this Xbox it had some noname modchip from 2003 which I can't even guess clone what of. Anyway, error code switched to: Green, Green, Orange50%-Red50%. Which is RAM error, I guess.
      Now I think I should have tested it with each new RAM chip soldered.
      I only left original 4 RAM chips inside right now, but it still FRAGs.
      What can I do to repair it?
    • By ieblj01
      Hello All,
      Long time listener, first time caller here.   I have never modded an XBOX before, but looks like a fun project and I wanted to run my plan by the gurus on this forum to avoid any potential pitfalls (i.e. destroying the data on the original HDD doing something stupid being a newbie) after watching a ton of YouTube videos on the subject.
      I have an OG XBOX v1.6 that was modded and setup around 6-7 years ago.  The motherboard died and I am looking to swap that drive into a new system and upgrade it to an unlocked SATA HDD (I don't want to have to deal with locked HDDs anymore).  I have no knowledge of how it was built originally aside from the HDD password, but I love how it is laid out and boots up directly in to the emulator menu, etc and want to keep that. 
      There is no evidence of any hard modding on the motherboard (no chip, no bridged soldering, etc), so I am assuming some version of soft mod. 
      I  have two working units (v1.2 & v1.4) and both are currently soft modded with the latest Rocky5 build with stock HDDs.  I did install XMBC-Emustation on one of them, but aside from that, they have nothing special going on with them and I don't need anything off those drives. 
      30K foot view of my plan is as follows:
      1.  TSOP mod one of the working units and flash the BIOS with Evox M8 with F & G (HeXen 2020).
      2.  Take the currently modded HDD (400GB) out of the dead unit and using Victoria, remove the user password.
      3.  Install that HDD in the new TSOP modded unit and test (I assume that since the password is removed from the drive and the BIOS is flashed, it will simply boot even though I have no idea how the HDD was originally prepared).
      4.  Assuming steps 1 - 3 go as planned, convert the TSOP unit to an 80-pin cable and IDE/SATA adapter and clone the HDD to a WD Blue 500GB SATA using Chimp. 
           -Am I correct in that I should pick the TSOP hard mod option in Chimp even though the HDD itself is soft modded?
           -Since my new SATA is bigger than the drive I am cloning, pick option 2 for select partitions and pick option 4 so partition G takes up all the remaining space on the larger drive
      5.  Shut it all down and remove the stock hard drive and install the SATA in the unit and hopefully it all boots up correctly.
      6.  Assuming everything up to this point went well, clone the new SATA drive with Chimp to another WD Blue 500GB (this time I can just pick the full disk clone option)
      7.  TSOP the second working unit and install the cloned drive and have 2 working, upgraded units.
      Let me know your thoughts and if you have any suggestions.  I appreciate the feedback!
       
    • By geohunk
      Hi guys,
       
       So I was given an Xbox 1.0 from a friend that is chipped and has a 120gb HDD. Unfotunately the chip does not have support for HDD larger than 120gb and I am unable to flash the chip's BIOS (evox says it is not flash writeable).
       I'm basically in a bind to find a guide on how to softmod this box and tsop it from a modchip because I don't know what type of chip it is and how to disable it. Pictures below: 
      Apologies for the very dusty MB, lol! As always any guidance will be highly appreciated.
       

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.