I have a Nexus 4 running Carbon Rom 4.3. I faced a problem with the proximity sensor where the screen would turn off and never come back on. A repair shop fixed that problem by disconnecting the proximity and light sensors. Following the disabling of sensors, I could not get any Rom using radio above .48 to boot. The phone would always get stuck on the boot logo. After a lot of searching I came to find that 4.3 could be booted with .48 radio and went with it. However I want to update my phone to 4.4 kitkat and that isn't possible with the new radio until the proximity sensor is disconnected.
I want to know if it's possible to boot 4.4 (Custom or Official Rom) with my current hardware situation i.e with the light and proximity sensors disconnected? Is there a fix I can patch that can make it possible? I can't connect the sensors back or get a replacement device due to my location. Please help!
m.rehman028 said:
I have a Nexus 4 running Carbon Rom 4.3. I faced a problem with the proximity sensor where the screen would turn off and never come back on. A repair shop fixed that problem by disconnecting the proximity and light sensors. Following the disabling of sensors, I could not get any Rom using radio above .48 to boot. The phone would always get stuck on the boot logo. After a lot of searching I came to find that 4.3 could be booted with .48 radio and went with it. However I want to update my phone to 4.4 kitkat and that isn't possible with the new radio until the proximity sensor is disconnected.
I want to know if it's possible to boot 4.4 (Custom or Official Rom) with my current hardware situation i.e with the light and proximity sensors disconnected? Is there a fix I can patch that can make it possible? I can't connect the sensors back or get a replacement device due to my location. Please help!
Click to expand...
Click to collapse
I knew it I wasn't alone. It took me ~3 days to know that it's a proximity issue. I downloaded 7 different ROMs including stock and stuck at the boot logo. Anyways, if that's the case I would re-connect the sensors back, just waiting to get the mobile toolkit to open up my Nexus 4.
I have the same problem, my audio 3.5mm module with sensors is broken so I can use only the 4.2.2
Can I make any changes to other ROM's or bootloaders to flash Android 6 ?
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.
hi friends I m in deep trouble I have s4 i9505. whenever I open camera phone freezes for couple of seconds and black screen appears then a warning pop up with "camera failed .front cam is working fine. I have done following but none of these works.
1. 1st of all i thought its a h/w issue and I have changed 2 camera which were also the same model (i9505) of mine but it also dosn't work.
2. clear the the cache and data from application manager.
3. cleared the cache partition from recovery.
4. removed the battery and reinserted.
so plz help.me and yes there another problem. WiFi is not turning on whenever I try to turn it on it turns off by itself. I m.on lollipop5.0.1
waiting for some help
Flash the ROM again to fix your WiFi. While the ROM may help, I believe your camera problem is a hardware issue. You'll have to replace the camera module.
Strephon Alkhalikoi said:
Flash the ROM again to fix your WiFi. While the ROM may help, I believe your camera problem is a hardware issue. You'll have to replace the camera module.
Click to expand...
Click to collapse
than for reply. but I have replaced more than two camera modules. when I changed the module and open the camera. a message came updating camera firmware but after few minutes same warning came as camera failed. I think it's a software issue. kindly help me what to do.
Strephon Alkhalikoi said:
Flash the ROM again to fix your WiFi. While the ROM may help, I believe your camera problem is a hardware issue. You'll have to replace the camera module.
Click to expand...
Click to collapse
thanks for reply. but I have replaced more than two camera modules. when I changed the module and open the camera. a message came updating camera firmware but after few minutes same warning came as camera failed. I think it's a software issue. kindly help me what to do.
Flash the ROM again. You have to anyway in order to fix the WiFi issue.
Strephon Alkhalikoi said:
Flash the ROM again. You have to anyway in order to fix the WiFi issue.
Click to expand...
Click to collapse
ok i just updated 5.0.1 . and how to flash rom via odin?
Flashing a custom ROM won't help fix your WiFi. You need to flash a stock ROM through Odin, and there are threads in the S4 forums which explain how to flash a ROM. Please use the search engine to find it.
Same Problem...
Just noticed this problem 3-4 days ago. I've done a factory reset and also tested a known working rear camera in my phone - I still get an updating firmware message or can't connect to camera message when I open the camera app. Also, the flashlight won't work and disappears from the pull-down menu in Lollipop. I'm unrooted on an I9505G (GPE S4) running 5.0. Not having any other issues with the phone and have tried re-seating the rear camera on the pins over a dozen times. Cleared cache /data from the camera app, uninstalled upadates, etc. I'm stuck. My best guess is either the board, or software related and I haven't figured it out.
With the OP, once firmware had been ruled out as a problem, the only thing remaining would be a motherboard issue. He had already replaced his camera module.
i just want my camera to work no matter wifi work or not. i m stock lollipop
so kindly suggest me something for camera. btw today i will try to flash ro
Take your S4 in for service. If you've updated the ROM and still do not have a working camera, you have a problem with the motherboard, not the camera module.
Hello. I have 2 questions for you. 1st is i flashed pacman rom to my device. After that my proximity sensor killed. I formatted my phone and flashed previous rom. Proximity still not working. I tested it with sensor tester. It says your phone not allows proximity. How can i fix it?
And second question is, how can i back to stock system on g7? I cant install system with dload. Thank you all!
Nexus 6p, unlocked bootloader and running 8.1DP.
Whenever I make a call and put the phone to my ear the screen turns off and never comes back on. I tested the sensor with the device info app and I the sensor stays in the "close" position when engaged untill the app is restarted.
I did some research and I found that some users had this issue with the Nougat update but no relevant solutions were found and the 7.1.1 update fixed the problem.
I would like to avoid factory reset or locking the bootloader if possible.
Can anyone think of a possible solution?
I tried the Proximity sensor reset app from the play store and that does absolutely nothing.
EDIT: Stable 8.1 doesn't fix the issue, even after clean install and manual flash and wipe.
I'm on SuperXe 8.0 Oreo built and it works flawlessly. I remember having that issue on nougat ROMs use to drive me nuts. Every time I needed the keypad I had to fight to get the screen back on. ?
Not a factory reset. Manually wipe the phone and apply the latest 8.0 image.
So after manually flashing the 8.0 image everything worked. I thought id give 8.1 DP2 a shot and I wiped and flashed this manually. It worked during the restore but stopped working after all my apps were back, so I thought it may be an app that's causing the problem. Strated in safe mode, issue is still there. I guess Ill just have to wait for the stable 8.1 release. If anyone else is facing the issue please post here.
I have recently unlock my boot loader and install a custom rom on my asus zenfone max pro m1, at that movement my sensors are working fine, once i was update the custom rom all sensors did not working, except proximity and light sensor, and i had a problem with flash light torch it is also not working properly.
I have verified with stock rom firmware but problem was not solved. And i have tried factory reset, but output is zero.
Kindly help me out, is it any software issue or hard brick??
Please do the needful
Sensors not working
Bro me to plz help me to get sensors back
bhimachari said:
I have recently unlock my boot loader and install a custom rom on my asus zenfone max pro m1, at that movement my sensors are working fine, once i was update the custom rom all sensors did not working, except proximity and light sensor, and i had a problem with flash light torch it is also not working properly.
I have verified with stock rom firmware but problem was not solved. And i have tried factory reset, but output is zero.
Kindly help me out, is it any software issue or hard brick??
Please do the needful
Click to expand...
Click to collapse
Actually I don't know, how it returned back.. But same issue happened to me thrice.. Each time when it happens I start changing firmware 53 to 59, 59 to 82 or 82 to 59, 59 to 53 something like that..
After flashing firmware, sometimes all sensors returns back automatically.. But sometime it doesn't work.. But if you try same process everyday two or three time then someday sensors will return back.. I know it's illogical but believe me I have seen this two times..
If anyone has any better solution please share.. Before that try changing firmware and check which works perfect for you..
It's not a custom ROM related issue.. Same things happened to me even with stock ROM.. I called service centre and they told me it is motherboard related issue.. But as I told you after changing firmware it returns back so I think it's definitely firmware related issue..
Enjoy..
Swamoy said:
Actually I don't know, how it returned back.. But same issue happened to me thrice.. Each time when it happens I start changing firmware 53 to 59, 59 to 82 or 82 to 59, 59 to 53 something like that..
After flashing firmware, sometimes all sensors returns back automatically.. But sometime it doesn't work.. But if you try same process everyday two or three time then someday sensors will return back.. I know it's illogical but believe me I have seen this two times..
If anyone has any better solution please share.. Before that try changing firmware and check which works perfect for you..
It's not a custom ROM related issue.. Same things happened to me even with stock ROM.. I called service centre and they told me it is motherboard related issue.. But as I told you after changing firmware it returns back so I think it's definitely firmware related issue..
Enjoy..
Click to expand...
Click to collapse
I'll try then my light and proximity sensors are working but not orientation, gyro etc..
bhimachari said:
I have recently unlock my boot loader and install a custom rom on my asus zenfone max pro m1, at that movement my sensors are working fine, once i was update the custom rom all sensors did not working, except proximity and light sensor, and i had a problem with flash light torch it is also not working properly.
I have verified with stock rom firmware but problem was not solved. And i have tried factory reset, but output is zero.
Kindly help me out, is it any software issue or hard brick??
Please do the needful
Click to expand...
Click to collapse
did you fix it plz reply i have the same problem
Imran7junior said:
I'll try then my light and proximity sensors are working but not orientation, gyro etc..
Click to expand...
Click to collapse
did you fix it . Reply