These are my running notes for when I’m reinstalling Android on a phone. Most everything these days is synced to Dropbox or Google, but there are still a few little gotchas. (Sorry, Ben! And everyone who texted him in 2017-2018)
- Signal messages
- Contacts – should be syncing to Google
- Photos – should be syncing to Dropbox
- 2 factor authentication apps for work will need to be reinstalled. Have spare codes if possible.
Convince VLC to see the music on the phone. I thought that I had convinced it to see the Dropbox music folder, so all we needed to do was make some music files offline via Dropbox. But VLC did not like the Dropbox music location in July 2018, so we moved files into Android Music location. Bah!
My running notes on what to consider when purchasing a laptop computer. And I also run over to The Wirecutter to review their latest advice, along with the little googling.
Screen resolution: screen resolution and how does it play with programs (the blurry tool bars with my silver Asus)
Track pad: can it take two finger input? Does it get bumped really easily (my blue Acer)
Physical assembly: Can the screen push way back? When sitting on the coach, I want to push it way back (more than the silver Asus)
Ports: options for connecting to other things (what are the plugs and how many are there? USB, USB-C, HDMI, mini-HDMI, )
Keyboard: quality of the keyboard and placement of keys
Drive: Solid State Drive that is big enough for Dropbox to sync
RAM is comparable to other computers in similar price point
CPU is comparable to other computers in similar price point
I got a new laptop. Resolutions is very sharp except for a few of my favorite programs. It’s looking blurry. Sort of smudged. Boo…
Go to File Explorer, right click on the .exe and right-click properties. Under “Compatibility tab” select “Override high DPI scaling behavior. Scaling performed by: Application”
*Note, I am NOT an Android developer. This documentation is for my own reference as much as anything else. There is a second Galaxy s2 that I’ll need to tackle at some point.
My device, the Samsung Galaxy s2 i777 (AT&T) running Android 4.1.2 (but connected with T-Mobile since I got crabby with AT&T). Since I’m well off warranty, a nice clean install of Android was highly tempting. We have two of these phones in our household, so below is the second, clean install I completed. The meandering of the first attempt is outlined in more detail below.
- Charged phone
- external sd card in phone
- usb cable
- Windows 7 computer
- Charge the phone and remove it from its case.
- Change the phone settings to allow transferring the files (if not already possible). I used Settings->Wireless and networks->USB utilities when Windows Explorer was not displaying the phone. This was not always necessary.
- I also changed Security->Unknown sources for application installs, but I’m not sure this was necessary.
- Move update.zip (the Clockwork file) using whatever mechanism you prefer to the external sd card for the phone. This was the second of two phone drives visible in Windows Explorer for me when using the USB utility or simply the “card” when phone immediately displayed in Windows Explorer. Eject the phone from the computer if possible (icon usually in lower righthand corner of computer screen).
- Turn the phone fully off.
- Restart the phone in recovery mode by holding down the up and down volume buttons and the power button until “Samsung” displays on the screen. Quickly release them to get into a Recovery screen.
- Move through the screens using the volume rocker and power button to select.
- In retrospect, I’m not sure if this was necessary since I repeated it below.
- Select: “apply update from external storage” and then update.zip (the file you added)
- Select: “install zip from sd card” and then “apply /sdcard/update.zip”
- I also did a factory reset at this point, but I’m not sure it was necessary.
- Reboot using the menu option
- Attach phone to computer again with USB cable.
- Transfer (again using Windows Explorer in my case) cyanogenmod.zip and gapps zip files. Probably could have just done this in step 3 above.
- Turn off and restart in recovery mode. Follow step six above so that the right version of clockwork mod is running. Then repeat for the cyanogen and gapps zip files.
- Reboot the phone
- In my case the CyanogenMod loading animation hung. I then restarted again and it booted up nicely.
- Start setting up your new phone!
I totally disregarded the adb push instruction the second time
- In a command window, change directory (cd) to the abd directory and push the modified cyanogenmod and gapps zip files. For whatever reason, abd push did not work after I had unzipped (flashed?) the cyanogenmod file on the first phone, so I’m carefully pushing both of them now.
I first tried to use the simple, lazy person install of CyanogenMod, and had it fail. It seemed like it should work, but failed on step 4 in fall 2013 (when on AT&T) and in March 2014 (When on T-Mobile) with an “unsupported device” alert.
I then moved onto the wiki for the i777 installation.
A few things I learned:
- Recovery mode: volume up/down and power. Nav: volume up/down and power for enter
- “Flashing” appears to mean unzipping a file
- Finally figured out checksums using the Microsoft utility fciv.ext
- Not sure I ever got http://www.clockworkmod.com/rommanager running right, but could fire it off from recover mode
- Need Java Development Kit to run ADK
- Eventually just moved the zip files to the external card using file manager (ignoring
- cyanomod only installed after remove the version check: http://www.youtube.com/watch?v=QW1znjDLe-k
- gapps had a metadata failure: http://stackoverflow.com/questions/19860479/set-metadata-recursive-failing-on-android-install Successfully installed after the supposed cyanomod install
- Stuck in the cyanomod loading animation
- Booted into recovery mode.
- Noticed running clockwork mode 220.127.116.11, not 18.104.22.168 which is the approved version for i777. Read some errors.
- Did a restore
- INstalled original cm.zip
- Seems to be working
- Discovered installed wrong version of Google Apps for the version of CyanogenMod I’m running on my phone.
- Couldn’t convince adb to push the correct gapps version (tried the Developer settings — 7 clicks on version and activating various debugging, restarting), ended up transferring with Windows Explorer. Restarted in recover/reboot mode, shifted to the correct update.zip, and the unpacked the hand transferred gapps. Worked fine.
Original time estimate: 2 hours.
Actual time: 4+ hours