A3 2016 SM-A310F Camera flash doesn't work properly - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Hello everyone,
In russian segment of the internet many cases that camera led flash is not working properly.
But i didn't find any similar issue here. So i am trying to describe symptoms below:
1. Firmware - latest 5.1.1 [A310FXXU2APDC SER]
2. Torch is working perfect
3. When you tried to make a shot with flash enabled - autofocus is working properly and led flash are working, but when it makes a shot - flash is blink on the 5% of power for short period of time. Video was taken by someone from 4pda forum: _youtube.com/watch?v=zEAtzw7Knj0
Photos after that looks like black square of Malevich.
Wipes - don't help
Flash firmware + wipes - don't help (i tried 1 file fw and 4 files fw)
Did anybody face with similar case? How you solve this? This is a really strange bug, because LED is working good, so it looks like software issue, but changing firmware is not helping as you can see above.
Thank you for any help,
BR Alexey.

i have the same problem
yeah..

ttdom said:
i have the same problem
yeah..
Click to expand...
Click to collapse
Thank you for your reply.
Didn't find solution. Today i passed it to service center Samsung.

@leksey said:
Thank you for your reply.
Didn't find solution. Today i passed it to service center Samsung.
Click to expand...
Click to collapse
it doesnt happen all of the time i think but a lot..

Fixed it with the following:
And now the very solution to the problem:
I continued those that put the phone on charge, I go to the camera, I turn on the flash, press on the side rocker (to take pictures), and while the camera focuses - pull charger from the outlet, and voila, the phone now makes normal images with the flash under all conditions as before.
Here is an unexpected decision.

how to overcame this problem?

@leksey said:
Hello everyone,
In russian segment of the internet many cases that camera led flash is not working properly.
But i didn't find any similar issue here. So i am trying to describe symptoms below:
1. Firmware - latest 5.1.1 [A310FXXU2APDC SER]
2. Torch is working perfect
3. When you tried to make a shot with flash enabled - autofocus is working properly and led flash are working, but when it makes a shot - flash is blink on the 5% of power for short period of time. Video was taken by someone from 4pda forum: _youtube.com/watch?v=zEAtzw7Knj0
Photos after that looks like black square of Malevich.
Wipes - don't help
Flash firmware + wipes - don't help (i tried 1 file fw and 4 files fw)
Did anybody face with similar case? How you solve this? This is a really strange bug, because LED is working good, so it looks like software issue, but changing firmware is not helping as you can see above.
Thank you for any help,
BR Alexey.
Click to expand...
Click to collapse
Try wipe cache /dalvik

Same problem... plz help to fix this problem

ÉNITSED said:
Try wipe cache /dalvik
Click to expand...
Click to collapse
Mainboard was replaced in service center. I sold this phone and bought A3-2017.

cobr said:
Fixed it with the following:
And now the very solution to the problem:
I continued those that put the phone on charge, I go to the camera, I turn on the flash, press on the side rocker (to take pictures), and while the camera focuses - pull charger from the outlet, and voila, the phone now makes normal images with the flash under all conditions as before.
Here is an unexpected decision.
Click to expand...
Click to collapse
Hi, I updated my Samsung A3 (SM-A310F) to Android 7.0 recently. At the beginning everything worked fine but maybe 2 days ago I started to have a problem with camera taking pics with flash (same as described in first post). I cleared cache for camera app, gallery app and cache partition as well. It didn't help. I used method posted by "cobr" and it worked straight away. Huge Thanks to cobr
gemini

Hello, i have the same problem on my a3 2016, but the solution about the charger didnt work for me...
---------- Post added at 04:15 PM ---------- Previous post was at 04:10 PM ----------
Hello, i have the same problem, and the solution cobr posted didnt work for me. any ideas?

Cobr's recommendation worked!
Connect the charger to your phone. While charging the phone, launch the camera app.
Press any of the volume button (up or down) to take a shot, immediately the first flash comes up, quickly disconnect ( yank) the charger from the phone.
njoy!

Thank you cobr
I did it and it works
Thank you so much.

Related

[FIXED] black screen on hboot/recovery and camera issue (FIXED)

During an update, (PASSIMG.zip) in hboot I selected yes (to install) then about a second later, my screen
turned black and now, the only thing I can do is to boot in the installed stock rom (FRG33).
My english is not perfect, i'm sorry for that.
1. I Removed my battery after a while. (about 10 minutes)
2. Inserted the battery back in his place
3. Power down + vol down and I'm stock, I can navigate in
the menu but I can't see anything...
Anyone know how I can get my screen back ? OLED vs SLCD ?
Note: I can boot in my rom, the rom is unrooted, my phone is unlocked.
(And yes, I tried to flash recovery and another rom without success. And I can't
find a way to flash hboot again (bad signature)
I'm using the last version of hboot and radio.
If anyone have an idea of how I can fix this, this will be really appreciated.
Thanks.
I'm starting to think than my /dev/mtd/mtd0 is screwed up.
Anyone know where I can get/or generate a image of a normal mtd0 ?
At the moment I'm running debian sid dand SuperOneClick seem to freeze
after trying to chmod rageagainstthecage or psneu..
Note: Yes my screen work when the boot is completed. (but not in hboot/recovery)
bad spl ?
fblodroid
Ok, sorry for the noise, I was able to perform an update via 766a101ae02c.signed-passion-ota-60505.766a101a.zip (renamed to update.zip) and I powered off my phone.
Removed the battery to be sure there is no power at all.
and using some screenshot found on the web.
I was able to perform the update (blindly, this word exist ?) and the phone rebooted
and asked me if I want to update again (google update) I selected yes, the phone rebooted
and, VOILA, I can see again the crappy X logo with an open lock at the bottom.
Thanks again (ok for nothing, but if than can help some people...)
Yes, shame on my english again.
fblodroid
My guess is that you have an SLCD Nexus One, and the passimg installed the .33 HBOOT which doesn't work for them.
I had the same problem when flashing the MIUI-AU rom, screen went black,removed battery and replaced but the phone was dead,I was already thinking which phone to buy then when I connected the N1 to my laptop miraculously the X logo appeared and the rom launched ok
At the moment my phone is working again but I'm still having a camera issue.
About a 1 1/2 month ago I experienced this problem, no flash, no camera, just
a black screen when I try to run anything than use the camera.
Then a day, I was walking on the street and I checked to see if the flashlight was
working and obscured magic occured, the flash was working again but not the camera,
I wiped my phone again, repartitionned my SD card and installed a new rom and the
camera was back to normal.
Now, about a month later, (the problem started yesterday) i'm having the same issue.
I'm persuaded than this problem is related to a firmware problem, something related to
my /dev/mtd/mtd0 (hboot, perpaps ?) I don't know exactly where the camera firmware
is writed in the phone memory (nand)
I wiped and flashed again and again a lot of rom last night and today and the problem
still exist.
No camera/flash at all.
I'm thinking about returning the phone for warranty issue but like I said before, the
phone is unlocked... perpaps I will try to black the screen again and send the phone for
warranty... this way they cannot see (without fastboot) if the phone is locked or not.
If anyone have an idea of what I can do... a rom to recommend ?
Today I tryed to revert hboot without success...
EDIT: At the moment I'm running a rooted rom based on FRG83G.
fblodroid...
Related to my camera/flash problem:
Hum, I think I found the problem, this is hardware related, something seem to be
badly connected in the phone, I tryed too apply some force on the right border of the
phone with the flashlight ON (I previously looked on the web to see where the "contacts/plugs"
are located on the pcb (teardown pictures) and after applying some pressure, the light came ON
and now I can open and stop the "flashlight" mode.
teardown on the way ? I'm thinking about it... but i'll try to flash another rom again to see
if my camera is back.. (like in the past)
EDIT: No camera for the moment and the flashlight app light on the LED only if I select
the option "High Brightnes", ON/OFF are working with this option selected.
fblodroid
FIXED
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
http://img121.imageshack.us/i/icedqlubgg4zzbv2huge.jpg/ (in the red circles, the two pink dots)
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Hi, I have a HTC Desire GSM PVT4 (HTC__203), with the exact same issue as what is described in the original post. When I boot in hboot or recovery the screen is completely black. When I boot in the normal rom the screen works fine. I reflashed a number of RUU's successfully, but the problem remains.
The misc partition is not part of the RUU images, and I did re-flash the misc partition in an attempt to downgrade. Any idea where I can get an image for the misc partition for my device, or where I can generate one?
Thanks,
Hans
fblodroid said:
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
/link/
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Click to expand...
Click to collapse
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
soylapinta said:
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
Click to expand...
Click to collapse
Did you managed to fix it ? Be sure to check all the plugs, at best unplug everythings
and disassemble the phone entirely.
Mine is still working perfectly after two years.
fb

[Q] galaxy s4 no sound no cam

hi
i've serious problems with my galaxy s4 i9505. I rooted my phone and after that i've installed clockwork recovery. i've installed some roms and every thing worked fine. but 3 days ago, the phone started to boot randomly. after that the camera app doesn't work anymore (it hangs on black screen). And the sound doesn't work anymore too (on earphones too). if i open an app with sound then the app hangs/freezes. if i push the volume buttons i've the same problems. so i tried to flash different roms (of course i did wipe cache, dalvik, data factory reset) - but always the same problem. i did a backup before flashing any rom - so i've also tried to restore the backup, but the problems remain.
can anyone help me?
looks like we have same problem...
Sounds on my Galaxy S4 aren't working either and so do cam app... I've also tried to switch between MusicFX and BeatsAdudio (after the problem with soud begun) but with no help at all.
You guys might try to flash back to a stock rom with (Mobile) Odin to see if that solves the issue (probably will). Use Triangle Away first to reset the binary flash counter. And data factory reset after the flash. Or first try reflashing the custom rom you`re on with a full wipe without the sound mod.
hi
nothing did help. So I guess it's a hardware issue. finally I reset flash/binary counter with triangle away, then flash stock rom (of course did full wipe) then unroot. Now I try to send the phone back and claim guarantee.
Same problem
Got the same problem here.
At first at reboot the sound would occasionally come back but would be gone after a screenlock.
Also when starting up the phone would hang during startup.
Went back to unrooted and stock firmware of july 2013.
Now no sound whatsoever.
Need to send it for repair... gonna be without a phone for three weeks.
Actually the phone seems to behaves like there is a headset connected while there is not (no headset logo either).
Platypus said:
Got the same problem here.
At first at reboot the sound would occasionally come back but would be gone after a screenlock.
Also when starting up the phone would hang during startup.
Went back to unrooted and stock firmware of july 2013.
Now no sound whatsoever.
Need to send it for repair... gonna be without a phone for three weeks.
Actually the phone seems to behaves like there is a headset connected while there is not (no headset logo either).
Click to expand...
Click to collapse
I sent it to samsung. they replied that they don't what the problem is - so the didn't repair anything.
So i really don't no what to do - a mobile with no mic, front & back speaker and no workin earphones is worthless ;(((
does any one have some ideas what to do?
could it be a software issue, because in my opinion it's strange, that mic, front & back speaker and earphones doen't work - i mean these are separate hardware components... the only connection thing on hw side is the motherboard. so i could imagine it's a sw problem. but i tried different roms, set back root and went back to stock rom.... but no change.
PS: sorry for bad english...
hi all, sorry for bumping up this thread. has anyone found a solution for this? I have the same problem with my S4.
tulogista said:
hi all, sorry for bumping up this thread. has anyone found a solution for this? I have the same problem with my S4.
Click to expand...
Click to collapse
Just flashed a Google Edition ROM and no sound guys!? Sound was working perfectly on stock!??
tronje85 said:
hi
i've serious problems with my galaxy s4 i9505. I rooted my phone and after that i've installed clockwork recovery. i've installed some roms and every thing worked fine. but 3 days ago, the phone started to boot randomly. after that the camera app doesn't work anymore (it hangs on black screen). And the sound doesn't work anymore too (on earphones too). if i open an app with sound then the app hangs/freezes. if i push the volume buttons i've the same problems. so i tried to flash different roms (of course i did wipe cache, dalvik, data factory reset) - but always the same problem. i did a backup before flashing any rom - so i've also tried to restore the backup, but the problems remain.
can anyone help me?
Click to expand...
Click to collapse
Updated to the new rom recently? Try flashing MH8 BTU over it through kies then go into "STOCK" recovery and wipe. This happend to me when i flashed MH8 then flashed another rom. Its to do with the bootloader and knox security crap.
---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------
tulogista said:
hi all, sorry for bumping up this thread. has anyone found a solution for this? I have the same problem with my S4.
Click to expand...
Click to collapse
Try my solution i quoted.
Heres the thread in which it was mentioned before: http://forum.xda-developers.com/showthread.php?p=45417714#post45417714
---------- Post added at 09:09 PM ---------- Previous post was at 09:00 PM ----------
I just realised for the first few person the update wasn't even out yet so is irrelevant.
jayjay2244 said:
Try my solution i quoted.
Heres the thread in which it was mentioned before: http://forum.xda-developers.com/showthread.php?p=45417714#post45417714
Click to expand...
Click to collapse
Thanks! Yes, I saw your thread after I posted here and tried your solution. Everything is back to normal now :good:

[Q] [q] Camera failed i9500 - revisited (help)

May I have your attention please.
Greeting to all who may be concerned or able to fix camera failed issue on Samsung Galaxy S4 i9500 !!!
I know that there are other threads with similar topic, but I think we should recindle this issue as serious problem.
The story goes:
I bought slightly used S4 i9500 phone with no guarantee. It worked fine, was taking pictures and all. Splendid.
It was on some stock firmware. Some german version I think.
Then crappy and useles bloatware began to bother me. Just mountains of really crappy and uselles meaningless bloatware.
I wanted to remove that horses*it apps and therefore I rooted the phone flashing adam kernel and cofface cwm.
One lovely day i tried to take photo, camera opened with black window and showed camera failed notification with persistancy.
i flashed some newer stock firmware, it opened and was taking pictures till i tried some camera modes (action or something) and it froze with pink screen.
After that event, nothing was helpfull to fix this problem.
1. I flashed countles stock roms, nearly all available custom roms, new and old (think over 20 flashes).
2. Prior to flashing I did: Wiping dalvik, system, data, cache, preload, or full wipe, hard resets, wiping sdcard and external card.
3. Tried also nand erase (it took some time to revive phone afterwards).
4. Tried solutions like clear camera cache and data.
5. Tried turning off phone, taking battery out for some time, with full recharge,
6. Tried non stock camera apps. (e.g. camera fx, camera mx..)
7. Tried removing camera app by deleting it with titanium backup, or with root exploer - then installing it back to system apps with root explorer.
8. Tried switching sd cards- 8gb, 16, 32, 64 gb, no card, and tried settings without saving pics to sd card but internal storage.
9. Tried turning off gps, and location services
10. Tried limiting processes to 4 only.
11. Tried flashing with odin, or via cwm cofface or philz.
12. I opened phone with screwdriver to check for posible visible faults or something - all ok.
13. Flashed official firmware claimed to solve camera problems.
Maybe something more i did?- i cant remember, if i do i will notify about it.
And I ordered camera module from internet, will try to replace it - we will se what happens.
In the meantime, if someone, some wise one, genious or ordinary person, knows how to fix this persisting problem PLEASE HELP!
You will help me, and help others that have this problem.
Samsung officials, if you somehow should read this, take this into consideration. There are many eyes upon you. Provide solution for this.
Any one - SOS
FIXED IT.
Since no one cared enough to even try to help me with this problem I will not post the solution !
Said enough.
duxerica said:
FIXED IT.
Since no one cared enough to even try to help me with this problem I will not post the solution !
Said enough.
Click to expand...
Click to collapse
I too like you tried everything and found nothing. Camera takes forever to open. Hope you decide to share the solution.Knowledge should be shared.Don't be bitter about it.I'm sure if someone had a solution they would have posted it.
cheers.
duxerica said:
FIXED IT.
Since no one cared enough to even try to help me with this problem I will not post the solution !
Said enough.
Click to expand...
Click to collapse
Likewise, some people may have missed your post or nothing good to add, still I too would like to know what finally worked as I tried most of what you did.
Bests
M
If you have message "Camera failed"...
First of all try this: Open Camera app from the "Application manager" and do "Clear data", then restart the phone.
Second: Do a Factory reset (of course save your data!).
Third: Reinstall Android OS.
If this not help you, you have a hardware problem. You need to change the camera.
-------------------
Video tutorial:
http://youtu.be/3nzetqisty0

Home button not working at all (tried several fixes)

(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro
Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users
Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....
DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.
faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.
can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english
I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also
i've turned to stock i've updated to oxygen 3.0 bet and the button worked again
i think rooting installing twrp and installing different roms may be the cause of this issue
faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.
pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue
faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.
Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.
Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.
For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?
Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max

half blue half black screen after flashing a rom

hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
rukenau said:
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
Click to expand...
Click to collapse
First go to recovery and check that display problem present or not if not then flash any other custom rom or reflash rr
if you are unable to go to recovery then flash stock rom via odin it will fix every software related issue
and if flashing stock rom doesn't work then it may be hardware issue
You confirmed the model # in download mode? Tried using different version of TWRP?
I am facing same problem recently, did you find any solution ?
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
blue screen
rukenau said:
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
Click to expand...
Click to collapse
make a clean install and try a different kernel than pre installed one
maniwaraich said:
make a clean install and try a different kernel than pre installed one
Click to expand...
Click to collapse
clean install worked for a day or so, until i turned off ambient dislpay and restart. then it went blue&black again.
i tried a few kernels, some bootloaders and modems (including nordic) but problem persists.
i will try to get a logcat :/
In case anyone has the same problem: reboot to safe mode, go to settings, flip cover and turn off S-View flip cover.
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
pierpa2 said:
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
Click to expand...
Click to collapse
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
JJEgan said:
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
Click to expand...
Click to collapse
lareay flashed lots of time differents ROM sorry for the wrong forum but i can't find a solution.
Stock rom with oreo does not exist.
Solved turning off smart cover

Categories

Resources