Hello All,
I have a small problem. if anyone can help me out please help.
Recently I cracked my screen and hence went to a local shop to get it replaced. Once replaced my phone was not booting. I thought it maybe a software issue. Later I realized this happens due to hardware and maybe some connection is not made, like the headphone jack.
I opened my nexus and checked. Turns out that guy dropped my light sensor which is close to the front camera. There is no light sensor now in the phone. I cannot go back to him.
Can anyone please suggest me some ROM which skips this hardware test? or any other solution please?
From what i remember, proximity sensor causes such issue on Nexus 4. The solution was to downgrade modem to the very first one (from 4.2.2 factory image) and then flash either 4.2.2 or 4.3 stock firmware. Switching modem to a newer one causes bootloop on 4.3 and up. Try this, then it's possible that some more current custom ROM will work with an old modem as well, but that's something you'll have to check on your own.
THANK YOU!
Sir,
Thanks A LOT!
I cannot thank you enough. I have search everywhere, and your solution worked. I installed 4..2.2 radio then pre rooted factory image. Worked like charm
I am really grateful. Thank you.
KrzychuG said:
From what i remember, proximity sensor causes such issue on Nexus 4. The solution was to downgrade modem to the very first one (from 4.2.2 factory image) and then flash either 4.2.2 or 4.3 stock firmware. Switching modem to a newer one causes bootloop on 4.3 and up. Try this, then it's possible that some more current custom ROM will work with an old modem as well, but that's something you'll have to check on your own.
Click to expand...
Click to collapse
Related
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
I have the same problem, can someone help ?
Any updates?
I have the same problem. I used to get the bootloop when I updated from 4.4.3 to 4.4.4 and from 4.4.4 to 5.0 and from 5.0 to 5.01 and in all those times, from what I can recall, a wiping of the cache/delvik + fix-permissions + install the modified boot image from NRT - solved the problem.
However - a couple of days ago, after getting the Google Cardboard and playing around with it, installing all the VR stuff and playing with magnets around my phone to get it to work with the VR - I think I must've damaged something because it suddenly died and refused to get back up and out of a bootloop. I tried the above procedures and it didn't work. I went back to version 5.0, then 4.4.4 and further back till only 4.2.2 worked, as with the first post here. It's the only version that doesn't give me the bootloop. If I try then to upgrade I again get the bootloop, whether it's a full flashing or an OTA update (to 4.3).
One thing I noticed with 4.2.2 - it's not acting all that well: when I download apps through Google Play some of them seem to get stuck at 85-95% on the download and won't install. Maybe I have a faulty storage issue...?
Any insight on how to fix that?? Any news from those who experienced the same issue?
Thanks!
tiagomoraisc said:
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
Click to expand...
Click to collapse
no good news ...
hummus said:
I have the same problem. I used to get the bootloop when I updated from 4.4.3 to 4.4.4 and from 4.4.4 to 5.0 and from 5.0 to 5.01 and in all those times, from what I can recall, a wiping of the cache/delvik + fix-permissions + install the modified boot image from NRT - solved the problem.
However - a couple of days ago, after getting the Google Cardboard and playing around with it, installing all the VR stuff and playing with magnets around my phone to get it to work with the VR - I think I must've damaged something because it suddenly died and refused to get back up and out of a bootloop. I tried the above procedures and it didn't work. I went back to version 5.0, then 4.4.4 and further back till only 4.2.2 worked, as with the first post here. It's the only version that doesn't give me the bootloop. If I try then to upgrade I again get the bootloop, whether it's a full flashing or an OTA update (to 4.3).
One thing I noticed with 4.2.2 - it's not acting all that well: when I download apps through Google Play some of them seem to get stuck at 85-95% on the download and won't install. Maybe I have a faulty storage issue...?
Any insight on how to fix that?? Any news from those who experienced the same issue?
Thanks!
Click to expand...
Click to collapse
I think it's a defective device. You have to repair or change it. Sorry
No Sensors
Looks like none of my sensors are working, judging from 3 sensor testing apps I've downloaded. Seems as if the motherboard is defective.
tiagomoraisc said:
no good news ...
Click to expand...
Click to collapse
hummus said:
Looks like none of my sensors are working, judging from 3 sensor testing apps I've downloaded. Seems as if the motherboard is defective.
Click to expand...
Click to collapse
The same situation I have
Fix
tiagomoraisc said:
Hello Guys,
I'm with a problem in my #nexus4 .. If i update my device to #android 4.3 or newer my phone gets #bootloop and don't start anymore. I read a lot of tips to solve that but nothing worked. I tried to reflash with stock firmware from google (developers images to nexus devices) but didnt work (flash-all.bat), i tried use #NexusRootToolkit but happened the same situation. I tried to install the versions 4.3, 4.4, 4.4.2, 4.4.4, 5.0 and happened the same problem at all.
Someone could help me? Because i didnt find how to solve since a last year. I'm using android 4.2.2 because its the only one that works.
I tried all methods like flash stock rom, but, wont works. ....
Could someone help me with that please??
Click to expand...
Click to collapse
I made a similar thread, and found a fix.
Here http://forum.xda-developers.com/nexus-4/help/nexus-4-jellybean-4-2-2-t3472292#post68941174
Hey everybody,
I've been having an issue lately. Since I upgraded to Android Lollipop, I have not been able to get a GPS lock anymore. This issue only applies when I'm on a Lollipop ROM. As soon as I flash back to a kitkat TW ROM, everything works again. When I go back to a Lollipop ROM, the issue returns again.. No GPS lock. This is not ROM specific, but just related to Lollipop in my experience.
I have not seen anyone else yet with this issue, so I find this very strange. I'm currently on the latest version of GPE5 by @Danvdh if this helps. But like I mentioned before, the issue exists on every Lollipop ROM.
If someone could please help me, this would be very much appreciated! Thanks!
Anyone? ?
Me Gusta!
It seems to be a Lollipop thing.
I have the same issue with my Find 7 since installing Lollipop.
See this discussion:
https://code.google.com/p/android/issues/detail?id=81140
Me Gusta said:
Anyone?
Me Gusta!
Click to expand...
Click to collapse
mate, flash official firmaware and reset /set up your original csc with samsung phone info+ app from google play , worked on 3 phones until now this solution , be carefully csc reset gonna wipe your internal storage
thanks, i will try it
Hi
I've been trying to get to the bottom or this for months and months, no clue what to do.
Firstly, no matter what ROM i try, whether it be stock or not, sensors do not work AT ALL. I've tried about 10 ROMs, and no joy.
When i first had my phone, it was on stock 4.3 ROM, and rotation worked fine. after this i upgraded to 4.4.2 OTA and rotation still worked. As soon as i rooted my phone, all sensors died and now i cannot fix them. The phone also has a stupid amount of lag, especially when trying to answer a call. I tried then going back to stock 4.4.2, but the sensors remained broken
I have tried reinstalling Samsung HUB as i found in a few posts on the internet, but again this does nothing at all.
Can someone please please help, any ideas no matter how far-fetched are welcome,.
Thank you in advance.
hi my device 900f and proximity sensor 4.4.2 works fine but i flash any 5.0 lollipop my proximity sensor its broken pls help me
sorry my bad english
You didn't say anything beside your proximity sensor not working..
Did you do a full wipe?
What's your boatloader?
What build are you on?
Custom kernel?
Anything else you installed?
nomenore said:
hi my device 900f and proximity sensor 4.4.2 works fine but i flash any 5.0 lollipop my proximity sensor its broken pls help me
sorry my bad english
Click to expand...
Click to collapse
did you tried *#0*# ? this will take you to diagnostics menu. Go to sensors.. Check if values of proximity sensor change as you move your hand close to the sensor. Check light sensor as well.
copy'
hi guys, im not sure whether having same issue as op, but in my case...whenever i answered a call and decides to end it --->pull phone away from face it does nt light up instantly 1-2 delay (at random times, sometimes it light up instantly sometimes it doesnt). anyone with such issue? everything stock 5.0 Boa3 rom..thx
i have done full wipe, reflash rom again*
Nic2215 said:
hi guys, im not sure whether having same issue as op, but in my case...whenever i answered a call and decides to end it --->pull phone away from face it does nt light up instantly 1-2 delay (at random times, sometimes it light up instantly sometimes it doesnt). anyone with such issue? everything stock 5.0 Boa3 rom..thx
i have done full wipe, reflash rom again*
Click to expand...
Click to collapse
This is definitely a firmware issue. i am also facing it..its really annoying. Shame on samsung that they didnt refine their ROM before its release......These aren't there in KK.
I am looking for a fix but till now couldnt find any....lets see.
saqaw said:
This is definitely a firmware issue. i am also facing it..its really annoying. Shame on samsung that they didnt refine their ROM before its release......These aren't there in KK.
I am looking for a fix but till now couldnt find any....lets see.
Click to expand...
Click to collapse
Same here happens to all my gadgets on lolipop not only s5...sadly not sure if boa2 had address the problem. Will test boa2 when I get my SD card
Hi,
Got a strange issue on my i9505. Evrything working fine at boot until i lock the screen (or until it lock by himself).
Then touch screen become irresponsive.
other roms , factory reset nothing works ...strange because seems to be driver related.
I was about to odin flash a samsung rom ...
Has anybody ever experienced such behaviour ?
Z
Problem solved by reflashing samsung firmware than soin all he road again .
Suppose bl related.
zapatt said:
Problem solved by reflashing samsung firmware than soin all he road again .
Suppose bl related.
Click to expand...
Click to collapse
Hello!
I know that reviving dead threads is not very popular but would you please tell me what you wanted to say in your post? I presume that some auto complete function garbled your text. Which revision of Samsung firmware did you flash to solve the problem?
I have exactly the same problem. Moreover, it prevents me from installing Optimized CM13 since I don't have touch in AROMA installer.
eTaurus said:
Hello!
I know that reviving dead threads is not very popular but would you please tell me what you wanted to say in your post? I presume that some auto complete function garbled your text. Which revision of Samsung firmware did you flash to solve the problem?
I have exactly the same problem. Moreover, it prevents me from installing Optimized CM13 since I don't have touch in AROMA installer.
Click to expand...
Click to collapse
Hi Taurus,
I m not sure we got the same issue. My touchscreen become irresponsive After being Locked, either in twrp or in Android. As far as I Can remember, it Was related to custom kernel, i have to reflash à Samsung kernel. I think i Was underground jdc lollipop rom.
We have exactly the same problem, actually. It prevents me from installing a custom ROM which sucks!