Develop Bugs

[NIGHTLY][ROM][2.3.7][GWK74] CyanogenMod 7 for Samsung Galaxy S

This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Galaxy S.
All Samsung Roms are running ontop of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you're not able to flash any kernel or run any filesystem you want. Use it as it is.
Only data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix").
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
INSTRUCTIONS:
- First time flashing CM 7 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from earlier CM7?
Do a Nandroid Backup!
Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=galaxysmtd
Compatible Radio Images (>= Nightly 15): http://codeworkx.de/download/cyanogenmod/
Supported devices: GT-I9000, GT-I9000M, GT-I9000T
before flash is recommended to check the md5sum
FREQUENTLY ASKED QUESTIONS:
http://forum.cyanogenmod.com/topic/24169-faq-cm7-on-the-samsung-galaxy-s/
CYANOGENMOD WIKI:
http://wiki.cyanogenmod.com/index.php?title=Samsung_Galaxy_S
HOWTO BUILD FROM SOURCES:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_GalaxySMTD
ADDITIONAL INFORMATIONS:
Maintainers:
- atinm - http://twitter.com/atinm
- codeworkx - http://twitter.com/codeworkx
- coolya - http://twitter.com/dumdidum
- guiperpt - http://twitter.com/guiperpt
- unhelpful - http://twitter.com/unhelpfulone
Irc:
- Host: irc.freenode.net:6667
- Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
- Generic Changelog
- CyanogenMod Source Twitter
- Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!

If You Have Any Questions, Please Refer To This
CM7 QUESTIONS & ANSWERS XDA THREAD
http://forum.xda-developers.com/showthread.php?t=1067074​
Regards,
~drz

have i ever told you i love you? i'm pretty sure i have but i'd just like to tell you again. i'm sorry for this offtopic post but i'll edit it later to something useful. just wanted to show my affection.

This should be it since the beginning.

Clean thread. That's how I like it
Excited for the Coming Soon patch!
Reboot Recovery

Woah! Can't wait to try this.

The quick troubleshooting post.
This post contains a compilation of problems/issues and answers provided in this thread and earlier threads. Not all answers are tested by me and I will in no way guarantee that this wont mess up your phone.
You know, watch your kittens. They might be eaten by following the advice written down here.
DETAILED INSTALLATION INSTRUCTIONS CAN BE FOUND HERE.
rschenck wrote a very nice (and updated) guide for how you install CM7 on your SGS these days.
Things have changed quite a bit recently, so even if you installed it two weeks ago, you may want to check this one again.
What do people mean with "correct" bootloader? How can I make sure I have the right one?
Do NOT install directly on top of existing Samsung 2.3.3 firmwares or other firmwares based on this (like Darky's 10). Similarly, don't install directly on top of Eclair.
See this very easy guide on the android soul for flashing XXJPU, which is Froyo with the correct bootloaders needed..
I'm not sure I understand these procedures. Can you draw it out for me?
Anticipating this very question, rschenck actually did draw out a flow-chart for you.
See here.
But I'm not using the I9000, I'm using something else...
codeworkx provided a reference list you can check to ensure you are getting the right files.
After flashing the initial CM kernel I can't get CWM Recovery to work. It just displays some weird image
CWM Recovery might have different keymappings from the ones you are used to.
- Volume keys: Naviagte up and down in menus
- Power button: Select item
- Home key: Show/hide menus
If you are only seeing a weird image, chances are you've hidden the menu by pressing the home key. Try pressing it again
I can't find Cyanogenmod nightlies in ROM Manager
Yes. CM7 for the SGS is now mainlined and supports ROM Manager for nightlies, should you have the premium version. If you have the Premium version, follow these very graphic instructions to configure ROM Manager for nightlies.
To install from MIUI (courtesy of runedrune)
- Reboot into recovery using 3-button-combo
- Choose "mounts & storage" and format system, data, cache, datadata
- Do not apply the initial-file.
- Apply the latest update
- Apply the latest gapps (which can be obtained here. You want the one with -gb- in the name )
- Done. Reboot
Odin doesn't recognize my phone anymore and I want this fixed in case I mess something up
You will probably need the Nexus S drivers (which supposedly is really just some updated Galaxy S drivers).
If Odin for some reason don't see your device when connected, make sure the old Galaxy S drivers are uninstalled and removed. Bilboa1 gives some good hints about how to make sure your drivers are actually fully removed. Do check this before proceeding to install the Nexus S drivers.
After you have installed the Nexus S drivers, plug in your phone. Windows should now install some drivers, but you are not done yet. When using download-mode your phone will show up a little differently to Windows, so put your phone in download-mode and plug it in, with neither Kies nor Odin running. You will probably see Windows installing some more drivers.
After doing this, Odin should hopefully be able to recognize (and flash) your phone.
IS THIS "FOR EVERYDAY USE" NOW?
It depends. If you have to ask, it probably isn't.
I've flashed this and decided it is not ready for me. How do I flash back to stock ROMs?
Get the appropriate firmware you are interested in, flash as usual using Odin, but check re-partition and use the 512 pit-file.
For pre-rooted stock-images, you can use EZBase as shown here (also includes download links).
OTHER STUFF / KNOWN ISSUES AND SOLUTIONS
Please take a look here to see if your issue is mentioned and has a known solution before posting.
After flashing CM7 I get strange colours on my screen during boot
You do not have the correct bootloaders. Basically flash 2.2.1 following this article and then redo the CM7 installation. All should be fine.
Guys! Guys! I cannot find Android Market!
Google stuff is not included in CM7 by default. Download and apply latest gapps from CWM. You want the "universal" one with "-gb-" in the name.
But I want the latest gtalk with video and all that fancy stuff
got_milk was nice and uploaded some stuff. Beware though that lots of people are reporting this to force-close a lot, and that's not just on SGS CM7.
Can I run Samsung apps like Memo, Camera etc on this firmware?
No. Sorry. All Samsung apps depend on TouchWiz libraries which can only be found in Samsung firmwares.
How do I get additional themes for CM7 themes chooser?
Check the themes forum here on XDA or search for "CM7 themes" on Android market.
Once installed, the themes will be available in the themes chooser yes. According to the devs should reboot to fully apply the theme, but if you want to avoid reboots Android market might have something for you.
Things used to work, I applied a nightly update and now everything force-closes
Try wiping cache and dalvik cache in CWM. You should do this every time you install a new update.
Does CM7 need a lagfix?
CM7 uses ext4 (for /data) and yaffs2 (for everything else). CM7 does not use Samsung's RFS which was the main cause of poor performance on Samsung firmwares.
So no, your system is already lagfixed, you don't need to apply a lagfix and according to the developers very bad things will happen if you try to apply one anyway.
My current ROM has a lagfix. Do I need to disable that?
Probably not.
If you have a 2.3.3 ROM with 2.3.3 bootloaders, you will want to do a full wipe to stock 2.2.1. See above. In this case you no longer have a lagfix anyway and don't have to worry about it.
If you have a non-2.3.3 ROM with a lagfix, you don't have to disable it. All your partitions will get wiped by the installer anyway and so will your lagfix.
For whatever reason, I want to flash a custom kernel
You can use custom-kernels, but CM7 is a work in progress with new kernel-revisions popping out with every release. Make sure you flash a kernel which is compatible with the nightly you are running. Also: Do NOT flash via Odin, flash via CWM.
rschenck has a very good post on this.
If all you want is a "voodoo kernel" for voodoo sound, just (buy and) install Voodoo Control Plus from the market. It will load the required kernel-modules while you can stay on the stock kernel, making the lives of the developers much easier should you encounter bugs.
Is it possible to flash my own CSC from recovery after installing cm7?
According to the devs, this should not be needed.
Flashing other modems/radios
(Courtesy of GrimVarg: http://forum.xda-developers.com/showpost.php?p=13399590&postcount=8117 )
Odin will not work and it might **** **** up. The reason is that Odin and heimdal does not understand the CM partition layout and will just write the modem where it thinks is should be. Overwriting other stuff in the process.. So you need to use the specific update zipfiles on teamhacksungs sourceforge page
Click to expand...
Click to collapse
Instead of using Odin, download radio-packages from the following link, transfer to your phone and flash via CWM:
http://sourceforge.net/projects/teamhacksung/files/galaxys/
I want to keep my 850 band, and I don't recognize any of the modems on the sourceforge page
Lorssoth says "use KC1" and robbiev80 posted some download links you might be interested in.
Does external SD card work with cm7? Thanks!
It does. Make sure you have the proper bootloaders before installing as mentioned in the first part of this post. EZBase can be used for this.
External SD card will get mounted as /mnt/emmc. This may not be visible to all apps. If you desperately need the contents visible to apps only looking in /mnt/sdcard, create an empty directory there and remount the /mnt/emmc there as well:
Using either the terminal emulator or adb shell:
Code:
su
mkdir -p /mnt/sdcard/external_sd
mount /dev/block/vold/179:9 /mnt/sdcard/external_sd
Note: This is only a temporary fix for when needed. It will cause issues when you try to use USB sharing later. Write the following to get things back to normal:
Code:
umount /mnt/sdcard/external_sd
USB sharing doesn't work
Try installing the Nexus S drivers, instead of the Samsung ones.
After installing this camera doesn't work
Try locking and unlocking your phone. No really.
After installing this I cannot get any data-connections apart from wifi
There is a problem with RIL (radio interface layer)-polling. Lock and unlock and you should be OK.
If this sounds cumbersome, mobilescooby claims that installing Juicedefender somehow fixes this for him and that he no longer needs any lock and unluck boot-rituals.
This issue should now be resolved.
After doing this I still cannot get any data-connection apart from wifi
You might need to configure APN settings. Normally your network-provider will have this information on their homepages and some even offer to send them to you over the network.
After installing this I cannot send and/or receive MMSes
See above: You might need to configure APN settings. Check your provider.
After installing CM7 I cannot connect to my wifi-network
It might be related to what channels you have enabled on your phone. If your wifi network is using channel 12 or higher, you may need to enable those channels on your phone.
Go to Settings/Wifi & Network/Wifi settings/Advanced/Regulatory domain. And try not to be in violation of local laws with regard to channel usage
After installing CM7 I cannot connect to 802.1x EAP Wifi networks
This is seemingly an issue with lots of custom kernels and even some of the Samsung Firmwares. Yours truly can't get it to work at all, not on CM7 nor Samsung's JVB firmware.
Other people have reported that forgetting the network and adding it manually, by entering the SSID (with correct casing) and filling in all the details themselves have solved their problems.
YMMV
After installing CM7 I cannot charge my phone to 100%. WTH
No actual firmwares allows you to charge the battery to 100%, but stops a little bit before it reaches that point. This is to protect the battery from overcharging and should (in the long run) give you much better battery-life.
While stock firmwares from Samsung shows that the phone is 100% charged, this simply isn't true and is just UI-candy to make you all feel comfy. It's really charged to something around 94-98 percent.
So if your phone stops charging around that point, everything is normal, and the only new thing is that your phone is no longer lying to you
My GPS performance is terrible
Welcome to the world of Samsung Galaxy S GPS flux. Things you can try to improve on this includes the following:
- Install faster fix from Android market. Ensure you have the best time-server for your area chosen.
- You can also try AngryGPS, which siberian tiger was nice enough to upload.
- If all else fails, you can also try to flash a radio with a good GPS reputation. For flashing radios, see the appropriate section of this post. For some detailed post about the different radios eeyunopper posted this link and this link. (With ZSJPG I am getting decent result, YMMV)
Auto brigthness is kinda not-worky
You can try the presets outlined by Arkymedes right here.
How do I configure proxy settings?
(Thanks to runedrune)
If you are used to looking for proxy settings under Settings/Wifi & Network/Wifi settings/Advanced, you wont find it there.
Using either Launcher pro/ADW Launcher or another launcher which lets you create shortcuts to activities:
* Long hold on some open space on your launcher
* Select (Custom) Shortcut
* Select Pick your activity/Activities
* Scroll down to settings and click this
* Scroll down the long list and you should find proxy settings
You now have a shortcut to configure proxies as usual.
This "headphones mic on mute + instant music after call bug" is really irritating
If you are using Samsung or Nokia headsets, this is due to a problem on their part. See Arkanius' post right here.
Other things I should be aware of?
- Don't use 2G/3G data-switching. Period. At least not while the data-connection is active.
Not trough widgets, tasker or any other means. Seriously. Should you do this, you might end up having to restore nandroid backups or doing factory resets.
This report has details on more sophisticated ways of cleaning up which may lead to less data-loss, although not everyone can get it to work.

*subscribes*
nice work with the GPIOs, camera and other parts !

Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...

eeyunopper said:
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
Click to expand...
Click to collapse
I've already notified the mods to close / lock the other one ...

Good job on the clean house, everything is working great on my phone and very speedy

Mortify1 said:
Good job on the clean house, everything is working great on my phone and very speedy
Click to expand...
Click to collapse
The same for me My phone is working so great and very very speedy

Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!

Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
format /system /data /cache /datadata and then flash the latest update and the latest gapps.

I'm waiting the upcoming improves on camera in great expectation.

Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
no
after format system/data/cache
just apply the last update

runedrune said:
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
Click to expand...
Click to collapse
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?

Nice things are comming... I hope for battery improvemant and radio FM. Since we got GPS, Compass is not so important but nice additional that save battery/make quicker fix.
Codeworks, do you got any rodemap?

Tantrico I said:
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Click to expand...
Click to collapse
nope. just flash that file. i made the same switch from miui to cm7 two days ago

@codeworkx , if reboot in recovery works = nightlys updates for ROM Manager? !
Enviado desde mi GT-I9000 usando Tapatalk

[ROM] Very Unofficial BeanStalk 4.4

Since this is still in the alpha testing stages, I'm not going to go with a big OP with all the details. Once we get CM-11.0 working well enough to be used as a daily driver, I will rewprk the OP..
Here it is though, Bean Stalk 4.4. ALPHA.
I know there are issues, but cannot fully test everything myself. So, I need you guys to help us out. I need logs and descriptions of the issues you find. I will update post #2 with bugs, downloads and changelogs as they come in.
Installing:
Make a nandroid backup, then test you nandroid backup.
Wipe, data, cache, dalvik
Wipe /system
Install ROM
If you desire, install gapps. Although, the last version I tested was so laggy it wasn't worht flashing gapps.
Booting back to recovery is a pain in the butt to say the least. But if you boot the ROM, hit the menu button, select System Settings, go to developer options, check the box for Advanced reboot, hold the power button until the options box appears, select reboot, recovery. This will easily boot you into recovery so you can restore your nandroid backup. BE PATIENT! Like I have already stated, the ROM was very laggy when I tested the initial build.
How to get logs:
There are 3 logs that I/we need, logcat, last_kmsg, and dmesg.
For a logcat, it will take some patience:
Once ROM is booted, go to System Settings, Developer Options, tap root access and select Apps and ADB, scroll down a little further and check the box for Android debugging. Then on your computer in terminal type:
Code:
adb logcat
Then manually copy the output to a file on your computer. Upload the output to pastebin.com and post a link in this thread. Please be as descriptive as possible with your findings.
For dmesg log:
Flash and boot ROM
Play with the ROM for a bit, I would suggest enabling adb and debugging, and advanced reboot options during this.
DO NOT TURN OFF THE PHONE
Boot into recovery
Make sure /system and /data is mounted
In terminal type:
Code:
adb shell
dmesg
Then manually copy the output to a file on your computer. Upload the output to pastebin.com and post a link in this thread. Please be as descriptive as possible with your findings.
For last_kmesg:
This log is a raw version of dmesg. If you pulled a dmesg, then there isn't much of a need to pull this one. However, there maybe instances that you cannot pull a dmesg. If you encounter this, make sure /system and /data is mounted. In terminal type:
Code:
adb shell
cat /proc/last_kmsg
Then manually copy the output to a file on your computer. Upload the output to pastebin.com and post a link in this thread. Please be as descriptive as possible with your findings.
Some things to note:
When I say "In terminal type", I mean on your computer.
When I say "manually copy the output" that means click on edit on the menu bar of terminal and choose "select all", copy it, open gedit and paste it in there and save the file with an appropriate name.
If someone has already posted the same issue(s) and has provided a log, there is no need to post anything, unless I ask for another log.
Optional:
In an attempt to help things a long a bit, you can make a nandroid of this ROM. Then, when you flash an update, you can restore that nandroid, wipe /system, then flash the update. This will save your settings for adb and advanced reboot.

Downloads, changelog and bug tracker
BeanStalk-4.4015-20131212-p930.zip
This is the initial tester. I'm not going to post any bugs or issues until I get feedback from you guys.

thomas.raines said:
BeanStalk-4.4015-20131212-p930.zip
This is the initial tester. I'm not going to post any bugs or issues until I get feedback from you guys.
Click to expand...
Click to collapse
Good job! Thanks for your work!

[TWRP][any G4][BL LOCKED] TWRP-in-FIsH for all LOCKED G4 devices

TWRP on locked devices is impossible right?
Oh no wait there are hacks up to KK which work but I couldn't find anything for LL (sorry if I missed something) and so nothing for the G4
Here is where the FIsH steps in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FIsH: [F]luffy [i]ncredible [s]teadfasterX [H]ijack​
FIsH is different from Safestrap or other hijacks because it should be understood as a kind of framework for any boot image you want to boot.
FIsH will not harm the Android boot chain!
It is NOT multirom
It is NOT efidroid
It is NOT Safestrap
It is NOT twrp.
.... but FIsH can boot any of the above. U got it? FIsH is the hack to boot whatever you want.
Will FIsH void your warranty? Not more or less then rooting your device.
Will FIsH unlock your bootloader? No read again.
Is there a risk with FIsH? For example could it soft-brick my device? Well.. absolutely! Safe is the death only. There are always risks especially for untested devices. I do all I can to keep this risk as low as possible and I provided a way to get out of bootloops but again you will get no guarantees here and elsewhere.
.. and it is more then just a hack for the G4 (any model) it is a hack for ALL devices of ANY vendor! wtf? yes.
Sure you have to met the pre-requirements and there has to be done some things to get it ported but those are straight forward.
Go to IRC channel #androidfish if u can't wait but I will publish a public porting guide when it is ready.
Are there plans to make more out of it for the G4? Absolutely. I'm currently working on an "efidroid in FIsH" version which will let you flash & boot (hopefully) any custom ROM u like.
ALL DETAILS ABOUT HOW FIsH WORKS HAVE BEEN RELEASED IN ANOTHER THREAD (check my signature).
So going back to topic. This is:
TWRP in FIsH for the LG G4 (any model) - Bootloader LOCKED
Do you have a bootloader unlocked device?
If the answer is YES: you don't need it
Do you have a bootloader locked device and want TWRP?
If the answer to BOTH is YES. you need it. you can't install TWRP on a locked device.. up to now. FIsH allows you to do so.
If your question is: Can this ENABLE root for my device?
NO! you actually NEED root to activate TWRP for your device with this method.
Important: Here are the pre-requirements you have to met!
If you can't get them:
Close this page and FORGET it (until the day you may met those reqs)!
Requirements!
root by SuperSU >=v2.76 (greater or equal v2.76) (atm this means you have to downgrade/install LL. It also means that you have to upgrade your SuperSU to this version by e.g. FlashFire if you have a lower version installed!)
you have to be able to disable SELinux in your booted Android (which should be the case when you have a full rooted device)
Those above are hard facts so it may never work with MM. That also means if MM can get fully rooted by SuperSU and you can use "setenforce 0" the method should work there as well!
Before you think about downgrading to LL read about ANTI-ROLLBACK protection some LG devices and MM versions may have!
Anti-Rollback means you CAN NOT downgrade - it would brick your device.
I will NOT provide downgrading guides there are plenty of them so search and read.
If you can not meet ALL of the above 2 requirements lay down and cry. For the others: calm down and read on!
You can test requirement 2 (disable SELinux) by:
adb shell
su
setenforce 0
getenforce
-> you should see "Permissive" as a result. If you see "Enforcing" or error messages you may doing something wrong or it just do not work for you.
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader.
That means with TWRPinFIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = soft brick. for this u need "efidroid in FIsH" - coming soon)
Install a custom Kernel (this will modify boot = soft brick)
Install a custom recovery (this will modify recovery = may soft brick)
In short: nothing which modifies boot or recovery partitions.
You can of course flash everything which is modifying /system /data only (e.g. xposed,...)
That means you could install even a custom ROM which works with the stock kernel so with unmodified boot image. Let's say the creator of imperium or genisys provide a release without the containing boot image. You could flash it..
State / Roadmap
FULL takeover/hijack of boot -> DONE (the modifications required are not voiding the Android boot signing chain!)
replace RAM disk -> DONE
boot own RAM disk (TWRP!) -> DONE (atm TWRP 2.8.7-0) <-- TWRP-in-FIsH v1.0 private BETA
Upgrade bundled TWRP to latest version -> DONE (TWRP 3.1.0-0) <-- TWRP-in-FIsH v1.0 final release
Download
READ THE REQUIREMENTS above before proceeding!
Then UNDERSTAND the requirements before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
READ THE LIMITATIONS above before proceeding!
Then UNDERSTAND the limitations before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
... and NEVER ask for ETA's!
if you can say:
Yes! I have read and totally understood the limitations AND the requirements!
then proceed. Otherwise read again until you got it.
Keep in mind that this is a HACK. It may soft-brick your device. you have been warned!
The concept is the same for all models but again no guarantees here for anything.
There is ALWAYS a risk and you should better backup what you do not want to loose before starting downloading this.
Go to the DOWNLOADS tab in this thread.
TWRP-in-FIsH is now integrated into my TWRP build server and so whenever a new change happens in TWRP you will get the same automatically on next build. This way it is much easier to release new TWRP versions made for FIsH.
From now on you will find nightlies (untested automatic builds) here:
Jenkins build status
Nightlies download server
Installation (Linux)
You can just install any newer version over an old one.
boot Android and connect USB cable
download the newest version to your PC and open a terminal in that directory
tar xzf TWRPinFIsH*.tgz (tar xzf TWRP-in-FIsH*.tgz since v2.0)
cd openFIsH (cd android_FIsH since v2.0)
./install.sh
check the output of that script. you should not see any errors there (hopefully)
Installation (Android / no PC)
Requirements:
TWRP-in-FIsH v4.2 or higher!
BusyBox pre-installed (e.g.: with this app )
You can just install any newer version over an old one.
Thanks to @ReeS86 starting from v4.2 on TWRP-in-FIsH has an enhanced installer which can run without any PC - directly on your Android device!
It would be nice if you could give him a thx click (here) for his contribution !
Bring TWRP-in-FIsH to your Android device
Example-1 with any PC (windows, linux, ...): adb push TWRP-in-FIsH.tgz /sdcard (replace TWRP-in-FIsH.tgz this with the real file name)
Example-2 within an Android Terminal:
cd /sdcard
wget http://full-URL-to-file (replace full-URL-to-file with the real direct download link)
Example-3 with just a browser: well just download it.. but remember where it gets saved!
extract it
Example from within Android Terminal:
cd /sdcard (or the folder where you have downloaded TWRP-in-FIsH)
tar xzf TWRP-in-FIsH.tgz (replace TWRP-in-FIsH.tgz this with the real file name)
run the installer (but do it correctly)
Example from within Android Terminal:
su
cd /sdcard/android_FIsH
sh ./install.sh (using sh is absolutely important otherwise it will fail)
done
Installation (Windows)
If none of the above methods is working for you: use FWUL
First run (no PC required)
This FIsH gets installed PERMANENTLY! That means:
You can boot up TWRP the same way as described here again without re-installing.
If you re-install your STOCK image you have to re-install TWRPinFIsH as well.
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH has done it's job well!
This is a good time to do a full backup isn't it ? Manually mount the SYSTEM partition as it gets not auto mounted atm and do a full backup
reboot from here (safely ignore the msg "no OS installed" and reboot anyways) and you should see Android booting (hopefully ... if not see bottom)
Daily Usage (no PC required)
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH is doing it's job still very well
AGAIN: keep your mind up! You HAVE to ensure that whatever you do and whatever you flash -> NEVER TOUCH BOOT/RECOVERY! If you flash a ZIP ensure first that it do not modify them! Otherwise you WILL softbrick. You have been warned (several times now)
FIsH helpers
If you just want to reboot directly from within Android check out these:
Thanks to @sdembiske who has onboarded the developer @AntaresOne we have an option to reboot into FIsH very comfortable now!
Check it out here: QuickReboot App
Trouble / Bootloop fix
if you encounter a bootloop (should never happen but who knows) you have 3 choices at least:
Option 1a: (TWRP-Bootloop) Within TWRP open Advanced -> File Manager -> Goto: /system/su.d and click "select" button -> Delete
Option 1b: (TWRP-Bootloop) From your PC: adb shell rm -rf /system/su.d/
Important: Catch the fish log (see next topic)
Option 2 (this works also for a bootloop without twrp): boot into download mode and use LGLaf to get a shell
then:
setenforce 0 <-- if that doesn't work you may have to do a FULL restore to stock
mount -oremount,rw /system
rm -rf /system/su.d/
reboot. You are out of the bootloop.
Important: Catch the fish log (see next topic)
Option 3: Last resort: Reflash STOCK. sorry.. there is always a risk..
Catch the FIsH logs
reboot back to Android and catch the fish log (IMPORTANT!):
adb shell "su -c cat /cache/fish/fish.log"
adb shell "su -c cat /cache/fish/fish.log.old"
Upload it to https://paste.omnirom.org and paste the link in the IRC channel (see next topic)
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support there only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you be asked for a server network choose: freenode
Known issues (may never get fixed)
Due to the fact that TWRPinFIsH is a brutal hijack of the booting process several things may not work as expected.
This will normally not harm anything but you have to know about.
System IMAGE backup:
Using this new option is a bulletproof method to backup and restore in TWRP-in-FIsH because you have to keep in mind that FIsH is a giant and brutal hack and even when a usual backup & restore is proven to work fine I would recommend to use both backup methods - if you can.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
@sdembiske reports success using the internal storage as target for the backup but if you do this keep in mind that you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
ZIP / ROM flashing:
omg really you wanna hear that again? OK: DON'T TOUCH BOOT / RECOVERY. And you be safe.
When you try to install a ROM it will modify at least BOOT. That means soft-brick!
When you try to install a custom Kernel.. omg really? It will definitively SOFT-BRICK! Maybe you should read the limitations again??
When you try to install a ZIP like xposed, supersu, Vipermod and others ensure that those are not modifying BOOT or RECOVERY partitions. For those mentioned it would be very unlikely but who knows.
When you find a stock based ROM which is not modifying boot you can flash it. But ensure that it does not modify anything on boot!!! You could ask the devs of imperium etc if they can provide such a zip..
SYSTEM partition (since v2.0: may be not a restriction on your device model!):
when you boot into TWRPinFIsH you may see an error message regarding the fact that /system cannot be mounted.
you can mount /system manually without a problem - BUT - it will work only if you do NOT select "mount system read-only". It has to be unchecked to work.
after you have mounted /system manually and you want to take a backup you may see "0 bytes". Just press refresh and the size will be updated. If not: Do you have mounted it correctly (see above).
FIRMWARE partition (since v2.0: may be not a restriction on your device model!):
cannot be mounted - even not manually. You have to live with it.
Double Tap to wakeup (in TWRP):
You may heave seen/heard that this works in the official / usual TWRP for the G4 for unlocked devices. Unfortunately this cannot work in TWRP-in-FIsH due to the nature of this hijack. You have to live with it.
Installing more than 1 ZIP at a time (may be not a restriction on your device model!):
It is not possible to install more than 1 ZIP at the same time. TWRP gives you the option to install multiple ZIP files but the problem is you have to re-mount /system after each ZIP flashing. This is due to a problem with mounting /system readonly and most ZIPs will exactly try to do this when they finished their work - leaving you with an unmounted /system.
This will be not the case for every ZIP combination - so it is possible that you can flash some ZIPs at the same time while others not.
atm I believe you have to live with it.
Credits (without them - no TWRP-in-FIsH!!!)
If you feel that someone / you is missing on this list lemme know!
Chainfire for SuperSU! This is the main part of FIsH!
TeamWin for TWRP of course!
@cray_Doze, @dssmex and @KeiranFTW for their hijack implementations which given me many input (e.g. https://forum.xda-developers.com/showthread.php?t=2608408)
@Aaahh for his great first steps to a G4 hijack -> His work had given me the motivation back to continue when I was about to stop all this
@dibbled for creating the android FIsH logo
steadfasterX for being steadfast!
@jasonlindholm for your donation it was highly appreciated!
XDA:DevDB Information
TWRP-in-FIsH_LGG4, Tool/Utility for the LG G4
Contributors
steadfasterX, Aaahh, TheMadScientist420, KeiranFTW, cray_Doze, dssmex, TeamWin, ChainFire, the_naxhoo, SimoxTav, Rees86, uio88, sdembiske, jasonlindholm, ... and all new other contributors who gave me feedback for this!
Source Code: https://github.com/Carbon-Fusion/android_FIsH
Version Information
Status: Stable
Current Stable Version: 4.2
Stable Release Date: 2017-06-21
Current Beta Version: 5.0
Beta Release Date: 2017-12-19
Created 2017-03-14
Last Updated 2017-12-19

List of confirmed devices (as of 2017-06-04)
If you own a device missing on this list - let me know and I will add it here.
F500L Korean variant - locked (Thanks @Syntist)
H810 - locked (Thanks @shane87)
H812 - locked (Thanks @ReeS86)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test with PURE stock and without touching the boot chain so its similar to locked devices.)
H815 EUR - locked (Thanks @uio88)
H815P - locked (Thanks @KnightOdin)
H815T - locked (Thanks @the_naxhoo)
H815L - locked (Thanks @foxyfoxyblah)
H818P - locked (Thanks @SimoxTav, @alitavas)
LS991 Sprint - locked (Thanks @TheMadScientist420)
VS986 - locked (Thanks @g_ding84)
List of confirmed flashing experiences (as of 2017-05-19)
If you tested a ZIP missing or unknown on this list - let me know and I will add/update it here. Write the exact version tested would be helpful as well.
Xposed - confirmed to work (tested: Xposed version 87 (SDK 21). THANKS for your report @g_ding84, @the_naxhoo, @KnightOdin, @shane87)
Viper4Android - confirmed to work (tested: Viper4Android 5.4 stock zip with Dolby Atmos. THANKS for your report @g_ding84 , @the_naxhoo, @SimoxTav)
SuperSU - confirmed to work (tested: v2.79. Thanks for reporting @g_ding84)
A.R.I.S.E - confirmed to work (tested: v.2.94 -> Am3d Eq, Viper4arise, Viper4Android Xhifi, Esira. Thanks for your report @alitavas
Android O emoji package - confirmed to work (thanks for your report @alitavas)
Editing system/build.prop - confirmed to work --> read carefully HOW (thanks for the howto & report @sdembiske )
Xtreme music 9.2 - confirmed to work (thanks for your report @jason_l367)
ANY OTHER ZIP - unknown ----> Please report back if you have flashed one missing here

Releases
TWRP-in-FIsH v5 (5.0)
Released: 2017-12-19
Download: Go to the Downloads tab
Changelog for FIsH: previously used version <---> this version
Changelog for TWRP-in-FIsH device tree: previously used version <---> this version
Changelog for:
- TWRP v3.2.0-0
- TWRP v3.2.1-0
Summary changelog (read the above FULL changelogs for details!):
new TWRP version
all important fixes from the main TWRP releases like corrected time and EFS backup, added Bootloader backups etc.
Many enhancements and fixes in FIsH, e.g. enhanced and fixes issues in the installer and qseecomd (device encryption) added to the brand new exclude service option
Everything is better now
Old releases:
TWRP-in-FIsH v4 (4.2)
Released: 2017-06-21
Download: Go to the Downloads tab
Changelog for FIsH: previously used version <---> this version
Changelog for TWRP-in-FIsH device tree: previously used version <---> this version
Changelog for TWRP: v3.1.1-0
Summary changelog (read the above FULL changelogs for details!):
Installer is now able to detect and run from within Android* (read the NOTES in the OP - topic "Installation (Android / no PC)"!)
Added the option to backup /system as an IMAGE* (read the following HINT!)
Using this new option is a bulletproof method to backup and restore in TWRP-in-FIsH because you have to keep in mind that FIsH is a giant and brutal hack and even when a usual backup & restore is proven to work fine I would recommend to use both backup methods - if you can.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
@sdembiske reports success using the internal storage as target for the backup but keep in mind that if you do this you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
Everything is better now
(.... TWRP updated, many FIsH improvements, added an option to backup /system as image,... read ALL the above changelogs!)
TWRP-in-FIsH-v3_LGG4_LL
Released: 2017-04-16
Download: here
Changelog: on github
Summary:
Big speed improvements
adding model detection as property (ro.product.detection -> should be "success")
fixing unify detection
adding all known devices to unification
- these both above will fix issues where your device was not detected correctly in TWRP and fails to install a ZIP which requires this!
Installer:
./install.sh --check will give you the option to check if TWRP-in-FIsH works for your or not - without changing anything on your device.
TWRP-in-FIsH-v2.0_LGG4_LL
(as far as im able to remember.. i have changed so many things inside..)
Released: 2017-03-24
Changelog: on github
Summary:
TWRP-in-FIsH now has a meaningful package name (TWRP-in-FIsH-v2.0-BETA1_LGG4_LL.tgz) which reflects all required information
The installer is checking for the SDK level now instead of the Android release version! This means ANY Lollipop version will work without modifications of the installer
new: completely overworked WIDE parts of FIsH
In order to be more easy portable all variables users may need to adjust are moved to FIsH.porting
while FIsH.me contains global variables for FIsH a user/dev normally would NOT change.
The log has been enriched with some more useful information
The stopping of android services is now more aggressive
Apropos aggressive: now we use fuser to kill ALL processes before trying to unmount a disk (excluding init and ourself)
Another porting stuff was added: we extract the FISHFOOD but WITHOUT a possibly existing file </init>. When you prepare your own ramdisk it may or may not contain a file /init but we do not want to overwrite the current running /init by just cpio yet.
The reason is: it makes a difference in the Linux world to use cp or mv or cpio > to overwrite!
The short version: using mv is the best choice here. So we extract first without /init (if there is one) and then extract /init ONLY but to a different directory. Afterwards we use mv to overwrite the current /init with either an extracted /init or your own init name configured by the new FOODBIN variable.
Unfortunately this has not that positive effect I hoped but I leave it there because it is the way it should be done nevertheless.
Now FIsH also:
- checks the exec bit before it tries to start it! Im still thinking of adding a reboot if not.. but this could cause bootloops.. on the other hand doing nothing will leave the device in a unusuable state.. well it should more or less never happen though but..
- save the current SELinux mode
- trying to restore the saved SELinux mode when something goes wrong (at the end this will make no sense but it doesnt hurt)
- umounts when a mount point is mounted ONLY
Besides that FIsH now comes with callmeFIsH - a caller script which gets executed at very first.
The only task callmeFIsH has is to prepare the whole FIsH to get started out of /system and then starting FIsH from /res. After this it immediately exists to not keep open tasks on /system.
Also new are some parts of the installer e.g. starting adb server first and then wait for a connected device before continue the installation.
The installer is keeping track of an older FIsH install and removes the previous one before as well
The installer also now giving a hint that you may have to change to PTP mode on your G4 to get detected
For completeness: Same TWRP version inside so nothing changed here..
During these changes I have renamed the package folder from openFIsH to android_FIsH. Please keep this in mind when you extract the FIsH
So after you extract the BETA package you have to do
"cd android_FIsH"
instead.
TWRPinFIsH_v1.0
Released: 2017-03-18
Changelog:
first public release
.

As current. To further op. When released remeber bl is still locked do not modify recovery and or boot partitions. Will throw secure boot errors done tried and found out. Was able to restore orig boot and recovery images.
On ls991.
So lets get our flash on. I wanna see some good clean flashing and no hits below the bootloader

TheMadScientist420 said:
As current. To further op. When released remeber bl is still locked do not modify recovery and or boot partitions. Will throw secure boot errors done tried and found out. Was able to restore orig boot and recovery images.
On ls991.
So lets get our flash on. I wanna see some good clean flashing and no hits below the bootloader
Click to expand...
Click to collapse
Well .. Correct. For me it is totally clear but this will be not for the average user maybe.. I will add it to the OP. Thx
Sent from my LG-H815 using XDA Labs

Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!

Jkmoran said:
Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!
Click to expand...
Click to collapse
2 posts up.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Jkmoran said:
Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!
Click to expand...
Click to collapse
Yes and no. I flashed viper 4 android. But because of signed bl. Any recovery or modified boot image will not work just yet. Still a wip.

Reserved. I hope to install this in my H815p soon...

TheMadScientist420 said:
2 posts up.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Yes and no. I flashed viper 4 android. But because of signed bl. Any recovery or modified boot image will not work just yet. Still a wip.
Click to expand...
Click to collapse
Hey i just want to say thanks for acknowledging thqt i helped you more than what happens in the sprint thread. I have a post 2400 views where i tore my g4 down 3 days after purchase to show a thermal paste mod. 2400 views and 1 thanks. Id thank u properly but unfort ive hit my 8 thanks a day limit
---------- Post added at 07:25 PM ---------- Previous post was at 07:22 PM ----------
Newmak said:
Reserved. I hope to install this in my H815p soon...
Click to expand...
Click to collapse
It will come in due time. The third release was sent out in one day. Progress is moving rite along my friend.
Some of us have been waiting since day one. I have about 15 months. Or nov 15 we are all anxious for offic release. And please make sure to give the man his cr3dit where due. Took time out of his day to do a team view session to test on mine at like 5 am this mornin. Some of the greatest minds have not been able to do this. And now look. Lol all the nay sayers
---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------
Newmak said:
Reserved. I hope to install this in my H815p soon...
Click to expand...
Click to collapse
sorry i didnt actually answer ure ?
this should work on all g4s and possibly many other lgs and or devices

I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.

tmihai20 said:
I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.
Click to expand...
Click to collapse
No read the OP again (wait for efidroid-in-FIsH).

tmihai20 said:
I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.
Click to expand...
Click to collapse
Lol op and about 4 or 5 posts up. Same ? Just asked.
Either was locked bl or not this is a majpr victory for the g4. They said it couldnt be done and

Hopefully You could port this also to G Flex 2?

dadaa1 said:
Hopefully You could port this also to G Flex 2?
Click to expand...
Click to collapse
he has stated should work on any android device running loli as long as u meet the prequisites
root and kernal set to permissive if he doesnt some one probly could adapt it from here no prob once its offic released
---------- Post added at 06:36 AM ---------- Previous post was at 06:04 AM ----------
dont know how much feed back uve been gettin but figured id chime in again
so after all night playing lol still sick as a dog cant sleep about 4 hours on 2 days feel high and drunk lol
ive do have to mount system everytime i load twrp to backup restore or flash but i flashed viper flashed xposed again just to check it out
bricked about 10 times and have restored perfectly everytime.
bricks my own fault trying and testing most def incompatible mods and fixes but so far through every brick recovery is holding strong and steady havnt installed the beta 3 yet
should i is much changed from there?

TheMadScientist420 said:
he has stated should work on any android device running loli as long as u meet the prequisites
root and kernal set to permissive if he doesnt some one probly could adapt it from here no prob once its offic released
---------- Post added at 06:36 AM ---------- Previous post was at 06:04 AM ----------
dont know how much feed back uve been gettin but figured id chime in again
so after all night playing lol still sick as a dog cant sleep about 4 hours on 2 days feel high and drunk lol
ive do have to mount system everytime i load twrp to backup restore or flash but i flashed viper flashed xposed again just to check it out
bricked about 10 times and have restored perfectly everytime.
bricks my own fault trying and testing most def incompatible mods and fixes but so far through every brick recovery is holding strong and steady havnt installed the beta 3 yet
should i is much changed from there?
Click to expand...
Click to collapse
Thanks for ur ongoing support here. please always go to IRC if possible:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,http://webchat.freenode.net/?channels=androidfish)
Whenever you have to choose a channel it is: #androidfish
When you be asked for a server network choose: freenode
.

Just wanted to let you know the current device list.
If you own a device missing in this list send me a PM with subject FIsH !
Please do not write me if your device is shown here already!
List of confirmed devices (as of 2017-03-15)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test without touching the boot chain so its similar to locked devices.)
LS991 Sprint - locked (Thanks @TheMadScientist420)
H815T - locked (Thanks @the_naxhoo)
H818P - locked (Thanks @SimoxTav)
H812 - locked (Thanks @ReeS86)

steadfasterX said:
Just wanted to let you know the current device list.
If you own a device missing in this list send me a PM with subject FIsH !
Please do not write me if your device is shown here already!
List of confirmed devices (as of 2017-03-15)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test without touching the boot chain so its similar to locked devices.)
LS991 Sprint - locked (Thanks @TheMadScientist420)
H815T - locked (Thanks @the_naxhoo)
H818P - locked (Thanks @SimoxTav)
H812 - locked (Thanks @ReeS86)
Click to expand...
Click to collapse
Nice work Waiting my Flex 2 LGH955 to arrive from warranty, I hope this can be ported to "LG Damed" locked flex 2 also

With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?

nikomedes said:
With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?
Click to expand...
Click to collapse
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader.
That means with TWRPinFIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = soft brick. for this u need "efidroid in FIsH" - coming soon)
Install a custom Kernel (this will modify boot = soft brick)
Install a custom recovery (this will modify recovery = may soft brick)
In short: nothing which modifies boot or recovery partitions.
You can of course flash everything which is modifying /system /data only (e.g. xposed,...)

nikomedes said:
With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?
Click to expand...
Click to collapse
Yes, with Efidroid you should be able to flash Custom ROM.
You can search about efidroid if you want to know more.
and thank you very much @steadfasterX , Good job bro ! :good:

[ROM][All Quark][10.x]LineageOS

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][All Quark][Android 11] LineageOS 18.1

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.