Jump to content

Sir Lags A Lot

Member
  • Posts

    120
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Contact Methods

  • Discord
    Sir Lags A Lot #2040
  • Steam
    Sir Lags A Lot (level 13)

Profile Information

  • Gender
    Male
  • Interests
    Gaming, game development, content creation, trains.

System

  • CPU
    Core i7 9700k
  • Motherboard
    Gigabyte Z390 I Aorus Pro Wifi
  • RAM
    Generic Skhynix 16gb ddr4 @2133mhz
  • GPU
    Msi Ventus 1660ti OC edition
  • Case
    Fractical Design Node 202
  • Storage
    1TB WD blu M.2 drive + 500gb Seagate HDD
  • PSU
    Fractal Design 450w Bronze
  • Display(s)
    Prim.- Asus Rog XG27VQ 1920x1080 144hz
    Sec.- Dell se198wfp 1400x900 75hz
  • Cooling
    Noctua L9I
  • Keyboard
    Asus Rog Strix Flare
  • Mouse
    Asus Rog Spatha
  • Sound
    Turtle beach stealth 600
    Skullcandy crushers rev. 1
    Sony 5.1 Surround Setup
  • Operating System
    Windows 10 Pro
  • Phone
    Samsung Galaxy s9

Recent Profile Visitors

951 profile views

Sir Lags A Lot's Achievements

  1. I was looking at possible upgrades for my monitor I have now. A 1080p 27in with a 1800r curve. I was looking at getting the Samsung G5 Odyssey but im not sure what size to get it in. Options being 27 or 32 inches. Both are the same price. Then I noticed the pixel density and it got me thinking whether I should stick with 27 inches or go up to 32?
  2. Well, the flash succeeded with the new files. But the phone has not fixed itself. It'll still load up to the carrier screen then sit there for about 2 minutes, then reboot. At this point I suspect its a hardware issue.
  3. Update, I may have downloaded the wrong firmware/Image. I'm downloading the proper one now. I wont be able to get to it until later tonight or possibly tomorrow.
  4. Odin itself gave an error. First time was a "model mismatch" error. I read a forum and used the User Data Usc instead of the CSC. It then gave a write error, I forgot the specific error name. I can try it again to get the name. Edit: When using BL+AP+CP+USERDATA it gave the model mismatch error. Log here: <ID:0/005> File analysis.. <ID:0/005> Total Binary size: 10718 M <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> FAIL! Model mismatch fail When using BL+AP+CP+CSC it oddly enough gave the opposite of yesterday. Log here: <ID:0/005> File analysis.. <ID:0/005> skip file list for home binary <ID:0/005> persist.img <ID:0/005> carrier.img <ID:0/005> Home Binary Download <ID:0/005> Total Binary size: 10268 M <ID:0/005> SetupConnection.. <ID:0/005> Complete(Write) operation failed.
  5. No, it wouldn't be under warranty, unfortunately. Its close to 4 years old and was my mothers old phone.
  6. A few days ago I was using my Samsung Galaxy S9 for a webcam. While doing so, I had not plugged it in. So it died without me realizing. When I realized, I plugged it in and let it charge for a few minutes. I turned it on, but it wouldn't get past the carrier screen, verizon for me. It would just stay there. This was similar to something that my phone would sometimes do after turning it on cold. To explain that shortly, it would turn on and stay at the carrier screen for a few minutes then finally get to my home screen. But it didn't really function, fingerprint sensor didn't work, many UI elements didn't work, and eventually it would become unresponsive. I would then have to hold power and volume down to go into the boot maintenance mode and restart it. I have no clue what caused that to happen but it seemed to be just something that would randomly happen. Sometimes it did this rarely and sometimes it would take half an hour to get it out of that state. Anyways, my phone now just stays at the carrier screen, it would stay there for hours im sure. I left it to do its thing while I slept and came to it saying along of the lines of "Cant load android system, your data may be corrupt." I've tried factory resetting it many times, it'll proceed to the erasing data screen but for only a second or two and will restart. Nothing gets fixed. Currently it just boot loops after being on the carrier screen for about 2 minutes or so. Today I did try using Odin and loading new firmware and OS onto it but that failed. This is the article I followed: https://norsecorp.com/install-stock-firmware-galaxy-s9/ . I'm not sure what to do at this point besides just getting a new phone, but I want that to be my last resort. Im not concerned about losing data as I'm sure it already long gone. In the mean time, I'll try searching for a fix.
  7. I daily my pair of Asus Rog fusion 700's. Almost all of the time I use them wired via USB. On the occasion I use the Bluetooth on them for music, I notice that they sound just fine until bass notes kick in. At that point, the volume drops significantly and highs fade a little. It happens whether I'm using my phone or any PC. I don't use any equalizers. I'm not sure if it just bluetooth or how the headphones handle the signal. Just curious why its doing this.
  8. Modem is a MOFI NETWORK MOFI4500-4GXeLTE-V2, cable is cat 6.
  9. Recently got a new internet service through unlimited-ville. Old was verizon. In short we live where dedicated hotspots are the only decent option. But the modem only supports 2.4GZ wifi and I notice my PC gets slower speeds than my phone. I bought an ethernet cable to hook to but my PC says unidentified network with no internet. I looked into the modem settings a bit but its kind of a nightmare in there so I couldn't find much aid. I made sure both of the ethernet connections are plugged in good and that it was plugged into the Lan not Wan on the modem.
  10. A few days ago, my dell latitude e6530 wouldnt post after I put some different ram in it. I press the power button and nothing happens for about 10 seconds, the fan will spin up and down and the LEDs on the inside start putting out a code. Hdd blinking, battery solid and network solid. Looked it up to find it meant a possible cpu failure. With that, I ordered a working cpu from ebay and put that in. Same thing. I'm not sure what's going on but I'd guess it's the board or maybe the chipset.
  11. I figured as much, I bought a usb to m.2 adapter to use but I bought one that is nvme only, not sata. I'm just hoping I dont run into other weird issues.
  12. So pretty sure I figured out the problem. The the adapter is nvme protocol only, while the ssd is a sata protocol.
×