kaberett: A series of phrases commonly used in academic papers, accompanied by humourous "translations". (science!)
[personal profile] kaberett
This is relevant because my current auxiliary internet device was running Cyanogen. I was annoyed about this for a variety of reasons, including "unrooted device means I can't transfer data between handsets for one of the apps I use" and also "unrooted app means I can't run f.lux but am instead stuck with Twilight". I was well aware that rebraining the device was likely to lead to sharks (official plaintext transcript, containing comic titles, URLs, post dates, transcripts (when available), and other metadata).

Here are some of the details of the implosion. Here's another report. tl;dr: if you are running CyanogenMod you probably want to turn off automatic updates; if you are running CyanogenOS you may wish to reconsider this plan.

The upside is that CM is in the process of being forked to LineageOS, with updating from CM to Lineage planned to be as seamless as possible -- if you want to build your own you can do so, at this point, but if you'd like flashable build packages you'll have to wait while infrastructure gets put in place.

So. Under the circumstances, having been planning to rebrain to CM this holiday anyway, I bumped that up the priority list (with hand-holding from [profile] silver_adept and [personal profile] me_and; many thanks). Herewith details of all of the sodding sharks involved, from the perspective of someone who had done some of this once previously under less frustrating circumstances. A lot of it might read as stating the obvious! I'm completely okay with that because I would like to have the reference material for my future use.

My laptop is running Debian 8 (jessie), and also has a Win10 partition About Which We Mostly Do Not Speak (not least because it was set up by the kind of people who think it's a good idea to have an administrator account without a password). My auxiliary internet device is a OnePlus One, which was running OnePlus' version of stock Android 6 IIRC.

I first acquired the latest nightlies of the CM recovery image and build package for my device following this advice on reddit about accessing mirrors. The rest of the thread may also be of interest. (This adds up to Android 7.1, in case that's of interest to you.)

I then attempted to follow the relevant instructions for my device (thank you archive.org). Note that these instructions are, to my taste, in a non-obvious order -- you want to have pushed your build package pushed to /sdcard/ before you flash the custom recovery image, or you'll have to go through several additional tedious reboot cycles (unless you're using something that prevents the stock installation from reflashing the recovery image on boot).

I couldn't work out how to push the build package onto the emulated /sdcard/ storage in such a way as to be able to wipe the necessary partitions pre-installation without... also wiping the .zip I was wanting to install. Under Debian (using android-tools-adb and android-tools-fastboot) adb sideload returned the error "protocol fault (no status)"; it appears to be the case that this is the error you get if you're using an older version of adb than your device expects, and I ended up booting into Windows and sideloading the build package from there (which did work), made more hilarious by the fact that the guide I found on unbricking your OnePlus (after e.g. listening to your partner who works in telecomms when they say "okay well you've tried everything else, why don't you see what happens when you wipe the /system/ partition") was written with a previous version of Android SDK tools for Windows in mind and a lot of the specifics have changed since then. (Spoiler alert: searching "sdkmanager" in Explorer will, in fact, eventually bring up the things you need, though I've yet to work out under what circumstances the search will return useful results.)

Via a hilarious diversion into soft-bricking my laptop while the phone was still inoperable (an attempted reboot from Win10 to Debian did not go well, I noped out, A fixed it for me), I ended up with a working install of CM...

... and then realised I really wanted GApps, but following the instructions in docs to flash GApps terminated with errors about there not being enough space on the /system/ partition to unpack even very small Open GApps packages, despite df -h from inside adb shell saying that there perfectly well was space, and additionally having a wail about error code 70.

I should, in point of fact, have just used the TWRP recovery image from the get-go. Error code 70? Is apparently because the CM recovery image really hates the idea of intalling GApps. I have not dug further into why. TWRP Just Worked.

Having done all that the next priority was clearly getting Pokémon Go working. Said guide more-or-less worked, give or take the link-rot affecting links to phh's SuperUser and to Magisk. I found this tutorial on installing Magisk on CM13 pretty helpful; however the options I want in Magisk v9 are not those given in said outdated guide, but were instead hidden under Settings -- I wanted to tick "Enable Magisk Hide" and "Enable systemless hosts", then reboot.

Which got me to a working version of Pokémon Go with 20 minutes to go til the end of the day, so I popped over the road to hatch an egg, pick up an incubator, and incidentally pick up a Seasonal Pikachu which actually had IVs over 80%, which was quite nice.

I have spent most of the time since then gradually setting myself back up in a workable configuration. I am mostly there. Basically the only thing left is "work out how to make Regularly read off the backup I made two OSes on two handsets ago", but frankly I think that might be a problem for another time.

(no subject)

Date: 2016-12-28 09:51 pm (UTC)
me_and: (Default)
From: [personal profile] me_and
Minor correction: the OPO was running CyanogenOS. This is potentially an important distinction at least for other readers because AIUI some OPOs were shipped with OxygenOS instead, and "OnePlus' version of stock Android" may well be taken as referring to OxygenOS. (Can expand on details/distinctions/etc if desired.)

(no subject)

Date: 2016-12-29 01:56 pm (UTC)
pseudomonas: (Default)
From: [personal profile] pseudomonas
Thanks for this. My phone's running CM13 rather than CnOS, but it's good to know the issues. I guess I'll hold off OS updates until something emerges from Lineage (may it come soon and in our days).

(no subject)

Date: 2017-01-28 08:56 pm (UTC)
pseudomonas: (Default)
From: [personal profile] pseudomonas

Excellent! I think I'll do my usual thing of letting the brave folk like you find the bugs first, and then I'll jump on the bandwagon in a few weeks ;)

(no subject)

Date: 2017-01-29 02:58 am (UTC)
pseudomonas: (Default)
From: [personal profile] pseudomonas

Ah, on looking it appears that my phone isn't yet supported (Samsung s4 mini)

(no subject)

Date: 2016-12-29 03:23 pm (UTC)
silveradept: A kodama with a trombone. The trombone is playing music, even though it is held in a rest position (Default)
From: [personal profile] silveradept
Glad things worked out okay and the problems were beatable, with help and moral support.

Now I need to figure out how to get myself up on CM14. 1 without having to lose all of my critical data so that the thing will stop force-closing everything.


kaberett: Overlaid Mars & Venus symbols, with Swiss Army knife tools at other positions around the central circle. (Default)

October 2017

9 10 1112131415

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Powered by Dreamwidth Studios