I've got a i9505 and I wanted to flash CM 11 so I backed up all my apps and did a nandroid backup with TWRP.
I downloaded the latest nightly and when I swiped to flash it did nothing for a while and then the screen went greenish and white and later just the kind of white that lets you know that you f'ed up and the screen is broken I guess.
Fortunately it isn't but I want to know what I did wrong.
Related
After restoring a nandroid backup yesterday, I ended up with screen flickering that I didn't have before the nandroid. I passed it off as something strange with the restore so I clean flashed the ROM and all was well. Then I couldn't get the network type to stick to LTE so I decided to restore a nandroid of ProBam form 11/4, which was also working fine at the time of the nandroid. After rebooting once the restore was complete, my screen flashed green with horizontal lines then went black and I haven't been able to get it to stay on since. I've successfully Odin'd back to stock MDB after re-partitioning with a PIT file via Odin and the phone boots, I just can't see what's going on because the screen is dead. Even with a dead screen it's not hard to get to download mode which is how I made Odin work. My question is... is there any way at all I can reset the flash counter prior to chalking it up as a warranty claim? Even though it's stock MDB now, I'm not sure if they might go to the trouble of replacing the screen to see the flash counter then void my warranty. Maybe it's not even that big of a deal. ? If I was signed into my Google account on the phone, I could install a remote control app from the Play Store and maybe see the screen from my PC, but I can't even get that far. Any suggestions?
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).
OK, so I was preparing to flash a new ROM to my Sprint Samsung Galaxy S4. I backed up my original/stock ROM using TWRP Recovery and everything went well. I then flashed CWM to my phone and it was a bad ROM, so when I went to restore my original ROM, it installed great, however the boot process didn't backup. So now every time I turn on my phone, the Samsung Galaxy S4 logo shows up, but then blank screen with blue LED on. It would stay like this until I took my battery out. I need to know how I can restore my original ROM. Can I install a stock ROM, then restore my backup, or what?? Please guys I really need help.
Hi All,
I was on some Lollipop rom for a few weeks and decided to try something new so downloaded one jackaway rom l2 and did the usual backup, factory reset and flashed the rom. All good but after say 30mins i decided to go back and restore my previous rom. Went to recover did a cleanup to install new rom and then started restoring the backup previously made however after sometime in the restore process the screen dimmed and then just blacked out without any warning.
Now my phone does boot up into recovery after removing the battery and putting it back again but any thing like flashing a new rom or restoring causes it sometimes suddenly blackout or goes through the screen dimming and blackout.
I have never experienced this before so can someone pls advise if they know as to whats happening and if Odin flashing is the only way left for me. Thanks
Forgot to mention, mine is a N9005.
bump.
Can someone help me pull the cwm backup from internal memory using adb. Thanks
What recovery are you using?
Sent from my SM-N9005 using Tapatalk
So my assumption is I forgot to turn on developer unlock. All I get now is vertical lines when I turn it on. It WAS showing a samsung logo before but now its all messed up. When I go into download mode I can vaguely see the big arrow but I cant do anything. Is it ded?
Edit: Got it in download even tho I cant see anything.
Flashing a stock FW isn't fixing this. All I did was flash a twrp recovery, I didn't think it be this hard to revert.
I got custom OS on it and working twrp and the screen works sometimes now. Just gonna return it. Has to be a physical defect.
Got a new one, got twrp on it and crDroid and its all good.
dark background with red stripes?
what twrp version have you flash?
use last version 3.2.3-4 for oreo