I have an htc one as stated above. It is rooted and has s-off but at the time things went wrong I was running my stock rom.
Yesterday when I went to pause my music my screen froze. I tried turning my phone off and when I attemtep to reboot it all I got was the htc white logo screen. It will remain on this screen until I turn the phone off.
I can enter the bootloader but the options don't work (reboot only turns the phone off, factory rest freezes the bootloader) I have tried everything to fix this, from locking the bootloader and using an RUU exe (locking the bootloader failed) to reflashing the recovery (gave me the error "remote image update error).
The thing that I really don't understand is why this happened, I wasn't even doing anything and my phone just crapped out on me.
I need this phone back and I don't know what to do, any help is greatly appreciated.
Thanks!
Oh, and the best part is that all of this happened AFTER I already filed a warranty claim for the phones faulty mic. My new device comes tomorrow and if I send them this one back I'll be out 600 bucks.
Is there any way to fix this?
wolfsummers said:
I have an htc one as stated above. It is rooted and has s-off but at the time things went wrong I was running my stock rom.
Yesterday when I went to pause my music my screen froze. I tried turning my phone off and when I attemtep to reboot it all I got was the htc white logo screen. It will remain on this screen until I turn the phone off.
I can enter the bootloader but the options don't work (reboot only turns the phone off, factory rest freezes the bootloader) I have tried everything to fix this, from locking the bootloader and using an RUU exe (locking the bootloader failed) to reflashing the recovery (gave me the error "remote image update error).
The thing that I really don't understand is why this happened, I wasn't even doing anything and my phone just crapped out on me.
I need this phone back and I don't know what to do, any help is greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Additionally, everything is still unlocked (bootloader says unlocked, still have s-off) and there is no tamper evidence either.
wolfsummers said:
Additionally, everything is still unlocked (bootloader says unlocked, still have s-off) and there is no tamper evidence either.
Click to expand...
Click to collapse
When you enter your boot loader, what does the following command give you: fastboot devices
If you get your phone in response, you are not out of hope.
Sent from my Lunar Ecliptic One.
Related
Hey all!
I have a question, I recently tried to flash the stable CyanogenMod 7 for Wildfire. The ROM flashed but when it was installing no dialogue came up, I decided to reboot my phone to see if it had worked. I discovered that the ROM had not actually installed because my phone stayed on the HTC boot logo forever. I even left it on before I went to sleep to see if it would eventually boot into the software but no, it was still on the boot logo when I woke up. The logical solution to this would be to boot into the recovery screen but there's a problem with that, I can't. In getting my screen replaced in the past the volume buttons have been broken and therefore I cannot select the recovery option on the bootloader screen :\ Would anyone be able to offer me an alternative to booting into the recovery screen as I currently have no way of fixing my phone and am beginning to get pissed off with the ZTE Racer I'm using as a replacement...
Any help would be much appreciated!!
Try installing a RUU of 2.1 and then see if your volume buttons work. If not then contact HTC for a repair.
You misunderstand my problem, I think. I can't run the RUU because there is literally no software on my phone right now so RUU won't even recognise that it is connected to the PC because I can only access the Bootloader screen but cannot select any options because of my non-functional volume buttons. I'm pretty sure I can't send it back to HTC because my warranty is voided by the fact that I've rooted the phone and failed to install custom firmware on it and therefore it has been modified, please tell me if I'm wrong but I'm really in a predicament here. If I'm wrong about having voided my warranty would I be right in thinking any repair would be free?
EDIT: I managed to fix my phone. Pretty much all I had to do was load the bootloader, select fastboot, plug it into my PC and using the correct RUU I managed to restore my phone to stock ROM Thanks for the help!!
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
alibabazhang said:
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
Click to expand...
Click to collapse
The first time I tried to Root my phone, I had the same problem with Toasts Root method. That's stock Recovery you're seeing.
I ended up having to use Unrevoked Linux version and swore I would never unroot again, and I haven't.
I've tried using unrevoked and several other methods. The problem is I think most of them rely on the phone being on with USB debugging enabled. I unfortunately can't get there. The one ray of hope I have is that the device is recognized in my device manager as "Android USB device - HTC bootloader". Is there any other way I could fix this?
alibabazhang said:
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
Click to expand...
Click to collapse
Are you holding power and volume down at the same time. Sounds like you are just holding volume. When you get to the bootloader I'd you see s-off all you will need to do is flash a PC36IMG of the recovery of your choice(I recommend twrp). Good luck!
Sent from my PC36100 using XDA Premium App
Also, no need to unroot for any rom. Once you are rooted you can flash anything you want. Compatibility wise, you may need to update a radio but that is just flashed in recovery.
Sent from my PC36100 using XDA Premium App
Thanks for the reply. Unfortunately I am holding power and volume down. Powering it on normally and powering it on while holding volume down both go to the same screen.
Hi all, first time poster long time reader.
I'm stuck, tried a few things and I don't know what to do next. I'll try and keep it brief..
One X international, sim unlocked, Stock ROM 3.20.401.31, bootloader locked
So, I was using Google Maps navigating a place I never visited trying to get somewhere I have never been, the One X completely froze on me Did a hard reset by holding the power button down and then I powered the phone on again, the phone then started up straight in the the bootloader, before that that the HTC logo appeared with some red writing stating it was in dev mode..weird? (I've rooted phones before an never seen this).
- In the bootloader I tried factory reset and entering recovery they all just brought me back to the bootloader menu
- Tried locating the RUU for my software version in the hope I could just reflash that, couldn't find it anywhere
- Battery got way low so ran a battery script to continually reboot the phone, works well and gets me to 10%
- Thought I could try and get a custom recovery on the phone no such luck because ...
- Bootlaoder won't unlock, fasboot gives an error "Too many links" but I believe this is nothing to worry about. Phone reboots with "locked" and "security warning" at the top of the bootloader screen
- Now where do I go?
Any suggestions would be great, as far as I can tell I'm screwed unless I get that bootloader unlocked.
Keep up the great work guys.
H
I give up, I think I'm going to have to ring the insurance company, no matter how many times I try to unlock the bootloader I get nowhere.
did anyone get anywhere with this problem?
hybridised said:
I give up, I think I'm going to have to ring the insurance company, no matter how many times I try to unlock the bootloader I get nowhere.
Click to expand...
Click to collapse
did u get anywhere with this?
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON. The device had never been Rooted or tampered with previously.
So now the phone does not boot at all. I've tried every button combination, but nothing seems to work. If I plug in the phone to charge the orange light flashes, endlessly. Even after I've left the device to charge for 6hours, the orange light still flashes.
When I plug in the phone to my PC, all I get it seems is this new device: QHSUSB_BULK, which shows with an exclamation mark next to it. I've read similar threads for different phones where they've unbricked devices while they were in this mode, is that even possible? I can hear Windows recognizing a device was plugged in, and if I press Power+VolumeUP, it will disconnect the phone and reconnect it, at least based on the sounds Windows is playing. The screen is Black at all times.
How badly have I bricked this device and is there any hope to revive it? Thanks to everyone who chimes in on this.
arrayy said:
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON.
Click to expand...
Click to collapse
Most likely it's a soft break. So you can fix it. First of all get yourself a working usb cable. Your's maybe broken.
Your phone's data partition had been encrypted. It never boots up completely without lux password. You could've format the data partition with a custom recovery such as TWRP. Instead you tried the reflash firmware but obviously it didn't finish and failed. All you need is reflash again but doing it correct way so it can finish. Your old data is gone atm. You will have factory reset phone at the end. Before giving you any instructions, you need to answer a few questions so anyone can help.
Have you ever updated your phone to marshmallow which is android 6? If no: You can recover it with voidzero's wonderful answer titled back to stock. Follow that exactly. If yes you can't flash old versions since they are using different bootloaders. Also you will have to reflash it manually. It's long and difficult for anyone who is new. If you don't know if it was updated. Just boot into bootloader then Fastboot mode, connect usb. Then use htc's Fastboot. Run htc_fastboot getvar all command. Paste output here.
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader using the Power+VolumeUP keys, or any other combination.
Instead of flashing the RUU, or maybe turning to S-OFF(I still don't know if this would've made a difference), I flashed a firmware, one that matched my version. This is the exact filename: 0PKVIM[email protected]60201_20.05_018_F_release_479349_combined_signed
I've renamed it to 0PKVIMG.zip and booted using the Power+VolumeUP keys. For whatever reason, everything went OK, no errors whatsoever. In the end it told me to press Power to reboot the phone. I've pressed Power and nothing happened since.
If anyone can help me figure this out, I'd be forever grateful.
arrayy said:
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader
Click to expand...
Click to collapse
That is a big problem. I assume you never tried to go S-OFF (which is dangereous). While phone was S-ON. You could always boot into bootloader. That's one of the purpose of staying S-ON.
Combination is Power + Volume down. But if your phone is up & somehow can not continue to boot. eg: stuck at reading system or kernel etc. You can do a hard reset which is pressing Volume up + volume down + power for at least 15 seconds. phone will shut down. then you can try bootlader combination. Make sure it's has power on with light at screen edges you must look at carefully. After trying this if you still can not see bootloader. That's a problem beyond my experiences, so I don't have any idea to fix it.
I have never tried the firmware you have used. Maybe that firmware is not usable, broken or even dangerous.
We need to confirm that here. if anyone else tried and brick their phone with that.
My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
pamack said:
My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
Click to expand...
Click to collapse
You didn't relock the bootloader did you? After unlocking it?
Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
pamack said:
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Click to expand...
Click to collapse
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
pamack said:
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
Click to expand...
Click to collapse
Still probably worth flashing via adb to check?
mikefnz said:
Still probably worth flashing via adb to check?
Click to expand...
Click to collapse
He means fastboot.