Hello every body, hope u're all good
I have a strange problem with my S Duos, and I hope I find a solution from you
So, my phone won't accept any ROM even his stock ROM (jb4.2.2), while it accepts just a version of cm I downloaded the last year, it's (cm-12.1-20151025-UNOFFICIAL-kyleprods.zip ), so, all roms I've tried was being successfully installed with cwm, but when I reboot the phone, it just shows the Samsung logo, and after a while it turns to blank (the screen is just lighting when I press home or power button).
I notice, that i've replaced the phone's screen. And the previous screen was accepting all Roms
Hope I find a solution
Related
Hey guys,
i have 2 from in the title mentioned device(they're both dual core versions with 512 mb ram), and flashed on both a custom rom, because the stock rom available for it and the stock rom which was on it after shipping were working badly. (slow reaction on starting/stopping applications, crashing and low available memory(ram))
But the custom rom i found for them works great, without any problem until now. (only one of them, both has the same rom, but only one of them is faulty, and i don't think so it's caused by the rom flashing)
The problem occured yesterday evening after 2 days of using after flashing the custom rom. The problem itself is, that the screen became white, fully bright white.
I tried to reboot the phone maybe it just stucked or crashed or something like that, but after reboot, on startup/bootup, i got the same white screen, which became sometimes a bit dimmer, sometimes again bright, but i think that's just the screen backlight, the background remained full white.
I tried to boot into recovery mode, the same happened.
Then i tried to boot into bootloader/fastboot mode through my pc with usb cable plugged in and in adb, i tried to log into the shell. (adb shell). That's works, i can see all the folders and files in the internal storage. Anyways, i flashed back a stock rom(system and boot img, there was nothing else in it) through adb without problem, but the problem still remained.
I think the problem is related to the screen, or some cable contact failure or maybe the gpu?
Any suggestion what could be the problem, and what can i do against it?
Thanks for your answer and help in advance.
Matt
PS: i wanted to post the links to the roms too, but i don't have enough post yet.
I have the Galaxy Fame DUOS GT-S6812B variant, I installed the Unofficial CM11 from this forum (http://forum.xda-developers.com/galaxy-fame/orig-development/rom-cyanogenmod11-t2897673), and suddenly touch screen and capacitive buttons weren't working. I tried to install back the official stock rom with Odin and I had the same problem (which I didn't have before installing the CM11) after this I tried to install the stock rom with Kies and same thing. Phone loads the OS and shows the "select language" menu but screen is unresponsive and "menu" and "back" buttons don't work at all, not even light up. Only power button, "volume buttons" and "home" work. I'm getting kind of desperate, a relative gave me the phone so I could make it faster and smoother and instead I've broken it. Please, some help would be highly appreciated. I think the problem might be that installing the CM11 messed up with the Drivers and flashing back the stock couldn't fix that. Is there any way to revert the process and get the drivers back?
Thank you all in advance.
I've got an answer in another forum saying it could be the kernel, but, wouldn't the stock ROM had solved that? in case it wouldn't how can I install the original kernel and thus fix this issue?.
ringox said:
I have the Galaxy Fame DUOS GT-S6812B variant, I installed the Unofficial CM11 from this forum (http://forum.xda-developers.com/galaxy-fame/orig-development/rom-cyanogenmod11-t2897673), and suddenly touch screen and capacitive buttons weren't working. I tried to install back the official stock rom with Odin and I had the same problem (which I didn't have before installing the CM11) after this I tried to install the stock rom with Kies and same thing. Phone loads the OS and shows the "select language" menu but screen is unresponsive and "menu" and "back" buttons don't work at all, not even light up. Only power button, "volume buttons" and "home" work. I'm getting kind of desperate, a relative gave me the phone so I could make it faster and smoother and instead I've broken it. Please, some help would be highly appreciated. I think the problem might be that installing the CM11 messed up with the Drivers and flashing back the stock couldn't fix that. Is there any way to revert the process and get the drivers back?
Thank you all in advance.
I've got an answer in another forum saying it could be the kernel, but, wouldn't the stock ROM had solved that? in case it wouldn't how can I install the original kernel and thus fix this issue?.
Click to expand...
Click to collapse
i m facing the same problem!!!!!
don't know how to solve this....
@ringox....Was your problem solved? please help me because i am having the same problem...my gt 6812 stucks on select language as touch is not working...
Nothings gonna work...trust me i have tried everything...your touchscreen got fried up. The only thing you can do is get it to a nearby samsung store or any nearby mobile repairing store to get a brand new touchscreen. I recommend you to not go to samsung store as it would cost you almost rs.2500 whereas if you go to any other repairing store you can get it fixed in less than rs.1000.
Hello everyone, today I upgraded to a 'newer' version of phicomm i600 that i found online and on the installing that upgrade (in the recovery) it showed some wierd error and when it completed it went blank screen.. I hear logo and contrast is not completly dark, a bit bright (my display didn't died) and when somebody called me, i answered.. so everything is working except I cant see anything (even the phicomm logo) and I cant even load recovery cause I cant see.. Is there any program to show what is happening on mobile cause I tried UNIFLASH and didnt work and I cant even find any firmware.. so HELP PLEASE!
Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help?
The experts there may be able to help.
dark112 said:
Hello everyone, today I upgraded to a 'newer' version of phicomm i600 that i found online and on the installing that upgrade (in the recovery) it showed some wierd error and when it completed it went blank screen.. I hear logo and contrast is not completly dark, a bit bright (my display didn't died) and when somebody called me, i answered.. so everything is working except I cant see anything (even the phicomm logo) and I cant even load recovery cause I cant see.. Is there any program to show what is happening on mobile cause I tried UNIFLASH and didnt work and I cant even find any firmware.. so HELP PLEASE!
Click to expand...
Click to collapse
So, if anyone get blank screen, but not completly as mine, you can solve it like this. I noticed that a black contrast gets a little brighter sometimes. So, I entered recovery (using power + volume down) mode and noticed there is first brighter than darker blank, so i figured out that I entered recovery mode. Previously I plugged in phone in laptop and then deleted all my files on phone and sd card and only copy original rom that I have found on official SIngapore Phicomm page. Then I turned phone, entered recovery mode, then on blind, went on any kind of update (cause usually update is 2. and 3. option, internal and external, 1. is reboot now).
So I pressed down to pick that update (i guessed) and power and repeat it 2 more times and all I could see is blank. After some time, I saw a phicomm logo.. And reminder ** don't use any Phicomm update found on any internet page cause it's all wrong**
Later I have red that it have installed wrong kernel. I hope it will be at any help!
Hello!
Around a month ago I installed a custom rom on my Samsung Galaxy Note Pro 12.2 (SM-P905), which ran smoothly until a week ago, when my tablet suddenly wouldn't leave the Samsung Galaxy Logo screen when booting. I was also unable to access recovery (I had TWRP installed), however I was able to access download mode. Then I decided to try to install the stock firmware using Odin. It seemed fine until it was about halfway through the installation, when it seemed to disconnect and the installation failed. After several attempts this still happened. I also tried installing both TWRP and CWM, both of which passed in Odin, however I am still unable to access recovery mode. I also tried installing the custom rom, with the same results as I mentioned earlier. In addition to this the screen has also begun flickering a whole lot, both when showing the Samsung logo and when in download mode, however it seems to intensify during the latter. This, in addition to the fact that I am unable to get any response when it isn't hooked up to my computer, has led me to believe that there is some issue with the battery as well, however I am absolutelly clueless at the moment.
I also have to mention that this is my first post here and my first attempt at installing a custom rom or doing anything of this nature to my devices. Any help would really be appreciated!
mbrau said:
. In addition to this the screen has also begun flickering a whole lot, both when showing the Samsung logo and when in download mode, however it seems to intensify during the latter. This, in addition to the fact that I am unable to get any response when it isn't hooked up to my computer, has led me to believe that there is some issue with the battery as well, however I am absolutelly clueless at the moment.
Click to expand...
Click to collapse
Your battery connector needs to be re soldered first before trying to flash firmware.
Read the threat " Flickering Screen " for more information. Cracked battery connector will cause flickering screen, reboot, hang on samsung logo at boot..etc...
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.