Jump to content

Recommended Posts

Are there any issues/conflicts I need to be aware of when tsoping my xbox? Ive been running a soft mod for a week or so and have a sata 500gb HDD locked with apps, games and of course a dash, XBMC4gamers.

If so I can always put the original HDD in to tsop it that way but then am I good to go with putting the 500gb back and just straight booting? OR, do I need to reinstall everything?


Any specific bios reccomendations? I will be using the drive as well as the HDD and on 1.4 I think. Certainly not 1.6

Edited by Haizum74
Link to post
Share on other sites

EvoX m8+ FG noDVD (Yes, you can still boot any DVD you like even it is named noDVD). If you use a WD Green drive you should disable head parking first.

You should reinstall your HDD using a Installer like OGXBox, HeXEn, Slayers or AID to prevent conflics with the softmod files.

To reinstall your games use XDVDMulleter to extract the ISO and FATXplorer to move them on your pc to the XBox hdd.

Link to post
Share on other sites
1 hour ago, sweetdarkdestiny said:

EvoX m8+ FG noDVD (Yes, you can still boot any DVD you like even it is named noDVD). If you use a WD Green drive you should disable head parking first.

You should reinstall your HDD using a Installer like OGXBox, HeXEn, Slayers or AID to prevent conflics with the softmod files.

To reinstall your games use XDVDMulleter to extract the ISO and FATXplorer to move them on your pc to the XBox hdd.

Thanks for the info, am I right in thinkking the noDVD only tells the xbox not to check for one on boot seeing as those things are becoming somewhat old so the xbox can be booted without one?


I've dl'd the OGxbox installer iso and will give that a go. 

Edited by Haizum74
Link to post
Share on other sites
5 minutes ago, Haizum74 said:

... am I right in thinkking the noDVD only tells the xbox not to check for one on boot seeing as those things are becoming somewhat old so the xbox can be booted without one?

Thats right. But if you have a DVD in your drive and your drive still works, it will boot the DVD.

Link to post
Share on other sites

Bit late doing it but I think I've sorted it. It's a winbond chip so used the EVO 8 F+G noDVD bios for winbond

Now, I expected it to boot with the Evo logo on the top left but it just bootedf with a blue xbox logo. Is that right?

Edited by Haizum74
Link to post
Share on other sites

Depends where you got the BIOS from.

It is is easily edited and the logo/colour and other things changed using the EVTool. Whoever prepared the BIOS just changed the colour - its not important at all if that's what you're worried about.

If you don't like the blue logo then you can use that tool yourself to revert it or even use another logo of your own design.

I would suggest you do not simply because flashing a BIOS, particularly a TSOP, is potentially risky. If its working as it should why risk changing it just for aesthetic reasons?   

 

Link to post
Share on other sites
8 hours ago, Haizum74 said:

Bit late doing it but I think I've sorted it. It's a winbond chip so used the EVO 8 F+G noDVD bios for winbond

Now, I expected it to boot with the Evo logo on the top left but it just bootedf with a blue xbox logo. Is that right?

Thats fine. The 1.0-1.4 bioses I made are blue and the 1.6 bioses are teal. All without logo and without flubber animation.

 

3 hours ago, HDShadow said:

Depends where you got the BIOS from.

From my installer.

Edited by sweetdarkdestiny
  • Like 1
Link to post
Share on other sites
34 minutes ago, Haizum74 said:

Ahhh right. Every vid I have watched of this being done shows a specific green logo, flubber and the Evox logo top left. I thought it hadn't flashed correctly so tried it again and now balked. Damn. 

No thats totaly fine and made to speed up the boot process.

So lets marge the topics and talk further in the last one you made linken below (Maybe a mod could marge them please?).

Link to the other topic : https://www.ogxbox.com/forums/index.php?/topic/4715-another-botched-tsop-job/&tab=comments#comment-30088

  • Like 1
Link to post
Share on other sites

Well, i think you maybe right. Which makes me realy wonder why da hell will this happend now? And why it worked in the first run for you? Damit. I have made no changes at all to any bios so they can't be the problem. I have made no changes to Resctoox.

@SS_DaveDave, Any idea?

I think i have to drop n64_Freak a pm, i need one of the modded aladdins to recover the TSOP.

I have take down all installers.

 

EDIT: Wrote n64 a PM about the XBLast. In case he still has one of them and i have recovered my TSOP, i will give it to you to rescue your TSOP. I will keep in touch with you via PM for that.

Edited by sweetdarkdestiny
Link to post
Share on other sites

 

12 minutes ago, sweetdarkdestiny said:

Well, i think you maybe right. Which makes me realy wonder why da hell will this happend now? And why it worked in the first run for you? Damit. I have made no changes at all to any bios so they can't be the problem. I have made no changes to Resctoox.

@SS_DaveDave, Any idea?

I think i have to drop n64_Freak a pm, i need one of the modded aladdins to recover the TSOP.

I have take down all installers.

I am wondering if it's not some thing else like the power caps near the CPU/power connector.

Especially as he successfully did one flash and it failed on the 2nd flash.

 

Is there any error led flashes?

 

Cheers

SS Dave


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

Link to post
Share on other sites
12 minutes ago, SS_Dave said:

 

I am wondering if it's not some thing else like the power caps near the CPU/power connector.

Especially as he successfully did one flash and it failed on the 2nd flash.

 

Is there any error led flashes?

 

Cheers

SS Dave


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

Nothing on the board and the caps look in good condition too however on boot there is a 'thunk' noise coming from the TV speakers when it tries to boot (might be nothing might be something)  Ill try get a video up later this eve. 

Link to post
Share on other sites

So, i have flashed the same bios with EvoX to a different TSOP. The ST TSOP works fine. Problem is RESCTOOX!

I will investigete further. All images will be down and no download will be possible till i can provide new images and the error is found. The problem is, it worked the first time for you, it worked for eightball and didn't work for me in the first run. That makes it pretty hard to find out whats wrong with resctoox.

I think, the only thing i can do is grab the older version from the HeXEn installer which is different to the latest from the HP.

Edited by sweetdarkdestiny
Removed some typos.
Link to post
Share on other sites

That's worrying news about Resctoox.

I extracted the version I used from an older HeXEn version (2017? I think).

It was used with a Winbond TSOP and I'm pretty sure I reflashed it a second time to customise the logo and Xbox logo colours. No problems in that regard.

The other TSOP I did was a ST done with EvoX.

Could it be Resctoox or a particular version of it does not work with the ST TSOP?

Link to post
Share on other sites
1 hour ago, HDShadow said:

That's worrying news about Resctoox.

I extracted the version I used from an older HeXEn version (2017? I think).

It was used with a Winbond TSOP and I'm pretty sure I reflashed it a second time to customise the logo and Xbox logo colours. No problems in that regard.

The other TSOP I did was a ST done with EvoX.

Could it be Resctoox or a particular version of it does not work with the ST TSOP?

I updated it some version back but eightball has testet them and so I thought they are ok. Now I have made new images (Using the old version of Resctoox) and lucky me, I have a second Winbond XBox here to test until the XBLast from n64 freak will show up to fix the other one.

I have already burned a copy of it and will test it in the next hour (Need some coffee first ;) )

I have borrowed the version for the new images from Hexen 2020 which should work.  If I rember right I have used it to flash my Winbonds in the first run with it.

About your question with the ST TSOP, I have no answer to that. I flash all other TSOP's with EvoX which always worked for me. But as far as I know resctoox should be able to flash all TSOP's like raincoat can do (Below a list of the TSOP's which can be flashed with both of them).  Problem with raincoat is, it only recognize the first 20 (or so) enties in the config, not sure about resctoox. Interesting question would be if you could do the flash with XBlast HDD instead of Resctoox/Raincoat. Maybe Dave has a answer to that.

When I do the Winbond flash I will record a Video and publish it in case it's working. If not I have to wait till the XBLast is here so I can try further.

 

EDIT : What I find is way more strange is, that he flashed the Winbond in the first run without a problem. Mine was dead right a way. Maybe different types winbond?

EDIT2 : Flash done BUT it also killed the TSOP with the Resctoox version from the Hexen 2020 installer. Now i have to wait for the XBlast to test further.

Flash = 0xda45,"Winbond W29C020",0x40000;
Flash = 0xdab5,"Winbond W39L020",0x40000;
Flash = 0xda0b,"Winbond W49F002U",0x40000;
Flash = 0xda8c,"Winbond W49F020",0x40000;
Flash = 0xdab0,"Winbond W49V002A",0x40000;
Flash = 0xda46,"Winbond W29C040",0x40000;
Flash = 0xdab6,"Winbond W39L040",0x80000;
Flash = 0xda3d,"Winbond W39V040A",0x80000;
Flash = 0xb0c9,"Sharp LHF00L02/L06/L07",0x100000
Flash = 0xb0cf,"Sharp LHF00L03/L04/L05",0x100000
Flash = 0x89a2,"Sharp LH28F008SA series",0x100000
Flash = 0x89a6,"Sharp LH28F008SC series",0x100000
Flash = 0xb0ec,"Sharp LH28F008BJxx-PT series",0x100000
Flash = 0xb0ed,"Sharp LH28F008BJxx-PB series",0x100000
Flash = 0xb04b,"Sharp LH28F800BVxx-BTL series",0x100000
Flash = 0xb04c,"Sharp LH28F800BVxx-TV series",0x100000
Flash = 0xb04d,"Sharp LH28F800BVxx-BV series",0x100000
Flash = 0xbf10,"SST 29EE020",0x40000
Flash = 0xbf12,"SST 29LE020/29VE020",0x40000
Flash = 0xbfd6,"SST 39LF020/39VF020",0x40000
Flash = 0xbfb6,"SST 39SF020A",0x40000
Flash = 0xbf57,"SST 49LF002A",0x40000
Flash = 0xbf61,"SST 49LF020",0x40000
Flash = 0xbf52,"SST 49LF020A",0x40000
Flash = 0xbf1b,"SST 49LF003A",0x60000
Flash = 0xbf1c,"SST 49LF030A",0x60000
Flash = 0xbf13,"SST 29SF040",0x80000
Flash = 0xbf14,"SST 29VF040",0x80000
Flash = 0xbfd7,"SST 39LF040/39VF040",0x80000
Flash = 0xbfb7,"SST 39SF040",0x80000
Flash = 0xbf60,"SST 49LF004A/B",0x80000
Flash = 0xbf51,"SST 49LF040",0x80000
Flash = 0xbfd8,"SST 39LF080/39VF080/39VF088",0x100000
Flash = 0xbf5a,"SST 49LF008A",0x100000
Flash = 0xbf5b,"SST 49LF080A",0x100000
Flash = 0x20b0,"ST M29F002T/NT/BT/BNT",0x40000 
Flash = 0x2034,"ST M29F002B/BB",0x40000 
Flash = 0x20d3,"ST M29F200BT",0x40000 
Flash = 0x20d4,"ST M29F200BB",0x40000 
Flash = 0x20e2,"ST M29F040 series",0x80000 
Flash = 0x20d5,"ST M29F400T/BT",0x80000 
Flash = 0x20d6,"ST M29F400B/BB",0x80000 
Flash = 0x20f1,"ST M29F080 series",0x100000 
Flash = 0x20ec,"ST M29F800DT",0x100000 
Flash = 0x2058,"ST M29F800DB",0x100000
Flash = 0x01b0,"AMD Am29F002BT/NBT",0x40000
Flash = 0x0134,"AMD Am29F002BB/NBB",0x40000
Flash = 0x0151,"AMD Am29F200BT",0x40000
Flash = 0x0157,"AMD Am29F200BB",0x40000
Flash = 0x0140,"AMD Am29LV002BT",0x40000
Flash = 0x01c2,"AMD Am29LV002BB",0x40000
Flash = 0x013b,"AMD Am29LV200BT",0x40000
Flash = 0x01bf,"AMD Am29LV200BB",0x40000
Flash = 0x010c,"AMD Am29DL400BT",0x80000
Flash = 0x010f,"AMD Am29DL400BB",0x80000
Flash = 0x0177,"AMD Am29F004BT",0x80000
Flash = 0x017b,"AMD Am29F004BB",0x80000
Flash = 0x01a4,"AMD Am29F040B",0x80000
Flash = 0x0123,"AMD Am29F400BT",0x80000
Flash = 0x01ab,"AMD Am29F400BB",0x80000
Flash = 0x01b5,"AMD Am29LV004BT",0x80000
Flash = 0x01b6,"AMD Am29LV004BB",0x80000
Flash = 0x014f,"AMD Am29LV040B",0x80000
Flash = 0x01b9,"AMD Am29LV400BT",0x80000
Flash = 0x01ba,"AMD Am29LV400BB",0x80000
Flash = 0x014a,"AMD Am29DL800BT",0x100000
Flash = 0x01cb,"AMD Am29DL800BB",0x100000
Flash = 0x01d5,"AMD Am29F080B",0x100000
Flash = 0x01d6,"AMD Am29F800BT",0x100000
Flash = 0x0158,"AMD Am29F800BB",0x100000
Flash = 0x013e,"AMD Am29LV008BT",0x100000
Flash = 0x0137,"AMD Am29LV008BB",0x100000
Flash = 0x0138,"AMD Am29LV080B",0x100000
Flash = 0x01da,"AMD Am29LV800BT/DT",0x100000
Flash = 0x015b,"AMD Am29LV800BB/DB",0x100000
Flash = 0x378c,"AMIC A29002T/290021T",0x40000
Flash = 0x370d,"AMIC A29002U/290021U",0x40000
Flash = 0x3786,"AMIC A29040A",0x80000
Flash = 0x37b0,"AMIC A29400T/294001T",0x80000
Flash = 0x3731,"AMIC A29400U/294001U",0x80000
Flash = 0x3734,"AMIC A29L004T/A29L400T",0x80000
Flash = 0x37b5,"AMIC A29L004U/A29L400U",0x80000
Flash = 0x3792,"AMIC A29L040",0x80000
Flash = 0x370e,"AMIC A29800T",0x100000
Flash = 0x378f,"AMIC A29800U",0x100000
Flash = 0x371a,"AMIC A29L008T/A29L800T",0x100000
Flash = 0x379b,"AMIC A29L008U/A29L800U",0x100000
Flash = 0x04b0,"Fujitsu MBM29F002TC",0x40000
Flash = 0x0434,"Fujitsu MBM29F002BC",0x40000
Flash = 0x0451,"Fujitsu MBM29F200TC",0x40000
Flash = 0x0457,"Fujitsu MBM29F200BC",0x40000
Flash = 0x0440,"Fujitsu MBM29LV002TC",0x40000
Flash = 0x04c2,"Fujitsu MBM29LV002BC",0x40000
Flash = 0x043b,"Fujitsu MBM29LV200TC",0x40000
Flash = 0x04bf,"Fujitsu MBM29LV200BC",0x40000
Flash = 0x040c,"Fujitsu MBM29DL400TC",0x80000
Flash = 0x040f,"Fujitsu MBM29DL400BC",0x80000
Flash = 0x0477,"Fujitsu MBM29F004TC",0x80000
Flash = 0x047b,"Fujitsu MBM29F004BC",0x80000
Flash = 0x04a4,"Fujitsu MBM29F040C",0x80000
Flash = 0x0423,"Fujitsu MBM29F400TC",0x80000
Flash = 0x04ab,"Fujitsu MBM29F400BC",0x80000
Flash = 0x04b5,"Fujitsu MBM29LV004TC",0x80000
Flash = 0x04b6,"Fujitsu MBM29LV004BC",0x80000
Flash = 0x04b9,"Fujitsu MBM29LV400TC",0x80000
Flash = 0x04ba,"Fujitsu MBM29LV400BC",0x80000
Flash = 0x044a,"Fujitsu MBM29DL800TA",0x100000
Flash = 0x04cb,"Fujitsu MBM29DL800BA",0x100000
Flash = 0x04d5,"Fujitsu MBM29F080A",0x100000
Flash = 0x04d6,"Fujitsu MBM29F800TA",0x100000
Flash = 0x0458,"Fujitsu MBM29F800BA",0x100000
Flash = 0x043e,"Fujitsu MBM29LV008TA",0x100000
Flash = 0x0437,"Fujitsu MBM29LV008BA",0x100000
Flash = 0x0438,"Fujitsu MBM29LV080A",0x100000
Flash = 0x04da,"Fujitsu MBM29LV800TA/TE",0x100000
Flash = 0x045b,"Fujitsu MBM29LV800BA/BE",0x100000
Flash = 0xadb0,"Hynix HY29F002",0x40000 
Flash = 0xada4,"Hynix HY29F040A",0x80000
Flash = 0xad23,"Hynix HY29F400T/AT",0x80000
Flash = 0xadab,"Hynix HY29F400B/AB",0x80000
Flash = 0xadb9,"Hynix HY29LV400T",0x80000
Flash = 0xadba,"Hynix HY29LV400B",0x80000
Flash = 0xadd5,"Hynix HY29F080",0x100000 
Flash = 0xadd6,"Hynix HY29F800T/AT",0x100000
Flash = 0xad58,"Hynix HY29F800B/AB",0x100000
Flash = 0xadda,"Hynix HY29LV800T",0x100000
Flash = 0xad5b,"Hynix HY29LV800B",0x100000
Flash = 0xc2b0,"Macronix MX29F002T/NT",0x40000
Flash = 0xc234,"Macronix MX29F002B/NB",0x40000
Flash = 0xc236,"Macronix MX29F022T/NT",0x40000
Flash = 0xc237,"Macronix MX29F022B/NB",0x40000
Flash = 0xc251,"Macronix MX29F200T",0x40000
Flash = 0xc257,"Macronix MX29F200B",0x40000
Flash = 0xc245,"Macronix MX29F004T",0x80000
Flash = 0xc246,"Macronix MX29F004B",0x80000
Flash = 0xc2a4,"Macronix MX29F040",0x80000
Flash = 0xc223,"Macronix MX29F400T",0x80000
Flash = 0xc2ab,"Macronix MX29F400B",0x80000
Flash = 0xc2b5,"Macronix MX29LV004T",0x80000
Flash = 0xc2b6,"Macronix MX29LV004B",0x80000
Flash = 0xc24f,"Macronix MX29LV040",0x80000
Flash = 0xc2b9,"Macronix MX29LV400T",0x80000
Flash = 0xc2ba,"Macronix MX29LV400B",0x80000
Flash = 0xc2d5,"Macronix MX29F080",0x100000
Flash = 0xc2d6,"Macronix MX29F800T",0x100000
Flash = 0xc258,"Macronix MX29F800B",0x100000
Flash = 0xc23e,"Macronix MX29LV008T",0x100000
Flash = 0xc237,"Macronix MX29LV008B",0x100000
Flash = 0xc238,"Macronix MX29LV081",0x100000
Flash = 0xc2da,"Macronix MX29LV800T",0x100000
Flash = 0xc25b,"Macronix MX29LV800B",0x100000

 

Edited by sweetdarkdestiny
Link to post
Share on other sites
7 hours ago, Haizum74 said:

Hmm, interesting.  I wonder if it's a winbond thing then?

I will not say can't be but some how, it seems to " 50%/50% " This is what a user reportet yesterday.

11 hours ago, chrisf said:

I was just abuot to post about this - not sure if the same problem  -

flashing a winbond chip 1.4 xbox with the IND BIOS doesnt work

I tested a few versions of the bios and instead of creating c:\bios\bios.bin   it creates a folder called bios.bin  so there is no file to flash 

flashing an m8 bios worked fine 


I did the only thing which i could to atm and took down the images to prevent any thing happen to other users. Right decision i think.  What makes me wonder is why the Resctoox version from Hexen 2020 also failed.

And i wrote it in the OGXBox topic already, i will redo the biosfiles, even they work when flashed with EvoX (What makes me wonder even more!) and i will make the Resctoox configs new.

And till the XBLast comes to reanimate the WInbond TSOPs, I can't do anything more. So i think the Images will stay offline for at least 1-2 weeks.

For to all other who maybe read this, if you don't flash a winbond TSOP the installer works fine.

 

EDIT : I googled a little bit and found out that you could also use XBLastOS to flash the Winbond and Sharp TSOPs. SO I'm going to drop Resctoox for the next build and let XBLastOS do the job. (

Edited by sweetdarkdestiny
Link to post
Share on other sites

I got  two Winbond TSOP xbox. Should I try the same bios on them? I got pin headers intalled on them in case TSOP fails and I will snap in a modchip. That way we will know for sure. 

But the Xblast TSOP recovery does not work on a 256kb TSOP that has a EVOX M8  or Xecuter bios fragged on them.  The  M7_TSOP bios simply will not boot the to TSOP to run the DVD. I tried it many times. Please share the method if you succeed.

Link to post
Share on other sites
2 minutes ago, Raja said:

I got  two Winbond TSOP xbox. Should I try the same bios on them? I got pin headers intalled on them in case TSOP fails and I will snap in a modchip. That way we will know for sure. 

But the Xblast TSOP recovery does not work on a 256kb TSOP that has a EVOX M8  or Xecuter bios fragged on them.  The  M7_TSOP bios simply will not boot the to TSOP to run the DVD. I tried it many times. Please share the method if you succeed.

PLEASE NO! DON'T DO THAT!

I'm right now coding a new flash xml for the winbond using XBLastOS.

When thats done I can drop you a link with a Beta to test them if you like.

I have tried it yesterday with an XCharger 2.5 and with a SmartXX v2 but both dosn't support XBlastOS.

So right now i can't do anything until the XBLast ModChip comes to Flash the broken Winbonds. Hope n64 freak get the money today but they will probably not show of here till Wednesday or Thursday.  And if all fails to recover the Winbond, I have to more options. Got some 27C2001 and 27C020 this morning for cheap. That way I could try the 29 wire recover method .If that fails as well, I will unsolder the Winbonds and flash them with a flasher and resolder them.

The one way or the other I will bring them back to life.

Link to post
Share on other sites
9 hours ago, sweetdarkdestiny said:

XBLastOS

 

On 1/21/2021 at 6:48 AM, sweetdarkdestiny said:

So, i have flashed the same bios with EvoX to a different TSOP. The ST TSOP works fine. Problem is RESCTOOX!

I will investigete further. All images will be down and no download will be possible till i can provide new images and the error is found. The problem is, it worked the first time for you, it worked for eightball and didn't work for me in the first run. That makes it pretty hard to find out whats wrong with resctoox.

I think, the only thing i can do is grab the older version from the HeXEn installer which is different to the latest from the HP.

Is the winbond chip only on a 1.4 or can it be any version? Just wondering if it's a specific xbox version that can cause it or if it's potentially widespread. 

Link to post
Share on other sites

It was

16 minutes ago, Haizum74 said:

 

Is the winbond chip only on a 1.4 or can it be any version? Just wondering if it's a specific xbox version that can cause it or if it's potentially widespread. 

One 1.4 and one 1.2.. I have send Raja a beta version of the new build with the new config. I use XBlast now and see what Raja will tell about the Beta version. If they is ok, i will write a new config for the Sharp flasher and new images will come soon. If the beta fails, not to sure what i do then. MAybe i provide a last copy without the option to flash winbond & Sharp TSOPs for all of who don't need it. But we will see. I will also do testing but sadly i can do test with a sharp TSOP because i don't have a XBox with that kind of TSOP. So, In case Raja reports it working 100% i would appreciate if someone with a XBLast and Sharp TSOP on hand would drop me a PM to test the config. Or in case some lives in germany and has a Sharp XBox up for sale drop me a PM as well. So atm we all have to wait.

I will also do some testing with the original HeXEn to see if they cause problems because yesterday i flashed with the HeXEn version and failed. But the bios i used worked fine with a ST TSOP.

So maybe Heimdall could give me some feedback, in case he read this, because we maybe would both profit from the results which I would share with him and ofc you guys when I'm done with testing.

So yeah for now ìm out and wait for Raja to tell me whats his results. 

And if anyone ask's, i will keep a copy of Resctoox one the image to install it ( I will grab a copy of the Heimdall HeXEn for that because I´m pretty sure I flashed both of my Winbonds with his Image in the first run (2018 or 2019 vesion I guess, not to sure about that)), like i have made with raincoat but, if the results are good, I switch to XBlast OS to flash winbond and sharp TSOP's.

And some offtopic. Did you guys know, that english is the only language where you write "I" (German "ich") as a capital letter/word? I think i will never learn that. :D ;)

  • Like 1
Link to post
Share on other sites
38 minutes ago, sweetdarkdestiny said:

It was

One 1.4 and one 1.2.. I have send Raja a beta version of the new build with the new config. I use XBlast now and see what Raja will tell about the Beta version. If they is ok, i will write a new config for the Sharp flasher and new images will come soon. If the beta fails, not to sure what i do then. MAybe i provide a last copy without the option to flash winbond & Sharp TSOPs for all of who don't need it. But we will see. I will also do testing but sadly i can do test with a sharp TSOP because i don't have a XBox with that kind of TSOP. So, In case Raja reports it working 100% i would appreciate if someone with a XBLast and Sharp TSOP on hand would drop me a PM to test the config. Or in case some lives in germany and has a Sharp XBox up for sale drop me a PM as well. So atm we all have to wait.

I will also do some testing with the original HeXEn to see if they cause problems because yesterday i flashed with the HeXEn version and failed. But the bios i used worked fine with a ST TSOP.

So maybe Heimdall could give me some feedback, in case he read this, because we maybe would both profit from the results which I would share with him and ofc you guys when I'm done with testing.

So yeah for now ìm out and wait for Raja to tell me whats his results. 

And if anyone ask's, i will keep a copy of Resctoox one the image to install it ( I will grab a copy of the Heimdall HeXEn for that because I´m pretty sure I flashed both of my Winbonds with his Image in the first run (2018 or 2019 vesion I guess, not to sure about that)), like i have made with raincoat but, if the results are good, I switch to XBlast OS to flash winbond and sharp TSOP's.

And some offtopic. Did you guys know, that english is the only language where you write "I" (German "ich") as a capital letter/word? I think i will never learn that. :D;)

Mine is a 1.4 that failed. I've just secured another and going to pick up the xbox tomorrow morning. 

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 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.
       

    • By Edge
      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.

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.