Database Info

[Q] How to get new language!

Hi guys!
Recently i buy this Photon Q 4G LTE Sprint to my wife's birthday.
It's a wonderfull device with a nice hardware, but the best is the external keyboard (She likes it, because his old device was Motorola dextr, and she was used to), but we're from brazil and my first difficulty was to find a rom that support drivers without bugs.
So here i was: My first try was MIUI. I unlocked my bootloader, rooted and installed TRWP. Didi Backup, formated and installed MIUI, :good:
First i tryed with Kernell the UFO developed for it, and the device don't boot. After i tryed just the rom, but it has no modem or wifi. So i flashed up the stock rom modem img and worked fine.
But apks like "retrica" doesn't work with it, bringing black photos and others apks made for instragram. I love this rom and i have installed in my Xperia Play. It works perfect, but in this device have a lot of bugs, so i give up.
I know how to use it with bugs, but not my wife. Then i had to try another one.
I downloaded Cyanogenmod CM10.1, CM10.2, CM11 nightly, snapshot. Then after try all "Xt897" roms, i tryed all "moto_msm8960".
I can't get in any of this roms make my wifi or 3G work. I believe that modem is not compatible. Even if i tryed to flashed stock modem after, i still had no signal at all. No IMEI, no MAC Address, nothing. :crying:
This device have few alternative roms, so i decided try to translate the rom with less bugs at all. I picked up the stock rom JellyBeans 4.1.2, but this was my second failure. A language patch is something that you don't find in market, and to disassembly entire rom and work in a translate is something beyond my knowledges.
So i have an answer to someone that know how to do a fix patch to wifi in cyanogenmod(Specific "cm-11-20140518-NIGHTLY-moto_msm8960.zip" ), or someone good in translate rom, or input a language in stocked rom, like The Solutor did in " [Full ICS ROM] Multilanguage/Toggle2g /STK/Tethering" (but the rom he used was 4.0.4 and it have bugs).
I will be grateful for any help. :fingers-crossed:

Hmm, what's the language you want (CM11 already have lots of them - not in the list?), and what WiFi/3G problem are you having? And you also failed to RSD the phone back to stock?
My recommendation is you first sort the RSD thing out and get the phone back to stock 4.1.2, and flash everything from that onwards. Assuming that you don't do anything wrong in the process, you should have no quirks with WiFi/3G.
Sent from Google Nexus 4 @ CM11

Try MoreLocale2 for the stock ROM language issues.
As for the CM issues... I agree with Andy, if it works in stock form, it "should" work on CM - at least that has been my experience.
You are clean wiping / factory resetting before or after flashing CM yes? I see you have done this step for MIUI, so I am thinking that you have already done this step...
If you have, can you provide logs from CM if the wiping/RSD'ing doesn't work?

Thx for help guys...
AndyYan - The language i need is Portuguese(Brasil) and it has on CM 11 and MIUI.
I did it as you said. I downloaded stock from here:
http://sbf.droid-developers.org/phone.php?device=3
Rom version: Android 4.1.2 - Blur_Version.98.10.5.XT897.Sprint.en.US)
And flashed by RSD.
Everything ok till here. No errors, nothing wrong. Wifi working as well, and the network.
My MIUI was taken from here: http://forum.xda-developers.com/showthread.php?t=2444449 (GSM one).
Cool rom, it has wifi and network, but camera bugs with some apks. For me ok, but not for my wife. So this rom was discarded.
CM i dwonloaded from here: http://download.cyanogenmod.org/?device=moto_msm8960
The last one was: cm-11-20140521-NIGHTLY-moto_msm8960.zip (i tryed all of then "XT897" and "moto_msm8960", but none of them could get my network working. No wifi, no IMEI, no MAC, no wifi).
CM was my hope, because it has my language, but in all tries i did the wipe in cache, dalvik, system, factory, even internal memory, before installing, and cache or dalvik after flash. I tried this in all (tried not wiping too) and still has no modem.
After this, just for try, i flashed stock modem "NON-HLOS.bin". Still got no modem in any CM roms.
arrrghhh - i did try "MoreLocale2" for the stock rom, and "Set Locale and Language" (and more). This softwares did a nice job for keyboards and apks, but system stays intact in english. It need to be a real translation for my wife.
My guess is that this issue can be easily solved.
If all JB roms have the same system(at least for "moto_msm8960" processor kind ).
This ROM is generic for Motorola Atrix HD, Electrify M, Photon Q, RAZR HD, and RAZR M right?
Razr HD is a type of phone that came to my country.
Is it possible compile a system from Brasil career stock, for this phone with modem and anything else from my stock rom? Does it will crash my phone?

Please provide logs from the latest build of CM after booting and attempting to engage/connect to wifi.

Logs??
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.

Skymidt said:
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.
Click to expand...
Click to collapse
CM does create logs. If you're not familiar with them, the easiest way is to use an app from the Play Store... which I'm not sure how you will manage without wifi or mobile data, and I assume you are not familiar with adb.
I can go thru the detail, but it's a bit involved. Perhaps this thread will help you?
Once you know how adb works, there's actually an easier method than using adb logcat to output to a file - there are logs stored in '/data/logger'. So:
Code:
adb root
So you can have the permissions to pull the files, then pull them:
Code:
adb pull /data/logger
Will pull all of the log files to wherever your command prompt is. If you 'cd' (change directory) to your desktop, doing the adb pull will send all the log files to your desktop.
Let me know if you have any questions, good luck.

Logs from Adb
Yeap! I'm familiar with ADB!!
(i'm not expert in it, but i already did something with that...)
I don't know exactly what are you lookin for, so i did two logs.
First a complete boot:
Code:
adb reboot system
adb logcat -v long > boot_log.txt
And one for especific modem log from boot
Code:
adb reboot system
adb logcat WifiStateMachine:E *:S -v long > just_wifi_error.txt
(I believe this this won't help u a lot?!)
The first one is the most complete solution for this and have all the boot infos, errors and other things.
If am i wrong please say the correct command to use.

I forgot something...
In filemanager i can't access internal storage.
It shows /storage/emulated/0, and points to nothing.
If i'm right, this was a well know bug on CM 10.2, which supposedly been fixed in CM 11 right?!
I think that information can help to solve this bug...

Please try the adb pull command I sent... Those logs are not very helpful, and quite difficult to read.
However, I have a feeling if you use RSD Lite to flash everything back stock, confirm it works, then start with the latest CM, I'd be curious if it works.
Also, someone mentioned they needed to install the CM10.2 snapshot before going to CM11 - or else BT and wifi did not work.

Eureca...
That is something that i didn't tried! I'd never flashed CM 10 in first!!!
I'm downloading "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip ".
Fisrt i'll flash stock "Blur_Version.98.10.5.XT897.Sprint.en.US" with RSD.
Then fastboot "logo.bin" (to avoid warning unlocked), and TRWP(my stock have a original recovery that can't install CM. I can edit XML, but to cleanse my conscience i'll let this way).
After i'll install "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip" with TRWP and boot with this one.
Then i'll flash "cm-11-20140526-NIGHTLY-moto_msm8960.zip ".
But i'll have to do this at night(it's 12pm here), because i'm working today.
If that don't work i'll pull the log that you said here, but I come back to thank.

Same problem
I confess I was hopeful in that case you said to flash first the CM 10.2.
But again failed. I tried two ways:
In both I tried to install the Snapshot CM 10.2, then the CM 11.
There is no way that cell boot with "CM 10.2" in any case. That saty on boot animation for several time(i waited 30 minutos each).
In the first I downgraded to version 4.0.4 stock to see if the modem worked.
After that i flashed CM 10.2 that stood in boot animation, then CM 11 booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.0.4.7z)
On the second attempt, I used the default stock 4.1.2.
After CM 10.2 which was stucked on boot animation again, then CM 11 again booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.1.2.7z)
Strange thing happened on both CM 11 boot. When the system's load, it shows a message "The clock stopped". This is strange thing for me.

Can you wait for CM10.2 to boot...? There is a fsck process which sometimes takes quite a long time to boot.
Also, for your FC issue - you are clean flashing the ROM everytime? You are doing a factory reset everytime you flash a new ROM?
Edit - looking at your logs, I don't think the fsck is the issue... something is causing the CM10.2 boot to die over and over. Please try clean flashing...

I clean everything before.
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?

Skymidt said:
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?
Click to expand...
Click to collapse
Yes, factory reset == clean flash.
As for the long boot, I'm not sure the fsck is your issue - basically there is a process which runs a disk check, and sometimes this will make the boot take quite longer than usual. I can't say how long, I've never personally experienced the issue.
However, the fact that CM10.2 isn't booting is a little disturbing. I've heard some people report 45-60 mins... can you do me a favor, charge up the phone, and try to let it boot for at least 90 minutes?
If at the 90min mark it still hasn't booted, pull logs and post them.
Thanks.

The logs contain references to apps that are present only in stock firmware.
That means the CM boot is actually not happening in a clean environment (the data wipe/factory reset in TWRP hasn't worked as it should?).
Please try to use OpenRecovery 2.09 instead of TWRP (as OR is the recovery I personally use and watch for possible bugs) to wipe the device and to install CM11 - http://forum.xda-developers.com/showthread.php?t=2211579&page=10
When installing CM in recovery, you will probably also want to install the gapps package - http://wiki.cyanogenmod.org/w/Google_Apps
Btw., CM11 expects the baseband (modem) and other partitions the be at the 4.1.2 stock level. Experiments with 4.0.4 are useless.
Please post the logs from CM11 boot.
You will need to enable the logger under CM11 by
Code:
su
setprop persist.log.aplogd.enable 1
in Terminal app or ADB shell, it's not enabled on CM11 by default.

Links are broken
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?

Skymidt said:
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48551561&postcount=75
I'm on an older version of TWRP, and it has never failed me... that's a shame really. I'll try to update and see what's what. In the meantime, flash OpenRecovery I linked above ^^.

Skymidt said:
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
Click to expand...
Click to collapse
TWRP 2.6.3.x should also work properly.
@arrrghhh, so you see it's not just me having the "wiping /data reboots the recovery" problem... I've already sold my PQ (might buy a new one in the future), but please do help let this problem be known to whoever's developing TWRP for us
Sent from Google Nexus 4 @ CM11

I can't believe it works
Unbelievable! :laugh:
This very simple solution worked for me.
My TRWP did not work right.
He said he had done successfully in cleaning the cache and manufactures, but did not.
I downloaded the link you guys sent me and it worked on the first try.
Not needed before installing CM 10.2. Already installed in the first CM 11, has worked with modem and everything. Now I can configure the GSM network my country and language of the country for my wife (PR-BR).
I want to thank the efforts of user @ AndyYan to respond, the attention given by the user @ Arrrghhh teaching me with patience, and the solution given by the user @ kabaldan. :victory:
You are awesome for this forum. Thanks for everything.
If you still want the log I get, but I think with everything working, you guys should already know the outcome.

[Q&A] [ROM][5.1.1] Candy 5 - Skyrocket

Q&A for [ROM][5.1.1] Candy 5 - Skyrocket
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1] Candy 5 - Skyrocket. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

hello
I changed my i727 to 5 candy lollipop , everything works except that appeals nobody hears me and I hear nothing
Here are the notes from phone
baseband i727ucmc1
Version 3.0.101 CyanogenMod - g0c7bddd
uMTS network
state service
current service
Homelessness: Homelessness without
state of the mobile network : offline
thank you for your answer
i have installed rom from sd card after wipe data and partitions
___________________________________________________________
new:
that's it, after two reboot it works; but I'm waiting still the problem will return, I install once "kitkat bluelighting 4.4.4" and "Slim-skyrocket - 4.4.4.build.6 - OFFICIAL-5252" "
everything worked very well
Thank you

Anaya Boom said:
hello
I changed my i727 to 5 candy lollipop , everything works except that appeals nobody hears me and I hear nothing
Here are the notes from phone
baseband i727ucmc1
Version 3.0.101 CyanogenMod - g0c7bddd
uMTS network
state service
current service
Homelessness: Homelessness without
state of the mobile network : offline
thank you for your answer
i have installed rom from sd card after wipe data and partitions
___________________________________________________________
new:
that's it, after two reboot it works; but I'm waiting still the problem will return, I install once "kitkat bluelighting 4.4.4" and "Slim-skyrocket - 4.4.4.build.6 - OFFICIAL-5252" "
everything worked very well
Thank you
Click to expand...
Click to collapse
This is a problem with most 5.1 roms. Mostly after using another audio app like hangouts phone,whatsapp phone,music players and video players. Driver is not released back too phone.Reboot is needed . On a good note, Paranoid Android 5.1.1 has just come out with an update and an audio patch that fixed mine. Hope this helps.

I don't get any signal
My phone after updating it to candy 5(5.1 Lollipop) I can't get any signal?
Please Help!

New to this
This is the best rom I have installed ever since fixing my bricked Skyrocket a couple weeks ago.
Latest Version 5/15:
After installing the latest update the data drops far less frequently... however it is still a good five times every twenty minutes or when I send two or more text messages. I tried rebooting, messing with wifi/airplane mode, removing excess APN's, and using Signal Boosters which are junk. Folders seem to be a bit different and overall rom is a bit more laggy compared to previous version. My recents menu did not work, holding the home button with no response, fixed by turning on OmniSwitch.
Installing SlipLP fixed the data, so I am confident you will figure it out for Candy! If only I digged the look of SlimLP.
Will report back next update, still learning how to Logcat... I will post if I figure it out tonight.
I am not getting any charging or heat issues like the poster above. I did not change to noop prior to writing this.

Found a PERMANENT signal fix!
Apparently this has something to do with the radio being flashed and 5.x.
Here is how you fix it, I have not had one drop in signal since my previous post!
(For AT&T, T-Mobile, possibly others)
1. Download the [UCMC1] I717 AT&T Radio
http://d-h.st/PKI
- official thread: http://forum.xda-developers.com/showthread.php?t=2228292
2. Either Clean flash or Recover from a backup of Candy 5.x
3. Install the AT&T Radio
Signal drop is fixed, select your APN and enjoy!
I suggest this for those who are using AT&T Servers, T-Mobile, or etc. If not visit here and find your carrier radio... http://forum.xda-developers.com/showthread.php?t=1785999
I hope this helps everybody! :good::fingers-crossed:
I am not a professional, I have been flashing custom for a couple years here and there! This is working on my device, I now have ZERO signal drops and perfect signal, please allow OP to further test.

requiredhq said:
Apparently this has something to do with the radio being flashed and 5.x.
Here is how you fix it, I have not had one drop in signal since my previous post!
(For AT&T, T-Mobile, possibly others)
1. Download the [UCMC1] I717 AT&T Radio
http://d-h.st/PKI
- official thread: http://forum.xda-developers.com/showthread.php?t=2228292
2. Either Clean flash or Recover from a backup of Candy 5.x
3. Install the AT&T Radio
Signal drop is fixed, select your APN and enjoy!
I suggest this for those who are using AT&T Servers, T-Mobile, or etc. If not visit here and find your carrier radio... http://forum.xda-developers.com/showthread.php?t=1785999
I hope this helps everybody! :good::fingers-crossed:
I am not a professional, I have been flashing custom for a couple years here and there! This is working on my device, I now have ZERO signal drops and perfect signal, please allow OP to further test.
Click to expand...
Click to collapse
Thanks, yes the UCMC1 radio or newer is needed for this. It is one of the last versions available for the Skyrocket. My Slim threads have this but I didn't see that mentioned here, so I have updated the OP.
Cheers!

Preinstalled App
Does this ROM has Apollo music player installed?

Hunter661 said:
Does this ROM has Apollo music player installed?
Click to expand...
Click to collapse
It has CM's Eleven music player. You can install whatever you want, Google Music, XenoAmp, etc.

GAPPS
Everything is working on my Skyrocket SGH-I727R but when I want to install gapps from my recovery it says it successful but I can't find google play when I installed the zip. Do I need to use a different GAPPS file?

Candy 5 v2.5.3 onto skyrocket I727 as well as I727R)
tried to update from v2.5.1 .Got Google play bug .
Then did a full wipe and installed on both units with slim Gapps .No more chance .same error .When back to prvious version from restore .
Should we be able to update from the previous 5.1.1 buid v2.5.1 ?
Thanks

Twisterboy669 said:
Everything is working on my Skyrocket SGH-I727R but when I want to install gapps from my recovery it says it successful but I can't find google play when I installed the zip. Do I need to use a different GAPPS file?
Click to expand...
Click to collapse
Michel177 said:
tried to update from v2.5.1 .Got Google play bug .
Then did a full wipe and installed on both units with slim Gapps .No more chance .same error .When back to prvious version from restore .
Should we be able to update from the previous 5.1.1 buid v2.5.1 ?
Thanks
Click to expand...
Click to collapse
Make sure you are using an up-to-date version of GApps. Recommended is Slim's Zero GApps (~60MB), a link to which you can find in the OP.

Google Cards
The google now widget I can't find under the widgets tab is their anyway to retrieve it?

Minor Question
How would you update the 2.53 version to this one?

Twisterboy669 said:
The google now widget I can't find under the widgets tab is their anyway to retrieve it?
Click to expand...
Click to collapse
When you flash the ROM, either the GApps package you flash needs Google Now (might be Google Search, not sure), or you need to install it from the Play Store separately. Voice input on the AOSP/Google keyboards may be missing as well until you do.
I partitioned my Skyrocket to have a 6GB Data partition so the tiny GApps is fine and I can install pretty much all I want for apps. It's quite nice.
Twisterboy669 said:
How would you update the 2.53 version to this one?
Click to expand...
Click to collapse
Wipe Dalvik and Cache in recovery
Make a nandroid backup
Flash the ROM
Flash either Slim Zero GApps or a very small base GApps package
Reboot
Have fun!

Flashing Potential Issue
I am currently Flashing the ROM using TWRP and everything seems good it's just that its stock on "Patching system unconditionally" It's been on that step for about ten minutes. I did the Cache and Dalvick Cache wipes. So I Don't know what I did wrong.

Twisterboy669 said:
I am currently Flashing the ROM using TWRP and everything seems good it's just that its stock on "Patching system unconditionally" It's been on that step for about ten minutes. I did the Cache and Dalvick Cache wipes. So I Don't know what I did wrong.
Click to expand...
Click to collapse
Then it sounds like there were core changes which may require a full wipe (/data or a factory reset).
I normally clean flash to test, so unless I've made a change that I know requires a full wipe, or coming from another version (5.0 vs. 5.1, etc.) I would suggest to try dirty first and see. If you get stuck, as you have, then I'd go clean.
Sorry for any inconvenience...

NoSpamDan said:
Then it sounds like there were core changes which may require a full wipe (/data or a factory reset).
I normally clean flash to test, so unless I've made a change that I know requires a full wipe, or coming from another version (5.0 vs. 5.1, etc.) I would suggest to try dirty first and see. If you get stuck, as you have, then I'd go clean.
Sorry for any inconvenience...
Click to expand...
Click to collapse
When I down graded bak to 2.5.3 It flashed perfectly. So do I just wait for the next update or is their a solution because none of the methods you mentioned to me are working. I backed up my data and did a full factory reset.

Twisterboy669 said:
When I down graded bak to 2.5.3 It flashed perfectly. So do I just wait for the next update or is their a solution because none of the methods you mentioned to me are working. I backed up my data and did a full factory reset.
Click to expand...
Click to collapse
Have you wiped /system in the process?
Have you formatted your device with ODIN using a PIT file, or have you used any virtual partitioning?
Post your recovery log. You can export it from TWRP.

NoSpamDan said:
Have you wiped /system in the process?
Have you formatted your device with ODIN using a PIT file, or have you used any virtual partitioning?
Post your recovery log. You can export it from TWRP.
Click to expand...
Click to collapse
Nvm, Sorry I forgot about the dirty flashing and it worked. Thank you

[ROM] [DEV ABOOT ONLY] [OFFICIAL] CyanogenMod 13.0 MM [KLTEVZW] [Nightlies]

CM 13.0 has gone official for kltevzw. I may post a test build here or there to this thread, but otherwise get your builds from download.cyanogenmod.org
Code:
*** Disclamer
-- You install these at your own risk! You are responsible for anything that happens from flashing these files to YOUR phone! If your phone melts into a pile of goo, catches on fire etc. IT IS NOT MY RESPONSIBILTY BUT YOURS!
FAQ:
Q: Can I use this?
A: Do you have a developer aboot? If so then yes, but I won't help you install a developer aboot. I only ever had a Developer phone, so I only know the process as well as reading the thread. See this thread for info/help: HERE
Q: Why does my phone reboot when I try to make a call?
A: Your default dialer got changed for some reason. Maybe you installed a gapps package that replaced the dialer with Google Dialer or your default dialer somehow else got changed. Stop that: Settings -> Apps -> (Gear Icon) -> Default Apps -> Phone App -> (Select Phone).
Click to expand...
Click to collapse
Recovery:
I recommend the test1 recovery here by @jcadduono. This is the only TWRP I've found that handles adopted storage, MTP, and encrypted userdata.
The only caveat is that if you encrypt userdata then adopted storage doesn't work correctly. You won't be able to see /sdcard, so to flash things you either need to copy what you need to a safe place (/cache or /data/media/0 are both good options) or use an app like Flashify which does that for you.
Click to expand...
Click to collapse
Modem/Firmware:
Most of the LP modem/firmwares should work, but I use the one PB1 here. This modem matches with the proprietary vendor files that are part of the build. Flash it in ODIN. You must fully poweroff your phone before booting into download mode for any modem flashes to take.
https://www.androidfilehost.com/?fid=24459283995308895
Click to expand...
Click to collapse
GApps:
CyanogenMod recommends Opengapps. I use Opengapps mini, but feel free to use whatever you would like, even non-Opengapps. Make sure to use an ARM 6.0 version.
http://opengapps.org/
Click to expand...
Click to collapse
Downloads (the thing you were looking for):
Unless I post a test in-thread, everything you need will come from Cyanogenmod.
CM-13.0 kltevzw Official nightlies
Click to expand...
Click to collapse
Does/Doesn't Work:
Same as the other klte* devices. I'd suggest tracking the below thread and participating in it.
http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-13-0-android-6-0-t3237502
And yes, bluetooth is glitchy. It's less glitchy when you turn off WIFI and ensure there aren't apps (WeatherBug is apparently a culprit) using/polling BT. When I get a free moment I may try to dig in and see if I can find something.
And yes, WIFI can sometimes drop when the screen is off. That's a Google AOSP thing.
Click to expand...
Click to collapse
Thanks:
Everyone on the CM team. This is 99% CM with just a couple tweaks to make it build, boot, and run for KLTEVZW. See Post 2 for those changes.
Click to expand...
Click to collapse
Android Version: 6.0.1_r46
I forgot something. I know I did. I'll try to update this post sometime.

More things...
Source
Unless otherwise noted (test or other), builds are all 100% CM source for filename dates (UTC build dates) of 20160409 or later.
Cyanogenmod github: https://github.com/cyanogenmod
My github: https://github.com/haggertk
Click to expand...
Click to collapse

Works perfectly! Thank you, thank you, thank you! I have been waiting for marshmallow for so long...

Question
Works for any verizon S5?

RichyValents said:
Works for any verizon S5?
Click to expand...
Click to collapse
FAQ #1 - any that has a dev bootloader, whether that is because you bought the device with one or whether you used the tools (provided you had a Samsung emmc) in the linked thread to flash one.
Sent from my SM-G900V using Tapatalk

so how do i go about installing this on my device that is now with developer mode

Download the ROM, make a backup in twrp, and install in twrp

Voice and SMS are not working after flashing. LTE data works however.....

I found that waiting, toggling airplane mode and data worked. Glitch free ROM once you get it dialed in.

Curious, can you both confirm to me what baseband version is being reported in Settings -> About Phone?

I wonder if they're set to the wrong network mode. I remember that being an issue auto selecting wrong on past cm roms.

talktosamson said:
Voice and SMS are not working after flashing. LTE data works however.....
Click to expand...
Click to collapse
In the bootloader thread you mention flashing a 122715 version of CM13. Where did you get this? If you got any version from anywhere other than my AFH dropbox (https://www.androidfilehost.com/?w=files&flid=52843) then things may not work correctly.
The symptoms make it sound like you have a standard klte version, not one of my kltevzw versions -- klte is a GSM ROM and it's init.cpp doesn't initialize CDMA properties like is done here.

If I am on PB1 already and rooted and unlocked to developer, should I bother with the PB1 firmware? I verified again just for good measure and I am on PB1.

thewebsiteisdown said:
If I am on PB1 already and rooted and unlocked to developer, should I bother with the PB1 firmware? I verified again just for good measure and I am on PB1.
Click to expand...
Click to collapse
If you confirmed that your baseband is reporting PB1 then there really is no need. Install a version of TWRP, at a minimum format /system, format /cache, wipe /data, and start installing the ROM and gapps.
A full factory reset would be even better then just wiping /data as far as starting fresh, but that erases /data/media (internal storage) and you may not want to jump that far.

How do I install the pb1?

coopmaster said:
How do I install the pb1?
Click to expand...
Click to collapse
If your about phone says you have PB1 baseband then you don't have to.
If you don't have that baseband, boot your phone to download mode and flash the .tar.md5 (containing just the modem and non-hlos) in the AP (or PDA if older version) slot of ODIN.

haggertk said:
If your about phone says you have PB1 baseband then you don't have to.
If you don't have that baseband, boot your phone to download mode and flash the .tar.md5 (containing just the modem and non-hlos) in the AP (or PDA if older version) slot of ODIN.
Click to expand...
Click to collapse
Thank you

Factory reset and noticed that it stated it was skipping /data/media and I was like meh, I installed anyway and it booted after optimizing the apps and everything worked and works. Awesome sauce! Thank you everyone!

haggertk said:
Curious, can you both confirm to me what baseband version is being reported in Settings -> About Phone?
Click to expand...
Click to collapse
Just replying back, I've got it nailed down now. Wasn't sure what the issue was, but it's all good now.

So one question how do i go about updating for each nightly build? do i just flash over it and everything should be fine or ?

June LineageOS build cannot establish data connection with updated bootloader

Coming here for help since the LineageOS subreddit basically told me to **** off since the Note 5 build is unofficial, I hope you guys can help me out a bit more than them.
I just got a new TMobile Note 5 (SM-N920T) and wanted to get the latest CyanogenMod on it, so I went with the only builds of LineageOS I could find (I think the only two builds I found for the 920T came from here on XDA) I could never get the later June build to properly install, only the older March build, so I used that for a while until I ran into several bugs I was hoping to fix.
I looked more into the update and found my N920T was using an old bootloader (UVU4DQC2), and I needed to update it to one of two newer ones (UVU4EQE1 or UVUEQC6, I went with EQE1). The only way I could find to update it was flashing a newer stock ROM, so I did, got it set up real quick, checked the options and found I was indeed using the new bootloader. During this time, I had noticed my 4G LTE data was coming through just fine. After making sure I was on the new version, I put TWRP back on the device, wiped, flashed LineageOS June build (which succeeded), Open Gapps, and rebooted. After which during setup I found I could no longer access any mobile data connection at all.
I checked the usual suspects, APN was set up to properly use TMobile LTE, LTE was set as my preferred network, I reset data connection and enabled then disabled airplane mode, restarted and repeated the previous steps, to find I couldn't find any way to get the data working at all. I looked up online, but the only fixes I could find were to check the APN settings, reset them, and to reinstall root (which I tried to no avail).
After this I gave up on the June build and reinstalled the March build, which I found now also had the same problem. The only difference being that it was now using the EQE1 bootloader instead of the DQC2 version. Same fixes applied with the same results. I only could fix the issue by eventually rolling back to a backup of the March build with the DQC2 bootloader.
Probably the only thing I have left to try is installing the other accepted bootloader and seeing if that will work, but the other version I believe is for the universal/international build, not the TMobile build, so I'm not sure it will be any better. I like LineageOS and I want to keep it if I can, but at this point it's being a major pain to deal with with the bugs and no data on the bugfix build. I would appreciate any suggestions, let me know if there's any information you guys need to know.

I used the lineage port by Raymanfx for months. What you need to do is roll your baseband back in Odin (flash the firmware package) of the firmware T-mobile released in May. After flashing that, get TWRP back on your device and flash the June build by rayman.

Metabolic12 said:
I used the lineage port by Raymanfx for months. What you need to do is roll your baseband back in Odin (flash the firmware package) of the firmware T-mobile released in May. After flashing that, get TWRP back on your device and flash the June build by rayman.
Click to expand...
Click to collapse
If you're referring to the builds in this thread as posted by RaymanFX then those are the ones I'm currently using and having issues with.
That said, I'll still give it a shot. I found some stock builds on samsung-firmware here and it looks like the only TMobile specific releases are either well before may (N920TUVS4DPH2 August 2016), or a few months after (N920TUVU4EQE1 May 2017, the one I'm currently having issues with). I can alternatively try either of the two versions that were released specifically in March 2017 (N920TUVU4DQC2 the one I started with, and N920TUVU4EQC6 I think this is the other one that the June Lineage build supports, but it's not TMobile specific).
Which would you recommend? I'm thinking the EQC6.

I use updato.com no speed restrictions and the server never goes down.
N920TUVU4EQE1 is the firmware you want.

Metabolic12 said:
I used the lineage port by Raymanfx for months. What you need to do is roll your baseband back in Odin (flash the firmware package) of the firmware T-mobile released in May. After flashing that, get TWRP back on your device and flash the June build by rayman.
Click to expand...
Click to collapse
I went ahead and tried that with the EQC6 build only to get the same results as with the EQE1 build. Any suggestions? I feel like there must be something different I'm missing here.

Metabolic12 said:
I use updato.com no speed restrictions and the server never goes down.
N920TUVU4EQE1 is the firmware you want.
Click to expand...
Click to collapse
I'll give it a shot, but it'll have to wait until later tonight when I'm back home. I'm almost out of data for the month so I can't download it while at work.

Alright. If you have anymore problems just PM me or if you want some help.
MufinMcFlufin said:
I'll give it a shot, but it'll have to wait until later tonight when I'm back home. I'm almost out of data for the month so I can't download it while at work.
Click to expand...
Click to collapse

Metabolic12 said:
Alright. If you have anymore problems just PM me or if you want some help.
Click to expand...
Click to collapse
I went ahead and tried out the updato build, and I'm still running into the same issue, so I figured I'd try to list what I'm doing (in as much detail as I can manage) to make sure I'm doing everything as I should be.
1. I'm using ODIN 3.10.6 (can't find an official site that doesn't look sketchy, I just found my download link through a bunch of tutorials), TWRP 3.1.1-0 nobleltetmo, Open Gapps for ARM64 Android 7.1 Micro variant, and LineageOS June build as uploaded by RaymanFX here on XDA.
2. Download Updato UVU4EQE1 build, and extract file from archive.
3. Start up ODIN, click AP, and select file from the UVU4EQE1 archive, then wait the ~5 minutes for it to check the md5 hash, meanwhile doing step 4.
4. Turn off device and start it back up in download mode (Power + Home + Vol. Down), confirm the security check (Vol. Up), then plug device into computer.
5. After md5 finishes, click Start and wait for ODIN to install the stock ROM with UVU4EQE1.
6. Phone will restart into the newly installed stock ROM, go through first startup quickly to verify 4G LTE data is working and that you have the correct baseband (UVU4EQE1)
7. Shut down device and start it back up in download mode again.
8. In ODIN, click Reset, then AP, and select the TWRP img.tar (twrp-3.1.1-0-nobleltetmo.img.tar) file
9. Click Start, and be ready to restart device into Recovery mode (Power + Home + Vol. Up) once the screen turns off, as installing TWRP takes only a few seconds
10. Restart device into newly installed custom recovery (TWRP)
11. Move the LineageOS .zip file onto the device as well as the Open Gapps .zip.
12. In TWRP, select Wipe, and confirm.
13. Then in TWRP, select Install, choose your LineageOS .zip file, and confirm.
14. Go back to main menu of TWRP, select Install again, choose Open Gapps .zip file, and confirm.
15. Reboot into newly installed LineageOS June Build using Baseband UVU4EQE1, and begin first startup.
These are just about the exact steps I follow when trying to install LineageOS. Am I missing something I should be doing or otherwise doing something wrong?

If you have any experience with Win-Rar and Notepad++ you can open the updater script and change the supported bootloader's to the newest (EQG3) bootloader. That's what I did, but most don't have the experience with those programs. Using the newest baseband, you have the latest security features and better performance.

Metabolic12 said:
If you have any experience with Win-Rar and Notepad++ you can open the updater script and change the supported bootloader's to the newest (EQG3) bootloader. That's what I did, but most don't have the experience with those programs. Using the newest baseband, you have the latest security features and better performance.
Click to expand...
Click to collapse
I think I remember seeing how to do that a few days ago, will give it a shot.

If you have any questions just let me know bro

Metabolic12 said:
If you have any questions just let me know bro
Click to expand...
Click to collapse
Found the file just fine, went ahead and just replaced EQC6 with EQG3. I flashed the EQG3 build, but ran into some very odd behavior upon booting. I got the usual Note 5 screen, Samsung, and TMobile screens (TMobile stuck around for a long while as usual), but after TMobile, I got a black screen, then a notification that System UI app has crashed, and I was stuck on a black screen after hitting Ok. I could hit the power button and I'd get the usual stock "Shut down/Restart" options, so I went ahead and tried that so I could try the LineageOS flash regardless of that odd behavior, but I ran into an error with "Invalid ZIP format". I'm gonna guess that 7zip inserted itself another signature file to say "This archive was made with 7zip!" which made the phone act weird. Gonna try a few other things with that LineageOS zip.

I had that same problem. Download Win-Rar and get the free trial. Repack the files into .zip format and you should be good to go. The problem you had with flashing the firmware in Odin is you have to NandErase All, which wipes everything, and turn off auto-reboot. Most people don't know you have to manually boot the phone into recovery twice after using Odin and flashing a firmware.

I found the issue was actually because I accidentally put the folder all the files were in into the archive, so it was .zip/folder/meta-inf, etc. so once I moved everything from the folder to the root archive, it worked just fine. Besides that, not sure exactly what you mean by booting the phone into recovery twice. I've been doing download mode twice (one for stock rom, second for TWRP), but I've only ever been doing recovery once (install LineageOS, Open Gapps, then reboot to system). The only time I ever tend to boot twice into recovery is when I'm reinstalling root after the initial startup.

Metabolic12 said:
Most people don't know you have to manually boot the phone into recovery twice after using Odin and flashing a firmware.
Click to expand...
Click to collapse
So what are the two times you have to manually boot into recovery after Odin? I can only think of one time during the process it's necessary to boot into recovery, when installing LineageOS then Open Gapps.

I meant only when flashing back to stock.
MufinMcFlufin said:
So what are the two times you have to manually boot into recovery after Odin? I can only think of one time during the process it's necessary to boot into recovery, when installing LineageOS then Open Gapps.
Click to expand...
Click to collapse

So I went ahead and tried flashing the EQG3 ROM, using the NAND Erase setting, and for some reason it fails to boot now. I gave it a solid 10 minutes to try and it's stuck on the T-Mobile logo screen. So after giving that enough time, I went ahead and tried putting TWRP back on so I could revert to a backup, and for some reason TWRP now fails to mount internal storage so I can't put the backup file back on the device. I tried several other builds of the stock ROM and all builds appear to fail to boot. Do you have any suggestions? The only things I can find online are saying to factory reset, which doesn't appear to make a difference, since this is failing on its startup boot, not after an update.

Don't know what the issue was exactly, but I somehow fixed it. I tried several options for wiping data on TWRP and eventually found that for some reason "Format Data" right next to "Advanced Wipe" worked. Reflashed TWRP and finally have access to internal storage again. Now I'm back to the old issue of no data on the June LineageOS build once again even with the EQG3 baseband.

Lineage OS 14.1 Release 1 (uploaded January 17 1025pm eastern)

Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!

beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631

wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.

Awesome work! I've finally got me a full featured daily driver

I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...

After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.

Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk

I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..

This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.

I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.

Any update?

pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.

Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.

won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated

whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance

gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.

derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.

Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.

elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH

derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.