Bowlsnapper
-
Posts
4,262 -
Joined
-
Last visited
-
Days Won
110
Content Type
Profiles
Forums
Calendar
Store
Posts posted by Bowlsnapper
-
-
33 minutes ago, joshua_1543 said:
it is stock, i dont know much about og xboxes so sorry about the little info
Don't trip. Check my edited post!
Thanks for the info. I'll research a bit. I'm sure dave or kaos will drop some wisdom shortly.
..That pic IS disturbing though. NO xbox motherboard should look that stock in 2022. I look at it and I just wanna' fuckin' solder shit to it.
-
1 hour ago, joshua_1543 said:
Uh, you may wanna shoot us a bit more info there, player. That is one clean-ass pic of a disturbingly unmodified xbox. I do NOT disagree! But can you throw us a bone? Is it tsop flashed or totally stock?
Edit: i'm a jackass. My browser jumped to your last post and i thought that was the opener. I'm a tool.
Yes, other side too, please. Also, it looks like the clock cap has leaked a bit.
-
57 minutes ago, alfredo2 said:
Yeh lol, it was in the same container as the first water damaged console.
That's crazy how the both had the same issue and literally no others. I would be pretty grateful for that!
-
1 hour ago, KaosEngineer said:
What dot xbe files and their sizes are in the top-level/root folder of the C and E drives?
In c - xboxdash.xbe 1.9mb, evoxdash.xbe 752kb.
In e - evoxdash.xbe 2.9mb.
-
4 minutes ago, SS_Dave said:
I tested that with 2 different Xbox's (1.6 and 1.1) and it did the same when booting direct to the dash and not loading the X3 menu 1st and the clock gets scrambled every time but not with the X2 or Ind on the 1.1, The 1.6 gets reset to 1/1/1900 on the Evox dash and 1/1/2000 in the M$ dash every time you power cycle it.
It made no difference if the clock as set via the net then unplug the network cable and power cycle then the clock was scrambled or the clock setting in the M$ dash it did the same.
When I get bit more time I will test the older versions of X3 bios.
Cheers
SS Dave
Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.I moved this topic and replied here:
-
I'm moving this topic from:
I would do it in a more polished fashion, but I'm not a moderator and don't have the means to do so.
-----------------------------------------------------------------
Post 1: In response to what dash I was using.
Old ass xbmc 1.1 dude. I actually want to change to evox or maybe xbmc 3.5.3 but I don't know what the previous owner did for the installation on this particular box and i don't want to de-stabilize anything. The dash boots from a mounted (I'm assuming it's mounted) q: partition. X3cl is configured to boot the dash from f:, but the only files present in the root directory are evoxdash.xbe.old and evox.ini... What the fuck? How is this thing even booting? What the hell is going on?
I would just do a clean install but i won't have direct pc access for another month or so, so i can't back up. I do have slayer 2.7 and ogxbox 2021 discs. Can i pull it off with those?... Assuming that's even enough info for you to assess the situation!
Post 2: Basically, when asked to clarify and provide more details.
Kaos, the two files I listed (an .ini and an .old) are literally the only 2 files in the root of f:. There are no valid executables there so i have no idea what the x3 is booting to get me into xbmc. That's my main point of confusion - If the X3 is set to boot the dash from the root of F: and there's no dash executable located there, then how the FUCK is my Xbox booting at all? How can my bios launch a dashboard (the XBMC 1.1.0 I mentioned) that, by all available and tangible evidence, doesn't fucking exist? but it loads, so obviously it exists somewhere) but can't even load a I'll check the logs. The dash priority list in configlive is the default list. When I change to boot from E: a bare unleashx loads with no menu entries (games and emulators are empty) and is useless except for the file browser. Booting from c partition results in a boot loop, even though there is an evoxdash.xbe in the root, which I'm assuming was created as an old shortcut because there are no resource files/folders and trying to load it manually results in a dash restart... This thing reminds me of the house from poltergeist - full of randomness and wormholes and shit.
Dave, thank you for confirming. Is it possible that the bios is just resetting the time every time I try to set it with the dash?
Edit: Oh for fuck's sake. I can't open the .log file in unleashx because q: is only present when xbmc is running. And when I try to copy the log file from q: to any other partition so I can view it in unleash, xbmc just refuses to do it. For the life of me, I can NOT find the folder that is being mounted to q:, either. My xbox is a fucking sociopath.
What the CHRIST?
Edit 2: i found softmod install files in udata and some evox dash files in a subfolder of 41560017. So this thing was softmodded at some point in its life. No wonder it's such a mess. Still can't find the real q: directory...
Edit 3: I'm able to get UnleashX to boot if I copy the files from the slayer's 2.7 disc to, say, the root of E:. But if I try to get EvolutionX to run by copying files from the same method, it fails to load and triggers a bios default-dash restart. Does the Evox dash have to be run/setup/installed a certain way, or something? I'm able to load any other dash like Avalaunch or XBMC 3.5.3 (if run as an application from a default.xbe). EvolutionX seems to be really touchy in that respect. Ironically, I was able to get the Evox menu from OGXbox (or slayer's, I can't remember now) actual installer to run from the root of E:, but not the one from the Dashes folder of Slayers. Wow. That makes no sense to me.
-----------------------------------------------------
SS_Dave's responses to my time issue:
-I tested this with a X3cp with the X3 bios and yes the date gets scrambled on each boot where the X2-5035 and Ind 5004 bios didn't reset the date/time
I haven't noticed it before as my Xbox's are connected to the home network and the date/time is set automatically.
-I tested that with 2 different Xbox's (1.6 and 1.1) and it did the same when booting direct to the dash and not loading the X3 menu 1st and the clock gets scrambled every time but not with the X2 or Ind on the 1.1, The 1.6 gets reset to 1/1/1900 on the Evox dash and 1/1/2000 in the M$ dash every time you power cycle it.
It made no difference if the clock as set via the net then unplug the network cable and power cycle then the clock was scrambled or the clock setting in the M$ dash it did the same.
When I get bit more time I will test the older versions of X3 bios.
My Reply:
So my problem is reproducing when you mimic my setup? Glad to know it's not just me. Definitely let me know when you get some time and are able to experiment further. I appreciate it, buddy. Do you have any insight into my dashboard clusterfuck, by chance? I'd appreciate your input on that, if you don't mind.
-
6 hours ago, alfredo2 said:
Thanks for your help.
I booted it up, everything seems to be in working order, the fan is dead though so I will have to see what I can do about that.
Damn. It's a dead-fan epidemic for you, huh? Lol. At least it's something easily diagnosable and fixable!
-
Kaos, the two files i listed (an .ini and an .old) are literally the only 2 files in the root of f:. There are no valid executables there so i have no idea what the x3 is booting to get me into xbmc. That's my main point of confusion. I'll check the logs. The dash priority list in configlive is the default list. When i change to boot from E: a bare unleashx loads with no menu entries (games and emulators are empty) and is useless except for the file browser. Booting from c partition results in a boot loop, even though there is an evoxdash.xbe in the root, which im assuming was created as an old shortcut because there are no resource files/folders and trying to load it manually results in a dash restart... This thing reminds me of the house from poltergeist - full of randomness and wormholes and shit.
Dave, thank you for confirming. Is it possible that the bios is just resetting the time every time i try to set it with the dash?
Edit: Oh for fuck's sake. I can't open the .log file in unleashx because q: is only present when xbmc is running. And when i try to copy the log file from q: to any other partition so i can view it in unleash, xbmc just refuses to do it. For the life of me, i can NOT find the folder that is being mounted to q:, either. My xbox is a fucking sociopath.
What the CHRIST?
Edit 2: i found softmod install files in udata and some evox dash files in a subfolder of 41560017. So this thing was softmodded at some point in it's life. No wonder it's such a mess. Still can't find real q: directory...
-
Old ass xbmc 1.1 dude. I actually want to change to evox or maybe xbmc 3.5.3 but i don't know what the previous owner did for the installation on this particular box and i don't want to de-stabilize anything. The dash boots from a mounted (i'm assuming it's mounted) q: partition. X3cl is configured to boot the dash from f:, but the only files present in the root directory are evoxdash.xbe.old and evox.ini... What the fuck? How is this thing even booting? What the hell is going on?
I would just do a clean install but i won't have direct pc access for another month or so, so i can't back up. I do have slayer 2.7 and ogxbox 2021 discs. Can i pull it off with those?... Assuming that's even enough info for you to assess the situation!
-
22 hours ago, SS_Dave said:
The clock cap is been charged at 2.4 volt by the components next to it so it is close to it's rated voltage of 2.5 volt, I would suspect the clock cap may be short circuit and or the charging circuit has a shorted cap.
I had a Xbox with a leaking clock cap in for repair around 15 years ago and I also noticed that the cap failed and damaged the traces more often in tropical locations.
Inside the red box is the 2.4 volt regulator an I have seen pics of the 2 caps in yellow that have burnt the board from a possible short
Over the years (40 +) of working with electronics the super caps are always the 1st one to fail followed by the low value high voltage caps used in CRT TV's but all electrolytic caps will fail.
With the clock cap removed test the voltage across the points where the cap was and you should have just under 2.5 volt in standby.
Cheers
SS Dave
Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.All good info. Thank you. I'm a bit more informed now.
I recently read that the x3 bios will not store a date past june 20 2020. Is that true, and is that why it basically resets to my box's manufacturing date every time i power cycle? I did read about a workaround but i can't find it at the moment. It can't be the clock cap because mains power is always on and it loses the info even if the console is off for one second. Internet is not an option atm.
-
1 hour ago, sweetdarkdestiny said:
You are not wrong. The old releases indeed sometimes needed that long to boot. Problem was one config with ~ 4500 lines of code and the autoscan function. UnleashX is not realy made to load up that much code of a DVD. So splitting up the config into soft and hard mod config, cleaning out all the commend lines (which are btw. false) and hardcoding the live apps instead of let the dvd scan for the apps folder on the DVD (Why scanning for it when you know whats there?), the boot times are now pretty good. Took some nights to figgure all that out but the end was nice. I still have a copy of the version I made which I handed ToxicMedz so if you're interested in it to compare or just for fun, let me know and I send you a pm with the DL link.
Jesus, that's what it was doing at boot? No wonder it took so long. That's cool that you took the time to write those in manually. Yeah, ill check it out! Shoot me a link whenever. I appreciate that, dude.
-
17 minutes ago, sweetdarkdestiny said:
There are some reasons to use a BFM bios for an installer.
Mainly, you can make use of things which are not supportet by the bios the user have on his mod chip or are not active. You can make sure it's a .67/FG bios in case the user uses a old bios which dosn't support partition 7 (Happends every now and then). You can make use some gimmicks which would not be possible without a BFM bios (Disk swap for example which is usefull if you like to make an addon disk which can be side loaded in the main installer (Damn spoiler
)).
And like Kaos already wrote, you can use also a debug bios to run an debug dash on your console which for the most pll doesn't make any sense.
Over all, for 98% of the users which just like to use there xbox to play games, a BFM bios has no use.
Okay, makes sense. Thank you very much.
-
34 minutes ago, sweetdarkdestiny said:
2.7 is the last version Slayer has made. How ever, there are some updated version floting around which make use of a BFM bios and have softmod stuff added but the most of them also use old apps.
BTT. TruHeXEn 2021 boots up in just some seconds (30 sec max if you use a thomson which is a bit - slow.) on every XBox. Since the main config is splittet into a soft and hardmod section and some other bugs got fixed (autoscan etc:) the disc is fast. How ever, I personaly have still my problems with it because ToxicMedz sadly decided to re-add some major flaws of the old releases. Anyway, if someone like TruHeXEn, go with the 2021. It's the best version beside the 2018 release (Which some ppl still prefere over any other version).
And if you search for more, take a look at the OGXBox Installer.
Thanks for the info. I coulda sworn i saw like, 2m boot times in some vids, but i guess they were old. I do have both slayers and ogxbox and i use the og disc for apps mainly. I've yet to use it for a clean install.
-
15 minutes ago, Mave_rick said:
Sorry for the questions, I am just starting out, so still a n00b.
Does it look for DASH1 first, then if it's not found, it moves to DASH2?
So depending how I config those txt files, I could either have each bios running the same dashboard , or each bios has a different dashboard?
Yes, the dashes will be prioritized. You've got it.
As long as your dash settings are identical, they will share the dash. But you can load whatever dashes you want independently as long as your paths are right.
-
Hey dave: if i have a box without internet access, and the cap is only for mains interruption, you have any idea why i keep losing the time after i set it manually and power cycle?
Also, is it true that MS overvolted that cap? If so, why the fuck would they do that? Didn't they know it would cause the cap to fail?
-
I knew dave would come in and slam dunk that shit. Right on.
-
On 3/2/2021 at 12:53 PM, KaosEngineer said:
You can also load a debug BFM BIOS to change your console from a retail device into an Xbox Debug Kit. Operation of a retail console as a debug kit works better if it has an additional 64MBs of RAM added (v1.0-1.4 consoles only) bringing in par with a Debug Kit's 128MBs of RAM. I'm not exactly sure how limited a retail console is when being used as a debug kit with the stock 64MBs of RAM.
I've actually been wondering the same thing regarding 64mb debug consoles. Does anybody have an answer?
On topic, why would one use a bfm? Why do newer installers use them?
-
26 minutes ago, sweetdarkdestiny said:
Slayers didn't use a BFM bios (Ofc depending on which slayers you use, some does like 3.37 for example.).
Problem could be still the used HDD or the dvd media you used.
Damn. I'm still on 2.7. I need to get updated. I need to read up on the whole bfm thing because i really don't know anything about it. I want to know why installer discs use them. That's probably mandatory knowledge.
-
1 hour ago, roybridge said:
I left the disc sitting for roughly 30 minutes (whilst I was doing other things) and it just sat there. Slayers does load almost instantaneously.
Yeah, it should only take a few minutes to load the bfm... Slayers is just a normal executable. I love slayers. It's simple and it just works. It was the first installer i ever used, so i'm a bit attached to it.
-
Damn. I wish i had some extra cash right now. I'd definitely pick it up from you!
-
1 hour ago, roybridge said:
Just to follow on, I burned the ISO to a different brand of disc, selected 1x burn speed and the disc boots bust just sits at a large EvolutionX logo.
Try using either the Slayers installer or the ogxbox installer. That's my recommeodation, anyway. Also, i think hexen takes a few minutes to load. How long are you waiting?
-
On 8/21/2019 at 5:35 AM, tabajara said:
Unfortunately, it doesn't work for me. Tried with my 1.4 winbond tsop xbox with m8 plus bios, 256 kb.
I followed the tutorial, using the xboverclock ( i ran the program as administrator). I pathed the bios, flash the bios on tsop using the xblast but the clock speed doesn't change on xbmc
I'll be very glad if someone help me
Sorry for my bad english.
For the record, older versions of xbmc have a bug (or something) that keeps it from displaying the true speed. Using the newest version of xbmc or avalaunch will show you an accurate speed.
I flashed a 145mhz fsb bios and it's showing 142mhz in avalaunch. Wtf?
-
2 hours ago, Nf Given XD said:
Power supply died so wont be working on it for a lil bit till I can grab another
Hmmm, if your power supply was already on its way out, i'll keep my fingers crossed in the hopes that a new one may fix your issue... Although i can't imagine why it really would from a technical standpoint. I've seen weirder things happen though!
-
16 minutes ago, SS_Dave said:
As both Xbox's are chipped an can work with the drive unlocked I would use a standalone HDD cloner like this type of thing.
The one I have is Sata to Sata and takes around 7 hours to clone a fully loaded 2tb (I normally leave it working over night and it's done in the morning ) with out tying up a PC or Network.
The other option is to make a image of the master drive then restore the image on a PC
Cheers
SS Dave
Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.I guess with a tool like that, filesystems are irrelevant. Just raw data. That thing's fuckin rad.
Board Life Status
Board startup date: April 23, 2017 12:45:48
Xbox infinitely restarting
in Repair
Posted
There's nothing that stands out to me. In fact, it looks pretty good. That clock capacitor should get pulled and the area around it inspected.