This is a LineageOS 14.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.
Working features
HW accelerated GUI
Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Sound
SMS
Initiate and receive calls
Wifi
Mobile Data
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
NFC
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
SD-Card as internal storage (new Android M feature)
GPS
Fingerprint scanner
SELinux
Non-working features:
Known issues:
Camera crashes when switching from camera to video. Use Google camera or Open camera to solve camera issues.
See the Bug Report section of this thread.
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.0.0 recovery image [25/03/2016] (AndroidFileHost Mirror)
LineageOS 14.1 ROM for G800F/M/Y
Latest build by hennymcc: Android File Host
There might be a more up-to-date (OTA enabled) build by ayke: https://aykevl.nl/android
There are monthly builds and recent bootloaders and modems by Panzerknakker: https://androidfilehost.com/?w=files&flid=201249
Google Apps (contains Google Play, ...) for Android 7.1. The following is recommended:
Open GApps Project, Platform:ARM, Android:7.1, Variant: whatever you prefer (e.g. "mini" or "nano")
Install recovery:
Reboot your device into Download mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select "PDA" (in newer versions: "AP") and select the recovery image (recovery.tar.md5)
Check that only "F. Reset Time" is set. "Auto Reboot" should be disabled to avoid a reboot into stock ROM.
Click on "Start": the recovery image should be flashed now. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device, wait a few seconds and reboot into recovery mode (see instructions below).
Important: make sure not to boot into stock ROM, otherwise the stock ROM might remove the custom recovery again. If this happens, flash the recovery image again.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 14.1.
Flash ROM:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and the ROM zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM ROM zip-package
Install the GApps zip-package
How to root:
LineageOS does not have root support integrated by default. You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
After that root access is still disabled by default. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
Changelog:
19/08/2017:
* SELinux policy update
* Update to newest LineageOS sources
02/06/2017:
* Firefox crash&reboot fixed (thanks to Spookcity)
* Enabling the fingerprint reader does not cause bootloops anymore (thanks to Spookcity)
* Ambient display option added (disabled by default)
28/05/2017:
* [COLOR="red"]Note: ROM is stuck in bootloop when fingerprint reader is enabled. ROM removed.[/COLOR]
* Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
* Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
* Updated kernel to 3.4.107
* Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
* Updated LineageOS sources
* FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
* Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
* Replaced the buggy Snap camera with the LineageOS default camera app
* Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
20/02/2017:
* Fixed Youtube scaling issue on window resizing
* Compass fixed (thanks to mirhciulica for figuring out what's wrong)
* cpufreq config added
* Charge mode fixed (starts when plugging USB into a powered-off phone)
* USB-Tethering and Wifi SoftAP (Hotspot) fixed
* Camera doesn't crash when switching between camera and video (but might still crash sometimes)
* Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
01/02/2017:
* conversion to LineageOS
* updated some libs with stock MM versions
* fixed robotic voice problem
* fixed silence on first call
07/11/2016:
* Initial test build
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to CTXz, Psyafter, spookcity138, ayke and mirhciulica for working on this ROM.
XDA:DevDB Information
[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Panzerknakker, spookcity138, psyafter, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: LineageOS
Version Information
Status: Beta
Created 2017-02-01
Last Updated 2018-08-18
CostasGr said:
henny, what is ur baseband at the moment?
Click to expand...
Click to collapse
My baseband is G800FOJV1CPK1 at the moment.
Thx!!!
Fingerprint sometimes does not works: No response from the sensor. :crying:
hennymcc said:
My baseband is G800FOJV1CPK1 at the moment.
Click to expand...
Click to collapse
So Marroco Baseband is working in Germany?
Cool .... So ... Stock 6.0.1(Marroco Baseband) will also work in Germany, right?
?
Everything's working perfect right now besides the fingerprint sensor sometimes not getting any input and the "Cast" option for streaming on Smart TV's is broken as well ("Unfortunately, Settings stopped working", when connecting). YouTube still has this weird resizing problem on >=360p...
Thanks anyway for providing free software with regular updates!
EDIT: Are OTA-Updates active in this build or do we have to install them via TWRP-flash?
installing the root didnt work
edit: oh does seem to work, although TWRP says installation failed
edit2: although app says i have no root
wogooo said:
installing the root didnt work
Click to expand...
Click to collapse
Whats your error? What zip flashed? For me it worked at the first time
The problem with the videos is almost solved, it seems a bit slow and it is necessary to play the video, go to the menu and go back
---------- Post added at 09:01 PM ---------- Previous post was at 08:59 PM ----------
Mystixor said:
Everything's working perfect right now besides the fingerprint sensor sometimes not getting any input and the "Cast" option for streaming on Smart TV's is broken as well ("Unfortunately, Settings stopped working", when connecting). YouTube still has this weird resizing problem on >=360p...
Thanks anyway for providing free software with regular updates!
Click to expand...
Click to collapse
If you put the video to 720 and press the home button and you return, the bug disappears for a moment and you can see it normally, once time per video
PS: I use the google translator, I do not speak English
Mrdream94 said:
Whats your error? What zip flashed? For me it worked at the first time
Click to expand...
Click to collapse
You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
Error 7.
operation not supported on transport endpoint
set metadata: some changes failed
Try this zip. For me is working 100%
thanks for the work,great rom, everthing smooth, rooting worked with SR3-SuperSU-v2.79-SR3-20170114223742.zip (can't link it i am new )
only problem for me is the tethering. wifi tethering gives me an error, usb/bluetooth tethering is working but then there is no internet access with my laptop
@hennymcc I saw message here about wierd YouTube video resizing. In galaxy note 3 exynos development section there was same problem in Laos 14.1 ROM and op of that thread fixed it. His name is tincho5588.
Could you look into the Snapchat bug? When loging in it shows: Connection failed.
It only does that on CM14.1 and LineageOS14.
I Tried to log in on my tablet and backup/ restore the APP, didnt work.
Edit: tried everything availible on the Internet. Snapchat wont work
derhunt said:
thanks for the work,great rom, everthing smooth, rooting worked with SR3-SuperSU-v2.79-SR3-20170114223742.zip (can't link it i am new )
only problem for me is the tethering. wifi tethering gives me an error, usb/bluetooth tethering is working but then there is no internet access with my laptop
Click to expand...
Click to collapse
I'm loving my first taste of nougat - the rom is super smooth for me.
Unfortunately I also have a problem with the wifi hotspot. It starts to open the hotspot but a second later says 'error'.
Sent from my SM-G800Y using XDA-Developers Legacy app
Mrdream94 said:
Try this zip. For me is working 100%
Click to expand...
Click to collapse
worked! thx!!
information
anyone has noticed some problems with the battery life?
Ala1101 said:
anyone has noticed some problems with the battery life?
Click to expand...
Click to collapse
Yes, in my case it was the cell phone standby. I had it set to LTE. After switching to 3G battery live is much better because cell phone's energy consumption gets much much lower
Gesendet von meinem SM-G800F mit Tapatalk
No Root Access
There is no option for app root access, only for ADB
Ala1101 said:
anyone has noticed some problems with the battery life?
Click to expand...
Click to collapse
yesterday i've installed lineage, today I had huge battery-drain with 35% Media-Server, now I think it's better
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We will not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our instructions word by word
are unfriendly
WIKI
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Endeavoru_Info
INSTRUCTIONS
First time installing CyanogenMod 12.0 to your HTC One X (GSM), or coming from another ROM:
Read the official wiki
Read known issues and FAQs
DO A BACKUP
Unlock your device via http://www.htcdev.com if you haven't done so already
Read post #3 and flash a recovery supporting the new storage layout
DO A DATA WIPE / FACTORY RESET
Copy GApps and the CM 12.0 zip to your SD card
Boot into Recovery
Flash the CM 12.0 zip from SD card
Flash GApps for Lollipop from SD card
Flash the boot.img included in the CM 12.0 zip via Fastboot
Reboot (be patient, "optimizing apps" takes a while)
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 12.0:
If you're coming from a pre-/data/media build read post #3
Copy the CM 12.0 zip to your SD card
Boot into Recovery
DO A BACKUP
Flash the CM 12.0 zip from SD card
Optionally flash the most recent GApps for Lollipop if you encounter problems
Flash the boot.img included in the CM 12.0 zip via Fastboot if necessary. If in doubt, flash it.
Reboot (be patient, "optimizing apps" takes a while)
Upgrading from CyanogenMod 11.0: (untested and unsupported, see FAQ below)
Read the known issues and FAQs
DO A BACKUP
Read post #3 and flash a recovery supporting the new storage layout
Copy GApps and CM 12.0 ZIP to your SDCard
Boot into Recovery
Flash the CM 12.0 zip from SD card
Flash GApps for Lollipop from SD card
Flash the boot.img included in the CM 12.0 zip via Fastboot
Reboot (be patient, "optimizing apps" takes a while)
DOWNLOADS
Recovery: See post #3
CM12.0 unofficial testing builds:
Old layout:
2014-12-17
2015-01-02
2015-01-11 (broken UMS)
2015-02-03 (fixed boot.img)
2015-02-28
New Layout (read post #3):
2015-02-14
2015-02-28
CM12.0 official stable builds: Not available
CM12.0 official nightly builds: Not available
Google Apps: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
CHANGELOG
http://github.com/CyanogenMod & http://www.cmxlog.com/12/#
2015-02-28
Synced with CM
Fixed an issue with some SIM cards
Fixed USB OTG
Fixed broken Wi-Fi after a soft reboot
Device encryption should work (make a backup first!)
Fixed Rezound Proximity Calibrator
2015-02-14
Uses new storage layout. Read post #3. New boot.img and a complete wipe is required!
Synced with CM
Maybe working Google Play Movies
2015-02-03
Fixed boot.img is not required but recommended.
Synced with CM
UMS situation unchanged from 2015-01-11
Included a fix to allow moving Apps to SD
Allow toggling NVIDIA smartdimmer under Settings -> Display -> Advanced settings -> Adaptive backlight (with fixed boot.img)
Allow toggling sweep2wake under Settings -> Display -> Advanced settings -> Double-tap to wake (with fixed boot.img)
Allow changing the vibrator intensity under Settings -> Sound & notification -> Other sounds -> Vibrator intensity (with fixed boot.img)
2015-01-11
Synced with CM
Default to MTP for new installations (set it to MTP manually in the storage settings when coming from an older build)
Revert some custom UMS related fixes which restores the stupid pre 2015-01-02 auto-mount behavior. DON'T UPDATE IF YOU WANT TO USE UMS
Enable multi-user UI (and guest mode)
Fix setting maximum CPU frequency
Fix signal strength
2015-01-02
Synced with CM
Fixed SD card / UMS mounting issues
Fixed tethering
Button backlight is now adjustable
Long press action for "Recents button" now available (back is still missing)
USB connection mode can now be set to MTP
2014-12-17
First testing build
KNOWN ISSUES
Roughly in order of seriousness.
Outgoing calls & mobile data might be problematic
There is currently an issue with some SIM cards (MultiSim?) that don't work properly. You are able to receive calls and SMS messages but you cannot make calls or send SMS and mobile data does not work. The cause has been identified: http://review.cyanogenmod.org/#/c/88932/
No mobile data after disabling Wi-Fi
IP routes are not updated properly (check if "ip route")
Disable and enable mobile data to work around this
Recent App switcher is broken in landscape and may cause reboots.
Workaround: Select "Disable HW overlays" in the Developer options.
Using NFC with the Smart Lock feature causes a deadlock.
No device encryption possible.
No P2P/Wi-fi Direct.
Battery stats list Wi-Fi as always turned on even though it was disabled.
Audio may be problematic with MHL.
Sense 5 camera features not available (no burst, no zero-shutter-lag, picture quality seems to be worse).
Docking stations are not properly supported
Dock speakers do not work
Select "Disable HW overlays" in the Developer options to avoid crashes
Dock drains the battery
Proximity sensor issues (screen stays black after call, hardware issue, it may not affect you).
Workaround: install Rezound Prox Sensor Calibrator and play with the PS1_CANC slider).
SD card might not be available or might be always shown as shared.
Workaround: unplug the phone from your PC.
Moving Apps to SD is broken
Tethering seems the broken
No MTP
Mobile signal display is incorrect.
Unable to change the maximum CPU frequency through the settings.
FAQ
Can I dirty flash coming from CM 11.0?
It should work.
Do I need to update the recovery?
Please read post #3.
Where are the Sweep2Wake, Button Backlight Notifications and Fast Charge Settings?
Not accessible anymore from the settings. The functionality is still in the kernel. See second post for details.
When do the nightlies start? When do upload the next version? When do you fix XYZ?
I don't know.
Device not recognized in Windows (Recovery, UMS, MTP)
Please follow the steps outlined under "Option 1" or "Option 2": http://mdmower.cmphys.com/htc-drivers-adb-recovery/
Xposed?
No.
XDA:DevDB Information
CyanogenMod 12.0, ROM for the HTC One X
Contributors
Thömy
Source Code: https://github.com/CyanogenMod/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-12-17
Last Updated 2015-02-28
Here are instructions to enable or disable some features that were previously in the advanced settings menu. Currently untested with Lollipop!
Button Backlight Notifications (enabled by default)
Button backlight notifications are enabled/disabled by settings write permissions on a special file. To disable them remove the write permission for the sysfs file with
Code:
chmod 444 /sys/class/leds/button-backlight/slow_blink
Only execute it while the lights are not currently blinking.
The newest kernel also contains the ability to limit to the notification brightness. Do
Code:
echo 1 > /sys/class/leds/button-backlight/slow_blink_brightness_limit
to limit the brightness to your normal button backlight brightness (which you can adjust in the settings).
Fast Charge (disabled by default)
Fast charging is disabled by default and can be enabled with
Code:
echo 1 > /sys/devices/platform/htc_battery/fast_charge
Sweep2Wake (disabled by default)
Code:
# Enable s2w
echo 1 > /sys/android_touch/sweep2wake
# Adjust the needed swipe length. 325 for one button (default), 500 for two buttons and 850 for three buttons
echo 500 > /sys/android_touch/s2w_min_distance
# Disable direction independent behaviour
echo 0 > /sys/android_touch/s2w_allow_stroke
Nvidia SmartDimmer (disabled by default)
Now called "Adaptive backlight". Setting was moved to the "Display & LED" menu.
All settings where you manually have to execute a command are not persisted between reboots. You can use a third party app that supports toggling the settings or you can put the commands into /data/local/userinit.sh to apply them at boot.
The New Storage Layout
To combat the space problems on Lollipop due to ART builds will be switched to the /data/media storage layout that is commonly used with newer Android devices.
The new partition layout will change our internal SD card be the /data partition. The internal SD card will also be located in this partition under /data/media. This means the 25GB can now be distributed freely between Apps, Data, Music, Picutres, Dalvik cache, ... that were previously on separate partitions. Moving apps to SD is unnecessary now.
The transition to the new layout requires a complete wipe including the SD card contents.
Advantages
Free disk space problems are largely gone because the sdcard and /data share the same place
Properly supporting UMS and supporting moving Apps to SD is getting harder and harder. This change will make both unnecessary
Disadvantages
2GB (size of the old /data partition) are “lost”
Breaks compatibility with all existing ROMs, recoveries and boot.imgs
Hopping between Sense and CM based ROMs will be nearly impossible
No more UMS, only MTP
Downloads
Recoveries using the old storage layout.
TWRP 2.8.1.0 (by teemo)
CWM
Recoveries using the new storage layout
TWRP 2.8.4.3 (by @teemo, @Thunder07)
Migration
Basic steps for switching to the new storage layout.
Flash a recovery using the new layout
Reboot to new recovery
Format /data (Wipe -> Format Data in TWRP)
Flash ROM (don't forget the boot.img)
SD Card Data Migration
This guide uses TWRP 2.8.4.x to convert your phone without losing data.
Boot into the TWRP recovery supporting the old layout
Make a backup (only /data needed)
Copy everything (including hidden folders) from the SD card to your pc
You can use UMS or MTP
This will include the backup
Reboot to fastboot and flash the new TWRP recovery using the new layout
Flash the boot.img from the ROM you are using
Reboot to new recovery
Format /data (Wipe -> Format Data)
Go back to Mount and enable MTP if it is disabled
Reboot the recovery
Restore your SD card backup to the Internal SD card
Use the “Internal Storage” device
Execute “adb shell chown -R media_rw:media_rw /data/media/0/” to fix the permissions
Restore your /data backup from the SD card
If you don’t see any backups then you might have to move /data/media/0/TWRP to /data/media/TWRP manually
Flash the new ROM
adb push and flash it or use adb sideload, it’s your choice
More Information
You'll find more information in the New Storage Layout for HOX Endeavoru thread by @teemo and in the New Storage Layout document by myself
wow....it's christmas gift from Thomy...
Thanks a lot for your great work..will test it soon.. I'm the first to see this post..
I hope i'm the first to test this Unofficial Build..
Update 1 (On 18/12/14 - 2:54 (GMT +1)):
-- Flashed the rom successfully -- No black screens, no random reboots -- Wait for atleast 5-10 minutes on the first boot, it does take a long time on the first boot, but it boots successfully, don't just rush and reboot repeatedly
----------------------------------------------------
First time I'm testing Lollipop build:
1.) yeah, the interface is really amazing, pretty smooth UI compared to Kitkat
2.) every little animation is blend to perfection
3.) You'll love the Lollipop from the initial look at Unlock screen..
What's working so far (tested till now):
Wifi, Bluetooth, GPS -- Working fine..
Apps -- almost every app worked perfectly,
Broken:
App2SD is not working-- yeah, known as many reported about it earlier.. when updating the app, it says out of storage, so the best way is to uninstall and then reinstall the app...temp solution..
As of now, it's a perfectly stable build...will update later in detail..
Haven't checked so far: Normal Phone call...I hope it's perfect too.. also i didn't check the mobile data...
Ohh can't wait :fingers-crossed:
Any screenshots?
kicikk said:
Any screenshots?
Click to expand...
Click to collapse
Added.
Wake up and see THOMY'post,it is very very wonderful day.thanks lot Thomy.
Sent from my One X using XDA Free mobile app
Thanks, will report back after a day or so of use.
Thömy said:
Added.
Click to expand...
Click to collapse
hey thomy thanks a lot for this man! You are literally rebreathing life into this phone LOL. I upgraded to an S4 in anticipation of lollipop but then it broke so im happy that there is progress for this phone!
im very tempted to install this experimental build but its been a while since ive done any flashing... i dont wanna ef anything up. Maybe ill wait for a more stable copy.... but knowing me i probably will end up flashing it.
Finally LP has arrived on HOX thanks @Thömy you are the Xman of HOX.
Downloading......
So I got the ROM installed smoothly, I was trying to install the GAPPS you provided and I got the following error log:
Installing files....
cleaning up and setting metadata...
set_metadata_recursive:some changes failed
E:Error in /sdcard/gapps-lp-20141109-signed.zip
(status 7)
Installation Aborted
Click to expand...
Click to collapse
btw while installing the ROM i got this message at the end but it said install WAS complete:
Warning: No file_contextscript succeeded: result was [0.200000]
Click to expand...
Click to collapse
do you guys know what this is for?
I am going to try redownloading the GAPPS again and try flashing it again.
EDIT: Tried it again, didnt work.
Also, the ROM is running very smoothly from what i have used so far. The cell data doesn't work? I think you should mention that in the OP but otherwise nice job looking forward to the stable releases!!
----
from some research online, its due to the recovery I have on it? I'm at CWM version
Excited / Cautious
@Thömy Thanks
I'll wait & see how things go before downloading it, I have a question about project volta? the battery optimization thing Google did for Lollipop, does it work for the HOX? my battery has seen better days
I've installed the Rom and Gapps without any issues...
PaKii94 said:
So I got the ROM installed smoothly, I was trying to install the GAPPS you provided and I got the following error log:
btw while installing the ROM i got this message at the end but it said install WAS complete:
do you guys know what this is for?
I am going to try redownloading the GAPPS again and try flashing it again.
EDIT: Tried it again, didnt work.
Also, the ROM is running very smoothly from what i have used so far. The cell data doesn't work? I think you should mention that in the OP but otherwise nice job looking forward to the stable releases!!
----
from some research online, its due to the recovery I have on it? I'm at CWM version
Click to expand...
Click to collapse
Yeah, i guess, you have to update your recovery to the latest recovery.... I have installed it without any issues in philz latest recovery..
I haven't tried using mobile data...but most of the other features and apps work without any hiccups...i must say this is way too good for unofficial build.. great work by Thomy..
Thanks for the great ROM again everything is working fine and is nice and smooth :good:
raminjpr said:
Yeah, i guess, you have to update your recovery to the latest recovery.... I have installed it without any issues in philz latest recovery..
I haven't tried using mobile data...but most of the other features and apps work without any hiccups...i must say this is way too good for unofficial build.. great work by Thomy..
Click to expand...
Click to collapse
well i updated my CWM Recovery and now reflashing the roms. wish me luck!
EDIT: completed yay time to setup and test out. Thanks again OP!
Everything seems to be working perfectly except Mobile Data.
Its amazingly beautiful and smooth Great preview we are overwhelmed.
Thanks @Thömy
Anybody tried flash it with TWRP 2.8.1. 0?does it work?
Sent from my Galaxy Nexus using XDA Free mobile app
So data is working on that build?
Nevermind, saw it's not working atm..
Tapped from another Dimension
DumbleCore said:
So data is working on that build?
Tapped from another Dimension
Click to expand...
Click to collapse
You mean Mobile data network?
Sent from my One X using XDA Free mobile app
This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y). Support for G800M is untested so far.
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Working features
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Audio
Bluetooth (audio in HFP seems to be distorted with at least some headset devices)
Wifi
HW accelerated GUI
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
Camera (pictures+video: Back+Front)
MTP storage
IR
GPS
NFC
Non-working features:
Fingerprint scanner (no app for tests found)
Pulse sensor + Step counter (no app for tests found)
Hall sensor
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 2.8.7.0 recovery image [08/07/2015] (AndroidFileHost Mirror)
CM 12.1 ROM for G800F/M/Y (AndroidFileHost Mirror)
Google Apps (contains Google Play, ...) for Android 5.1.1 from Jajb (Recommended) or the one that suits you best from Consolidated GApps.
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 12.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 12.1 ROM zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
15/08/2015:
* Synchronize with newest CM 12.1 sources (contains stagefright patches)
08/07/2015:
* Update to latest CM-12.1 sources (LMY48G)
* Camera app supports saving pictures to external SD-cards
* Partition sizes of system and data slightly reduced to avoid "unable to mount /system" failure during installation on some variants of the G800 (e.g. G800Y)
19/05/2015:
* Update to CyanogenMod 12.1 (Android 5.1.1)
* Merged Kernel-sources from G800FXXU1ANL1
* Re-enabled NFC
* TWRP update
11/04/2015:
* Update to CyanogenMod 12.1 (Android 5.1)
* Update to TWRP 2.8.6.0
* Fixed blinking capacitive touchkey lights
* Fixed unresponsive touchscreen on wake-up
* Added support for Automatic Brightness control
* Added advanced touchscreen settings (Glove and Hovering mode)
* Use open-source Light-HAL, Power-HAL and IR-HAL implementations
* Updated Power-Profiling
23/03/2015:
* Fixed non-working mic on incoming call issue
* Fixed non-working menu-button
* Synchronized with latest CyanogenMod sources
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/patcher_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by one person (hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to Unjustified Dev from Team Regular. As the S5 mini (G800F/M/Y) and the Galaxy Light are quite similar we worked on this together.
XDA:DevDB Information
[G800F/M/Y][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for G800F/M/Y [Alpha 15/08/2015], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Unjustified Dev
Source Code: https://github.com/cm-3470
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-15
Last Updated 2015-09-22
FAQ:
Question:
I'm trying to flash this rom but it says to me: "This package is for kmniltexx, kminiltedv, kminilteub; this device is kminilte. E:Error executing updater binary zip ...."
Answer:
The device names were changed with the newest CM12 build to be able to distinguish between G800F (kmniltexx), G800Y (kminiltedv) and G800M (kminilteub) as all of them are kminilte devices. The new builds of TWRP and CM12 detect the correct device at runtime.
Older TWRP releases (for example that of RVR in another XDA thread) still detect the device as kminilte (instead of kmniltexx,...) and hence are not able to install the new CM 12 releases so please do not install RVR's TWRP if you want to install CM 12. Always use the TWRP image linked in the first post of this thread.
Reserved
As none of the pre-alpha testers reported any issues with NFC, I assume that the broken NFC of LS97 and me was caused by electrostatic discharge while removing and re-inserting the battery (at least I did this hundreds of times). In addition we already broke our NFC some weeks ago after having used 5.0.2 for some while, so this ROM should be at least as safe as 5.0.2 and there is no direct link between the custom ROM and the broken NFC.
Just as a precaution: to avoid damage of the NFC-chip (which is connected to the antenna in the battery) by electrostatic discharge, use the power button to reboot the smartphone instead of removing the battery.
What a nice first post for this new ROM
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
CTXz said:
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
Click to expand...
Click to collapse
Exactly the same.
hennymcc said:
Exactly the same.
Click to expand...
Click to collapse
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
CTXz said:
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
Click to expand...
Click to collapse
I haven't looked any deeper into this so far.
So how is the Final version going to look like if this is Alpha... Damn [emoji41]
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
CTXz said:
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
Click to expand...
Click to collapse
Well tried that but The setting just changes back to the default.
Nielsieboy said:
Well tried that but The setting just changes back to the default.
Click to expand...
Click to collapse
Ok thats wierd. Have you wiped all partitions you needed to like said above ( dalvik cache, cache, system, data )
If it gets verry anoying you might give a reflash a try. Also i know this sounds funny but did you atleast try rebooting the device?
---------- Post added at 08:55 PM ---------- Previous post was at 08:50 PM ----------
Also did you give this a shot https://play.google.com/store/apps/details?id=com.deskangel.kblight
There are many more apps on gplay for button backlight. Just search it
i've flashed it yesterday over the old buidl (without full wipe). so i got FC's on several google apps.
after flashing several different gapps for lolipop 5.1 the errors with the FCs are still stere.
then i've made a full clean install with full wipe and installed the pa gapps from the 04-10-2015 and now everything works fine & smooth.
tommorrow ill gonna test the bluetooth cause on the old build there were sond errors....
but for now it looks very good
I've discovered something. If you enable LiveDisplay the device will lag a bit.
And when you think I did a full wipe and reflashed the ROM, just to find out that my problem was related to this little feature...
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
it doesnt let you do that? why not? for me it worked...(i hate those lights too)
DerMoeJoe said:
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Click to expand...
Click to collapse
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
LS97 said:
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
Click to expand...
Click to collapse
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
CTXz said:
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
Click to expand...
Click to collapse
The only way to find out if it works is to try it. So if you want this feature you can flash that mod and report if it works .
I personally do not need it as I want the phone to turn off when I "power it off".
Note that the mod could cause stability issues. So before reporting bugs here you should reinstall CM 12.1 first with a full wipe and check if the problem is still present.
Edit:
this was supposed to be an answer to DerMoeJoe's question about the QuickBoot mod
Preparation
*
Decide on which version of Android to use. You need to find a recent version of Android that is stable and has the bugs worked out. There are a lot of choices and many still have bugs. For an older phone with limited capacity, I decide to take the AOSP version which is the baseline from Google with no fancy features added. Other ROMs can provide more capabilities but will take more resources of the phone and the more features the more to go wrong.
Couple of articles if you are interested
https://www.quora.com/What-are-the-...ock-Android-stock-rom-Lineage-OS-and-TouchWiz
https://www.google.com/url?sa=t&rct...39857/&usg=AFQjCNGMo0MHXcakgYtSiMJXCLaNZBYAUg
You also need to find the best custom recovery program for your phone. I used TWRP but there are other ones google to find a recommended one for your particular phone. http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
Prepare the PC
*
Create a folder on the PC for all the downloads and files
*
Download the minimal Google SDK or install the whole studio
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
*
*
HTC Sync Manager on PC** (This installed the phone drivers so the PC can talk to the phone)
www.htc.com/hsm
Alternatively you can go to the phone website and download the drivers for the PC
Check Java up to date on PC* (www.java.com)
*
*************** Connect the phone to the PC using USB and ensure phone is 100% charged********
*
Download the files you need
*
Download new Rom* (aoscp_eye-3.6.3-20170508-unofficial.zip) *
https://www.androidfilehost.com/?fid=457095661767159592
*
Rename to a simpler name Android712.zip
**
Download Google Apps
*
http://opengapps.org/
*
Download ARM 7.1 nano (You can install other google apps from the app store)
***********Rename to a simpler name GAPPS71.zip
*
Backup the phone
*
Record the APN settings (Access Point Names) Hidden in “Cellular Network” settings under data.*
Ensure Google backup is turned on* (Give it at least 24 hours with WIFI and Power to complete google backup)
Use a backup tool such as HTC sync manager or Windows explorer to backup all photos, music etc.*
*
Move key files to Phone
*
Copy key files onto SD card.* GAPPS and new ROM
Use windows explore on your PC to move the files to the SD card on the phone
**
Unlock the bootloader on the phone (you need to register to get an account)
*
**https://www.htcdev.com/bootloader/
*
Remove Encryption on the phone (I removed the SD card from the phone for this step, not sure that is actually needed)
Factory Reset in settings under Backup and Reset.
*
Install TWRP
Download recovery* (TWRP 3.1.0-0 Desire EYE OMNI by Arun)* Again find the most recommended one for your phone model. https://twrp.me/Devices/ for the official download by my phone isn't supported.
*
https://forum.xda-developers.com/devdb/project/dl/?id=23630&task=get
*
In Windows explorer rename to something simpler eg *recovery.img
*
*************** Go to the windows Command prompt
*
*************** CMD prompt
***************
Fastboot* flash recovery** recovery.img
*
Fastboot reboot (the phone should reboot)
*
***************
Boot into TWRP.*
*************** Power off the phone
*************** Hold volume down button and then holder power button.
*************** Use volume up/down to highlight recover
*************** Use power button to select recover
*
Do a full backup of your operating system to your SD card.* **TWRP backup. (Boot, System and Data)*** Optional copy the backup directory back to your PC using windows explorer on the phone (you will need to reboot the phone to do this). *
*
Wipe using TWRP (Swipe to Factory Reset)
*
Install using TWRP : select the sd card and the New71.zip
*
Install using TWRP : select the sd card and the gapps.zip
*
Reboot
*
*
Donate to the developer of your new ROM at the end when it works.*
*
*
Working perfect, thanks! The only problem I had is that the camera crashes after a while. The solution is using this app Camera Error Fix (Root) (from VatsalX Software)
When do you think Android Oreo aoscp for HTC Desire Eye will be available?
matias.uy said:
Working perfect, thanks! The only problem I had is that the camera crashes after a while. The solution is using this app Camera Error Fix (Root) (from VatsalX Software)
When do you think Android Oreo aoscp for HTC Desire Eye will be available?
Click to expand...
Click to collapse
This fix works for me too thnx!
htc desire eye unlocked version
will it work on unlocked phones (htc desire eye).
i tried the custom roms but thos have un fixed bugs
challenger07 said:
Preparation
*
Decide on which version of Android to use. You need to find a recent version of Android that is stable and has the bugs worked out. There are a lot of choices and many still have bugs. For an older phone with limited capacity, I decide to take the AOSP version which is the baseline from Google with no fancy features added. Other ROMs can provide more capabilities but will take more resources of the phone and the more features the more to go wrong.
Couple of articles if you are interested
https://www.quora.com/What-are-the-...ock-Android-stock-rom-Lineage-OS-and-TouchWiz
https://www.google.com/url?sa=t&rct...39857/&usg=AFQjCNGMo0MHXcakgYtSiMJXCLaNZBYAUg
You also need to find the best custom recovery program for your phone. I used TWRP but there are other ones google to find a recommended one for your particular phone. http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
Prepare the PC
*
Create a folder on the PC for all the downloads and files
*
Download the minimal Google SDK or install the whole studio
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
*
*
HTC Sync Manager on PC** (This installed the phone drivers so the PC can talk to the phone)
www.htc.com/hsm
Alternatively you can go to the phone website and download the drivers for the PC
Check Java up to date on PC* (www.java.com)
*
*************** Connect the phone to the PC using USB and ensure phone is 100% charged********
*
Download the files you need
*
Download new Rom* (aoscp_eye-3.6.3-20170508-unofficial.zip) *
https://www.androidfilehost.com/?fid=457095661767159592
*
Rename to a simpler name Android712.zip
**
Download Google Apps
*
http://opengapps.org/
*
Download ARM 7.1 nano (You can install other google apps from the app store)
***********Rename to a simpler name GAPPS71.zip
*
Backup the phone
*
Record the APN settings (Access Point Names) Hidden in “Cellular Network” settings under data.*
Ensure Google backup is turned on* (Give it at least 24 hours with WIFI and Power to complete google backup)
Use a backup tool such as HTC sync manager or Windows explorer to backup all photos, music etc.*
*
Move key files to Phone
*
Copy key files onto SD card.* GAPPS and new ROM
Use windows explore on your PC to move the files to the SD card on the phone
**
Unlock the bootloader on the phone (you need to register to get an account)
*
**https://www.htcdev.com/bootloader/
*
Remove Encryption on the phone (I removed the SD card from the phone for this step, not sure that is actually needed)
Factory Reset in settings under Backup and Reset.
*
Install TWRP
Download recovery* (TWRP 3.1.0-0 Desire EYE OMNI by Arun)* Again find the most recommended one for your phone model. https://twrp.me/Devices/ for the official download by my phone isn't supported.
*
https://forum.xda-developers.com/devdb/project/dl/?id=23630&task=get
*
In Windows explorer rename to something simpler eg *recovery.img
*
*************** Go to the windows Command prompt
*
*************** CMD prompt
***************
Fastboot* flash recovery** recovery.img
*
Fastboot reboot (the phone should reboot)
*
***************
Boot into TWRP.*
*************** Power off the phone
*************** Hold volume down button and then holder power button.
*************** Use volume up/down to highlight recover
*************** Use power button to select recover
*
Do a full backup of your operating system to your SD card.* **TWRP backup. (Boot, System and Data)*** Optional copy the backup directory back to your PC using windows explorer on the phone (you will need to reboot the phone to do this). *
*
Wipe using TWRP (Swipe to Factory Reset)
*
Install using TWRP : select the sd card and the New71.zip
*
Install using TWRP : select the sd card and the gapps.zip
*
Reboot
*
*
Donate to the developer of your new ROM at the end when it works.*
*
*
Click to expand...
Click to collapse
Worked well also for me - i followed the instructions and all went smooth and my HTC Desier EYE have now android 7.1.2 - Thanks !!!
18tanvir said:
will it work on unlocked phones (htc desire eye).
i tried the custom roms but thos have un fixed bugs
Click to expand...
Click to collapse
My phone is unlocked (not rooted) and worked just fine. This ROM is stable with few issues.
Only H+ speeds and unable to access Google acct after installing 7.12 on Desire Eye
After installing Android 7.12 on the HTC Desire Eye, I am only getting H+ mobile data speeds instead of my former 4g LTE even after changing the APN settings to what I was using previously. Are the APN settings different on Android 7.12 for T-Mobile? I notice there are more options then there was on the stock ROM. I am also unable to access my Google account after updating though am entering my current password correctly. Has anyone else had a problem like this after installing this ROM? Any suggestions much appreciated.
Note:
After rescanning for available networks and re-selecting T-Mobile, I am now getting LTE, no APN changes were needed. Google account problems may have been due to timing out on a bad connection, both are working now.
Try RR rom.
https://forum.xda-developers.com/de...ent/rom-resurrection-remix-os-t3602048/page23
Build 20170905 is without any bugs.
Also don't forget to install aroma gapps (not Pico)
TahirZX said:
Try RR rom.
https://forum.xda-developers.com/de...ent/rom-resurrection-remix-os-t3602048/page23
Build 20170905 is without any bugs.
Also don't forget to install aroma gapps (not Pico)
Click to expand...
Click to collapse
Thanks, will give it a try.
Noticed there is a newer version of TWRP. https://forum.xda-developers.com/devdb/project/dl/?id=24849
challenger07 said:
Noticed there is a newer version of TWRP. https://forum.xda-developers.com/devdb/project/dl/?id=24849
Click to expand...
Click to collapse
Has bugs. Use Tark's twrp from RR rom forum it's the most stable.
challenger07 said:
My phone is unlocked (not rooted) and worked just fine. This ROM is stable with few issues.
Click to expand...
Click to collapse
Issues as in?
---------- Post added at 08:00 AM ---------- Previous post was at 07:57 AM ----------
TahirZX said:
Try RR rom.
https://forum.xda-developers.com/de...ent/rom-resurrection-remix-os-t3602048/page23
Build 20170905 is without any bugs.
Also don't forget to install aroma gapps (not Pico)
Click to expand...
Click to collapse
Sir, i tried the rom but rr has some bugs.such as over heating,sudden app closing, problems with floating window (messenger) etc.
18tanvir said:
Issues as in?
---------- Post added at 08:00 AM ---------- Previous post was at 07:57 AM ----------
Sir, i tried the rom but rr has some bugs.such as over heating,sudden app closing, problems with floating window (messenger) etc.
Click to expand...
Click to collapse
Those issues are only with latest builds because of a kernel rebase. U have to install 20170905 5.8.4 build of RR and always use Tark's recovery to flash RR rom. It has zero bugs. I'm using it with no issues at all. Clean install it and u won't be having any of those issues.
TahirZX said:
Has bugs. Use Tark's twrp from RR rom forum it's the most stable.
Click to expand...
Click to collapse
Thanks I assume you mean this one: https://androidfilehost.com/?fid=817550096634770683
I will give it a try.
The only issues I have noticed with the AOSP ROM that I used in my guide are
1. A couple of times per month the whole phone will crash and I have to reboot.
2. Luna (Google launcher) goes slow sometimes and I've fixed the issue by deleting luna cache and data but it seems to return after a few weeks usage. I may return to the standard Google launcher.
Not sure if either is related to the ROM. Otherwise the ROM is very stable. But I've not tried the RR Rom so far.
challenger07 said:
The only issues I have noticed with the AOSP ROM that I used in my guide are
1. A couple of times per month the whole phone will crash and I have to reboot.
2. Luna (Google launcher) goes slow sometimes and I've fixed the issue by deleting luna cache and data but it seems to return after a few weeks usage. I may return to the standard Google launcher.
Not sure if either is related to the ROM. Otherwise the ROM is very stable. But I've not tried the RR Rom so far.
Click to expand...
Click to collapse
No such issues on RR. Also it's smooth and lots of customization.
I installed Tark's TWRP and was going to try his ROM but when I boot into TWRP (3.1.1.0) I get the following error message and TWRP doesn't see the SD card where the ROM is. Looking on google but not clear what the issue is. Any suggestions?
Immediately after I enter the encryption password "Failed to mount /external_sd" repeated 3 times
When I go into the Mount option it says Micro SDCard (0 MB) and you cannot select
Micro SDCard
USB-OTG
SD-EXT
If I select storage I get
Micro SDCard (0MB)
USB-OTG(0MB)
Use this. https://www.dropbox.com/s/fn8s3z6m7ttb3zk/5_6152376089848053798.img?dl=0
Hopefully u won't face sd issue on this one.
Problem is twrp doesn't recognize extFat and one other format I can't remember now but it recognizes ext4 and fat32 only just try this twrp.
And flash 20170905 build cuz it has no bugs. @challenger07
Thank you for the quick reply. I did try the new TWRP you sent but it was the same. I then tried Arun's TWRP 3.1.1 https://forum.xda-developers.com/dev...t/dl/?id=24849 which seems to be fine. I know you said there were issues with it but at least it sees the SD card. I've run out of time to swap the ROM will have to do that another day but wanted to know why you suggest the one from early September. When I look at the change log it would imply that the November release now has all the fixes in?
RR-N-v5.8.5-20171111-eyeul-Unofficial.zip
Thanks
challenger07 said:
Thank you for the quick reply. I did try the new TWRP you sent but it was the same. I then tried Arun's TWRP 3.1.1 https://forum.xda-developers.com/dev...t/dl/?id=24849 which seems to be fine. I know you said there were issues with it but at least it sees the SD card. I've run out of time to swap the ROM will have to do that another day but wanted to know why you suggest the one from early September. When I look at the change log it would imply that the November release now has all the fixes in?
RR-N-v5.8.5-20171111-eyeul-Unofficial.zip
Thanks
Click to expand...
Click to collapse
1st off big warning. Do not use arun's twrp to flash the rom. It will boot loop or not install the rom.
What u can do is format ur SD in a different format that is recognized by Tark's twrp like ext4 or fat32.
2nd why I suggested 20170905 and not 20171111 is cuz 20171111 is build after the kernel rebase and cause of that there is issues with the front camera. This all is already extensively discussed in HTC desire eye telegram group.
Basically, on 20171111 front camera lacks focus and front flash. Even if it's on latest security patch. U can fix the camera issue by flashing a custom boot img but then the Bluetooth would stop working so both are a loss of functionality.
On 20170905 has no such camera issues and everything works fine as it's the build before the kernel rebase.
If u r not too big on selfies then ya go with 20171111
If u want best of everything except latest security patch go with 20170905
ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open GApps :
Open Gapps Click Here
Choose Platform: ARM, Android: 10.0, and a Variant the one that have all you need, I recommend the nano pack but it may not have all you need so check before download.
TWRP For Quark:
TWRP Use laste Mod version that I release Click Here
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 10 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
Can't swipe/draw the pattern in lock screen : Screen lock pattern is set with the extra option of patterns "Directly show pattern view" and ambient display enable all at the same time, will bug ambient display for the wave or pick featuring of gestures, this doesn't bug when you received a notification, disable one or the other until the bug is fixed.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][10.x]LineageOS ROM for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community the quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 17.x
Version Information
Status: Stable
Created 2020-24-01
Last Updated Check Changelog click here
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up
duplicated
Really nice! Getting a battery replacement for my Droid so that it can work as a backup phone. Tysm for Android 10!
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
Inform what you are doing
The ROM is much much smoother than pie ROMs...Thank you so much bro ......Android 10 on this 6 year old handset is just unbelievable....
fgl27 said:
Inform what you are doing
Click to expand...
Click to collapse
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
And just the ROM? What happens
fgl27 said:
And just the ROM? What happens
Click to expand...
Click to collapse
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Thanks / Flashlight issue
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
fgl27 said:
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Click to expand...
Click to collapse
Yoiks! Not quite that tech savy. Even tried after a full wipe & zip-by-zip install. If I have to be happy with RR Pie, so be it. Not all that bad. My Turbo has some miles on it, rebuilt twice already. Got one last battery & display in the wings. Best, last phone Motorola made. Don't waste your time, further, on what's likely a hardware flaw.
Sent from my LM-V405 using Tapatalk
I think your not using latest twrp
newbe1droidx said:
I think your not using latest twrp
Click to expand...
Click to collapse
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Kinzhal said:
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
Click to expand...
Click to collapse
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
Einsteindks said:
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
fgl27 said:
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
Click to expand...
Click to collapse
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
noting crashing to me, sim or no sim.
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open Gapps
Choose Platform: ARM, Android: 11.0, and a Variant the one that have all you need, I recommend the Nano pack, but it may not have all you need so check before download, if any problem with a diferent version try the Nano before reporting issues.
TWRP For Quark:
TWRP Use laste Mod version from xda
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 18.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 11 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][Android 11] LineageOS 18.1 for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community, quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 18.x
Version Information
Status: Stable
Created 2021-30-05
Last Updated Check Changelog click here
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up
Everything was working great, until this weekend. I was in an old hotel that gets terrible signal, so i used WIFI the whole time. When i left to head in to work this morning, i noticed that my data never came back. I can make calls, send texts, get on WIFI, use bluetooth... but the 4g LTE icon is not on my top bar, and im getting "No internet connection" errors. --- I verified that Data is turned on, i have something along the lines of "LTE/CDMA/EvDo" selected, ive restarted the phone, and ive tried popping out my SIM card and reinstalling it. -- Any suggestions?
imcensored1 said:
Everything was working great, until this weekend. I was in an old hotel that gets terrible signal, so i used WIFI the whole time. When i left to head in to work this morning, i noticed that my data never came back. I can make calls, send texts, get on WIFI, use bluetooth... but the 4g LTE icon is not on my top bar, and im getting "No internet connection" errors. --- I verified that Data is turned on, i have something along the lines of "LTE/CDMA/EvDo" selected, ive restarted the phone, and ive tried popping out my SIM card and reinstalling it. -- Any suggestions?
Click to expand...
Click to collapse
I figured it out. I started playing with all the network settings, and i found one that allowed me to set the "access point". I found the access point somehow was set to "Xfinity", once i changed it to "Verizon" my data came back. I am not sure how it changed or why it changed, as it was working before I entered the no coverage zone.
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog
fgl27 said:
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Click to expand...
Click to collapse
I tried these fixes for the GPS a few times but no luck. Do you have any other ideas?
Thank you.
It's been awhile since I've had to deal with this issue. I forget exactly what I went through to get it resolved. Have you tried an absolute cold raw reinstall? Wipe everything in the phone except internal memory, from TWRP.
SecretPotatoChip said:
I tried these fixes for the GPS a few times but no luck. Do you have any other ideas?
Thank you.
Click to expand...
Click to collapse
Sorry I was busy didn't check xda for a while.
If those don't help the best option is to try Einsteindks from above post
On Android was added a update to the GPS libs that fixed most of the issue, that is way most don't have any issue anymore, but if you have one is probably something very odd that need a full clean to resolve.
Active display is not working. How do I turn it on?
DobrRk said:
Active display is not working. How do I turn it on?
Click to expand...
Click to collapse
Active display is a Motorola name.
Use Ambient display, enable it on settings -> system -> actions
fgl27 said:
Active display is a Motorola name.
Use Ambient display, enable it on settings -> system -> actions
Click to expand...
Click to collapse
Thank you very much. It is a pity that it does not work as on the old motorola, with a separate processor under this option. I really liked the firmware.
Power Functions was an awesome option on Motorolas, at one point. Shame they didn't carry over. At least other options exist. Neat idea, though. Good to see the display stuff be standard, albeit under different names.
Verizon just sent me this text. (Advanced Calling /HD Voice). I feel like I enabled this years ago. I went to search to turn it on and I see it's not an option. Is this something that was coded out of Lineage?
I know you have to activate it on your phone and then Verizon has to activate it on their end.
imcensored1 said:
Verizon just sent me this text. (Advanced Calling /HD Voice). I feel like I enabled this years ago. I went to search to turn it on and I see it's not an option. Is this something that was coded out of Lineage?
I know you have to activate it on your phone and then Verizon has to activate it on their end.
Click to expand...
Click to collapse
I believed HD voice needs VoLTE something that doesn't work in custom ROM
opengapps release they version for Android 11, I updated OP with the link.
Sometimes after not using my device from a few hours it became very slow the first few minutes I try to use it, some apps freeze giving me that warning "app is freeze kill it" or something like that, I notice that a lot of service don't run as they did on old version of android regularly on background, but they sometimes run all together when you wake the device up.
Most are service from google apps and frameworks, to improve this I'm using this new battery option that show on each app info, that allows you to enable "Background restriction" see attached.
You have to manually set to restrict each individually app that you wanna to be restricted, after I did to almost all available apps, notifications are working as expected and I don't have slows down at least not from service on the background.
If anyone has some issue related try to use those options to improve.
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog
Einsteindks said:
It's been awhile since I've had to deal with this issue. I forget exactly what I went through to get it resolved. Have you tried an absolute cold raw reinstall? Wipe everything in the phone except internal memory, from TWRP.
Click to expand...
Click to collapse
I went into TWRP, and wiped everything except internal storage and usb otg. My gps still does not work.
SecretPotatoChip said:
I went into TWRP, and wiped everything except internal storage and usb otg. My gps still does not work.
Click to expand...
Click to collapse
Next step would be to save internal on an OTG, along with ROM & Gapps, Titanium Backup, etc, eject/remove OTG. Get into TWRP, wipe ALL, plug in OTG, reboot into TWRP, install ROM, Gapps & modem reset zips after selecting OTG as source. Double check yourself along the way, trust me! It's easy to forget a step and have to re copy files onto the OTG from computer backup.