Related
CM Wiki, CM Google+, Fireball Wiki, Fireball Google+
Non-development related questions and troubleshooting belong here: [Q&T][ROM] CyanogenMod 10.1 and 10.2
Contents
This Post: Instructions and information - Please read all of this post before installing CyanogenMod!
Post 2 - Restoring a non-functioning radio
Post 3 - Frequently asked questions and workarounds for common problems
Introduction
This is CyanogenMod 10.1 (cm-10.1) for the HTC Droid Incredible 4G LTE (fireball) based on Android 4.2.2. Usage of this ROM indicates that you understand...
the warranty on your device is void;
the developer(s) are not responsible for any damages that may occur to your device as a result of using this ROM;
there is a significantly higher chance that your device will eat your cat (for which the developer will not take responsibility).
Preparations and Installation
Get your phone ready for a new ROM
You must have an unlocked bootloader or be S-OFF (read here for instructions)
Before leaving your stock based ROM, turn on all GPS location services:
Settings > Location > (all three location services) = On
Backup the contents of your internal sd card. You can ignore these files/folders: ext_sd, battery_history.txt, .android_secure
Install a custom recovery: CWM or TWRP
Make a backup of your current ROM in recovery - DO THIS!
Install CyanogenMod
Perform the factory reset function in recovery and wipe the /system partition
Flash the CyanogenMod zip and optionally flash the GApps version corresponding to CM 10.1.x
If you are S-OFF, you're done; reboot and enjoy
If you are only unlocked, and not S-OFF, you will need to flash the boot image through fastboot. Extract boot.img from the zip file and place it in the same directory as your fastboot and adb executables. While still in recovery, execute these commands:
Code:
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Updating to a new build
Make a backup of your current build in recovery
Install the new build
If you are S-OFF, reboot
If you are not S-OFF, reboot to the bootloader and flash boot.img using fastboot (extract it from the CyanogenMod zip)
Your settings and data will be preserved. You will get an "Android Upgrading" notice upon reboot which is nothing to worry about.
Special notes about connecting to Verizon's network
Getting the RIL to play nicely with Verizon is tricky. The following quirks should be noted:
Waiting for network...: If you install gapps, the phone might seem to hang at "Waiting for network... Activation can take a few minutes" on the first boot. This takes a long time to timeout (maybe 3-5min). When it eventually fails, choose the SKIP option. Do not choose restart or the cycle will repeat. This is a one-time inconvenience that should not reappear on subsequent reboots.
SIM card added: the first couple times you boot the phone you may get a notice, "SIM card added". Do not hit restart, just hit the back button and the notice will go away.
Borked radio: in the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then see Post 2 for instructions on how to get the radio working again.
Official Downloads
Official builds are available at download.cyanogenmod.org/?device=fireball
Archive of older official nightlies: goo.im/devs/cm/fireball/nightly
If your display flickers noticeably after an hour or so of usage, discontinue use of these official releases (see below for unofficial releases that do not exhibit this issue). This issue affects about half of the fireball user base (rough estimate based on forum replies). These builds use linux kernel 3.4 which was never released by HTC for the fireball, so the board files are assembled as best possible with what little we have for reference. If your device suffers from this problem, you may notice the flickering persists for a few hours after restoring another ROM, but it should eventually subside. The developer(s) are not responsible for damaged devices as a result of running these builds. Stick with a stock-based ROM if you're uncomfortable with this.
Unofficial Builds
These builds are not endorsed by CyanogenMod. They are my personal builds.
Most recent builds: goo.im
Archive/Mirror: mediafire.com
goo.im folder structure: visit the page to read release-specific notes
mdm-releases - Recommended for users that have flickering panels on official builds. Based on CM 10.1.2 stable using linux kernel 3.0
kernels - Enhanced kernels for use only in CM
cm-10.1 - CM 10.1 builds that incorporate experimental patches being considered for inclusion in official CM releases
cm-10.2 - CM 10.2 builds that incorporate experimental patches being considered for inclusion in official CM releases
GApps
Download the GApps version corresponding to CyanogenMod 10.1.x
Reporting Issues and Getting Help
Policy on bug reports:
You must reproduce the issue in a clean state. i.e. install cm after wiping /data, /cache, and /system
logcat or GTFO
If these steps are not taken, your report will be ignored.
How to gather helpful data for troubleshooting
How to use the issue tracker
Getting help
There is an IRC chat room on freenode.net where you can speak with other HTC s4 and m7 users: #cm-htc. A device maintainer is usually present as well. For reference, the fireball is an s4 device in the same league as jewel (EVO 4G LTE), ville (One S), and evita (One XL), and these are all based on the Qualcomm Snapdragon S4 Plus MSM8960 processor. The various HTC One models for different carriers fall under the m7 name and use a similar but more advanced processor, the Qualcomm Snapdragon S4 Pro APQ8064. The device maintainers on s4 phones are: jewel=deck, evita=h8rift/rohan32, ville=intervigil, fireball=mdmower.
Change Log
CyanogenMod BBQLog
fireball-specific changes:
20130725 - fix blank MMS messages from iPhone 5 users
20130723 - fix low in-call volume and raise speaker volume max
20130721 - fix signal strength reporting zero on some GSM networks
20130715 - fix front facing camera face detect crash, fix dim screen on wake
20130628 - wake-on-volume fixed
20130622 - camcorder can now record in all resolutions
20130619 - finishing touches to battery parameters; charging should properly reach 100% now
20130618a - stereo audio fixed
20130618 - fix charging and battery level indicator
20130616 - kernel 3.4 introduced, updated adreno driver blobs from Qualcomm
---- break all teh things ----
20130504 - wake-on-volume fixed; flash and shutter synchronized better in camera
20130424 - encryption of /data partition is now supported, read post 3 for instructions!
20130306 - fix for selecting bands crashes com.android.phone, SMS/MMS behavior changes
20130303 - camcorder video focus improvements (still loses focus, but should be better)
20130226 - all resolutions save without restarting camcorder application
20130223 - all resolutions available in camcorder (with quirks)
20130221 - secure adb, experimental microphone noise suppression fix (amluto)
20130217 - camcorder saves videos correctly
20130209 - gooManager OTA support, camera focus fixed, notification led fixed
20130207 - fixed audio applications freezing phone, sending mms messages should not return invalid destination, battery charging LED can be disabled
20130204 - removed non-effective VZW APNs, enabled MTP support
20130131 - experimental VZW APN configuration
20130128 - initial Release
Click to expand...
Click to collapse
Known Issues
Official Builds
Display flickers and gets worse the longer the phone is on (may not occur depending on specific panel in your phone) - if you experience this issue, discontinue use of the CyanogenMod nightlies until the bug is fixed
Screen-on delay is long
Audio pauses briefly during screen on/off events
High pitch background noise in camcorder recordings
Touch to focus doesn't work
Flash crashes camera application
The first few times the phone boots there may be a "SIM card added" notice
Workaround in post 3
Unofficial MDM Builds
Moving between 1x and LTE networks sometimes requires toggling airplane mode to get data working
Camcorder does not stay focused
Music lock-screen widgets sometimes flicker when you turn on the screen; the controls are still active though
The first few times the phone boots there may be a "SIM card added" notice - Workaround in post 3
Known Issues that will not be fixed
OTG mounting of USB sticks - Likely no hardware support
FM Radio - Likely no hardware support
MicroSD does not show as a mass storage drive when connected to the computer - UMS was deprecated in Android 3.x
Workaround in post 3
Development Information
CyanogenMod 10.1 builds using linux kernel 3.0 were becoming very stable before DxO Labs made a DMCA take-down request on a camera auto-focus library: libDxOAF.so. CyanogenMod had to pull official support for this device until builds could be offered that do not include this library. Kernel 3.4 no longer depends on the auto-focus routines in that library, so development efforts have gone into getting evita, fireball, jewel, and ville running well on it. Official nightlies are currently available for fireball, based on kernel 3.4, but there are a number of issues to be resolved (see above). Since HTC has not released an official jellybean ROM for this phone, there is no recent kernel source that could provide hints about how to fix these issues. If you have kernel development experience, your help would be greatly appreciated in fixing up the board files: android_kernel_htc_msm8960/arch/arm/mach-msm/htc.
The following trees are needed to build CyanogenMod 10.1 based on kernel 3.4:
CyanogenMod/android_device_htc_fireball
CyanogenMod/android_device_htc_s4-common
CyanogenMod/android_device_htc_msm8960-common
CyanogenMod/android_kernel_htc_msm8960
Use the extract-files.sh script in the fireball device tree while running an official cm-10.1 build to pull necessary proprietary files into vendor/htc.
The following trees are needed to build unofficial CyanogenMod 10.1.2 based on kernel 3.0 (a.k.a. mdm-releases):
mdmower/android_device_htc_fireball - branch cm-10.1-FbR
mdmower/android_device_htc_msm8960-common - branch cm-10.1-FbR
mdmower/android_kernel_htc_msm8960 - branch cm-10.1-FbR
mdmower/android_frameworks_base - branch cm-10.1-FbR
mdmower/android_frameworks_opt_telephony - branch cm-10.1-FbR
mdmower/android_apps_Settings - branch cm-10.1-FbR
Use the extract-files.sh script in the fireball device tree while running an unofficial mdm build to pull necessary proprietary files into vendor/htc.
Credits
The task of bringing CyanogenMod to the HTC Droid Incredible 4G LTE was not a one man effort. I'm indebted to
htc-msm8960-devs: a talented group of developers with lots of patience while I was learning
utkanos, KemoNine, and Jin^eLD for general building questions
jose51197, Linch89, and blazingwolf for early testing reports
squeezyb for selling his fireball at a discount so I can share it with other developers
Restoring a borked radio
In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.
Downloads
Stock ROM
recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391
Instructions
From your preferred recovery, run the factory reset option
Follow the directions in this thread to install the stock ROM
Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash the stock recovery:
Code:
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
Factory reset from the bootloader: BOOTLOADER > FACTORY RESET
Let the phone reset and boot up
Allow network connectivity to be restored (make a test call)
Turn on all GPS location services: Settings > Location > (all three location services) = On
Turn off HTC's fast boot: Settings > Power > Fast Boot = Off
Reboot to the bootloader
Flash your preferred recovery: CWM or TWRP
(If you just want to run this stock ROM, you can stop here)
From your preferred recovery, run the factory reset option
Restore your ROM backup and wipe cache again before rebooting
FAQ and Workarounds
The solution to many problems
Before installation, you really need to run the factory reset option in recovery. If you are the only person experiencing a problem, try this first. It cures many problems!
Stuck at the HTC boot screen (solution by Aldo101t)
If you are only unlocked, and not S-OFF, you need to flash the boot image through fastboot. Extract boot.img from the zip file and run
Code:
fastboot flash boot boot.img
Enable USB debugging or access Developer Options
Settings > About phone > tap 'Build number' 7 times
Screen flicker
If after leaving the phone on for a few hours you notice the screen flickering rapidly, it is advised that you stop running the offical builds and restore a stock based image or one of the unofficial CyanogenMod 10.1 mdm-releases. You may still notice flickering for an hour or two after switching to a different ROM, but it should eventually subside.
"SIM card added" or "Waiting on... activation" notice every time the phone boots
SIM card added notice: do not hit restart, just hit back and the notice will go away
Activation notice: just hit home and the notice will go away (if the home button does nothing, just wait it out for 3-5min and then choose the skip option).
"What mobile network settings should I use?"
Verizon Wireless users in the U.S.
Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Network mode = LTE/CDMA/EvDo
CDMA subscription = RUIM/SIM
Do you have suggestions for other carriers and/or other countries? Let me know what settings work for you, as well as necessary edits to build.prop.
Missing menu button in applications (solutions by blazingwolf and somerandomname1)
Option 1: Re-associate the recent apps button: Settings > System > Hardware keys > Enable custom actions > App switch key
Option 2: Use action overflow: Settings -> System -> Hardware keys > Show action overflow
Text messages from 6250 with message VZWNM: # (solutions by Linch89, MJL99, and slacka-vt)
See this thread and this post.
ext_sd doesn't show files on the MicroSD
ext_sd is a leftover folder from the stock ROM. It is not used in CM because it prevents the internal storage from mounting successfully to the computer in UMS mode. File managers for Android should set /storage as their home directory to access internal and external storage.
Examples:
ES File Explorer: Settings > Path Settings: Home Directory = /storage/
Root Explorer: Preferences > General Preferences: Home Folder = /storage/
ADB reports device offline
After connecting the phone to your computer via USB, accept the prompt on the phone to allow connections from your computer.
Sound is distorted when DSP presets and/or bass boost are enabled or
Gapless music playback doesn't work
Set lpa.decode=false in build.prop:
Step 1) Settings > Developer options > Root access: Apps and ADB
Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
Code:
adb root
adb remount
adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/lpa\.decode=true/lpa\.decode=false/g' /system/build.prop
exit
adb reboot
To revert this change later, perform the same steps above, but swap true and false in the sed line.
MicroSD will not mount as a mass storage drive when connected to the computer
UMS was deprecated in Honeycomb, so be appreciative that you can access your device at all through this method! You can use MTP connection mode if you need to access both internal and external storage:
Settings > Storage > (menu) USB computer connection > MTP
Windows and Mac recognize MTP devices automatically.
Linux requires a bit more work, here's the quick instructions:
edit /etc/udev/rules.d/51-android.rules to include these lines for adb and mtp:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
install gvfs-mtp; for Ubuntu (or Ubuntu based distributions) this can be done with:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install gvfs
Restart your computer
Phone number, MIN, and PRL do not show in phone status or
MMS messages don't send: "Invalid destination"
Go to Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription. Change the subscription type from NV to RUIM/SIM. Restart the phone.
"I'm running RC1 or RC2 and I refuse to update!"
At least apply this small update package to fix low power audio and update the RIL to comply with changes to Verizon's network.
GPS doesn't acquire a signal (solution by somerandomname1)
From recovery, make a nandroid backup of CM
Wipe data, cache, and system
Restore a stock-based ROM backup
Enable all location services: Settings > Location > (all three location services) = On
Use a GPS application to get a lock on your position (I use GPS Test)
From recovery, wipe data, cache, and system
Restore CM backup
Wipe cache and Dalvik cache
Internal storage is not accessible by ROM or recovery
This rarely happens and unfortunately only seems to be remedied by formatting the internal storage:
Restart the phone to recovery and connect the USB cable to a Windows computer
In recovery, use the mount USB feature:
ClockworkMod(-based): mounts and storage > mount USB storage
TWRP: Mount > Mount USB Storage
When Windows informs you that it needs to format the drive in order to recognize it, go ahead and format it as FAT32
After the format is complete, use the safe eject feature in Windows followed by unmounting the USB storage in recovery
Your /sdcard partition should now be accessible
Encryption (thanks to Slick1123)
Pre-requisites: TWRP 2.6.0.0 or newer
Encryption procedure:
Make a full backup in TWRP
Restore /data from your backup - This seemingly odd step will ensure a footer is allocated at the end of the /data partition for encryption information.
Reboot and let phone battery charge to 100%
Turn on Airplane mode
Settings > Security > Encrypt phone
Be patient, your screen may go black for a couple minutes without indication of anything occurring before a reboot occurs and encryption progress is displayed.
Reverting encryption:
Make a full backup in TWRP (you will need to enter your encryption PIN upon entering recovery)
Reboot to TWRP, but instead of entering your encryption pin, just hit cancel
Wipe your data partition
Restore your backup
Using the Droid Incredible 4G LTE on non-Verizon carriers
Remove the following lines from build.prop:
Code:
# Carrier definitions
ro.cdma.home.operator.alpha=Verizon
gsm.sim.operator.alpha=Verizon
gsm.operator.alpha=Verizon
ro.cdma.home.operator.numeric=311480
gsm.sim.operator.numeric=311480
gsm.operator.numeric=311480
# Access to Verizon/HTC apps in Play store
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.gmm=android-htc
ro.com.google.clientidbase.ms=android-verizon
Congrats on getting this working.
+1 this is what is making me keep my phone
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews
Love cm10, congrats on the work.!!!
Sent from my Incredible 4G LTE using xda premium
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews
Great im happy to tell i have run this like for 3 days great battery exelent performance and I'll post over clock for this soon
Sent from my Incredible 4G LTE using xda app-developers app
With this version I have the following issues:
1. Apps don't have menu buttons. I had to change the recent apps button to open/close menus to get menus working.
I am not S-Off as I couldn't get that to work for me but I have the unlocked bootloader.
blazingwolf said:
1. Internal sdcard is not mounting correctly. It shows as not mounted in Root Explorer and Gallery, Camera and other apps that need it complain that it is not there. What's interesting is Settings/Storage sees the internal storage.
Click to expand...
Click to collapse
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.
Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1
mdmower said:
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.
Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1
Click to expand...
Click to collapse
just wondering, i used JOSE'S swap mod on sdcard, should i switch back before attepting this rom??
mdmower said:
Did you wipe data and cache before installing? These work for me. You may need to backup, then wipe your internal storage to eliminate conflicting application settings.
Also, for root explorer, internal sd is at /storage/sdcard0 and external sd is at /storage/sdcard1
Click to expand...
Click to collapse
Yep, sure did.
sdcard should also show sdcard0 when tapped on. It doesn't though it does show the symlink in Root Explorer.
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews
Aldo101t said:
just wondering, i used JOSE'S swap mod on sdcard, should i switch back before attepting this rom??
Click to expand...
Click to collapse
Im using another sdcard mod forma this ROM ill upload tomorrow by no ill just attach the file needed for that
Uploaded to drop box since xda app can't do it
http://db.tt/XPJ59Ux0
Sent from my Incredible 4G LTE using xda app-developers app
jose51197 said:
Im using another sdcard mod forma this ROM ill upload tomorrow
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
thanks JOSE
blazingwolf said:
Yep, sure did.
sdcard should also show sdcard0 when tapped on. It doesn't though it does show the symlink in Root Explorer.
Click to expand...
Click to collapse
Another thing to check is whether you're using the latest recovery version. Changes had to be incorporated when Android 4.2 came out. I have used ClockworkMod 6.0.2.7 for all of my testing, but I assume TWRP 2.3.3.0 should also work (can anyone comment on their experience with TWRP and installing this ROM?).
Aldo101t said:
just wondering, i used JOSE'S swap mod on sdcard, should i switch back before attepting this rom??
Click to expand...
Click to collapse
When you wipe /system you wipe out this mod.
Re: [ROM] CyanogenMod 10.1 Unofficial Release Previews
mdmower said:
Another thing to check is whether you're using the latest recovery version. Changes had to be incorporated when Android 4.2 came out. I have used ClockworkMod 6.0.2.7 for all of my testing, but I assume TWRP 2.3.3.0 should also work (can anyone comment on their experience with TWRP and installing this ROM?).
Click to expand...
Click to collapse
I usted twrp no problem
Sent from my Incredible 4G LTE using xda app-developers app
Twrp no prob in root explorer internal shows as SD card and SD shows as external_sd
Well, my issue seems to be that my internal sdcard got toasted. Not sure how yet and as of now I have been unable to get it back.
blazingwolf said:
Well, my issue seems to be that my internal sdcard got toasted. Not sure how yet and as of now I have been unable to get it back.
Click to expand...
Click to collapse
Perhaps /system didn't get properly wiped and something from your previous ROM is hanging around. I would reboot to CWM recovery, wipe /sdcard and /system (I hope you made a backup of internal sd like instructed), then re-install cm. After installing CM, wipe /data and /cache.
Also, while in CWM recovery, you can check that internal sd is accessible by first mounting /sdcard, then trying to access it through adb:
Code:
adb shell
cd /sdcard
ls
mdmower said:
Perhaps /system didn't get properly wiped and something from your previous ROM is hanging around. I would reboot to CWM recovery, wipe /sdcard and /system (I hope you made a backup of internal sd like instructed), then re-install cm. After installing CM, wipe /data and /cache.
Also, while in CWM recovery, you can check that internal sd is accessible by first mounting /sdcard, then trying to access it through adb:
Code:
adb shell
cd /sdcard
ls
Click to expand...
Click to collapse
It won't mount. Tried both CWM and TWRP. They both say unable to mount sdcard.
Still working on it.
Hmm. Windows wants to format something.
21.03.2014 RELEASE #4 UPDATE
Here is first ever CM for LG D605 (Optimus L9 II).
This is unofficial ROM and might have some serious faults, if this breaks your phone or they fire you from your job because alarm didn't start it will be your own fault since you have installed it. You have been warned!
The installation procedure was tested with unbranded phone (OPEN_EU variant). This might not work with branded ROM (but it would be good if someone check it).
Sources can be found at:
https://github.com/Varcain/android_kernel_lge_d605
https://github.com/Varcain/android_device_lge_d605
Things that don't work and won't be included in this ROM by default (possible enable by porting stock apps):
- FM radio
- IR port
Things that I already know that don't work at all or are bugged:
- NFC (no support at all yet)
- Manual service network selection (only auto supported right now)
- SIM card contact/SMS reading
For best battery life keep bluetooth off if you are not using it. It will keep constant wakelock if left on right now
NEWEST RELEASE #4
- Added USB tethering
- Added Bluetooth tethering
- Working move to sd-card function (but MTP on internal memory is disabled, external SD card is now mandatory)
- Vibration patterns tuning
- Correct WLAN and Bluetooth MAC addresses should be used now
CHANGES FROM RELEASE #3
- Fixed first call with no voice bug
- Fixed incoming call volumes
CHANGES FROM RELEASE #2
- Fixed voice call volume
- Fixed mute microphone option during calls
NEWEST ROM RELEASE #4:
d605_cm10_v4.zip - 164.61 MB
GAPPS:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Old releases:
release #3:
http://d-h.st/Zr4
How to install:
1. Flash CWM (from here: http://forum.xda-developers.com/showthread.php?p=50407619)
2. Download the ROM and gapps to sdcard
3. Boot to recovery
4. Wipe all userdata
5. Install CyanogenMod first then gapps
6. Reboot.
Now wait for CM to boot... (first boot will take longer as always).
For reporting bugs/problems:
- Send me logcat output (it would be good to have "logcat -b radio" output too if this is related to sim card/radio)
- Send me dmesg output
If you experience reboot (kernel panic most likely) then send me contents of /proc/last_kmsg (you have to copy this right after reboot, you can do it from terminal application if you don't have access to PC with adb at that time).
Reserve for info.
Thanks Varcain!
Beginning installation right now.
----------------------------------------EDIT---------------------------------------------
Help: http://forum.xda-developers.com/showpost.php?p=50007962&postcount=318
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
TaZRAge said:
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
Click to expand...
Click to collapse
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
How to install:
Unzip contents, boot your phone to stock ROM, connect via USB with USB debugging mode on, install adb (if you don't have it yet), then adb push all unzipped files to /data/local/tmp (for example adb push ./system.tar /data/local/tmp). After that enter adb shell, issue "su" command and:
# cd /data/local/tmp
# chmod 777 clear_partitions.sh
# chmod 777 loki_flash
# chmod 777 system_update.sh
# mkdir mntpoint
# ./clear_partitions.sh
# ./loki_flash recovery rom.lok
# ./system_update.sh
After that locate your unzipped gapps and do the following (I assume gapps are unzipped directly in /storage/external_SD/Download
# cp -r /storage/external_SD/Download/system/* mntpoint/
# sync
# reboot recovery
Click to expand...
Click to collapse
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/sdcard1/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Varcain said:
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/external_SD/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Click to expand...
Click to collapse
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
TaZRAge said:
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
Click to expand...
Click to collapse
I made a typo, try /storage/sdcard1 instead of /storage/external_SD.
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
TaZRAge said:
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
Click to expand...
Click to collapse
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Varcain said:
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Click to expand...
Click to collapse
reinstalled everything
maybe I gona set up a dualboot on my PC too =)
made 2 screenshots from my adb shell with wel.... rare behaviour
but now it worked!
i have Gapps
Not rare behavior at all! You forgot Download directory in first screenshot and in second one it looks fine to me.
Varcain said:
Not rare behavior at all! You forgot Download directory in first screenshot and in second it looks fine to me.
Click to expand...
Click to collapse
*headpalm* no wonder it did not work
Well whatever.... that is one fine port =)
I am only missing my apps i installed via the amazon appmarket =D
And since its not really a ROM for daily use i will not install everything i have in my stock ROM
---------- Post added at 07:44 PM ---------- Previous post was at 07:14 PM ----------
Varcain said:
Just use the ROM like you normally would, compare with stock and if you find some anomalies report it in my ROM's thread, I will add them to bug list and hopefully fix in next release.
you can save logs to sd card and then load them from PC connection (I turned off MTP setting by default so it wont be detected as MTP device for file transfers, you need to turn it on in settings>storage>press menu> select MTP).
To do this from console app in phone:
logcat -d > /storage/sdcard1/logcat.txt
logcat -d -b radio > /storage/sdcard1/logcatradio.txt
dmesg > /storage/sdcard1/dmesg.txt
cat /proc/last_kmsg > /storage/sdcard1/lastkmsg.txt
Click to expand...
Click to collapse
This should be in here too!
And by the way, after activating MTP in the ROM i can use adb shell at my computer again!
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
TaZRAge said:
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
Click to expand...
Click to collapse
Settings>Launcher>Homescreen>Homescreens
TaZRAge said:
*headpalm*
Click to expand...
Click to collapse
Thanks again
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Varcain said:
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Click to expand...
Click to collapse
Works this way!
---------- Post added at 11:01 PM ---------- Previous post was at 10:39 PM ----------
I connected my BT stereoheadset to listen to some music that doesn't sound like coming out a can....
Music via BT is no fun with this right now
I'm sitting next to my phone and the music comes interruptedly and sometimes with crackling sounds.
Gets even worse when i begin to experiment with the equalizer.
Next song comes flawless.... Ah display got disabled.
Screen back working and interruptions are back.
Controlls work perfect as i am used to (volume up + down + start/stop + next song + previous song do what they are supposed to do).
BT Speed to slow?
Disabled GPS now its better again.
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Varcain said:
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Click to expand...
Click to collapse
I tested it with stock many times before. Without problems like these.
And its sure I am in a radio-noisy environment. Around here are 4 wifi nets and the one i am in has 3 repeaters.
I had BT disabled on my computer during the test.
I will test it with a cable headset today, I don't have another BT headset.
Yet i had no other problems, bugs or errors!
Just install it!
First impression is VERY GOOD!
I think is faster than stock rom.
Minor problems with installation.
GApps works ok.
Known problem with camera.
Play some games, all run ok and FAST.
I think battery goes faster.
Install some themes, minor problems.
Basic Bluetooth ok.
That's all for now. I will play more later.
Thanks a lot Varcain! :victory:
I will upload new build in a moment and update the OP with it. There is major bug in first alpha release which causes constant wakelock (so the phone never goes into deep sleep). I managed to debug and fix it, please install new version.
Hi
I've installed CM10.2 (last update) (http://forum.xda-developers.com/showthread.php?t=2499796) on my Archos 80G9. It also runs the SDE firmware from Archos (http://forum.xda-developers.com/showthread.php?t=1653566). So far, so good, it runs quite nicely, all things concerned. Here's a screenshot to the system info: https://www.dropbox.com/s/0ri8n4jb6gyrfz7/Screenshot_2014-11-17-20-56-01.png?dl=0
Now I'm trying to install X-posed Framework, but this won't work. When I try, I get an error that tells me /system can't be mounted. (Screenshot: https://www.dropbox.com/s/ryaryqkie023sl4/Screenshot_2014-11-17-20-40-16.png?dl=0 )
When I take a look is ES3 if the folder is mounted, it looks like this: https://www.dropbox.com/s/4kwv0ja16qz52tq/Screenshot_2014-11-17-20-49-21.png?dl=0 . I can't tick the other boxes here, I get the message "sorry, operation failed" when I try.
I've already tried to use the "mount -o remount,rw /" command, to no avail...
I have no idea how I have to fix this problem and if it's even fixable.
Does anyone have any idea? Thanks in advance!
Same here...
No solution for that yet.
Before you type the mount command did you type "su" first (without the quotes)?
Just opening up terminal gives you regular user permissions which will not let you run the mount command. You need to become root/superuser first and that's what su does.
Yes I did ... Terminal emulator gives a notification that It's been granted superuser permission, but it still doesn 't Work.
Sent from my Ascend Y300 using XDA Free mobile app
Can you send a screenshot of the "mount" comand and response?
Did the prompt change from $ to #? What was the output of "mount"?
If terminal doesn't work try with superuser adb (allow superuser not only from applications, but from adb). Connect to the device with "adb shell" and issue this command.
Hi, thanks for your response. Here are two screenshots: the first is of the mount command in Terminal Emulator, the second of the same via abd shell. No results.
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Bor-ka said:
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Click to expand...
Click to collapse
1) I had 2.7 Experimental, so I uninstalled it and installed 2.6 Stable instead.
2) I do indeed use the "classical" option for installing Xposed.
3) Tried it, gave the following result: the file is created in /System/bin, so I guess /sytem is mounted okay. (see screenshots)
4) I use SuperSU, XPosed had root acces (see screenshot)
Seems to me /system is mounted fine, but Xposed just doesn't know it...
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Bor-ka said:
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Click to expand...
Click to collapse
Alright, did all of it.
1) Don't fully understand what is listed here, but in the first screenshot is the list of mounts.
2) Checked it, doesn't seem to exist, see second screenshot.
3) Logcat is attached.
Ok, it appears that I got the problem. Need a little time to think how to solve this.
The problem is rather technical. In newer androids supersu has isolated filesystem mounts for different processes.
It means that if you remount filesystem rw in one process, it (read-write-ness) is not accessible to the other process.
I have a little older cm10.2 build (for low-memory devices), perhaps, this was enforced later.
http://su.chainfire.eu/#how-mount (3.5)
So you're saying there's a good chance that if I install version 22_12_2013-13_29_20 (which i was planning anyway), instead of the latest one, the problem could be fixed?
Hmm, I installed the previous version of CM10.2, the problem seems to be persisting...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work. Seems I do have rw access to /system, but not with all apps...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work (permission denied). Seems I do have rw access to /system, but not with all apps...
Well, it seems like what I've said, filesystem mount encapsulation.
I've noticed one thing - you are using the standalone supersu application. And for me superuser mode is integrated in the system settings near the developer options. May be this is the case, internal superuser is patched already.
Alright, I'll uninstall superSU for now, give it a go with the built-in superuser app. I'll let you know!
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself.
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Bor-ka said:
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself..
Click to expand...
Click to collapse
Eureka! I re-installed CM, issued the mount-command i used earlier and installed X-posed! I used the built-in superuser app, no such problems as before. I did have to issue the mount-command, but that isn't a problem Is it normal I have to re-issue the mount-command each time I want to access /system rw?
Thanks a million! I can't believe it was something this trivial But I'm so glad it's solved, thanks!
Bor-ka said:
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Click to expand...
Click to collapse
I don't use the deepsleep-option. I do use Greenify to ensure certain apps (like Youtube or Chrome) aren't active in the background. Boot manager to be sure only essential apps boot in the first place. This seems to save me some battery life. Airplane mode as well.
I got this tablet from my dad because it was so slow he couldn't work with it. Even after factory reset, it very quickly became sluggish again. With CM, it feels like it's a new tablet. So no doubts about CM for me
I do have another issue: My pc won't show the tablet in explorer. I can access it via ADB, but I can't access the storage via explorer... I suppose I best start a new topic for that...
Glad the issue was solved. I wonder why the superuser application didn't work.. Deepsleep - it allowed the tablet to lose, say, 10-15% charge during a week sleep. Very handy if the tablet is used not often - really miss it.
Explorer connection - if I remeber correctly, you should go to settings -> storage (where the size of apps/pictures etc is shown). Then press the three dots in the upper right corner, select "usb computer connection" and select MTP.
P.S. I wonder also if CM12/Android 5.0 in the "development" section is worth a try...
(I'm running cuoco92 stable release, so I also posted in that thread. But maybe this section here is a better place for my problem)
Hi there!
Right after charging, the notification area and the "Home" and "Recent" buttons stopped working ("Back" still works). I also can't access the Settings>Users and Developer Options menus ("Developer options are not available for this user").
Most fixes I could find relate to other phones like Motorola and LG, but with the LeEco everything seems a little different. Those guides pretty much all tell the same thing:
1. Try a different user account (doesn't work, because I can't access it anymore) and
2. create an Activity Widget with Nova Launcher pointing to SetupWizard/.SetupWizardTestActivity (or com.google.android.setupwizard/.SetupWizardTestActivity). It also can have slightly different names like TestActivity, SetupExitActivity, or WizardFullActivity.
Problem is: I can't find any of those. There's LeEco Setup Wizard/.EnableSetupWizardActivity but it just says "App isn't installed" when I click on the widget.
Wiping the cache partition and re-installing the ROM also didn't work. I really hope someone can help me with this, because I don't have time for a complete wipe right now...
splicehere said:
(I'm running cuoco92 stable release, so I also posted in that thread. But maybe this section here is a better place for my problem)
Hi there!
Right after charging, the notification area and the "Home" and "Recent" buttons stopped working ("Back" still works). I also can't access the Settings>Users and Developer Options menus ("Developer options are not available for this user").
Most fixes I could find relate to other phones like Motorola and LG, but with the LeEco everything seems a little different. Those guides pretty much all tell the same thing:
1. Try a different user account (doesn't work, because I can't access it anymore) and
2. create an Activity Widget with Nova Launcher pointing to SetupWizard/.SetupWizardTestActivity (or com.google.android.setupwizard/.SetupWizardTestActivity). It also can have slightly different names like TestActivity, SetupExitActivity, or WizardFullActivity.
Problem is: I can't find any of those. There's LeEco Setup Wizard/.EnableSetupWizardActivity but it just says "App isn't installed" when I click on the widget.
Wiping the cache partition and re-installing the ROM also didn't work. I really hope someone can help me with this, because I don't have time for a complete wipe right now...
Click to expand...
Click to collapse
That's odd, the same thing happened to me 2 days ago on RevengeOS. I thought it must be a bug in ROS... Anyway, I was able to get the phone back along the lines you mention above. Through adb:
adb shell am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
Or just launch a terminal app on the phone, type su and then:
am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
mjoach said:
That's odd, the same thing happened to me 2 days ago on RevengeOS. I thought it must be a bug in ROS... Anyway, I was able to get the phone back along the lines you mention above. Through adb:
adb shell am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
Or just launch a terminal app on the phone, type su and then:
am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
Click to expand...
Click to collapse
Thanks for your suggestion!
Unfortunately, it went how I suspected it would. I'm getting:
Error Type 3
Error: Activity class {...} does not exist.So, this Setup Wizard is just not part of the ROM, it seems. There must be something equivalent in it somewhere, but where to find it?
I also tried:
am start -a android.intent.action.MAIN -n com.letv.android.setupwizard/.EnableSetupWizardActivityand got "Error: Activity not started, unknown error code -2".
But i only guessed the package name since I have no idea how to find those names. I only know the folder structure is "/system/priv-app/letvsetupwizard/letvsetupwizard.apk" and it shows up in activities as "LeEco Setup Wizard/.EnableSetupWizardActivity".
The only other thing I could think of is to create a new user via terminal. Is that possible?
But yeah, I'm running out of options. Should've looked into TWRP backups sooner. Was just about done perfectly configuring everything...
So, I got it working again, today!
First, I created a new user with
pm create-user User_Nameand switched to the new user with
am switch-user User_IDand back again to my old user.
(This first step might be unnecessary, can't tell after the fact.)
That action restored seemingly everything but the soft buttons. I then used this command I found after some googling:
settings --user 0 put secure user_setup_complete 1and it restored everything else!
So, maybe this can be of help for someone in the future if everything else fails...
First time posting and I wanted to say thank you to all the excellent talent here on XDA! None of this would have been done without the work of so many people.
I have a Moto G Play (2021) (XT2093-4) that I recently purchased (Best Buy - $159 US/Carrier Unlocked) and I wanted to document my adventure in to rooting, making '/system' RW, and fixing the missing LED notification light (hint: I used the charging light) (hint^2: It's not required to make '/system' RW in order to fix the LED notification light - I just wanted more control over my phone).
First, "OEM unlocking" was greyed out for me, but became available after several days of having the phone online with a SIM card.
I followed the instructions here to unlock the bootloader and root with Magisk (Non-TWRP). Along with these instructions.
Once bootloader is unlocked, you will need the 'boot.img' file from your stock firmware. I used the "Rescue and Smart Assistant" utility to grab a copy of the stock firmware (GUAMNA_RETAIL_QZAS30.Q4_39_35_9_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml) and extracted the "boot.img" file for the next steps.
Continue installing Magisk (Filenames may be different! Don't just copy and paste.):
Code:
adb install Magisk-v23.0.apk
adb push boot.img /sdcard/Download
(Follow the instruction on your phone to patch 'boot.img' in Magisk)
adb pull /sdcard/Download/magisk_patched-23000_aKKMt.img
adb reboot bootloader
fastboot flash boot_a magisk_patched-23000_aKKMt.img
fastboot flash boot_b magisk_patched-23000_aKKMt.img
You should now have a working, rooted Moto G Play. You can just stop here and have fun with your phone, but I noticed that even with root, the system partition was not RW.
I followed these instructions to make '/system' writable (Note: you will need the 'sysrw_repair.zip' that's included in the bundle and a Linux system):
Code:
adb push systemrw_1.32_flashable.zip /data/local/tmp/
adb shell
su
cd /data/local/tmp/
unzip systemrw_1.32_flashable.zip
cd systemrw_1.32/
chmod +x systemrw.sh
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` out=/data/local/tmp/systemrw_1.32/img/super_original.bin size=50
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
(On another Linux terminal)
Code:
cd /path/to/unzipped/sysrw_repair/dir/
chmod +x sysrw_repair.sh
./sysrw_repair.sh
This results in a new folder (img) with a rather large bin file (super_original.bin).
(Back on the phone adb)
Code:
exit # Exit root
exit # Exit adb
adb reboot bootloader
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
You should be able to login and have a writable '/system':
Code:
adb shell
su
mount -o rw,remount /
No errors should appear.
Last, I like having an LED indicator that tells me that I have an SMS/MMS notification waiting. Motorola thought it would be wise to eliminate that feature altogether instead of having the option to enable it. So, I forced it back on using a startup script that dumps the notifications and greps for some key words. And, if it finds something, it "breaths" the charging LED. The script loops until the notification is gone, then keeps checking for new notifications every 30 seconds. (Note: the "/data/adb/service.d/" directory is used by Magisk like an INIT service):
(Still root on the phones adb)
Code:
cd /data/adb/service.d/
cat <<EOF > ledfix.sh
#!/bin/sh
while true; do
if dumpsys notification | egrep NotificationRecord | egrep sms > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) == 0 ]]
then
echo 1 > /sys/class/leds/charging/breath
sleep 2
continue
else
sleep 2
continue
fi
elif egrep 'Charging' /sys/class/power_supply/battery/status > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) -ne 0 && $(cat /sys/class/leds/charging/brightness) -ne 0 ]]
then
echo 0 > /sys/class/leds/charging/breath
echo 255 > /sys/class/leds/charging/brightness
elif [[ $(cat /sys/class/leds/charging/breath) == 0 && $(cat /sys/class/leds/charging/brightness) == 0 ]]
then
echo 255 > /sys/class/leds/charging/brightness
else
continue
fi
else
echo 0 > /sys/class/leds/charging/breath
echo 0 > /sys/class/leds/charging/brightness
fi
sleep 30
done
EOF
chown 0.0 ledfix.sh
chmod 0755 ledfix.sh
reboot
Now, the charging light will fade off and on about every 2 seconds if there's an SMS/MMS notification waiting. And will check for notifications every 30 seconds. I'm sure someone can come up with a better way of doing this, but this was a nice quick-and-dirty way to get what I wanted.
Hope this helps!
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
PROFSLM said:
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
Click to expand...
Click to collapse
You can also get the firmware from
Lolinet Mirrors
https://t.me/MotoUpdatesTracker
Search for Firmware by codename, software channel, Software Version, and build #
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
mario0318 said:
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
Click to expand...
Click to collapse
I know!
I don't know what triggers that light to come on. I even waited until the battery was at 6% and the light still never came on.
So, I updated the script above to make the light go full brightness if the battery is charging. The order matters, so if a notification comes in while charging, it'll "breath" the LED. Also, if the battery is full, then the light will turn off. Kind of telling you that it's time to unplug.
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
jorduino said:
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
Click to expand...
Click to collapse
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
mario0318 said:
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
Click to expand...
Click to collapse
Im not completely sure how to get the right file, but I think the first time it was the wrong one, but then when i got what i thought was the right one, it just didn't work at all and I had to recovery flash it. I had just updated so maybe the correct image wasn't available yet. Im going to try again though
Oh! Hello @latentspork. Thanks for your interest in my SystemRW project. I just came across this thread randomly...
I'm happy you got my script to work on your Motorola device by using the included sysrw_repair script
Please feel free to send me your log files from script folder. Thanks. It's useful for further development of the script
latentspork said:
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
Click to expand...
Click to collapse
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Yes that's true the included sysrw_repair script (Linux only) pulls the image files from the phone to your computer and attempts to run the same lpmake command with the same arguments that just failed with error 73 on the phone itself and now all of a sudden it just works in Linux. Go figure.
latentspork said:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Click to expand...
Click to collapse
Why would you delete the super_original.bin ? That's your stock read-only super image which by default is automatically dumped by script for backup purposes in case you ever get a bootloop.
And if you launch the script by specifying a custom input value (in=x) like in your example above then you won't even have a super_original.bin file to begin with because script will skip the whole dumping of original super image process.
latentspork said:
This results in a new folder (img) with a rather large bin file (super_original.bin).
Click to expand...
Click to collapse
I think you mean super_fixed.bin
latentspork said:
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
Click to expand...
Click to collapse
Here in your instructions you are manually flashing the wrong file. Shouldn't you be flashing super_fixed.bin to your super partition?
Usually I only flash the super_original.bin to get back out of a bootloop...
latentspork said:
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
Click to expand...
Click to collapse
See that's why I included that automatic flash() function in the repair script. Then you don't have to worry about manually flashing the wrong file to your super partition
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
@lebigmac
I really appreciate the reply and the tool! It did work really well on my model (XT2093-4).
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Click to expand...
Click to collapse
I only assumed that "Error 73" was caused by insufficient space, because the phone really did run out of space. I noticed that the phone was out of space because I got a home screen notification warning, asking me to free up space. I confirmed it with a "df -h" at the shell. Apparently, the OS takes up almost 15GB. When you add the ".img" files, there's only about 5GB left. There wasn't enough room to complete the ".bin" file. Maybe I could have used an SD card or something.
You're probably correct in that "Error 70" is the correct error for that, but on my phone, I never saw that error. I did notice that the tool was still trying to write data as the phone ran out of space, then it would throw the "Error 73". Maybe it didn't register the lack of space, or just an oddity with my model? No idea.
Why would you delete the super_original.bin ?
Click to expand...
Click to collapse
This is the file that was created when I initially ran the "./systemrw.sh" command on the phone. The result of running the command on the phone were several ".img" files and a very large "super_original.bin", but it was incomplete because the command threw an "Error 73". I was following your instructions, and I noticed that the output name of the file was "original" instead of "fixed". I probably could of outputted it to a new name to reduce confusion, but I didn't really care too much about the name as long as I had a working file.
I think you mean super_fixed.bin
...
Shouldn't you be flashing super_fixed.bin...
Click to expand...
Click to collapse
Normally, yes. But the Linux script also outputted the filename "super_original.bin". Again, as long as it worked, I was okay with it. The commands I used above were the exact commands that I ran at the time. I copied them from the terminal consoles I was using. So I don't know why it wasn't outputting the correct filename (again, I was following your instructions and was a little confused that the names came out differently - I just figured I was doing something wrong like not use the proper output command or something).
Then you don't have to worry about manually flashing the wrong file to your super partition...
Click to expand...
Click to collapse
I was really just being cautious because my previous phone broke and I didn't have a fallback.
But, at no point were there two bin files (original and fixed), so there wasn't much confusion. Where I originally had just ".img" files before running the script, I now had a single ".bin" file. I knew that was the file I needed.
But again, thank you for all the hard work on this tool! I was reading that it's worked on lots of different model phones, and it's always good to see the open source community doing things that help all kinds of people.
For moto notification for this phone at least use https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledreborn or moto led reborn from the play store it just works
Hi, sorry. This can be removed. I put it in place because I was having issues with the xda app. For whatever reason, every time I tried to share this particular post, it would share a link for the post which I used originally, rather than the current post. I knew that if I commented I could get back here easily on my PC.
So what is the place holder for