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
Related
I have a problem with my Htc Wildfire S. It charges very slowly, its slow to start up (about 20 mins, sometimes doesn't start and vibrates 10 times) and the touch wont work. I don't know if this means something but when its started up it have like a red light next the the htc text on the screen.
Please help if u can. Sorry for my bad English.
random_word said:
I have a problem with my Htc Wildfire S. It charges very slowly, its slow to start up (about 20 mins, sometimes doesn't start and vibrates 10 times) and the touch wont work. I don't know if this means something but when its started up it have like a red light next the the htc text on the screen.
Please help if u can. Sorry for my bad English.
Click to expand...
Click to collapse
That is strange, is the bootloader unlocked and have you installed any custom roms on it? The more ifno you cabn give about the phone and its present condition the better
robt77 said:
That is strange, is the bootloader unlocked and have you installed any custom roms on it? The more ifno you cabn give about the phone and its present condition the better
Click to expand...
Click to collapse
yes it's unlocked and i've installed cm9. Phone was working well and suddenly it happened. Phone didn't turn on. After that i've installed stock rom (that was really really hard) and now it starts up. (about 20 mins)
random_word said:
yes it's unlocked and i've installed cm9. Phone was working well and suddenly it happened. Phone didn't turn on. After that i've installed stock rom (that was really really hard) and now it starts up. (about 20 mins)
Click to expand...
Click to collapse
Do you still have the custom recovery installed? If so the best bet would be to do a wipe data from the revcovery and re isntall CM9 personally i would isntall CM10 and see how you get on. Have added different Roms to phones and sometimes a fresh install will sort out most problems.
No even soft bricked....
But why so slow boot no idea. It's very weird 20 mins boot!
Sent from my HTC Wildfire S A510e using Xparent SkyBlue Tapatalk 2
20 minutes for a boot ?
Did you install anything prior to this ?
Did you modify anything prior to this ?
All I can think of is a system file being misplaced ...
Bazinga
Can u boot into recovery, or do u have a nandroid backup... check that u format system as well as data.
robt77 said:
Do you still have the custom recovery installed? If so the best bet would be to do a wipe data from the revcovery and re isntall CM9 personally i would isntall CM10 and see how you get on. Have added different Roms to phones and sometimes a fresh install will sort out most problems.
Click to expand...
Click to collapse
No, stock rom installed. Yes i formatted as well as data. Phone isn't charging (actually it's charging but very very slowly) and touch screen isn't work. Can't install cwm after stock rom. (bootloader is unlocked.)
any help?
Try wipeing the delvic cache.. maybe itll help.
I think it's the hardware problem.
Sent from my HTC Wildfire S A510e using Tapatalk 2
Hi and firstly. thanks for your help!!
A friend gave me his hox for a repair after he tried putting in a new rom the wrong way...
so ive managed to put the rom he wanted (revolution hd 22) and the phone is now working ok...
calls, data, heavy apps... all works fine.
UNLESS- and thats the awkward part- unless you plug the usb data\charging cable out.
once the usb is out- the phone freezes for 30 seconds> reboots >than works fine for 30 seconds and than freezes whole over again
-this can happen until battery dies.
ive tried putting a new RUU
ive tried different kernels
ive tried wiping anything with fastboot or from the recovery
also tried TWRP and CWM- altough it dosnt even seems to be related
ive tried locking, unlocking, clearing fastboots cache... and NOTHING...
Now, the most weird thing, is when the phone is in recovery mode- it works on battery just fine!!
it can install my roms and kernels ok!
problem only occours when system goes up- than it will work only if its connected.
because of that- i can tell this isnt a hardware problem, and there must be a solution
does anyone has a clue with my issue please?
pazush said:
Hi and firstly. thanks for your help!!
A friend gave me his hox for a repair after he tried putting in a new rom the wrong way...
so ive managed to put the rom he wanted (revolution hd 22) and the phone is now working ok...
calls, data, heavy apps... all works fine.
UNLESS- and thats the awkward part- unless you plug the usb data\charging cable out.
once the usb is out- the phone freezes for 30 seconds> reboots >than works fine for 30 seconds and than freezes whole over again
-this can happen until battery dies.
ive tried putting a new RUU
ive tried different kernels
ive tried wiping anything with fastboot or from the recovery
also tried TWRP and CWM- altough it dosnt even seems to be related
ive tried locking, unlocking, clearing fastboots cache... and NOTHING...
Now, the most weird thing, is when the phone is in recovery mode- it works on battery just fine!!
it can install my roms and kernels ok!
problem only occours when system goes up- than it will work only if its connected.
because of that- i can tell this isnt a hardware problem, and there must be a solution
does anyone has a clue with my issue please?
Click to expand...
Click to collapse
try a custom kernel...if that doesn't wprk just go into a store or so and ask there what could the issue...if it wasn't there when he had the stock rom on it than he had a really bad flash and it is maybe rom or mainboard problem in some way
Sounds like a power issue. I think its hardware
Yep its maybe HW problem but why he can charge then in Recovery Mode
Solution:Your friend could charge in Recovery Mode and then boot up to the Rom
or you could try another ROM (your last hope ?)
Hey, thanks for helping,
There is no problem with charging it...
Problem is it cant work on battery
Only recovery works with bat power.
When using rom on bat- it freezes.
Edit: oh and one more thing, the phone is almost brand new, it has been used for only one week and worked ok. Until my friend took it to a store here for adding other lang...
Sent from my GT-I9300 using xda app-developers app
Recovery mode is taking less battery power then if you are using it with a rom booted up... Maybe the battery is now broken or the connectors are bad or so...
And what do you mean with adding other lang?
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
Recovery mode is taking less battery power then if you are using it with a rom booted up... Maybe the battery is now broken or the connectors are bad or so...
And what do you mean with adding other lang?
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
i thought about it, but i think installing a new rom via recovery is taking more power
than just staring at the regular booted screen while its on idle
30 seconds of staring- freeze and than reboot...
i just cant figure how its a hardware issue, the device is almost new... how is it possible that im the first one meeting this issue?
and i ment my friend wanted to add another os language that didnt come stock (rom change)
pazush said:
i thought about it, but i think installing a new rom via recovery is taking more power
than just staring at the regular booted screen while its on idle
30 seconds of staring- freeze and than reboot...
i just cant figure how its a hardware issue, the device is almost new... how is it possible that im the first one meeting this issue?
and i ment my friend wanted to add another os language that didnt come stock (rom change)
Click to expand...
Click to collapse
try a complete full wipe ...wipe system, data, dalvik-cache and cache...and before maybe try factory reset from bootloader and be sure to save all content from sdcard to pc ...if that doesn't help try the complete full wipe ...if that doesn't help it's an hardware issue and he maybe pulled the caable wrong out or so or i really don't know...
One-X-master said:
try a complete full wipe ...wipe system, data, dalvik-cache and cache...and before maybe try factory reset from bootloader and be sure to save all content from sdcard to pc ...if that doesn't help try the complete full wipe ...if that doesn't help it's an hardware issue and he maybe pulled the caable wrong out or so or i really don't know...
Click to expand...
Click to collapse
hey, ive done that already.
whats the deepest way to rewrite the onex's software?
i tried ruu, is there anything other i dont know?
pazush said:
hey, ive done that already.
whats the deepest way to rewrite the onex's software?
i tried ruu, is there anything other i dont know?
Click to expand...
Click to collapse
Go into a store or ask and say you have this problem or your friend have to go and if he ask if you unlocked say yes but this problem was even on stock therefore you flashed a custom Rom because you thought it will fix it...
Gesendet von meinem HTC One X mit Tapatalk 2
Thank you for trying to help again,
But it isnt resonable to determine the phone mainboard is dead, all signs shows its software...
If it helps, the hox makes a long beep, or drawing stripes on the screen sometimes before it restarts, the other times it just freezes.
Sent from my GT-I9300 using xda app-developers app
pazush said:
Thank you for trying to help again,
But it isnt resonable to determine the phone mainboard is dead, all signs shows its software...
If it helps, the hox makes a long beep, or drawing stripes on the screen sometimes before it restarts, the other times it just freezes.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Flash completely another Rom...and also other kernel...some ppl had those issues too but it was problem with mainboard maybe its the mainboard problem...
Gesendet von meinem HTC One X mit Tapatalk 2
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:
Hi Guys,
I just got my replacement M8 from AT&T yesterday. After obtaining root, S-OFF, and flashing a ROM the phone boots up, goes to the HTC lockscreen for about 4-5 seconds, freezes immediately (ie does not respond to touch) and then proceeds to reboot. This has been going on for the last 24 hours.
Im currently running ViperOne 1.50 with TWRP 2.7.0.4, but I've tried flashing Philz and a few other roms just to see if it is a common occurance and it is.
I'm thinking that I may have to bring it back to the carrier to see if I am able to exchange it. Hopefully I will be, but in the meantime any assistance or insight you guys can provide would be awesome.
I forgot to mention that I had an old Philz backup from my previous M8 stored to my MicroSD, which I have attempted to restore, with the same results.
Im currently attempting to check the integrity of the internal storage via "check SmartSD" option in bootloader mode. Hopefully I can figure out exactly what is going on.
noaone said:
Hi Guys,
I just got my replacement M8 from AT&T yesterday. After obtaining root, S-OFF, and flashing a ROM the phone boots up, goes to the HTC lockscreen for about 4-5 seconds, freezes immediately (ie does not respond to touch) and then proceeds to reboot. This has been going on for the last 24 hours.
Im currently running ViperOne 1.50 with TWRP 2.7.0.4, but I've tried flashing Philz and a few other roms just to see if it is a common occurance and it is.
I'm thinking that I may have to bring it back to the carrier to see if I am able to exchange it. Hopefully I will be, but in the meantime any assistance or insight you guys can provide would be awesome.
Click to expand...
Click to collapse
go to fastboot mode and type fastboot erase cache
reboot
make a factory reset from ur recovery. (not necessary)
hope it helps
mr.dj26 said:
go to fastboot mode and type fastboot erase cache
reboot
make a factory reset from ur recovery. (not necessary)
hope it helps
Click to expand...
Click to collapse
Thanks for the response. Already ran the fast boot erase cache command. Seemed to help in at least prolonging the rebooting. But it starts again nonetheless. It's strange; it only seems to start after I've connected to my SSID. It reboots into setup mode repeatedly without saving data.
noaone said:
Hi Guys,
I just got my replacement M8 from AT&T yesterday. After obtaining root, S-OFF, and flashing a ROM the phone boots up, goes to the HTC lockscreen for about 4-5 seconds, freezes immediately (ie does not respond to touch) and then proceeds to reboot. This has been going on for the last 24 hours.
Im currently running ViperOne 1.50 with TWRP 2.7.0.4, but I've tried flashing Philz and a few other roms just to see if it is a common occurance and it is.
I'm thinking that I may have to bring it back to the carrier to see if I am able to exchange it. Hopefully I will be, but in the meantime any assistance or insight you guys can provide would be awesome.
Click to expand...
Click to collapse
Get official 2.7.0.2 from their site. Reflash recovery.
Fastboot flash recovery twrp.img
Fastboot erase cache
Go to recovery, wipe dalvik, cache, system
Reflash Rom.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Did you install any kernels or try undervolting at all? I agree it shouldn't be rebooting as it is doing. Other thought is to do a full wipe data reset.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Phoneguy589 said:
Did you install any kernels or try undervolting at all? I agree it shouldn't be rebooting as it is doing. Other thought is to do a full wipe data reset.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was running Elemental 0.9 when I backed up Viper on my previous device, but I was not underclocking......I remember I had an issue siimilar to this in the past due to selecting the AT&T variant when actually flashing the rom as opposed to selecting the International variant, installing the rom, and then selecting AT&T at the setup screen.
I appreciate everyone's help. Ive tried most of these methods, but Im sure I probably missed a step along the way.
I am going to try to do this all over again....hopefully I can discern what the problem is.
an0ther said:
Get official 2.7.0.2 from their site. Reflash recovery.
Fastboot flash recovery twrp.img
Fastboot erase cache
Go to recovery, wipe dalvik, cache, system
Reflash Rom.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so i've gone through these steps pretty religiously 3 times, and each time seems to be elongating the time between boot, setup, and eventual reboot. the last time I thought I licked it, but sure enough it started the rebooting again and even went into a period of rapid bootlooping. (!?)
This is really weird. I think its a problem with the actual network adapter. Everytime I start to enter my wifi settings (specifically entering my proxy/static IP) it freezes and reboots.
Im just going to take this thing back to the store tomorrow. I love this phone and Im sure this is a fluke.
Again, thanks for your help, bros.
CJerk
i am out of ideas
So my HTC one m8 shuts off if i dont have it plugged into the Charger it only stands a ChanCe if the power saver is on but even then if i open a video from the gallery or youtube or fb it shuts off and if i play musiC to loud through the speakers it shuts off sometime it works fine an sometimes it doesnt but now i have it plugged in all the time and even when its plugged in sometimes it shuts off. It wont turn on unless its plugged in it jus goes to the HTC sCreen an shuts off but onCe plugged in it turns on. i have no idea what is goin on i think its the battery i think a new battery wud help i tried deleting apps even a faCtory reset but it didnt help so i seriously think its the battery if anyone wud help that wud be awesome.
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