My HTC One XL went on low battery and i plugged it on charge. Power outages meant the phone couldn't charge and when power came back on, I plugged it again on charge for about two hours. I tried booting the phone and the phone couldn't start, but the red light kept blinking even though it was unplugged from the charger. I pressed and held the power button for a while and turned it on again. It came on, but could not boot pass the "HTC quietly brilliant" screen, it kept restarting from that screen after it stays on for some seconds.
Next thing i did was to boot into bootloader. The bootloader was initially "Unlocked" but when the bootloader came up, it showed "LOCKED", which means the bootloader has gone back to locked all by itself. I tried unlocking the bootloader again, but when the unlocking warning screen shows up and i select "YES", it restarts and the "HTC quietly brilliant" screen keeps restarting. I tried factory reset from bootloader but the htc screen comes up and restarts from there.
The next thing i did was to look for an RUU. I couldn't find any, as most of the links were down. So i downloaded "RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio_0.19as.32.09.11_2_10.105.32.25L_release_271865_signed" and I tried flashing from there, but the RUU loader could not load on the phone, could not even restart into the bootloader, as the HTC screen keeps restarting. RUU could not also be loaded from fastboot commands. I tried flashing a new kernel, but the phone doesn't allow the command to push the "boot" image file.
The phone was running on the official T-Mobile 4.2.2 Sense 5 which I updated OTA before unlocking the bootloader, and everything was working just fine, until the phones battery run low and the bootloader went back to locked by itself. Please help, as it seems all options have been exhausted. I have attached a copy of an image of my bootloader. But the details are as follows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OpenDSP-v33.1.0.45.1128
eMMC-boot
Aug 14 2013, 16:02:22:-1
Please help :'(
Related
I have an HTC Amaze 4G PH85110 that will not boot up into the Android OS past the boot screen.
Let me walk you through what happens;
I push the power on button, the phone vibrates and the screen comes to life showing the HTC logo. This is where it stays forever until I pull the battery. I left it on for a good 20 minutes on this screen on a number of occasions and it just hangs there.
When I press the Power + Volume Down button it boots into the special boot screen with the following visible:
Code:
*** UNLOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
eMMC-boot
Mar 15 2012,21:46:51
HBOOT
SD Checking...
Loading...[PH85DIAG.zip]
No image!
Loading...[PH85DIAG.nbh]
No image or wrong image!
Loading...[PH85IMG.zip]
No image!
Loading...[PH85IMG.nbh]
No image or wrong image!
Loading...[PH85IMG.tar]
No image!
Loading...[PH85IMG.aes]
Battery voltage is too low!
Please change a battery...
[Power] -> Continiue
Once I press Continue it goes in to this screen
Code:
*** UNLOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
eMMC-boot
Mar 15 2012,21:46:51
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
Selecting FACTORY RESET gets me to a dark screen where there is an icon of a phone with a progress bar below it, it stays there for aprox 20 seconds and it then it goes to a white screen with the HTC logo, just like on a fresh boot and it just hangs there forever, until the battery is pulled.
Selecting RECOVERY brings me to a dark screen with an icon of the phone and a red triangle with an exclamation mark in front of the phone icon and it just hangs there till the battery is pulled.
From what I remember the previous owner tried installing a custom firmware and something went wrong along the line and was never able to boot the phone back up. I am guessing that because the S-ON was never changed to S-OFF this somehow ****ed with his firmware change. But all that is guesswork as I do not remember the specific details.
I remember at one point installing a custom recovery screen on the phone and it would boot into it, but once I would try and flash a custom rom it would never complete, complaining about access restrictions if I am remembering correctly.
I also remember getting the phone in to FASTBOOT and getting the computer to recognise and communicate with it, but every time i tried to upload a custom radio/rom/whatever to it it would complain about access restrictions.
However, the phone is unlocked. But, the S-ON is.... on.
so
Is this phone salvageable or should I just throw it away and stop worrying and trying to fix it anymore?
Two pieces of info needed:
Pls download AIO 5.1 http://d-h.st/users/hasoon2000/?fld_id=2811#files
1. Check what the phone CID is. (write down what displayed in the command prompt)
2. Then try: Reboot into Recovery (see what happened on handheld screen)
P.S. Find a way to charge the battery either..
P.P.S. Make sure you have a microSD card available with you..
Got the AIO 5.1 tool
The CID as copied from the command prompt is cid: GLOBA001
Selecting reboot to recovery makes the phone boot into 4EXT Recovery Touch
I have the battery charging as we speak, and there is a 16Gb MicroSD waiting incase I need it.
Try to download this http://d-h.st/7kW
Rename it PH85IMG.ZIP (make sure you see the file extensions on your PC so it is not got named PH85IMG.ZIP.zip ) then put it on your microSD, insert it, then reboot Amaze into Bootloader (not into 4EXT Recovery) and let us know what happened..
P.S. However it seems being EXE - not sure 100% it will work particularly the way mentioned above.. may require to be executed on the PC..
Alright downloaded the RUU_Ruby_Globalive_WWE_1.45.1500.2_R_Radio_1.09.55 0L.11v2DC_30.67.550L.09_release_227347_signed.exe it recognised my phone but it failed to install on the final step saying that it can not continue.
Now I am going to try and download the .zip ones, both from Globalive and T-Mobile and try each one and see what happens.
Turbonator said:
Alright downloaded the RUU_Ruby_Globalive_WWE_1.45.1500.2_R_Radio_1.09.55 0L.11v2DC_30.67.550L.09_release_227347_signed.exe it recognised my phone but it failed to install on the final step saying that it can not continue.
Now I am going to try and download the .zip ones, both from Globalive and T-Mobile and try each one and see what happens.
Click to expand...
Click to collapse
To flash ph85img from bootloader the bootloader has to be relocked first. But for your carrier I believe you have to run the exe from your computer
sent from.. wait, where am I?
Need to upgrade your T-Mobile Amaze to ICS? CLICK ME!
Unbranded/Asian/International Amaze owners CLICK HERE. Upgrade to ICS from GB so you can flash custom roms
:good: If someone has helped you, hit their thanks button! :good:
Did you try executing the downloaded EXE file on PC whilst connected by the native Amaze 4G microUSB cable (which is slightly different though)?
I don't have the native Amaze MicroUSB cable. Just a regular one.
I am now going to try and lock the bootloader and try the .exe again.
I tried quite a fiew of the official UUM .zips and exe's both with bootloader unlocked and locked. Same thing happens, the .exe's detect the phone start and then say IMG FAIL. The .zip's in the custom recovery menu all start updating then immediately stop.
Does this have anything to do with the fact that I have S-On? How would I switch it off if I can't get into the phones OS in the first place?
To have a phone that seems to work yet refuses any attempt at loading a working OS on it is so very frustrating.
Can I take this into a shop and have them force feed the rom onto the phones memory somehow with some kind of special connection that goes straight to the memchips?
- If you are S-ON - you may just install ROM which is intended for WIND.. no any other ROM..
- Wind ROM must work in Bootloader whilst named PH85IMG.ZIP even if it is UNLOCKED though..
- When you run EXE on PC - keep the phone attached and booted in Bootloader (and there must be Fastboot USB mentioned )
- Try using AIO to install RUU (make sure microUSB cable is 100% operational)
P.S. No sure - but you might want to give it a try:
http://forum.xda-developers.com/showpost.php?p=38142562&postcount=6
Help! My htc amaze install the Rom the wifi didin't work
jauhien said:
- If you are S-ON - you may just install ROM which is intended for WIND.. no any other ROM..
- Wind ROM must work in Bootloader whilst named PH85IMG.ZIP even if it is UNLOCKED though..
- When you run EXE on PC - keep the phone attached and booted in Bootloader (and there must be Fastboot USB mentioned )
- Try using AIO to install RUU (make sure microUSB cable is 100% operational)
P.S. No sure - but you might want to give it a try:
http://forum.xda-developers.com/showpost.php?p=38142562&postcount=6
Click to expand...
Click to collapse
Everything is fine, but..my wifi and bluetooth didin't work. :crying:
In my Setting:
Wifi showing "Error",
Bluetooth showing "off", and both I can't switch it on.
Personalize is not working.
I also got the same problem from the hboot
*** UNLOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT
SD Checking...
Loading...[PH85DIAG.zip]
No image!
Loading...[PH85DIAG.nbh]
No image or wrong image!
Loading...[PH85IMG.zip]
No image!
Loading...[PH85IMG.nbh]
No image or wrong image!
Loading...[PH85IMG.tar]
No image!
Loading...[PH85IMG.aes]
stickies
htcamazeg22user said:
my wifi and bluetooth didin't work
Click to expand...
Click to collapse
Check the stickies at the top of the forums for what you are trying to do.
I have a hunch you updated to ICS and didn't update the radio.
Hello there!
I have some questions about my phone that is bricked..
My phone: HTC EVO 3D (GSM)
I will tell you all things that I did to my phone, and how the phone behaving is. ( Sorry for bad English at the start )
All started when I swapped different SIM card into my phone, that was already swapped before and phone was functionaling normally.
And last time I swapped it again and I got it bricked, or boot looped, or something else.
So the phone behaving is next:
When I put my battery in and put it on charge, the red light for charging turns on for about 4-5 seconds, and then it turns off and stops charging.
And when i turn it on, it just shows HTC logo for few seconds and after that it goes to black screen and stays there forever, and my touch button lights stays turned on.
When I connect my USB cable while that black screen is on, Windows starts to search drivers for "qhsusb_dload".
When I put battery out and in again, I can access my HBOOT and FASTBOOT by pressing volumedown and power button, but when i try to go to Recovery, or Factory reset, phone just shuts down.
My HBOOT version was 1.53.0007, and I successfully downgraded it with Unknownforce Ultimate Recovery Tool 3.1. to 1.49.0007 on this thread:
http://forum.xda-developers.com/showthread.php?t=2124142
And then I successfully installed RUU with PG86IMG.zip, but still goes to black screen.
And condition of my phone now is:
***LOCKED***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0007
RADIO-10.13.9020.08_2M
eMMC-boot
So I found thread on xda-developers forum with unbricking procces for qhsusb_dload issue, but that proccess can't detect my phone.
Here is thread: http://forum.xda-developers.com/showthread.php?p=25501417
I did not do any updating, or anything that could brick my phone to this state, just what I did is swapping different SIM CARD, and after that I did not manage to turn it on.
So I'm out of my mind, and asking you for options if you have any?
Thank you.
I have a stock HTC one from t-mobile. I have not rooted or even gone into the bootloader menu until now.
Here's my story
I tried to install an OTA update.
Phone got stuck at the HTC one screen with the beats logo at the bottom.
I restarted multiple times and it never made it past that screen. I even left the house for 4 hours and came back to the same screen.
Here's when things got strange
I boot into bootloader to do a restore and at the top it says
*** TAMPERED ***
*** LOCKED ***
Keep in mind I have never so much as been to the bootloader screen, so it goes without saying that I have never unlocked the phone, rooted, or flashed any roms, custom or otherwise.
I try to restore, and it brings me back to the bootloader screen.
I try to do a factory reset, and it brings me back to the bootloader screen.
I get the RUU from the HTC website.
I proceed with the RUU, phone goes to a black screen with an HTC logo in the center, a few minutes later I get a signature error.
Try again, same thing.
At this point I say screw it, I'll just unlock it and flash a custom rom, no biggie.
I go through the steps, get my unlock_code.bin and send it to the phone.
CMD says it's successful. But the phone doesn't change to the unlock confirmation screen. It just stays in the fastboot menu.
I go to the bootloader menu, and poof! The tampered bar at the top goes away, but it still says locked.
I try unlocking a few more times to no avail.
I then attempt the RUU once more thinking that since the tampered bar is gone, maybe this will help somehow. this time when it says it's booting into bootloader on the pc, the phone tries to actually boot.
of course this doesn't work, and I get an error saying the RUU can't communicate with the phone or something.
I reboot into bootloader, and the tampered bar is back, I do what I did last time to take it off, and it works.
I run the RUU again, but this time when it tries to reboot into bootloader I hold down the power and volume down buttons, trying to get it there manually. But it just tries to boot as normal again.
Now I'm at a loss.
I reboot into bootloader one last time, and run the RUU without doing the steps to take of the tampered bar
RUU is successful (WTF) and phone reboots just fine.
Just for ****s and giggles I reboot the phone into bootloader,
The tampered bar is gone... now it just says locked.
I have no Idea what happened. but if anyone else has similar problems maybe something in what I did will fix it... Who knows.
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
Hi,
Got a bit of a problem here. I recently bought a HTC One Mini second hand from a flea market, with the apparent problem of it not being able to boot. What happens when you just normally turn the phone on with the power button is that it goes into boot loader without booting into the normal HTC phone. I'm pretty sure it's a software problem (i.e. not like the volume down button is stuck), because trying to boot into recovery, factory reset, clear storage is all useless.
Some details about the phone:
The phone is LOCKED, not re-locked. This means that the boot-loader has never been unlocked before, right?
I've tried unlocking the bootloader on the phone, and the steps are successful until the " fastboot flash unlocktoken Unlock_code.bin" part, where the phone doesn't react at all even though the process is shown as successfully completed.
The first few lines on the fastboot screen are:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
OS-4.14.401.2
eMMC-boot 1024MB
Aug 12 2015, 18:31:50.0
Thanks for the help!