This phone has gotten me wanting to quit technology altogether. I have had so many problems with mine, I can't even explain how irritated I am and how good an iPhone sounds to me. Phone rejects all usb connections, can't stay on for more than half an hour (If I can get it to boot fully) I don't even know what to do anymore. I know I could probably get it RUU'd, only thing is that I can't lock its bootloader anymore. And also broke my root. Superuser and su are still there, but superuser can't gain root access, neither can anything else. Tried factory resetting and reflashing my rom, but that didn't work for more than 10 minutes. Honestly if I could, I would torch this phone and leave it in a ditch, unless someone has a way for me to RUU without needing to lock the bootloader, because I'm pretty sure that's the only way I can do it.
I'm on CleanRom 4.[one version before the newest]
Warranty it. But that sounds like a cluster**** of user error.
tekhna said:
Warranty it. But that sounds like a cluster**** of user error.
Click to expand...
Click to collapse
what he said. were these problems there when it was stock unrooted? doubt it.
Wow...I've had no real problems with mine at all, except for some weirdness with recovery and Boot Manager yesterday. But I finally managed to clear those up. This has been a great phone for me. I don't intend to assume user error, but it's always a possibility...but don't give up and go to the iCrap...Android is still WAY better. Hopefully someone in the community can get ya straightened out.
Sent from my ADR6425LVW using XDA
tekhna said:
Warranty it. But that sounds like a cluster**** of user error.
Click to expand...
Click to collapse
The only reason why there's any problems is because none of my cables connect to my phone anymore. My stock one broke and so now I'm using the standard usb cables that every other phone has. usb connection has never worked since the switch. Also my phone was working fine till it decided to randomly reboot into death.
jayochs said:
what he said. were these problems there when it was stock unrooted? doubt it.
Click to expand...
Click to collapse
I don't blame you for blaming me, but the truth is I really don't think this is my fault. I have almost bricked my phone due to a batched RUU Flash, but it still worked fine after I got it out of the loop. And this all started happening recently. I dunno what to think.
ο χάκερ said:
The only reason why there's any problems is because none of my cables connect to my phone anymore. My stock one broke and so now I'm using the standard usb cables that every other phone has. usb connection has never worked since the switch. Also my phone was working fine till it decided to randomly reboot into death.
Click to expand...
Click to collapse
...are you using a data cable? Not all micro-USB cables work you know.
tekhna said:
...are you using a data cable? Not all micro-USB cables work you know.
Click to expand...
Click to collapse
Is there a difference? I've tried at least 6 different cables, brand-new out of the box to older used for other phone. I know I can connect older phones with the same cable, so I'm pretty sure it's a data cable.
ο χάκερ said:
Is there a difference? I've tried at least 6 different cables, brand-new out of the box to older used for other phone. I know I can connect older phones with the same cable, so I'm pretty sure it's a data cable.
Click to expand...
Click to collapse
the cable for the og droid should be a data usb cable, so try taht one. i know that we sell cables that actually don't work for sending data in my store, but come with a travel charger.
idk man, it sounds like you may have f'ed it up somehow. why can't you unlock it again? try RUU'ing the newest leak maybe?
jayochs said:
the cable for the og droid should be a data usb cable, so try taht one. i know that we sell cables that actually don't work for sending data in my store, but come with a travel charger.
idk man, it sounds like you may have f'ed it up somehow. why can't you unlock it again? try RUU'ing the newest leak maybe?
Click to expand...
Click to collapse
I know I had a feeling it was totally F'ed but I didn't want to quit. I use every cable and I thought it might be my SD card maybe? just maybe? and don't I need to be locked to run RUU's?
ο; χάκε;ρ;25712129 said:
I know I had a feeling it was totally F'ed but I didn't want to quit. I use every cable and I thought it might be my SD card maybe? just maybe? and don't I need to be locked to run RUU's?
Click to expand...
Click to collapse
To run the exe, yes. But if you S-Off, it won't matter. It may be worth it.
FWIW, I know the 4G issue that occurs after flashing a radio is resolved by running the RUU then doing an hboot factory reset...maybe give that a shot?
Sent from my ADR6425LVW using Tapatalk 2
LunaticSerenade said:
To run the exe, yes. But if you S-Off, it won't matter. It may be worth it.
FWIW, I know the 4G issue that occurs after flashing a radio is resolved by running the RUU then doing an hboot factory reset...maybe give that a shot?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Can't S-OFF if I can't connect my phone to my computer.
The vzw corporate just agreed with me that the battery life is ****ty and sent me a gnex which ill be happy with since the battery is better and it has miui roms which I like
what i would reccomend doing is flashing the latest ruu.
to do this take out your microSD and put it in a sd card adapter and put the ruu onto the sd card and then run it, and then do an hboot factory reset
devilsrogue said:
The vzw corporate just agreed with me that the battery life is ****ty and sent me a gnex which ill be happy with since the battery is better and it has miui roms which I like
Click to expand...
Click to collapse
What was the process you went through to get this done?
I would definitly say you should warranty replace it. Dont know why you cant use a data cable to connect to pc, I use em all the time, sounds like a hardware issue with that. Unless you can data connect while in Recovery or in Hboot I would say just replace with warranty.
Just tell them about the heat issue....and bad battery life...they sent me another rezound and I complained again and now they sent me the nexus....I know im going to be happy with that phone...I can just smell it
devilsrogue said:
Just tell them about the heat issue....and bad battery life...they sent me another rezound and I complained again and now they sent me the nexus....I know im going to be happy with that phone...I can just smell it
Click to expand...
Click to collapse
I have a friend who did the same thing but regrets it now... He has horrid signal with the nexus
Sent from my ADR6425LVW using Tapatalk 2
I think some of the specs are ****tier but the batt is better and the design is better and it has the devs....
devilsrogue said:
I think some of the specs are ****tier but the batt is better and the design is better and it has the devs....
Click to expand...
Click to collapse
no, the specs aren't ****tier. however, the actual phone itself is ****tier. the pentile amoled screen with oversaturated colors, the terrible radio that gives awful 4g reception and awful 4g speeds when compared to a rezound. you act like we don't have the developers...really? have you ever been to the development subsection? either way, go enjoy your nexus. i'll continue to enjoy my customized rezound, thanks to our many developers.
Related
For some reason, when I go to flash a file in RSDLite 5.6, everything works until the program puts it into AP Fastboot. The program isn't able to recognize my phone and ends up displaying "The phone failed to switch to fastboot mode."
Any ideas?
Thanks!
Extra info - Win7 64x machine
I am having the same exact problem!! i was about to post a new thread when i found this.... hope someone can chime in and give us a heads up.
my problem is that i can only get windows to recognize my razr in bp flash SBF mode. it will not recognize my razr while in AP fastboot mode. no matter how many times i've tried. i have successfully flashed an sbf before.
since then i have removed and re downloaded the drivers just to be sure that i have the correct ones. thought it might be a usb cable so i switched it out along with multiple ports on the comp. i have no idea.
don't know if this helps but the only bootstrap i could use prior to bootlooping was razrbootstrap. cwmonboot would not work no matter what (which i had working once also) and i came from arctic rom where i also lost usb mode while booted. no options at all to connect to pc. thought that might have something to do with it.
i really hope this helps someone to point us in the right direction. if i don't find anything out tonight i am going to take it to verizon. thank you guys for all that you do!!
Kalvin
What a lengthy post haha. I think the problem may be that I was using my 64x laptop. Switched to my moms 32 and its made it much farther so far. *fingers crossed
Sent from my ADR6300 using xda premium
It was just about done, and I guess the battery got too low.....I'm screwed. It says it cant transfer because the battery is too low. Now im stuck in ap fastboot...
figured out my problem..... it wouldnt recognize my razr while in AP fastboot mode all because of me using a different cable. make sure you use the cable that came with the phone!! I thought i had the new cable but i was using an old one.
what a relief!! so that was my problem. if anyone experiences the same thing you know what to look for.
thanks XDA for somewhere to go to when i have a problem like this tho lol.
also have you tried to boot into AP fastboot then just hit the power button once. should just turn off the phone so that you can charge it on the wall charger for a while.
amberkalvin said:
figured out my problem..... it wouldnt recognize my razr while in AP fastboot mode all because of me using a different cable. make sure you use the cable that came with the phone!! I thought i had the new cable but i was using an old one.
what a relief!! so that was my problem. if anyone experiences the same thing you know what to look for.
thanks XDA for somewhere to go to when i have a problem like this tho lol.
also have you tried to boot into AP fastboot then just hit the power button once. should just turn off the phone so that you can charge it on the wall charger for a while.
Click to expand...
Click to collapse
I'm seriously about to lose it. Since it made it partially through the process, my phones soft bricked. It doesn't charge. I need a factory cable.
Sent from my ADR6300 using xda premium
jimbub said:
I'm seriously about to lose it. Since it made it partially through the process, my phones soft bricked. It doesn't charge. I need a factory cable.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Sorry to hear that, thankfully there's an easy mod if you have a sacrificial microUSB cable: http://forum.xda-developers.com/showthread.php?t=1403100
Sent from my XT910 using xda premium
onslaught86 said:
Sorry to hear that, thankfully there's an easy mod if you have a sacrificial microUSB cable: http://forum.xda-developers.com/showthread.php?t=1403100
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Ive seen it... I sadly dont own a soldering iron. I might try and bs it..... hopefully I don't blow anything up.
jimbub said:
Ive seen it... I sadly dont own a soldering iron. I might try and bs it..... hopefully I don't blow anything up.
Click to expand...
Click to collapse
Was hoping these were in stock, might be worth contacting them:
http://shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
Bought one a while back just in case.
Good luck getting it to charge!
WVULTRA said:
Was hoping these were in stock, might be worth contacting them:
http://shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
Bought one a while back just in case.
Good luck getting it to charge!
Click to expand...
Click to collapse
Been there too :/ Decided to contact them. Hopefully they get back to me! I will most likely take it to verizon though. Are they good about their warrenties?
jimbub said:
Been there too :/ Decided to contact them. Hopefully they get back to me! I will most likely take it to verizon though. Are they good about their warrenties?
Click to expand...
Click to collapse
I went through a situation of FCs with my first Razr that VZW nor Moto could diagnose, and local Verizon replaced it with no questions asked. But I'd only had it for 9 days. Was told VZW replacement period was 14 days; but I never confirmed it.
I was able to unroot/factory reset though before taking it in. Your's might be questionable unless you have a good relationship with the VZW dealer.
IMO, if your way past any warranty period, I'd hold out for a factory cable or get someone experienced to build you one via the post above.
Good luck!
WVULTRA said:
I went through a situation of FCs with my first Razr that VZW nor Moto could diagnose, and local Verizon replaced it with no questions asked. But I'd only had it for 9 days. Was told VZW replacement period was 14 days; but I never confirmed it.
I was able to unroot/factory reset though before taking it in. Your's might be questionable unless you have a good relationship with the VZW dealer.
IMO, if your way past any warranty period, I'd hold out for a factory cable or get someone experienced to build you one via the post above.
Good luck!
Click to expand...
Click to collapse
I'd be willing to buy one from anybody on here.
Did you ever figure anything out? Or Try charging the way I suggested?
Sent from my DROID RAZR using XDA App
amberkalvin said:
Did you ever figure anything out? Or Try charging the way I suggested?
Sent from my DROID RAZR using XDA App
Click to expand...
Click to collapse
Well, this morning my dad took it in (since it was his) and switched back over to his blackberry. Verizon was nice enough to overnight him a replacement my conscience is clear for exams
Sent from my ADR6300 using xda premium
not if you've rooted, that voids the warranty & gives them an excuse to hide their corporate heajs in the sand, & force people to do without a full system backup b/c they don't have root…
also, it saves them fm having to support all the difftroms, patches, etc.
So, yesterday morning this all went down. My Rezound has been nothing but an expensive paperweight. I am not new to the rooting game so save the nonconstructive comments.
Early Monday morning I felt the need to change things up a bit so I wanted to flash the latest CleanRom 3.7 to check it out (coming from BAMF v.09). I backed up all my apps & data and continued to make a nandroid backup (with Amon_Ra 3.14). After that, I completed the necessary wipes (including boot because Scott packages his roms with the kernel) in recovery and then flashed CleanRom 3.7 (MD5 sum matched) then booted into bootloader to flash the kernel. Everything went perfect with that.
After the phone booted I realized how low on battery I was on but connected to Wi-Fi during the initial start-up on the new rom. I got all my accounts and data synced/restored and was getting ready to knock out. I set my alarm, placed the phone on the wall charger and confirmed it was charging by the orange light around 3am.
I woke up yesterday morning around 7:30am and realize I'm running late. I pick up my phone to see if the time is correct and I get nothing but a black screen. Pulled the battery...nothing...plugged in the phone without the battery..then plugged in the battery...nothing. On my 45 minute commute to work I removed the battery and let the phone sit (hoping some magic would happen lol) and nothing changed.
When I made it to my office, I plugged the phone in to see if it would accept a charge and 2 hours later nothing. I have the 3.7v battery and have had no indications of a bad battery (short life, warm, etc.). Due to the circumstances, I was left with no choice but to go to the local VZW and order a replacement.
The guy at the Verizon store plugged my phone in the wall charger and saw it was not accepting a charge. Swapped the battery with his own personal Rezound and mine worked in his, however, his fully-charged battery would not work in mine. Narrowed it down to the phone itself which blows. I thought at worst it would be the battery.
I am really curious how/why this all went down of all times when I wasn't doing anything to my phone. You guys/gals have any idea?
Marcismo55 said:
and continued to make a nandroid backup.
Click to expand...
Click to collapse
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
My bad..I forgot to mention I have been running Amon_Ra from the start. I've never ran CWM on my Rezound and I did run across some threads regarding the charging issues associated with CWM.
Thanks though!
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
mpalatsi said:
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
Click to expand...
Click to collapse
Yes. All the contacts were intact and free of dirt/debris.
pkopalek said:
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
Click to expand...
Click to collapse
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
More than half of all the roms out there are from ports/leaks. Please explain.
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
nosympathy said:
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Actually I didn't even take the SIM out. Maybe I should have given that a try.
EmerikL said:
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
Click to expand...
Click to collapse
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
That's only for charging when you're booted into recovery if I'm not mistaken...
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If flashing killed it, it would have never booted back up...
Marcismo55 said:
Actually I didn't even take the SIM out. Maybe I should have given that a try.
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
Click to expand...
Click to collapse
In my case when the Verizon rep gave me the phone he put the sim in and put it in backwards. To be fair, it does go in "backwards" to every other android phone I have owned haha.
Sent from my ADR6425LVW using XDA
mjones73 said:
That's only for charging when you're booted into recovery if I'm not mistaken...
Click to expand...
Click to collapse
It may depend on how you're charging. The charging process requires some intelligent oversight - if you power off the phone, and connect a charger, the process is controlled by code loaded from somewhere. I think that code is in, or loaded by, the recovery. That would tend to explain things like this, this, this, and this.
jayochs said:
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
Click to expand...
Click to collapse
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Marcismo55 said:
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Click to expand...
Click to collapse
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
^This. Even if it is new hardware there can be defects. **** happens!
Marcismo55 said:
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Click to expand...
Click to collapse
I assessed your OP as related to a phone not charging.
I see what you mean, now. My points were in the case of non-charing, or failure to charge (and a phone going dead on the charger) which aren't things I've seen on any stock-based ROM, but very much so on ICS ROM's (and Kernels, as such).
I bid you good luck on your replacement hardware. Stuff happens!
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
I understand Scott. I am in now way shape or form saying flashing your ROM was the reasoning behind all this as I have flashed numerous times before this and had no issues. Also, considering I am one of the very few this has happened to, i think its pretty obvious this was a hardware failure. I
I'll be running your roms soon enough
Thanks to everyone providing insight on this situation. I'll be back at it again very soon!
Just throwing it out there. As the title states. I attempted the S-off, failed a couple of times, more than likely due to my timing on the wire trick. Then my computer was unable to find device anymore. Long story short, I got my rom to reboot, however the phone will not connect to computer or charge. Tried Pc, Mac, different usb cords. Wiped, reinstalled rom, pulled battery, etc..
This is a risk that I took, and I take full responsibility for that. But just beware that this could affect your hardware and not just your software too, which makes sense because you are messing with the hardware. I am def in the minority here, but I thought I would share. But something to think about. The phone now still functions but I have to take out the battery to charge, and I can't push any files to the phone.
ive never heard of anyone's usb port getting fried with the s-off method but i guess it's possible since your basically grounding your device out.
I know it won't help you with fastboot, but you can still do ADB over wireless. Look for instructions on how to enable it via terminal, or just go the the store and find a widget or app to enable it. At least with functional ADB, you can still push files to your phone using wifi tether or if they are on the same wireless network.
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
con247 said:
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
Click to expand...
Click to collapse
do you think the wire trick is causing this? if soo that's kinda scary.
fix-this! said:
do you think the wire trick is causing this? if soo that's kinda scary.
Click to expand...
Click to collapse
I had the exact same thing happen to me on my original Rezound, while I was doing all sorts of fastboot stuff to completely wipe it and prepare it to be shipped back to Verizon. In the end, it shipped back to them in a state where it would ONLY boot to hboot, because it had no /boot or /system or /data or /recovery partitions or anything. I don't really know what happened, but before I could run the RUU to complete the job, the USB connection just stopped working and it wouldn't charge. Exactly the same situation, except it was on its way back to Verizon anyway with a dead screen so I didn't bother to investigate any further.
To the people who have had the problem, were you using an uninsulated wire?
tekhna said:
To the people who have had the problem, were you using an uninsulated wire?
Click to expand...
Click to collapse
Or else inadvertantly touched the wrong terminals ? Just trying to figure out how it could happen.
lack of usb function was a product of a corrupted misc image on the HTC Desire. It is possible the same thing happened here so that is being tested. It is worth looking into as a last resort before sending it back.
Yes I was using an insulated wire. I placed the wire exactly where the pictures show. I'm really not sure what happened. But at least I have a backup phone.
Sent from my Galaxy Nexus using XDA
con247 said:
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
Click to expand...
Click to collapse
Thanks con
Sent from my Galaxy Nexus using XDA
Knew I didn't wanna do it.
Sent from my ADR6425LVW using xda premium
http://forum.xda-developers.com/showthread.php?t=1620803
Here's a case of fried USB but no s-off. Currently unlocked. Any ideas?
Snuzzo said:
http://forum.xda-developers.com/showthread.php?t=1620803
Here's a case of fried USB but no s-off. Currently unlocked. Any ideas?
Click to expand...
Click to collapse
Sounds like he is in the exact same boat as me. Will be following that thread as well.. Thanks.
Me three
In same Boat.
Please post a cure if you find one.
Another nice option for transferring files is SSHDroidPro used with something like WinSCP.
I know you tried wiping your rom, but did you try an RUU? On the off chance it is a corrupted partition that might be able to fix it. Worth a try anyway.
I'm trying to brick my device so i can downgrade to 1.40. Everything is fine up until the point where i have to pull the battery out and run off AC power without battery. When i pull out the battery the phone stays on like it is supposed to, but when i press volume + button to start update the phone immediately turns off.
I relocked my device and am running this stock rom. If anyone can offer some advice it would be greatly appreciated
Thank you
Are you using the actual HTC charger that came with the phone? I've read here on XDA that the stock HTC charger puts out a little more power than normal chargers. Also, you can't use USB via your PC.
thefsfempire said:
Are you using the actual HTC charger that came with the phone? I've read here on XDA that the stock HTC charger puts out a little more power than normal chargers. Also, you can't use USB via your PC.
Click to expand...
Click to collapse
Yep, using the one that came with the phone and i'm plugged into the wall. I even tried a couple different outlets. Do i need to have a certain rom installed?
jeffhbo said:
Yep, using the one that came with the phone and i'm plugged into the wall. I even tried a couple different outlets. Do i need to have a certain rom installed?
Click to expand...
Click to collapse
That shouldn't matter since we're dealing with just the bootloader. I'm not sure which guide you're using (if there's even more than one now) but here is the link I followed: http://forum.xda-developers.com/showthread.php?t=1547695
Make sure you boot recovery, remove back cover, plug in phone then pull battery when it says.
Yesss this sh*t is impossible.! I actually got pissed off cuz I COULDNT brick the damn phone lol
Sent from my PG86100 using XDA
ognimnella said:
Yesss this sh*t is impossible.! I actually got pissed off cuz I COULDNT brick the damn phone lol
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
I know right! Never thought I'd be mad cause i couldn't brick my phone. Next time someone says they're scared about rooting cause they dont wanna break their phone, I'll tell them they couldn't do it if they tried.
I think I'm going to go back to HTC unlock. The only reason I decided to downgrade my phone in the first place was because i wanted to flash Newtoroot's rls3 and was not able to get it running without losing service. At this point I think I can get that rom to work on 1.50 before i can get this SOB to brick, much less get through the rest of this damn process. If not, I'll just go back to rls1, cause i had that version running perfectly (bugs listed in OP excluded).
Good luck to anyone who's trying to do this...may you have better luck than I did lol.
Sincerely,
J
thefsfempire said:
That shouldn't matter since we're dealing with just the bootloader. I'm not sure which guide you're using (if there's even more than one now) but here is the link I followed: http://forum.xda-developers.com/showthread.php?t=1547695
Make sure you boot recovery, remove back cover, plug in phone then pull battery when it says.
Click to expand...
Click to collapse
I had this problem where my phone would turn off as well..I was using a stock htc charger that came with the E3d. What I did was hold my charger steady because if I moved it too much the charge would leave. No I didnt have a shortage in my charger but it just read like that in the laptop. Probably because being plugged into the laptop or cpu it doesnt feed off enough voltage. Hope this works for you.
I don't know how many times I posted because of this, but I think I'm done trying to fix it.
My phone, regardless of ROM, computer, or cable, etc, will isn't seen by any computer
I've installed all the drivers (through HTC sync) multiple times and on multiple computers. I've tried new roms, stock roms, nothing. New cables old cables, nothing. I've even formatted my SD cards and tried that way, nothing. I've tried the wireless ADB, and I get "<waiting for device>" which of course is never going to be found. I don't really think there's anything else I can do at this point but assume that it's my phone's USB port is damaged, can I replace that though?
Any ideas? And also someone could tell me about replacing hardware on this phone, that'd be great.
Thanks anyone.
ο χάκερ said:
I don't know how many times I posted because of this, but I think I'm done trying to fix it.
My phone, regardless of ROM, computer, or cable, etc, will isn't seen by any computer
I've installed all the drivers (through HTC sync) multiple times and on multiple computers. I've tried new roms, stock roms, nothing. New cables old cables, nothing. I've even formatted my SD cards and tried that way, nothing. I've tried the wireless ADB, and I get "<waiting for device>" which of course is never going to be found. I don't really think there's anything else I can do at this point but assume that it's my phone's USB port is damaged, can I replace that though?
Any ideas? And also someone could tell me about replacing hardware on this phone, that'd be great.
Thanks anyone.
Click to expand...
Click to collapse
Does it charge over USB?
AshtonTS said:
Does it charge over USB?
Click to expand...
Click to collapse
You mean if I plug it into a USB port will it charge?
Yes
All I know is that in my experience my phone stopped showing when I installed HTC drivers. It only came back up when I reinstalled windows. Try more computers before you determine it as a physical defect
Sent from my ADR6425LVW using xda app-developers app
cincyelite22 said:
All I know is that in my experience my phone stopped showing when I installed HTC drivers. It only came back up when I reinstalled windows. Try more computers before you determine it as a physical defect
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I have tried 5, and I'm positive it isn't a problem with any of them.
If it charges over USB I have a hard time thinking the USB port has issues... There is one common denominator over the 5 computers you have tried
I had the same issue, unfortunately it was an issue with the USB port. I went through many, many cables and PCs ( xp, vista, win7) and I finally gave up. Called big red and got a warranty replacement
Sent from my ADR6425LVW using Tapatalk 2
AshtonTS said:
If it charges over USB I have a hard time thinking the USB port has issues... There is one common denominator over the 5 computers you have tried
Click to expand...
Click to collapse
I appreciate your input, but I seriously doubt it.
Computer 1: very old, used 3 other phones, all no problems, ReZound isn't seen
computer 2: not used much, used 1 other phone with it, ReZound ins't seen
Computer 3: Brand spanking new, ultimate specs, fresh driver intallation, ReZound isn't seen (also had 2 different software versions installed - Win 7 Home Premium and Ultimate)
Computer 4: Not used, barely a year old, fresh driver install, ReZound still isn't seen
Computer 5 - Laptop: Same deal, newdriver, nothing.
TheBr0ken said:
I had the same issue, unfortunately it was an issue with the USB port. I went through many, many cables and PCs ( xp, vista, win7) and I finally gave up. Called big red and got a warranty replacement
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I don't have warranty
I think I'm screwed
ο χάκερ said:
I appreciate your input, but I seriously doubt it.
Computer 1: very old, used 3 other phones, all no problems, ReZound isn't seen
computer 2: not used much, used 1 other phone with it, ReZound ins't seen
Computer 3: Brand spanking new, ultimate specs, fresh driver intallation, ReZound isn't seen (also had 2 different software versions installed - Win 7 Home Premium and Ultimate)
Computer 4: Not used, barely a year old, fresh driver install, ReZound still isn't seen
Computer 5 - Laptop: Same deal, newdriver, nothing.
Click to expand...
Click to collapse
Idk man I always have trouble with the drivers for windows.. That's why I use a Mac anyway does it say like android device or android 1.0 or HTC USB Device or something to that effect when you plug it in WITHOUT installing the drivers?
AshtonTS said:
Idk man I always have trouble with the drivers for windows.. That's why I use a Mac anyway does it say like android device or android 1.0 or HTC USB Device or something to that effect when you plug it in WITHOUT installing the drivers?
Click to expand...
Click to collapse
Nothing, the phone doesn't even realize it's being connected, although if you restart the phone with a cable plugged in (whether or not it's plugged into a wall or computer) the phone pops up with the options to charge only, etc. None of the options do anything though.
ο; χάκε;ρ;29430152 said:
I don't have warranty
I think I'm screwed
Click to expand...
Click to collapse
Just tell them it's a defect with the rezound they'll replace it with a refurb. They cover it as long as its not physical damage you did which isnt your case.
Sent from my ADR6425LVW using xda app-developers app
cincyelite22 said:
Just tell them it's a defect with the rezound they'll replace it with a refurb. They cover it as long as its not physical damage you did which isnt your case.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
And what about the software changes? I can't RUU back because I can't re-lock or run the .exe
ο χάκερ said:
And what about the software changes? I can't RUU back because I can't re-lock or run the .exe
Click to expand...
Click to collapse
Brick it
ο; χάκε;ρ;29430152 said:
I don't have warranty
I think I'm screwed
Click to expand...
Click to collapse
How can you not? Us it physically damaged? Factory warranty should have you covered if not
Sent from my ADR6425LVW using Tapatalk 2
TheBr0ken said:
How can you not? Us it physically damaged? Factory warranty should have you covered if not
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Because he rooted it
ο; χάκε;ρ;29430501 said:
And what about the software changes? I can't RUU back because I can't re-lock or run the .exe
Click to expand...
Click to collapse
Why can't you? It's time consuming but you can. Run the ruu to get yourself back to stock. Lock the bootloader and s-on. Then you will be stock, unrooted and bootloader will say either relocked or tampered or whatever. Root it. S-off with junipbear but do not install the modified hboot. Then ruu again. You will now be completely stock, unrooted and bootloader will say locked. Worked perfectly fine for me.
Sent from my ADR6425LVW using Tapatalk 2
TheBr0ken said:
Why can't you? It's time consuming but you can. Run the ruu to get yourself back to stock. Lock the bootloader and s-on. Then you will be stock, unrooted and bootloader will say either relocked or tampered or whatever. Root it. S-off with junipbear but do not install the modified hboot. Then ruu again. You will now be completely stock, unrooted and bootloader will say locked. Worked perfectly fine for me.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I can't lock my bootloader because I can't make contact with my computer through a usb cable, that's the whole problem
AshtonTS said:
Brick it
Click to expand...
Click to collapse
That's what I was thinking actually
Erase everything so it doesn't even turn on, then just be like "Iunno what happened"
ο; χάκε;ρ;29430276 said:
Nothing, the phone doesn't even realize it's being connected, although if you restart the phone with a cable plugged in (whether or not it's plugged into a wall or computer) the phone pops up with the options to charge only, etc. None of the options do anything though.
Click to expand...
Click to collapse
If your phone doesn't realize it's plugged in, then you got a defect.
Verizon usually doesn't check for unlock/root and many people have successfully gotten replacements for rooted phones.
Sent from my ADR6425LVW using xda app-developers app