Two defective Rezounds

[quejo]

I ordered the Rezound last week and recieved it on the 16th..on the 22nd it started the continuous reboot. I ordered another Rezound and Verizon sent me a "Like New" Rezound on the 24th..on the 25th it went into a continuous reboot. Pissed off.

 

[rootbrain]

I ordered the Rezound last week and recieved it on the 16th..on the 22nd it started the continuous reboot. I ordered another Rezound and Verizon sent me a "Like New" Rezound on the 24th..on the 25th it went into a continuous reboot. Pissed off.

I hate say this and don't want to start anything, but IMO users with multiple "defective" units are usually the problem rather than the device.

I was at a VZ store and someone brought back a Rezound in bootloop and the reps were just going to exchange it. Having been out here and read the information on the bootloop fixes, I took the unit, removed the back and SIM, put the battery back in and rebooted.

Everything came back fine, re-inserted the SIM and the customer was back on the network.

I can believe you MIGHT have had the bad luck to get 2 defective units. If you come out here and tell us you got another, look within my friend.

 

[pappy53]

I ordered the Rezound last week and recieved it on the 16th..on the 22nd it started the continuous reboot. I ordered another Rezound and Verizon sent me a "Like New" Rezound on the 24th..on the 25th it went into a continuous reboot. Pissed off.

Why would they send you a "like-new" when you had the phone for only a week?

 

[rootbrain]

Why would they send you a "like-new" when you had the phone for only a week?

They always do that to save $$. You have to speak to a manager and be insistent. Did that with my last Blackberry. Wanted to send refurb to replace a problem unit, I insisted and they sent a new one. Tell them you will just return within the alloted time frame, reactivate your old phone and then be eligible for a discounted upgrade and you'll just get another phone in a week from after the records reflect your upgrade status as available.

 

[humpagardengnome]

I hate say this and don't want to start anything, but IMO users with multiple "defective" units are usually the problem rather than the device.

I was at a VZ store and someone brought back a Rezound in bootloop and the reps were just going to exchange it. Having been out here and read the information on the bootloop fixes, I took the unit, removed the back and SIM, put the battery back in and rebooted.

Everything came back fine, re-inserted the SIM and the customer was back on the network.

I can believe you MIGHT have had the bad luck to get 2 defective units. If you come out here and tell us you got another, look within my friend.

Once again, saved by a customer who knows the phone better than Big Reds own retail reps., that's hysterical. I always get a kick out of stories like this. I read awhile back that this exact same thing happened to another guy. He fixed the phone in front of the rep.& customer. They asked how he knew that, he said the xda-dev forum and the rep. said that wasn't an approved fix and made the guy who brought it in the store, exchange it. At least, your story had a more satisfactory ending.

 

[humpagardengnome]

I ordered the Rezound last week and recieved it on the 16th..on the 22nd it started the continuous reboot. I ordered another Rezound and Verizon sent me a "Like New" Rezound on the 24th..on the 25th it went into a continuous reboot. Pissed off.

I'm not sure why Rootbrain is blaming you but your issues w/ both phones weren't defective and it's not your fault you chose to return them. What happened w/ your phones is caused by an overlooked network setting. That popped up after the 2nd national outage. They hopefully have a patch in the works but it is easily remedied by doing a manual setting switch. If you want instructions for future reference, check this thread link out, it's not complicated by any means

http://forums.androidcentral.com/verizon-htc-rezound/139235-boot-loop.html?highlight=boot+loop

P.S. If you encounter an issue in the future hit up the forum before just returning a phone. There may be an easy fix that you can do on.your own.

 

[rootbrain]

I'm not sure why Rootbrain is blaming you but your issues w/ both phones weren't defective and it's not your fault you chose to return them. What happened w/ your phones is caused by an overlooked network setting. That popped up after the 2nd national outage. They hopefully have a patch in the works but it is easily remedied by doing a manual setting switch. If you want instructions for future reference, check this thread link out, it's not complicated by any means

http://forums.androidcentral.com/verizon-htc-rezound/139235-boot-loop.html?highlight=boot+loop

P.S. If you encounter an issue in the future hit up the forum before just returning a phone. There may be an easy fix that you can do on.your own.

Actually, I wasn't really blaming him,but you're right, I guess it did come off that way. This is really an issue with VZ reps who should be a little more knowledgeable about the phones they put on their network, OR with VZ for not creating a "knowledge base" for these reported issues that the reps can use to check for solutions beforehand. They just keep replacing phones.

The old "pay me now or pay me later" applies here.

 

[humpagardengnome]

Actually, I wasn't really blaming him,but you're right, I guess it did come off that way. This is really an issue with VZ reps who should be a little more knowledgeable about the phones they put on their network, OR with VZ for not creating a "knowledge base" for these reported issues that the reps can use to check for solutions beforehand. They just keep replacing phones.

The old "pay me now or pay me later" applies here.

I agree, it's not up to par but I think the blame falls more on the oem, than the carrier, regarding this problem. They only see the answers/troubleshooting in the database if HTC informs them of it. What bothers me more is that the upcoming bug fixing OTA, doesn't include the boot loop patch. Granted, it's unlikely finalized, but I fully expected to see it, atop the heap. I guess HTC enjoys getting Rezounds returned from Big Red.

Btw, you were right about returns, a large percent are due to user errors, not the phone by it's own accord.

 

[tkong]

I hate say this and don't want to start anything, but IMO users with multiple "defective" units are usually the problem rather than the device.

I was at a VZ store and someone brought back a Rezound in bootloop and the reps were just going to exchange it. Having been out here and read the information on the bootloop fixes, I took the unit, removed the back and SIM, put the battery back in and rebooted.

Everything came back fine, re-inserted the SIM and the customer was back on the network.

I can believe you MIGHT have had the bad luck to get 2 defective units. If you come out here and tell us you got another, look within my friend.

Actually, you are incorrect. My first Rezound came on Dec 28 and no less than 24 hours it got caught in the continuous boot loop. I took the battery AND sim card out then put both back in and rebooted. The boot loop persisted. You may have gotten that particular device to work by removing the battery and sim but mine did not work when I did it. It did not work when I took it to the store and the tech person did it and it didn't work for the manager when he did it.

I'm on my second Rezound, and as of Jan 25 multiple apps started force closing. Tech support advised that I hard reset. As of Jan 26, my second Rezound started powering itself off and when it came back on it read "no service".

These are defective devices, plain and simple.

I'm currently trying to get out of my Verizon contract without paying the ETF.

 

[humpagardengnome]

Actually, you are incorrect. My first Rezound came on Dec 28 and no less than 24 hours it got caught in the continuous boot loop. I took the battery AND sim card out then put both back in and rebooted. The boot loop persisted. You may have gotten that particular device to work by removing the battery and sim but mine did not work when I did it. It did not work when I took it to the store and the tech person did it and it didn't work for the manager when he did it.

I'm on my second Rezound, and as of Jan 25 multiple apps started force closing. Tech support advised that I hard reset. As of Jan 26, my second Rezound started powering itself off and when it came back on it read "no service".

These are defective devices, plain and simple.

I'm currently trying to get out of my Verizon contract without paying the ETF.

Rootbraiin, was fortunate if that's all he did to fix that cuatomers phone. Some phones respond better than others, it corrects itself upon a sim card reboot. So, if that was all you did to correct it, I know why it returned so quickly. You omitted the most important steps in correcting the boot loop fix. You didn't revert the network setting that causes it. You may be correct but I don't think Rootbrain is misinformed, anyone who does it correctly, is good to go. It may trigger again at a later point since they haven't patched it, yet. Although, it likely won't in most cases

Check this..... http://forum.xda-developers.com/showthread.php?t=1394659