After trying to upgrade my unlocked phone to another ROM, I got into a bootloop.
But that's not the problem.
I tried to troubleshoot it and restore using CWM but I kept getting MD5 errors.
I ended up relocking my phone and now I cannot access CWM. AT ALL.
I tried getting a PrimoC Virgin Mobile RUU, but it fails with error 132 (signature error).
Currently when I turn on my phone I go straight to the bootloader. My phone is relocked. I cannot access CWM. RUU does not seem to work. All I got going for me is that my phone still turns on. What can I do guys? I really would like this phone to work again. I need help desperately as I need to be able to use this phone to text my friends and girlfriend.
go to bootloader then unlock it with a same way as you did before (hope u didn't deleted your unlock_code.bin)
flash the CWM again then try to go into recovery
mostly it should work
Related
I have serious problems with my phone that I could really use some help with as at the moment I'm completely screwed - I've already spent hours reading forums but have yet to find advice that will help. Here's whats happened:
I have an A8181 HTC Desire, and I took an OTA update yesterday that bricked my wifi. At this point I thought it would be easiest to root my phone, and after checking that my hboot version was 0.93, I read advice that said to downgrade this to 0.83, which I duly did.
Now, my phone is stuck in a bootloader loop - I get the 3 androids on skatebooards with FASTBOOT in red, and I can choose from:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I select bootloader I then get:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I can access recovery and apply update.zip roms successfully (I've only tried official HTC 2.2 roms as the phone isnt rooted), but after doing so it just goes back to the bootloader loop.
If I select FASTBOOT then I'm just back at the first screen.
I've tried clearing cache and factory reset aswell, but I still can't get past this 2 screen loop.
It's like the bootloader just can't load whatever rom is installed.
Because the phone isn't booting up, I can't use adb or any other pc tools as the device is not detected on my pc - although it does show up in device manager on windows.
I'm close to sending this back to try a warrantly claim, although I'm worried that by trying to fix this I may have invalidated this.
I'd really appreciate any help or advice as to how I can get out of this and get my stock 2.2 back.
Cheers
If your computer using windows, have you installed hboot drivers?
If you have those installed your pc should detect the phone.
unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
You shouldn't have had to downgrade your bootloader. If you can, go back to the newer.
The wifi issue, was widespread on desires, I had it also after a "pushed" update from HTC (european model, unlocked). I downloaded a stock 2.29 froyo. Had to make a gold card also. Took several tries, wipe cache, but eventually successful.
Then, I rooted, and went to CyanogenMod7 rom with clockwork recovery.
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
Hi, I've just bought a HTC One M8 from craigslist and I have a problem or two. The phone cannot connect to google servers, but the posts I found to fix that didn't help (delete hosts, install gmail). The main problem is I can't get it back to stock to get the new firmware (it's on 4.4.3), which I thought may cure my problems.
The phone is on Venom ROM, carrier is T-Mobile USA, tampered and unlocked flags showing, S-On
Here's what happens when I try to flash a recovery image:
adt and fastboot do exactly what they are supposed to do, but when I hit "Recovery" on the phone it says 'entering recovery', then just boots up as normal. I never get to TWRP. If I use CWM, it says 'entering recovery', then goes back to fastboot.
For some reason, the phone is taking a good 60 seconds to boot up each time.
I have tried to go to S-Off, but I got the Firewater message:
*** whelp, this sucks, firewater can not work on your device *** (etc.)
Can you tell me how to get communication to Google working again, or how to upgrade the firmware?
Thanks for your help, I am new to this, and running out of ideas
Alex
I would say use fastboot to install TWRP and try again. Or use fastboot to install the stock bootloader and then try to flash an RUU. Google around this forum for instructions.
like FreydNot said, I'd try downloading and fastbooting the latest TWRP onto the phone. power it down and let it chill for a minute and then try to get into the recovery.
So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.
You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.
Yeah that's what I did yesterday thanks for the response!
Hey there,
I have an HTC One M9 on Bell Mobility in Canada
I've completely messed up my phone trying to install an update for the new CM13 that wasn't working, but basically where I am now is that my phone can boot into download mode and bootloader mode no problem, but in the process of trying to fix it, some how my TWRP Recovery mode got wrecked. If i got to bootloader to reboot into recovery i get the message, "Failed to boot into recovery mode, press volume up or down to back to menu".
Now, I was going to try and mess around and try to flash back a recovery img that has twrp that can atleast get me somewhere, but now my phone wont even be recognized by ADB on a machine that was working for it last night, idk if it is because I cant get into recovery or what.
I've heard of people putting an RUU on their SD Card, which I have, then putting it in the phone with it renamed to something specific then it'll flash for them in download mode, but I don't know where to begin for that, especially trying to find one for Bell.
If anyone could give me any help it would be greatly appreciated.
XYandZe_ said:
Hey there,
I have an HTC One M9 on Bell Mobility in Canada
I've completely messed up my phone trying to install an update for the new CM13 that wasn't working, but basically where I am now is that my phone can boot into download mode and bootloader mode no problem, but in the process of trying to fix it, some how my TWRP Recovery mode got wrecked. If i got to bootloader to reboot into recovery i get the message, "Failed to boot into recovery mode, press volume up or down to back to menu".
Now, I was going to try and mess around and try to flash back a recovery img that has twrp that can atleast get me somewhere, but now my phone wont even be recognized by ADB on a machine that was working for it last night, idk if it is because I cant get into recovery or what.
I've heard of people putting an RUU on their SD Card, which I have, then putting it in the phone with it renamed to something specific then it'll flash for them in download mode, but I don't know where to begin for that, especially trying to find one for Bell.
If anyone could give me any help it would be greatly appreciated.
Click to expand...
Click to collapse
Regarding the computer recognizing your phone - do you have HTC Sync Manager installed? That usually solves all my problems for drivers on a Windows computer. This might be necessary because you're connecting your phone while in bootloader or downloader mode.
A great place for learning to use and obtaining RUU files for the sd card method is Flippy498's Back-to-Stock spreadsheet.
It looks like the Bell Mobility variant of the M9 uses the WWE software, so you've got RUUs available.