Various Nokia RM-496 Firmwares

I've amassed some Nokia RM-496 / Nokia XpressMusic 5130 firmwares. I tried uploading them to cpkb.org to replace some broken links, but their account creation system is broken (and probably has been since 2016). Obviously, Blogger is the next best file sharing site. Here are the firmwares in question (plus some other stuff): https://drive.google.com/open?id=1WSLGXezgi9h21tC2_hQ2NSBwMfpEDm_r
They're on my Google Drive, which shouldn't ever go down - but if it does, I think we have bigger problems than a lack of very specific Nokia firmware from 2009.

List of files as of 2019-07-10:

• Nokia_5130_XpressMusic_RM-496_NDT_DP_18.00_MCU_07.95.rar
• Nokia_BB5_Easy_Service_Tool.zip
• Nokia_Connectivity_Cable_Driver_rel_7_1_69_0_eng.msi
• Nokia_Flashing_Cable_Driver_v8.23.0.0.msi
• NokiaCareSuiteForStore-2012_5_5_5.zip
• Phoenix_Service_Software_2011_8_5_45529.pdf
• phoenix_service_software_2012.50.001.49220.rar
• RM-496_06.68_AMER.exe (if your phone is from T-Mobile, this is the one you want!)
• RM-496_CareDP_11.0_sw06.65.exe
• rm496_CareDP_18.0_NDT_07.95.exe
• rm496_CareDP_18.1_OperatorDP.exe

I had to type that list out by hand (Google Drive won't let me select text), and manually hyperlink each file, and pay some shady file hosting website £2.00 for most of the files, and manually request for this webpage to be indexed by Google. So you better thank me!

EDIT: Well, well, well. I ran out of space on my Google Drive. The above files can now be found on Mega: https://mega.nz/folder/0oE3yCra#WDaIRvI_DGi7Tn-jqT-qcw

If you have any questions, leave a comment, and here's hoping Google sends me a notification for it.

Blogger's Mobile Application Sucks

All of my blogs posts are out of order. It's terribly annoying.

EDIT: It turns out there's an option to sort posts by "date created" instead of "date updated".

Tally, Tally, Hall, Tally, Hall, Hall, Tally

A good while ago, I bought an external HDD with two FireWire ports. It was a FireWire HDD.
Note that this HDD also had an external power jack. For what reason, I'm not sure; the FireWire cables were perfectly capable of powering it on their own. Anyway, I originally thought it was necessary to use this jack, and I left it plugged in to the wall overnight.
I woke up and the HDD did not work. I took the HDD out of the enclosure, and put it in a different computer (via SATA). It still did not work.
I tested the enclosure with a known-working second HDD. That HDD also did not work, so I took it out of the enclosure and tested it with my known-working SATA-to-miniUSB adapter. No dice.
So this enclosure fried my only two 2.5" HDDs. Lovely.

Anyway, I've been listening to a lot of Tally Hall recently. They're a very good band.

I Used to Call This Website "Bloggr"

Yeah. Guess I got it confused with the other website.

Legend of the PowerMac G5

A few days ago I bought a PowerMac G5 for $13 because hey, why not. The seller listed it as not working, and they had removed the hard drive for privacy reasons. From experience, I could extrapolate that it probably worked just fine. This would mostly be the case (making this a pretty boring blog post).

I set up the computer on my desk, plugged into a display and whatnot. It booted up with no issue to the flashing question mark folder; it couldn't find a filesystem because the HDD was empty. However, it did not make the "BONG" noise when booting up — I would later discover that this meant some of the RAM was bad.

So I burned the Mac OS X 10.5.6 installer to a USB drive and– uh oh, guess what's not detected by the OPTION menu. After a fiasco with trying and failing to get the Mac to boot from the USB, I thought, "Fuck it." I ran out to Office Depot, bought some DVD+R DLs, and burned the 10.5.6 installer to one of those. I put it in the machine and, once again, failed to get it to work.

It was at this point I reached out to Reddit™. "Try booting it off another Mac via FireWire," one helpful soul suggested. The only other Mac I had with a PowerPC 970 processor was an iMac G5 — with no OS installed, might I add. While digging that out of storage, I found a "Not for Resale" 10.5.6 retail installation DVD, which I then used to reinstall Leopard on the iMac.

Once that was done (it took about an hour), I decided to put the retail DVD in the PowerMac, because I figured it was worth a try. Lo and behold, it booted off the DVD and I had Mac OS X installed in no time. Absolutely maddening. But at least Mac OS X was working now.

Afterwards, I dug some old RAM out of storage (2GB total) and pulled out the broken RAM (4GB total), leaving my Mac with 4GB of RAM. Hey, that's pretty good. Don't forget to join me next week for "Twist Hopefully Sticks to the Trend of Not Saying 'fuck' That Much."

Folly of the iPhone. iFolly?

Today, I thought to myself, "Boy, what better time to restore my iPhone 5S to iOS 12 Beta 4 while simultaneously erasing the device than now. I am sure it will be a quick and seamless operation." I could not have been more wrong.

iTunes does not allow the user to erase the device as you restore it (EDIT: I think SHIFT/OPTION+"Restore" does just that), so I was forced to look for alternatives... just kidding, I won't touch iTunes with a ten-foot stick, so I already knew what program to use: idevicerestore. The aforementioned program is a command-line tool that acts like iTunes, but only for restoring/updating iOS firmware. It also allows the user to do some cool things, like downgrade devices, given proper circumstances (EDIT: No, I think only futurerestore/idevicererestore allows this). Unfortunately, idevicerestore is not readily available for Windows (my OS of choice), so I had to use my trusty macOS Sierra VM to use it. Little did I know that fuck-all would work.

Installing idevicerestore on macOS was a fairly painless process; I am no stranger to the command line. It even got pretty far in the restoring process - except, to my dismay, it didn't restore anything. It got stuck on "waiting for the device," despite the device being plugged in, recognized, and ripe for a restore. I thought to myself, "Fuck. Fucking fuck. Fucking fuck fuckity." That's when I turned to the trustier-than-macOS Linux. I didn't exactly want to install Debian on my primary desktop quite yet, so I used the 16 year old Dell desktop that sits at the other side of my room (this desktop was already running Debian). I once again installed idevicerestore, and started the restoring process -- but what's this? "Error 5"? Thanks for being so incredibly verbose, libzip.

It turns out libzip can't comprehend files larger than 2GB on i386 systems, which the IPSW file is and the Dell desktop is, respectively. "No big fucking deal," I thought to myself, cursing more than usual. "I'll just fucking recompile libzip with a fucking compiler flag that will fucking fix everything." It did not fix anything, as I was soon to find out. I append the flag, and recompile libzip. idevicerestore throws the same error. I append the flag again, this time by inserting it directly in CMakeLists.txt, and recompile libzip. Again, no dice. It was at this point that I exploded.

Afterwards, I decided to make a Blogger account for the sole purpose of writing this blog post. Wow, I feel like the average early 21st century Internet user! See you all next week, for another episode of "Twist Says Fuck."

Oh crap my iPhone is still in DFU mode.

P.S. For those interested, what finally worked was using idevicerestore on my Chromebook (running GalliumOS 3.0 beta).