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 -_-
Related
Hello folks, first post, hope you can help.
My phone has a very specific problem that happens with every rom BUT with AOKP.
When the phone is on idle it just gets stuck, black screen, button lights are on. Only thing to do is pull the battery out. It also happened with the stock rom, so I tried to unroot it and give it to sprint but they couldn't take it because of a small crack on the screen(been there forever).
I came back home and tried to flash it with a custom rom again, and recovery was broken, so I flashed recovery on the device 3 times before it started working again.
I randomly chose AOKP and it was working pretty well, although it slowed down lately a lot. I tried to install JB on it recently and the problem returned, so I tried CM9 again, CM10 even tried Bugless Beast, same thing. I keep going back to the backup I have of AOKP and it's the only one that doesn't crash my phone.
I've attached the phone information so you guys can see exactly which built I'm running.
Bump.
Please help me fix my phone, I'm really at loss how to solve this problem,
Do you turn deep idle on? If so that could be the problem......when u flash a new rom, as your setting everything up, make sure deep idle is turned off.....the option is under advanced in the cm roms .......hope that helps
10....0011....10101
Hi guys,
So yesterday I updating my HTC One to CM10.1.3 Stable release from some older 10.1.1 nightly, using the OTA updater, it flashed fine, then I put it into fast boot in order to manually flash boot.img uing adb. That worked, it booted no issues.
A couple of hours later, the phone just turned off, it was sitting in my desk, I saw the screen flash, it then rebooted, and bootlooped on the CM start up screen. I thought okay maybe the boot.img didn't flash right, so flashed again (note the boot.img used was extracted from the update zip file, so I am assuming is the correct one)
After flashing the boot.img again, starts up fine.
Then again at like 3am, the bright startup screen woke me up, and it was bootlooping again while on charge. I have no idea what's going on, it works fine besides that, I'm posting from my phone as well.
Anyone else having this issue? Or any way to solve it?
Thanks,
Aaron
arono7342 said:
Hi guys,
So yesterday I updating my HTC One to CM10.1.3 Stable release from some older 10.1.1 nightly, using the OTA updater, it flashed fine, then I put it into fast boot in order to manually flash boot.img uing adb. That worked, it booted no issues.
A couple of hours later, the phone just turned off, it was sitting in my desk, I saw the screen flash, it then rebooted, and bootlooped on the CM start up screen. I thought okay maybe the boot.img didn't flash right, so flashed again (note the boot.img used was extracted from the update zip file, so I am assuming is the correct one)
After flashing the boot.img again, starts up fine.
Then again at like 3am, the bright startup screen woke me up, and it was bootlooping again while on charge. I have no idea what's going on, it works fine besides that, I'm posting from my phone as well.
Anyone else having this issue? Or any way to solve it?
Thanks,
Aaron
Click to expand...
Click to collapse
Aaron - Please use this thread to continue to write about this issue. Hopefully, we can solve this as a community: http://forum.xda-developers.com/showthread.php?p=46993463#post46993463
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?
HI,
I have had a problem with my phone for two days. When the AUX cable was connected and I was listening to music, the sound suddenly stopped and I thought it was a system bug and restarted the phone. But after restarting, it got stuck on the miui logo and did not come up.
I tested flashing the phone and changing the ROM. And it had no effect. Every time I install the ROM, the sound is still muted and after restarting, it gets stuck on the miui logo.
Also, a mobile repairer fully tested the phone board and there was no problem and also the sound ic was healthy. Please give me a solution so that I can fix the phone. I really wonder why such a problem has arisen
Some more details would help. Which rom, version, you changed the rom by flashing to... what?
Tomo123 said:
Some more details would help. Which rom, version, you changed the rom by flashing to... what?
Click to expand...
Click to collapse
vayu_global_images_V12.0.4.0.RJUMIXM, vayu_global_images_V13.0.4.0 And evolution_vayu
When miui 13 ROM is installed, the phone does not turn on at all. In addition, the ROM that I installed before this problem was the latest official version (13.0.4).
"I have exactly the same problem as you, did you manage to solve the problem?"
Please help me out as I messed my phone up real bad recently and I need to fix it as soon as I can as I have interviews right now and need to be updated with them.
So here's what I did:
I was using Pixel Experience ROM on Android 12, with OrangeFox recovery, it was working fine with no major issues.
I really wanted to try out Android 13 though it's still in Beta but I have heard good things about it, specially the one by Project Elixir.
But since I was already using Pixel Experience and loved the ROM so much, I decided to be on the safer side and look if they have a Android 13 ROM for my phone.
That's where the story began, I mistook the Redmi Note 7 forum (lavender) as Redmi Note 7 Pro forum, I forgot how they were two separate devices.
So I flashed the Redmi Note 7 recovery on my phone and it it didn't boot into recovery when I tried it to, then I downloaded the original (correct one) from OrangeFox's official site and flashed it after which the recovery works. But then as I tried installing the new ROM, my adb sideload kept getting stuck at "Starting ADB Sideload feature" and I couldn't make it work, so I flashed the new OS from my sdcard. It was all fine, I set it up and was loving the experience until I plugged it out of the charger. After a few minutes of plugging it out of the charger, it literally started rebooting and it restarts just in the middle of the boot animation. And when I manually power it on by pressing and holding the power button, it displays that It has no charge left.
I tried flashing quite a few other ROMs too, even Android 12 and 13 both, and at a point for some reason it also showed "system has been destroyed. press the power button to shut down" while booting into recovery but it went away once I re-flashed the recovery, and after no luck, I flashed MIUI but the same thing still persists.
I read in a few forums that it might be a battery issue which I too thought at first but the fact that it happened exactly after I flashed the wrong recovery bothers me. I thought installing the stock MIUI rom through fastboot would solve it by replacing every corrupted files and partitions but the issue seems to persist.
What might have been the issue and what can I do to fix it, and can flashing a wrong recovery cause this even if I have flashed the right one just after that?