Hi
I recently purchased a second hand htc desire locked on Orange UK.
The phone seemed to be running fine (not 100% sure though) at the beginning. The first thing I did was to unlock the phone, by using the method posted on the giffgaff site.
Everything seemed to be running fine at the beginning, but after a while the phone started rebooting randomly. It escalated to the point to where it would not go past the HTC logo, and just went into a reboot circle. The only thing that helps in this situation is taking out the battery for a couple of minutes and than it would boot up.
I figured it was a software issue, so I tried installing a custom ROM. It took a while but I managed to ROOT the device and install the CyanogenMod 7 (latest). The installation was successful but unfortunately the reboot issue hasn't changed at all.
I would have wanted to reverse the unlocking procedure that I did at the beginning, but there's nothing about how to do it.
The other possible solution I found, is to do a RUU. I wasn't able to find a ROM made for Orange UK version, so I went with RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865.exe figuring that that is the generic one for EU. The problem is that from what I can tell Cyanogen doesn't have HTC Sync mode for USB connectivity, and when I try to do it without it gives me an USB connection error. I checked and from what I can tell I have the drivers installed for it.
I'm stuck at this point so any help would be greatly appreciated.
P.S.: I also made a gold card for the phone but I'm not sure what I'm supposed to do with it.
-edit-
I also noticed that it tends to reboot especially when I try to enter recovery mode
-edit2-
In all fairness I never managed to access recovery mode from the HBOOT menu. It always took me to the HTC Logo, and then went into a reboot cycle. The way that I managed to access the Recovery mode was either through rom manager or direct recovery reboot from cyanogenmod
Have a look in bortak's troubleshooting guide and follow instruction which applies to your problem
Is it PVT1 model? Check hboot/fastboot screen
Sent from my Sensation XE with Beats Audio Z715e
I'll try to keep my post short since a full summary would take forever.
I rooted my HTC One X about a week ago and installed a nightly of CyanogenMod 10. It was fun for a while but I started to notice the ROM was unstable, causing issues with battery life and freezing. So I wiped it and tried to do a restore to the backup I made just after rooting. But it didn't work. I ended up stuck in a bootloop and panicked. So I went to the same guy that showed me how to root my phone and found a video from him on how to UNROOT/UNBRICK it to get it working again. Also: had to edit out the links to the videos I used because I have less than ten posts. But his videos are stamped with AndroidRoot.
I got my bootloader relocked with no problem. But whenever I tried to use the RUU file he gave me to get HTC back on there it wouldn't work. I spent hours trying everything I could think of. I kept getting Error 155 and it would get stuck on 'Sending' and never get past it. So now I have a phone with a locked bootloader, no OS/interface, no Recovery, or anything of any kind, just my fastboot screen.
So then I gave up on the RUU (and it's the right one last I checked but maybe I'm wrong here) and decided I would just try to reroot it and find a stable ROM. Anything to get it working again. But now I can't get my bootloader unlocked. I'm following the same video as last time, and using the same unlock token that I had and everything. But it keeps failing to send the unlock token, or else it just gets stuck on 'Sending Unlock Token' in the command prompt.
Please help me I miss my phone.
EDIT: Now, after trying to use my unlock token, the RUU isn't working at all. It gets stuck on 'Verifying Android information'. But my bootloader still says it's been relocked.
If you can get into fastboot this should be recoverable. There is a guide to updating at http://forum.xda-developers.com/showpost.php?p=37777135&postcount=5141 HBOOT that has some useful information. In particular, did you use the right RUU for your CID?
You also need to get the right kernel for the ROM you are installing. Because the HOX is an S-ON device you can only flash the kernel from fastboot mode. The ROM is flashed from recovery mode. All very confusing.
Solirus said:
I'll try to keep my post short since a full summary would take forever.
I rooted my HTC One X about a week ago and installed a nightly of CyanogenMod 10. It was fun for a while but I started to notice the ROM was unstable, causing issues with battery life and freezing. So I wiped it and tried to do a restore to the backup I made just after rooting. But it didn't work. I ended up stuck in a bootloop and panicked. So I went to the same guy that showed me how to root my phone and found a video from him on how to UNROOT/UNBRICK it to get it working again. Also: had to edit out the links to the videos I used because I have less than ten posts. But his videos are stamped with AndroidRoot.
I got my bootloader relocked with no problem. But whenever I tried to use the RUU file he gave me to get HTC back on there it wouldn't work. I spent hours trying everything I could think of. I kept getting Error 155 and it would get stuck on 'Sending' and never get past it. So now I have a phone with a locked bootloader, no OS/interface, no Recovery, or anything of any kind, just my fastboot screen.
So then I gave up on the RUU (and it's the right one last I checked but maybe I'm wrong here) and decided I would just try to reroot it and find a stable ROM. Anything to get it working again. But now I can't get my bootloader unlocked. I'm following the same video as last time, and using the same unlock token that I had and everything. But it keeps failing to send the unlock token, or else it just gets stuck on 'Sending Unlock Token' in the command prompt.
Please help me I miss my phone.
EDIT: Now, after trying to use my unlock token, the RUU isn't working at all. It gets stuck on 'Verifying Android information'. But my bootloader still says it's been relocked.
Click to expand...
Click to collapse
First post here, please excuse my ignorance. This is a Virgin Mobile HTC One V. I never rooted a phone before, and was just trying to do a basic rooting, and somehow got into trouble. I would like to return the phone to stock and start over.
Right now the phone boots itself into bootloader, and shows me this:
Relocked
Security warning
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
I am able to do this: fastboot getvar cid. The response is this: cid: SPCS_002.
I am also able to do this: fastboot devices. The response is this: FA2AKX405758 fastboot.
I have attempted to use this RUU:
RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
It gives me error 170, USB connection error (even though I have installed the HTC drivers). I relocked the phone in an attempt to get that RUU to work, but it didn't help. I also tried to extract the rom.zip from the RUU.exe (by finding it in a temp folder, as described on another XDA thread), but the rom.zip acts corrupt. Various zip programs refuse to open it.
Before relocking the phone (in an attempt to get the RUU to work) I tried this:
fastboot flash boot boot.img
I did that with various boot.img files I found via threads here. This just created various problems. One result was that I was in a bootloop. Another result was that I booted to the screen that said "this build is for development purposes only do not distribute outside of htc without written permission." And it would hang there.
Now my condition is that I boot directly to bootloader.
Starting from the beginning: I unlocked the phone using the unlock bootloader procedure at htcdev. No problem. Then I figured I should do a backup right away, so I installed CM Recovery. Right away I knew I had a problem because it did not run correctly. It would present a menu. Then I would select "backup and restore." It would present a splash screen (with the hat) and just hang there. When I pressed power, it would return to the menu. That's when I started trying various other things.
I never got as far as doing anything with superboot or superuser, which is what I thought I was going to do after doing the backup.
I have read a zillion threads here, and tried various things from those threads, but I'm afraid that without specific help I'm just going to make it worse. I'm pulling my hair out, so I hope someone here can help me while I still have a few left. Thanks!
OK, I have made some progress but I'm still pretty stuck.
I have been able to solve two problems I had before. Before when I ran the RUU, it gave me a USB error. And I could not extract recovery.img from the RUU. I solved both those problems by moving to a different PC.
So now I can run the RUU, and it gives me a bunch of progress messages I didn't see before, but at the end it tells me this:
"Error 155, unknown error. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
So then I tried the procedure described here:
http://forum.xda-developers.com/showpost.php?p=27301573
I unlocked the phone again, and I did this:
fastboot flash recovery recovery_signed.img
I did that using the img file I extracted from the RUU. Then I relocked the bootloader, and I ran the RUU again. But it gave me the exact same error (155).
What should I try next? I notice that the RUU also contains these img files:
system.img
radio.img
boot_signed.img
Should I try flashing those?
Any ideas would be greatly appreciated!
Edit: One more thing. When I ran the RUU, at the end the phone said this:
RUU
Hboot version is older!
Update Fail!
OK, the next thing I tried is the method described here:
http://forum.xda-developers.com/showthread.php?t=1674226
I extracted rom.zip from the RUU, and I renamed it PK76IMG.zip, and I put it on the sdcard, and then I rebooted the phone. The phone found that file and tried to install it, but in the end it gave me the same error message: "Hboot Version is older." On that same screen I see that my current Hboot is 1.57.0000. I guess the RUU contains an older Hboot?
Anyway, that's the same error I get when I run the RUU as an exe.
I notice a couple of people in that thread reported the same problem (Hboot is older), but it's not clear how or if they got around this.
Any ideas?
OK, so here's the next stage in this saga.
Looking around, it seems that there is no RUU for this phone, because I have Hboot 1.57.0000 and radio 1.00.00.0928. I have noticed that people with those specs cannot find a RUU that works, but they have been able to get the phone working with RhythmicRom. I see that discussed here:
http://forum.xda-developers.com/showthread.php?t=2147407
So what I'm trying to do now is install RhythmicRom, but I'm having trouble doing that, I guess because I don't have CM Recovery installed, so the standard recovery is running instead.
I have placed RhythmicRom_v1.4.zip on my sdcard. I am able to boot into bootloader, and I have done factory reset. In the bootloader, I can select Recovery and I see a screen that indicates the phone is looking for something (green circle containing green arrow pointing down, and with a progress bar at the bottom, and an icon of an sdcard). But I guess it doesn't find what it's looking for, and then I see the screen with the red triangle/exclamation mark.
I'm thinking that maybe it will work if on the sdcard I rename RhythmicRom_v1.4.zip to whatever the phone is looking for. Maybe I should rename it to PK76IMG.zip? Just a guess.
Many thanks in advance.
OK, that sort of almost worked. On the sdcard, I renamed RhythmicRom_v1.4.zip to PK76IMG.zip. I booted into bootloader, and it looked like the phone found that file, and loaded it. Then I did this:
fastboot flash boot boot.img
With the boot.img that was inside RhythmicRom_v1.4.zip. Then I rebooted. Now the phone gets to the red animated Virgin Mobile splash screen with the annoying audio. That seems like a good sign, since I haven't seen that in a while. But instead of continuing to boot, then I see the white HTC screen that says "this build is for development purposes only do not distribute outside of htc without written permission." And then it continues to loop between those two screens, so I am stuck in a bootloop. Although I found I was able to interrupt it and get back to the bootloader.
Not sure what to try next. Any suggestions?
Wow, I can't believe you haven't had a single reply.
Ok. First of all.... Use TeamWinRecoveryProject
( TWRP ) as your recovery img
So easy to use
Use fastboot the flash
fastboot flash recovery recovery.img
Then boot into your new touch screen recovery
Now click wipe
Cashe,Dalvick,Factory Reset, System
In that order. It makes sure every thing is wiped thoroughly.
Now navigate to where the Rom is you would like to use and flash it in recovery.
After It's flashed click the wipe cashe/dalvick
Then click home,reboot,bootloader.
Once in bootloader, flash the kernel/bootimg
fastboot flash boot boot.img
After the boot.img is finished,
fastboot reboot
Victory and enjoy the awesomeness of custom ROMs!
P.S. don't forget to unlock your bootloader again. First and foremost
fastboot flash unlocktoken Unlock_code.bin
Russell, thank you for your response. After 24 hours with over 100 views and zero replies, I figured that meant that I had already done the proper steps, and there wasn't some obvious solution I was missing. Although I can see now that I should have tried TWRP. It couldn't have made things worse, and maybe it would have worked better for me than CM Recovery (which seemed to fail as soon as I installed it).
Another key thing was when I figured out that there is no RUU for my specs (because there was an OTA that installed a newer hboot and radio). I like the idea of trying different custom ROMs, but I don't like the idea of never being able to go back to stock, since I would expect that all the custom ROMs have some quirks that I might find unacceptable. But I notice that you have the same hboot and radio, and I assume you have a backup of your stock ROM, so maybe you could have helped me with that.
Anyway, at literally the exact moment that you were posting your comment, I was standing at the UPS counter handing them the phone. If the phone had been working, we would have heard it buzzing inside the box as your email came in! The phone is heading to the HTC repair facility in Houston. They told me they would unbrick it for me for less than $35. I haven't seen anyone else report this, so maybe I was misled and it's too good to be true? We'll see. I don't like being without the phone for a week, but $35 seems like a cheap price to clean up the mess I made.
Anyway, thanks again for speaking up.
Check out the CDMA development thread
Whenever you get your phone back.....
Good luck
I see the thread you're talking about. I just did the download (might as well have it handy). Thank you.
Hope it helped or helps in some way
:beer:
---------- Post added at 02:40 AM ---------- Previous post was at 02:35 AM ----------
I gave you a thanks for first download
Similar problem
Hi,
I had a similar problem. Following this thread I have successfully "unbricked" my phone. My main concern though is activating my phone on VM, which I'm unable to do as I can't go back to stock. I bought the phone as is from craigslist. Any suggestions?
Edit: Internet seems to work though. No go on phone calls or texts, when trying to call this is what I get(Audio):"Account couldn't be verified"
Visit the HTC one v CDMA thread I have a stock rooted Rom there for the taking
Yes, here's the link to that thread:
http://forum.xda-developers.com/showthread.php?t=2321904
It would be interesting to hear if your rom works for cellphoneman.
Hi All,
I have a VZW Htc One M8, and I have been playing with it when have gotten the chance recently. I have installed/flashed an RUU before to correct an issue I ran into (trying to take an OTA) and everything went smoothly. As I said I took the OTA, but kept the RUU from the previous time I used it (first mistake). I am s off so I am hoping that is going to save me here.... This brings me to my problem.
I was trying to flash Viper Rom, but at the end of the setup I kept getting a popup saying setup has stopped, and I was unable to see a homescreen, but the phone was working. I decided to revert back to stock using the old RUU (be gentle) and it loaded and I hit yes to begin. About 10 second in it stopped and wanted me to reboot... I was in the middle of doing something else when it happened so I rebooted back to the bootloader and my OS line was in red. I then went back to recovery and restored my very recently created backup of my stock rom, which worked. I then went back to the boot loader to look at what was in red more closely and it is now blank. It says OS but then nothing after.
I have since gotten the new RUU that I should have used, but it seem to hang on the last part of the loading (put in on my external sd card) and my phone works... but the boot take forever and the VZW logo doesn't come up anymore. It almost seem like the phone boots fine but the HTC ONE logo stays until the phone screen turns off and when I hit the power button to turn the screen back on the phone is booted. My question is... should I 1) try the old RUU again and then take the ota since I am s off I have seen that technically it should work. 2) let the phone sit at the loading of the newer RUU and see what happens (I haven't tried seeing if the old RUU will load yet) or 3) count my blessings and deal with a non completely broken phone?
I realize I made a few errors while doing this, but I am hoping that s off will allow me to correct the problem. Any help would be greatly appreciated.
Issue should be resolved
Sorry to everyone that read this... I didn't make it all the way through the thread where I found the new RUU, and the thread tells how to resolve the problem with not loading all the way. I am going to try the fix after work.
Edit 1: problem resolved... I am an idiot
I bought an AT&T M8 on eBay a few months ago. My carrier is T-Mobile. Everything actually worked fairly well but there are a few nagging issues. No OTA updates, MMS doesn't work, etc.
I did some research on the forums here and elsewhere and the solution seemed to be flashing the phone to a stock T-Mobile firmware. Tonight I set out to do that.
I downloaded and paid for Sunshine. Installed with no issues.
I installed HTC Synch and ADB on my PC
I flashed CWM recovery onto the phone using fastboot. TWRP wouldn't work for some reason.
I used CWM to install SuperSU to root the phone.
I used fastboot to change the CID to T-MOB010.
I used scotty1223's instructions here to change the MID from 0P6B12000 to 0P6B13000.
There were some false steps along the way but I think everything worked fine to this point.
Next I used fastboot to flash the firmware I found here. At this point I don't even remember why I decided that was the right choice.
The firmware flash failed the first time but apparently that isn't uncommon. I ran it a second time and it seemed to succeed. I rebooted the phone using fastboot. When it comes up I see the HTC logo on a white background and I can still hear the AT&T "chimes" but I don't see the AT&T globe. And that's it. The phone won't finish booting. I can reboot into the fastboot menu but Recovery just gives me an red triangle with an exclamation point. ADB can't communicate with the phone anymore. So I feel like I'm stuck.
Any advice on what to do next?
AlphaJ23 said:
I bought an AT&T M8 on eBay a few months ago. My carrier is T-Mobile. Everything actually worked fairly well but there are a few nagging issues. No OTA updates, MMS doesn't work, etc.
I did some research on the forums here and elsewhere and the solution seemed to be flashing the phone to a stock T-Mobile firmware. Tonight I set out to do that.
I downloaded and paid for Sunshine. Installed with no issues.
I installed HTC Synch and ADB on my PC
I flashed CWM recovery onto the phone using fastboot. TWRP wouldn't work for some reason.
I used CWM to install SuperSU to root the phone.
I used fastboot to change the CID to T-MOB010.
I used scotty1223's instructions here to change the MID from 0P6B12000 to 0P6B13000.
There were some false steps along the way but I think everything worked fine to this point.
Next I used fastboot to flash the firmware I found here. At this point I don't even remember why I decided that was the right choice.
The firmware flash failed the first time but apparently that isn't uncommon. I ran it a second time and it seemed to succeed. I rebooted the phone using fastboot. When it comes up I see the HTC logo on a white background and I can still hear the AT&T "chimes" but I don't see the AT&T globe. And that's it. The phone won't finish booting. I can reboot into the fastboot menu but Recovery just gives me an red triangle with an exclamation point. ADB can't communicate with the phone anymore. So I feel like I'm stuck.
Any advice on what to do next?
Click to expand...
Click to collapse
check that your cid and mid are now correct for T-Mo by doing a fastboot get var all.
Firmware you flashed is fine.
your phone is stuck in a bootloop which isn't un-common, due to the rom version and firmware version mis-maych I expect.
red triangle is stock recovery, so that's also normal.
at this point, rather than trying to reboot the phone, you should of just booted back to the bootloader fastboot usb mode and run the T-mo RUU, the first thing the RUU does anyway is boot your phone to the bootloader anyway, your just manually doing the first part yourself.
Thanks a lot for the help. A couple of follow-up questions for you. Adb/fastboot can't connect to the phone now. I've tried at the HTC white screen and the bootloader fastboot screen. It just says '< waiting for device >'.
I'm also having a problem with the RUU. When I accept the license agreement on the install it seems to crash. No errors but nothing else happens and the process isn't running. I'm going to try that on a different machine and see what happens. Thanks again.
Another update. The RUU install works fine on a different machine. I think that was a Windows 8.1 issue. The problem now is that the RUU can't see the phone either. So I can't get a PC to see the phone over USB at all. I assume that's because of the bootloop. Is there anything I can do from the bootloader to fix this?
Some progress. The RUU finally found the phone. I guess that was a timing issue. Now it seems to be stuck at 'Updating.... (1/7) Sending....'. It's been doing that for over an hour.
Finally, success!! I found a Reddit thread about the RUU failure. It recommended finding the ROM.zip that gets dropped in a temp folder by the installer, renaming that to 0P6BIMG.zip, moving it to the sdcard, and rebooting. It worked like a charm. Fastboot found the zip automatically and prompted me to install it. It took a little while to update but now I have a stock T-Mobile HTC One.
please help
AlphaJ23 said:
Finally, success!! I found a Reddit thread about the RUU failure. It recommended finding the ROM.zip that gets dropped in a temp folder by the installer, renaming that to 0P6BIMG.zip, moving it to the sdcard, and rebooting. It worked like a charm. Fastboot found the zip automatically and prompted me to install it. It took a little while to update but now I have a stock T-Mobile HTC One.
Click to expand...
Click to collapse
my phone has exactly the same problem but i really dont know what to do from here