Hello, i recently ordered a new digitizer & lcd for my phone but the phone stucks on samsung core 2 logo when i turn it on.
I figured out that the problem is the digitizer and not the lcd since the new lcd boots with the old digitizer.
BUT if i turn on the phone with the old parts and replace the lcd+digitizer while the phone is turned on, everything works perfect until you turn off the phone again and it stucks at logo again.
So, i assume that there is a code in the firmware that doesnt let the phone boot with thirdparty replacements. If i am correct, will a custom firmware solve my problem? Or, is there any other solution?
IzNoO said:
Hello, i recently ordered a new digitizer & lcd for my phone but the phone stucks on samsung core 2 logo when i turn it on.
I figured out that the problem is the digitizer and not the lcd since the new lcd boots with the old digitizer.
BUT if i turn on the phone with the old parts and replace the lcd+digitizer while the phone is turned on, everything works perfect until you turn off the phone again and it stucks at logo again.
So, i assume that there is a code in the firmware that doesnt let the phone boot with thirdparty replacements. If i am correct, will a custom firmware solve my problem? Or, is there any other solution?
Click to expand...
Click to collapse
u can install speedrom, i had the same issue and it fixed the problem. but make sure u have twrp or any custom recovery and root.
Related
Hello Guys,
Screen in my i9505 stopped working,. It looked as it was some lcd problem so I ordered new screen and...it did not help so I would like to try warranty option but I cannot do anything since my screen is off. The phone probably is working. It is visible in Odin and allows flashing firmware. Booting sound is ok and it looks like only the screen is damaged but it is not issue since another screen also not worked.
The question is how to blindly restore some stock firwmare and reset flashing counter without screen? Will hdmi cable help when I buy it?
Triangle away I think works only from phone itself it is not doable via Odin somehow?
Thank you!
I cracked my screen a few months back and am just now getting around to attempting to replace it. After going through the steps to replace it, I began to experience a blank screen when attempting to boot into the rom.
The screen works just fine in bootloader mode, or in recovery. If I attempt to boot into the rom, the screen will go blank after a few seconds of showing the rom logo. I can tell the N7 is on as I have it connected to my laptop.
Although, my screen was cracked, I was not having this type of issue prior to replacing the screen. I attempted to flash into stock on the off chance that it is a software issue, with no change in the situation. I am wondering if maybe I damaged some component while attempting to replace the screen.
Any advice or assistance is appreciated. Thank you.
I messed up with my LG G2 D802 and i need help because i believe it's a software problem.
When i was installing the latest cm12.1 nightly, after trying a few other roms, i also installed, by mistake, an old jb bootloader/bootstack.
As result the phone entered in Bootloop, but not a normal bootloop, on the screen start appearing some crazy interferences and then the phone boot up, but the screen not. The phone made sounds and the touchscreen work, but the screen was black/off.
I've managed to solve the problem with an unbrick method, but now i have a huge problem: the screen, on the rigth side, from the top to the botton has 6/7 black lines. I have no idea how to solve this and if is a hardware problem ... I've read it's an kernel problem, not hardware, but don't know how to solve the problem :/
Picture:
https://meocloud.pt/link/58d13900-ffa8-4114-8957-8c4b973bad1a/IMG_20150916_020454.jpg/
I feel your pain
Hi mate
Same thing happened to me.
Background info: I had successfully upgraded to CM12.1 , was running fine for a few days then I wanted to update my TWRP, updated the recovery and just went to check that I had OTG cable support then boom, boot loop.
It didnt just loop it just loaded loaded loaded, then the screen made some funny sounds. and then shut down. I hard reset to recovery and reinstalled CM12.1 and was able to successfully exit the loop. but damage to screen had occurred in the exact same place, and method right side of the screen.
Tried rinstalling original jellybean software from my backup. no success, and also flashing other versions of CM12.1 nothing.
After some research I saw that this is a manufacturing fault and that this occured quite often. it appears that the best solution is to buy a new screen as it is the actual hardware that is damaged in the screen digitizer. I might be wrong, and I pray that I am because I want to fix it too. in the end I just bought a new note 4 (not note 5 as i wanted SDcard storage). Phone was 2 years old and a new screen costs a fortune. But i miss my little G2 and its super fast speed and simpleness. :crying::crying:
If someone else has the solution to this problem on the forum we are all ears.
Hi,so i replaced LCD in my I9515, I've been doing this with youtube tutorial. Before 1-2 weeks ago my phone boot normally but i couldnt see anything due to broken LCD. In store, guy took my battery and connected it to a naked motherboard and lcd to see if it's working. After replacment when i try to boot it's stuck on Samsung Galaxy S4 logo and wont boot further. I can go into download mode, computer and odin are seeing connected phone, but i cannot boot into recovery it's just showing blue "booting recovery" and nothing happening. When I charging it, the grey battery pops out, but when i unplug it the battery is still there like it's still connected. Sometimes when i try to turn it off when it's stuck on galaxy s4 logo it's turning off then on by itself like 2 or 3 times. Any ideas how to fix it? It's hardware or software problem? In a minutes i'll try to flash stock soft from sammobile. Phone was never rooted and no custom roms were installed.
Thanks for all help.
EDIT Flashing with ODIN not solved the problem
EDIT Now phone doesnt show battery when connected just one vibrate and screen is blank, and when i try to boot it while connected it's just vibrating and still black screen. When it was connected to pc it was vibrating every 2 seconds. When I try to boot it's by itself trying to boot recovery but it's not booting and blue "recovery booting" just hang on top of screen and nothing happening.
EDIT After restarting it from download mode it's get back to the problem i had in the beggining
EDIT Just flashed 4-files soft with PIT and nothing changed
I think the screen may not have been replaced properly.
And motherboard is broken now ? I think i did everything right.
There might be a short circuit somewhere. I can't tell you exactly.
So the best option now it's tech look at it?
Saintseu said:
So the best option now it's tech look at it?
Click to expand...
Click to collapse
Yes. Unless you have some tech-savvy friends who could also look at it.
Hello today a screen replacement i ordered in aliexpress arrived and i did change it carefully (i did this process 2 times 1 in my phone and another in a cousin mi a1. No problems).
The thing is... after this i turn on the phone and the screen turns on but only until rom starts to load and then it comes black as if it wasn't turn on. The screen turns on also in fastboot mode but instantly shutdown when entering to recovery mode or normal boot as i said. The phone is working properly the rom loads and there is notification sounds and touch is working too.
If anyone can help me please. The only thing i can thing of is that the screen came with some strange malfunction.
EDIT: I flashed stock rom with flash_all and got the screen and everything working fine. I then tried again to flash a custom rom as i had before and screen failed to turn on again. Then i flashed stock kernel just to try if was it the cause and after this screen worked fine again but i lost wifi and probably there is other issues because of the stock kernel on a custom rom. I don't know if it may be because a different display driver or a kernel setting that may cause this malfunction. Hope someone can help me to solve this as i really want to use a custom rom.