Hi
i was used the command for S-ON after S-off "fastboot oem writesecureflag 3" and "fastboot reboot-bootloader".
My Phone turn off and that was it...
Only the red Led lighting very weak...
and no response on press Power&Volume buttons..
The battery has still 50%...
Has anyone an Idea?
PS: When i plugged the Phone on the Computer, i see an unknown Device called "QHSUSB_DLOAD"...
cheater2 said:
Hi
i was used the command for S-ON after S-off "fastboot oem writesecureflag 3" and "fastboot reboot-bootloader".
My Phone turn off and that was it...
Only the red Led lighting very weak...
and no response on press Power&Volume buttons..
The battery has still 50%...
Has anyone an Idea?
PS: When i plugged the Phone on the Computer, i see an unknown Device called "QHSUSB_DLOAD"...
Click to expand...
Click to collapse
i'm taking a guess in the dark, but when you hold vol up + pwr, that'll boot the device into qpst mode/diag mode and perhaps windows will show that is "QHSUSB_DLOAD" .. or the other thought is maybe dload is for Download mode?
Either way, perhaps a battery pull should reset the device then pressing only power should allow it to power on properly.
Hope that helps! Let us know!
It's help not really.
But i think your supposition that the Device was in a Download Mode, can be right.
I have take out the battery for one hour, put it in and without that i do anything, the red light was lighting weakly.
A press of the Buttons are without any reaction...
The only what it does, was on USB.
If i Plug it in, the PC recognize an Device "qualcomm CDMA Technologies MSM". 8-10 seconds later, it will be disconnected itselfs and connected with the "QHSUSB_DLOAD".
I don't understand, what the programm "fastload" does. I've rootet the Evo without any failure, but the command "reboot-bootloader" with the pre-command " writesecureflag 3" seems to be killed my HTC...
Is there a driver for the Dload? Or any driver, that allows Fastboot or revolutionary to connect my htc, when it's in this mode? xDD
I was serching a little bit for this device and found another Thread.. it sounds like my problem...
http://forum.xda-developers.com/showthread.php?t=1041153
The driver works - but how can i switch the phone back in the normal mode?
They talking from JTAG and i have no Idea, how to use this...
Or should i send it back and hope, that they don't recognize ,that it was rootet before i make more damage on the HTC?
cheater2 said:
I was serching a little bit for this device and found another Thread.. it sounds like my problem...
http://forum.xda-developers.com/showthread.php?t=1041153
The driver works - but how can i switch the phone back in the normal mode?
They talking from JTAG and i have no Idea, how to use this...
Or should i send it back and hope, that they don't recognize ,that it was rootet before i make more damage on the HTC?
Click to expand...
Click to collapse
as a last ditch effort, the only solution i can suggest would be trying different combination of hardware buttons when booting or while the device is on or while pulling the battery.
after reading the thread you linked above, they confirmed what i suspected, nobody really knows a way to recovery out of this situation.
for whatever reason, the phone is booting into a deeper, very uncommon, level of diagnostics and its something very few ppl around here are familiar with.
i've never seen this mode and actually hope i never do!
might get lucky and somebody with inside or special knowledge will know how to navigate. otherwise, as far as this community goes, there isn't much i've seen posted around here to assist.
Last night I bought a brand new Streak 5 from a local guy. Box was sealed, no mention of refurb, inner contents were sealed.
I didn't have time to test it and the guy I bought it from said he had gotten it a while back from a work raffle and that it had been sitting in a drawer in his house - I have no reason not to trust that he was lying to me.
When I actually got time to unbox it, I popped the battery in and tried to turn it on. The menu buttons lit up briefly and then when out. The screen never came on. Since then, it has been completely unresponsive.
I've tried to charge it with the wall charger, as well as my PC. Neither seem to be doing anything and my PC doesn't recognize it - even with Dell's software installed.
I've tried to take out the battery and hook it up to the wall charger and my PC to get it to turn on.
I've removed the Micro SD.
There is no SIM card in it currently.
I ordered another battery and an external battery charger. They should be here in a few days. I have the current battery rigged up and charging with a spliced USB cord.
What else can I do? I feel like I've done everything "simple" thus far and I'm a little nervous when it comes to utilities like Streakflash.
I'm coming over from the iPhone world and my Android use has been limited at best. Any help is appreciated.
What happens on the device itself after having had a chance to charge?
Does it light up when you press the power button, or nothing at all?
Thanks for the response.
There is no indication that it's charging. The screen doesn't come on, or even flash. The buttons do not light up. However, I don't believe it's the cable or the connector since my PC responds with an unrecognized device -- "Qualcomm CDMA Technologies MSM" prompt. I also managed to get my PC to tell me that the device "wasn't plugged in."
I've tried to get some response out of it in every possible combination regarding the buttons, battery, back cover, microSD, and where it's plugged in. It just sits there. No lit screen, no lit menu buttons, nothing.
If it helps, I'm running Windows 7 64 bit. I've installed every possible thing I could find regarding the Dell drivers and my OS.
It sounds like your device somehow got shipped without having all the software installed onto it.
Can you provide more information about the device itself, such as it's manufacture date or any other info on the box/device labels? Devices getting shipped half baked like that isnt exactly common.
This sounds like a legitamate time to use QDL tool to reflash it, but I cant provide any help with that as I've never used it.
Can you use QDLTool if your computer doesn't even recognize it?
The date on the label is 10/12/2010.
If it's displaying as "Qualcomm CDMA Technologies MSM" that's a sign that it should be able to get into upload mode as that's what the driver qdl tool uses I believe.
It's likely out of warrentee already, so you prob have to fix it on your own if at all.
I can't get it to respond to anything I do. It's very disheartening. I really, really wanted this phone, too.
I'm downloading the latest version of Ubuntu. I'm going to see if I can make any headway through Linux.
I can't get QDLTool to pick-up the device, either. I get an error message when I try to use it and scanning for it does nothing.
Did you install the driver bundled with it properly?
If it still doesnt detect it after that it's likely a dud
use qdltool, you can download it from here
http://www.box.com/s/rj9xd5tl7v5amimbm3youll need to make sure you have all drivers installed though, info is on this forum somewhere,
once installed run the software on pc you should see a big box with "run" on it, click run then connect phone by holding volume up and connecting usb then qdltool will do rest from there
when i got my both my dell streak it was the same deal. first one came exactly as how you described it. I put in the battery, made SURE THAT THE CONNECTORS ARE lined up on the back case, and then tried to power it on. NOTHING.
It seems even if the battery was fully charged, the only real way to turn it on was to connect the streak to the power adapter and then press hold down the on button. WHen the device finally gave me the dell logo, it would just sit there stuck. So i took out the battery, and redid it. Then went into fastboot mode (hold camera and power) and it wouldnt detect the touch screen. It seems that the touch scree was faulty and hence it would remain stuck on the dell logo. I tried to calibrate the touch screen a few times, all failed. Then finally for one time it worked, and the touch screen came back to life. Shortly after though upon booting into the old stage 1.6, it restarted and the touch screen failed again.
So i sent it back to rogers and they gave me a replacement phone. Same deal, when you first put in the battery and the case it wouldnt start no matter what. Only upon plugging it into the power adapter then it starts up. However this new one had a functional touch screen.
1) check out the touch screen by using the fastboot, or stock recovery. If you get error messages, it means your screen is toast most likely and then you might have to open her up and see if all the connections are lined up
2) if it doesnt boot at all, try connecting it to the power adapter first and then after about 30 seconds power it on. You should be able to see the dell logo unless as the guys stated before the software is hosed.
3) if the software is totally hosed, tried to get it into fastboot mode or recovery and see if you can reflash the device.
something like that...
Thanks for the comments, guys.
As of now, it's still in the same position it was in. It doesn't respond to any combinations of buttons, battery in/or, or plugged into the wall/pc.
I'm assuming that the situation it's in currently is what's preventing any sort of legitimate connection between the phone and my PC.
My last shot is a battery and external charger that should be here next week.
After a little discussion in the Development section, we decided to offer a fix for those who continue to use ROM Manager and Clockwork Mod Recovery. Some of you started using CWM as default choice, not knowing the issues, and others of you simply prefer CWM.
Be warned! Neither I nor any others credited in this post are responsible for you breaking your phone! You do this at your own risk! This is given as a basic tutorial, but assumes some working knowledge of Windows and command line
The reason your battery does not appear to charge is that you are using CWM, which puts the Rezound in a recovery state (screen off) when the battery is run down too far. The recovery's kernel does not activate the LED while charging. CWM recovery also does not recognize use of the power button. Please see more about this below, in punman's replies to this post.
NilsP has posted a fixed recovery.img based on CWM Touch. This is essentially a kang of Koush's work, but the only change is the battery fix. Nils has tested the fix for a few months and feels confident that it works properly. Neither he nor I take any credit for this. The fix was provided punman (many thanks to you), who is willing to field support questions, as noted below in his responses, and know far more about the recovery than I do. If you use the "fixed" CWM recovery found here for download, please give him your thanks.
EDIT: The "fixed" CWM Touch works in two ways:
1. - If you replace your current battery with a charged one.
or
2. - If you leave your Rezound charging for a few minutes, then use the command "adb reboot."
The following steps should bring your rezound back and are based on djh816's guide for "Debricking your Rezound" here http://forum.xda-developers.com/showthread.php?t=1711408. Thanks to djh816 for his work on this.
What do you need?
1. A Windows 7 PC
2. Fastboot and ADB installed (you do not have to install the Android SDK, unless you want to). Links to these two programs are common in the development section and throughout xda.
3. Patience
Start up your PC and place a copy of the file I have attached into the directory where you have placed ADB and Fastboot on your PC. Rename this file "recovery." If you have deselected "Hide extensions for known file types" in your advanced folder viewing settings, confirm that the file is named "recovery.img"
Plug in your Rezound and confirm you receive a USB connection sound. If you don't get the connect sound, install HTC Sync and try connecting again. Make sure you select "Charge only" on your Rezound
With Windows 7, search in the Start menu for "cmd" and right click on the cmd program selecting "Run as administrator" - click "Yes" or enter your admin credentials in the UAC dialog box.
In the command line window, type "cd" and the path to the ADB/Fastboot directory.
ex.: "cd C:\Users\WookieFan\Desktop\ADB" (excluding quotations)
Type the following exactly (excluding quotations):
"adb devices"
If the list of devices is blank, unplug your Rezound and plug it back in to confirm you hear the USB connect sound.
If you have a device listed, type the following (as always, no quotation marks):
"adb reboot recovery"
If you have not had your phone plugged in for ten minutes or more at this point, this command may do nothing. After a few minutes, your Rezound will have trickle charged enough to reboot into CWM, so keep trying every few minutes.
Once you've successfully booted into a normal recovery state, leave the phone charging on your PC for an additional 15 minutes. There is some debate whether or not the Rezound charges in CWM recovery. It has done so for me, even though the charging indicator light does not come on.
Now type:
"adb reboot"
Your phone will now be charged around 10% and should reboot normally. You can charge it up using a regular outlet at your convenience. If you are unable to reboot your phone normally, wait a few minutes more and try again.
To avoid this problem in the future, flash Amon Ra or TWRP recoveries via Hasoon's All-In-One Toolkit v2.x found here:
http://forum.xda-developers.com/showthread.php?t=1504824
Or, if you prefer to continue using CWM, take a deep breath and try the following:
With your phone connected to your PC via USB, type the following into your command line window:
"adb devices"
and confirm your device is listed. Then type:
"adb reboot bootloader"
After a short wait, your phone will reboot to the bootloader (HBOOT) and you will see the familiar white screen with skateboarding androids. "Fastboot" should be highlit at this time.
Now type:
"fastboot flash recovery recovery.img"
You will receive a confirmation that the flash went through successfully and you will now have a fixed version of CWM Touch recovery installed. Now type:
"fasboot reboot"
This will bring you back to a normally operating Rezound. But wait! there's one more step.
Before you take this next step, I would also suggest that you go into ROM Manager settings and confirm that "Quick Backup and Restore" is checked and "Use External Storage" is checked.
Using the root explorer of your choice, navigate to the clockworkmod directory. The full path will be something like this:
/%root%/mnt/sdcard/ext_sd/clockworkmod/
Create a file in this folder named ".hideandroidprogress" - this is a hidden file, so once you've created it correctly, you may not see it in the directory.
At this point ROM manager and CWM will work primarily as you would expect. I have heard that there are issues flashing ROMs or recovering backups from internal storage, but I did not test this, since I feel it is best to keep backups on your external storage and to flash ROMs and backups from there as well.
As always, be careful, ask questions and read through the instructions. Good luck!
Thanks for the post. However, I would still recommend users stick with Amon Ra or TWRP.
I agree - Amon Ra is presented as the preferred choice. I'll provide a link to the Amon Ra and TWRP recovery pages in the OP.
Battery fix version doesn't work for me. If I plug the phone while off the led will come on like before then goes off shortly after. Then the phone won't boot without pulling the battery. I know you were just reposting the file for Nils but I thought I should let others know.
zhp pilot said:
Battery fix version doesn't work for me. If I plug the phone while off the led will come on like before then goes off shortly after. Then the phone won't boot without pulling the battery. I know you were just reposting the file for Nils but I thought I should let others know.
Click to expand...
Click to collapse
Ok, I've tested replacement of the dead battery with a charged one with no issues. Testing with charging a discharged battery later tonight, but with "regular" CWM, replacement with a charged battery didn't help.
I'll confirm results later.
Sent from my ADR6425LVW using Tapatalk 2
WookieFan said:
Ok, I've tested replacement of the dead battery with a charged one with no issues. Testing with charging a discharged battery later tonight, but with "regular" CWM, replacement with a charged battery didn't help.
I'll confirm results later.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Cool. I will try it again just in case. My battery was at like 40% or so when I powered it down. Honestly, I have so many batteries that there's always one with something on it laying around. But it would be nice to have a working version in that rare rare event it dies and I'm away from home and forgot a spare.
zhp pilot said:
Cool. I will try it again just in case. My battery was at like 40% or so when I powered it down. Honestly, I have so many batteries that there's always one with something on it laying around. But it would be nice to have a working version in that rare rare event it dies and I'm away from home and forgot a spare.
Click to expand...
Click to collapse
I can confirm - if you are using the USB cable to charge your battery inside your Rezound after a full discharge (or down to 8% or so), it appears at first that nothing has changed - you will still go into the screen-off recovery but your phone will continue to charge normally - you can either replace the discharged battery with a charged one, or wait roughly ten minutes (while charging through a power outlet, not a PC) and then remove the battery and replace it. Your Rezound should charge normally after this and you should be able to turn it on.
I will note the OP, accordingly.
zhp pilot said:
Battery fix version doesn't work for me. If I plug the phone while off the led will come on like before then goes off shortly after. Then the phone won't boot without pulling the battery. I know you were just reposting the file for Nils but I thought I should let others know.
Click to expand...
Click to collapse
Ignore the charging led, the kernel in Koush's recovery image doesn't know how to turn it on. What you're seeing is the Rezound firmware turning on the charging led while it's doing power-up stuff, but once control is transferred to the recovery kernel the light will go off, but it's still charging. CWR also doesn't know anything about the keycode for the power button in the screen-off recovery mode.
Plug your phone in for a few minutes and do an "adb reboot" instead of hitting the power button. This should get you enough charge (if you're using the image posted here) to boot into Android proper, which has all the right software.
When you plug a Rezound in with a dead battery, the phone detects USB power and no battery charge and then boots a mini-recovery image with some special flags that tell the kernel not to display anything and just charge the battery. Problem here is that Koush's CWR image isn't set up to run in this special recovery mode, but Amon Ra's is.
Even with the "fix" to get your phone to charge in recovery, the power button won't work, so when you all keep trying to "power on" your phone after unplugging it, what's really happening is that it's ignoring you completely, and very slowly draining your battery more while still running in recovery. That's why there has been some success reported with pulling the battery at this point, but if you wait too long or your battery hasn't charged enough, you still won't have enough juice to boot.
[Advanced users: you can run a dmesg in the mini-recovery and watch the BATT lines to see what level it's at before doing a reboot, 10% should be enough to get you booted.]
I'm the "anonymous" fixer, btw. Not so anonymous any more, but I figured if this is posted, I might as well chime in.
Good luck.
punman said:
Ignore the charging led, the kernel in Koush's recovery image doesn't know how to turn it on. What you're seeing is the Rezound firmware turning on the charging led while it's doing power-up stuff, but once control is transferred to the recovery kernel the light will go off, but it's still charging. CWR also doesn't know anything about the keycode for the power button in the screen-off recovery mode.
Plug your phone in for a few minutes and do an "adb reboot" instead of hitting the power button. This should get you enough charge (if you're using the image posted here) to boot into Android proper, which has all the right software.
When you plug a Rezound in with a dead battery, the phone detects USB power and no battery charge and then boots a mini-recovery image with some special flags that tell the kernel not to display anything and just charge the battery. Problem here is that Koush's CWR image isn't set up to run in this special recovery mode, but Amon Ra's is.
Even with the "fix" to get your phone to charge in recovery, the power button won't work, so when you all keep trying to "power on" your phone after unplugging it, what's really happening is that it's ignoring you completely, and very slowly draining your battery more while still running in recovery. That's why there has been some success reported with pulling the battery at this point, but if you wait too long or your battery hasn't charged enough, you still won't have enough juice to boot.
[Advanced users: you can run a dmesg in the mini-recovery and watch the BATT lines to see what level it's at before doing a reboot, 10% should be enough to get you booted.]
I'm the "anonymous" fixer, btw. Not so anonymous any more, but I figured if this is posted, I might as well chime in.
Good luck.
Click to expand...
Click to collapse
Thanks for clarifying for everyone.
punman said:
........
I'm the "anonymous" fixer, btw. Not so anonymous any more, but I figured if this is posted, I might as well chime in.
Good luck.
Click to expand...
Click to collapse
Thanks for chiming in. I didn't want to volunteer you, so we did not have to support it, but thought it was worth posting originally.
NilsP said:
Thanks for chiming in. I didn't want to volunteer you, so we did not have to support it, but thought it was worth posting originally.
Click to expand...
Click to collapse
I think if it's useful and has been stable for a few months (on my phone too) it's probably ok at this point. I'm certainly willing to try to answer questions if people are having problems.
Hey guys - made a few changes to reflect this discussion. Let me know if you feel I got it wrong, and many thanks to punman for his work and input here.
Still need help with this PLEASE!
Hey guys,
I know this thread hasn't been used in almost a year and a half, but I would love it someone could help me out with this issue!
My Rezound with CWM won't power up so I believe this thread describes my problem. I've tried the instructions given here for a few days now and I can't get it to work.
When I plug my phone into the computer I hear the "plugged in" sound. However, after typing "adb devices", no devices are listed. I've unplugged, replugged, tried reinstalling drivers, google usb drivers, htc sync drivers, and nothing seems to help my phone being recognized by adb.
Oddly, when my phone is plugged in, two drives show up in My Computer just as they had when this phone used to work. However, those two drives are greyed out and unclickable (when clicked, it says "please insert media into drive..").
Can anyone help me with getting adb to recognize the phone so I can fix it and retrieve all my data on the internal storage?!
Thank you!
Alex
puckgenius said:
Hey guys,
I know this thread hasn't been used in almost a year and a half, but I would love it someone could help me out with this issue!
My Rezound with CWM won't power up so I believe this thread describes my problem. I've tried the instructions given here for a few days now and I can't get it to work.
When I plug my phone into the computer I hear the "plugged in" sound. However, after typing "adb devices", no devices are listed. I've unplugged, replugged, tried reinstalling drivers, google usb drivers, htc sync drivers, and nothing seems to help my phone being recognized by adb.
Oddly, when my phone is plugged in, two drives show up in My Computer just as they had when this phone used to work. However, those two drives are greyed out and unclickable (when clicked, it says "please insert media into drive..").
Can anyone help me with getting adb to recognize the phone so I can fix it and retrieve all my data on the internal storage?!
Thank you!
Alex
Click to expand...
Click to collapse
Alex,
You'll have to help out by being more specific. I am sorry that I have not had a chance to respond sooner, but I was away traveling when you wrote your question.
Where do my instructions break down? You say that the drives show up in your "My Computer" directory, but you cannot open them. Do they appear to have the blue colored USB drive icons when they appear in My Computer, or are they a grey/white color? If grey/white, then they are not being recognized as drives (they are not mounting properly), which probably means you never installed the Rezound drivers from HTC.
Either way, there should be a fairly simple solution. Remove your battery and charge it with an external charger or try a new, charged battery. If the Rezound hasn't had a battery in it for more than a few hours, a charged battery should work normally.
If you don't want to go through the trouble of getting an external battery charger or extra battery, then make sure to charge the battery for about two hours on the wall charger and then try connecting the Rezound to your PC.
Make sure to install the Rezound drivers from HTC on your PC - they will be part of a HTC Sync download/installation. Uninstall HTC Sync, and the drivers will remain on your PC.
Make sure you've installed ADB & Fastboot (instructions for this found all over xda) before trying the ADB commands. If you don't have those files on your drive, my process won't work for you. Also, I would highly recommend using another recovery - Amon Ra or TWRP - whichever one is most highly recommended by the good folks here now - I have since moved on to a One X, so haven't been following the Rezound threads at all.
We can also do a G+ hangout if you like and I can walk you through some of this, but I won't be able to do that tonight.
Good luck, either way. And i hope I have helped.
WookieFan said:
Alex,
You'll have to help out by being more specific. I am sorry that I have not had a chance to respond sooner, but I was away traveling when you wrote your question.
Where do my instructions break down? You say that the drives show up in your "My Computer" directory, but you cannot open them. Do they appear to have the blue colored USB drive icons when they appear in My Computer, or are they a grey/white color? If grey/white, then they are not being recognized as drives (they are not mounting properly), which probably means you never installed the Rezound drivers from HTC.
Either way, there should be a fairly simple solution. Remove your battery and charge it with an external charger or try a new, charged battery. If the Rezound hasn't had a battery in it for more than a few hours, a charged battery should work normally.
If you don't want to go through the trouble of getting an external battery charger or extra battery, then make sure to charge the battery for about two hours on the wall charger and then try connecting the Rezound to your PC.
Make sure to install the Rezound drivers from HTC on your PC - they will be part of a HTC Sync download/installation. Uninstall HTC Sync, and the drivers will remain on your PC.
Make sure you've installed ADB & Fastboot (instructions for this found all over xda) before trying the ADB commands. If you don't have those files on your drive, my process won't work for you. Also, I would highly recommend using another recovery - Amon Ra or TWRP - whichever one is most highly recommended by the good folks here now - I have since moved on to a One X, so haven't been following the Rezound threads at all.
We can also do a G+ hangout if you like and I can walk you through some of this, but I won't be able to do that tonight.
Good luck, either way. And i hope I have helped.
Click to expand...
Click to collapse
Thank you so much for getting back to me.
I've included a screenshot of what's going on and where I'm held up.
I reinstalled HTC sync 3.3.63 and the drivers installed.
I plug the phone in, hear the plug in sound, the orange LED turns on for about 10 seconds then turns off, and then the devices listed in my device manager show up: HTC Android Phone under disk drives, Portable Devices now show E: and G:, and USB controllers now show USB Mass Storage Device. Nothing shows up anywhere about "Adb Device" or anything like that, which I'm pretty sure I've read is supposed to show up in Device Manager
My Computer then shows the two Removable Disk drives E and G, but they are greyed out.
Again, these devices only show up when I actually plug the phone in.
In the command prompt, daemon opens up but is unable to detect any devices.
I'm actually using a battery that I bought online last week. The same exact sequence of events happened when I first put the battery in several days ago.
You mentioned I need the ADB and Fastboot files on my drive. They are installed on my computer through the SDK manager, but I only did that recently ie: after my phone bricked. Was there something I had to do to my phone before it bricked for it to be recognized by the Adb software?
Thank you so much for your help!
puckgenius - I will get back to you tonight, but a quick answer to your last question is yes - ADB also has to be enabled on the phone, although many cooked ROMs have this set by default. Also, "fast boot" should be disabled in the phone. This is not the same as Fastboot which is a bootloader function. Confused yet? More to come.
Sent from my HTC One X using Tapatalk
I actually had this issue for almost a year with no idea how to fix it. So I simply took it apart and put it back together. That did the trick after praying to God. XD Haha. I immediately changed the recovery, ROM, and other things.
Josh8550 said:
I actually had this issue for almost a year with no idea how to fix it. So I simply took it apart and put it back together. That did the trick after praying to God. XD Haha. I immediately changed the recovery, ROM, and other things.
Click to expand...
Click to collapse
What do you mean you took it apart? What specifically did you take apart and then put back together?
Thank you so much for the help!
This probably isn't helpful because I'm guessing you've tried this but when I had this problem, I charged it overnight, pulled the battery, put it back in and the phone worked.
puckgenius said:
What do you mean you took it apart? What specifically did you take apart and then put back together?
Thank you so much for the help!
Click to expand...
Click to collapse
I took the whole thing apart. I just started removing whatever I could with a screwdriver, prying the back pieces off until I reached where the screen, digitizer, etc connect to the motherboard. I didn't want to mess with the hassle of fiddling with the ribbons so I stopped, put it back together, plugged it up for a while, and it booted up when I pressed the power button.
Putting the battery in an HTC Thunderbolt, another Rezound, or a charger might be necessary to charge it up enough to actually boot however. I used my sister's Thunderbolt to charge the battery.