• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Please HELP!!

C

cdcampbell

Lurker
Basically, I was trying to get the latest Viper rom to work with my Evo3D. So i was experimenting with different HBOOTS to see which one would work better. I started at 1.5, then went to the 1.58 then 1.57, then once i flashed 1.50 again cause i couldnt get them to work with the rom. Once i flashed 1.5, my phone was un responsive. No red light when charging, cannot turn on. Ive tried taking the battery out and putting it back in. I feel as if its bricked....

Is it bricked?
Is it fixable?
WHAT DO I DO?!?!?!:confused:
thank you!!!
PLEASE REPLY QUICK!
 
cdcampbell said:
Basically, I was trying to get the latest Viper rom to work with my Evo3D. So i was experimenting with different HBOOTS to see which one would work better. I started at 1.5, then went to the 1.58 then 1.57, then once i flashed 1.50 again cause i couldnt get them to work with the rom. Once i flashed 1.5, my phone was un responsive. No red light when charging, cannot turn on. Ive tried taking the battery out and putting it back in. I feel as if its bricked....

Is it bricked?
Is it fixable?
WHAT DO I DO?!?!?!:confused:
thank you!!!
PLEASE REPLY QUICK!
Click to expand...

welcome to the forums!!!!!!!!!!
one thing you have to be careful of and that is when you start messing with hboots like that. not sure if there is anything you can do at this point.
 
Well looks like you flash 2 different HBoot Roms, one is a CDMA and the other is a GSM, and that is not good, what carrier are you with ??



cdcampbell said:
Basically, I was trying to get the latest Viper rom to work with my Evo3D. So i was experimenting with different HBOOTS to see which one would work better. I started at 1.5, then went to the 1.58 then 1.57, then once i flashed 1.50 again cause i couldnt get them to work with the rom. Once i flashed 1.5, my phone was un responsive. No red light when charging, cannot turn on. Ive tried taking the battery out and putting it back in. I feel as if its bricked....

Is it bricked?
Is it fixable?
WHAT DO I DO?!?!?!:confused:
thank you!!!
PLEASE REPLY QUICK!
Click to expand...
 
1.57 is a GSM hboot I think... You might be bricked :s

You can try taking it to sprint and see what they say, but they might just be like you tried rooting, your fault..
 
well i unfortunately moved on from this phone so i can't help too much. but i can say this, if you can't get to the bootloader or recovery, then then there is very little you can do. i know of no trick that can fix a phone in that state.
 
For the record Hboot 1.57.0000 is the evo v hboot. It's possible that the GSM has a 1.57 as well I suppose. But I just want to throw it out there that he very well may have used the evo v cdma 1.57 hboot and that should not brick the phone. I suppose it's possible that it ran into problems if the android-info.txt didn't specify cid for both VM and Sprint.

I would plug the phone into the wall. Leave it alone over night or if possible up to 24 hrs. Just let it be. After leaving it for an extended period, try a battery pull and see if you can boot to anything. It's possible you hit a deep sleep.

Check this thread out. It just happened to someone else recently and we got it resolved. It's happened to me before as well. It's worth a shot. Just need a little patience and hope for the best!

http://androidforums.com/cdma-evo-3d-all-things-root/656656-dead-after-rom-flash.html


Edit to add:
Just looked at his source of the file. These were posted by Ramjet at XDA who knows his stuff. He also says in the thread that he specified the android-info.txt to work with both Sprint and VM. So he definitely didn't flash a GSM hboot!

That's great news! This means you are likely in the deep sleep as mentioned. It sucks but just be patient and your Evo will likely revive from the dead eventually!
 
Brian706 said:
For the record Hboot 1.57.0000 is the evo v hboot. It's possible that the GSM has a 1.57 as well I suppose. But I just want to throw it out there that he very well may have used the evo v cdma 1.57 hboot and that should not brick the phone. I suppose it's possible that it ran into problems if the android-info.txt didn't specify cid for both VM and Sprint.

I would plug the phone into the wall. Leave it alone over night or if possible up to 24 hrs. Just let it be. After leaving it for an extended period, try a battery pull and see if you can boot to anything. It's possible you hit a deep sleep.

Check this thread out. It just happened to someone else recently and we got it resolved. It's happened to me before as well. It's worth a shot. Just need a little patience and hope for the best!

http://androidforums.com/cdma-evo-3d-all-things-root/656656-dead-after-rom-flash.html


Edit to add:
Just looked at his source of the file. These were posted by Ramjet at XDA who knows his stuff. He also says in the thread that he specified the android-info.txt to work with both Sprint and VM. So he definitely didn't flash a GSM hboot!

That's great news! This means you are likely in the deep sleep as mentioned. It sucks but just be patient and your Evo will likely revive from the dead eventually!
Click to expand...

Now that I think about it, 1.57 is the evo v hboot, not GSM. GSM is on 1.49 or 1.53.. It's definitely better that you flashed the evo v's hboot and not a GSM hboot. That being said, you'll still have a difficult time fixing what happened.

I read about this somewhere: http://forum.xda-developers.com/showthread.php?t=1880478 (http://unlimited.io/qhsusbdload.htm) but I don't know of a fix for the evo 3d... What you described is what seems to be happening to them also.
 
Checking your link form XDA posted by Ramjet, looks like you are with Virgin Mobil, please confirm this before we go any further. If this is the case then you are not most likely bricked and we will be able to help you out, but we need as much info as possible before we proceed before we give you the wrong info and brick your device.

For now I am moving it to the Evo V section to be safe



cdcampbell said:
I used hboots which i got from here. ( http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7 )

The 1.57 did appear on my screen, but yeah, what are my options? thanks guys!
Click to expand...
 
Sorry to jump in a little late here, but I have a couple of questions for you.

1. Was the last bootloader flash interrupted in any way? A partial bootloader update can "soft" brick a phone but there is a thread on XDA to revive it.

2. How does the phone appear in device manager when connected to a Windows PC? I realize you can't boot it at this point, but am trying to determine if it is the QHUSB-DLOAD state.

If the last bootloader flash wasn't interrupted it may just be in the "deep sleep" state that others have described. If you have a spare battery I would suggest trying that, and also make sure the contacts are clean and the battery is properly seated in your phone. Sometimes the phone will appear "dead" simply because the battery isn't making good contact.

ramjet73
 
Are you posting in the right thread ?? This thread is related to the OP members issue, Do you have the same issue ??



bhoff15226 said:
My phone is the vm cdma, and my hboot is currently 1.57. I just looked again to be sure
Click to expand...
 
DonB said:
Are you posting in the right thread ?? This thread is related to the OP members issue, Do you have the same issue ??
Click to expand...

Im just stating that 1.57 is cdma, not gsm. I have a cdma with the 1.57 hboot. My phone is working perfectly. I dont know if there is a 1.57 for gsm or not. Just trying to help
 
So I have Sprint.
Also my bootloader was acting normal when I did the flash.
When I flashed back to 1.5, my phone said flash complete. Then turned off. Ill try working on it. But am I just screwed....im using a Rumor Touch....this is a piece of crap compared to my old droid:/
 
cdcampbell said:
for the record, after relating to previous forums...Im sure that im in qualcom diagnostic mode. So how do i fix this?
Click to expand...
There's an XDA thread here for reviving a phone that is stuck in the QHSUSB-DLOAD mode. Please read the note right below the large graphic in the OP:

Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
Click to expand...
My understanding is that you are currently S-OFF so this probably doesn't apply to you. The only thing that I can recommend is to charge the phone overnight and try flashing the RUU.exe from Windows, if you can actually see your phone as QHSUSB-DLOAD device in the device manager.

ramjet73
 
Unfortunately, if you can't power on at all and at least get into the current bootloader it's going to be hard to attempt any other recovery. If you are still under warranty or have insurance it shouldn't be a problem getting the phone replaced if it can't be powered on.

ramjet73
 
cdcampbell said:
Basically, I was trying to get the latest Viper rom to work with my Evo3D. So i was experimenting with different HBOOTS to see which one would work better. I started at 1.5, then went to the 1.58 then 1.57, then once i flashed 1.50 again cause i couldnt get them to work with the rom. Once i flashed 1.5, my phone was un responsive. No red light when charging, cannot turn on. Ive tried taking the battery out and putting it back in. I feel as if its bricked....

Is it bricked?
Is it fixable?
WHAT DO I DO?!?!?!:confused:
thank you!!!
PLEASE REPLY QUICK!
Click to expand...


So you cant get into recovery by hooking you phone up to your computer and starting recovery thru command prompt?
 
jjavitable1 said:
So you cant get into recovery by hooking you phone up to your computer and starting recovery thru command prompt?
Click to expand...
No. If you can't power on the phone ADB and fastboot aren't available. ADB commands require debug mode in Android and fastboot commands require "fastboot usb" in the bootloader. Some ADB commands may be available during the boot process but you have to be able to power on to get that far.

ramjet73
 
You must log in or register to reply here.
Back
Top Bottom