I could use some advice on any options I have for trying to salvage this Rezound. Here is what I know:
The Symptoms:
-Was completely stock and actively used phone
-Charging port began misbehaving. I believe it may be loose/damaged. It will only charge reliably on one particular USB cable (an Amazon Basics, but only one of my dozen or so of those)
-Started randomly rebooting
-Did a factory reset, seemed to help for a while, then it started rebooting again
-It started getting stuck in a bootloop. HTC screen up ~2s -> black ~0.2s -> HTC screen up ~28s -> black ~5s -> repeat. Does this for a variable amount of time, sometimes minutes, sometimes hours before it will actually boot all the way into the OS
-If it does boot, it usually does not last long before it reboots and will typically get stuck again
The Facts:
-I can into bootloader with no issues
-Because I can get into bootloader, I went ahead and unlocked and flashed TWRP 2.6.3.0
-I can get into TWRP and use all of it's functions reliably
-I decided to try wiping data and cache then system several times, flashing a custom ROM (Global_OTA_RED_DESENSED-v1.0) in TWRP and then flashed boot.img with fastboot, but the new ROM has the same issue. In fact I've yet to boot all the way into the ROM
-Does the same thing with the SD card and SIM card removed
My Guesses:
Based on the fact that it is rock solid in the bootloader and in recovery, I thought that it was possibly corruption on system or boot, which is why I tried to install a custom ROM. Now I'm leaning towards bad memory, either where system or boot reside, possibly data or even RAM, perhaps caused by electrical damage from the charge port issues. I just don't understand why I've not seen any sort of read/write errors while doing anything with fastboot or recovery.
At this point I don't know what to do beyond throwing it out. If anyone has any fresh ideas for salvaging this thing, I'd appreciate it.
If not, any ideas for replacing are also appreciated. A new phone isn't really in the budget at the moment, particularly because I desperately want to get away from Verizon (most likely will lose unlimited data if we I start swapping and don't really have $600-$700 to throw around at the moment. I have 4 lines to move and the Rezound line is on contract, so I'm sort of feeling the rock one side and a hard place on the other.
Thanks in advance, folks!
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
acejavelin said:
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
Click to expand...
Click to collapse
Thanks for the suggestion. I had let the phone sit turned off all afternoon to charge and tried this after work. I grabbed Amon Ra from http://forum.xda-developers.com/showthread.php?p=37362226, made sure to wipe boot in excess and installed the ROM you linked. It booted up on the first try unlike the last ROM, and I've been able to load some things on it and delete some bloat for a bit with no reboots. I've even powered off and went back into recovery to do a backup, and had a successful reboot afterwards. I don't know if it was wiping boot that did it, but I hope it holds. I'll keep you posted, and either way, thanks again.
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
"Haus" said:
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
Click to expand...
Click to collapse
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
acejavelin said:
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
Click to expand...
Click to collapse
I'm still on the stock ROM. Unfortunately it quit booting again.
"Haus" said:
I'm still on the stock ROM. Unfortunately it quit booting again.
Click to expand...
Click to collapse
Hmm... Honestly looking like a hardware issue... Sorry bro
Sent from my Nexus 4 using Tapatalk
Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
I tried to run a kernel tweaking script and ended up screwing the phone up. I have wiped and re-flashed several times but I keep getting Android layer restart loops and I have to pull the battery. Is there any way to actually wipe the phone and get a truly "clean" install?
I read some stuff posted by bftb0 but I'm not sure if any of it applies to my situation. Can I use the ErisMTDNuke zip if I have never used Clockwork?
I have RA Recovery and the S-Off bootloader (1.49.2000). I can get into recovery with no problem it's just that flashing the ROM again is not fixing the problem for whatever reason.
PieceKeepr said:
I tried to run a kernel tweaking script and ended up screwing the phone up. I have wiped and re-flashed several times but I keep getting Android layer restart loops and I have to pull the battery. Is there any way to actually wipe the phone and get a truly "clean" install?
I read some stuff posted by bftb0 but I'm not sure if any of it applies to my situation. Can I use the ErisMTDNuke zip if I have never used Clockwork?
I have RA Recovery and the S-Off bootloader (1.49.2000). I can get into recovery with no problem it's just that flashing the ROM again is not fixing the problem for whatever reason.
Click to expand...
Click to collapse
Try Wiping Everything, then Boot up your phone Without the Sdcard!
How far does the phone get before it loops back? Are you able to use adb to get a logcat of what's going on?
Some things to think about trying if you haven't already:
* Flashable Stock ROM - March 2011 OTA - keeps custom recovery
* Flashback21 v2 - March 2011 OTA - reverts to stock recovery
* Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP - April 2010 - rename to PB00IMG.zip, flash with bootloader
PMGRANDS said:
Try Wiping Everything, then Boot up your phone Without the Sdcard!
Click to expand...
Click to collapse
I have wiped everything that Recovery will allow me to wipe. I have not pulled the SD card though.
MongooseHelix said:
How far does the phone get before it loops back? Are you able to use adb to get a logcat of what's going on?
Some things to think about trying if you haven't already:
* Flashable Stock ROM - March 2011 OTA - keeps custom recovery
* Flashback21 v2 - March 2011 OTA - reverts to stock recovery
* Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP - April 2010 - rename to PB00IMG.zip, flash with bootloader
Click to expand...
Click to collapse
It varies actually. Sometimes it will boot all the way but when I do a function or two, say bring up the keyboard, it will reboot. Other times it will boot to the lockscreen, but then reboot and go into a loop. And sometimes it will never make it past the boot animation before looping.
I did try flashing another ROM I had on the SD card, xtrROM, then wiped cache and data before flashing GSB again, but no joy because it still happens. I'll try these and see what happens.
PieceKeepr,
It sounds to me like you might be overclocked too high...we have seen some phones in the past that used to run okay at higher speeds but no longer do...
If you can get to the overclocking / setCPU settings, try backing your clock-speed down from where ever the phone is booting-up or running at.
You could also test this by flashing the stock ROM that I see a link that MongooseHelix posted above since that should run at 528MHz (i.e., the one that retains custom recovery).
Worth a shot anyway (make a Nandroid backup, then wipe and flash the stock ROM and see how that behaves for a little bit...might shed some light on if overclocking is the issue).
Cheers!
It definitely was not an overclocking problem.
Tentatively I think I have it fixed. I flashed the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP then rooted again. Wiped dalvik and data and flashed xtrROM to see if it booted OK and it did. Wiped dalvik, wiped data and deleted the android.secure folder and flashed GSB. Everything seems to be working great.
The only downside is I lost my S-Off bootloader but I can fix that later. The upside is that my phone has not been this responsive and snappy in quite a while. I don't know if the IMG file is responsible for that or if it's the fact that when xtrROM loads it says it formats boot, system and cache.
I noticed the performance increase briefly the first time I flashed xtrROM then GSB but it crashed and started looping when I tried to install and set up an app from the SD card. After the process outlined above I again installed the app (Swiftkey) but when I tried to configure it the setup started looping. This was a problem encountered by many a while back and was determined to be a corrupt file. So I uninstalled the app and installed the newest version from the market even though I don't like it as much as the older version.
I'm gonna leave this open until I'm comfortable that it's fixed. Thank you all for the input and a huge THANK YOU to MongooseHelix!
As a side note I followed these instructions to get the S-Off bootloader... http://forum.xda-developers.com/showthread.php?t=725047 ... and I'm wondering if I actually have to do the whole thing again. Can I flash the PB00IMG.zip and get the S-Off bootloader again or should I do the whole thing?
Two days and not a single problem, so I thinks it's safe to say it's fixed. Thanks again for the help.
I Have restorted to being the noob that signs up to ask a question...The other day I was driving (pre-root) and I look down to notice my phone had power cycled on its own. I thought it would come back one, boy I was wrong....
It spiralled into endless boot cycle. It would at first reboot get to the 4g screen and then back to the htc...over and over. I was able to get into Hboot, and atempt to do a factory reset that didnt help because it became a endless reboot that way as well.
Now before any of you say "why dont you warranty replace the phone" Im a VZW agent, alas we dont have a warranty on our phones when it comes to our concessions lines...
Now, at that point I said enough is enough and I delved into the world of rooting. I self taught everything within a few hours. I had my phone unlocked and ready to go. I picked Ineffabile (http://forum.xda-developers.com/showthread.php?t=1420513) to use as a rom, I followed the procedure to a T it installed correctly, but then when it came back on everything seemed to work fine...for about 5 minutes and then it happened agian a power cycle all over again. and again...and again. It now comes on works for about 5mins and then reboots.
Im at a complete loss at this point I have gone back into the SD card and deleted the ph98 file etc.... I just dont know what to do. I need this phone to work.
Any help is appreciated Thank you so much!
I know you said it's not the wcdma problem but will your phone stay booted with the back cover off?
Else I'd ruu back to stock. Could try the different radios and see if it helps.
If you want to try the older radios and are on the OTA you'll have to hexedit you mainver. There's a guide if you look.
older radios? Im still new to this so I applogize...
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
Here's a couple guides to help you get familiar with rooting stuff:
http://androidforums.com/evo-3d-all-things-root/389787-beginners-guide-rooting-android-devices.html
http://androidforums.com/evo-4g-all-things-root/129648-quick-intro-rooting-those-new-rooting.html
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
feralicious said:
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
Click to expand...
Click to collapse
I dont have insurance =/ and cant get it either. Im trying to find the radios, and what kernal should I be flashing? because I cannot find the one that should match the rom im using.
What I dont understand is why the phone powers on, works for a few moments like nothing is wrong what so ever. Then freezes and reboots.
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
http://themikmik.com/showthread.php...-Beats-Tweaks-2-01-605-11&p=164906#post164906
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
feralicious said:
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
Click to expand...
Click to collapse
This is a clean SD card, and I didnt create a backup because I couldnt get the phone past Hboot when it was doing boot cycles previous to the root. I re-ruu'd right now. And im starting from scratch. I used clockwork before, Im trying amon ra now.
OK, so I got a little "cocky" and flashed to another ROM. Apparently it wasn't capability with Rezound as it didn't boot. When I tried to boot into recovery, only could select Hboot. That lead to a loop. Took out the memory card, the SIM chip, battery, cover all to no avail. I finally got Scott's rom that was working back on the phone. But still having issues, the phone constantly reboots. I get to the home screen and/or lock screen it works but then freezes and resets. I no longer have the ability to boot into recovery. When I connect to the MAC (or PC) it says charging only.
When able tried a factory reset but that didn't do anything, I can no longer get to that screen. Did a nandroid backup before playing around with the new ROM but can't figure out how to get to it.
HELP... need your help pretty please
Did you just do a factory reset before you flashed Scott's rom or did you wipe /system as well? Also make sure debugging is enabled as well. Have you tried to boot to recovery with adb?
Sent from my ADR6425LVW using Tapatalk 2
DOOD YOUR PHONE IS TOTALLY BORKED. PANIC!
Kidding
in all seriousness. What firmware are you on. ICS or GB firmware?
I.E. have you run an RUU, are you s-off or s-on
if you are unsure, just type out like the first 5 lines in HBOOT.
Did you just do a factory reset before you flashed Scott's rom or did you wipe /system as well? Also make sure debugging is enabled as well. Have you tried to boot to recovery with adb?
Click to expand...
Click to collapse
When I was able to select something other than HBOOT I did a factory restore but didn't notice anything different. Also manually deleted. However now when I try to go into recovery mode, only HBOOT is selected and the up/down button doesn't work.
Not sure how to boot to recovery with adp.
Appreciate your wisdom
What firmware are you on. ICS or GB firmware?
I.E. have you run an RUU, are you s-off or s-on
if you are unsure, just type out like the first 5 lines in HBOOT.
Click to expand...
Click to collapse
The last time the phone worked, was running Scott's Clean Rom 4.5, Android 4.0.3
Kernel ver: 3.0.16-g8fa42b5
I believe it's s-off but it's fighting me to get back to the recovery screen
Sadly I'm not sure about RUU
What ROM was it if you don't mind me asking? I mean was it at least for the Rezound if so then it shouldn't be that bad..
I didn't do anything different this morning than last nite, but the phone came back to life. I restored the nadroid backup and it appears to be working. Though getting an error about the SIM card after a reboot.
Don't know what I did wrong when trying to flash or if the ROM just wasn't compatible.
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