Without fail every time after the lg logo disappears after flashing a custom rom made for the h918 lg v20 I get a flashing black screen. I'm doing a factory reset/wiping davlik cache/ cache/ and data 3 times each time I flash the custom rom and sometimes I even go as far as wiping the internal memory completely even after a factory reset but no matter what I try without fail I always get the flashing black screen right after the lg logo disappears. I even tried upgrading twrp from 3.0.2.0 to 3.1.1.0 and I even tried flashing the no-verity-opt-encryption 5.1 and 6.0 but nothing I've tried seems to fix it so I'm asking for help now since I've exhausted my knowledge on what could fix it. What can I do to fix that issue so I can finally start using custom roms again? Any help would be most appreciated thanks in advance.
P.S. The only rom I could get to flash successfully was the stock twrp flashable t-mobile rom on one of the threads in the rom section of the lg v20 forum so for now until I can fix that issue I'm currently running that so I have a phone I can still use.
raze5115 said:
Without fail every time after the lg logo disappears after flashing a custom rom made for the h918 lg v20 I get a flashing black screen. I'm doing a factory reset/wiping davlik cache/ cache/ and data 3 times each time I flash the custom rom and sometimes I even go as far as wiping the internal memory completely even after a factory reset but no matter what I try without fail I always get the flashing black screen right after the lg logo disappears. I even tried upgrading twrp from 3.0.2.0 to 3.1.1.0 and I even tried flashing the no-verity-opt-encryption 5.1 and 6.0 but nothing I've tried seems to fix it so I'm asking for help now since I've exhausted my knowledge on what could fix it. What can I do to fix that issue so I can finally start using custom roms again? Any help would be most appreciated thanks in advance.
P.S. The only rom I could get to flash successfully was the stock twrp flashable t-mobile rom on one of the threads in the rom section of the lg v20 forum so for now until I can fix that issue I'm currently running that so I have a phone I can still use.
Click to expand...
Click to collapse
did you ever find a solution? I'm having the exact same issue and am pulling my hair out trying to get something to work
If the version number of twrp your using is in fact 3.1.xx then that could be your problem all the new roms im almost positive need the newest twrp from pheonix i think it 3.2.3.4 its in the deveopment section...ive heard alot of problems on this device with older interations of twrp. I would start there
https://forum.xda-developers.com/showpost.php?p=77177529&postcount=6
Phoenix591 said:
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
lineage-14.1-20180721-UNOFFICIAL-h918.zip.md5
When lineage 15.1 becomes official the h918 builds will be aimed at post10p. x86cpu is currently doing unofficial builds for both.
Click to expand...
Click to collapse
Related
my f320s was rooted and had twrp with lamhoang installed I decided to flash the 4.4 kitkat rom but ended up with a boot loop and no recovery I then used lf flash tool to flash stock,, now I have black lines down the right side of the screen as soon as device is switched on I even restored the twrp backup and tried a full wipe still no joy :crying:
yadabwoy said:
my f320s was rooted and had twrp with lamhoang installed I decided to flash the 4.4 kitkat rom but ended up with a boot loop and no recovery I then used lf flash tool to flash stock,, now I have black lines down the right side of the screen as soon as device is switched on I even restored the twrp backup and tried a full wipe still no joy :crying:
Click to expand...
Click to collapse
I just tried to install the new furnace CM kernel and upon reboot the LG logo come up the it began to fade like my screen was going out. Then I reinstalled my old kernel and now I have the same problem. This shouldn't happen by just flashing software. Please HELP!!!
calcappone said:
I just tried to install the new furnace CM kernel and upon reboot the LG logo come up the it began to fade like my screen was going out. Then I reinstalled my old kernel and now I have the same problem. This shouldn't happen by just flashing software. Please HELP!!!
Click to expand...
Click to collapse
Same thing happend to me when flashing furnace i just went back into recovery and factory reset and clean flashed another ROM all was good
You should change the title to "Screen Damage after updating Custom rom/kernel".
This is one of the risks in installing custom software and drivers is that it might get flaky. I would recommend flashing an older Kernel or one with an older screen driver as the new one doesn't play nice, apparently.
The Touchscreen graphics driver is a weird one. It generally can be updated... but not downgraded easily. The Nexus 7 2013 has a big issue with its screen and they've had to force a custom driver in it and lock it from being updated (since an Google Update installed a bad driver). It's been fixed now, but a bad problem. I doubt it is exactly the same since ours affected touch inputs where yours is affecting color, but pretty sure its the same chip that controls it.
Flashing an older Kernel will likely NOT fix your issues but it is worth a shot. You may have to wait until the developer puts out a patch (to update).
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
schmidty455 said:
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
Click to expand...
Click to collapse
Omni clearly states that it is an alpha, so you mileage may vary considerably.
Sounds kernel related. Have you tried just reflashing the kernel and seeing if it'll boot after that. Or trying a different kernel?
Thanks for the reply! I actually just fixed the problem on my own. I used Odin to flash a newer version of TWRP and then flashed omni, and it looks like everything is working just fine. I read a few people saying that they were having issues flashing kit kat roms with older versions of recovery, so I figured it was worth a shot.
Hey guys. About a week or three ago I saw nightlies started rolling out for the D802, and decided to try the third nightly that has been released. While flashing itself went fine, I'm having trouble with getting the ROM to boot. After the LG logo the phone enters a blank screen, and won't do anything at all. I can barely notice that the backlight stays on, and I noticed that during this bootloop or whatever this is, Windows Explorer spams over and over I need to format the disk before I can use it when the phone's plugged in. I've read from someone that I should flash the ROM and google apps simultaneously, thus I've added them to a flashing queue and wiped the Davik cache after the flashing.
At first I thought it might've been my recovery being out of date, since I was running TWRP v2.6.x.x before, so I flashed the most recent version I could find which was v.2.8.3.73.
Doing this however made no difference whatsoever, so I gave up at this point and decided to wait for a week or two for the developer to fix a potential issue on the ROMs end.
Now it's fast forward to two weeks later where I'm typing this post after trying to flash the most recent version of cm13 which was available for my phone (the D802).
The problem is I'm starting to run out of ideas to do, so I'm hoping somebody can hold my hand regarding this issue. I really like to try Marshmallow and it's really irritating it doesn't work.
Thanks in advance guys!
i yhink you need to install boostacks when you install boostacks for your varian. dont reboot into system, just go back to main menu. then reboot into recovery from recovery. then copy the rom. flash and gapps ...
i also ecoment blastagator twrp to prevent ecreen dmage
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Thank you!
I was having the same trouble with lineage OS 14.1 on my D802.
I always got a black screen after the logo of LG appeared.
luckily I could get to TWRP and push the alternative bootstack via "adb push (filelocation) /sdcard/"
Thanks a lot!
thc8 said:
Thank you!
I was having the same trouble with lineage OS 14.1 on my D802.
I always got a black screen after the logo of LG appeared.
luckily I could get to TWRP and push the alternative bootstack via "adb push (filelocation) /sdcard/"
Thanks a lot!
Click to expand...
Click to collapse
Newbie here - I'm having the same problem with my D800 after Lineage OS 14 flash via TWRP. Where do I get an 'alternative bootstack'?
Get bootstack from here!
Check this out: https://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715
Hello,
I have an odd problem I need to iron out. . . Recently I installed the NeculaROM mostly without a hitch, however I was having issues not being able to make outgoing calls, so I wanted to switch back to my old Rom. Normally this wouldn't be an issue however when attempting to wipe anything on the phone, it starts vibrating and shuts off in TWRP. I can flash things fine still, back things up, yada yada. I tried reflashing TWRP, and that didn't help either.
So now I am stuck on this rom, and I can't do anything in TWRP. Is there any way to fix this? I can't seem to find much information on this particular issue. Any help would be great.
Thanks!
I believe this is caused by f2fs changes with rebasing this device to nougat.
Have you tried using the TWRP linked to the OP of the NucleaROM thread? You might have to format internal storage to get things working right again.
If that doesn't work out for you I'd recommend searching around more recent discussions in the TWRP thread and LineageOS thread. These issues with wiping and differences between unofficial TWRP, official TWRP, and what works with what ROM/firmware combinations have been covered in both.
Sorry I'm not more help on exactly what to do. I've just stuck with marshmallow firmware and custom roms based on it. I'm waiting for the dust to settle on this nougat rebase business.
Had same issue. I ended up just reflashing all the firmware images. Fixed my problem (for the most part.)
Hi. I’ve got a customer with a j5 that I factory reset as she was having problems with it. But now it will only boot to TWRP which must have been installed before she bought it.
I’ve tried sourcing a stock android but with no luck so I tried a few Roms from here today. I can’t get it to work at all! Here’s what Happens.
From twrp I install CM rom and gapps. When I reboot the phone an orange line appears across the screen followed by the Samsung logo. Then the screen starts fading to green. The screen is in full working order when using twrp.
Does anyone have any ideas?!
Thanks
Davidb8 said:
Hi. I’ve got a customer with a j5 that I factory reset as she was having problems with it. But now it will only boot to TWRP which must have been installed before she bought it.
I’ve tried sourcing a stock android but with no luck so I tried a few Roms from here today. I can’t get it to work at all! Here’s what Happens.
From twrp I install CM rom and gapps. When I reboot the phone an orange line appears across the screen followed by the Samsung logo. Then the screen starts fading to green. The screen is in full working order when using twrp.
Does anyone have any ideas?!
Thanks
Click to expand...
Click to collapse
More than likely that version of twrp is outdated get a .IMG file of twrp version 3.2.1 and flash the image in twrp. Use this https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3769408/page5
If that isn't the problem and the problem you have persists than you have either flashed the wrong version file as there is several types of galaxy j5 with different hardware,
Or the bootloader you have on the phone is the wrong version ie. it has marshmallow bootloader and your trying to flash a ROM that only supports lollipop or vice versa. Links for both bootloaders are here
https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page14
This should fix your issues hope it helped