Had simple rooted stock stuff, then decided to unroot it just because I didn't get much benefit from it, and tried to flash an unrooted stock ROM, and now it's only booting into the HTC error screen with 4 caution corner arrows. I've heard that I may have to use a RUU .exe, but whenever i attempt to use one, I either get a USB Connection Error, or it says halfway through preparing itself that the download may be corrupted and to redownload, which I've done many times.
Any ideas?
Also, when I unplug it when it's on the htc error screen, it brings up the white recovery screen. It says:
Supersonic EVT3 SHIP S-OFF
HBOOT-2.10.0001
and the only option to select is "RUU," and pressing that does nothing.
EDIT:
The Error I get when it gets to about 75% is "ERROR [110]: FILE OPEN ERROR
The ROM Update Utility cannot open the requested files or the files are damaged. The RUU cannot continue with the update. Please get a complete RUU package and try again." It gets through updating the HBOOT, RADIO, etc, so I have noo idea what the issue could be.
Where have you gotten this RUU? If you can, go download it from an official download because it might be a bad download you are using.
b-felt said:
Had simple rooted stock stuff, then decided to unroot it just because I didn't get much benefit from it, and tried to flash an unrooted stock ROM, and now it's only booting into the HTC error screen with 4 caution corner arrows. I've heard that I may have to use a RUU .exe, but whenever i attempt to use one, I either get a USB Connection Error, or it says halfway through preparing itself that the download may be corrupted and to redownload, which I've done many times.
Any ideas?
Also, when I unplug it when it's on the htc error screen, it brings up the white recovery screen. It says:
Supersonic EVT3 SHIP S-OFF
HBOOT-2.10.0001
and the only option to select is "RUU," and pressing that does nothing.
EDIT:
The Error I get when it gets to about 75% is "ERROR [110]: FILE OPEN ERROR
The ROM Update Utility cannot open the requested files or the files are damaged. The RUU cannot continue with the update. Please get a complete RUU package and try again." It gets through updating the HBOOT, RADIO, etc, so I have noo idea what the issue could be.
Click to expand...
Click to collapse
It is your decision but you could just leave it rooted stock and go on. that will not hurt your phone and it will be the same IMO to just unrooting it. At least you can delete apps you do not want.
Ok lets see, since you still have S-Off I would flash a recovery from here
Then flash Sprint Lovers Rom from here and you will be stock with the ability to at least delete apps if needed. I know you don't see a benefit but believe me there are quite a few and this way incase you change your mind in the future it will be ok..
I think you are ok with the S-off right now but you just need to flash a recovery of your choice. If you need any more help PM me
UNROOTING OPTIONS
Edit: Actually here is one stop shopping website - It has it all right here
Other option is here
Have you tried flashing a PC36IMG of the RUU through hboot? You're still s-off, so if you can flash through the bootloader then you have more options. Try that first, hopefully it will work.
Sent from my PC36100 using Tapatalk
Related
Hello,
I need major assistance, I have been running third party roms on my phone for a while as well as S-Off (alpharev's iso). My phone provider has recently released the OTA update so I was trying to go back it seemed to run fine but now when I boot my phone all I get is a short vibrate and the Alpharev splash screen then the phone reboots. I have tried to power up with the Vol- and power button and nothing happens, I have tried to use fastboot from the command line and all I get is Waiting for Device. I really need help please.
Devin
UPDATE:
I can now get into Android system recovery but when I try to apply a new rom it keeps saying "failed to verify whole-file signature" "signature verification failed". Does anyone have any ideas?
Have you tried installing a working RUU? That will get your phone back to working state and you can root it once again.
Note: Use the proper RUU. Flashing a AMOLED ruu will cause a display brick if you have a SLCD desire.
Edit: Also you cannot flash a custom rom from android system recovery. Only a .zip file that is signed by htc can be flashed I think. Search and download a htc rom and flash from recovery if the above mentioned method does not work.
careful while running the ruu on a s-off device. i had a s-off device and flashed a amoled ruu instead of a slcd one and ended up bricking my screen -- fixed it later though but it caused major panic. so, run the ruu only once you're very very sure.
secondly, each ruu extracts a rom.zip file when run in a temp directory. if your ruu doesn't work because it throws a hboot or a cid error, you can try searching and flashing for this rom.zip file from fastboot and it should ideally flash the stock rom -- since it is signed by htc. you will lose root though.
Thank you for your response, do you know of a way to extract an 'update.zip' from an RUU exe file? The latest RUU from my carrier has been posted and I can't run through the normal update process as it doesn't detect my phone.
put your phone in fastboot -- switch off phone. press back button+power and try running ruu again. Once it detects, search for rom.zip on your comp temp file location.
i don't know any other way unfortunately
Sorry if it seems like I'm being stupid.
I found the rom.zip, I tried renaming it to update.zip and it fails signature verification. So right now I'm sitting at a black screen with the picture of the phone and the triangle and when I type 'adb devices' into my terminal I get the S/N and Offline. Any assistance would be great, I'm doing this on OS X if it makes a difference.
You need to rename it PB99IMG.zip as it needs to be found when you first turn the phone on in HBOOT. Any 2.2-based RUU will be fine on an SLCD screen
Obviously flashing a ROM this way will reset the phone back to stock and delete ALL data
I renamed the file, it worked!! I Have a functional phone!!
Thanks so much to everyone who helped me out in the this thread. I love this community so much.
may i ask how you got into recovery? because it looks looks like i have the same problem.
dragonithe said:
may i ask how you got into recovery? because it looks looks like i have the same problem.
Click to expand...
Click to collapse
switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery.
What I did power on the phone holding the back and power buttons until the menu opened.
hi can you please have a look on this as well
http://forum.xda-developers.com/showthread.php?p=9097558#post9097558
Regards
hey i am at exactly where your problem was
i tried to update telus 2.2 OTA and i've bricked it
now i actually don't know which rom.zip to use what did you use?
since we are from the same service
i tried a wrong rom.zip and it said wrong modal ID
SOOO CLOSE PLEASE HELP ASAP
SPENT ALL DAY LOOKING FOR A SOLUTION
Here is the link to my dropbox with the PB99IMG.zip for Stock Telus Froyo rom I used to fix the problem.
PB99IMG.zip
I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
LaloHigh said:
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
Click to expand...
Click to collapse
What do you mean record what software I started with? I had 2.02, now have 0.76 (But my screen says 2.10). I've tried both the exe and the PC36IMG.zip that you've linked.
Using .exe gives me a Error 170 (Not recognizing my phone is plugged in)
Putting PC36IMG.zip on sd and using hboot gives me Failed-PU, Partition Update Fail! for every category but Radio_V2. BTW I'm supposed to use the first two files from that link
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Greenfieldan said:
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
Click to expand...
Click to collapse
Well what I did was messup the way it sees my partition. I have a nwer partition scheme i believe but the 0.76 software thinks I have the older partition settup.
If you mean unroot method from this post http://forum.xda-developers.com/showthread.php?t=829045 the one I rooted with then I can't do it cause I have no recovery. I can't get to it cause bad partition settup.
I know I can run fastboot erase commands, do you guys think I should run
Code:
fastboot erase boot
to create an unbootable system. One that doesn't even have the screen turn on?
*Which if any partition can I delete in order to never have the phone even turn the screen on?
Here's the choices (wimax, misc, recovery, boot, system, cache, userdata)
if your getting error 170, the RUU can't communicate with the phone.\
Can you get Hboot USb on? IF so, the RUU may run with it.
Drivers installed on computer?
Otherwise, you mave have blown out USB port, like I did.
Try putting the RUU, rom.zip (rename rom.zip to PC36IMG.zip) to your sd card, and see if that saves your a$$.
If that don't work, better run it over with a car or something and take it back.
The good news is you are still in your 30 day warranty. The solution I would suggest is try to flash the bootloader back to hboot 2.10. I would find a pc36 with 2.10 and flash away. Maybe even fastboot erase every partition except boot and hboot first. Don't do radio or wimax either or it will brick your radio and wimax. Then flash a full pc36. Other than that, manually brick. I would erase hboot and boot to brick.
Good luck
If you erase boot.img, it will still go to hboot. Erase the touchpanel image. That way they cant see it. By the time your phone gets to its repair destination, "they" wont be looking for that type of thing. They will just repartition. Also, it wont let you erase hboot
What error are you seeing when you select recovery from the bootloader menu?
The RUU that you tried, what version was it? You MUST use the 3.70.651.1 RUU because your phone thinks you are on hboot 2.10. Do not try an older RUU.
--------------------------------
Try the following
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
4) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
-----------------------------------------------
If that does not work then try the following:
1) Download the img file for the modified Amon_Ra Recovery
2) Put evo-test.img on the root of your sdcard
3) Put the phone in fastboot mode
4) fastboot boot evo-test.img
5) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
josh4trunks said:
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
Click to expand...
Click to collapse
But if you can't flash a RUU.exe, then you can probably flash a zip file of a ROM.
This can or be or is not correct, I am just curious how this well happened to you.
nope tried flashing ROM through hboot, fastboot... Tried 'fastboot erase boot' didn't do anything. I'm gonna update the OP on the current situation, giving up...
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
i think he said multiple times that he was totally screwed and his partitions were messed up so he either needs a total memory reflash or god's private java code
illogos said:
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
Click to expand...
Click to collapse
Can't flash through bootloader. Get Fail-PU
Which is a Partition Update Error
Hey guys,
I had a friend root my phone and wanted to unroot it, I wasnt sure how to do it so i stupidly did stuff without reading first.
I am running unrevoked it seems and i went into recovery and did a factory reset. Well my phone still wouldnt accept the OTA update so i went back into recovery and deleted data and a few other options. Well i have been reading and been trying to reflash my phone back so i can use it again. Well i dont have an OS anymore it seems so the only thing my phone does is go to the bootloader. ( white screen with options Fastboot, Recovery, ect. )
I downloaded an image file and the bootloader checked it and said Main version older and failed to install. So i did more reading and flashed the unrevoked zip again and tried again. didnt work, so i have been downloading every image i can find tring to get it to install and it never does. It says i am missing file PC36diag.zip and PC36diag.nbh or NBH file is not correct. It then unpacks the img file i have on there then checks it, then nothing happens ( that is with the other image files i dled not the original ) And when i say nothing happens i mean it says checking, then just goes back to the bootloader screen. I dont know what to do. Any help?
Did you try Z4 mod to un-root?
No,
This link is the method i was using to unroot
http://forum.xda-developers.com/showthread.php?t=780141
Kethron said:
Hey guys,
I had a friend root my phone and wanted to unroot it, I wasnt sure how to do it so i stupidly did stuff without reading first.
I am running unrevoked it seems and i went into recovery and did a factory reset. Well my phone still wouldnt accept the OTA update so i went back into recovery and deleted data and a few other options. Well i have been reading and been trying to reflash my phone back so i can use it again. Well i dont have an OS anymore it seems so the only thing my phone does is go to the bootloader. ( white screen with options Fastboot, Recovery, ect. )
I downloaded an image file and the bootloader checked it and said Main version older and failed to install. So i did more reading and flashed the unrevoked zip again and tried again. didnt work, so i have been downloading every image i can find tring to get it to install and it never does. It says i am missing file PC36diag.zip and PC36diag.nbh or NBH file is not correct. It then unpacks the img file i have on there then checks it, then nothing happens ( that is with the other image files i dled not the original ) And when i say nothing happens i mean it says checking, then just goes back to the bootloader screen. I dont know what to do. Any help?
Click to expand...
Click to collapse
Have you tried running the RUU yet? I would give that a try. Also, I believe that when you get the 'main version older' error, it has something to do with what version hboot you have on your phone. There are many different PC36IMG.zips and many different RUU's. I believe you need to find the correct one for your phone. I would try the RUU first though, and see if you can get your phone back up that way. You run the RUU from your computer, and have the phone plugged in via USB. I will provide a couple links, one that contains every RUU and PC36IMG (all software versions), and another that has a bunch of factory ROMS. Hope it works for ya.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
You've got good advise on the RUU. I already did it to bring my Evo into a store to be looked at.
In the Evo Development thread you'll find one or more posts with links to the Evo RUU files. If you have a 002 or 003 hardware version Evo, download the 3.29.x version RUU; if you have an 004 you can get the latest 3.70.x file.
Connect your Evo to your PC via the USB cable, run the RUU file on your PC, and befor eyou know it, you've got an unrooted, completely stock Evo. Add your info again, run the OTA updater to get you back to the latest version, and enjoy your stock Evo.
I hope this helps. Thank you for your time.
This is really starting to look like a megaupload advertisement
I'm having trouble unrooting my evo and have to ship it back in 4 days. I,ve tryed the unrevoked s-on and it worked but reflash pc36img didn't take tried 3 or 4. going to try this but what do I do to phone to connect? disk drive?
i was also having this problem yesterday but i did it. i rooted using the autoroot program. i unroot using the ruu . heres what i did first download htc sync for your evo then plug in your phone to the pc. turn off your phone. turn it on to the bootloader . leave it there dont do anything else. then run ruu , if you get an error message keep on trying it . also google for the ruu program. hope this help
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, 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.