Phone Flashing – Part 2

Further to my previous post, here’s a run down of what happened.

I’m currently running Cyanogenmod or a variant of it, which has lots of nightly builds – normally I choose not to flash but on Sunday, I decided to try. Probably a mistake.

Cyanogen updated from Android 5 Lollipop to Android 6 Marshmallow, which meant after I flashed, I was getting huge numbers of “sorry but xxxx crashed”. I suspected the Gapps was out of date or incompatible with the android version I had, and I was right – a different version was needed. So I flashed that also but that didn’t work, so I rolled back to my last good backup, which was from November 2015, that restored fine, and I’m back to where I was, minus a lot of app changes and updates needed (I uninstalled/reinstalled a lot of apps since that backup), fixed that, reupdated my apps, and redid both my app and my Nandroid backups so I’m good to try again sometime.

I lost a good hour to two hours over this, so let this be a reminder to make sure you have good backups before flashing. I was lucky I only lost 2.5 months of changes, and that was easily fixed, but losing ALL your data because you don’t have a backup is never fun (I’ve been there)

EE

As you’re probably aware, I love to tinker with phones, especially Android ones, having been able to root several:

  • HTC Wildfire
  • HTC Sensation
  • Asus Transformer TF101
  • Samsung Galaxy S5

However, when trying to tinker with my dad’s S5, some really weird behaviour occurred. I first unlocked it using a SIM unlock code, and it started to randomly reboot. Regardless of whether or not you use an EE SIM or not (we tried EE, Virgin and Three SIMs — all were subject to the rebooting behaviour). So, I decided to take a change and rooted it and flashed Bobcat ROM (a ROM which I was running successfully on my own S5, which is the same model as my dad’s with the only difference being the network provider — I’m on Three, he’s on EE.)

The phone still randomly rebooted, so I turned on Logcat and tried to see if it recorded anything. No such luck.

So I tried a few different ROMs — Stock Samsung (Lollipop), Bobcat ROM, and Phoenix ROM. All still rebooted. So I took it to Samsung for their opinion. They said they couldn’t flash it because Knox was void (Knox is a warranty flag on Samsung devices which indicates whether you have custom flashed the device or not — I obviously have.) But they were nice enough to tell me that the behaviour described usually indicates the Firmware is wrong (which is something I didn’t flash).

So, since this behaviour started before I even did a deep-level tinker with the device (before I flashed anything), I can only assume EE either flashed an incorrect firmware, or did not flash the correct firmware – or maybe did not flash the firmware properly. I now need to find an S5 firmware to flash onto the device. Since my own S5 is working, I can check that firmware and try to find the same one.

ROM Reflash – Cyanogenmod 11 (Flemmard) – Part 3

I am not impressed. After flashing and restoring my applications, the phone seems extra sluggish and seems to have locked me out of recovery mode. When I tried to set my alarm for weekdays, I was fighting the phone to click the days of the week. I was pressing Monday, Tuesday, Wednesday, then the phone took several seconds before showing up the change, then unticking them, and ticking them back on again.

I reflashed my recovery from 4EXT, since I could still get into the main OS, and now I’m reflashing from my image back to my albinoman build. This Flemmard build is going on my “do not use” list.

ROM Reflash – Cyanogenmod 11 (Flemmard)

Reflashing my phone again. Using Cyanogenmod again, this time, a different build. This build is V4.4.4 instead of V4.4.2 which is the one on the albinoman build. The build is also later than albinoman’s one, so might contain some fixes to problems encountered in V4.4.2.

Restoring my backups as I type this post.

Screenshot_2014-07-26-15-45-00

%d bloggers like this: