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
Related
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.
My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...
Ok, here is the deal and I hope someone can help me. I have a cheap DigiLand DL1010Q tablet to play around with. It is stock, but I rooted it with KingRoot. There was a recent OTA wireless update and after it was installed it said that it needed to go into recovery mode to install and reboot. I selected install now and reboot. This is where my problem started and has remained. It loaded into recovery mode and is in an endless boot loop. I've tried rebooting it, recovery with the recovery file and every manual reset possible to no avail. DigiLand support said that I should power down the tablet, and while holding down the Volume Down (-) hit the power button and it will boot into a Chinese recovery mode. I've tried that and it just stays on the DigiLand screen forever. (I left it there for 8 hours.) I can sideload via ADB and the drivers are installed, but it will not let me load anything. It states that the bootloader is closed. I receive the same message via Fastboot. Now here is the interesting thing. Even after selecting the factory reset within the Recovery Mode, everything is still there. I have wiped the cache and partition and user data, but nothing really happens. It is still all there. I see the recovery file, but it will not load. All I see is NO Command.
I do have a sd card that I could flash things on, but it doesn't seem to register the card. It sees the sdcard, but that is the internal drive. How do I get it to look at the sdcard that I put into the slot? Is there a bootloader unlock? Does anyone have the factory image that I can put on my sdcard? HELP!!!!
I am fairly good with computers and have rooted phones and tablets before, but I seem to be hitting my head on a bricked wall - no pun intended. Let me know what programs, files or whatever. At this point I am willing to try anything. I can send it back to China for $50 for them to redo it, but I only paid $69 for it and I'm not going to put more money into this cheap tablet. I would just like to get it to work.
My One M9 is stuck on boot screen and I've tried everything. This was just given to me it wasn't brand new though. When I do volume down and power button it just goes to HTC black screen and silver logo then reboots after 2 seconds. When I go to recovery mode to format data and cache it shows data can't be mounted. When I try to install RUU it says low battery when I go on Fastboot mode. And I also tried to install the ruu zip on recovery and it also shows the mount error. I also tried to unlock the bootloader but I can't do it because the OEM UNLOCK option in developer mode is not checked.
My bootloader screen shows
Software: modified
Locked
S-on
I'm so desperate right now I don't know what to do.
I'm having a similar issue. It started with the settings application on my phone apparently getting corrupted. I could no longer open it and couldn't do things like turn WIFI and GPS on and off, also Maps would crash just after launching. This was...inconvenient, as I was on a business trip at the time. Fortunately I had my work phone as a backup. Unfortunately, as I had just bought a larger SD card, I hadn't copied any of my backups over. By the time I got home, the phone would not reboot to the system at all, it just gets stuck on the white HTC screen.
I can still get into recovery/fastboot/download mode, and can still connect via USB in these modes. I first tried to reflash a few different backup ROMS, and some fresh ones. They all had the error "cannot mount /system". I also found out that I couldn't get to the data or system image partitions. After digging around in TWRP, I found that they have a size of 0MB. Looking around various threads, I read that an RUU has a good chance of restoring this, so I tried that out.
I ran into another problem with the RUU...no matter what my battery is charged to, the RUU will not start the install. It fails saying that the battery must be charged above 30%. This is was after I left it plugged in overnight. When powered off, it reads 100%. TWRP also registers it at 100%.
I have also tried extracting the stock ROM from the RUU to flash in TWRP, but no matter how many times I try the .zip that I find in the temp directory says that it is corrupted.
I am Modified/UNLOCKED/S-ON, does anyone have any ideas? I really appreciate any help!
Someone help us, please. Thank you!