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!
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
A few weeks ago, I decided to install Liberated Aria. I had a few problems with the installation, but eventually it ended up working fine. Last night, I turned my phone off and turned it back on this morning, but now it won't boot. When I turn the phone on, I get:
LIBERTY PVT SHIP S-ON
HBOOT-0.57.0000
MICROP-031b
TOUCH PANEL-STN 21_00
RADIO-7.08.35.06
MAY 8, 2010,03:56:58
FASTBOOT
and then the options:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
When I try to boot into recovery, I eventually get:
SD Checking. . .
Loading . . .[LIBEDIAG.zip]
No image!
Loading. . . [LIBEDIAG.nbh]
No image or wrong image!
Loading. . . [LIBEIMG.zip]
No image!
Loading. . . [LIBEIMG.nbh]
No image or wrong image.
and the options change to:
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
The only problem is that I can't select any of the options. None of the buttons - volume, power, whatever - change or select anything. I can't get past either of these screens. I'm kind of a noob when it comes to this kind of thing, so any help would be appreciated.
The phone will automatically boot into FASTBOOT mode if you hold down the trackpad button while pressing the power button. Is it possible that your trackpad button is broken and is being registered as held down? Try messing with it to see if you can fix it. Otherwise you may have to get the phone replaced if it's under warranty.
This issue does not sound like it is related to installing Liberated Aria.
The trackpad button feels the same as it always has when I click it and I don't see anything visibly wrong with it, so I don't see why it would be registered it as clicked. I tried pushing it and all the other buttons a number of times with the same results. I even took off the screen protector thinking maybe that was causing a problem. Is there a way I can just put an image on my SD card and have it automatically boot that so I can fix it?
Doesn't installing a custom bootloader and/or ROM void the warranty?
Well, you probably will be able to simply run the 2.1 RUU on your phone since you can get to FASTBOOT. I'd probably recommend that over doing the SD card method because when you do the SD card method, you have to press a couple buttons to confirm actions which may not work if your phone isn't accepting button presses. The RUU method does not involve any button presses on the phone itself.
However if you want to try the SD card method I can point you in the right direction.
Edit: Link to 2.1 RUU here: http://www.mediafire.com/?cj56c2gfk86k8oe
Rohda said:
Doesn't installing a custom bootloader and/or ROM void the warranty?
Click to expand...
Click to collapse
Installing a custom bootloader would for sure, but you don't have a custom bootloader. Installing a custom ROM does, but you can reverse the process (via RUU) so they can't really tell.
I downloaded the 2.1 RUU, booted to recovery, connected my phone to my computer, and tried to run the RUU but it gave me a USB connection error. Windows also gave me a USB device not recognized error. My phone does say HBOOT USB PLUG, though. Aside from HTC Sync, do I need another driver?
Do you still have the HBOOT driver installed from when you used Unrevoked? If so you should uninstall that driver I believe. That might be interfering.
Also trying running the RUU when your phone is in FASTBOOT, not HBOOT, to see if that works.
I did have the HBOOT driver still installed. I uninstalled it from device manager and deleted the driver folders. Android Phone doesn't show up in device manager anymore. I retried running the RUU in HBOOT and tried running it in FASTBOOT and still get the USB connection error. Any other ideas?
Try reinstalling HTC sync
Sent from my Liberty using XDA App
Also try doing it on a different computer if you have access to one. Preferably one that never had any drivers on it before. Just install HTC Sync, then run the RUU, that's it.
I've always had trouble getting the RUU to run. It's bizarre.
If that doesn't work, and you still want to try the SD card method, you can download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file to LIBEIMG.zip then place it on the SD card. Then it should automatically detect the file next time you're in HBOOT and ask you if you want to proceed with the install. It's pretty self explanatory. Be patient as some steps take a while and it may appear like nothing is happening. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.ZIP file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
I reinstalled HTC Sync and it wouldn't recognize the phone was connected.
It seems to have taken a turn for the worse. Now, it won't even turn on. The screen turns on (but stays black) and off and the notification light flashes red when connected to a computer but won't do anything at all when it's not connected. I'll try to plug it into a wall instead of a computer and let it charge for a while and try the SD card method.
I went in today to get it checked out and got a new SIM card and a new battery and it fixed the problem.
Thanks a ton for all the help.
Hello,
I accidentally didn't put the rom in my internal storage and i thought that i put the rom and tried to boot.img which it was successful, then i realize that i could go to my stock rom even after booting the image file from ARHD rom, but something happend, my internal storage or phone storage shows unavailable so i couldn't mount it on the computer then to put the rom back, i also used sideloader many times but all the time it shows device not found but the things is i use hasoon tools to get in recovery however just onetime it sent the rom into the phone but when i was trying to install it the percentage stuck at 0% no progress, i also did factory reset and hold the power off button for 10 secs but didn't help so much, now nothing work cannot put anything in the phone via computer or adb, and also my wireless shows error and cannot even turn it on,,
please help me
-----
my computer shows the device but cannot put anything into it it just stucks.
arman258 said:
Hello,
I accidentally didn't put the rom in my internal storage and i thought that i put the rom and tried to boot.img which it was successful, then i realize that i could go to my stock rom even after booting the image file from ARHD rom, but something happend, my internal storage or phone storage shows unavailable so i couldn't mount it on the computer then to put the rom back, i also used sideloader many times but all the time it shows device not found but the things is i use hasoon tools to get in recovery however just onetime it sent the rom into the phone but when i was trying to install it the percentage stuck at 0% no progress, i also did factory reset and hold the power off button for 10 secs but didn't help so much, now nothing work cannot put anything in the phone via computer or adb, and also my wireless shows error and cannot even turn it on,,
please help me
-----
my computer shows the device but cannot put anything into it it just stucks.
Click to expand...
Click to collapse
i'v solved it, finally found my sideload in sdcard and boom, it works now,
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
I took it to Sprint. They thout it was the power button, after replacing it and the same I got a refurbashed phone through TEP insurance at no cost. WIN. Except does anyone have S-off suggestions for Hboot 2.09 and mainver 3.17.651.4 dirtyracun which I am familiar with does not apper to work.
m1gramme said:
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
Click to expand...
Click to collapse
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
fizbanrapper said:
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
Click to expand...
Click to collapse
My HBOOT is 2.09.4444
I believe my ROM was eiter a rooted sense or BeanStalk 4.3. I honestly don't remember because I haven't changed anything in so long.
I had TWP openrecovery-twrp-2.6.3.0-jewel.img
Again this wasn't a problem that came from trying to change anything. My phone froze I soft-reset it and it was in an unstoppable bootloop. No images were found. Telling it to go to recovery still took it to bootloop. Even after power down from bootloader, after 20 seconds it boots back into bootloop.
The problem I feel most at hand is I can't charge the battery enough to do anything because it appears to not charge in bootloader.
I have had my phone rooted and s-off through Dirty Racun for almost a year now and have been using the same setup without changing for at least 6 months.
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
If you're able to and have the proper equipment, I'd test the internal battery with a voltage meter to see if it is even able to hold a charge, will save a lot of frustration.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
Again the hardest part about this is my phone refuses to turn off. I have gone into the bootloader and selected Power Down. The phone turns off and the charge light blinks. Then 20 seconds later without me touching it, it turns on and starts into the bootloop.
I am currently finding some luck by holding the down button so when it starts itself again I can be in bootloader mode and select power down. I have elevated my battery from 3530mv to 3649mv (as per fastboot getvar battery-voltage)
Any suggestion as to where a good number to reach would be helpful.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
See above about "charging" after getting it up a little (and without SD card) I tried booting to recovery (getvar battery-status good) still went to htc bootloop screen. Tried to flash recovery and boot as per
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
in troubleshooting guide. Still continues in bootloop
So a littel update after spending forever with my charging trick I was able to get a little more charge. I was able to run commands of flash recovery it stated it was complete. Still boots to bootloop. I was able to try to run RUU using RUU 3.15.651.16 - HBOOT 2.09
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip RUU.zip
The whole process worked (said it did)
Still in repeating bootloops at htc screen.
Phone still turns itself on into a bootloop even after selecting power down from bootloader.
I'm beginning to think it's the dreaded brick...
Interesting issue, indeed. There were some problems reported with the 3.15 RUU, but none that should cause the issue you're having. Check out the top link in my sig and go to the bottom of the first post. Hit up the link for VipeRUU. I suggest trying it and returning your phone to stock. If after returning your phone to stock the issue persists, then you most likely have a hardware issue (already sounds like that's likely the case). If you have TEP with Sprint you can take the phone to a Sprint service center and see about getting it replaced.
Sent from my HTC device
My wife had that issue as well but a factory reset fixed
Sent from my EVO LTE using Tapatalk
This is going to be a little long, but I figured the more info the better. I recieved a TF201 from a friend of mine. He already had it rooted and running a custom ROM. It was loaded down with a bunch of stuff so I attempted a factory restore through CWM so I could start over and customize to my liking. Everything went fine (or so I thought) It booted back up to stock interface and still had root intact. I downloaded Astro FM from Play Store just to have a look around and make sure everything was intact. Everything seemed normal but suddenly rebooted and stuck at splash screen. Im able to boot into recovery still so first thing I tried was loading a backup as there were about 6 of them in the list of backups. None of them work, I just get "No files found" error. Next I tried to reload stock ROM with the Install zip from SD option. Also getting no files found error. somehow the SD card has nothing on it anymore even after copying a zip of the stock ROM downloaded from ASUS. The only other thing I can do that I know of is instead of loading recovery, is go into the cold boot menu with the 3 icons in the middle of the screen. By pressing nothing, it says that it is cold-booting Linux. This process just hangs and nothing happens. It does attempt to install MTP device drivers (which were already previously installed) but ends in an error (Failed). Selecting the middle option gives me "Starting Fastboot USB download protocol" but this also hangs and does nothing. Lastly the "Wipe Data" option completes it process and says "Wipe-Data done" but then also hangs and does nothing. At this point Im assuming its Hard Bricked and nothing can be done but I just wanted to see if anyone would be able to help. I have read a lot of similar posts on here but haven't been able to find anything that helps. Most other people with similar problems at least have a way to install from SD but my device wont recognize anything on the card. Does anyone know of anyway to fix this??