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).
Related
So I recently purchased my AT&T Galaxy S4 with MDL baseband. I rooted and installed TWRP via motochopper. I then loaded Kangabean 4.2.2 and everything was great. Got notification for OTA update to 4.3 and decided might as well load Kangabean 4.3 as opposed to dealing with the OTA notification. I did so (after formatting internal SD and performing factory reset) and now my phone won't boot beyond the Galaxy S4 splash screen. I restored a nandroid backup of the original software and was able to boot the phone once, but couldn't load the custom rom again, nor can i load into the stock rom anymore either. Does it sound like my phone may have a hardware failure? Would attempting to restore through odin be the next logical step? I'm by no means an expert with these sort of things but my S2 has never given me any sort of grief when flashing various roms in the past. Any advice would be greatly appreciated. Thanks in advance!
Try a different kernel, also, pull the battery for 5 min, it will boot.
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
Yeah I left the phone off with the battery removed all night - didn't want to boot this morning. I'm also noticing an oddity with TWRP - it's for some reason asking for a password on startup even though I've never set one. It also gives an error when attempting to wipe the phone or re-flash
id try odin
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
jd1639 said:
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
Click to expand...
Click to collapse
It will not let you past the password, been there, it will only do simulated flashes.
Odin is his only option.
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Squidbert said:
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Click to expand...
Click to collapse
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
//
Squidbert said:
.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
Click to expand...
Click to collapse
If you're on the stock AT&T rom and you're getting stuck on the AT&T boot logo try the following:
Power off your phone and hold down Volume Up, Center Home, and Power buttons together.
Once you see the Galaxy S4 splash - Keep holding down Volume Up and Center Home buttons but let go of Power button.
Choose the wipe datafactory reset. This will wipe your phone completely but it should boot after.
Hope that helps.
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Squidbert said:
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Click to expand...
Click to collapse
TWRP does not now and has never added LOKI to any ROM or Kernel. Only OUDHS CWM auto-LOKIs. You have to use A pre-LOKIed Kernel or flash the LOKI DokI script to LOKI anything with TWRP. You can do a search to find the LOKI DOKI script and how to use it.
fatah
hi my phone is galaxy s4 at&t i337 rooted but not installed recovery the phone was working good suddenly i deleted at&t software updater after that the phone rebooted it's self and then stuck in at&t boot logo won't bootup please help
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
galaxy s4 i337 stuck on at&t bootAnimation
i tried everything but still same please help my phone is not booting up
fatahmusse said:
i tried everything but still same please help my phone is not booting up
Click to expand...
Click to collapse
Flash the stock firmware.
samsung galaxy s4 i337
thank you i flashed to mf3 everything is ok
fatahmusse said:
thank you i flashed to mf3 everything is ok
Click to expand...
Click to collapse
Glad to hear
Hi all,
I recently installed the newest build of Slimbean. I am having a few issues: I am unable to play any media... Music, videos (youtube). My phone app does not work. I cannot receive nor send any calls. And my phone produces no sounds at all.
I tried installing build 7 to see if it was an issue with the build I was using... didn't help.
Internet and wifi work without any problems.
Galaxy S4 i337m
Baseband: I337MUMUAMDL
Version: Slim-4.2.2.build.7-OFFICIAL
Build #: slim_jfltecan-userdebug 4.2.2 JDQ39E eng.blk_jack.20130706.15730 test-keys
Any ideas?
Thanks in advance
Update: Any ROM I install... Phone and sounds do not work.
Talabis said:
Update: Any ROM I install... Phone and sounds do not work.
Click to expand...
Click to collapse
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
jd1639 said:
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
Click to expand...
Click to collapse
I did just that... But it's a bit of a story.
I had just fixed another problem I was having yesterday. Was getting stuck at the S4 splash screen right after powering on the phone. The problem was caused by TWRP 2.6 and formatting /data partition. Long story short, I installed CWM and used it to do a full wipe/format of partitions and then was able to install ROMs, restore backups without issue.
So today, since everything was working, I decided to flash a new custom ROM (which I installed) and the MG1 radio. Wasn't having any luck with the radio. Finally, I was able to flash a radio via mobile odin, but then I soft bricked my phone. Got stuck at the S4 splash screen (same issue I had yesterday, but this time, a different cause). So was troubleshooting it all day. Tried to go back to stock, no luck. Tried to restore the stock backup I had, no luck. Only thing I could do was install custom ROMs at this point to get into my phone (i.e. Slimbean, FoxHound, etc...). But, at this point, although I could boot into Android, I had no sound at all and couldn't play video. So after hours of trial and error, I installed CWM again (replacing TWRP 2.5.0.2), did a full wipe/format and tried to install a stock ROM. No luck. Still was hanging at the S4 splash screen. Then I tried to install this ROM again which I had luck with in the past; |ROM| |★VLUAMG1★| |CANADIAN||i337M||STOCK||ROOTED||July.26.13|. But his instructions said to install a wifi fix or fear soft bricking my phone. So I installed the wifi fix, but selected the wrong file (I know, stupid. Done a lot of stupid **** in the past couple days with this phone). Now, after the phone rebooted, I would see the S4 splash screen for a split second, and it would auto load into download (odin) mode. Couldn't get into recovery at all. So then I decided to flash one of the stock ROMs I tried earlier that didn't work, but this time, SUCCESS!!!!! Phone was booting and all sounds worked. I could make/receive phone calls as well... Everything seems to be working fine now. I find it funny that flashing a wifi fix that I shouldn't have seems to have fixed my issue in a sense. Since it allowed me to successfully flash a stock ROM. So I am making a backup of the stock ROM and will decide what I'm going to do from here.
Holy goalie!!! It's been a very vexing couple of days.
Nice that you got it all worked out, I've found out that if your "status" is custom, it will sometimes give you problems when flashing a "stock" rom via odin.
So what I always do when reverting back to the stock rom, I use triangle away to clear the flash count and make my phone back to "Official". If you want the steps to do this, let me know, it's not hard, but there are crucial steps to get this right!
JP
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.
So I have been running CM11 since January and finally got around to updating to KitKat to see what was new and because CM11 wasn't using the kitkat kernel which I assume is what caused all the SoDs and instabilities in all the ROMs. Well now I'm on stock and I'm suffering horrible battery life in comparison (17 hours with 4 screen on vs 36 hours with 8 screen on). I tried flashing CM11 and it worked but after a day or two I wanted to try a new ROM. Carbon was one that I saw near the top of one of the G2 development forums so I decided to try that. Went through the normal process to flash a ROM and it bootlooped when I rebooted. My backup also boot looped and I had to use some method to go back to 12B since I had no ROM or anything on my phone. Got back to 24A and I tried flashing Malladus to see if a stock based ROM would work and it looped. Restored my backup and tried CM11 and it also looped. Now I'm sitting on stock with Verizon's bloat hogging resources and battery and a phone that won't flash and boot successfully. Is there any way I can fix this? Has anyone seen this before?
TLDR: phone won't flash a ROM without bootlooping since 24A update
Only gonna bump this once but I really hope the right person sees this. Really confused as to why my phone won't properly boot after a clean ROM flash
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