yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] PhantasmRezound:
Well who_mike_d isn't around right this moment. But to quote what he was saying in messages, double-click that .bat file to run it. It should launch the Dalvik Debug Monitor window.

Take the phone, pull the battery to ensure a fresh reboot. Power it on with the power button and connect via USB. Wait and see if the device shows up in the Dalvik Debug Monitor window with some activity.

If it does show, wait a minute or two more to see if it will boot into the ROM; then take a Screenshot in the program in the menu Device > Screen capture. Basically trying to see if there is a functional ROM which would rule out major hardware issues other than the LCD.

Edit: However, I'm still curious about that vibrate motor. You claim it doesn't work... it should vibrate when the phone very first powers up on a normal boot and just before the ROM loads and goes to the lockscreen. It will also vibrate whenever you boot into the recovery; only the bootloader doesn't vibrate. That is an odd thing to just break, whether it was when you disassembled or from the seller. Seems more likely that the motor is fine, but there are issues with the software you know? Counterpoint to that, however, is the thing charges fine... so at least some of the firmware is operating as it should.

Hmm.
[HTC Rezound] superbeak:
And if you get a screenshot, then you are good. Then swipe the screen to scroll your home page. Then take another screenshot. If it changes then yo have a good digitizer. In which case you only need a new LCD. Or does the rezpund have LCD and digitizer factory fused together?

Sent from my Nexus 7
[HTC Rezound] PhantasmRezound:
This. And the LCD and digitizer are glued together, just have to apply a heat gun or a hair dryer to them to separate for the the record.
[HTC Rezound] vetteguy112233:
Well.....I found the ddms file, double clicked it and it opened, I then installed the battery into the phone and pressed the power button. Win 7 made the noise and verified that a USB device was hooked up, but NOTHING at all changed on DDMS?
[HTC Rezound] superbeak:
Aren't you supposed to run ddms through adb and not just open it up? Otherwise it can't connect to the device.....correct me of I'm wrong I'm away from the computer and it is pretty late.try cd'ing to ddms directory in platform tools and use ddms through command line instead. (Or ./ddms?) Ive never had to use it sry. But yes. Command line..zzz.try that

Sent from my Nexus 7
[HTC Rezound] PhantasmRezound:
Well then, no adb connection. That is all that can really be concluded from this chain of events, not even a cause... best case scenario now is that it is possible the ROM boots, but USB debugging over the Android Debug Bridge is not enabled. Worst case being we still have a lemon, especially if the motor isn't vibrating when you hit the power button.

Try something a bit simpler, one that doesn't rely on all the potential issues with the ROM: try communicating with Fastboot via the bootloader.

Remove the battery and then remove the SD Card. The bootloader will scan the SD Card for PH98IMG.zip files on startup, so *if* the card contained one it would snag this procedure. Doubtful either the seller or you placed such a file on there in this state, but anyway...

Pop the battery back in. With it off the USB cord, press and hold the Vol Down key followed by the Power key; hold them down for a 3-5 seconds and the bootloader should load up. Press the power key by itself once and it should select the first hboot menu entry, "Fastboot".

Hook the phone up to the PC and you should hear the device connect sound on Windows.

Now, open up a command prompt on Windows at Administrator level. Assuming you're on Windows 7, you can go to the Start menu > Search "cmd.exe" > Right click and select "Run as Administrator".

Once you have the command prompt up, run a Change Directory (cd) command to the "platform-tools" folder within the SDK files. In my screenshot, that would be the path C:\Program Files\Android\android-sdk\platform-tools but you may need to adjust depending on your own install location. Either way, on the command prompt type "cd" followed by a space and then the path to the "platform-tools" folder.

Once the prompt reflects the new path, type "fastboot devices" and see if your device shows up or not. If it shows, this will confirm the bootloader and firmware at the very least are working properly, and the issue is just with the ROM. That is typically, easily fixable. If it doesn't even show a fastboot device, then there may be issues beyond the LCD and the vibrate motor...
[HTC Rezound] tomraedisk:
I had a issue like this when I had cwm installed were it gets stuck in a non interactive recovery. Had to reboot my phone though adb.

If that is the case do adb devices and it should say recovery. If so I believe it is adb reboot but I don't quite remember off the top of my head
[HTC Rezound] brisdaddy1207:
I'm going off topic to complement everyone in here. It's great to see the help you are giving someone and working together with no BS.. :):):):):):)

Like a great big family again.
[HTC Rezound] vetteguy112233:
I was thinking the same thing, I posted this in another forum and got NOTHING!!! I'm very appreciative of the help so far.

I tried the power/volume down again for 3-5 seconds and again, nothing.

I navigated to my android-sdk directory via the cmd prompt and typed "fastboot devices" it just created a blank line and then put me back to the command prompt.

What if my phone wasn't ever rooted or the software wasn't changed, would the "fastbook devices" still work? I know pressing power/volume down works regardless, but just got to thinking what if all these other steps only work on phones with modified files???

ALSO, I do not have a SIM card, my old phone is a 3G and since this phone doesn't "function" I didn't want to pay for a SIM card just yet.
[HTC Rezound] dottat:
Did you try the bat file again after win finished installing drivers for the adb device ?
[HTC Rezound] vetteguy112233:
Another thing I noticed... the micro sd card he gave me only has the following files/folders on it:

drv (folder with a wmodemdriverinstall.exe file)

img (folder with vendor.bmp and verizon.bmp picture files)

autorun.inf

TL-Bootstrap.exe

TL-Bootstrap.exe.manifest

tlbs.ini

VMMModeSelection.exe

My Samsung Fascinate's micro sd card has a very different file structure, more android type files, so I assume this means the phone has never had a successful boot with THIS micro sd card, otherwise it would have made all necessary files/folders??? Again, this micro sd card isn't the original, but it is a 16GB
[HTC Rezound] vetteguy112233:
Windows made the noise to tell me a USB device is plugged in and under safely remove devices it shows "android phone", so then I ran the ddms.bat file and the black DOS screen opened with a blinking curser and Dalvik Debug Monitor opened as well, but none of the information on the right has changed, it's all still empty

Is this what you are asking?
[HTC Rezound] wildstang83:
Yea, hey vette, just disregard what is on that sd card. What you need to do is just take it out of the phone, place it in a microsd card reader and just format it back to fat32.

Basically what I am saying is just make sure that sd card is completely empty and properly formatted to "fat32".

The files he has on that card right now belong to some other thing he was trying to do, sounds like to a totally different phone even :)
[HTC Rezound] wildstang83:
When that ddms window appears, look on the left. You will see the line that something about htc? Click that line to activate the log on the bottom.
[HTC Rezound] vetteguy112233:
Another question, the phone is just snapped back together without screws and I've been trying all this without the back battery cover on. I've since noticed that the battery cover has a bunch of electrical terminals, which I'm wondering if it has to be connected to the phone for any reason.
[HTC Rezound] wildstang83:
Well the battery cover doubles as the devices antennae. Without it the phone wont get data (4G/3G) signal.
[HTC Rezound] vetteguy112233:
As long as it's not causing the phone to not go through these tests, thats all I'm worried about.
[HTC Rezound] wildstang83:
Right, it won't effect any tests.
[HTC Rezound] vetteguy112233:
Another thing I just noticed...I wanted to format the micro sd card and can't find my reader, so I plugged the phone into the computer since it sometimes reads what I thought was the micro sd card, anyway I just got it to read again (it's hit and miss???) and it comes up labeled CDROM and shows the files I mentioned before, but it's properties show 0 byes of 6.71MB free and CDFS under that, so this appears to be data on the phone, not the micro sd card, but I can't confirm this since I can't find my card reader to see exactly whats on the micro sd card.
[HTC Rezound] PhantasmRezound:
Make sure it is the down the to sub directory "./android-sdk/platform-tools/" where the file "fastboot.exe" is located, same folder as the adb file. After changing directory, type out "fastboot help" to make sure it is functioning first. Once you confirm that launching fastboot from the PC isn't an issue, make extra sure the phone is on fastboot: When you start the bootloader by holding Vol Down and Power, wait ten seconds (and ten more if the SD Card is in, as the bootloader will scan it if present), then press Power one more time to select the first option on the bootloader's menu -- Fastboot. Then try that command prompt once again.

Fastboot should work on any reasonably functional device no matter the condition. It comes as part of the bootloader itself. You can't run certain commands when the bootloader is locked, but you can always communicate with Fastboot whether stocked or rooted.

Trying adb commands makes an optimistic assumption that the ROM is both bootable *and* has USB debugging enabled, which it isn't by default. If the guy's being truthful about the screen just conking out suddenly, should be able to assume the ROM was working. But still don't know about if debugging was enabled or not.

Fastboot should work or shouldn't: if you can't even detect the device over fastboot, something is wrong with the bootloader and would indicate the software is pretty messed up. Hard to repair the software if the bootloader isn't even working right.

SIM card and the backplate being on or off shouldn't affect any of these diagnostics either, as wildstang83 pointed out.

This phone uses the 16GB internal memory to create its default folders. It basically treats the phone memory as the main "SD Card" and the physical one as "External SD" or "SD Card 2" in the system. So don't expect that part to mean anything. The files that are on that SD Card he gave you are for USB Tethering to the PC, for the record. But those have no bearing on any of the diagnostics.

The CDROM folder is a virtual drive that Verizon puts into the stock ROM. It is just an emulated drive to install Verizon's sync applications on the PC, not an actual drive on the phone. Those files and that virtual drive are utterly useless to all this, other than giving the optimism that the software is still functioning in this phone's comatose state lol.
[HTC Rezound] vetteguy112233:
I think we might be getting somewhere.... after holding volume down/power for 25 seconds then pressing power one more time, windows actually said installing device driver this time and then said the driver was installed successfully. I then went into cmd and navigated to the platform-tools directory, where I typed "fastboot" and now a list of commands come up.....

ooo ooo ooo what next??????
[HTC Rezound] PhantasmRezound:
Try the command "fastboot devices". Hopefully it will show your phone's serial number *and* the word "fastboot" over to the right. If that is confirmed working, we can assume the bootloader works fine. Then we can reasonably conclude any software issues can be resolved if and when the LCD is repaired successfully.
[HTC Rezound] vetteguy112233:
That worked, it shows the serial number and Fastboot next to that.

If the screen is broken, the phone should still boot, just replacing the LCD wouldn't fix that.

Thoughts???
[HTC Rezound] vetteguy112233:
What about using my computer screen as the phone screen somehow?
[HTC Rezound] PhantasmRezound:
With the bootloader functioning as it is, worst case you could download a RUU file for the ICS update that just came out. Copy it onto the external SD card, rename it to PH98IMG.zip, and start the bootloader up with the card in the phone; doing the update blind to make sure it is back to stock and working normally. That is ultimately all the foothold you need to get it up and running. You could continue diagnosis still if you can get adb working, however, as that is more informative than fastboot.

Would help to know from the seller if they did HTCDev Unlock, rooted the phone. Or if it is fully stock and locked. If it is on the stock Gingerbread ROM, updated to ICS past couple of days, or an entirely custom ROM if rooted. Just for the sake of diagnosing if the ROM is working or not right now.

Assuming it is stock, the problem with adb is probably that it isn't turned on in the ROM. You could do a blind set of swipes on the screen to get to the setting.

You cannot use the PC as the phone screen unless adb is turned on. Try a normal reboot by unplugging and removing the battery, then re-inserting the battery and holding power (while still off the cord preferably.) Give it a while to do so, three or four minutes to be safe. Take that command prompt and run "adb devices" from the same directory. If nothing shows there, either the ROM is not working at all or just adb is off. Assuming then that only adb is the issue, you could try blind swipes according to what ROM is on it to access the setting and turn adb on.

To bring that last part full circle, if blind swipes don't work still, try running the RUU update in the first paragraph. Then you should have a working ICS ROM you can do blind swipes on with more certainty.

Well, unless the digitizer is damaged too lol.
[HTC Rezound] vetteguy112233:
As I guessed, I can't get ahold of the seller anymore, surprise, surprise! So getting any information from him is not an option, but the wife is ragging on me for trading stuff for a broken phone, so I have to get this fixed or I'll never hear the end of it.

I did unplug the cord and pull the battery, put battery back in and pressed power for 10 seconds and waited a few minutes. I then hooked the cable up, windows beeped, so I then went back into fastboot and typed "adb devices", to which it returned "list of devices attached" and a BLANK line.
[HTC Rezound] PhantasmRezound:
Well, going to try swiping to the debug setting blind then.

Could assume this is stock and on GB. Conflicting hints here: perhaps stock because of the Verizon virtual drive still being there (most custom ROMs remove this.) But the SD card has stuff that works only with rooted phones. Going to assume the stock GB ROM scenario nonetheless.

Now, need to figure out the exact blind swipe sequence needed to get to the USB debugging setting on GB.

For starters, a touch of the power/lock button to wake it up. Then a swipe from the bottom center edge going up for the unlock ring. From there... unsure, on ICS right now myself lol.

Need input on this from someone on stock GB or similar enough. Flashing a GB ROM myself in the meantime. Looking for a YouTube video of Gingerbread being demoed in lieu of that method as well.
[HTC Rezound] vetteguy112233:
If the phone was booting (just not visible because of LCD issue) wouldn't it write files to the SD card? Also, if it was booting I should get a vibration and sounds, shouldn't I?
[HTC Rezound] vetteguy112233:
Also, HTC Sync is installed and doesn't recognize the phone either.
[HTC Rezound] vetteguy112233:
I just typed adb devices again and something different came up this time.

adb server is out of date. killing....

* daemon started successfully *

list of devices attached

nothing was listed, just a blank line and returned me to the command prompt.
[HTC Rezound] PhantasmRezound:
No, it doesn't write any directories to the external SD card "automatically" as some other phones do. It might write a folder or two as you work with apps, but by default it doesn't configure any directories immediately on insert.

It doesn't have a boot sound on stock, but there should be a vibration. However, the vibration before the ROM gives as it nears the end of booting may be a lot weaker than the one when you first power on the phone. You may have to hold the phone and pay attention for the vibration just to notice it actually.

HTC Sync will only recognize it if the particular Sync option is selected on the prompt that pops up when USB is connected. Same boat as adb basically, the setting is not on by default.

That will happen from time to time using the adb command, it is simply refreshing the thing monitoring the connection from the PC side. Doesn't have bearing to the diagnostic procedure itself.
[HTC Rezound] vetteguy112233:
So, if this were your phone, what would you do next. I can watch youtube videos of people using the phone and might get lucky turning on USB debugging, doubtful though, but I'm willing to try, how would I know if i'm successful?

Anything else I should/could try?
[HTC Rezound] PhantasmRezound:
I'd go ahead and download the ICS update lol. Going to want to put that on there sooner or later.

http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/

If this round of blind swiping doesn't work... Download the latest RUU from there. Power off your phone (pull the battery and re-insert) and charge up until it is green. Preferably on AC wall charger to be quicker about it lol.

Rename the RUU file to PH98IMG.zip and copy to the external SD card. Boot into the bootloader with the SD card in and do the update blind. Get the thing back to stock and then we'll know exactly the state of the phone; we will know what precise swipes could be done to get the adb setting turned on and diagnose everything else.

In the meantime, still concocting the exact steps to activate USB debugging on this assumed GB ROM. Anybody else out there have any input on the swipes?

---------- Post added at 01:51 PM ---------- Previous post was at 01:34 PM ----------

See this video here for the layout of the screen menus on the stock GB, in order to turn on USB debugging:

http://youtu.be/dZEaYMKmHbw?t=1m44s

The tricky part is where he swiped down to Applications in the menu list, then back up some. :\ I'd observe carefully where he had stopped at the bottom of the menu, around 1:50 mark. Just before he scrolled up a bit, aim for a screen tap where "Applications" was listed at that brief moment.
[HTC Rezound] vetteguy112233:
If this were your phone, would you buy a new LCD?
[HTC Rezound] PhantasmRezound:
How much have you already put in? Is the digitizer and/or glass damaged as well? That may need replacing in addition to the LCD itself, which is more cash. Are there any other signs of damage inside beyond the LCD?

The software all seems to work. If nothing else appears damaged and $100 or less was invested in this, I'd personally buy the LCD first and install that. Hope the digitizer isn't broken as well but invest in that too if needed. The LCD is what, $30-$50 and the digitizer/glass bezel is another $20-$40. Looking at $50-$90 overhead perhaps.

I'd put a ballpark valuation of the phone at $200-250 used on the low end, so I'd be iffy on risking more than $150-200 parts + $50 time investment on this project.
[HTC Rezound] vetteguy112233:
I traded some speakers that I bought for $20, for the phone and dre beats earbuds and 16gb micro sd card. So I'm technically into the phone $20, but with the dre beats earbuds/16gb card I'm way ahead. He also gave me 2 laptops to fix and if he doesn't respond to my txts then looks like I own those too. The phone is in overall good condition, there is a black ring that runs around the outside of the phone that is trying to come off, but I can glue that back in place if the LCD fixes my problems. The digitizer looks like it's in good condition, but I understand that might need fixed too. I found an LCD on eBay for $35 free shipping and the digitizer is another $20 if needed. While inside the phone there was a bent contact, which I fixed, but I can't see anything that looks broken/damaged.

I think I'll just order the LCD and hope for the best.
[HTC Rezound] ruvort:
I'm not sure if you've opened it up at all but the ribbon attaching the screen to the device maybe loose or unhooked and that would cause the screen not to show.
[HTC Rezound] PhantasmRezound:
Why couldn't I find these people, I have some spare speakers rofl. :eek:

Sounds good, good luck.
[HTC Rezound] vetteguy112233:
This was the first thing I tried ;) I made sure the ribon cable connecting to the motherboard is good, I haven't seperated the LCD and digitizer yet. I plan on getting the new LCD and just plugging it into the motherboard and powering up the phone to see if that works, if it does, I'll seperate the screens and fix it correctly.
[HTC Rezound] merlin66676:
Androidscreen caster.
[HTC Rezound] vetteguy112233:
My phone doesn't actually show up in "adb devices" from the command prompt, it says "List of devices attached", but nothing shows underneath that.

This would be a really cool feature, if I could get my phone to show in that list. I'm following the directions here:

http://code.google.com/p/androidscreencast/

I have Java 6

Step 2 says connect your device and ensure that it's connected throud adb devices, from what I've learned from my earlier troubleshooting I'm opening the command prompt, navigating to the "platform tools" folder and typing "abd devices"

I've had it do 2 things, the first one it just says "list of devices attached" as mentioned above, but then I heard the computer make the USB connected sound, so I tried again and this time it says:

adb server is out of date....killing

*daemon started successfully*

list of devices attached

blank line and it returns me to the command prompt, I assume under "list of devices atttached" i'm looking for it to show HTC Rezound or something similar?

Suggestions?
[HTC Rezound] PhantasmRezound:
Yup, a serial number and the the word "device" out to the right.
[HTC Rezound] vetteguy112233:
The only way I was able to get it to show that earlier was to hold the volume down and power button for 25 seconds, then press power once more.

That's not what I want, is it?
[HTC Rezound] PhantasmRezound:
Nah, those were "fastboot" commands earlier. That's an entirely different command set than adb. Fastboot is a relatively small set of "maintenance" commands, used by endusers mostly for flashing stuff to memory. You can only do the remote viewing of the screen and other advanced debugging over adb.
[HTC Rezound] vetteguy112233:
So why would my phone show up in fastboot, but not adb?
[HTC Rezound] PhantasmRezound:
The bootloader, ROM, and recovery partitions function independently in the memory.

Fastboot works in the bootloader. The bootloader is intact and the fastboot command was easy to get to, just one extra push of the power button away in the menu options.

Adb requires the ROM, the Android OS, to be both booted and have USB debugging enabled in settings. Either the ROM doesn't boot properly at all, or it does but the setting is not enabled.
[HTC Rezound] vetteguy112233:
And thats why we were trying to enable usb debugging, got it now! I guess my only option is to wait for the LCD now.
[HTC Rezound] GMSweet:
This is a completly rookie guess, but when I was troubleshooting a regular PC LCD screen, I could see the desktop if I shined a flashlight directly into the front of the monitor. I have no idea if that is even possible with the Rezound's screen, but it's worth a shot. I would think booting back into fastboot would be the best place to check.

Of course someone more experienced with smartphone LCDs could correct me if I'm comparing apples to oranges.

I must say though, I've appreciated all the posts trying to help you out.

Matt
[HTC Rezound] vetteguy112233:
I do a lot of pc repair and I tried that first, lol, but thanks!