Hello all,
My apologies if this is a common issue. I have searched but the only old thread about it is the following:
http://forum.xda-developers.com/showthread.php?t=2190960
and no real answer was suggested there, which is why I am asking it again.
So the issue is the same as in that previous thread: quite often, when I longpress the power button, the menu (to shut down, put it on vibrate mode, ...) does not pop up. The only way to get it back is to hold the power button until the phone shuts down, and then reboot the phone, after which it works again (for god knows how long).
I was rooted (with stock rom) before 4.3, but lost my root when updating to 4.3, so I was on stock ROM without root when the problem first appeared. Now yesterday I rooted again and flashed paranoid android ROM (first factory reset, clearing cache and dalvik cache), but the problem remains.
In that old thread one member solved the problem by flashing the stock kernel, however I have never flashed another kernel so I doubt the kernel is the problem?
If anybody knows the issue and a way to solve it, please let me know, it would be greatly appreciated.
Thanks,
Maarten
You did flash a kernel when you flashed the rom
Wayne Tech Nexus
Hey there
No, as in the first post, I have never flashed another kernel on the nexus. Neither did I flash a new radio.
I had not flashed anything yet when the problem started, I only unlocked the bootloader and rooted my phone when I first got it (but it worked a long time without any problems)
Delete this post
Nobody had this issue ?
Found a solution at last!!
wolfway said:
Nobody had this issue ?
Click to expand...
Click to collapse
After quite a long search and a lot of worries, I finally found THE solution...
https://www.youtube.com/watch?v=d8dbrerUacw
how to get out of factory mode for a s4 but it worked on my N7105
- efs/factoryApp/factorymode/ouvrir avec/editeur de texte/ON
- efs/factoryApp/keystr/ouvrir avec/editeur de texte/ON
I have this issue too. I'm using paranoid Android beta 4 with franco kernel and since The moment o rooted my phone this issue started
Sent from my Nexus 4 using XDA Free mobile app
Related
Dear all,
I bought my wife a Galaxy y from t-mobile. I noticed when I locked the device via the button on the right and put the device in standby, I cannot wake up the phone by pressing the home button and get the screen to unlock the device by wiping. Only when I press the home button fot long time and sometimes twice for a long time, I manage to get the unlock screen. Very annoying. And when I do this, the sd card has to be remounted every time. Does anyone have had similar issues? Phone is on GB2.3.5 with LA2 rom if i'm correct. LH2 is the new release.
There's a software update available via Kies, but is not installed yet. Could it solve the issue? I hope someone can help. Thanks
Update the device, maybe the problem is due to update............
Did you check your lockscreen settings? Check there, you may put long press option there. Btw are you on stock rom or custom rom?
Sent from my GT-S5360 using xda premium
You've got quite a strange problem man! Maybe some glitch with your framework-res.apk. Do a full wipe (data & cache), and see if it resolves the problem. If it dosen't then flash the latest stock firmware.
Thanks for all responses. I was on Kernel LC1 and now after the update on LH1. But more important is that the issue is solved. Now home button works fine and no strange messages about memory card anymore. So I'm happy now...or better my wife
I am experiencing sudden shutdowns (or atleast non-responsive screen) quite often while on 4.2.2. For example, last night, the phone was at 89%. I went to sleep. When I woke up, the phone did not respond to the power button. I am not sure how long I pressed the power button (so I am not sure if I did a reboot or a boot) but the phone did not go to the lock screen, a (re)boot was required. I've had this since the day I had it (came on 4.2.1, currently running 4.2.2 stock).
When I did boot my phone back up, my battery was as indictaed in the screenshot. It was suddenly at 34%! I have no idea what causes this, but would much like to resolve this issue. I'd love to try a different kernel, but on the franco kernel (r82) I was unable to receive notifications (and thus missed alot of Whatsapp messages) unless I would actively turn on my phone with the power button.
I did google this problem but found no solution for me.
If you're using custom kernel, then post this kind of issues on kernel thread. If not then clean phone and stock reflash it.
Some mods (like the awesomeBEATS) breaks 4.2.2 so keep that in mind.
Adam
AdamLange said:
If you're using custom kernel, then post this kind of issues on kernel thread. If not then clean phone and stock reflash it.
Some mods (like the awesomeBEATS) breaks 4.2.2 so keep that in mind.
Adam
Click to expand...
Click to collapse
I have reflashed the custom ROM and kernel. So that can't be the issue.
I just posted this thread:
http://forum.xda-developers.com/showthread.php?t=2153860
Did you get a flashing white led?
As I was very sleepy when I woke up, I'm not sure, but there could have been one, yes!
Anyone ever experienced this? Is this RMA-worthy?
Edit: Just happened again, while I was whatsapping. I turn it on standby, want to turn it on 5 minutes later and I have to reboot it...
I have this problem since 4.2.2 on the nexus 5
I rooted my S4, flashed to a rom, now switched back to stock, wich i updated now.
However since i updated rooting doesn't seem to work anymore,
and whenever i press my wifi button it goes on but immediatly goes off giving me a "Prevention information".
My question now is can i fix my WiFi?
(factory reset did not work)
Pixelhouse said:
I rooted my S4, flashed to a rom, now switched back to stock, wich i updated now.
However since i updated rooting doesn't seem to work anymore,
and whenever i press my wifi button it goes on but immediatly goes off giving me a "Prevention information".
My question now is can i fix my WiFi?
(factory reset did not work)
Click to expand...
Click to collapse
if you flash back a stock ROM u wont have root anymore
Hi newer updates have a security fix that prevents rooting. The fix is in the kernel. Please see this thread to root and fix any warning messages.
http://forum.xda-developers.com/showthread.php?p=40819876
Sent from my GT-I9505 using xda premium
Yeah i figured i lost my root, tried using motochopper but didn't work anymore.
Can i fix my wifi somehow?
Do you have the 9505 version? If so use method in my first post.
Sent from my GT-I9505 using xda premium
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 all,
I've recently upgraded from a Samsung Galaxy S3 (i9300) to a Samsung Galaxy S5 (SM-G900F). Phone seemed to be working as desired so decided to go ahead, root, and install a custom ROM for enhanced functionality and customisation. Root process went smoothly, just running a simple CF-AutoRoot with Odin3 (voids KNOX, but no other problems), then installing PhilZ Advanced CWM Recovery.
From there I decided to install an unofficial build of CyanogenMod 11; found information on this forum. Flashing worked perfectly (and took rather little time!), but upon installation I noticed a strange problem. If I hard reboot (power off, power on) the device, with Wifi & Mobile Data off, the time and date are reset to incorrect values. Usually 01/01/xxxx and the time around 00:00. Same problem occurs even if when I turned off Network-allocated time and tried and set time manually.
The same problem occurred with other similar CyanogenMod based builds such as [AICP] and [AOSB]. I decided to restore back to the stock ROM and noticed that the clock and date were set correctly on reboot (and also on custom versions of 4.4.2 such as SpeedROMv7).
I checked with the terminal the value of the 'hwclock' (from BusyBox) and it reported an odd date somewhere in 1970, but different to the ones in found on CyanogenMod etc.
Does anyone have any idea what could cause this kind of problem and how to fix such an issue? If anyone wants any additional information about my device, please don't hesitate on commenting in this post. Would be grateful for any feedback. Thanks! :good:
PS: Also seem to be experiencing a problem with WiFi randomly disconnecting after a period of time. Not seen many threads with this said explicitly however. Problem with no voice in phone calls with headphones still persists but I've acknowledged that this is a known bug at the moment.
A.
Bump
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Anyone?
AlfieJPalmer said:
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Click to expand...
Click to collapse
Same Issue.
I have been encountering this very same problem for a while now, in fact, I am expriencing the same issue with my Galaxy S4 (i9505). So this must really be an issue of the CM code I guess.
Any ideas on how to solve this would be welcome since it is a really annoying issue
remove me