• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Lineage OS 13 Alpha 4 (Updated March 13 537am eastern)

also you need a few modded hardware/qcom folders, until the kernel gets updated to play nice with caf sources:
audio-caf: https://github.com/touchpro/android_hardware_qcom_audio-caf
display-caf: https://github.com/touchpro/android_hardware_qcom_display-caf

Sorry if this is a noob question, but I have never had to do this before and I just wanted to clarify...To get these modded hardware/qcom folders, do I just need to flash the zip files from those links before I attempt to flash the rom?
 
  • Like
Reactions: whoshotjr2006
Upvote 0
Sorry if this is a noob question, but I have never had to do this before and I just wanted to clarify...To get these modded hardware/qcom folders, do I just need to flash the zip files from those links before I attempt to flash the rom?

Nope. Dont try to flash anything but the rom zip, gapps and supersu. Those are just dev trees that you would need for compiling this if you wanted to. Those links are stuff thats already integrated into building the rom zip so no need to worry about them unless your trying to build this or some other rom from source.
 
  • Like
Reactions: bkttk2 and AP2FTW
Upvote 0
alpha 4 is up. repos are synced as of now.

manual network selection is now working thanks to kangs from the g3, but still no lte yet. im getting closer and hope to have data working sooooooooooner than later.
since your the maker/porter of this rom maybe you can help me? ever since i flashed this rom and restored a backup in twrp wifi and bluetooth haven't been working for me. even restoring with a kdz did not work but switching back to lineage it works fine.
 
  • Like
Reactions: whoshotjr2006
Upvote 0
since your the maker/porter of this rom maybe you can help me? ever since i flashed this rom and restored a backup in twrp wifi and bluetooth haven't been working for me. even restoring with a kdz did not work but switching back to lineage it works fine.

i really have no clue bud. i havnt had that happen and havnt heard of it happening to anyone else yet.

what software version were you on before you flashed lineage? I was on v20k and the kernel and firmware in this rom are based off of v20k. If I were you I would try to find the v20k kdz and use LGUP to flash it, see if you can use the refurbish setting instead of upgrade, but obviously do whichever one it lets you. remember, i did say in the OP that you should probably be on v20k to avoid issues since I havnt had any being on that version before I flashed.

while your in the stock rom backup you took, you should use adb and see if /firmware/image/ exists and make sure that wcnss.b0* and wcnss.mdt exist. there should be like six entries in there that say wcnss.something. if they arent there, that could be the issue since those are firmware files for bluetooth and wifi and you might have to take them from lineage or another stock rom and place them there or in /vendor/firmware/ after making an insecure boot image for your stock rom that lets you remount system as rw.
 
  • Like
Reactions: herminiachristian
Upvote 0
i really have no clue bud. i havnt had that happen and havnt heard of it happening to anyone else yet.

what software version were you on before you flashed lineage? I was on v20k and the kernel and firmware in this rom are based off of v20k. If I were you I would try to find the v20k kdz and use LGUP to flash it, see if you can use the refurbish setting instead of upgrade, but obviously do whichever one it lets you. remember, i did say in the OP that you should probably be on v20k to avoid issues since I havnt had any being on that version before I flashed.

while your in the stock rom backup you took, you should use adb and see if /firmware/image/ exists and make sure that wcnss.b0* and wcnss.mdt exist. there should be like six entries in there that say wcnss.something. if they arent there, that could be the issue since those are firmware files for bluetooth and wifi and you might have to take them from lineage or another stock rom and place them there or in /vendor/firmware/ after making an insecure boot image for your stock rom that lets you remount system as rw.
i have wcnss.b0 wcnss.b01 wcnss.b02 wcnss.b04 wcnss.b06 wcnss.b09 wcnss.b011 wcnss.b0 and wcnss.mdt but still not working, also wouldent falshing a kdz from a diffrent device would cause a permabrick?

edit:to add i was on MS63110j before flashing
 
Last edited:
  • Like
Reactions: whoshotjr2006
Upvote 0
i have wcnss.b0 wcnss.b01 wcnss.b02 wcnss.b04 wcnss.b06 wcnss.b09 wcnss.b011 wcnss.b0 and wcnss.mdt but still not working, also wouldent falshing a kdz from a diffrent device would cause a permabrick?

edit:to add i was on MS63110j before flashing

you wouldnt be flashing a kdz from a different device so no worries there. v20k is available to the ms631 too.

im going to 99% say that its being on a lollipop firmware and then flashing a marshmallow kernel that did it. i cant be 100% sure but im pretty positive thats the case. im not sure if you can go back to katana after flashing a v20k kdz but its worth it from a performance and security standpoint to be on marshmallow. xposed has been a godsend for our device and anything katana could do is available with xposed addons until i get data and double tap to wake figured out for lineage 13.

it looks like viperdink has v20k and even v20L available for the ms631 here: http://androidforums.com/threads/newest-metropcs-tmobile-6-0-kdz-firmware.1058637/

i would follow what he says to get to v20k
 
Upvote 0
there's really no way to use katana when i restore to 6.0? i really don't want to lose all my data

id flash back to katana and back up any data you can before you kdz to v20k. probably the only way your keeping the data and having working wifi/bluetooth.

remember, i did say right in the top of the thread that you should probably be on v20k before you flash to avoid any problems. lollipop firmware and marshmallow operating system really isnt a good combo to avoid problems. sorry i cant be of more assistance, let me know what happens.
 
  • Like
Reactions: herminiachristian
Upvote 0
id flash back to katana and back up any data you can before you kdz to v20k. probably the only way your keeping the data and having working wifi/bluetooth.

remember, i did say right in the top of the thread that you should probably be on v20k before you flash to avoid any problems. lollipop firmware and marshmallow operating system really isnt a good combo to avoid problems. sorry i cant be of more assistance, let me know what happens.
do i have a brick? i used the 6.0 kdz and when i say wifi worked i used the lg flash tool for the lolipop one and now my phone has a black screen and when i charge it stays on the black screen and i can't get into downlaod mode
 
  • Like
Reactions: whoshotjr2006
Upvote 0
do i have a brick? i used the 6.0 kdz and when i say wifi worked i used the lg flash tool for the lolipop one and now my phone has a black screen and when i charge it stays on the black screen and i can't get into downlaod mode

you shouldnt have flashed a v10 anything kdz, especially after flashing a v20 something kdz and just about all the guides out there say that. you cant downgrade from v20 anything to v10 anything. pull the battery completely out of your phone. then put it back in. hold the volume up button and plug it into your computer and see if you can get to download mode, if so reflash v20k kdz.

trust me when i say, lollipop is worthless these days. marshmallow is the same as lollipop but with better memory and battery management. dont waste time on lollipop because i really hope you didnt just 9008 mode your phone because afaik there is no coming back from that.
 
Last edited:
  • Like
Reactions: herminiachristian
Upvote 0
you shouldnt have flashed a v10 anything kdz, especially after flashing a v20 something kdz and just about all the guides out there say that. you cant downgrade from v20 anything to v10 anything. pull the battery completely out of your phone. then put it back in. hold the volume up button and plug it into your computer and see if you can get to download mode, if so reflash v20k kdz.

trust me when i say, lollipop is worthless these days. marshmallow is the same as lollipop but with better memory and battery management. dont waste time on lollipop because i really hope you didnt just 9008 mode your phone because afaik there is no coming back from that.
my pc detects it as QHSUSB_BULK
 
  • Like
Reactions: whoshotjr2006
Upvote 0
my pc detects it as QHSUSB_BULK

yeah im going to say you bricked it from flashing a v10x kdz over a v20x kdz. it sounds like your in usb 9008 or 9006 mode which is way way way beyond what i know how to deal with. you cant downgrade any phone these days to earlier software. if i were you i would try to go to xda and ask around there, asialove and MrObvious have dealt with stuff like this before with varying levels of success.

your question just went way beyond the scope of this dev thread. i wish you luck, and make sure you know what your flashing in the future so you dont have this happen again.

let this be a lesson to everyone, NEVER EVER TRY TO DOWNGRADE STOCK FIRMWARE! ESPECIALLY WITH LG!

start here https://www.mylgphones.com/unbrick-...-smart-boot-diag-tool-all-lg-g3-variants.html and see if maybe you can modify the method they used for the lg g3 for the ms631. if you need any files that any of us can provide to try to fix it, let us know.
 
Last edited:
Upvote 0
where would i get the recovery files?
also i think i neefiles that end with mbn

Start a new thread or repurpose your old one so you can have all efforts focused there and o can keep this thread dedicated to lineage os. Your going to have to do some research and reading on google to figure out how to get those files. Once you do, post in your thread a method for us so we can try to get you files you need.
 
  • Like
Reactions: herminiachristian
Upvote 0
small update.

we are going to be switching to the nougat kernel for lineage os 13 also as it compiles with caf sources with no issues. it broke camera/video recording/torch but im working on fixing it, since once i fix it for 13 or 14.1 it will be fixed for both. weirdly enough rotation and compass work with this, so it cant be kernel related in 14.1.

it saves a lot of effort and hassle since i dont have to keep switching back and forth between bases (13 to 14.1, then back to 13, blech) and we can just focus on one device tree set to fix our issues.

no real headway on data yet, and double tap to wake is a giant pain in my ass.

ill keep the download up for alpha 4 since it has working camera/recording/flash until i get those issues ironed out in this base.

once we have one working source for both lineage 13 and 14.1, im going to delete the old repos on github that we wont need anymore like hardware_qcom and lineage 13 specific device and vendor trees.

i repeat, the sources (device, vendor and kernel) in the op now are what I want everyone trying to build (if there is anyone but me) to focus on
 
Last edited:
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones