bricked no bootloader, recovery, RUU fails, windows wont recognize adb/fastboot - Sprint HTC EVO 4G LTE

This phone belongs to my brother and I own the Sprint account. The phone wouldn't turn on at all even on bootloader after he tried to flash a mod. It was htc dev unlocked using Regawmod. Phone was running viper rom 1.2.1. Heres where he got the mod http://forum.xda-developers.com/showthread.php?t=1609480 he downloaded one of the mods he cannot remember which one but they're all practically the same status bar mod except they're different colors. The thread belongs in the HTC One X device forums but ive heard of others flashing mods straight from there with no problems..I'm still surprised that it bricked the phone though..since it's just a MOD regardless I would expect twrp to just say "failed" but not brick the phone..so All was good until:
1. rebooted into twrp recovery (ver 2.1.8)
2. attempted to flash elegancia mod from one x forum
3. 1st time recovery displayed "failed"
4. he tried again 2nd time..twrp once more displayed "failed"
5. seeing that nothing happened and the flash simply failed, my brother chose the reboot option from twrp.
6. phone did not reboot
7. couldn't access bootloader at all no matter how many times we tried
8. holding down power button and power+vol up/down combinations [in desperation] did not do a thing no matter how long the buttons were held
9. RUU completely failed...it would not detect the phone..windows failed to recognize the phone but instead attempted to install drivers "QHSUSB_DLOAD" I had also forgotten that the bootloader must be relocked but that couldn't happen anyways since the bootloader was never accessible in the first place
10. opening the phone and unplugging battery and reconnecting did not do a thing
11. we're stuck with a brick..no bootloader access, no recovery, not even the power led displaying signs of life...nada.
12. my only hope is for a method to actually unlock the bootloader to be developed using the same method as made famous by the EVO 3d found here http://forum.xda-developers.com/showthread.php?t=1547695 which actually BRICKs the phone by corrupting hboot when S-On,thus placing it into download/emmc mode. I assume it's in download mode since windows tried to install "QHSUSB_DLOAD" drivers but failed at that.
If anyone has a clue what I should do or knows of someone that can help then please let me know! Thanks!
Sent from my PG86100 using xda premium

Pretty much have the same exact problem on my thread :S http://forum.xda-developers.com/showthread.php?t=1725027

Take to sprint store and they willgive you a new one
sent from my EVO LTE

cant wait
ddeecc said:
This phone belongs to my brother and I own the Sprint account. The phone wouldn't turn on at all even on bootloader after he tried to flash a mod. It was htc dev unlocked using Regawmod. Phone was running viper rom 1.2.1. Heres where he got the mod http://forum.xda-developers.com/showthread.php?t=1609480 he downloaded one of the mods he cannot remember which one but they're all practically the same status bar mod except they're different colors. The thread belongs in the HTC One X device forums but ive heard of others flashing mods straight from there with no problems..I'm still surprised that it bricked the phone though..since it's just a MOD regardless I would expect twrp to just say "failed" but not brick the phone..so All was good until:
1. rebooted into twrp recovery (ver 2.1.8)
2. attempted to flash elegancia mod from one x forum
3. 1st time recovery displayed "failed"
4. he tried again 2nd time..twrp once more displayed "failed"
5. seeing that nothing happened and the flash simply failed, my brother chose the reboot option from twrp.
6. phone did not reboot
7. couldn't access bootloader at all no matter how many times we tried
8. holding down power button and power+vol up/down combinations [in desperation] did not do a thing no matter how long the buttons were held
9. RUU completely failed...it would not detect the phone..windows failed to recognize the phone but instead attempted to install drivers "QHSUSB_DLOAD" I had also forgotten that the bootloader must be relocked but that couldn't happen anyways since the bootloader was never accessible in the first place
10. opening the phone and unplugging battery and reconnecting did not do a thing
11. we're stuck with a brick..no bootloader access, no recovery, not even the power led displaying signs of life...nada.
12. my only hope is for a method to actually unlock the bootloader to be developed using the same method as made famous by the EVO 3d found here http://forum.xda-developers.com/showthread.php?t=1547695 which actually BRICKs the phone by corrupting hboot when S-On,thus placing it into download/emmc mode. I assume it's in download mode since windows tried to install "QHSUSB_DLOAD" drivers but failed at that.
If anyone has a clue what I should do or knows of someone that can help then please let me know! Thanks!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Hopefully one day someone will figure this out with out actual casualties. Thanks all for your help. I'm getting a new one tomorrow.

I wanted to know if you found a solution because im dealing with a similar problem. I can cant access my phone manually or through fastboot

Linux will help you with download mode. There's threads on how to use ubuntu to unbrick. I'd find the thread for you, but am not in a position to do so.
Sent from my EVO using xda app-developers app

Related

[Q] Recovery & Flashboot issues. help is appreciated [SOLVED]

First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?

[Q] Bricked? : (

Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
U try running the RUU?
Sent from my EVO using XDA
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Gotta do it...
sent from my EVO LTE
See post edit.. : S
naterz said:
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Click to expand...
Click to collapse
where did you get the 1.12.651.2
all i can find is 1.12.651.1
shipped-roms.com. I guess i could try the .1 version
when i try to run the .1 ruu, it shows im on 1.12.651.1_R2
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
naterz said:
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
Click to expand...
Click to collapse
Navigate to your adb tools folder via terminal and type
adb reboot bootloader
tried adb reboot, error device not found : (
ddeecc
naterz said:
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
Click to expand...
Click to collapse
But you did get to the splash screen and that's a sign of hope..this phone won't even do that. nothing at all screen dead, everything is dead including bootloader. :\
Shutdown the phone and boot into bootloader.
Option 1) do a factory reset and if it doesn't work then,
Option 2) select fastboot then ran Ruu.
Sent from my HTC One X using xda premium
There is no way to boot into bootloader or fastboot, whether through adb or the key combos :S Adb states device not found and the key combos only give me splash then a lightly lit black screen..
Sent from my PC36100 using XDA
Are you positive about not able to boot into bootloader with key combo? Your phone has to pass bootloader before going to the splash screen.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
So you tried booting as instructed as the above link?
Sent from my HTC One X using xda premium
Ive never really pressed the power button a second time after the initial let-off. I'll give it a shot when I get home, but I'm expecting the same results. Just FYI, I DO see the two Orange bars move on the splash screen (upper right) before it goes blank..
Sent from my PC36100 using XDA
Sounds like a case of the looped boot screen
Sent from my HTC One X using xda premium
UPDATE! Phone was completely drained when i got home...plugged into charger, orange light came on! Was able to enter the bootloader through the key combo and successfully entered my TWRP to do a nand restore. Restore went well and am now running again! Brick fixed by draining battery!
Good to hear:good:. brick was fixed by draining battery :what: then why did you need to do a nand restore? Whatever worked for you
why i said it was fixed via drain was that the charge light finally came on after it died and was plugged in, therefore it allowed me to access bootloader which let me into recovery to restore my backed up clean system files. When the nand restore was completed i was actually able to pass my splash screen! : )

[Q] I bricked my Rezound need help

At first, I apologize if i didn't see this kind of thread. I was looking for solution for a couple of weeks and didn't find anything that would help...
My Rezound is S-OFFed with 2.27 hboot and CWM recovery (the one befor CMW6.*****).
I dodn't know what made me try flashing CMW 6.*** but i did. Right after i flashed CMW 6, i went to "advanced" and rebooted recovery.
This is where weird thing happend: My phone just turend off. I tried to turn it on but i doesn't do anything.
While in Windows, if i connect my phone it shows up as QHSUSB_DLOAD
I tried:
pulling out/in the battery - didnt help
Connecting charger and turning the phone on without battery and holding vol - - didn't help
I also tried " [UNBRICK]Wanna unbrick your Rezound? (9/8, Episode VI, Return of The Zip)" and ended up with something like " device isn't found". I tried it in Urbundu 12.04
Ivanov4912 said:
At first, I apologize if i didn't see this kind of thread. I was looking for solution for a couple of weeks and didn't find anything that would help...
My Rezound is S-OFFed with 2.27 hboot and CWM recovery (the one befor CMW6.*****).
I dodn't know what made me try flashing CMW 6.*** but i did. Right after i flashed CMW 6, i went to "advanced" and rebooted recovery.
This is where weird thing happend: My phone just turend off. I tried to turn it on but i doesn't do anything.
While in Windows, if i connect my phone it shows up as QHSUSB_DLOAD
I tried:
pulling out/in the battery - didnt help
Connecting charger and turning the phone on without battery and holding vol - - didn't help
I also tried " [UNBRICK]Wanna unbrick your Rezound? (9/8, Episode VI, Return of The Zip)" and ended up with something like " device isn't found". I tried it in Urbundu 12.04
Click to expand...
Click to collapse
Can you boot into bootloader? Pull battery and put it back in and hold down power+vol down. If so cant you just flash a new recovery?
It sounds like your phone is stuck in Download Mode, that is used by the older RUU EXE files... you run it from your PC and just walk through the steps to install the firmware. Perhaps trying one of those, they can be downloaded here: http://mobile-overload.com/topic/53-ruu-htc-rezound-ruu-roundup/ but I think the newest EXE version you will get is 2.1.605.11 which is Gingerbread. It will return your phone to bone stock Gingerbread, S-ON, stock recovery, and all that good stuff, but it might work and get you running again.
It's the glitch that you get when you install cwm on a rezound, you can't charge your battery. Look it up on xda they have a solution.
That's the thing. It doesn't work at all.
Sent from my SCH-I535 using xda premium
Here's the link to save your ass.
http://forum.xda-developers.com/showthread.php?t=1711408
If you need to buy another I can sell you mine 230 + shipping obo
mforminio7 said:
Can you boot into bootloader? Pull battery and put it back in and hold down power+vol down. If so cant you just flash a new recovery?
Click to expand...
Click to collapse
The phone doesn't work at all. It doesn't even turn on.

Evo 3d rebooting after drop

Hi all,
This is my sons phone which he doesn't use as phone - just for games.
Last night he dropped it and it froze, after removing battery it started powering and boot-looping on white htc logo screen.
I powered it with vol down and went on boot-loader and I thought I just restore it via recovery to a state I made him few months back, but failed to go to recovery, again on white screen loop.
I tried installing shipped ruu and after few fails I did it, but again restarts on white screen.
I can connect it to pc and all, running fastboot commands usualy comes with "remote not allowed"
I was sure that I did unlock bootloader for this phone but it says locked, so I am not sure ( having 4 htc phones in same house hard to know what I did to which )
This phone prior to drop had:
4EXT_Recovery_Touch_v1.0.0.5_RC7
S-OFF
not sure on unlocked bootloader
and
Cool-ICS-v17-EvoC
any ideas appreciated
Thank you
PS
I tried to go to htc page and unlock boot-loader, but numbers i paste are not recognized ( I did this many times so its not my error in copy paste)
I guess I cant edit my post.
I managed to unlock bootloader
I installed "Cool-ICS-v17-EvoC" rom via sd card as PG86IMG.zip as I can't load into recovery
and it reboots on white htc logo again
help
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Brian706 said:
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Click to expand...
Click to collapse
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
cipher101 said:
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
Click to expand...
Click to collapse
Apologies, I went and re-read the op and now I see that.
I think you are having trouble with the fastboot commands because of the locked bootloader like you said. You could also use the juopunutbear patched hboot since you are s-off, it will give you access to the extra fastboot commands regardless of locked/unlocked state. It can be flashed as a PG86IMG.zip via the bootloader.
If you use the patched hboot you could attempt to boot recovery into memory by using fastboot boot recovery.img
Because you are s-off, you can also flash a recovery via the bootloader as a PG86IMG.zip. If you want to try, here is 4ext recovery:
https://www.dropbox.com/s/t6q8wi58xzidgan/4ext_1.0.0.5.rc9_PG86IMG.zip
Obviously just Rename the file and remove everything prior to PG86IMG.zip.
I have a feeling though that since you successfully ran the ruu and it still won't boot, that no amount of software changes will fix the issue. I'm not sure if the motherboard will fix the issue or not buy that's a pretty cheap fix to try
Thanks for help and advice man,
I bought him a working used evo 3d from ebay, it was under $30 so I'll keep this one for parts I guess.
Thanks again

htc m9 root help

Is there a rooting section or something? I feel as if this may be in the wrong section (if so, please move it thanks)
So, today, I decided that I wanted to unlock, root, and install a custom ROM on my htc m9. Now, on my previous phone, I only rooted and installed a custom kernal, all of which were apps that I used on my phone to do all the work. for the m9, there are no apps that root the phone for you so I looked up a few tutorials. (I'll list what I did in case you find something I did wrong
list of my guides :
droidviews.com/root-htc-one-m9-marshmallow
.droidviews.com/how-to-root-htc-one-m9-and-install-twrp-recovery-on-it/
and I used htc dev to unlock my phone's bootloader
unlocking my bootloader.
Unlocking my bootloader was successful, when I go into download mode (the black screen to be clear) it says unlocked
installing twrp
There was a lot of issues when installing since all but one of the guides kept saying go into bootloader mode, bootloader mode this, bootloader mode that (which is the white screen). After some searching, I realized that they really meant download mode... two different things... I believe twrp was successfully downloaded since I am able to access twrp when I go into bootloader mode, then recovery mode, and I end up in twrp.
rooting
so, according to the guide, I move the supersu zip files into my internal storage (anywhere). then go into twrp, press install, select the zip file, then swipe to flash.
well, I did just that, however, when I go to turn on my phone, I get stuck on the htc load screen, It's not a boot loop, it's just that white screen that says htc... I can't do anything else. holding down the power button does nothing (even for 10 seconds)... update, after typing this, I get a nice animation, then I'm stuck on the white screen that says htc one...holding the power button again does nothing, power button, and volume down does nothing... I think if I hold the power button and volume up, I turn off the phone, meaning I can access download mode, boot loader mode, etc. So... now what? clearly, following instruction has got me not where (bummer) and my lack of experience has also gotten in trouble (it could be worse? right?) what can I do to fix this?
note: my previous phone, I soft bricked it and I was able to flash the stock rom with LG flash tool, but there's no such thing as htc flash tool...

Categories

Resources