Hello everyone.
I own an HTC EVO V 4G, which I have come to understand is practically identical to the 3D.
I went ahead and did the simple(ish) bootloader unlock process through HTC Dev, and had my phone rooted for at least a year now, tried a few S-ON capable roms, the usual mild rooting stuff, etc etc....
Much more recently, I decided that some of these S-OFF roms make my Unsensible rom look pretty old, and tried out the whole Wire Trick method through unlimited IO.
After a solid 3 hours of staring at my laptop screen....
I rebooted into the bootloader with that glorious S-OFF overtop.
As you might understand... I was very eager to install one of those amazing roms, and downloaded and tried installing the PACman rom for the EVO 3D, admittedly (and regrettably!!) rushing a bit :/
So, after flashing and rebooting, I was stuck in a bootloop with PACman's boot screen. I tried rebooting back into recovery through bootloader (pull out battery, volume down + power, reboot into 4ext recovery) and wiping everything except SD-card, re-installing the ROM, with no success.
At that point I was frustrated enough, to the point where I ended up trying anything I thought might have the slightest chance of giving me my long-awaited rom.
I don't remember what I did exactly, but I flashed a few more files, actually modified the updater-script in the ROM zip.... :/
And now I'm stuck at that White n' Green HTC boot logo, it does not reboot, just stays on constantly, laughing at my hours of fruitless labor.
I can boot into the bootloader whenever with a battery pull, go into 4ext with no troubles.
I have a backup of stock rom, but after whatever I did... Everything I have tried gives me the same results.
I've spent literally the past 9 hours trying to fix this thing, stayed up all night because I need it for the day, and the next day, and the next day...
I tried using the RUU, but I have taken both OTA updates, and even when I finally did get it to start up and run, it denies me almost instantly...
Some device specifics:
I am using linux (Ubuntu).
I own an HTC EVO V 4G (shooter)
I used to run 4.0.4 stock ROM.
Switched to Unsensible (with no issues before S-OFF)
Using 4ext recovery.
Currently on JuopunutBear HBOOT-1.57.5757.
Radio is 1.09.00.0108.
Last ROM I tried flashing before giving up in fear of throwing my phone was PACman.
A few weird things... That scare me a bit...
I can put anything on my SD-card from Ubuntu fine through 4ext's USB function, but everything I do doesn't "stick"...
As in... I put a PG861IMG on the root, see it stay on the root in Ubuntu's file manager, but then boot into bootloader and it doesn't register that there is one.
This is just one example, any other files I transfer over don't take either.
I've been using another phone (I think it's an ancient EVO 4G (Not an EVO V 4G))
I us that one to hold the SD card, and things transfer fine on that one, so I don't think it's the SD card.
If anyone can give me a miracle reply that will save my whole life, you have no idea how appreciative I would be.
Thank you in advance to any replies and/or advice and/or suggestions, etc...
I'm not 100% sure where to put this explanation/plea for help, so... I put it here for one.
I apologise if there's somewhere It'd fit better.
Related
Hello all, I flashed thE Twisted Sence 1.5.1 ROM this afternoon and at about 8:30pm my phone completely froze and I could not do anything at all. Pulled the battery and all I can get is the HTC Logo on the White Background.
I can get into HBOOT and I have been trying everything I can to get the phone to work again but no dice.
Clockwork doesnt want to load for some reason but after letting my phone sit for about 15 minutes one time it did load into Clockwork. So I wiped the system partition/cache/dalvik and reloaded the ROM again.
After 12 minutes of waiting the phone finally started to load into the OS but it was so sloooooooowwwwww. It would not even recoginize any gestures on the touch screen.
So I rebooted again and it is stuck on the HTC Boot Screen again.
So I was thinking that I might be able to go back to the rooted stock so I went to http://forum.xda-developers.com/showthread.php?t=996616 and got the PG05IMG_stock.zip from there and renamed to PG05IMG.ZIP and had HBOOT load that.
Again went through a super long start up process and now the phone is at the unlock screen and again I cannot do anything at all. It has the correct time and it is only showing 1X for data nothing else and I am in a 4G LTE zone. I called myself from a landline and the phone rings but I cannot answer it since the touchscreen is un-responsive.
So is there any reason why my phone would be running super slow and doing what it is? I don't know if it is a Kernel thing or a Radio thing or what.
Maybe a stock kernel would help if anyone has it.
Any help would be much apperaicted as I have a brick that lights up basically. Phone isn't useable at all. =(
Reboot into recovery and try a different kernel. Or just restore an earlier state.
^_^_^'s tbolt
Load another ROM. Any rom you load should come with a new kernel. If that fails, try a different radio.
Sent from Phoenix, AZ running Thunderbolt rooted Das BAMF Remix 1.5
Does anyone know a way to go back to locked Stock through HBOOT or Clockwork without being able to boot the phone?
If I can get back to S-ON I will return the phone to Verizon since I am within my 30 days.
It has to be a kernel issue. The radio may be in conflict with something else, because all phones are different, but just restore a backup you've made, and try flashing the rom with a different kernel. If it was stable, something had to occur for that to change obviously.
If I had a backup to use then I would give that a shot. =( Shame on me I know.
webbyz said:
Does anyone know a way to go back to locked Stock through HBOOT or Clockwork without being able to boot the phone?
If I can get back to S-ON I will return the phone to Verizon since I am within my 30 days.
Click to expand...
Click to collapse
You can do it through ADB.
adb reboot recovery
now you know to make a nandroid backup prior to reflashing anything
/slaps OP with trout
After marathon attempts to read, get to know my Amaze, and to root, I can appear to flash either Speed Rom 6.0 or Energy_6.21.2012.Amaze.Sense.3.6; however, after installation the initial reboot begins a loop. For Speed Rom, reboot occurs after the 4 colored X is on the screen awhile, for Energy it occurs after the Beats Audio logo completes. I am overwhelmed. I use 4ext v1.00.5 RC3.
Here is what I think I have done, including a pic of the screen.
Unlocked, S-Off, HBoot-1.90.0008 (pic 1 attached)
I had to work my way through losing HBoot after the wire trick and got it back after a lot of reading.
Had "PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_228638_signed" booted up prior to installing the Roms above and thought I was on the right path.
Not sure what else to advise becasue I am at a loss for what I have done.
Been Using a rooted MyTouch 4G/Glacier and felt like I could handle this device, not so much.
What should I try next?
Thanks,
jbillam said:
After marathon attempts to read, get to know my Amaze, and to root, I can appear to flash either Speed Rom 6.0 or Energy_6.21.2012.Amaze.Sense.3.6; however, after installation the initial reboot begins a loop. For Speed Rom, reboot occurs after the 4 colored X is on the screen awhile, for Energy it occurs after the Beats Audio logo completes. I am overwhelmed. I use 4ext v1.00.5 RC3.
Here is what I think I have done, including a pic of the screen.
Unlocked, S-Off, HBoot-1.90.0008 (pic 1 attached)
I had to work my way through losing HBoot after the wire trick and got it back after a lot of reading.
Had "PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_228638_signed" booted up prior to installing the Roms above and thought I was on the right path.
Not sure what else to advise becasue I am at a loss for what I have done.
Been Using a rooted MyTouch 4G/Glacier and felt like I could handle this device, not so much.
What should I try next?
Thanks,
Click to expand...
Click to collapse
Use this tool to ensure that your phone has the correct stock ROM on it, (and ensure that your phone has the correct firmware on it too) and then you can try reflashing the ROM through recovery.
http://forum.xda-developers.com/showthread.php?t=1762936
Good luck.
You are still running gingerbread, the 1.43 firmware. First upadte it to ics stock then root and flash anything you want
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Thank you for your help, I missed that I was not on ICS stock early on and thought I was on it.
The Super AIO Tool for HTC Amaze 4G worked great, stock booots. After a breather, I will flash something else.
Thanks again.
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.
Excuse me if I missed an existing thread with this issue, I have looked and didn't find one with exact problem.
It seems everyone else has one of the two problems, not both.
As the title claims, when I turn on my phone it freezes on the white background-green htc screen and won't load the OS.
I tried removing the batter then turning back on with power-volume down but nothing happens. That hboot menu doesn't show up.
As soon as I let go of the buttons, it attempts to start up normally then freezes again at the same screen.
Last night I rooted my phone (first time I've ever rooted) and installed SolidRom Suite ICS Sense 3.6 and it worked perfectly.
I then removed battery, went into hboot menu, cleared the catches and did a factory reset. I then attempted to install the SolidRom Suite JB 4.1.1
This is when it loaded the white screen-green htc and froze. I thought it was loading the rom slowly (First time like I said, I didn't know what to expect)
It was 2am so I just fell asleep. I woke up to a dead phone. I plugged it in to a charger and have been attempting to get access to the phone all morning with no luck.
CDMA (Sprint)
s-on
hboot 1.58
2.87
4ext
Any other information you need? Any and all help would be appreciated. Thanks in advance.
I just hope I didn't kill my phone
While rooting last night, I was using a youtube video as a cross reference to the directions I was using from AFs.
I asked the creator of the video the same thing and this is what he replied with
DON ,T BE SCARED (are u?)
this thing is called BOOTLOOP
the rom has problems OR U DID NOT FLASH THE KERNAL!!!!
to flash the kernal u need a working software and install an program called flash image gui
restore your nandroid back u created before flashing
DID U MADE A NANDROID BACK UP
If no
then u need to download the ruu image of your phone GOOGLE TIME keep searching until u got one
Click to expand...
Click to collapse
1-I didn't know I needed to flash the kernel if I was going to stick with the one provided with the custom ROM (is that a gross conceptual error?)
2-If I do need to flash the kernel first... I have no idea how.
3-I looked up flash image gui and all the instructions assume your phone is working fine so I'm not sure what I'm suppose to do with that.
I was so excited when the first rom (ICS) worked... guess that's what I get for then trying to upgrade to JB.
Thanks a lot guys. That noob video I watched to register on this site is so spot on.
update: I finally figured out how to fastboot. I keep trying clear caches then factory reset. I install new rom and then it bootloops again. What am I doing wrong?
I recommend you follow ramjet's guide here: http://forum.xda-developers.com/showthread.php?t=1889438
It will reset your phone back to stock (hopefully stopping the bootloops) and then get you s-off using the wire trick. This will allow you to flash ROMs without worrying about flashing kernels. It will also allow you to change hboots, which I think was what caused the issue in the first place. I think all the jb ROMs don't boot on hboot 1.58.
I was able to return the phone to factory settings. I then retried and now I get past the splash screen and am frozen at the next Sprint screen.
I'm still at it. I'll get it eventually.
ackNalej said:
Excuse me if I missed an existing thread with this issue, I have looked and didn't find one with exact problem.
It seems everyone else has one of the two problems, not both.
As the title claims, when I turn on my phone it freezes on the white background-green htc screen and won't load the OS.
I tried removing the batter then turning back on with power-volume down but nothing happens. That hboot menu doesn't show up.
As soon as I let go of the buttons, it attempts to start up normally then freezes again at the same screen.
Last night I rooted my phone (first time I've ever rooted) and installed SolidRom Suite ICS Sense 3.6 and it worked perfectly.
I then removed battery, went into hboot menu, cleared the catches and did a factory reset. I then attempted to install the SolidRom Suite JB 4.1.1
This is when it loaded the white screen-green htc and froze. I thought it was loading the rom slowly (First time like I said, I didn't know what to expect)
It was 2am so I just fell asleep. I woke up to a dead phone. I plugged it in to a charger and have been attempting to get access to the phone all morning with no luck.
CDMA (Sprint)
s-on
hboot 1.58
2.87
4ext
Any other information you need? Any and all help would be appreciated. Thanks in advance.
I just hope I didn't kill my phone
Click to expand...
Click to collapse
You can't run JB on 1.58
http://forum.xda-developers.com/showthread.php?t=1808332
You need to flash 1.58, the new firmware to flash my Rom.
Click to expand...
Click to collapse
I'm amusing he's talking about hboot there. Am I wrong?
I'm about to try that wire trick. Regardless of everything else, it seems to make life easier down the road.
Please lock
So today, i went to load up a book in kindle and it crashed a couple times in a row. I figured no biggy, and rebooted the phone (which I can't remember the last time I did, weeks ago).
Upon reboot, for some reason, I'm stuck in a boot loop. I get the white screen with the HTC logo for about 15-30 seconds, it shuts down, repeat. I figured no biggy, everything is stock, I don't care about anything on it, I'll just use the RUU to fix it.
That is where my problem begins. Unforunately, I am updated to 2.95, and the last release RUU is 2.89, so it won't let me install. I can get into hboot, I can use fastboot, so I used fastboot to erase the cache. Anything I select (factory reset, recovery, etc) in hboot just sends me back into the reboot loop. Manually flashing errors out because of the mainver discrepancy. I can't use the low version fix because I'm not rooted, so sure, let's try that... I started the process and unlocked successfully. Now the problem is, any recovery I've installed (4ext from the root thread, CWM5.8 from the boot loop thread) installs fine, but whenever I reboot recovery, again, boot loop. It doesn't matter whether the reboot comes from a fastboot command or selecting recovery reboot from inside hboot.
So, desperate (and somewhat ignorant), I booted up into Linux and tried the unbrick post, and of course, the device never shows up with the battery out, cause it ain't bricked. I was hoping somehow that I could use it to replace hboot, figuring that might be corrupt or something crazy like that (grasping at straws really).
What I really need is a 2.95 RUU, but that hasn't been released, and I figured if that didn't work, something is probably fried hardware wise.
I restored a stock signed recovery, so more or less, right now I'm back exactly where I'm started (other then the fact that my phone is now unlocked) and just not sure where to go from here. Any advice would be helpful. Thanks!
EDIT: I'm a moron, and I forgot to specify, but the phone is sprint. I also don't have any service on it (mainly used as an mp3 player) so I don't have any recourse through them.
I'm almost considering bricking the thing to change the hboot (I haven't done my homework on it yet) any thoughts there? Or is it not something I can do because of my problem?
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Well, the problem is that I can't get into a recovery after I install it, I'm still caught in the boot loop... but I will try flashing the boot img. Thanks!
If you would like a quicker response/fix check your pm....i can try to help
Sent from my Evo 3D CDMA using xda app-developers app
Well, I did reflash boot.img with no success. I went to relock the phone and was just gonna throw it on the shelf for a couple weeks (as I do have another one), and when I did that using fastboot, it sent the command over and the phone received it, but it gave me a failure message. So now, it doesn't turn on, when I hook it up to the charger, I get the red charging light for about 10 seconds, and very occasionally when I remove the battery and put it back in the HTC logo appears for about 3-5 seconds before the phone cuts off again.
I'm starting to think there was some hardware issue. Since it had a screwy digitizer anyways (and I chose to get another evo for 65 rather then paying 30-35 for the ldc/dig combo), I'm just going to keep it around for parts and maybe play with it another time.
Your offer of help is greatly appreciated however, thank you.
EDIT: It doesn't seem to be truly bricked, or it isn't a recoverable brick... not really seeing the dim red light and the unbrick script doesn't detect it... the phone isn't in emmc mode... but I'm not hugely concerned with it now like I said.
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
thatdumbguy said:
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
Click to expand...
Click to collapse
Good luck!
So pull the battery, and put it back in.
Hold volume up and then press power.
Does that bring you to boot loader?
Does it say unlocked?
Sent from my Evo 3D CDMA using xda app-developers app