Hi!
I probably did something I shouldn't and now I need help after 4 hours of searching the all so big internet.
What I did: I used the AAHK mod to try and root my Desire HD, everything went fine and it found an exploit and I saw it flash something onto the phone. After it was done, it said that the radio was now done. Please wait. So I waited for 45 min, and nothing happend. Rebooted the phone and it wont get passed the white HTC startup picture. I can still hold the vol down and get into boot.
What I've tried: I have tried the recovery option on the bootmenu, and all that gives me is a black screen with a red triangle. After that I tried communicating with the device through fastboot, and thats the only program that seemes to find it. I cant use the aahk tool again, since it says the phone is disconnected, nor any other tool I've found to flash/recover. I have also tried to flash recovery (command) to try and install CWM, but that gives me a FAILED (remote: signature verify fail).
I have now found a stock rom, wich I will try and put onto the SD card. Name it PD98IMG.zip and see if a miracle happens. Cause I see it searching for that name with intervals while I'm in the bootloader menu.
I am now at my wits end, any help would be greatly appreciated.
Download recovery, then flash through fastboot commander search in xda
The stock ROM should work I think.
Hi, flashing the stock rom actually worked!
I downloaded a stock 1.32 rom, put it on the root of my SDCARD and flashed it once I got into the bootloader.
Saved my day
Thanks for the replies though
Hi all,
I got a notification this morning about an OTA on my Vodafone UK One X, I have unlocked it already though, so the OTA refuses to install as per previous OTAs.
Like the previous OTA, I opened the zip (OTA_ENDEAVOR_U_ICS_40_S_Vodafone_UK_2.17.161.4-1.29.161.13_release_280431g20qld0c8sg0f1qb.zip) and modified the META-INF\com\google\android\updater-script to remove the cid check, copied the zip to the device, rebooted into CWM v5.8.4.0, disabled signature verification, flashed the zip.
All went well, progressed as normal patching the system, no errors displayed.
The device now boots all the way to my Android home screen with screen saver etc, but then immediately reboots as if it thinks part of the update is still pending. Any ideas what I can do to get out of the boot loops? I remember something like this from the last flash.
Thanks!
http://forum.xda-developers.com/showthread.php?t=1832900
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom
May help ?
Aidey68 said:
http://forum.xda-developers.com/showthread.php?t=1832900
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom
May help ?
Click to expand...
Click to collapse
Thanks, useful to know I have a few things to try before putting a stock recovery back and factory ruu.
I'll give them a try tonight, cheers!
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 developers,
I have just today gotten my M8 HTC One S-Off'd, and went ahead with google play edition conversion. It went well, but I missed some sense features. So I tried to follow the tutorial on how to get back to sense, but after rebooting to bootloader - and flashing the 54meg firmware thru fastboot - didn't notice to flash custom recovery. Phone is not booting (bootloop after first logo screen), and recover is a stock one. Now I have tried flashing some random RUUs I found on graffixnyc's website, but the stock recovery says "Finding update package", then "Opening", then "verifying" and then returns with error - exclamation mark in red, and "Installation aborted" message.
I have no connectivity thru fastboot or adb, just this recovery.
Is there any help, or is the device bricked for good? Supercid (11111111), S-off and unlocked bootloader.
Also, seems like I cannot enter HBOOT in any way - holding button up or down... just the recovery.
Best regards
Mike
EDIT: When I downloaded OTA 5.0.1 update from graffixnyc's website, the Verification didn't abort at the beginning, in fact it threw quite different error messages:
"Package expects buld fingerprint of htc/m8_google/htc_m8:4.4.4/KTU84P.H1/356549 (...) or 5.0.1, this device has htc_wurope/htc_m8:4.4.2/KOT49H" and then installation aborted. So I need another OTA package???
EDIT: Somehow I managed to enter FASTBOOT, just holding vol- and power between reboots and it worked finally. Now I'll flash twrp and hopefully it'll go better after that. Don't know what firmware to flash then though to have sense6 and 5.0.1.
Did you make a note of the software version you were on before you flashed the GPe? It would've been helpful to know for recovery purposes. It'd also have helped in case there was an RUU available to make the process easier
hello friends.
I'm in a pckle with my M9...
i was attempting to take an OTA update after reloading backup of my stock read-only TWRP recovery.. it was S-OFF, and UNLOCKED.. i decided to OEM relock and tried again.. nope it still said i had an altered system and couldnt upgrade.. so i tried an RUU .exe file... same thing... i tried an RUU from SDcard (.zip)... i saw a bunch of lines whizz by it was quick but i saw stuff like %0-SKIPPED for many lines.... now it only boots to fastboot mode, and i can get it to download mode if i try 2-4 times...
i've tried loading other RUUs .exe and .zips.. the .exe claims my battery is below %30 and quits... the zips also fail.. i have a video of the latest fail.
i've reflashed the recovery with TWRP and with the stock and i just cant get to recovery...
it wouldnt take the update like it did with this same recovery once before... now things are really messed up...
let me know what other info you need and i'll try to get it up here
THNX in advance for your help
pictures and video
https:// www. youtube.com/ watch?v=Ppoh8_x26eY
i managed to get a stock recovery onto it, but it gives me all sorts of header and signature verification errors... i have more photos you can see that my CID is blank....
pretty sure i must have made a firmware F-UP.. i was on a rooted stock dev rom and used a TWRP back up of my rogers on that dev firmware... im pretty sure that was 1 of many screw ups i did to get this far... anyways it turns on and has a battery charging icon when its off. it now has a stock recovery and is still S-OFF but before i tried to et that stupid OTA update by flashing a sour RUU i had locked my boot loader hoping that would show my device as unaltered.... STUPID i know... im open to any more advice before i aks HTC if i can pay them to fix it
gonna give up and go find a sim adapter for my M7... crappy speaker and all... at least its working right now...