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 guys!
My SM-G900F has its sensor stopped working last saturday...
It was working properly untill I installed a game from aptoide...
The accelerometer and the gyroscope do not transmit values when I use *#0*#
What could it be the problem? Is it a hardware or software problem?
Thanks for answers
paulocunhabr said:
Hi guys!
My SM-G900F has its sensor stopped working last saturday...
It was working properly untill I installed a game from aptoide...
The accelerometer and the gyroscope do not transmit values when I use *#0*#
What could it be the problem? Is it a hardware or software problem?
Thanks for answers
Click to expand...
Click to collapse
Should be software problem, as you've said "It was working properly untill I installed a game from aptoide".
Did you try to uninstall that game and see if the problem persists?
vndnguyen said:
Should be software problem, as you've said "It was working properly untill I installed a game from aptoide".
Did you try to uninstall that game and see if the problem persists?
Click to expand...
Click to collapse
I've done a factory reset through recovery mode, but it didnt solve the problem!!!
paulocunhabr said:
I've done a factory reset through recovery mode, but it didnt solve the problem!!!
Click to expand...
Click to collapse
Reflash the stock rom you have with Odin and data factory reset afterwards, that should solve it. Some system files probably got messed up somehow.
Hi, i'm cross-posting this for visibility.
So, i'm completely lost. I was playing around with ROMs and mods (the RAM build.prop, for example), and now all my phone's sensors seem to be stuck.
I have reflashed back to completely stock ROM, taken official sprint update. Tried modded ROM, done factory resets, cleared/wiped everything, and still the issue persists.
It would appear my Gyroscope, Accelerometer, Proximity Sensor, and Compass are all not responding at all.
Right now i'm on rooted stock AOJ6.
Does anyone have any ideas? Maybe a corrupted sensor properties file or something similar like that? I'm completely at a loss.
Any help is appreciated.
Guys, it fixed itself. I booted into safe mode, restarted and all the sensors are working again.
I doubt it had anything to do with safe mode, as the sensors weren't working in safe mode.
I have no idea what could have done it. I wish I had a real answer for you.
Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Foxxo990 said:
Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Click to expand...
Click to collapse
Solved, download the firmware version you have here and look for persist.img. The firmware comes with it but the install script doesn't use it. Just flash it:
Code:
fastboot devices
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
Hello friend,i have similar problems,apart from fingerprint sensor,all my sensors and cameras,camera light are not working,will i loose imei numbers if i flash the persist img ? i dont know how to flash persist img,can you help me please?
Edit: hi i actually fixed my problem by flashing persist.img, all sensors and cameras are working now
Thank you so much
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
3sgebeams said:
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
Click to expand...
Click to collapse
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
DIXES said:
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
Click to expand...
Click to collapse
Depending on your OS version yes, contact me on Telegram @GuerrillaRadi0 (the last character is zero) maybe I can help you, after I fixed the problem I configured fingerprint security and the problem came back, so I tried to flash persist.img again and it didn't work, so I got the raw rom of the Oreo version I have; WW-15.0210.1810.73, which comes with its own ADB, and flashed from there, the same raw rom has the persist.img. After that all sensors worked again, so I configured fingerprint security again just to be sure, and again I lost all the sensors, but after deactivate fingerprint again everything worked fine, I guess I have some hardware issue related to fingerprint sensor, I guess it was because a technician opened the phone to replace screen and battery 2 months ago. I always used fingerprint so I need to go back to pattern.
Good luck
After some days without any issue the problem came back, I flashed persist.img twice and it worked, but about 3 days ago I can't solve this flashing persist.img, I tried wiping everything, downgrading to Nougat, then flashing Oreo, with TWRP and via flashtool, no solution, any other idea?? all sensors are not working.
Thanks in advance
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