So I recently took the plunge and rooted, loaded TWRP and installed CM 12.1. I am unable to reboot my phone without pulling the battery. I also am unable to reboot to recovery from the reboot menu. The phone just goes black and will not power back on until I remove the battery first. Has anyone else seen this problem? I am afraid to do anything more to this phone as I feel I have gotten very lucky to accomplish what I have thus far.
Related
My Eris has been stuck in safe mode for several days now. I have done all kinds of searching on every forum, and no solution has fixed my problem.
The phone is rooted, had a recovery partition (amon ra 1.6.2 [trackball fix]), and can boot into the bootloader.
Things I have tried:
Wiping everything in recovery. Data/cache, dalvik, battery settings, etc. Flashing another ROM.
...still in safe mode.
Then, I tried using the bootloader, it refuses to recognize the img I have installed. So I changed the name of the .zip for the rom to be "PB00IMG.zip", rewiped, reflashed, and then the bootloader recognizes the ROM. Except, it says is is "caching" after "loading", and then returns to the "fastboot" and "recovery" menu screen. Upon reboot, it is still in safe mode.
Then, I tried installing the Stock rooted pb00img.zip, this removed the Amon Ra recovery partition unfortunately. Still in safe mode. I have tried every combination of button-holding during startup that I could find.
A bit of background on the issue:
Over the weekend, my phone got some water in it. There was some precipitation on the inside of the screen, but it has gone away. I thought I had sdcard damage, but data was (and is) accessible from the SD. I have tried booting the phone without the SD card in, still in safe mode
Does anyone have any other suggestions?
Thank you
mrnatas19 said:
My Eris has been stuck in safe mode for several days now. I have done all kinds of searching on every forum, and no solution has fixed my problem.
The phone is rooted, had a recovery partition (amon ra 1.6.2 [trackball fix]), and can boot into the bootloader.
Things I have tried:
Wiping everything in recovery. Data/cache, dalvik, battery settings, etc. Flashing another ROM.
...still in safe mode.
Then, I tried using the bootloader, it refuses to recognize the img I have installed. So I changed the name of the .zip for the rom to be "PB00IMG.zip", rewiped, reflashed, and then the bootloader recognizes the ROM. Except, it says is is "caching" after "loading", and then returns to the "fastboot" and "recovery" menu screen. Upon reboot, it is still in safe mode.
Then, I tried installing the Stock rooted pb00img.zip, this removed the Amon Ra recovery partition unfortunately. Still in safe mode. I have tried every combination of button-holding during startup that I could find.
A bit of background on the issue:
Over the weekend, my phone got some water in it. There was some precipitation on the inside of the screen, but it has gone away. I thought I had sdcard damage, but data was (and is) accessible from the SD. I have tried booting the phone without the SD card in, still in safe mode
Does anyone have any other suggestions?
Thank you
Click to expand...
Click to collapse
Well, sounds like you've hit the obvious things... Sounds like things are partially working since the base root ROM you installed replaced the custom recovery.
Since the phone did get wet, did you try the dry-rice thing? (putting the phone in a bag/container of dry rice for a few days to try to pull all of the moisture out).
Take a peek at this thread over on AF: http://androidforums.com/htc-droid-eris/142731-safe-mode.html
where apparently its the trackball thinking its pressed is what puts the phone into safe-mode. Perhaps an alcohol cleaning or attempt to clean/dry the trackball a little more (or even removal) might help you out.
Here's a thread discussing how to replace the trackball: http://forum.xda-developers.com/showthread.php?t=657468 which might help you get it cleaned / dried.
Hope this helps.
Cheers and good luck!
Safe mode happens when you hold the trackball down (center click) during booting.
That suggests to me that the moisture problem you had has somehow caused that switch to go (permanently?) closed. That's probably also what interferes with other operations from working correctly - your phone thinks you are holding the trackball down.
You could fool with inserting a USB plug and wiggling it around to see if that makes any difference. If it was my phone, I would probably try replacing the trackball assembly if the problem did not disappear after a couple of days.
bftb0
My sensation always start on safe mode.
How can i remove it?
I flash 2, 3 ROMS and is the same thing..
Any ideas?
Regards
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
Alright so I've been running UKB and Cubed kernel for the last 6 days without issue. I've had some random reboots and the phone locking up, but I was just going to deal with it until ViperDNA came out. So this morning comes and I unlock my phone and the phone reboots within 2 minutes. Comes to the lock screen and is completely stuck... Alright it happens. I hard reboot the phone (holding down power and volume down buttom) and reboot the phone. Still, it is frozen at the lock screen. Phone is coming up in ADB devices, but it cannot accept any commands. I reboot into recovery (CWM 6.0.2.1) and try to clear cache/dalvik. Reboot the phone and it's still stuck at the lock screen. I go into fastboot and push the stock kernel, phone boots gets to the lock screen, starts of fine and then locks again. I don't have any earlier restores to go to on the phone as I shifted them to my HDD to save a little space. I feel like an idiot now. Any help would be appreciated.
I also tried to sideload ViperDNA via CWM and it isn't showing up the device in ADB.
EDIT: Also while in Fastboot the computer shows the device as attached via Removable hardware as Android 1.0 it just wont let me sideload or push anything other than a kernel.
This happened to me at one point.. I had to re lock the phone in the all in one tool and reunlock and start fresh.. No problem since
With help from Dr_demento on the IRC channel I was able to get the phone booting again. For future reference of people running into this issue, formatting data helps. You'll unfortunately lose everything, but it's better than locking the phone and then unlocking it again.
Hi guys,
first of all thank you for taking your time and reading through this. I'm not completely new to android, nor using fastboot and recovery. I flashed a few phones over the past years I even resurrected bricked ones. However I have no idea what is happening to my Honor 8. One thing to mention, it's the latest Nougat update, and a STOCK ROM.
It all started this afternoon. The phone suddenly reboot while using it. After that, the android screen came on, then Honor animation and.. freeze. Completely. I had to reboot using the long press method since it was stuck between the bootloader and the rom itself. It started up ok after that.
An hour passed, and while I was typing a message, it froze again. I could go back to home but the phone was really slow. After opening up Messenger again, it froze completely. Had to restart again with the long-press reboot method. It started up ok, entered the sim pin and upon entering the screenlock code it froze again, completely. Long-press reboot, again.
Since then, the phone won't boot. It gets stuck every time on "Honor powered by Android" for about a minute, then it reboots itself. I even got some weird green screen with a blue and a red rectangle, but that just stopped after a few reboots.
I mentioned that I know how to recover and fix stuff when something acts weirdly, but that's not the case, I can't do ANYTHING. No fastboot, no recovery, no button combinations, I can't even turn off the phone. It just keeps rebooting on and on, and yes, the battery will eventually die, but I have no access to any recovery options. I even tried dload but no luck.
It's still under warranty so I can send it back but I just rather fix it at home (without taking it apart), because I don't want to wait 3 weeks to get fixed. But it seems like that is the only option right now, I have never ever seen anything like this happen.
Any help or comment is appreciated. Even if it's not possible to do it at home (hardware issues?), I am really curious what can be the cause of this issue (damaged rom, filesystem permission issues?).
Thanks.