Here's what happened - Few days ago, my Legend started to malfunction in phone coversations. I would talk, and I would hear myself from the speaker, but the person I called couln't hear my voice. I hoped rebooting will help. But it didn't. So I used ROM Manager to backup, and recover my previous back up file (I may not be using the most accurate terms. I was able to successfully root my Legend on my own but I'm most definitely not an expert.)
Even in my restored backup, I was having the same issue. So I tried to revert back to the back up I made minutes before. But this is when the problem started. It went to a blackscreen with a phone and a red exclamation mark triangle.
I physically removed the battery to reboot, and first I'l see the HTC boot screen, then I go to the android OS lockscreen. When I unlock/swipe, I once again see the HTC boot screen, and I eventually get the "com.android.phone is not responding" and "process com.hc.bg has sopped unexpectedly" error messages.
I tried to go into fastboot -> bootloader, and it freezes for a few seconds then spits out the "no image or wrong img" message, which promptly disappears. If I go to the "recovery", it goes back to the blackscreen with the phone and red exclamation mark triangle.
Have I "bricked" my phone? Or is there a way to restore my previous backups? and at the sametime, has anyone encountered the microphone issue that I mentioned at the beginning?
I tried running the recovery-windows.bat but that did nothing
I'm running CM on my phone when the power button stopped working. I tried to re install the rom but something went wrong, and now I can't get past the splash screen with Cid. Whenever I try to boot into recovery I get the blue text, but it will not boot, it just shuts off. Whats the best way to fix this problem?
Thank you.
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
UPDATE: Solved, i flashed TWRP over CWM using Odin, and was from there able to re-install the OS. Things seem to be working fine for the most part, with the exception of one random reboot last night.
Salomon3068 said:
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
Click to expand...
Click to collapse
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
buhohitr said:
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
Click to expand...
Click to collapse
I figured it out yesterday actually and forgot to update! Indeed I was able to flash TWRP with odin, since CWM seemed to be blocking me from doing anything. Once that was up and running, things went back to normal, i was able to flash CM 10.2.1 and things seem to be working now.
One thing though, while playing skyrim last night i had it on the charger next to me, and the phone randomly rebooted without any interaction from me. Was odd, but it hasnt done it since. Keeping an eye on it still.
Hello all!
Just got my One +1 today and I have an odd problem with it. Whenever I try to reboot it or reboot to install an update, it hangs up at the One +1 boot screen. I have to shut the phone down for a few minutes before it will start up again and it won't install updates to CM. So far I've tried going into Fastboot (hangs up at CM logo), factory reset (hangs up at One +1 logo), and even just plain reboot (One +1) logo.
It seems to work fine otherwise and I can power off and power back on again, but this is more than annoying. Has anyone encountered this before and have any wisdom to share so I can get past this?
Well, it seems to have fixed itself somehow.. Not exactly sure what went right, but there is hope if anyone else has the same problem.
Hello XDA!
This morning, I attempted to flash Cyanogenmod 12 (CM12) onto my Google Nexus 6 using this youtube tutorial that I cannot link in this post, because I am a new member. The title of the video is "How to install CyanogenMod 12 Official Lollipop on the Nexus 6" It can be found on youtube.
Whenever I boot up the phone, it shows the "Google" screen. then the Cyanogenmod boot animation appears. A white popup shows up saying "Android is Starting Up. Finishing Boot" The entire screen then comes to life with cyanogen's default background. Finally, an error message consumes the screen saying "ENCRYPTION UNSUCCESSFUL. Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone, we need to preform a factory reset. When you restore your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account." The only button shown on the screen says "RESET PHONE". If clicked, the phone reboots, but before it can boot it gets stuck loading the TWRP Recovery application. What happens is, it'll show the TWRP logo, then the screen will turn off, then it'll show the TWRP logo again, then this loop will repeat endlessly. The only thing that I could do was reboot the phone into the boot loader by holding down the power button, and the volume down button. From here, I attempted to boot into recovery mode. The same thing happens, the TWRP screen loads, then disappears, and that just repeats itself endlessly. I also tried to preform a factory reset, but that didn't work.
As you can see, I really need some help.
The encryption failing may be caused because I came off of a custom ROM where I had the phone's encryption disabled.
THANK YOU VERY MUCH, and if I can provide any information, please ask.