I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
JimmyDeemo said:
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
Click to expand...
Click to collapse
If you want good rom for gaming and everything else, then try gaming hybrid 2.1.2
Amazing rom with 190 mb free RAM on startup
And there is no bugs.
JimmyDeemo said:
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
Click to expand...
Click to collapse
What kernel are you using?
When the screen goes black can you see the phone in if you run adb devices?
Jure220 said:
What kernel are you using?
When the screen goes black can you see the phone in if you run adb devices?
Click to expand...
Click to collapse
Hi Jure220, thanks for the reply. I'm using the 480p version of the one you recommended in the ROM thread here; http://forum.xda-developers.com/showthread.php?t=1804003.
I'm not able to try adb devices right now, but will do later. It's like the phone is still running but just the screen won't turn on. Sometimes I can get it to come alive with by opening the slider. When booting with the problem, I get one vibrate to show that the power has been pressed, then another for the kernal logo (used to indicate going into the recovery menu). It's very strange, I will get back to you on the adb devices but is there any other details I could get you?
Cheers for the help.
JimmyDeemo said:
Hi Jure220, thanks for the reply. I'm using the 480p version of the one you recommended in the ROM thread here; http://forum.xda-developers.com/showthread.php?t=1804003.
I'm not able to try adb devices right now, but will do later. It's like the phone is still running but just the screen won't turn on. Sometimes I can get it to come alive with by opening the slider. When booting with the problem, I get one vibrate to show that the power has been pressed, then another for the kernal logo (used to indicate going into the recovery menu). It's very strange, I will get back to you on the adb devices but is there any other details I could get you?
Cheers for the help.
Click to expand...
Click to collapse
If its posible run adb logcat when the screen still works and keep it connected until the black screen apears and post the log in a txt file. But it isnt necessary. But if you reflash the rom it shuld work fine. And if it dosent try the new update I just released
Jure220 said:
If its posible run adb logcat when the screen still works and keep it connected until the black screen apears and post the log in a txt file. But it isnt necessary. But if you reflash the rom it shuld work fine. And if it dosent try the new update I just released
Click to expand...
Click to collapse
Yes I did notice that you had posted v1.3, will give that a try. I was a bit confused as to why the ROM would affect the screen on boot, but this is me assuming that it is something to do with the ROM at all.
Out of interest, did I need to use any specific settings when formatting /system ready for the ROM? I did a full wipe and fresh Kernal install at the time so had to format it.
JimmyDeemo said:
Yes I did notice that you had posted v1.3, will give that a try. I was a bit confused as to why the ROM would affect the screen on boot, but this is me assuming that it is something to do with the ROM at all.
Out of interest, did I need to use any specific settings when formatting /system ready for the ROM? I did a full wipe and fresh Kernal install at the time so had to format it.
Click to expand...
Click to collapse
When you flash the rom /system will be formated automaticly, and I also doubt it is a rom issue I think something went wrong while flashing...
Jure220 said:
When you flash the rom /system will be formated automaticly, and I also doubt it is a rom issue I think something went wrong while flashing...
Click to expand...
Click to collapse
Hi Jure2020, so I just flashed the ROM again with v1.3, booted fine after flashing. Powered off and then black screen again. I think that it must be a Kernel issue, do you have any other recommendations for Kernels compatible with your ROM?
I tried adb devices btw, all I got was the follwing;
C:\Development\Android SDK\platform-tools>adb devices
List of devices attached
CB5A1E0AJ2 device
C:\Development\Android SDK\platform-tools>
JimmyDeemo said:
Hi Jure2020, so I just flashed the ROM again with v1.3, booted fine after flashing. Powered off and then black screen again. I think that it must be a Kernel issue, do you have any other recommendations for Kernels compatible with your ROM?
I tried adb devices btw, all I got was the follwing;
C:\Development\Android SDK\platform-tools>adb devices
List of devices attached
CB5A1E0AJ2 device
C:\Development\Android SDK\platform-tools>
Click to expand...
Click to collapse
Try to reflash the kernel or use lupus ics/gb one and if it still dosent work reflash the firmware, btw when it first happend did you drop the phone or something?
Jure220 said:
Try to reflash the kernel or use lupus ics/gb one and if it still dosent work reflash the firmware, btw when it first happend did you drop the phone or something?
Click to expand...
Click to collapse
Yeah I will try re-flashing a new kernel this evening. Will try this one; http://forum.xda-developers.com/showthread.php?t=2167766.
No honestly, just one time I noticed it didn't wake the screen. Then it got a bit more regular, now it's pretty much every time the phone is left idle for a while, the screen just won't come on. The phone is active, I can 'unlock' it by swiping; I get the haptic feedback and hear the unlock noise. The phone is running, just the screen is off. I even thought it could be a CPU clocking issue, so used SetCPU to force the minimum speed up for resumption and no luck their either.
I have been thinking that it could be a hardware issue, my phone is kinda old now, but the thing is once the phone is on, it's on. I've gamed on it for a good hour or two with no problems, then pressed power to sleep and immediately haven't been able to turn it back on again. It's just very strange, thanks for the help though.
Hi JimmyDeemo,
I think your problem is flex cable related. I've also experience this before. After I replaced the damaged flex cable, my phone just work fine....:victory:
Related
I am devastated as i cant find the source of this problem. i tried changing rom, kernel and it still happens everytime. Whenever i lock my screen it just shuts down n i need to boot up again. if i boot up for too many times, it keeps popping up error "android.acore is not responding" which is very very annoying... n i have to reflash everything!! It happens just starting from ytd...
Surprisingly when i nandroid back to old base the problems seems to be resolved... can someone please help? thanks...
stephen2282 said:
I am devastated as i cant find the source of this problem. i tried changing rom, kernel and it still happens everytime. Whenever i lock my screen it just shuts down n i need to boot up again. if i boot up for too many times, it keeps popping up error "android.acore is not responding" which is very very annoying... n i have to reflash everything!! It happens just starting from ytd...
Surprisingly when i nandroid back to old base the problems seems to be resolved... can someone please help? thanks...
Click to expand...
Click to collapse
Do you do a full wipe before reflashing? Perhaps try relocking the bootloader and flashing the RUU then start from scratch.
I had this exact issue the other day, the problem was coming from SetCpu. Dunno if you have it or maybe a similar program installed? I was trying to underclock it but it keept rebooting whenever I offed the screen.
dr9722 said:
Do you do a full wipe before reflashing? Perhaps try relocking the bootloader and flashing the RUU then start from scratch.
Click to expand...
Click to collapse
I always full wipe before flashing... I think its the governor settings n underclocking that cause the problems. Still experimenting.
Johnny0906 said:
I had this exact issue the other day, the problem was coming from SetCpu. Dunno if you have it or maybe a similar program installed? I was trying to underclock it but it keept rebooting whenever I offed the screen.
Click to expand...
Click to collapse
Come to think of it I used system tuner to tweak my CPU abit... Maybe the kernel now still doesnt. Support underclocking.. glad to hear someone's experience as I am so scared that my power button or hardware might have some problems..
I am experiencing the same problem that my screen doesn't come back to life at times after it gets locked and i need to reboot it... You guys got any solution or would it be a better idea to claim my warrany?
I can get into recover,download mode, or the rom boot screen but phone turns off right after. It won't stay on long enough to change roms or backup anything. Does anyone have any suggestions of what to do? Thanks in advance
Can't not can...stupid tablet won't let me edit.
Please Specify your Rom and Kernel. If on Stock, do a factory reset.
Perseus71 said:
Please Specify your Rom and Kernel. If on Stock, do a factory reset.
Click to expand...
Click to collapse
I'm on Cyanogenmod with stock Kernel from Cyanogenmod, never changed my kernel. It was working fine for months then just rebooted on its own and won't stay on since. Unfortunately I'm stock and I'm not even sure it will stay on long enough to do anything to it.Its also not the battery. This video shows exactly whats happening to mine. https://www.youtube.com/watch?v=J61jghxz-Vc
If it can stay stable in Download mode, then you can Odin Flash Root66. Once that's done, flash recovery again and the Rom.
Perseus71 said:
If it can stay stable in Download mode, then you can Odin Flash Root66. Once that's done, flash recovery again and the Rom.
Click to expand...
Click to collapse
That's the problem I can't. Is there any other options. I'm not worried about backups or anything I just want it fixed.
The video points to Recovery only. Have you tried to boot into Download mode (the kind that has yellow triangle and Downloading message ) ?
Perseus71 said:
The video points to Recovery only. Have you tried to boot into Download mode (the kind that has yellow triangle and Downloading message ) ?
Click to expand...
Click to collapse
Yeh I've tried recovery and download. Neither one stays on for more than 5 seconds and in download mode after clicking up to go into download mode the phone restarts.
Could be hardware, could be softbrick. Can you try the De-Bricking thread's instructions ?
Perseus71 said:
Could be hardware, could be softbrick. Can you try the De-Bricking thread's instructions ?
Click to expand...
Click to collapse
Trying to find it now. Can you point me in the right direction with a link??
Pivo99 said:
Trying to find it now. Can you point me in the right direction with a link??
Click to expand...
Click to collapse
Here you go.
Perseus71 said:
Here you go.
Click to expand...
Click to collapse
I'm beginning to think its a hardware problem. I got it to boot into recovery long enough to factory reset, load a new rom, and gapps. I rebooted and it loaded for a few seconds and turns off. It booted again and went to the optimizing apps screen then shut off before it could finish. Does this sound like it could be a software problem?
Pivo99 said:
I'm beginning to think its a hardware problem. I got it to boot into recovery long enough to factory reset, load a new rom, and gapps. I rebooted and it loaded for a few seconds and turns off. It booted again and went to the optimizing apps screen then shut off before it could finish. Does this sound like it could be a software problem?
Click to expand...
Click to collapse
I got the phone to boot into cyanogenmod but in the set up screen it failed again. Really getting annoying and I can't figure out how to fix it.
Pull battery. Then put it back. Does it try to turn on by itself? Could be the power button issue many others have had.
DocHoliday77 said:
Pull battery. Then put it back. Does it try to turn on by itself? Could be the power button issue many others have had.
Click to expand...
Click to collapse
YES thats it I was thinking there might be a problem with the power button...Is there a fix on this or a thread anywhere?
There have been many threads posted with this issue, and some did manage to just buy the part and fix themselves. No instructions though thst I'm aware of.
I'd suggest you google galaxy s3 or t999 teardown.
DocHoliday77 said:
There have been many threads posted with this issue, and some did manage to just buy the part and fix themselves. No instructions though thst I'm aware of.
I'd suggest you google galaxy s3 or t999 teardown.
Click to expand...
Click to collapse
Found a few posts and people just thump around the general area of the power button and that seems to be a temporary fix and it worked for me for a little while. It's gonna work long enough to revert everything to stock and send in. Thanks you two for your help
Hello folks,
this morning i wanted to check the watch on my phone and noticed it was very slow. As i am on a cm 11 nightly, i decided to reboot.
The phone shut down correctly but didnt come up afterwards, the screen stayed black. About 4 minutes later, the "HTC quietly brilliant" logo appears. About another 1-2 min. the cyanogenmod boot screen appears. I can repeat that behaviour every time. same with boot to recovery or fastboot. After booting up completely, the phone usage appears to be normal excep the display brightness sensor is not working automatically.
Please note that i am on the same nightly for about 10 days now without any issues except a few reboots. I didn't change anything in the last days, same setup, same usage.
I wiped the caches, installed newest nightly, nothing changed. i cant logcat during boot because adb devices says no device attached.
does anybody has any idea what i can do? i am afraid it seems to be some kind of hardware failure...?
regards,
In fastboot use
Fastboot erase cache
and also backup apps and messages and wipe everything expect battery stats and sd card I had that problem too
big noob said:
In fastboot use
Fastboot erase cache
and also backup apps and messages and wipe everything expect battery stats and sd card I had that problem too
Click to expand...
Click to collapse
Thanks for your answer. Unfortunately, as i anticipated, it did not work. I factory resetted the phone and erased all caches (not via fastboot but cwm, i guess it does the same).
I don't think it is a ROM problem as there are no issues when android is booting but at the, i will call it POST (the htc quietly brilliant logo )of the phone.
I think the proximity sensor/brightness sensor is defective and the phone recognizes it during the "POST" and runs in some kind of timeout and then starts booting.
Can somebody confirm a phone does have something like a hardware check before booting the OS?
Kind regards,
two_handed said:
Thanks for your answer. Unfortunately, as i anticipated, it did not work. I factory resetted the phone and erased all caches (not via fastboot but cwm, i guess it does the same).
I don't think it is a ROM problem as there are no issues when android is booting but at the, i will call it POST (the htc quietly brilliant logo )of the phone.
I think the proximity sensor/brightness sensor is defective and the phone recognizes it during the "POST" and runs in some kind of timeout and then starts booting.
Can somebody confirm a phone does have something like a hardware check before booting the OS?
Kind regards,
Click to expand...
Click to collapse
Are you tryed with diferent rom? I think it is not a problem if your prox sensor not working!!!
Thant said:
Are you tryed with diferent rom? I think it is not a problem if your prox sensor not working!!!
Click to expand...
Click to collapse
No, i did not try a different ROM. Why should i? it worked with CM11 before without any issues...
two_handed said:
No, i did not try a different ROM. Why should i? it worked with CM11 before without any issues...
Click to expand...
Click to collapse
Obviously, it is ROM's problem. Because it is nightly. Although I have installed nightly too, one from 23 feb. And I have no problems. By the way, snapshot built l built is released now and I'm gonna try it today.
Sent from my One X using xda app-developers app
Timofey_K said:
Obviously, it is ROM's problem. Because it is nightly. Although I have installed nightly too, one from 23 feb. And I have no problems. By the way, snapshot built l built is released now and I'm gonna try it today.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Still i really don't think it is a ROM problem. I just noticed that the phone even in fastboot behaves REALLY slow (changing the menu with volume buttons takes 1-2 minutes). And fastboot definately is independent from the ROM.
Anyways, i am just downloading CM 10.2 stable realease and flash it just to be sure.
Yep, as i thougth, still black screen for 4 minutes until the HTC quietly brilliant logo appears.
Guess it's faulty hardware then... Would be nice if someone could confirm my assumption that there is some kind of POST before the ROM is loaded.
regards
two_handed said:
Yep, as i thougth, still black screen for 4 minutes until the HTC quietly brilliant logo appears.
Guess it's faulty hardware then... Would be nice if someone could confirm my assumption that there is some kind of POST before the ROM is loaded.
regards
Click to expand...
Click to collapse
Try to flash sense rom like ARHD it is close to stock and see what will heppend then if it is the same it is hardware if not is problem it CM
I'll preface this by saying I have searched the forums here and after reading a few threads about similar problems to mine, I haven't been able to find a solution. So, I'm making a new thread in the hopes you fine individuals will be able to help me troubleshoot what's going on.
The problem:
I was running CM 12 on my T800 for a while, but after some bugs and random reboot issues, I decided to give the new IronRom a shot. I went ahead and flashed it through TWRP and everything went swimmingly. I was able to set up the tablet and use it for a while. However, two days ago when my wife was using the tablet, it randomly restarted while she was using it and then froze at the Samsung startup screen. It would show the screen, then blink to black like the tablet had restarted, show the screen and repeat this about 4 or 5 times before freezing at the Samsung start screen.
What I have tried doing:
First thing I tried was home+power+volume up to get into TWRP and do a wipe and start over. But I cannot get into recovery. Once the tablet is frozen the only way to get it to restart is with a hard reset power+volume down, nothing done after that seems to make any difference.
Second, I realized I could still get into download mode, so using ODIN I tried going back to stock. Flashed the stock rom for my region but when Odin is done with the initial flash, it reboots the tablet and everything is the same. Frozen at the Samsung screen.
I've tried flash TWRP again, but once the tablet reboots after download mode, it just freezes at the Samsung screen.
Any suggestions at this point would be welcome.
last time i had this same trouble but on my T705. I had to wipe everything including the internal storage. only then the device boot properly.
edan1979 said:
last time i had this same trouble but on my T705. I had to wipe everything including the internal storage. only then the device boot properly.
Click to expand...
Click to collapse
I would love to be able to, but as I said in the original post, I can't get the tablet to enter recovery, so I can't wipe it. The only thing I can get it to do is boot into download mode.
Hi, sorry to be that guy who bumps threads, but I'm still sitting here with a tablet I can't use and no more ideas on what I can do to fix it. I'd really appreciate any ideas at this point. Thanks again!
Drschplatt said:
Hi, sorry to be that guy who bumps threads, but I'm still sitting here with a tablet I can't use and no more ideas on what I can do to fix it. I'd really appreciate any ideas at this point. Thanks again!
Click to expand...
Click to collapse
I had similar experience, and even started downloading official samsung image, with odin etc. However it looks like I was able to enter recovery if rebooting using the following sequence:
- power-vol_down-home combination until the screen goes black
- moving finger from volume-down to volume-up
-> waiting a few seconds (less than 10) until recovery screen shows up.
Then I just reinstalled the good old cm 12.1 (instead of the failing lineageos 14.1), and then all happy again.
Drschplatt said:
Hi, sorry to be that guy who bumps threads, but I'm still sitting here with a tablet I can't use and no more ideas on what I can do to fix it. I'd really appreciate any ideas at this point. Thanks again!
Click to expand...
Click to collapse
Hallo.
Try this https://forum.xda-developers.com/ga...k-disaster-t2838473/post54618555#post54618555.
It work for me, when i have similar problem.
Carlosk1966 said:
Hallo.
Try this https://forum.xda-developers.com/ga...k-disaster-t2838473/post54618555#post54618555.
It work for me, when i have similar problem.
Click to expand...
Click to collapse
Thanks for the link. I tried it but never could get the tablet turned off to see the battery icon. When I used the method in the link it just returned to the Samsung Galaxy Tab S startup screen
Drschplatt said:
Thanks for the link. I tried it but never could get the tablet turned off to see the battery icon. When I used the method in the link it just returned to the Samsung Galaxy Tab S startup screen
Click to expand...
Click to collapse
Well that is not good. Like i said, it allways work for me, when i get bootloop.
Hi All,
Opening a new thread bcz I didn't find any solution anywhere for this particular problem , if available pls redirect me.
So I am facing strange issue with my OnePlus 3. One day suddenly my phone slowed down and then followed by black screen. I was using havoc os based on pie back then.
I rebooted and phone worked for 2-3 mins and again I faced the same issue..so I thought it might be something with the rom.
I switched to stock rom and even locked the bootloader , still faced the same issue. My phone works fine in recovery and bootloader mode and I don't face black screen there.
Now I installed pixel experience rom Android 10 and facing the same issue it works for 2-3 minute and then I get the black screen followed by white led..also my phone works very slow during that 2-3 minute time.
I don't think it's a hardware issue as I am not having problem in recovery or fastboot mode, correct me if I am wrong.
If anyone knows the solution please reply to this thread..will appreciate.
Thanks ?
saurs94 said:
Hi All,
Opening a new thread bcz I didn't find any solution anywhere for this particular problem , if available pls redirect me.
So I am facing strange issue with my OnePlus 3. One day suddenly my phone slowed down and then followed by black screen. I was using havoc os based on pie back then.
I rebooted and phone worked for 2-3 mins and again I faced the same issue..so I thought it might be something with the rom.
I switched to stock rom and even locked the bootloader , still faced the same issue. My phone works fine in recovery and bootloader mode and I don't face black screen there.
Now I installed pixel experience rom Android 10 and facing the same issue it works for 2-3 minute and then I get the black screen followed by white led..also my phone works very slow during that 2-3 minute time.
I don't think it's a hardware issue as I am not having problem in recovery or fastboot mode, correct me if I am wrong.
If anyone knows the solution please reply to this thread..will appreciate.
Thanks
Click to expand...
Click to collapse
Hallo saurs94
I had the same problem.
the following helped me:
boot in recovery
System deleted
flash oxygenos-9.0.6-firmware-3.zip
flash lineageos-17.1-xxx (I had the firmware and the current nightly saved on sd-card)
reboot to system
I hope I could help you
wollez said:
Hallo saurs94
I had the same problem.
the following helped me:
boot in recovery
System deleted
flash oxygenos-9.0.6-firmware-3.zip
flash lineageos-17.1-xxx (I had the firmware and the current nightly saved on sd-card)
reboot to system
I hope I could help you
Click to expand...
Click to collapse
Thanks for the reply, by delete u mean wipe right?
i am wiping the system, cache, dalvik and data and installing..lets see
hope it works
saurs94 said:
Thanks for the reply, by delete u mean wipe right?
i am wiping the system, cache, dalvik and data and installing..lets see
hope it works
Click to expand...
Click to collapse
Sorry to say but it's still not working..while performing the lineage os setup, it became unresponsive (at wifi selection) and then black screen followed by white led.
i'm frustrated by this
Does anyone gonna help me?
saurs94 said:
Does anyone gonna help me?
Click to expand...
Click to collapse
Execute an EDL flash to completely restore your device to regular state https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
Will try..thanks?
This is same as found in Nexus 5x, Nexus 6P especially
Problem of high performance core in cpu section
A customized boot image
&
Kernel
Both at a time or boot.image will most probably fix it.
Currently facing same issue with op3 running LOS 10
pixelized screen then freeze. On force or hard re-start(no reset) stuck of 1+ logo.
Then white LED Light (indicator or notification light)
Im trying LOS's low performance mode in
Settings> Battery > Battery Savor & Performance> Battery profile.
Hope so it will fix this issue.
Otherwise I'll try any kernel with "Under clocking cpu & gpu profiles"
Share your experience thanks.
PierreVicquery02 said:
Execute an EDL flash to completely restore your device to regular state https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
Click to expand...
Click to collapse
I tried the hard brick method but it's still not working, phone got booted into system and while setup again it got stuck and restarted followed by a white led, restarted the phone and it's same.
Guess it's hardware issue :crying:
AlahmadPR said:
This is same as found in Nexus 5x, Nexus 6P especially
Problem of high performance core in cpu section
A customized boot image
&
Kernel
Both at a time or boot.image will most probably fix it.
Currently facing same issue with op3 running LOS 10
pixelized screen then freeze. On force or hard re-start(no reset) stuck of 1+ logo.
Then white LED Light (indicator or notification light)
Im trying LOS's low performance mode in
Settings> Battery > Battery Savor & Performance> Battery profile.
Hope so it will fix this issue.
Otherwise I'll try any kernel with "Under clocking cpu & gpu profiles"
Share your experience thanks.
Click to expand...
Click to collapse
Thing is i cant go to setting and do the steps..if any kernel in particular works for you , please share with me.
Thanks