Database Info

Phone powers off after flashing CAF based ROMS no boot.

Hi guy,
I have been trying to figure this out for a while now and can't seam to figure it out. Everytime I flash a CAF based ROM after clicking reboot the phone turns off. During this time it is very hard to get the phone to turn back on. Holding the power button does not seam to do anything. I have to hold the power+volup+voldown for around 30 seconds let go and do it again in order to get back into recovery. I am not getting any errors at all when flashing. I really have no clue what it could be. I have tried every CAF based ROM I have come across here and they all do it. The only thing I can come up with is my phone has had the screen, camera, and battery replaced. Could one of these parts or another part be causing a problem that doesn't allow CAF based ROMS to work? I know its a long shot but thats all I can think of at the moment.
Right now I am working on trying to flash CyanogenMod from this thread. I have tried both version 13 and version 14 both have the same problem. This is what I have tried.
Flash HammerheadCAF reboot back into recovery
Flash bootloader&radio_HHZ20h+2.30.zip reboot to recovery
Flash cm-13.0-20161029-UNOFFICIAL-hammerheadcaf.zip
Flash opengapps
Flash SuperSu
Reboot
Black screen of death
What is wrong with this process? I have also tried the same process with cm-14.0-20161029-UNOFFICIAL-hammerheadcaf.zip. I am now going to try this same process with cm-14.1-20161029-UNOFFICIAL-hammerheadcaf.zip. I don't expect any difference though. Anyone have any suggestions?
Thanks,
Rocky
*****Update*****
I have tracked the problem down to CAF TWRP. I have formatted the phone which has removed everything except CAF TWRP and I am still getting the black screen of death situation. When the phone reboots it completely turns off. It will not respond unless I hold down power+volup+voldown for around 30 or 40 seconds. Then the phone will finally enter the bootloader. Are there any other recoveries that will flash CAF based ROMs? I don't know what else to do =(

Maybe don't flash supersu? Cm comes prerooted?

audit13 said:
Maybe don't flash supersu? Cm comes prerooted?
Click to expand...
Click to collapse
Thanks for your reply and time. I also tried flashing without SuperSU and it did the same thing. When I tapped reboot the phone would not turn on. I also tried just flashing the ROM and rebooting. The problem is with TWRP CAF because I have even formatted the phone so there was no ROM just TRWP CAF and when I tapped on reboot to recovery the phone just turned off. The power button wouldn't do anything. It would not even turn the phone on. The only thing I could do was hold the power+voldown+volup for 30 sec let go and press them again and go into bootloader.

Hey guys anyone else have any suggestions? I have tried sending a support ticket to twrp over a week ago. I haven't heard a word from them. I really want to use CAF ROMs

Hi!
I'm facing the same problem. I've been trying everything I can think of, and everything ended with a black screen when trying to boot:
Flashing stock again and then TWRP and CAF.
Flashing a lower version of TWRP (2.8.7.0) and then flashing CAF.
Flashing an AOSP version of CM, then TWRP for CAF and finally CAF.
Fixing permissions.
Changing filesystems to F2FS.
I tried to logcat, but adb logcat keeps waiting for the phone and it doesnt find anything.
Anybody has another idea of what could be happening or how to solve it?
Thanks!

I can flash caf, aswell as noncaf roms on my N5 just fine.
I used the CM14 darkrom CAF. Excellent performance, great battery life
i wiped the device in TWRP caf (Latest) (system,data,cache,dalvik0
Then i flashed the rom and the Darkrom gapps (use only those, as rom comes withouth a launcher. Pixwl launcher embeded into gapps package)
Wipe cahce/dalvik & reboot
It looped like: GOOGLElogo ,bootanimation ,self restart and it works perfectly fine since then
---------- Post added at 18:54 ---------- Previous post was at 18:53 ----------
I should also mention, that i use the european D821 model

I was beginning to wonder if it was just me. I felt like an ass for posting for help because I felt like it was my fault. I still have not gotten any response at all from twrp support. I really want to use car based Roms. I use to be able to when I first got the phone. Now I don't have a clue what the problem is. I am using the 820 USA model.
After doing a Google search for CAF TWRP no boot black screen and other combinations I have found posts around the web from people with the same issue. The only resolution was to revert to stock. I have sent TWRP support another email linking to this topic as well as contacted them on g+ hopefully we can get a resolution.

since i dont own the device.... no logs= we cant help you

Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...

I'm having this problem too, I can flash any non-CAF ROM and it will bootup fine, but any CAF rom will leave me in a black screen. Did you found any solution yet?

I have not been able to find a solution to the problem. TWERP tech support seams to be non existent. I have emailed them numerous times. They don't even take the time to say they will look into it =(

Dark_Eyes_ said:
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
Click to expand...
Click to collapse
What else could it be if we are able to flash absolutely anything else we want to flash except for a CAFE ROM?
I have never tried editting the updater script. Could you please explain how to do the things you described?

Ok I got an update. Today just for ****s and giggles I tried to flash the latest TWRP twrp-3.0.2-0-hammerhead.img on top of itself from inside TWRP using the image flashing process. I got the black screen I been getting that we are discussing here. Therefore, that tells me that the problem is not with TWRP CAF but with flash recovery's in TWRP. For some reason TWRP does not like that. Therefore, I am manually flashing the fallowing files the old fashion way by hand using the android sdk and adb.
1.) TWRP CAF
2.) The latest bootloader directly from the latest google factory image
3.) The latest radio directly from the latest google factory image
4.) Install the latest build of Dark ROM
I will report back with my findings.
Findings are epic fail. No boot, black screen of death.:crying: After holding down volup+voldown+power I am able to get back into recovery just like with flashing all the files through recovery when I first started. However, I can't get the damn thing to boot the ROM. I don't know what to think anymore. I think we just have to come to the conclusion that CAF based ROMs are out of the question for us :crying: :crying: :crying: When my son gets home and can hold the tablet while I operate the Nexus 5 maybe I will try to make a video of the problem. Hopefully this will help lead to a resolution.

Let me guess. All your phones have been repaired or are second-hand devices, aren't they?

experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
will a repaired device not work, mine has had the screen replaced. Nothing else just the screen.

experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
Yup, I have replaced the screen, why is that? Is it too much different than the original, shouldn't it work normally?

Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.

experience7 said:
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
Click to expand...
Click to collapse
Wait seriously? because i fixed my screen i am not able to use a caf rom on my device? That seems ridiculous, what would cause that to even be a thing? is there some sort of security flag it checks for?

Yeah I replaced the screen on mine too. Not sure how that plays a role. The only thing I can think of is unless there is a missing driver or something like that because our screens are different.
There's gotta be a way to fix this problem. I wish I knew how to build ROMs, kernels, and recoveries. I don't think anyone will go out of their way to fix a problem that doesn't directly affect them. So for me it is stock, rooted, with ElementalX till this pos croaks.

Not sure what the problem is. Fact is that your screen somehow differs from the 'original' one which causes CAF ROMs to blackscreen.
If you really, really want your phone to run CAF you have to provide a lot more information. You could try to get a running system and fetch some hardware information. Pretty sure there are apps on the Play Store that print hardware brands/model names, etc. Report your results and I'll use the same method to get mine. We should compare. Furthermore we'll need logs. Try to boot CAF. Of course it will blackscreen again but you can reboot to recovery and pull some logs. Maybe last_kmsg and dmesg where the latter one should be even more interesting.
And last but not least I'd like to tag @myfluxi here. Perhaps that's interesting for you...

[Rom] [Stock] [Rooted] [Deodexed] [Debloated] [TWRP Flashable Zip] [SM-T350]

The reason I am posting here and not in the Rom section is because I am not a developer. I am an Android enthusiast who, with the help of a few awesome tools, some reading and some help from a couple of great devs, I was able to build a custom rom from a stock first release. I have been running it now for a couple of weeks and battery life is awesome. Just enough Samsung apks left in too call it a stock rom but not so many to cause it to lag. I thought that since it was running so nice, I would share it with you. So, without further ado, this is what I came up with.
"Ghost Project v1.0 6.0.1 t350" This is only for the t350.
With the help of a few awesome people, that provided me with the direction and resources links, I was able to take a stock firmware.tar (T350XXU1BPE3) and make a TWRP flashable zip. This is what I came up with:
I am not a developer..... Let me make this clear.. Lol.. I am not a developer. But I did use an awesome tool that allowed me to make this rom " superr kitchen" .... http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296/page26
So first and foremost a big thanks goes out to this developer for this awesome tool.
I would also like to give props to Samsung and Sammobile.com for the firmware.
The kernel is from http://forum.xda-developers.com/galaxy-tab-a/development/kernel-galaxy-tab-sm-t555-5-8-2016-t3433560 and is a stock, permissive kernel. By "[ashyx, http://forum.xda-developers.com/member.php?u=4899305 Recognized Contributor]" another awesome dev. This is a stock kernel in every respect with SElinux set to permissive.
I would also like to thank and give props to"{FankieT} of {R3Ds themes and Development}" https://plus.google.com/communities/102477541363210451018 for all of his help and guidance. He was who got me started into Linux through Ubuntu and spent many hours teaching this old dog the ways of Android coding. Just a pinch of coding on my part..lol
Glockman4519
Owner
Hayes Tech Rom Reviews
Dec 09, 2016
Use at your own risk. ********You have been warned..*********
Features:
1. Rooted with chainfires SuperSu in system, not systemless (I hate systemless root)
2. Busybox installed
3. Debloated. I didn't go too far (for reliability) but will work on getting more Samsung system apps removed.
4. Zip aligned
5. Deodexed (I may make one that is odexed later on)
6. Removed Kies
7. Custom kernel
Stock but SElinux permissive (see note on developer in Intro)
8. Some script changes but nothing to change system behavior
9. Added ES File explorer v3.2.5.
This app will try to update unless Play Store settings are changed to not auto update. But if you like the latest than update it.
10. Added Nova Launcher v3.3
I don't like the newer Material Designed updated builds. This will also try to update unless settings in Play Store are set to not auto update.
11. Latest Google Keyboard.
I just don't care for Samsung's and like the theming features of Google's latest keyboard. Samsung keyboard is still in though if you prefer to use it instead.
12. According to the toolkit, Knox was removed. Although I still see it in the settings tab under Settings/about phone. I don't think this can be removed safely however all updates (annoying notifications stating that there is an update available) have been removed so there shouldn't be any chance of accidentally updating to the latest firmware, if any is released. If you want an update than you will have to download any updates ( if the are any) from Samsung and use Odin to install it.
Kernel:
Here is a link to the kernel developer's thread, who is another awesome dev, who's kernel is the heart of this rom.
http://forum.xda-developers.com/gal...el-galaxy-tab-sm-t555-5-8-2016-t3433560/page8
By "[ashyx, Recognized Contributor]" This is a stock kernel in every reguard with SElinux set to permissive.
A few other small things here and there but mostly stock.
-This is a flashable zip using TWRP recovery and I highly recommend the 2.8.7.0 build as apposed to the 3.0.2.0 build that is also on XDA in this forum.
Link to recovery built by "ashyx" an awesome dev...
http://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560/page13
-Since this is a stock rom build, gapps are included
#####Flashing instructions#######
###MUST BE ON MARSHMALLOW BUILD ****T350XXU1BPE3******####### so, if you are on a lollipop build (5.0.1) you need to update to 6.0.1 and have TWRP installed........
1. Make a backup onto your external SD card or on a PC using TWRP recovery. This is a very important step as things do go wrong. You have been warned.
2. Wipe. I recommend a clean install with all 4 major wipes done (system, Cache, Dalvik Cache and Data)
3. Flash "Ghost Project v1.0 6.0.1 t350" rom zip.
4. Wipe both Cache and Dalvik Cache
5. Reboot to system and profit.
*****The first boot will take a long time to boot. Put the device down and walk away until it boots (could take up to 15 minutes ) but most likely around 12 to 15 minutes. That is because all files are deodexed.
After it boots up Go ahead and set up the device the way you like it and enjoy.
I also have a Google Plus Communitee Called "Hayes Tech Rom Reviews" where you can go to watch reviews/overviews of custom roms for many devices that I own. I have about 20 to 25 devices now and try to do reviews on all the diferent roms out for them. I also have awesome links like the 3Minit battery mod by{made by "gharrington"} for the Nexus 6 and many more things. Please feel free to stop by.
https://plus.google.com/communities/109262972011341635244
**LAST BUT NOT LEAST****USE AT YOUR OWN RISK**
Warning, I am not a developer. All I am doing is sharing my personal build. I am not nor will I be responsible for anyone ruining your device. Thermonuclear war or Loss of job from device not working is your responsibility. And above all this zip will void your warranty.
I can't think of anything else..lol.. This is the first time for me so I'm not too sure about proper post etiquette for Custom Roms. I am not posting in the roms section because I am not a developer. I do not have the skills those great people have. We just do not have any stock based roms yet and mine is running great so I am sharing with you all. I am going to try to add more custom features and may even add a pure stock rom for total stock experience, let me know... Enjoy.
A video review of my rom... Go here if you would like to see it
https://youtu.be/dVnx709LO7Y
I built another rom for those that want the stock experience but still want it rooted and Knox removed. It is also Zip Aligned and is running the same permissive kernel for Xposed Mods to work better with it.
Download Rom (AFH)
Stock/Rooted/Deodexed/Debloated/Knox Removed/Zip Aligned/Permissive Kernel/ES File Explorer 3.2.5, Nova Launcher 3.3, Latest Google Keyboard
https://www.androidfilehost.com/?fid=673368273298916139
Stock/Rooted/Deodexed/Knox Removed/Zip Aligned/Permissive Kernel/No Extra Apps Added (Pure Samsung)
https://www.androidfilehost.com/?fid=385035244224406713
Xposed Installer Zips (For Samsung) By wanam, Recognized Contributor. You can find his thread here http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Screens:

If you want to run the wallpapers that I am, I am working on getting them into the default wallpaper but until then you can get it here

Just in case again. Lol

Sent from my Nexus 6 using XDA Premium HD app
Merry Christmas Everyone.

the link to the rom doesnt work

ratchetrizzo said:
the link to the rom doesnt work
Click to expand...
Click to collapse
I am checking now to see whats up. Here is my original Google drive link.
https://drive.google.com/file/d/0ByTpk6hgHRa5VU4wSkVrcy1jakU/view?usp=drivesdk

ratchetrizzo said:
the link to the rom doesnt work
Click to expand...
Click to collapse
AFH link is now fixed
https://www.androidfilehost.com/?fid=673368273298916139

glockman4519 said:
AFH link is now fixed
https://www.androidfilehost.com/?fid=673368273298916139
Click to expand...
Click to collapse
Does xposed work on this rom? If so, which version?
thanks!

ratchetrizzo said:
Does xposed work on this rom? If so, which version?
thanks!
Click to expand...
Click to collapse
Yes it does. I used the kernel that is in this forum to build it with and it is a permissive kernel. The version is v87.1-sdk23-arm made by Wanam specifically for Samsung. I am running it now asking with gravitybox and a few other mods.
Just remember that since it is deodexed it will take a long, long time to boot. I timed it on my last 2 flashes at around 13 minutes both times. My battery life is outstanding.

glockman4519 said:
Yes it does. I used the kernel that is in this forum to build it with and it is a permissive kernel. The version is v87.1-sdk23-arm made by Wanam specifically for Samsung. I am running it now asking with gravitybox and a few other mods.
Just remember that since it is deodexed it will take a long, long time to boot. I timed it on my last 2 flashes at around 13 minutes both times. My battery life is outstanding.
Click to expand...
Click to collapse
do you have a link for that?

ratchetrizzo said:
do you have a link for that?
Click to expand...
Click to collapse
Yes I do but only to my Google Drive. I will try to link them to the OP later but to then here you go.
https://drive.google.com/folderview?id=0ByTpk6hgHRa5X3g5VnBVam9OaDQ

glockman4519 said:
Yes I do but only to my Google Drive. I will try to link them to the OP later but to then here you go.
https://drive.google.com/folderview?id=0ByTpk6hgHRa5X3g5VnBVam9OaDQ
Click to expand...
Click to collapse
Just installed this, flashed it and xposed at the same time, took 7 minutes to boot the first time.
Updating, reinstalling and debloating things I don't need now.
Seems faster than the debloated 5.02 rom I was on.
Will keep you posted after everything is done

glockman4519 said:
Yes I do but only to my Google Drive. I will try to link them to the OP later but to then here you go.
https://drive.google.com/folderview?id=0ByTpk6hgHRa5X3g5VnBVam9OaDQ
Click to expand...
Click to collapse
everything works great.
Quick question, what did you use to change your clock and signal icon colors?
Wanam isn't changing the clock color or left hand icons for me.

ratchetrizzo said:
everything works great.
Quick question, what did you use to change your clock and signal icon colors?
Wanam isn't changing the clock color or left hand icons for me.
Click to expand...
Click to collapse
Sorry, I am on night shift and was getting some sleep..lol.. I used Gravitybox MM. It has almost everything in it that I need to make a stock rom custom..lol..

ratchetrizzo said:
Just installed this, flashed it and xposed at the same time, took 7 minutes to boot the first time.
Updating, reinstalling and debloating things I don't need now.
Seems faster than the debloated 5.02 rom I was on.
Will keep you posted after everything is done
Click to expand...
Click to collapse
Thats great... It takesk me 13 minutes on both ( plus or minus)... Every device will respond differently though so the boot times will vary. Thats Awesome.

glockman4519 said:
Thats great... It takesk me 13 minutes on both ( plus or minus)... Every device will respond differently though so the boot times will vary. Thats Awesome.
Click to expand...
Click to collapse
I screwed something up with a xposed module (I guess, everything was fine until I installed a power menu module and told it to reboot into recovery). No matter what I did, It would only boot into twrp. Even if I powered off and plugged the charger in, instantly twrp. Reflashing the rom did absolutely nothing, I had to odin stock then reflash this rom.
Ah well, live and learn with xposed.. I know not to install that power module lol

ratchetrizzo said:
I screwed something up with a xposed module (I guess, everything was fine until I installed a power menu module and told it to reboot into recovery). No matter what I did, It would only boot into twrp. Even if I powered off and plugged the charger in, instantly twrp. Reflashing the rom did absolutely nothing, I had to odin stock then reflash this rom.
Ah well, live and learn with xposed.. I know not to install that power module lol
Click to expand...
Click to collapse
I hear ya. Xposed is something I use only if I know the module. I never use test version (anymore .. lol) I did the same thing you did a whike back with some other mod.
The only mods I use are Gravitybox, Notify Clean, Xuimod, and sometimes either HK theme engine out Xtheme engine. Gravitybox has most all mods that I need built right in it including an advanced powed menus settings.
Also, when you were in that issue, did you try using the Xposed uninstall zip? That may have got you fixed up too.

glockman4519 said:
I hear ya. Xposed is something I use only if I know the module. I never use test version (anymore .. lol) I did the same thing you did a whike back with some other mod.
The only mods I use are Gravitybox, Notify Clean, Xuimod, and sometimes either HK theme engine out Xtheme engine. Gravitybox has most all mods that I need built right in it including an advanced powed menus settings.
Also, when you were in that issue, did you try using the Xposed uninstall zip? That may have got you fixed up too.
Click to expand...
Click to collapse
Well, even with gravitybox's reboot menu, if i have it boot me into recovery it sets the recoverybit and makes me reflash stock firmware.
so DON'T pick recovery from your reboot menu

ratchetrizzo said:
Well, even with gravitybox's reboot menu, if i have it boot me into recovery it sets the recoverybit and makes me reflash stock firmware.
so DON'T pick recovery from your reboot menu
Click to expand...
Click to collapse
I use it all the time. I just rebooted into recovery just before I responded here. Anyways there are also app on the p
Play Store that will reboot you to recovery too, like "Quickboot". I don't understand why this is giving you issues. What version of recovery are you on? There are problems with the 3.0.2.0. I used the other one on this forum 2.7.8.0.

glockman4519 said:
I use it all the time. I just rebooted into recovery just before I responded here. Anyways there are also app on the p
Play Store that will reboot you to recovery too, like "Quickboot". I don't understand why this is giving you issues. What version of recovery are you on? There are problems with the 3.0.2.0. I used the other one on this forum 2.7.8.0.
Click to expand...
Click to collapse
I'll go down to 2.7.8.0 and see how that works for me

Completely Eliminated Static Boot on Rooted V20 with My Stock Kernel!!!

Alright guys, so this happened 100% ON ACCIDENT but it actually worked! I wanted to let you guys know because maybe it will help some of the devs figure out how to eliminate the static boot for good.
I have the H910 ATT V20. I initially rooted it using Dirty Santa but, at the time, nobody had made a custom ROM for the ATT variant yet. I flashed the Konverged Kernel and from then on, I had the dreaded static screen on boot. @Tilde88 was extremely generous in offering to make a custom ROM if I provided some files for him and he made the first excellent NotSoStock ROM for the ATT V20. However, I had some issues installing it on the first try. When I tried to flash his ROM, TWRP gave me an error telling me I had a US996. I patched the zip with a file from Tilde88 and it worked like magic!
Since then, there has been a lot of progress in ROMs and kernels for all the variants. For the sake of experimentation, I have tried different ROMs and kernels to see how they affect the phone. Since my phone is registering as a US996, I flashed that variant of the NotSoStock ROM. The Werewolf Kernel from @USA-RedDragon is the only one I know of so far that does not have the static on boot. I have been flashing Werewolf and Konverged along with different ROMs to see the difference in performance and battery.
The ROM I am on right now is Extreme Syndicate from @elliwigy. Since it is based off of the stock deodexed US996 firmware, I thought it sounded great to try since it has NONE of the bloat from any of the various carriers. I read in a post by @AlkaliV2 here about flashing the stock kernel located on my computer from the original Dirty Santa root method:
https://forum.xda-developers.com/v2...-nrd90m-modded-notsostock-rom-t3525344/page21
That gave me an idea to download and flash the stock unlocked US996 kernel since Extreme Syndicate is based off of that. I had Konverged Kernel at the time. I flashed the US996 kernel, but forgot to flash SuperSU before boot... Woops lol. So I went back to TWRP and formatted my phone to start from a fresh flash, but realized I also deleted my ROM backup when I formatted my phone. So I decided to install a ROM and kernel fresh.
HERE IS HOW I FIXED THE STATIC BOOT
After formatting my phone, I flashed the Extreme Syndicate ROM with the Werewolf Kernel. I chose this kernel so there would not be any static on boot.
Then
I booted back to TWRP, made a backup just in case, and flashed my stock H910 ATT kernel from the file named bootbackup.img. After that, I flashed SuperSU, wiped Cache and Dalvik, rebooted... and BAM, just like that, no static! It says under software information that I am on kernel version 3.18.31. 3C Toolbox shows the kernel as Linux 3.18.31g12e8957
It is still fresh so I have to see how it goes with battery and performance. Initially, it was noticeably slower. I completely fixed this by:
1. Implementing all options under "One Click -> Performance Optimizations" in the app 3C Toolbox
2. Selecting "Performance" under Profiles in the app L Speed
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!

Yes, there is an updated driver branch using CAF sources that fixes static boot. I'm far too busy in life to get anything done, and before anything else, I have to get v6.0 for the H918 going. Once that is up (using the latest build and soruces from LG), I can move forward for 6.0 for the other devices.

nikktrikk said:
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!
Click to expand...
Click to collapse
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb

AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Hmmm interesting. Mine returned with:
Code:
3.18.31-g12e8957
[/QUOTE]
Do you have any idea why that might have happened? I used the file directly from the Dirty Santa folder, but maybe there is an issue since I flashed it over the previous kernel.

AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.

nikktrikk said:
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.
Click to expand...
Click to collapse
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.

AlkaliV2 said:
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.
Click to expand...
Click to collapse
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!

nikktrikk said:
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!
Click to expand...
Click to collapse
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.

AlkaliV2 said:
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.
Click to expand...
Click to collapse
Definitely makes sense. Yeah I have been having issues with battery drain and all that, as well. This is the very first time since I have been having issues with the US996/H910 conversion and incompatibility that I have actually got it to be stable. I also didn't like not having comfort view, and this actually fixed it! Comfort view now works on my phone, it didn't work earlier today before this most recent flash. I think that I will just give it some time before I make a decision and see how the battery fares. You have been a HUGE help, I really appreciate you taking the time to explain the process to restore my phone. I do want to do it, but being that it currently seems to be doing a lot better than before, I'll wait before making the leap back to stock just for comparison.

Help me
I also have h910 model but when i tried to boot after dirtysanta 3 rd step it didnt boot into twrp..even though i tried to flash recovery with fastboot flash recovery command.
I m stuck and static screen is a mess..plz help me

Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?

titmus said:
Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?
Click to expand...
Click to collapse
you where supposed to back up your original filesystem you would have gotten it from there.

Has Anyone Gotten a Custom ROM onto a BLN-L24 (US Variant)?

I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?

Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050

RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?

Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.

Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop

i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?

I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.

I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?

code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.

It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.

TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?

BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.

When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??

BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?

galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.

I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.

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.