Hey guys,
I don't know whether you're able to help me.
I was a happy user of a Mi4, 16GB with latest CM13 nightlies installed and TWRP latest version working fine, too. After one of the latest updates of a CM13 nightly, my phone went into keylock and from there did not quite awake. It is in a strange state: The phone is working in principal, for example did I shoot some photos (by double clicking the on/off-button) which from there went up to my Google Photos account. Problem was: The screen stayed black, only the backlight did work. I tried to set up the phone newly, but couldn't manage to get into TWRP. Then I tried to start from scratch by installing a MIUI fastboot rom, still the phone did not awake. Now I followed this instruction:
http://en.miui.com/forum.php?mod=viewthread&tid=226426
Everything which is described under "Part 1" worked like a charm. Now the phone is hanging on the charger, the led is constantly yellow and the backlight is on, sometimes the vibration is going. I tried to boot into fastboot which is actually working (it appears on entering "fastboot devices" in windows cmd), but the screen doesn't show that fastboot image, still backlight is on.
As the phenomenon of working backlight with a dead screen seems to appear in CM13, in fastboot and with Fastboot Rom installed, what could be the reason for this!? Is the phone broken you think?
Related
Situation is kinda strange.
Yesterday i was bored and i started to flash some roms on my OPO. I started with the latest ColorOS that i found here on XDA, but i didn't like it. So i flashed PA 4.6 beta 6. I noticed that the red boot logo of colorOS remained despite the full wipe of the internal storage. And the fastboot mode started to show some chinese characters instead of the regular ones.
But that's not the problem. Problem is that this morning i wasn't able to turn off a call because the screen turns off every time a call is made and there's no chance to turn it again on. The only thing i could do is to long press the power button and reset the phone. The call starts, the speaker works, the screen turns on and you can't do nothing than this.
I said "ok, it could be the PA rom, it's in beta, y'know"...So i flashed the PA stable and...same problem.
Then i tried the first rom i saw (vanir lollipop, last build) and...same problem? WTF?
Now i'm flashing the original 44s by fastboot and see what happens. In case nothing happens with the fastboot way, i will try to flash it by recovery. But i have a bad feeling about this.
Any similar experiences? I will keep the thread updated for people with the same problem.
EDIT 1: ok, after the fastboot flash of the cm11 44s i'm able to make calls without those problems. It will be amazing if the problem were still there.
EDIT 2: i have to say that the chinese fastboot and the red logo are gone now.
The reason your proximity sensor stopped working was because of the modem you flashed while you flashed ColorOS.
I flashed ColorOS aswell and has the same proximity sensor issue after flashing back a CM11 rom.
mumaster20 said:
The reason your proximity sensor stopped working was because of the modem you flashed while you flashed ColorOS.
I flashed ColorOS aswell and has the same proximity sensor issue after flashing back a CM11 rom.
Click to expand...
Click to collapse
Damn! I knew it!
That terrible ROM messed up all my phone -_-
Hello guys,
some days ago my phone was permantly booting up in the recovery mode nothing else was possible. As I was on road and couldn't access internet anywhere I just tried to do some wipes, which then made my phone not show anything. I guess the reason that it didn't boot up anymore was that the battery was fully drained. When I was finally back home I was able to charge my phone but then the following happend:
I can start my OPO, see the android logo and then it turns black, but it fully boots up. I mean I can even click the touchscreen and hear some touch reactions/sounds. Also I'm able to turn up/down the volume and hear my phone. Furthermore I'm also able to do the "V-gesture" to turn on the flashlight. When I boot up into fastboot mode I also see the message "fastboot mode" + the little cyanogen face.
All in all everything seems to work, aside that I dont see anything else than dark after the logo.
I tried flashing new roms, stock reset, like seriously anything, but I can't get my phone to work probably again.
Does that mean that my phone got some hardware problems, maybe the touchscreen?
Help is appreciated, thanks in advance!
btw: English isn't my first language, so please excuse any mistakes.
You'll have to try flashing completely stock CM11 rom or CM12 rom, img by img in fastboot..modem, boot, system etc. I helped a friend who had this kind of problem. Probably not the cleanest way, but at least it works.
Already did that 3times using different methods. Stock CM11, CM12 and colorOS
I have a similar problem, did you manage to fix it? And if so, how?
Thanks,
Capelare.
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?
Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.
I was using havoc os with the last beetle kernel, but one day my phone suddendly stopped working. When I try to boot it up, the screen stays black and it vibrates once in a while. Once it stops vibrating i can connect it to my computer and see internal storage, i have access to adb commands but never managed to go fastboot mode. I'm prettry sure this is not hardware problem because absolutely nothing happened before it stopped working. It was just standing in my pocket. Can somebody help?
oh, i managed to access fastboot, can somebody help?
i managed to flash miui rom, now the phone is making sound, but the screen is still not showing anything