Related
Hi!
I just bought a Nexus 4 with broken touch screen which I replaced myself.
After I replaced it, I decided to start fresh and updated the device directly to stock 4.4 using fastboot commands and got stuck in bootloop (4 circles going on for hours).
Then I tried different factory images and managed to boot under official Android 4.2.2 and it worked flawlessly until I tried to update with 4.3 OTA (with radio .83)
I found out that downgrading radio from .83 to .48 (or .53) allows the device to boot under Android 4.3.
I'm now stuck at this stage because the same trick does not work after 4.4 OTA (from 4.3).
The issue seems to be acknowledged by Google but they don't seem to have an official software fix for it since they only go for a replacement.
I'm considering an RMA but since I replaced the screen myself, I'm facing the risk to be charged 200€ if my warranty gets void (if they really control the device as they say).
Anyone managed to fix this issue? It seems to be linked to the radio (can't go further than radio .48 / .53)?
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
neoantho said:
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
Click to expand...
Click to collapse
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
varun037 said:
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
Click to expand...
Click to collapse
Did you find a solution?
Not yet. I will definitely post if I am able to find one. Researching on the topic currently.
I've got the same problem with 4.3 bootloop. Could this be fixed with custom rom?
Try flashing 4.2.2 rom - custom or stock
I'm with 4.2.2... and that's not what I asked. I want 4.4.2. Is it possible to load custom kit kat with this kind of sensor problems?
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
varun037 said:
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
Click to expand...
Click to collapse
I'm on 4.3 and the sensors dont work ... the proximity, gyro... nothing works... any solution?
Hello friends, i have a similar problem.
I went to replace the glass and warmed him a lot and damaged the lcd. I bought a complete lcd with touch, but when installing it the cel came in infinite boot, Flashed the 4.2.2 and booted but sensor is working by testing q I did for an app, the problem is they do not find my network and baseband ta as unknown, been through the radio's 4.2.2 (the version I am now). the motherboard was not with the screen when I get heated to the glass, were in housing with the display flex earpiece with proximity sensor and flex usb that has the microphone and led, everything is normal, the LED only that does not work. One would like some light please. I thought about buying the flex usb to see if it resolves, but does not want to risk spending for nothing. Thank you very much!
Sorry for my english, I'm using google translator
Sorry to Disturb
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Gloftking said:
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Click to expand...
Click to collapse
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
FEW
varun037 said:
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
Click to expand...
Click to collapse
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Gloftking said:
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Click to expand...
Click to collapse
Follow this. It has the reset flag removed and will not wipe your data
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
Hi,
I am facing the same issue .. Nexus 4 is stuck at boot loader after screen replacement .. is there any solution that I can follow to resolve this .
Regards,
Ripu Daman
The same problem with me, i did replaced my phone screen. I didn't notice that could damaged the phone. :crying:
so, theres no way to solve ??
Only way is to downgrade the os version to 4.2.2 and stay there.
nexus 4 stuck at boot loop.
Hi guys i have the same problem as you are describing, o got a nexus 4 android 4.2.2 JQRW build I've flashed it from all different ways and i just got flash cm10.2 and carbon rom but only stuff jeallybean and as someone said here i used adb sideload to push the update 4.3 and got stuck at the boot but i flash the radio 84 to 48 and my phone boot Fine but i am stuck at jeallybean yet and i want chroma rom android 7
---------- Post added at 03:00 AM ---------- Previous post was at 02:56 AM ----------
Please we need a wise man to fix this problem. I am tired of flashing stock img and custom ron for nothing.
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
x102x96x said:
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
Click to expand...
Click to collapse
It was an official update so short of rooting it and flashing a new firmware i don't see any other options.
jake262 said:
It was an official update so short of rooting it and flashing a new firmware i don't see any other options.
Click to expand...
Click to collapse
rooting is not necessary for flashing stock rom.
I'm having the same problems. Screen locks up often when I'm browsing in Chrome. For Gods sake this has 3gb of RAM!!!!!
Sent from my Nexus 7 using Tapatalk
x102x96x said:
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
Click to expand...
Click to collapse
ok so i flashed a stock kitkat firnware. the problem is still there.
jake262 said:
ok so i flashed a stock kitkat firnware. the problem is still there.
Click to expand...
Click to collapse
flashed original rom via odin 3.09. Them hard reset. I have the same problem with screen. Is software problem.
Sorry for my bad English.
jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
While phone works just pull out the battery and also don't use cover. I think its just about samsungs politics. ..
Sorry for my English
Same issue
jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
I also have the exact same problem... I already did the factory reset but no luck. I increased the sensitivity but still happens...Can anyone help us? or it is caused by the recent upgrade of OS to kitkat version... Thanks.
GOOD NEWS!
I have been having this issue as well. Lots of research on the net has provided me with no real solutions. I think there is something missing in this update. I do not know what it is im not that smart but something is wrong across the board.
I have done a master reset back to factory and within minutes of the set up it started lagging/ not responding again. Figured i would give it a few days and well nothing changed so I contacted T-mobile and spoke with Tech Support located in Texas and he concluded that it is an SD card. He says that the SD card was on the phone prior to the update and is causing the issue since its old. WTF! I told him that the processor, ram, HDD, CPU are all considered old now. Personally I think its a stupid response.
I am going to give this a shot anyways. NO SD card no pictures no music.... Already within 15 minutes of no SD card issues are still there. I am really starting to hate this phone because of this update. Hoping to get a replacement (new) with 4.3 still on it. NO UPDATE for me till i know this and several issues are fixed.
I know i could root but i dont feel i should have to to fix any issues.
Has anyone else found a solution or heard of one yet?
Just try this , go to setting / general / power save , swith it on.
Then wait a moment before you try your phone again.
my wife phone got this issue because of over heating.
after switching the power save , the issue is gone.
update... contacted Tmobile within the last hour and apparently this rep said this is a known issue. She contacted Samsung and Google (could be blowing smoke up you know what) but she came back and said they are very aware of the issues and are vigorously working on a fix and your informations will be one of the first ones to get it. She was saying 4.4 (kitkat) screwed up a lot of Samsung devices. BTW she was also having the same problems. All replacement phones will come with 4.4 so exchanging is out of the question.
Regarding the power saving thing ill give it a shot. It was on before the master reset. Noticed it was off when i went in. On now so ill try then.
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
pimpl said:
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
Click to expand...
Click to collapse
Hi Mate,
Not saying this is your problem but i seen some people having issues with the power button , symptoms are similar to your random reboots like in constant reset....check the power button see if is stock and easy way to check is try to go to recovery without pressing the power button.....if is really stuck or short out you should be able to go to recovery without ( for a short time) ....that will prove that the problem is coming from there...
Of course if is very sporadic wait until is happening for testing ..
I had the same problem before because I disabled knox using supersu. What I did was delete all knox related apps and everything is good.
Many users had this problems with Knox as well. Try to uninstall everything relating to Knox, maybe it will work
Gesendet von meinem GT-I9505 mit Tapatalk
pimpl said:
Hallo all! I really HOPE someone might help me with a really annoying issue:
I recently bought a Samsung Galaxy S4 Black-Edition (Modelnumber: GT-I9505). From day one I rooted the phone
(CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
but still use the samsung stock Rom. My Android version is 4.4.2 and I had the genuine firmware-version I9505XXUGNF1 from the Samsung homepage (sammobile).
.. Everything has been working perfectly for about a month, but then suddendly my phone startet to turn off and on again randomly by itself. Note that the turning on is much quicker then the regular booting-up (after I properly shut the system down) and that the autonomious turning on does not require the PIN-code.
I tried to fix this problem by:
- removing the external Memory-Card,
- removing the sim-card,
- deinstalling busybox,
- completly whiping the system (via TeamWin recovery) and installing EVERYTHING from scrach (no Backup-restoring) --> tried this four times!,
- installing the latest firmware-version I9505XXUGNG2,
- changing the battery,
- COMPLETLY canging the device: (installing EVERYTHING from scrach (no Backup-restoring) on a completly new device (new Galaxy S4 Black-Edition)) --> same problem!
--> NOTHING WORKED OUT!!!! So I'm REALLY annoyed about that!
Note, that after a complete restoring of the system, the phone works perfectly for some days - maybe 4-3 - and then the turning-off-and-on terror returns.
I put a screenshot of my battery-trajectory as an attachment. You can see two vertical lines indicating that the phone has turned itself off for a short ammount of time.
Does anyone have an idea what could be the cause for that issue? Is there anyone sharing the same problem? What could I try to solve that problem? Is there mayby a taskmanager-app logging systemerrors, so I could check, what happened before the turning off?
I'm VERY thankful for any sort of help!
Click to expand...
Click to collapse
Delete all knox related apps via "titanum backup" and you are good to go! :good:
martikip said:
Delete all knox related apps via "titanum backup" and you are good to go! :good:
Click to expand...
Click to collapse
Well.. What can I say? Thank you SOOOO MUCH!! The problem is solved! Indeed, deleting all Knox-Entries via Titanium Bakup really solved the problem. Now, everything is fine and the system runs smoothly. Again, thank you very much!
pimpl said:
Well.. What can I say? Thank you SOOOO MUCH!! The problem is solved! Indeed, deleting all Knox-Entries via Titanium Bakup really solved the problem. Now, everything is fine and the system runs smoothly. Again, thank you very much!
Click to expand...
Click to collapse
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Marcelocohenarg said:
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Click to expand...
Click to collapse
Indeed, I have never had a problem again, since I deleted the Knox-stuff. Just do it and the problem will be solved!
Marcelocohenarg said:
Hi PIMPL
am curious about this because today my S4 started to do random shuts off. So your phone never showed the problem again after uninstalling all the Knox stuff? I have an I9500 Android 4.4.2; everything stock, non rooted.
Thanks!
Click to expand...
Click to collapse
It's right uninstall Knox and be happy
Gesendet von meinem GT-I9505 mit Tapatalk
I have the same issue at the moment - Phone is completely standard (Not rooted). All has been good until the morning of the 30th August when there was a new firmware update applied. I had already had the Kit Kat update earlier in August and the phone had been working with no issue, since this 220Mb odd 'patch' the phone will just randomly reboot, I say random but it just seems after it has been idle (Screen off) for a while on unlocking I can start an app (pretty much anything) and about 5 seconds later the phone will reboot. As the OP mentioned it is a faster than normal reboot and it doesn't play the normal start up sound either.
I am not sure what the update did, it mentioned ironically that it was fixing stability issues!!! - Is there a way without rooting the phone to roll back the firmware to before the patch?
Cheers.
Factory reset worked too
I have been struggling with a similar problem on my GT-I9505 since receiving a system update on May 30, 2014 -- random reboots many times a day, plus fairly reliable reboots about 30-40 seconds into any received phone call. I tried cleaning caches, uninstalling recently installed apps and then other unneeded apps, installing new updates, and lots of other things. My last resort was rooting and removing Knox as suggested here. But first I tried a factory reset, and it worked! I've now gone several days without an unintentional reboot. It's a pain to have to restore backups and reinstall apps, but it was worth it. I hope this information is helpful to someone.
Issues on my CF auto-rooted GT i9505
My firmware is the stock I9505XXUGNG8-DBT and rooted with CF Auto-root.and Phill''s CWM.
1. When I wake up my phone by pushing the home button my first screen is frozen until I push the home button again for 2 or 3 seconds. Only since then I can use my apps.
2. By incomming phone calls my phone reboots and I lose contact, so they have to call me again, Then everything is well.
3.The time on my homescreen doesn''t synchronize until I push the home button for the second time waking up the phone .
I already used SSCF Xposed. That didn''t help.
Somebody the same issues. Or somebody who got some tips for me.
Idebutterpiep said:
My firmware is the stock I9505XXUGNG8-DBT and rooted with CF Auto-root.and Phill''s CWM.
1. When I wake up my phone by pushing the home button my first screen is frozen until I push the home button again for 2 or 3 seconds. Only since then I can use my apps.
2. By incomming phone calls my phone reboots and I lose contact, so they have to call me again, Then everything is well.
3.The time on my homescreen doesn''t synchronize until I push the home button for the second time waking up the phone .
I already used SSCF Xposed. That didn''t help.
Somebody the same issues. Or somebody who got some tips for me.
Click to expand...
Click to collapse
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
DarkerTimes said:
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
No do I have to?
DarkerTimes said:
Did you uninstall every Knox app?
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
I guess this will help. Knox often causes this issues. Just uninstall everything relating to Knox with Titanium Backup
Sent from my Galaxy S4 using Tapatalk
I'm having the same problem as OP.
I've frozen all Knox related apps in Titanium Backup, but the problem persists. Do I need to fully delete the apps do you think? Is there a difference?
c0dewana said:
I'm having the same problem as OP.
I've frozen all Knox related apps in Titanium Backup, but the problem persists. Do I need to fully delete the apps do you think? Is there a difference?
Click to expand...
Click to collapse
I think I solved my problem: I deleted all Knox related items and when I rebooted my phone again it stucks on the Samsung logo. I installed the stock I9505XXUGNG8-DBT again with Odin. Installed CF Auto-root.and Phill''s CWM again. Installed Supersu again.
Now everything is working again without the frozen screen, time synchronizes and no booting by incoming phone call anymore.
Hi All
I have an issue with my S5 Plus (G901F) a few days ago I rooted, TWRP and installed the stable MM ROM from Tkkg1994 and have been happily using my phone. This morning while I was opening the Gmail app the device rebooted and when it came back up I noticed WiFi was not on. Pressing the quick menu WiFi button turns it green for a second before going back to disabled. Likewise going to into settings - WFi and using the slider does not work either, it just goes back to off.
So far, I have wiped ART/Dalvik, reflashed BL and Modem, factory reset. Wiped the whole device and redid everything including diffrerent ROM's on the same BL/Modem (CPE1) and have the same result.
Everything else works, just not WiFi, I should also add I have tried with and without the SD card and disabling/enabling other radios (GPS/BT) in different combos has not worked either.
Has anyone come across this and can they suggest next steps?
I'm currently downloading the stock ROM that came with my phone to see if that helps.
Cheers
Stock ROM did not help.
Did you find solution? I have recently started to have same issue with same device.
jaakla said:
Did you find solution? I have recently started to have same issue with same device.
Click to expand...
Click to collapse
Probably not. The S5 seems to suffer a lot by such issues. I bought mine 3 months ago in a shop. It worked for about 2 months very well. Then all of the sudden it became hot in my pocket so i had to quickly remove the battery. After this the device suffered by ocessional reboots. Nothing helped. Even trying to reflash the stock firmware by trying several Pit´s.
Finally got a replacement as obviously either the RAM or the CPU got defective. The other phone lasted for one week as the wifi module got defective there. Nothing helped either. Now it´s my 3th S5. This weekend my flashlight and camera stopped working. Fortunally got this fixed by reflashing the stock firmware.
Honestly I like the phone but it seems to be quite buggy. Never got such problems with my old S4 and am thinking about going back to the older device.
dude try flashing 4 files flash through odin
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