I recently managed to open the SIM slot of the phone und inserted a SIM from another phone. Since the SIM was not detected, I decided to put the latest nightly CynogenMod 12.1 (Download) on the phone. Again by SFTP to SSHDroid in the LAN.
The phone bootet into CM 12.1, but the Google services (especially Play Store) were crashing, so I had to upgrade the GApps and after the ZIP from OpenGApps ran into an error in Recovery Mode (CWM), the arm binary from CGApps was ok:
- Download CM 12.1: https://download.cyanogenmod.org/?device=e975
- Download latest ZIP from GApps for arm architecture (View Raw): https://github.com/cgapps/vendor_google/tree/builds/arm
- Copy both ZIPs to /sdcard using SSHDroid.
- Uninstall Google Apps (GMail, YouTube, Play Store, Hangouts) for all users using Settings/Apps.
- Boot into Recovery (CWM) with Volume UP Button.
- Install both ZIP files from /sdcard/<ID> location.
- Clear Cache using Recovery.
- At least the Play Store should no longer complain/crash and can be updated. But I needed to recreate the Account Information.
- Other Apps complaining/crashing should be uninstalled for all users in the Settings/Apps und reinstalled by using the Play Store (GMail, YouTube, Hangouts, …).
I hope, I did not forget a step in this CM 12.1 upgrade process. So far, I did not need to do a firmware reset flushing /data.
The bad news is, that my E975 is still not detecting the SIM card, but I can’t tell, if it’s a hardware problem (slot defect) or a software issue, I will keep updating nightly CM 12.1. Comments are welcome.
An Optimus G E975 (Intl) was still waiting for wakeup, but official updates still stuck at Android 4.4.2.
So I applied CyanogenMod to that phone and since it was not that easy to gather all the necessary information, I write down a short protocol of the steps, that helped in my case. I started with the rather incomplete (with respect to rooting and recovery) howto at https://wiki.cyanogenmod.org/w/Install_CM_for_e975 .
If you also own an E975 with an Android at 4.4 my method is worth a try to get CyanogenMod in release 12 upwards on that phone.
Disclaimer: There is no guarantee, that it will work and there is always the risk to brick the phone, which renders it unusable. Also the procedure will wipe all data, so please backup all your data first.
Warning: Since SIM is not detected, I can’t confirm that CyanogenMod will provide phone functionality on the E975.
- Rooting with Towelroot
- I downloaded, installed and applied Towelroot APK (v3). It did just work.
- I used a search engine to pick an URL for the Towelroot APK file on a trusted site.
- Framaroot 1.9.3 did not work.
- BusyBox (Prerequisite)
- I installed BusyBox by stericson via Play Store.
- This is only an installer, so also start the App and use the installer.
- This is a prerequisite of the next App FreeGee, it will redirect to the Play Store, if you skip this step.
- FreeGee (Recovery Installer)
- I installed FreeGee by Seth Shelnutt via Play Store.
- CWM – ClockworkMod
- I started FreeGee and installed CWM 18.104.22.168.
- CyanogenMod Release
- Optional: Google Apps
- The next steps will include a wipe on the phone dropping all apps and data.
- If you want to use Google’s standard apps, see the following howto for downloading the appropriate ZIP for your CM version: https://wiki.cyanogenmod.org/w/Google_Apps
- Once more put the ZIP into folder /sdcard.
- Reboot into Recovery
- I used FreeGee to reboot into recovery mode.
- CWM (ZIP Installation)
- After rebooting the E975 it started CWM.
- I installed both ZIPs in /sdcard/0 downloaded before.
- Please skip the recovery option for root level, since it restarted my E975 immediately before I was able to apply the wipe/reset. I you run into the same problem, just power off the phone and start it with volume up + power button, then select Recovery to get back to the CWM menu.
- CWM Wipe
- Before rebooting the phone with the freshly installed ZIPs select the option to wipe the data.
After this procedure the phone started CyanogenMod 12 properly providing a clean (wiped) installation.
While I was doing the regular bananian-update I got the reminder, that an upgrade to Debian 8/Jessie is possible: News on 15.08
So, I just did it and so far there were no major problems. The reboot into the new environment came back with networking, so I was not forced into a KVM session.
I accepted the suggestion for disabling root login on ssh and I had to manually migrate the swappiness setting in the /etc/sysctl.conf, but now it’s in /etc/sysctl.d/swappiness.conf, so it should work flawlessly after the next release upgrade.
After ongoing stability problems with (L)Ubuntu I switched to Bananian 2 weeks ago and the BPI is now running stable (as expected). Switching power supply and SD card did not help in contrast to the change to Bananian.
So, please try Bananian first, since it seems to better match the hardware (kernel, bananian-config, bananian-update) than Lubuntu and Raspbian.
With the documentation from my (L)Ubuntu setup it was a question of hours to migrate to Bananian.
Ubuntu Firewall was replaced by a standard setup with Netfilter/ip(6)tables configured into iptables-persistent.
backupninja with duplicity method is still responsible for the daily backup.
This device is still providing the jump server on IPv6, Wake-on-LAN for the VDR Appliance, dnsmasq for the ULA subnet, SMTP Reminders, … one of the most important devices in the LAN.
The Raspian and Lubuntu releases at http://www.lemaker.org/ are yet not supporting Tokenized Interface Identifiers.
Raspbian is missing the appropriate
ip frontend, Lubuntu’s kernel is too old in this edition (3.4.90) and the
ip frontend will understand the syntax (
man ip-token), but the system call will fail.
Instead of building a newer kernel, I used ruby to check the local IPv6 addresses, constructing a new address with public prefix and static interface identifier, adding it to the list of addresses, if necessary.